Before you can run the Web service support for the example application,
you must create two HFS directories, and create and install a number of CICS® resource
definitions.
Creating the HFS directories
Web service support for the example application requires a shelf
directory and a pickup directory in the Hierarchical File
System (HFS).
Creating the PIPELINE definition
The complete definition of a pipeline consists of a PIPELINE resource
and a pipeline configuration file. The file contains the details of the message
handlers that will act on Web service requests and responses as they pass
through the pipeline.
Creating a TCPIPSERVICE
As the client connects to your Web services over an HTTP transport
you must define a TCPIPSERVICE to receive the inbound HTTP traffic.
Dynamically installing the WEBSERVICE and URIMAP resources
Each function exposed as a Web service requires a WEBSERVICE resource
to map between the incoming XML of the SOAP BODY and the COMMAREA interface
of the program, and a URIMAP resource that routes incoming requests to the
correct PIPELINE and WEBSERVICE. Although you can use RDO to define and install
your WEBSERVICE and URIMAP resources, you can also have CICS create them
dynamically when you install a PIPELINE resource.
Creating the WEBSERVICE resources with RDO
As an alternative to using the PIPELINE scanning mechanism to install
WEBSERVICE resources, you can create and install them using Resource Definition
Online (RDO).
Creating the URIMAP resources with RDO
As an alternative to using the PIPELINE scanning mechanism to install
URIMAP resources, you can create and install them using Resource Definition
Online (RDO).
Completing the installation
To complete the installation, install the RDO group that contains
your resource definitions.