Orchestrator and AOPD Communication
Property | Description | Default Value |
---|---|---|
planGenerationQueue | Queue on which AOPD listens for all plan generation requests from Orchestrator. | tibco.aff.orchestrator.plan.generation.queue |
orchestratorInboundQueue | Queue on which the Orchestrator listens for all southbound replies that contain an originator header. | tibco.aff.orchestrator.inbound.queue |
orchestratorInboundNoOriginatorQueue | Queue on which the Broker Service listens for all southbound replies that do not contain an originator header. | tibco.aff.orchestrator.inbound.no.originator.queue |
The communication between the Orchestrator and AOPD takes place using EMS.
Submitting plan generation request
The Orchestrator submits the plan generation request to the planGenerationQueue
.
-
Gateway Mode: The Orchestrator submits the plan generation request to the
planGenerationQueue
without originator headers. In this scenario, AOPD sends the generated plan to the Broker Service on theorchestratorInboundNoOriginatorQueue
queue. The Broker service then assigns a new owner for the order and routes the message to theorchestratorInboundQueue
. -
Registered Mode: The orchestrator submits the request with the originator header. Consequently, AOPD sends the generated plan back to the Orchestrator on the
orchestratorInboundQueue
queue.
This modification utilizes EMS to boost both the reliability and efficiency of the communication flow between the Orchestrator and AOPD.