Date Added: Sep 2008
Managing SOAP messages over the Java Message Service (JMS) API can provide greater scalability and reliability than HTTP/S. JMS transports and stores Web service requests 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. The Java code for the client and service don't change when SOAP over JMS is configured as the transport protocol. In fact, a Web service can support SOAP over JMS and SOAP over HTTP at the same time. The paper explains and also provides various tips for using SOAP over JMS transport, using Oracle Service Bus (formerly BEA AquaLogic Service Bus) as the message backbone. There isn't yet a standard defined for the SOAP over JMS transport and this article will help to integrate with other vendor implementations. The business service on the Oracle Service Bus is created from the WSDL. The service endpoint is copied from the WSDL. Using the SOAP over JMS transport protocol differs from the more common HTTP protocol is also explained here. The client needs to remember that the endpoint address includes the queue name and connection factory, The URI and mime type need to be set in the service bus' proxy and There are defaults for the read timeout, queue and connection factory.