Managing Queued Transaction Processing
• com.arbortext.e3.transaction.maxConcurrentQueuedTransactions
Specifies the maximum number of queued transactions that may run concurrently.
There are two other possible values, -1 and 0.
If it’s set to -1, the default, there is no specified limit, and the Queued Transaction Scheduler will execute as many queued transactions as it can match with idle Arbortext PE sub-processes.
If it’s set to 0, no queued transactions will be allowed whatsoever. Transactions may still be queued, but they will never be executed.
• com.arbortext.e3.scheduler.threadInterval
Specifies the number of seconds between execution of the Queued Transaction Scheduler. The thread checks for queued transactions ready for processing and idle Arbortext PE sub-processes, subject to the value specified for the global maxConcurrentQueuedTransactions parameter and the maxConcurrentQueuedTransactions parameter specified for each Arbortext PE sub-process pool. The default is 1 second.
You should not need to change this value.
In addition, the following parameters apply specifically to a site where Arbortext Editor clients are using Arbortext PE server to fulfill publishing requests. These parameters control whether the Arbortext Editor client is allowed to queue a request and to, optionally, submit information to receive notification about the completed transaction.
The settings for these parameters are included in the Publishing Configuration report that is sent to Arbortext Editor clients using Arbortext Publishing Engine for publishing. The Publishing Configuration document establishes the queuing policies for Arbortext Editor clients. Refer to Configuration Guide for Arbortext Publishing Engine.
• com.arbortext.e3.queueCompositionOperations
Specifies whether Arbortext Editor clients are allowed to submit queued publishing requests. The values are always, optional, and never. The value never means Arbortext Editor clients will never be permitted to queue a request. If queueCompositionOperations is not specified in e3config.xml, the default is never. However, e3config.xml ships with this value set to optional, which lets the Arbortext Editor user choose whether to queue a request.
• com.arbortext.e3.compositionIdentificationPolicy
Specifies a valid HTTP query parameter name used to identify the user making a publishing request. If it’s not specified, the default value is header. The e3config.xml file ships with this value set to header.
• com.arbortext.e3.compositionEmailPolicy
Specifies an HTTP query parameter name that will be used to provide an email address to Arbortext Publishing Engine. This is the parameter that will specify the email address where the Arbortext PE server will send an email notification, if a notifier is configured. If the query name is not specified, the default value is an empty string "", which means no email will be sent.