Monitoring the Transaction Archive
The Transaction Archive page lists the transactions that have been processed and archived on the
Arbortext PE server, according to archiving configuration. This report is available from the
Transaction Archive link on the
Arbortext Publishing Engine index page. The report displays the archived transactions from newest to oldest. The parameters that control the behavior for archiving transactions are described in
The Global Transaction Archive Parameters.
|
|
A transaction can be archived in an alternate location that is not available from the Arbortext Publishing Engine index page. The alternate transaction archive allows transactions containing sensitive data to be stored in a location where permission would be required to access them. Refer to The Global Transaction Archive Parameters for more information on the alternate transaction archive. |
Each transaction is identified by a unique ID that's assigned at the time the request was received. An ID may be reused only after the transaction it identifies is deleted from the archive. If the archive entries are configured to persist across Arbortext Publishing Engine sessions, IDs of transactions in the archive at startup also won't be reused until they're deleted.
A transaction name may appear on the Transaction Archive page if one has been specified by the
Arbortext Editor client, a
transaction-name query parameter (see
Queuing Query Parameters), or by the global
com.arbortext.e3.defaultTransactionName parameter (see
The Global Transaction Name Parameter).
Each transaction ID number is a link to the Transaction detail page displaying information about the selected transaction. Each transaction has a check box that you can select before choosing an action from the menu at the top. A global check box in the title bar (just above the first transaction) selects all transaction entries. Clearing this check box clears all check marks. Each transaction displays information about its operation, start and end time, result, and the requesting client.
For each transaction in the archive, Arbortext Publishing Engine stores a zip file that contains the following information:
• the request, including the function, URI, headers, query parameters, and request body
• the response, including status code, HTTP headers, and response body
• whether a transmission error prevented the response from being returned to the client
• whether the Arbortext PE sub-process terminated while processing the request. If so, it returns the associated termination error file, assertion message, COM error information, or other relevant error information.
• an application log for the request
• the intermediate files associated with the request
The menu offers the following actions:
• 
Delete Put a check mark in one or more boxes and then click this button to delete the selected transactions.
• 
Delete Successful Click this button to delete all successful transactions, which are those that have a returned status of 200.
• 
Zip Archive Put a check mark in one or more boxes and then click this button to return a zip archive containing information about each selected transaction.
