Skip to main content

Configuring SOAP over JMS

The JMS Transport is a good alternative messaging mechanism to SOAP over HTTP, as it offers a more reliable and scalable messaging support.

The greater efficiency derives from the fact that JMS transports and stores Web service request and response messages in a queue until they can be processed by the server, and the client frees up threads and other resources on both systems. A Web service configured to use the JMS transport communicates with its client through a JMS queue. The client sends a SOAP message to the queue and waits for a response message on a temporary queue created just for the JMS session. The Web service processes the message and sends the response back to the temporary queue. The Java code for the client and service does not change when SOAP over JMS is configured as the transport protocol. The difference between using these protocols is apparent in how the Web service endpoints are defined.

Talend ESB supports the SOAP over JMS transport for ESB Consumers and Providers developed in JAVA (JAX-WS). The configuration in Talend ESB is primarily based on a URI-style SOAP over JMS address. For more information on the supported JMS Broker for SOAP over JMS, see Compatible Apache software and JMS Brokers for Talend ESB.

In this section

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here