More About Queues and the Queued Transaction Scheduler
The operation of the Queued Transaction Scheduler is constrained by:
• the com.arbortext.e3.maxConcurrentQueuedTransactions global parameter, which limits the number of queued transactions that can be executed simultaneously.
• each Arbortext PE sub-process pool’s maxConcurrentQueuedTransactions attribute, which limits the number of subprocesses from that pool that can be allocated to executing queued transactions.
Each queue object determining whether transactions are eligible for execution and for determining the order in which their transactions execute.
The Arbortext Queue shipped with the product can be configured to :
• allow transactions to execute only on specified days as well as during specified times of day.
• require that a transaction does not start until transactions higher in the queue have started or until transactions higher in the queue have finished executing.
• limit the number of transactions it contains that can execute simultaneously.
• sort transactions into priority order, either based upon an explicit parameter when the transaction’s request is transmitted to Arbortext PE Request Manager or as specified from a Queuing administration web page.
It is possible to configure several separate instances of the Arbortext Queue in e3config.xml, each accepting different transactions and having different attributes, so that different kinds of transactions are executed according to different rules. All the queuing configuration parameters are explained in Configuration Guide for Arbortext Publishing Engine.