Integration Server 10.3 | Web Services Developer’s Guide | Working with Response Services | About Response Services
 
About Response Services
At the time of creating a consumer web service descriptor, Integration Server creates a responseServices folder along with the connectors and docTypes folders.
The responseServices folder contains a response service for each In-Out and Robust-In-Only MEP operation in the WSDL document from which the consumer web service descriptor is created and a genericFault_Response service. Integration Server creates the response services and genericFault_Response service only if the consumer web service descriptor:
*Is created on Integration Server version 9.0 or later.
*Has the Pre-8.2 compatibility mode property set to false.
The responseServices folder contains:
*Response services. Integration Server creates a response service for each In-Out and Robust-In-Only MEP operation contained in the WSDL document. Response services are flow services to which you can add custom logic to process asynchronous SOAP responses. Integration Server invokes these services for processing SOAP responses received for the associated consumer web service descriptor. That is, Integration Server invokes a response service when Integration Server receives a SOAP response with the endpoint URL pointing to a consumer web service descriptor and if this SOAP response contains a WS-Addressing action through which the response service can be resolved.
The name of a response service is the same as the corresponding web service connector suffixed with the term “_Response”. The input signature of each response service is the same as the output signature of the corresponding web service connector.
*A genericFault_Response service. The default response service that will be invoked when Integration Server cannot determine the specific response service for an asynchronous SOAP response or if there are errors while processing the response (for example, errors related to authorization, handler processing, or missing headers). Each responseServices folder contains one genericFault_Response service.
Integration Server will also invoke the genericFault_Response service if the addressing action on an asynchronous response is one of the following URLs:
*W3C Member Submission WS-Addressing standard version: http://schemas.xmlsoap.org/ws/2004/08/addressing/fault
*W3C Final WS-Addressing standard version: http://www.w3.org/2005/08/addressing/fault
Keep the following information in mind when working with response services:
*Response services are created only for In-Out and Robust In-Only MEP operations. For example, in case of a consumer web service descriptor with one In-Only MEP and one In-Out MEP operation, Integration Server creates one response service that corresponds to the In-Out MEP operation.
*You can use the response services to process asynchronous SOAP responses only if you have attached WS-Addressing policies to the web service descriptor. To know more about how to handle asynchronous SOAP responses, see Processing Responses Asynchronously.
*You must refresh the web service descriptors or web service connectors to update the signature of the response services based on the changes that you make to the consumer web service descriptor or the WSDL from which this consumer web service descriptor is created.
For example, if you add a response or fault header to a consumer web service descriptor, you must refresh the connectors to update the response services with the response or fault headers.