Integration Server 10.7 | Web Services Developer’s Guide | Using SOAP over JMS with Web Services | Using SOAP/JMS with Consumer Web Service Descriptors | Run-Time Behavior for a Web Service Connector that Uses a SOAP/JMS Binding
 
Run-Time Behavior for a Web Service Connector that Uses a SOAP/JMS Binding
The following table provides an overview of how Integration Server receives and processes SOAP/JMS messages for web services.
Step
Description
1
Integration Server invokes the web service connector.
Note:Integration Server authorizes the user at various points during web service connector execution and handler execution. For more information, see Authentication and Authorization for Consumer Web Service Descriptors.
2
Integration Server builds the SOAP request message using the input passed into the web service connector and information in the JMS binder.
3
Integration Server executes the request handler services.
For more information about request handler services, see About Request Handler Services.
4
Integration Server builds the JMS message, using the SOAP request message as the payload. Integration Server uses the name/value pairs passed into transportHeaders input parameter to create JMS message headers and properties. Integration Server also uses information in the JMS binder to construct the JMS message.
5
Integration Server sends the JMS message to the JMS provider.
6
If the JMS provider is not available at the time the Integration Server sends the JMS message, one of the following occurs:
*If the client side queue is enabled for the JMS binder, Integration Server writes the JMS message to the client side queue. Integration Server sends the message to the JMS provider when the JMS provider becomes available.
*If the client side queue is not enabled for the JMS binder, the web service connector throws an ISRuntimeException when the JMS provider is not available.
7
After Integration Server sends the JMS message, one of the following occurs:
*For a synchronous In-Out operation, Integration Server creates a message consumer for the replyTo destination. Integration Server uses the message consumer to retrieve the response JMS message sent to the reply destination, extracts the SOAP response message, and executes response handlers. Integration Server populates the web service connector output.
*For an asynchronous In-Out operation, Integration Server populates the web service connector output. Integration Server does not populate responseHeaders.
*For an In-Only and Robust In-Only operations, Integration Server populates the web service connector output.
The contents of the transportInfo output parameter vary based on the operation MEP and the success or failure of the web service connector. For more information, see About Transport and Fault Information Returned by a Web Service Connector.