The following sequence lists the tasks that you would typically
perform when using Service Flow Modeler and CICS® Service Flow Runtime.
- At build time:
- Plan and design your implementation.
- Understand, design and implement the service requester.
- Create the adapter service using the Service Flow Modeler,
this could include the following tasks:
- capturing existing EIS interfaces.
- modeling a newly composed business service using these interfaces.
- generating a new adapter service.
- deploying the adapter service to the supported runtime environment.
For detailed information on the task flow for using the Service Flow Modeler,
see the applicable sections of the help in the WebSphere® Developer
for System z® tooling.
- Preparing your environment to install CICS Service Flow Runtime:
- Ensure that your site meets the programming prerequisites and
space and storage requirements necessary to support the CICS Service Flow Runtime.
- Unload the CICS Service Flow Runtime modules
from the media on to your z/OS® server.
- Set security and authentication parameters.
- Perform the necessary post installation procedures.
- Optional: Run the installation verification procedure
(IVP).
- At run time:
- Deploy adapter services in the runtime development region on
the z/OS server.
Note: This assumes that if required, FEPI, WebSphere MQ, MRO, ISC, IRC and CICS transactions
and custom programs, associated software and systems have already been made
operational and available.
- Monitor performance of the CICS Service Flow Runtime.
- Address any problems.