You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Bethapudi, Rohini Kumar (TR Technology)" <Ro...@thomsonreuters.com.INVALID> on 2025/06/05 12:13:15 UTC
RE: [EXT] Re: ActiveMQ Classic 5.18.6 - Clustering
Hi Matt,
Thank you for the details.
I used Camel-Integration as I realized true clustering is not possible between IBM MQ and ActiveMQ.
> 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
The full repository QMGR (MFQMGR) is on Mainframe IBM MQ (remaining as-is). There are two QMGRs on Linux which are being migrated to ActiveMQ (A & B).
I configured the connectivity between MFQMGR and A using camel integration. Now I need to configure B to become part of this group. This should look like my existing configuration in terms of functionality. What would be the approach here?
Here is how my existing configuration (names changed)
dis clusqmgr(*)
4 : dis clusqmgr(*)
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(MFQMGR) CHANNEL(TO.MFQMGR)
CLUSTER(MyCluster)
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(A) CHANNEL(TO.A)
CLUSTER(MyCluster)
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(B) CHANNEL(TO.B)
CLUSTER(MyCluster)
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: Matt Pavlovich <ma...@gmail.com>
Sent: 03 June 2025 23:13
To: users@activemq.apache.org
Subject: [EXT] Re: ActiveMQ Classic 5.18.6 - Clustering
External Email: Use caution with links and attachments.
Hi Rohini-
ActiveMQ is a great option to migrate from IBM MQ. For many use cases, there is little to no coding change required to applications (other than the connection factory swap out).
ActiveMQ supports store-and-forward clustering (IBM MQ-style), and also on-demand consumer driven (better for running cloud/Kubernetes where you may want to scale your cluster). These two approaches can also be combined to support really cool topologies =)
Migration is usually very straight forward!
Thanks,
Matt Pavlovich
> On Jun 3, 2025, at 4:17 AM, Bethapudi, Rohini Kumar (TR Technology) <Ro...@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!fYwQMHZkg65tipUH6B0e8pXzNCTSlpZlWBVI9z8
> xwSFqoQY-uhKZqVKCZoeB0LMvmplfLDeyltUu1-mDMjcUm7nDjo2DUHo$ >
>
> 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-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org For further information, visit: https://urldefense.com/v3/__https://activemq.apache.org/contact__;!!GFN0sa3rsbfR8OLyAw!fYwQMHZkg65tipUH6B0e8pXzNCTSlpZlWBVI9z8xwSFqoQY-uhKZqVKCZoeB0LMvmplfLDeyltUu1-mDMjcUm7nDi3bu4h4$
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: [EXT] ActiveMQ Classic 5.18.6 - Clustering
Posted by Matt Pavlovich <ma...@apache.org>.
Hi Rohini-
That is correct, Apache ActiveMQ and Camel do not have an option for integrating directly with IBM MQ clusters.
I suggest you check out the third-party support providers. I know there are options available to do exactly what you are looking for.
Thanks,
Matt Pavlovich
> On Jun 5, 2025, at 7:13 AM, Bethapudi, Rohini Kumar (TR Technology) <Ro...@thomsonreuters.com.INVALID> wrote:
>
> Hi Matt,
>
> Thank you for the details.
>
> I used Camel-Integration as I realized true clustering is not possible between IBM MQ and ActiveMQ.
>
>> 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
>
> The full repository QMGR (MFQMGR) is on Mainframe IBM MQ (remaining as-is). There are two QMGRs on Linux which are being migrated to ActiveMQ (A & B).
> I configured the connectivity between MFQMGR and A using camel integration. Now I need to configure B to become part of this group. This should look like my existing configuration in terms of functionality. What would be the approach here?
>
>
> Here is how my existing configuration (names changed)
>
> dis clusqmgr(*)
> 4 : dis clusqmgr(*)
> AMQ8441I: Display Cluster Queue Manager details.
> CLUSQMGR(MFQMGR) CHANNEL(TO.MFQMGR)
> CLUSTER(MyCluster)
> AMQ8441I: Display Cluster Queue Manager details.
> CLUSQMGR(A) CHANNEL(TO.A)
> CLUSTER(MyCluster)
> AMQ8441I: Display Cluster Queue Manager details.
> CLUSQMGR(B) CHANNEL(TO.B)
> CLUSTER(MyCluster)
>
> 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: Matt Pavlovich <ma...@gmail.com>
> Sent: 03 June 2025 23:13
> To: users@activemq.apache.org
> Subject: [EXT] Re: ActiveMQ Classic 5.18.6 - Clustering
>
> External Email: Use caution with links and attachments.
>
> Hi Rohini-
>
> ActiveMQ is a great option to migrate from IBM MQ. For many use cases, there is little to no coding change required to applications (other than the connection factory swap out).
>
> ActiveMQ supports store-and-forward clustering (IBM MQ-style), and also on-demand consumer driven (better for running cloud/Kubernetes where you may want to scale your cluster). These two approaches can also be combined to support really cool topologies =)
>
> Migration is usually very straight forward!
>
> Thanks,
> Matt Pavlovich
>
>> On Jun 3, 2025, at 4:17 AM, Bethapudi, Rohini Kumar (TR Technology) <Ro...@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!fYwQMHZkg65tipUH6B0e8pXzNCTSlpZlWBVI9z8
>> xwSFqoQY-uhKZqVKCZoeB0LMvmplfLDeyltUu1-mDMjcUm7nDjo2DUHo$ >
>>
>> 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-unsubscribe@activemq.apache.org
> For additional commands, e-mail: users-help@activemq.apache.org For further information, visit: https://urldefense.com/v3/__https://activemq.apache.org/contact__;!!GFN0sa3rsbfR8OLyAw!fYwQMHZkg65tipUH6B0e8pXzNCTSlpZlWBVI9z8xwSFqoQY-uhKZqVKCZoeB0LMvmplfLDeyltUu1-mDMjcUm7nDi3bu4h4$
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
> For additional commands, e-mail: users-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact