Arbortext Publishing Engine publishing supports both immediate and queued operations. Immediate operations do not use the queuing feature on the Arbortext PE server, and their execution follows the synchronous operation format. Queued requests use the queueing feature on the Arbortext PE server. The Client Composer transmits a request to the Arbortext PE server to queue the operation. The server returns a transaction ID, and the user can use Arbortext Editor’s Queued Transaction Viewer to determine when the queued request completes and to retrieve the queued transaction’s results.

A queued transaction is not an asynchronous operation in the sense it was described earlier. Asynchronous transactions do not persist past the termination of Arbortext Editor, but a queued transaction persists for as long as it’s configured to do so. You can submit a queued transaction request, exit from Arbortext Editor, and start Arbortext Editor at a later time and check the status of any queued transactions that you submitted using the Queued Transaction Viewer.

Only Print Preview and Print requests may be asynchronous, but Print Preview and Print operations, whether synchronous or asynchronous, may never be queued. If you submit an asynchronous Print Preview or Print request and then exit from Arbortext Editor, you’ll never get anything back from Arbortext Publishing Engine. The transaction ID which Arbortext Publishing Engine assigns to immediate synchronous transactions, is not returned to Arbortext Editor, so synchronous publishing operations are not visible in the Queued Transaction Viewer.