If a service provider application is to participate in
web service transactions, the pipeline configuration file must specify
a <headerprogram> element and a <service_parameter_list> element.
Before you begin
If you want your service provider application to 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.
About this task
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 /usr/lpp/cicsts/cicsts54/samples/pipelines/wsatprovider.xml directory
(where /usr/lpp/cicsts/cicsts54 is
the default install directory for CICS files on z/OS UNIX).
Procedure
- In the definition of your terminal handler, code a <headerprogram> element
in the <cics_soap_1.1_handler>, <cics_soap_1.2_handler>, <cics_soap_1.1_handler_java>, or <cics_soap_1.2_handler_java> 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.
- Code a <registration_service_endpoint> element
in a <service_parameter_list>. Code
the <registration_service_endpoint> as follows:
<registration_service_endpoint>
http://address:port/cicswsat/RegistrationService
</registration_service_endpoint>
- address is the IP address
of the CICS region where the registration service provider
pipeline is located.
- 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>
http://provider.example.com:7160/cicswsat/RegistrationService
</registration_service_endpoint>