ActiveMQ can talk to IBM's MQ via the "jmsBridgeConnectors"
http://activemq.apache.org/jms-to-jms-bridge.html . There was a bug after AMQ
5.2.0 until 5.5 that prevented it, but I've tested it in 5.5 successfully. I
defined a remote ConnectionFactory like so:
<bean id="remoteBlueFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType" value="1"/>
<property name="hostName" value="ibmbrokerhost1"/>
<property name="port" value="1414"/>
<property name="queueManager" value="QMGRNAME"/>
<property name="channel" value="UNSECURE.BKR.CHANNEL"/>
</bean>
We saw an issue where ActiveMQ needed to be restarted to send messages "stuck"
while the IBM MQ was down, but we haven't followed up on whether that was a bug
or a configuration issue. But to the original poster's original question,
"Yes, this is indeed possible, and relatively easy to do." :)
As an aside, we have looked at using WebSphere Message Broker to bridge between
ActiveMQ and MQ, but we are leaning towards using our existing webMethods
infrastructure instead because the JMS support is easier to work with in a
number of ways. But since a basic remote connection works with the JMS bridge
connector, I don't see why Camel wouldn't work too.
-----Original Message-----
From: andypiper [mailto:andypipe...@gmail.com]
Sent: Tuesday, May 31, 2011 9:55 AM
To: users@activemq.apache.org
Subject: Re: ActiveMQ integration with WebSphere MQ
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.
-----------------------------------------
***Note:The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify the Sender
immediately by replying to the message and deleting it from your
computer. Thank you. Premier Inc.
