Sequence of tasks for using CICS Service Flow Runtime and service flow project tools

The following sequence lists the tasks that you typically perform when using service flow project tools and CICS Service Flow Runtime.

About this task

Procedure

  1. At build time:
    1. Plan and design your implementation.
    2. Understand, design, and implement the service requester.
    3. Create the service flow using the service flow project tools. You will probably include the following tasks:
      1. Capturing existing EIS interfaces.
      2. Modeling a newly composed business service using these interfaces as a service flow.
      3. Generating the service flow runtime code.
    For detailed information on the task flow for using the service flow project tools, see the applicable sections of the help in the IBM Developer for z System z® tooling.
  2. Prepare your environment to install CICS Service Flow Runtime:
    1. Ensure that your site meets the programming prerequisites and space and storage requirements necessary to support the CICS Service Flow Runtime.
    2. Unload the CICS Service Flow Runtime modules from the media onto your z/OS® server.
    3. Set security and authentication parameters.
    4. Perform the necessary configuration tasks to correctly set up CICS Service Flow Runtime.
  3. At run time:
    1. Deploy service flows in the runtime development region on the z/OS server. This step assumes that, if required, FEPI, WebSphere® MQ, MRO, ISC, IRC, and CICS® transactions and custom programs, associated software and systems are already operational and available.
    2. Monitor performance of the CICS Service Flow Runtime.
    3. Address any problems.
    4. Deploy the service flows into production.


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