Creating a service provider application from a data structure

Using the CICS® Web services assistant, you can create a service provider application from a high level language data structure.

Before you can process your high level language data structures, you must ensure that: Which data structures you process depend upon whether you are using a wrapper program:
  1. Generate a Web service binding file. Use batch program DFHLS2WS to generate a Web service binding file. As well as the Web service binding file, the program generates Web service description. The service description can be used when building a service requester that interacts with your service. You will also need the Web service description if you intend to perform run time validation of SOAP messages for the service.
  2. Copy the Web service binding file to the pickup directory of the PIPELINE resource that you want to use for your Web service application.
  3. If you do not have a suitable PIPELINE resource definition in your system, create and install one. The PIPELINE resource specifies the XML file which defines the message handlers which will be used to process the inbound request and the reply. Typically, many applications can use the same PIPELINE definition, and if you already have a suitable PIPELINE in your system, you do not need to perform this step.
  4. Create and install a URIMAP which matches the URI used to invoke the Web service. The URIMAP specifies the names of the WEBSERVICE resource, and of the PIPELINE resource that provide further details of how the Web service request is processed.

    The URIMAP can be created automatically using the scan mechanism. In this case, CICS gets the information needed to build the URIMAP from the Web service binding file.

  5. Create and install a WEBSERVICE which specifies the location of the WSDL and of the WSBIND file. Although you can use RDO to create a WEBSERVICE, the recommended method is to scan for WSBIND files. This creates WEBSERVICE definitions which are consistent with the WSDL.
You should make the Web services description available to anyone who needs to develop a service requester that will access your service.