Arbortext Publishing Engine Preferences

The Publishing Engine category of the Preferences dialog box sets options for Using Arbortext Publishing Engine for Publishing Documents. If your site uses Arbortext Publishing Engine, you need to specify the URL of the Arbortext PE server.

• Use Publishing Engine check box — check the box to use Arbortext Publishing Engine to publish documents. Checking the box sends publishing requests to the Arbortext PE server specified by a URL. Clear the box to publish locally; local publishing requires that you have Arbortext Styler or appropriate licensing for Print Composer and Web/Wireless Composer.

• URL — specifies the URL to locate your site's Arbortext PE server. Follow the form:

where server-name is the host name of the server and port is the port that requests should be sent through. You will need to obtain the URL for your site from your Arbortext Publishing Engine administrator.

• The Status field reports whether the URL successfully connects to an available Arbortext PE server.

If the connection fails, click the Show Connection Error button to display the error message from the Arbortext PE server.

If you are using an Arbortext PE server for publishing and it supports queuing, you can set options in the Queuing box:

• Identification — specifies the user name of your login. This is a read-only field.

• Notification Email — specifies the email address where the Arbortext PE server should send notification of transaction results. An email notification application must be set up on the server, however, so check with your Arbortext Publishing Engine administrator for more information.

• Queue publishing transactions check box — specifies whether to always check the box to queue a request by default. This check box appears on each of the File > Publish dialog boxes.

Queuing on the server is configured by the server's administrator, so check with your Arbortext Publishing Engine administrator for more information on how your queued requests will be processed.

• Show transaction viewer after queuing check box — specifies whether to automatically launch the Queued Transactions Dialog Box (available from the Tools menu) after submitting a queued publishing request. You can retrieve your finished publication when it becomes available by selecting the transaction from the Queued Transactions list and clicking Download . In the Download Result Dialog Box, you can save and view the file.

• Delete transaction after downloading check box — specifies whether to automatically delete the transaction from the Arbortext PE server after you've retrieved it. A Delete button also appears on the Queued Transactions dialog box.

• Prompt before deleting a transaction check box— specifies whether to prompt you to confirm that a transaction should be deleted from the server.

• Prompt before overwriting a directory check box — specifies whether to prompt you to confirm overwriting an existing directory when you retrieve and save a published result from the Queued Transactions list by clicking Download . Some output types return a file and a subdirectory of related graphics files, such as HTML, RTF, or XSL. When the user chooses an existing location for saving the file, the subdirectory name and contents are also checked. When the box is checked, you will be prompted to confirm overwriting files in an existing subdirectory that is not empty.

• Advanced Transaction Options button — opens the Advanced Transaction Options Dialog Box. Your Arbortext Publishing Engine administrator will know if you need to set advanced options and can give you the instructions.

• Queued Transaction Names button — opens the Queued Transaction Names Dialog Box. Transactions are identified by their unique transaction ID, but you can assign a descriptive name to provide a readable description for the published document. Given that you can specify any text for a queued transaction name, it is not unique for finding a particular transaction or retrieving specific results. The name can include variables that can be resolved at the time the request is queued.