Orchestrator Interfaces

Fulfillment Order Management Orchestrator is the primary fulfillment engine and implemented in a Java component. Orchestrator requests Fulfillment Order Management AOPD to generate the execution plan for the order submitted by OMS. On receiving the execution plan from AOPD, it executes the plan tasks for order fulfillment.

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

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

1. AF_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, global variables, and so on.

2. AF_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 AF_TestHarness project.

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