It also refers to the way you route to a queue manager in the Kubernetes cluster.
The routing has something to do with the channel name. It is being done by using some DNS name that is linked to the particular MQ service in the cluster. Once you have a QM running in the Kubernetes cluster and have set up the routing from outside the cluster you will have a better understanding of what I am trying to describe.
Hope it helps
------------------------------
Francois Brandelik
------------------------------
Original Message:
Sent: Thu January 30, 2025 03:51 AM
From: Arthur Barr
Subject: Container Disaster Recovery QM ID
I think it might have originally said "queue manager network identity", meaning "how your client refers to the queue manager". e.g. if your CCDT contains a dotted IP address, then that IP address will need to route to the recovered location; it's a more common approach for your CCDT to contain a DNS name, which then gives you a point of indirection - "qm1.mydomain.com" can be changed in DNS to point to the newly recovered queue manager.
------------------------------
Arthur Barr
STSM, IBM MQ container technology
Original Message:
Sent: Wed January 29, 2025 09:43 AM
From: John Hawkins
Subject: Container Disaster Recovery QM ID
Hi Folks,
I'm, currently researching MQ in containers and I'm looking at DR. DR seems to be hinted at but not solved easily - I don't know if there's a better resource than this page anyone?
Disaster recovery for IBM MQ in containers
My question is around a line on this page which says:
- The queue manager network ID that is visible to IBM MQ client applications and other queue managers. This ID could be a DNS entry, for example.
I'm not sure I've heard of the term "QM network ID". Is this referring to the "standard" unique QM ID that is used in e.g. clustering? If so, then is this referring to how to make sure that each QM in each e.g region uses the same ID if they fail to the new site? Where does this data reside if I need to replicate it? I'm not sure how a DNS entry helps - any clues anyone?
thanks, as always, for your help folks.
John
------------------------------
John Hawkins
Integration Consultant
------------------------------