Step | Description |
1 | The SOAP-JMS trigger receives JMS messages from the destination it subscribes to on the JMS provider. |
2 | Integration Server extracts the SOAP message from the JMS message. Integration Server also retrieves JMS message properties including targetService, soapAction, contentType, and JMSMessageID. These properties specify the web service descriptor and operation that the web service client wants to invoke. Integration Server also retrieves JMS message properties including targetService and soapAction. These properties specify the web service descriptor and operation that the web service client wants to invoke. For more information, see
Determining the Operation for a SOAP/JMS
Request. |
3 | Integration Server passes the SOAP message and JMS message properties to the internal web services stack for processing. |
4 | The web services stack processes the SOAP message by executing handler services (if specified) and invoking the web service operation specified in the SOAP request message. Note:Integration Server also performs authentication and authorization for the web service descriptor, handler services, and the operation. For more information, see
Authentication and Authorization for Provider
Web Service Descriptors. |
5 | For an In-Out operation (or for a Robust-In-Only operation that ends with a SOAP fault), Integration Server constructs the response SOAP message based on the operation output, uses it as the payload in a JMS message, and sends the response to the reply destination specified in the request message. Integration Server uses the JMS connection alias specified in the SOAP-JMS trigger that received the request message to send the response message. |