Deploying the Web services binding file

The Web services binding file created by DFHLS2WS is deployed into your CICS® region dynamically when you install a PIPELINE resource.

When a PIPELINE scan command is issued, either explicitly via a CEMT P PIPELINE() SCAN or automatically during a PIPELINE installation, CICS scans the pickup directory to search for Web service binding files - that is, for file names with the .wsbind extension. For each binding file found, CICS determines whether to install a WEBSERVICE resource.

A URIMAP resource is also created to map the URI, as provided in the JCL, to the installed WEBSERVICE and the PIPELINE onto which the WEBSERVICE is installed. When a scanned WEBSERVICE is discarded the URIMAP associated with it is also discarded.

  1. Modify PIPELINE(EXPIPE01), which is the PIPELINE definition for your provider pipeline. Change the WSDIR parameter to /u/exampleapp/wsbind. This pickup directory contains the Web service binding file that you generated with DFHLS2WS.
  2. Copy any other Web service binding files used by the application to the same directory. In this example, the files to copy are:
    • inquireCatalog
    • placeOrder
    They are provided in directory /usr/lpp/cicsts/samples/webservices/wsbind/provider.
  3. Install the PIPELINE. CICS will create a WEBSERVICE resource and a URIMAP resource from your Web service binding file.