Deploying a new service flow

When you generate the runtime code for a service flow in the tooling, all of the necessary files are created for you to quickly deploy it into CICS. These files include JCL that compiles the required programs, an optional CSD update job that defines the resources to CICS, and a service flow properties file.

Before you begin

You can either run the JCL procedures remotely from service flow project tools or run them directly in MVS. If you want to run them remotely, you must have remote systems configured in the tooling.

About this task

To deploy a new service flow:

Procedure

  1. Optional: Copy the generated service flow output from the tooling to the correct location in MVS. If you have remote systems configured and select to deploy the service flow remotely, this deployment occurs automatically as part of the generation process.
  2. Optional: Run the batch job #jobname.jcl, where jobname is the name of the service flow project. This file is generated only when you select the appropriate option in service flow project tools. The JCL uses a CICS-supplied utility, DFHCSDUP, to update the CSD of the CICS region with the resource definitions for the programs, transactions, and files for your service flow. If a resource is already defined, the job does not replace it.
  3. Copy the generated service flow properties file to the zFS directory that contains your service flows. This file has a .sfp file extension. You can also perform this step using service flow project tools.
  4. Run any remaining JCL jobs to compile the programs that are needed by your service flow.
  5. Optional: If you selected that the CICS resources should not be installed automatically when you install the service flow, you must install the required CICS resources using the group name. The group must belong to the RDO list that was specified in the RDOLIST parameter of the postinstallation procedure DFHMAINJ. The default list is CICSSFRL.
  6. Optional: If your service flow is enabled as a Web service provider or includes an outbound Web service request, follow these steps:
    1. Ensure that the appropriate PIPELINE resource is enabled in the CICS region to process the Web service requests. CICS Service Flow Runtime provides sample requester and provider mode pipelines, and creates the PIPELINE resources for these during the postinstallation steps.
    2. Copy the generated Web service binding file and optionally the WSDL to the pipeline pickup directory in HFS. Ensure that you put the files in the correct pipeline pickup directory. If you try to install a Web service binding file for a Web service provider application into a requester mode pipeline or vice versa, the CICS resources do not install in an enabled state. If you copy the WSDL, you can run validation against the Web service at run time to check that the data is being processed correctly.
    3. Run a scan of the pipeline using the PERFORM PIPELINE SCAN command. This command checks the pickup directory for new files and creates a WEBSERVICE resource based on the Web service binding file. If the Web service is a provider, a URIMAP resource is also created.
    4. Optional: If your service flow is enabled as a Web service provider, and you want to receive Web service requests over HTTP, create a TCPIPSERVICE resource.

What to do next

When you have completed these steps, the service flow is ready for you to install to complete the deployment process.


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