This two-part article series shows you how to use SOAP over Java Message Service
(JMS) in IBM WebSphere Process Server and IBM WebSphere Enterprise Service Bus. Learn
how to set up and use SOAP over JMS as configured by default by the IBM
WebSphere Integration Developer tool and how to enable the use of the IBM WebSphere
MQ JMS provider via configuration. In this article, Part 1 of the series, you create and
invoke a Web service using SOAP over JMS and an end-to-end application example, covering
the full process of creating, building, deploying, and testing the applications.
Scenarios covering both point-to-point and publish/subscribe messaging walk you
through the process. In the second article in this series, you’ll
reconfigure a Web service that uses the SOAP over JMS protocol to enable the use of
WebSphere MQ as the JMS provider and allow the transport of SOAP messages via
WebSphere MQ queues.
I’m a big fan on the JMS transport for the ability to submit work to a destination even when the listener is down. This absolves the client from the responsibility of maintaining logic for retries, unlike the http transport. I would still be weary of using SOAP/JMS for external service consumption as the interop story isn’t quite there yet. Its still an order of magnitude more difficult to consume a SOAP/JMS service than a SOAP/HTTP one for users still learning Web Services.