Broker Service

The orchestrator communicates with various services such as AOPD or Process Component. This communication is asynchronous.

There can be scenarios, where for some reason, a particular service cannot process a request and cannot provide the required response. For such cases, to recover the failed process and complete the asynchronous call, a new service, called the broker service, is introduced.

For this broker service, the existing notification table is used. Whenever the orchestrator sends a request to any service, the request detail is also saved in this notification table. The request is marked as pending until the asynchronous call is completed with a proper response from that service.

The followings notifications are saved for the broker event keys in the notification table:

  • ORDER_PLAN_DEVELOPMENT

  • AMEND_ORDER_PLAN_DEVELOPMENT

  • ORDER_FEASIBILITY

  • AMEND_ ORDER_FEASIBILITY

  • PRE_QUALIFICATION_FAILED

  • PLAN_ITEM_EXECUTE_REQUEST

  • PLAN_ITEM_FAILED_REQUEST

  • PLAN_ITEM_ACTIVATE_REQUEST

  • PLAN_ITEM_SUSPEND_REQUEST

  • MILESTONE_RELEASE_REQUEST

The broker service uses this notification table and retriggers any request, which is pending. The broker service is stateless and it just does the retriggering and does not make any write operations in the database.

For more information about broker APIs, see the TIBCO® Order Management Web Services Guide.