Deployment patterns

Developers use service flow project tools to define a combination of elements or characteristics that describe how the service flow runs in the CICS Service Flow Runtime environment to process requests.

Deployment patterns vary depending on the characteristics of the service flow and the nature of the request. For example, a service flow that models a complex business transaction might require access to multiple target applications and might result in data being updated. While a service flow that models a simple business transaction might require access to only a single target application and result in no data being updated. The differences between simple and complex service flows mean that different processing patterns are used at run time.

Single connector simple patterns

A single connector pattern consists of a single server adapter program as modeled in service flow project tools to compose a service flow. The server adapter program can consist of one or more interactions with multiple target systems, but does not require a flow navigator to manage request processing. This pattern supports simple screen-sequencing if the server adapter type is FEPI or Link3270. Only one server adapter can be generated in a single connector pattern.

The single connector pattern does not support WebSphere® MQ server adapters, the program link server adapter, and the Web service server adapter.

There are two single connector patterns:

Nonpersistent single connector pattern
The term nonpersistent means that no record is written to the BTS repository data set to reserve the name of the BTS process. If a pattern is nonpersistent, the CICS SFR interface program uses the BTS NOCHECK option on the BTS DEFINE PROCESS command. Using this option improves BTS performance by removing the need to write to the repository and its associated logging. It also requires little if any BTS configuration.
Persistent single connector pattern
The term persistent means that a record is written to the BTS repository data set to reserve the name of the BTS process. In this pattern, the CICS SFR interface program does not use the BTS NOCHECK option on the BTS DEFINE PROCESS command. Omitting this option ensures that the context of the service flow (the request and reply data, as well as an intermediate state data) is persistent through a failure.

Aggregate connector complex patterns

An aggregate connector pattern consists of multiple server adapter programs as modeled in service flow project tools to compose a service flow. Each server adapter program can consist of one or more interactions with multiple target systems. This pattern also includes the use of a generated and deployed flow navigator to mediate and control the progress of the service flow. During service flow request processing, multiple server adapters can run without requiring action by the service requester.

There are two aggregate connector patterns:

Nonpersistent single connector pattern
The term nonpersistent means that no record is written to the BTS repository data set to reserve the name of the BTS process. If a pattern is nonpersistent, the CICS SFR interface program uses the BTS NOCHECK option on the BTS DEFINE PROCESS command. Using this option improves BTS performance by removing the need to write to the repository and its associated logging. It also requires little if any BTS configuration.
Persistent single connector pattern
The term persistent means that a record is written to the BTS repository data set to reserve the name of the BTS process. In this pattern, the CICS SFR interface program does not use the BTS NOCHECK option on the BTS DEFINE PROCESS command. Omitting this option ensures that the context of the service flow (the request and reply data, as well as an intermediate state data) is persistent through a failure.


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