Deploying a new adapter service

When an adapter service is generated in the tooling, all of the necessary files are created for you to quickly deploy it into CICS. These files include JCL procedures that will compile the required programs, define the resources to CICS and update the properties file.

You can either run the JCL procedures remotely from Service Flow Modeler or run them directly in MVS. If you want to run them remotely, you must have remote systems configured in the tooling.
  1. Optional: Copy the generated adapter service output from the tooling to the correct location in MVS. If you have remote systems configured and select to remotely deploy the adapter service, this will occur automatically as part of the generation process.
  2. Run the batch job RDOJOB.jcl to define the programs, transactions and files to CICS®. RDOJOB.jcl is created when the adapter service is generated using WebSphere® Developer for System z® version 6. If you are using version 7 of the tooling, the JCL is generated with the format #jobname.jcl, where jobname is the name of the service flow project. The JCL uses a CICS-supplied utility called DFHCSDUP to update the CSD of the CICS region with the necessary resource definitions. If a resource is already defined, the job does not replace it.
  3. Run the batch job @jobname.jcl to update the properties file. If you are using version 7 of the tooling, jobname is the name of the request defined for the flow. A sample job called DFHMAMPU is also provided. This JCL runs the properties file update utility DFHMAMUP, that adds records for your adapter service and associated server adapters to the properties file.

    The job has a MODE parameter that determines whether or not the properties file should be updated if it detects a naming conflict. By default, the parameter is set to MODE=SAFE, to avoid overwriting any definitions of the same name in the properties file. If you get a return code other than 0 when you run the job, check the output. There could be a naming conflict to resolve. You can either change the batch job to overwrite the definitions in the properties file using MODE=OVERWRITE, or you can change the values in your batch job.

  4. Run any remaining JCL jobs to compile the programs that are needed by your adapter service.
  5. Install the CICS resources using the group name. The group must belong to the RDO list that was specified in the RDOLIST parameter of the post-installation procedure DFHMAINJ. The default list is CICSSFRL.
  6. Optional: If your adapter service is enabled as a Web service provider, or includes an outbound Web service request:
    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 post-installation steps.
    2. Copy the generated Web service binding file and optionally the WSDL to the pipeline pick up 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, this allows you to 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 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 adapter service is enabled as a Web service provider, and you want to receive Web service requests over HTTP, create a TCPIPSERVICE resource.
When you have completed these steps, the adapter service has been successfully deployed into CICS.