How the processing mode is selected

The service flow project tools enables a developer to select from five processing modes. These processing modes define how the service requester invokes a service flow and how the service flow is processed, either synchronously or asynchronously, regardless of the deployment pattern associated with the service flow.

The processing modes are as follows:

Asynchronous
The asynchronous processing mode is used only when the service requester is a WebSphere MQ-enabled application. All of the BTS activities run asynchronously.
Link
The service requester invokes a service flow synchronously and all of the BTS activities run within a single unit of work. This is the most efficient form of request processing.
Synchronous
The service requester invokes a service flow synchronously and all of the BTS activities run synchronously. If there is an error, the changes are not rolled back
Synchronous roll back
The service requester invokes a service flow synchronously and all of the BTS activities run synchronously. If there is an error, the changes are rolled back.

Although the developer selects the processing mode when the service flow properties file is generated, the processing mode can be overridden by the service requester.



dfhcr_processingmode.html | Timestamp icon Last updated: Sunday, 4 June 2017