Rational Developer for System z, Version 7.6

Deploying the Web service artifacts to CICS

This topic describes how to deploy the Web service artifacts to CICS®

Setting up a CICS Web services provider PIPELINE

A TCPIPSERVICE resource using the HTTP protocol and listening on the desired port must be created and installed. First, create a PIPELINE resource that uses the previously created TCPIPRESOURCE. Within the PIPELINE resource definition, the WSDir or "pickup" directory must be defined which enables auto-install of Web services directly from WSBind files.

You can find detailed information on setting up a provider type PIPELINE in the CICS 3.1 documentation.

Moving generated artifacts to the host system

While building the XML converter programs, you deployed the XML converter load module to the host system. You now need to transmit the remaining artifacts, the WSBind and WSDL to the WSDir or "pickup" directory for the CICS PIPELINE under which the Web service will be installed. The "pickup" directory exists in an HFS on the target system.

Note: Both the WSBind and WSDL files are sensitive to codepage translation. Since the WSBind is in EBCDIC and the WSDL declares a UTF-8 encoding declaration, you must transmit these files in binary mode to the host system.

Auto-installing the Web service

After having transmitted the WSBind and WSDL to the PIPELINE pickup directory, you can do an auto-install if all of the fields on the advanced tab of the WSBind properties page in IBM® Rational® Developer for System z® are completed correctly. You can then issue a

CEMT PERFORM PIPELINE(pipelinename) SCAN

If this completes successfully you should see a new WEBSERVICE resource created by doing a

CEMT INQUIRE WEBSERVICE(*)

The name of the WEBSERVICE is derived from the first 31 characters of the WSBind file name. If you do a

CEMT INQUIRE URIMAP(*)

you will also see that a URIMAP resource is automatically created. The URIMAP resource maps a local URI to WEBSERVICE resource. By default full WSDL validation is turned off (for performance reasons). To turn it on you can do a

CEMT SET WEBSERVICE(webservicename)

and change "novalidation" to "validation". Doing this causes CICS to use the provided WSDL to do full validation of SOAP requests and responses related to this particular WEBSERVICE resource. The location of the WSDL that CICS uses for validation is visible when viewing a WEBSERVICE resource. If the WSDL specified in the WSBind file is not found at the expected location in the filesystem, the WSDL entry in the WEBSERVICE resource will be empty or blank.

Manually installing the Web service

The manual install is recommended for cases where it is not possible to know all of the necessary details to populate the advanced tab of the WSBind properties page in Rational Developer. The WSBind and WSDL need to be moved to the pickup directory.

The details of creating URIMAP and WEBSERVICE resources manually are explained in depth in the CICS documentation.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)