The runtime environment and BTS

CICS Service Flow Runtime uses the services provided by BTS to run service flows as business transactions in CICS.

An instance of a running business transaction in CICS is called a process. A process is a collection of BTS activities, where each activity is mapped to a traditional CICS transaction. The overall progress of the business transaction is controlled through a top-level program in the process that is called the root activity. The root activity in CICS Service Flow Runtime is the Navigation Manager (DFHMAMGR).

A service flow is invoked when a service requester sends a request message to the CICS Service Flow Runtime. The CICS SFR interface program DFHMADPL receives the request message and starts the Navigation Manager as the root activity, passing it the data from the request message. The Navigation Manager uses this data to run the required service flow as a hierarchical set of child activities, where data is exchanged between the activities in named areas of storage called data-containers. If the service flow is simple and contains one server adapter, the Navigation Manager runs the server adapter directly as a child activity. If the service flow is complex, the Navigation Manager initiates a flow navigator as the child activity. The flow navigator ensures that the server adapters are run in the correct order as determined by the service flow, managing each adapter as a child activity.

The following figure shows the components that are used when a service requester invokes a complex service flow.

Figure 1. The components used in request processing for a complex service flow
The image shows a service requester outside of CICS Service Flow Runtime invoking the SFR interface program DFHMADPL. This program starts the Navigation Manager as a BTS process, which runs as the root activity. The Navigation Manager invokes the flow navigator as a child activity, which in turn invokes the server adapters to perform request processing as child activities.

CICS uses the BTS repository to store information about the activities and processes that are running in CICS Service Flow Runtime. You must have one BTS repository for each instance of CICS SFR. You cannot share the repository between CICS regions.

The CICS Service Flow Runtime enables any application that can initiate a CICS® program to access these applications:

Several examples of service flows that implement business transactions are:



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