Orchestrator Interfaces

TIBCO Order Management - Long Running Orchestrator is the primary fulfillment engine and implemented in a Java component. Orchestrator requests TIBCO Order Management - Long Running Automated Order Plan Development to generate the execution plan for the order submitted by Order Management Server. On receiving the execution plan from Automated Order Plan Development, it executes the plan tasks for order fulfillment.

This section provides the details of interfaces exposed by Orchestrator for external integration.

For process component development, the following two project library files are shipped with the product under the $OM_HOME/be/projectLibs directory:

  • OM_Orchestrator.projlib - This library is used in the TIBCO BusinessEvents studio projects for BE 5.x based process component development. It contains the Orchestrator resources. For example, events, channels/destinations, XML payload schema, JMS connections, JMS application properties, and global variables.
  • OM_Orchestrator_ForDesigner.projlib - This library is used in the TIBCO Designer projects for the TIBCO BusinessWorks-based process component development and contains simple resources. For example, XML payload schema, JMS connections, JMS application properties, and global variables.
Note: This project library is used and imported in the OM_TestHarness project.

The XML schema for all the interfaces exposed by Orchestrator are available in the $OM_HOME/schemas/schema/orchestrator directory.