Status Listener Queues
When Order Management Server receives orders, it sends the orders to JMS queues, which are routed to the Orchestrator engine based on the type of the router configurator and routing condition specified by the administrator.
Multiple concurrent listeners can be listening for incoming orders on the Listener queue to let parallel processing of incoming orders. The number of such concurrent listeners is configurable.
Order Management Server receives a notification on status for orders in the system for fulfillment and supports two routers types, viz. Pass-through router and Filter based router.
Pass-through does not apply any condition on the incoming order message and passes the message to the default orchestrator.
| Name | Descriptions |
|---|---|
| Order Status Notification Queue | Destination queue for receiving status message from Orchestrator |
| Order Status Notification Queue Concurrent Listener | Order Status Notification Queue Concurrent Listener Count |
| Order Line Status Notification Queue | Order Line Status Notification Queue |
| Order Line Status Notification Queue Concurrent Listener | Order Line Status Notification Queue Concurrent Listener Count |
| Plan Status Notification Queue | Plan Status Notification Queue |
| Plan Status Notification Queue Concurrent Listener | Plan Status Notification Queue Concurrent Listener Count |
| Plan Item Status Notification Queue | Plan Item Status Notification Queue |
| Order Amendment Status Notification Queue | Order Amendment Status Notification Queue |
| Set Plan Queue | Destination queue for receiving execution plan from Orchestrator |
| Set Plan Item Queue | Destination queue for receiving execution plan item from Orchestrator |
| Set Plan Fragment Model Queue | Destination queue for receiving plan fragment from TIBCO Product and Service Catalog |
| Status Notification Dead Queue | Destination queue for poison message for status notification. Order Management Server moves the message to the dead letter queue after retrying a pre-configured number of times to avoid messages becoming poison message |
| Set Plan Dead Queue | Dead letter queue destination for execution plan |
| Set Plan Item Dead Queue | Dead letter queue destination for execution plan item |
| Set Plan Fragment Dead Queue | Dead letter queue destination for plan fragment |
| Update Jeopardy Configuration Rule Queue | Destination to send jeopardy rule updates |
| Enrich Migrated Plan Request Queue | Destination to send request to Jeopardy Management System to enrich execution plan with the jeopardy information |
The independent AFI, AFS, and Transient Data Store components have been rewritten in release 2.0.0 and they are now an integral part of Order Management Server. So apart from the above-listed queue configurations for core Order Management Server component, which are present since version 1.1.0, the queue/topic configurations corresponding to these three components have been added newly under separate categories in the configurator.