Specifies the directory where Arbortext Publishing Engine puts transaction subdirectories. For every request, Arbortext Publishing Engine will create a subdirectory in this directory and store intermediate files in it, as well as build the response to the request. The default directory is explicitly set to activeTransactions. Its location is in the directory specified by com.arbortext.e3.tempFileDirectory, described in The Global com.arbortext.e3.tempFileDirectory Parameter.

If your implementation will process a large number or size of transactions, you should put the directory in a location that is not in the server’s temporary storage area. You should also periodically monitor the completed transactions directory to assess the disk space being used.

This parameter specifies the maximum time, in hours, that a transaction directory will be kept in the Active Transaction Directory. This parameter applies only to queued transactions that have been completed but the results have not been retrieved. The default is explicitly set to 168 hours (or one week).

When Arbortext Publishing Engine finishes processing a queued transaction, it notes the time. When the interval specified by this parameter has elapsed, Arbortext Publishing Engine may copy the transaction directory into the transaction archive (according to the setting of the com.arbortext.e3.transactionArchive.selector parameter). Either way, the transaction directory is then deleted.

Queued transaction results that have been retrieved are deleted according to the interval specified by maxRetrievedTransactionAge.

This parameter specifies the maximum time, in hours, that a transaction directory will be kept in the Active Transaction Directory. This parameter applies only to queued transactions that have been completed, and the results have been retrieved at least once. The default is explicitly set to 48 hours (two days).

After Arbortext Publishing Engine finishes processing a queued transaction, it’s available for retrieval. When Arbortext Publishing Engine receives and processes the first request to retrieve a queued transaction result, it notes the time. When the interval specified by this parameter has elapsed, Arbortext Publishing Engine may copy the transaction directory into the transaction archive (according to the com.arbortext.e3.transactionArchive.selector parameter). Either way, the transaction directory is then deleted.

Queued transaction results that have not been retrieved are deleted according to the interval specified by maxCompletedTransactionAge.