Creating an XML-aware service requester application
Your XML-aware web service requester application handles the data conversion between the XML and the programming language and populates the control containers in the pipeline.
Before you begin
About this task
Using the XML-ONLY parameter results in the generation of a WSBind file that instructs CICS® that the application will work directly with the contents of the DFHWS-BODY container. The generated WSBind file must be installed into a requester mode PIPELINE to create a requester mode WEBSERVICE resource. The application must generate XML for the body of the web service request and store it in the DFHWS-BODY container. It must then call the EXEC CICS INVOKE SERVICE command. The outbound message is sent to the web services provider. The body of the response message is also in the DFHWS-BODY container after the call completes.
The XML of the response messages is parsed during SOAP message handling. To prevent this parsing, you must not specify SOAP message handlers in your pipeline configuration file.
XML-aware requester applications can receive SOAP Fault messages back from the remote provider mode application. In this case, the requester application is responsible for interpreting the SOAP Fault and distinguishing it from a regular response message. If the INVOKE SERVICE command is used with an XML-ONLY WEBSERVICE, CICS does not set the response code which is normally used to indicate that a SOAP Fault was received.
If you are writing your own XML-aware service requester application without using the XML-ONLY option, complete the following steps: