Web services with SOAP over JMS in IBM WebSphere Process Server or IBM WebSphere Enterprise Service Bus, Part 2, Using the IBM WebSphere MQ JMS provider

From the developerWorks archives

Fenglian Xu and Simon Holdsworth

Date archived: January 5, 2017 | First published: July 17, 2008

The IBM® WebSphere® Process Server and IBM WebSphere Enterprise Service Bus products both include support for invoking and providing Web services. Part 1 of this article series covered the support of the SOAP over Java™ Message Service (JMS) protocol in WebSphere Process Server and WebSphere Enterprise Service Bus V6.02 and V6.1. This second installment of the series reveals how to change the referenced Java Naming and Directory Interface (JNDI) resources of SOAP over JMS exports and imports so that they can receive and send SOAP messages using the IBM WebSphere MQ JMS provider rather than the SIBus JMS provider. To follow along with this article, you should know how to create modules in IBM WebSphere Integration Developer and how to create WebSphere MQ resources.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=SOA and web services, WebSphere
ArticleID=321785
ArticleTitle=Web services with SOAP over JMS in IBM WebSphere Process Server or IBM WebSphere Enterprise Service Bus, Part 2: Using the IBM WebSphere MQ JMS provider
publish-date=07172008