Hi om prakash,
Thanks for the update. In the meantime, we've also reached out to IBM Support, and they recommended using a single user to avoid authentication issues. We're currently evaluating the feasibility of that approach. Also, thanks for the heads-up regarding load balancers-we're considering those options as well
------------------------------
Prasad beathpudi
------------------------------
Original Message:
Sent: Tue June 10, 2025 10:47 AM
From: om prakash
Subject: IBM MQ SaaS – API Access Issues During Regional Failover in Active/Passive Configuration
U will need a loadbalancer like F5 - exposing a vip mapped to a fqdn which will handle the backend flip between the HA qmgrs.
The pool will be the qmgr VIP with a health check for the listener; so it know which host is the qmgr running and route.
------------------------------
om prakash
Architect
NorthwesternMutual
Milwaukee
Original Message:
Sent: Mon June 09, 2025 04:45 AM
From: Prasad beathpudi
Subject: IBM MQ SaaS – API Access Issues During Regional Failover in Active/Passive Configuration
Dear Team,
As part of our high availability architecture, we have two queue managers deployed-one in each region. This setup is integrated with our middleware (Boomi) to ensure message reliability and failover readiness.
However, we are facing a critical challenge during failover scenarios:
-
Each queue manager instance generates a unique API endpoint URL.
-
When we attempt to switch from the primary region to the secondary (e.g., during maintenance or outage), our applications and integrations are unable to access the secondary MQ instance due to the change in API endpoint.
-
The middleware (Boomi) currently relies on a fixed endpoint and cannot dynamically resolve or switch to the new API without manual intervention.