Data Queue Manager

This page is accessed via Business Process Automation > Integration > Data Queues.

Data queues use an infrastructure to handle asynchronous events within Oracle Transportation Management. Events can be written to database queues rather than memory queues. For each queue, a pool of threads is dedicated to periodically poll the queue for a batch of events and forward the events to an executor for processing. A single table can be partitioned into distinct virtual queues, each managed by a separate data queue process. The following queues must be set to Active if using Consolidated Notification: AdHoc and Consolidated. You must be a DBA to activate these. These default to inactive.

See also glog.dataqueue Properties.

The following public data queues are available:

• Ad-Hoc Consolidated Notify: processes notification requests consolidated by user selection
• Consolidated Notify: processes notification requests consolidated by recipient or date
• Integration In: processes inbound transactions
• Integration In Direct XML: an inbound method of sending inbound transmission XML to Oracle Transportation Management. The transmissions are saved directly into the database and the actual processing of the XML content is managed by this data queue.
• Integration Out Transport - FTP: processes outbound transactions through FTP

  Note: FTP is not supported.

• Integration Out Transport - HTTP: processes outbound transactions through HTTP
• Integration Out Transport - Queue: processes outbound transactions through Oracle Advanced Queuing

• Integration Out Transport - Service: processes outbound transactions through web services
• Integration Out XML Build: the process of building the XML transmission out of the DB tables and is the first step for all outbound transmissions. An XML build will precede the transport via one the four communication methods. You can configure the system so that it goes onto the XML build data queue and then when it processed from that queue it can go onto one of the TRANSPORT data queues.
• Lifetime: processes lifetime topics
• Message In: processes inbound messages for the Message Hub
• Message Out: processes outbound messages for the Message Hub
• Regular Notify: processes individual notification requests
• Scheduled Notify: processes scheduled notification requests
• Visibility: processes package shipment events

Note: Only one queue can be active for each event type per system.

The data queue manager collects the various power data into a single definition of the queue process.

Adding a Data Queue

1. Enter a unique identifier in the ID field.
2. Select a domain in which this data queue will be active from the Domain Name drop-down list.
3. Select the Active check box to make the queue active. If not selected, the system will ignore the queue.
4. Enter a number in the Thread Count field. This is the number of threads assigned to process requests in the queue. This field controls the number of transmissions processed.
5. Enter the Batch Size. This is a numeric field. It indicates the number of events to retrieve in a polling batch. If null, all events are retrieved. This field controls the number of transmissions processed.
6. Enter the Polling Frequency. This is the duration between queue polls. This field controls the number of transmissions processed.
7. Enter a Data Queue Table.
8. Enter a Data Queue Poller.
9. Enter a Data Queue Executor.
10. Enter a Finder Set for the event queue viewer.
11. The Handled by Event Queue field is reserved for future use.
12. When the Load Balancing is set to None, a server polling items in the data queue retrieves all pending items, queueing them up in memory if threads are busy. When Load Balancing is set to Thread Availability, a server polling pending items retrieves only as many items as it can immediately service in idle threads. For example, if you have three threads available, only three items are taken from the queue. If there are no threads available, it will leave the queue in the table and let it be processed by another server.
13. Enter a Related Queue if necessary.
14. Click Save for each related queue you enter.
15. Click Finished.