Installing web service support

Before you can run the web service support for the example application, you must create two z/OS® UNIX directories, and create the required CICS® resources.

The z/OS UNIX directories
Web service support for the example application requires a shelf directory and a pickup directory in z/OS UNIX.
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 act on web service requests and responses as they pass through the pipeline.
Creating a TCP/IP service
Because the client connects to your web services over an HTTP transport you must define a TCP/IP service to receive the inbound HTTP traffic.
Dynamically installing the WEBSERVICE and URIMAP resources
Each function that is 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 web service. Although you can use resource definition online (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 resource definition online (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 resource definition online (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.

Parent topic: Web service support for the example application

Last updated: Friday, 18 December 2020 08:52