Process Components

This component can be implemented in a variety of technologies depending on the required functionality. Typically this is TIBCO Fulfillment Provisioning.

All Process Components must adhere to the REST service contract specified by Orchestrator to be considered a valid Process Component. Process Components standalone rest service can be implemented using below mentioned rest documentation. For details, see "Process Component Technology Selection" in TIBCO® Order Management - Low Latency User's Guide.

Individual Process Components must be stand-alone components, which allows for changing the Process Component collection dynamically in real-time without requiring an order management outage.

All external component integrations are through the Process Components component. These integrations is generally either service calls to perform automated tasks or callouts to start a manual workflow.

The integration pattern for automated service calls take the form of Process Components sending out REST call to an adapter layer that includes relevant order and order line data as requested from the cache. This adapter layer then transforms the data into the format required by the back-end service and then invoke that service. When it has completed, it sends a response back to Process Components to complete the step in the flow.

Process Components are responsible for the following:

  1. Implement the tasks required to fulfill a particular product on an order. This might be done in any REST Web Service-enabled technology provided the interface specification for a Process Component is satisfied. For details, see "Process Component Technology Selection" in TIBCO® Order Management - Low Latency User's Guide.
  2. Accept Post planItemExecuteRequest from Orchestrator to start executing a new fulfillment process.
  3. Request required information from the cache that is required as part of a fulfillment process.
  4. Execute the required business process for fulfilling a particular product that a customer might order. This might take the form of invoking back-end service calls, business process management, or manual tasks as appropriate for the implementing technology.
  5. Update information in the cache as part of the fulfillment process if required.
  6. Return the execution results to Orchestrator.