Process Component Technology Selection

You can implement standalone REST services of a process component. To implement a standalone REST service, you must generate the swagger.json file of the process component from the Swagger UI. See "Generating a Swagger JSON File" TIBCO® Order Management - Low Latency Administration.

Generally speaking process components can be classified by using a combination of the duration of the process component lifecycle and a description of the statefulness.

Process component duration defines how long it takes to execute all tasks in the plan item. There is no absolute number that defines a short against long-lived process component.

  • Short-lived – Generates planItemExecuteResponse and post it on Orchestrator without including DataService calls.
  • Long-lived – Generates planItemExecuteResponse and post it on Orchestrator including DataService calls.
  • Process component statefulness defines whether or not a process component needs to persist state internally during the life of an invocation. This does not include storing data by using Order Management Server data service interfaces, which is available for all process components. Instead, the determining requirement is whether or not state is stored directly within the process component:
    • Stateless – short-lived process component that is invoked and does not require state persistence.
    • Stateful – short or long-lived process component that is invoked and does require state persistence.

The choice of stateless or stateful process component is not necessarily determined by whether the backend systems being invoked are synchronous or asynchronous. Asynchronous backend system invocation is a common use case for stateful process component. However, it might be possible to pass a correlationID through the backend system that lets the use of a stateless process component. Consequently, a process component is defined as a logical entity that provides a given set of functionality. It does not necessarily translate directly into a single physical process that is invoked and runs to completion.

If a process component requires manual interaction then it is in almost all cases be defined as stateful.

Technology Recommendations based on Requirements

Some technology recommendations for a given set of conditions are as follows:

Requirement

Technology

Short-lived process that does one or many asynchronous invocations to back-end systems.

TIBCO ActiveMatrix BusinessWorks™ 6.5.0

Long-lived process that does one or many asynchronous invocations to back-end systems.

Java