Hi Rohini- No, the camel-wmq component is essentially just the proprietary IBM MQ ‘MQI’ protocol vs using JMS. The use case for it is very narrow over using camel-jms for IBM MQ.
Thanks, Matt Pavlovich > On Jun 18, 2025, at 7:26 AM, Bethapudi, Rohini Kumar (TR Technology) > <rohinikumar.bethap...@thomsonreuters.com.INVALID> wrote: > > Hello JB, > > This looks interesting. We used v5.18.6 as it supports Java 11 as we some > legacy applications. > > I was able to establish the connectivity using camel route in v5.18.6 and it > works.However, this is not a true clustering. Meaning, > CONTECH.CODES.THEO.MQD.IBM is local to IBM MQ and > CONTECH.CODES.THEO.MQD.ACTIVE is local to ActiveMQ. > > Can a true clustering be achieved in camel-wmq in v6.1.x so that I don’t need > to create local queues replacing cluster queues? > > Here is my existing route: > > <camel:camelContext id="camel-bridge"> > <!-- IBM MQ to ActiveMQ Routes --> > <camel:route id="ibmmq-to-activemq-queue1"> > <camel:from > uri="jms:queue:CONTECH.CODES.THEO.MQD.IBM?connectionFactory=pooledIBMMQConnectionFactory"/> > <camel:to uri="activemq:queue:CONTECH.CODES.THEO.MQD.ACTIVE"/> > </camel:route> > > <!-- ActiveMQ to IBM MQ Routes --> > <camel:route id="activemq-to-ibmmq-queue1"> > <camel:from > uri="activemq:queue:CONTECH.CODES.THEO.MQD.ACTIVE.REPLY"/> > <camel:to > uri="jms:queue:CONTECH.CODES.THEO.MQD.IBM.REPLY?connectionFactory=pooledIBMMQConnectionFactory"/> > </camel:route> > > Thanks & Regards, > ………………………………………………………….. > Rohini Kumar > Associate Tech Lead - Middleware > Thomson Reuters > Mobile: +91 97392 11168 > Work Hours: 13:00 to 22:00 IST [Mon – Fri] > Escalation > > -----Original Message----- > From: Jean-Baptiste Onofré <j...@nanthrax.net> > Sent: 12 June 2025 21:04 > To: rohinikumar.bethap...@thomsonreuters.com.invalid > Cc: users@activemq.apache.org > Subject: [EXT] Re: ActiveMQ Classic 5.18.6 - Clustering > > External Email: Use caution with links and attachments. > > Hi Rohini > > Just curious: any particular reason for ActiveMQ 5.18.x ? > I would suggest to evaluate if ActiveMQ 6.1.x is not option ? > > Regarding Camel, I wrote camel-wmq directly using IBM MQ API (not JMS). Due > to license constraints, it's not part of Camel, it's in > camel-extra: > > https://urldefense.com/v3/__https://github.com/camel-extra/camel-extra/tree/master/components/camel-wmq__;!!GFN0sa3rsbfR8OLyAw!f49sYDgtfq4WfXS6WwPiEoxc4IdKDiHO4ittuyfJ6YkgM2gsspzvT57NEJ6X6_S84Grj6fwCH2oWYjv-YJKTRauW7AQ$ > > > I have several users that use camel-wmq to/from IBM MQ and camel-jms to/from > ActiveMQ. So you can create a route from IBM MQ and ActiveMQ easily. > > Regards > JB > > On Tue, Jun 3, 2025 at 11:17 AM Bethapudi, Rohini Kumar (TR > Technology) <rohinikumar.bethap...@thomsonreuters.com.invalid> wrote: >> >> Hello, >> >> I am working on migrating IBM MQ to ActiveMQ. Currently, IBM MQ (Linux) and >> IBM MQ (Mainframe) are part of a MQ cluster. I am looking for some guidance >> on implementing clustering in ActiveMQ classic 5.18.6. >> >> Here is my Scenario >> >> - IBM MQ servers on mainframe (remaining as-is) >> - IBM MQ servers on Linux (being migrated to ActiveMQ 5.18.6) >> - Currently, these systems form an IBM MQ cluster with cluster queues >> >> Please advise. >> >> Thanks & Regards, >> .................................................................... >> Rohini Kumar >> Associate Tech Lead - Middleware >> Thomson Reuters >> Mobile: +91 97392 11168 >> Work Hours: 13:00 to 22:00 IST [Mon - Fri] >> Escalation<https://urldefense.com/v3/__https://trten.sharepoint.com/si >> tes/intr-ihn-service-portfolio/SitePages/IHN-Contact-*26-Escalation(1) >> .aspx__;JQ!!GFN0sa3rsbfR8OLyAw!f49sYDgtfq4WfXS6WwPiEoxc4IdKDiHO4ittuyf >> J6YkgM2gsspzvT57NEJ6X6_S84Grj6fwCH2oWYjv-YJKTwJZS-lk$ > >> >> This e-mail is for the sole use of the intended recipient and contains >> information that may be privileged and/or confidential. If you are not >> an intended recipient, please notify the sender by return e-mail and >> delete this e-mail and any attachments. Certain required legal entity >> disclosures can be accessed on our website: >> https://www.thomsonreuters.com/en/resources/disclosures.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org For further > information, visit: > https://urldefense.com/v3/__https://activemq.apache.org/contact__;!!GFN0sa3rsbfR8OLyAw!f49sYDgtfq4WfXS6WwPiEoxc4IdKDiHO4ittuyfJ6YkgM2gsspzvT57NEJ6X6_S84Grj6fwCH2oWYjv-YJKT2fONV-Y$ > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
