Configuring a service provider for Web service transactions

If a service provider application is to participate in Web service transactions, the pipeline configuration file must specify a <headerprogram> and a <service_parameter_list>.

So that your service provider application can participate in Web service transactions, it must use SOAP protocols to communicate with the service requester, and you must configure your pipeline to use one of the CICS-provided SOAP message handlers. Even if you have configured your service provider application correctly, it will participate in Web service transactions with the service requester only if the requester application has been set up to participate.
In addition to the pipeline configuration information that is specific to your application, the configuration file must contain information that CICS® uses to ensure that your application participates in Web service transactions.

CICS provides an example of a pipeline configuration file containing this information in file Start of change/usr/lpp/cicsts/cicsts31/samples/pipelines/wsatprovider.xmlEnd of change.

To configure a service provider for Web service transactions:

  1. In the definition of your terminal handler, code a <headerprogram> element in the <cics_soap_1.1_handler> or <cics_soap_1.2_handler> element. Code the <program_name>, <namespace>, <localname>, and <mandatory> elements exactly as shown in this example:
    <terminal_handler>
      <cics_soap_1.1_handler>
        <headerprogram>
          <program_name>DFHWSATH</program_name>
          <namespace>http://schemas.xmlsoap.org/ws/2004/10/wscoor</namespace>
          <localname>CoordinationContext</localname>
          <mandatory>false</mandatory>
        </headerprogram>
      </cics_soap_1.1_handler>
    </terminal_handler>
    Include other <headerprogram> elements if your application needs them.
  2. Code a <registration_service_endpoint> element in a <service_parameter_list>. Code the <registration_service_endpoint> as follows:Start of change
    <registration_service_endpoint>
    http://address:port/cicswsat/RegistrationService
    </registration_service_endpoint>
    End of change where
    • address is the IP address of the CICS region where the registration service provider pipeline is installed.
    • port is the port number used by the registration service provider pipeline.
    Code everything else exactly as shown; the string cicswsat/RegistrationService matches the PATH attribute of URIMAP DFHRSURI:
    <registration_service_endpoint>
    provider.example.com:7160/cicswsat/RegistrationService
    </registration_service_endpoint>