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: ![]() ![]() |
7 | After Integration Server sends the JMS message, one of the following occurs: ![]() ![]() ![]() 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. |