The Arbortext Queue may be configured in e3config.xml with a TestSet element that specifies which transactions the instance of Arbortext Queue will accept for storage. If the TestSet is omitted, the queue instance will accept any transaction the Queue Manager offers it. Since queue managers offer transactions to the queues in the order configured in e3config.xml, this means that each queue except the last one should be configured with a TestSet.

It is important to note the distinction between a Queue Manager selecting transactions and a Queue selecting transactions. The Queue Manager determines whether a given transaction should be queued. If not, the Arbortext PE Request Manager treats the transaction as an immediate transaction. Once the Queue Manager selects a transaction for queuing (in the Arbortext implementation, by detecting queue=yes in the request), the Queue Manager offers the transaction to each configured Queue. Each Queue then determines, according to its configured criteria in e3config.xml, whether it is willing to accept the transaction.

If a Queue Manager determines that a transaction should be queued, but no queue is configured to accept transactions of that type, the situation is treated as a configuration error. The Queue Manager will return an error page to the Arbortext Publishing Engine Request Handler, which will return it to the client, and the transaction will not execute.