Integration Server 10.3 | Web Services Developer’s Guide | Using SOAP over JMS with Web Services | Using SOAP/JMS with Consumer Web Service Descriptors
 
Using SOAP/JMS with Consumer Web Service Descriptors
 
Run-Time Behavior for a Web Service Connector that Uses a SOAP/JMS Binding
Additional Guidelines for Using SOAP/JMS with Consumer Web Service Descriptors
To use Integration Server as a web service client that sends SOAP over JMS messages, you need a service that creates a SOAP message, places it in a JMS message, and then sends the JMS message to the JMS provider. Integration Server creates a web service connector that does all of these tasks when you create a consumer web service descriptor from a WSDL document with SOAP/JMS bindings. In addition to creating the consumer web service descriptor, you can specify how Integration Server will connect to the JMS provider and supplement or overwrite JMS URI information provided in the WSDL document.
The following table identifies the basic steps that you need to complete to use Integration Server as a web service client that sends SOAP/JMS messages.
Step
Description
1
Create a consumer web service descriptor.
When you create a consumer web service descriptor from a WSDL document that contains a SOAP/JMS binding, Integration Server creates a JMS binder for the web service descriptor. The JMS binder encapsulates the information needed to send a message to the JMS provider, including the destination and JMS message header values.
For more information about creating a consumer web service descriptor, see webMethods Service Development Help.
Note:
Binders cannot be added to consumer web service descriptors.
2
Optionally, create a consumer web service endpoint alias for JMS.
If you want to supplement or replace the binding information contained in the WSDL document, create a consumer web service endpoint alias.
Note:
The SOAP over Java Message Service standard requires only that the WSDL document contain the lookup variant and the destination. Consequently, it is possible that some of the details needed to connect to the JMS provider are absent from the JMS binder.
For more information about creating a consumer web service endpoint alias for use with JMS, see Creating an Endpoint Alias for a Consumer Web Service Descriptor for Use with JMS.
3
Optionally, assign the consumer web service endpoint alias to the JMS binder.
If you created a web service endpoint alias that you want to use to supplement or replace the JMS URI information from the WSDL document, assign the alias to the JMS binder.
For more information about assigning web service endpoint aliases to binders, see webMethods Service Development Help.
4
Configure use of the client side queue.
The client side queue is a message store that contains JMS messages sent when the JMS provider was not available. Messages remain in the client side queue until the JMS provider becomes available. For each JMS binder, you can decide whether or not to use the client side queue.
For more information about configuring the client side queue for a JMS binder, see webMethods Service Development Help
5
Build a service that invokes the web service connector.
When you create a service that invokes a web service connector, you supply values to use as input to the web service connector. These values determine the content of the SOAP message request.
When using a SOAP/JMS binding, you can pass in name/value pairs to the transportHeaders parameter. Integration Server creates JMS message headers and properties from the name/value pairs. You can also use name/value pairs to overwrite binding details specified in the source WSDL document or in the consumer web service endpoint alias assigned to the JMS binder.
For more information about the web service connector signature, see Signature for a Web Service Connector.
For more information about supplying transport headers and name/value pairs, see Setting Transport Headers for JMS.
For information about supplying security information into a web service connector, see Passing Message-Level Security Information to a Web Service Connector.