Creating the CICS infrastructure for a service provider

To create the CICS® infrastructure for a service provider, you must define and install a number of CICS resources. In many cases, CICS can generate some of these resources automatically.

For a service provider application deployed with the help of the CICS Web services assistant, you will need to define the following:
The transport infrastructure
If you are using the MQ transport, you must define one or more local queues that store input messages until they are processed, and one trigger process that specifies the CICS transaction that will process the input messages.
If you are using the HTTP transport, you must define a TCPIPSERVICE that contains information about defines the port on which inbound requests are received.
A PIPELINE resource definition
With its associated pipeline configuration file, the PIPELINE resource defines the attributes of the pipeline which is used to process inbound Web service requests, and the responses. Typically, one pipeline can process requests for many different Web services, and when you deploy a new Web service in your CICS system, you will be able to use an existing pipeline.

As well as the configuration file, the PIPELINE resource specifies a pickup directory, which contains Web service binding files.

When you install a PIPELINE resource, or when you issue a PERFORM PIPELINE SCAN command (using CEMT or the CICS system programming interface), CICS reads the files in the pickup directory, and creates URIMAP and WEBSERVICE resources dynamically.

Start of changePROGRAM resource definitionsEnd of change
Start of changeUnless you use autoinstalled PROGRAM definitions, you will need to supply a PROGRAM definition for each program that runs in the pipeline. These include the target application program, which normally run under transaction CPIH. The transaction is defined with the attribute TASKDATALOC(ANY). Therefore, when you link-edit the program, you must specify the AMODE(31) option.End of change
A URIMAP resource definition
The URIMAP is used to locate the pipeline that handles Web service requests. Although you can define and install URIMAP resources using RDO, you are advised to create them dynamically.
A WEBSERVICE resource definition

The WEBSERVICE resource defines the execution environment for your application.

Although you can define and install WEBSERVICE resources using RDO, you are advised to create them dynamically, using the Web service binding file that is created by the CICS Web services assistant.

Perform the following steps to create the CICS infrastructure for your service provider:

  1. Define the transport infrastructure. Repeat this step for each different transport configuration you need
  2. Define the pipeline. Repeat this step for each different pipeline configuration you need.
  3. Create a Web service binding file for each application program. Put the file into the pickup directory of the pipeline that you want to use for the service provider.
  4. Create a URIMAP and WEBSERVICE resource for each application program. Use the PERFORM PIPELINE SCAN command to do this. Repeat this step whenever you add a Web service binding file to the pickup directory for the PIPELINE.
Your CICS system will now contain the infrastructure needed for each service provider:
You can extend the configuration when you need to do so: