Product overview

CICS Service Flow Runtime (CICS SFR) is the server runtime environment to the service flows that are modeled, generated, and deployed using the service flow project tools in the IBM Developer for z System z® product.

A service flow is a reusable composed business function that exposes a programming interface to a service requester in an Enterprise Information System (EIS). Depending on how the service flow is modeled, it can contain a wide variety of function, such as:

Service flows are implemented in two stages:

At build time
A developer uses service flow project tools for the following tasks:
  1. Model a newly composed business function as a service flow, using processes or services and their interfaces.
  2. Capture existing EIS interfaces, such as screens or communication areas.
  3. Generate the runtime code that is required to deploy the service flow into CICS Service Flow Runtime.
  4. Deploy the service flow into CICS.
At run time
A service requester invokes the deployed service flow to perform a business function as modeled in the service flow project tools. By composing EIS interfaces and exposing the resulting service flows, it enables you to transform or adapt the enterprise to a new set of operations and methods that move applications towards a service-oriented architecture (SOA).

The deployed service flow adheres to a deployment pattern that describes whether it is simple or complex, depending on the number and type of server adapters that are required to run the service flow. A server adapter is a program that performs a particular function that was modeled in the service flow; for example, a Web service request or a link to a target application program. There are two types of service flow:

CICS Service Flow Runtime can support the processing of service flows by using CICS® Business Transaction Services (BTS).

Note: Structured fields, with the exception of QUERY PARTITION are not supported.


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