Yes. I've seen quite a few people use SOAP with IBM WebSphereMQ (the new name for MQ Series). But not necessarily the way you're describing it in your example.
SOAP, by definition, is transport-independent -- which means that you can transfer SOAP messages using any type of transport protocol, including IBM WebSphereMQ. Quite a few Web Services Platforms (WSPs) support SOAP over JMS. But in this scenario, the application works only with SOAP. It does not work directly with MQ. The SOAP engine encapsulates all the JMS functionality. The application uses JAX-RPC or SAAJ or some other SOAP API to invoke a Web service. The SOAP runtime system converts the request into a SOAP message, packages the message into JMS, and then puts the message onto the appropriate JMS queue/topic. At the other end of the wire, the receiving SOAP engine pulls the message off the JMS queue, unpacks the SOAP message, processes it, and invokes the appropriate application to handle the request.
The distinction here from your example is that both trading partner 1 and trading partner 2 must be using both SOAP and MQ for the interaction to work -- athough you can use a gateway product to bridge between HTTP and MQ environments.
Dig Deeper on Topics Archive
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.