Deploying the web services binding file

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

About this task

When a pipeline scan command is issued, CICS scans the pickup directory to search for WEBSERVICE binding files 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 resource and the PIPELINE onto which the web service is installed. When a scanned WEBSERVICE resource is discarded, the URIMAP resource associated with it is also discarded.

Procedure

  1. Modify the PIPELINE definition for your provider pipeline PIPELINE(EXPIPE01) in the CICS Explorer® by selecting Definitions > Pipeline Definitions . Double-click EXPIPE01 to open the Pipeline Definition (EXPIPE01) editor. In the Attributes tab, change the WS Directory parameter to /u/exampleapp/wsbind. This pickup directory contains the WEBSERVICE binding file that you generated with DFHLS2WS.
  2. Copy any other WEBSERVICE binding files used by the application to the same directory. In this example, the following files are copied:
    • inquireCatalog
    • placeOrder
    They are provided in directory /usr/lpp/cicsts/samples/webservices/wsbind/provider.
  3. Install the PIPELINE resource.

Results

CICS creates two URIMAP resources; the first URIMAP definition is required in a service provider when it contains information that maps the URI of an inbound web service request to the other resources (such as the PIPELINE resource) that service the request. The second URIMAP contains information that maps the URI of an inbound request for the WSDL document or documents associated with the web service.



dfhxa_t424.html | Timestamp icon Last updated: Monday, 5 June 2017