Routing of REST Requests to EMS

All order requests are processed sequentially by the same instance using EMS channels. The orchestrator uses EMS channels to achieve this.

For REST requests, there exists the possibility that a request is received by an instance that is not the owner of the order. Therefore, all POST requests are routed to the EMS with an originator header. These requests are no longer processed directly by the REST API. Instead, the REST API routes the requests to the EMS, where they are processed by the owner instance.

The following APIs are affected by this change:

Operation API Queue Name Remarks
Amend Order /v1/order/amend tibco.aff.orchestrator.order.amend  
Withdraw Order /v1/order tibco.aff.orchestrator.order.withdraw  
Suspend Order /v1/order/suspend tibco.aff.orchestrator.order.suspend  
Activate Order /v1/order/activate tibco.aff.orchestrator.order.activate  
Cancel Order /v1/order/cancel tibco.aff.orchestrator.order.cancel  
Purge Order /v1/order/purgeOrder tibco.aff.orchestrator.order.purge  
Bulk Action /v1/order/bulkaction Based on the action, value the request is redirected to the corresponding queue
Plan Item Execute Response /v1/planitem/executionreply tibco.aff.orchestrator.planItem.execute.reply  
Milestone Notify /v1/planitem/milestonenotify tibco.aff.orchestrator.planItem.milestone.notify.request  
Plan Item Suspend Response /v1/planitem/suspendreply com.tibco.fom.orch.planitem.suspend.response.queue  
Plan Item Error Handler /v1/planitem/errorHandler/reply tibco.aff.orchestrator.provider.planItem.failed.reply  
Plan Item Bulk Error Handler /v1/planitem/bulkErrorHandlerReply   Individual Plan Item Error Handler Reply message is dispatched to the EMS with originator headers.
Feasibility Reply /v1/order/feasibilityReply tibco.aff.orchestrator.provider.order.feasibility.reply  
Pre-Qualification Failed Reply /v1/order/preQualificationFailedReply tibco.aff.orchestrator.provider.order.prequal.failed.reply