Runtime processing for web services
To send a request to a web service provider or to receive a request from a web service requester, your application (or wrapper program) must interact correctly with the web services support in CICS®. You can also control the processing that takes place in the pipeline to determine how the inbound and outbound requests are handled.
- How CICS invokes a service provider program deployed with the web services assistant
When a service provider application that has been deployed using the CICS web services assistant is invoked, CICS links to it with a COMMAREA or a channel. - Invoking a web service from an application deployed with the web services assistant
A service requester application that is deployed with the web services assistant uses the EXEC CICS INVOKE SERVICE command to invoke a web service. The request and response are mapped to a data structure in container DFHWS-DATA. This method of invoking a service is not supported for JSON. - Local optimization for web services
You can use the provider application name in the web service binding file associated with the WEBSERVICE resource to enable local optimization of the web service request. - Runtime limitations for code generated by the web services assistant
At runtime, CICS is capable of transforming almost any valid SOAP message that conforms to the web service description (WSDL) into the equivalent data structures. However, there are some limitations that you should be aware of when developing a service requester or service provider application using the web services assistant batch jobs. - Customizing pipeline processing
In addition to providing your own message handlers, you can also use a set of global user exit points (GLUEs) to customize the processing that occurs for inbound and outbound web services in the pipeline. - Options for controlling requester pipeline processing
In service requester pipelines, message handlers can determine where the web service request is sent by changing the URI. CICS provides support for different URI formats so that you have much more flexibility in the way that the pipeline processes web service requests. - Controlling requester pipeline processing using a URI
In service requester pipelines, a message handler can determine where to send the web service request by changing the URI. By changing the URI format, you can choose to perform certain optimizations, such as starting another requester pipeline or starting a service provider pipeline without sending the request over the network.
dfhws_app01.html |
Last updated: Sunday, 4 June 2017