Indeed not - WebSphere MQ predates many of the other MOM technologies around and the sender/receiver channel can talk to other WMQ implementations at different versions, but not to ActiveMQ.
On your comment about standards, bear in mind that JMS is an API spec and not a protocol / implementation thing. It defines the API calls and objects that the provider must expose and support, but it says absolutely nothing about how that API interacts with the messaging fabric. There are a range of things you could do, including some bridge code which can talk WMQ JMS over the network using the WMQ "client" connection option, or (thinking outside the box) using the HTTP bridge to WMQ if the other server has it installed, and using a REST call to poke the message into the queue on that side. I guess none of these are quite what you are looking for out of the box. An IBM solution (which I suspect your client may not be keen on) would be to use something like WebSphere Message Broker to bridge between ActiveMQ JMS, and WebSphere MQ either JMS or natively. There's a great independent WMQ community over at http://mqseries.net http://mqseries.net if you want to see if any other users have ideas. (disclaimer: I work for IBM but these are my own ideas and opinions!) -- Andy Piper WebSphere Messaging Community Lead, IBM Hursley -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-integration-with-WebSphere-MQ-tp3550031p3563168.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
