CICS Service Flow Feature
The Enterprise Service Tools provide six types of projects that allow you to transform an existing CICS application to a Web service or to integrate an existing CICS application into a Web service. The service flow specific project can also be driven by MQ Messages and CICS Transaction Gateway.
The service flow project view is one of the six project views provided in Enterprise Service Tools. It allows you to develop a comprehensive Web service that collects and processes data from multiple sources, such as programs, screens, databases, and Web service invocable processing.
The CICS Service Flow Feature must be installed to run the Service Flow project. The CICS Service Flow Feature requires CICS Transaction Server (CICS TS) V3.1.
The CICS Service Flow feature provides components that extend CICS TS by providing adapters that exploit CICS interfaces to invoke the CICS terminal-oriented transactions and COMMAREA programs required by the Web service generated from the service flow project.
In support of the latest capabilities of the Service Flow Modeler in WebSphere Developer for System z V7.0, the CICS Service Flow Feature is enhanced as follows:
Integration with Web services and MQ environments is more easily enabled by providing for the use of CICS TS channels and containers as input and output interfaces to a service flow.
Support for invoking Web services as part of a service flow is introduced.
Additional management and configuration capability have been introduced together with improved tracing.
The CICS Service Flow Runtime delivers adapters for access to existing CICS transaction and application interfaces using non-invasive techniques, so that the CICS application assets orchestrated by the service flow do not have to be altered to support the CICS business service flow. This helps enable the fast reuse of existing assets while helping to minimize the risk of the new implementation. If required, the CICS business service can persist state data related to the business service between multiple invocations of the CICS application interfaces.
Where there is a requirement to integrate information from non-CICS applications into the CICS business service, the Service Flow Runtime delivers a Web services adapter and a WebSphere MQ adapter that enable the CICS business service flow to access any application supporting these interfaces, wherever the application may reside in the enterprise solution architecture.
The base capabilities provided by CICS TS to access CICS application interfaces extend to capabilities such as:
Distributed Program Link (DPL)
WebSphere MQ Adapter
Front End Programming Interface (FEPI)
The CICS Service Flow Runtime exploits these capabilities when generating the CICS business service function to provide the implementation needed to reuse the existing CICS applications as components in the CICS business service flow.
For more information on the CICS Service Flow Feature, refer to 205-303