| Author |
Message
|
| issac |
 Posted: Thu Apr 23, 2015 5:28 am Post subject: Connecting to 2 QMGRs of the same name. problem? |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello, dear supporters
One of my customers is going to deploy 2 mq clusters respectively in Tokyo and Shanghai. for some reason they want to use identical names for the gate way, MQMIPS.
Another qmgr located in Shanghai named MQESBGW1 needs to have SDR-RCVR chls to Tokyo MQMIPS, and another qmgr MQESBGW2, which is in the same cluster as MQESBGW1 needs to connect to Shanghai MQMIPS.
Is there going to be a problem for the topology?
MQESBGW1 ------(SDR)-------> Tokyo MQMIPS
MQESBGW2 ------(SDR)-------> Shanghai MQMIPS
------------
MQESBGW1 & MQESBGW2 are in the same cluster.
Thanks in advance.
_________________
Bazinga! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Apr 23, 2015 5:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes.
This will cause huge problems. |
|
| Back to top |
|
|
| issac |
| Posted: Thu Apr 23, 2015 5:32 am Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
| mqjeff wrote: |
Yes.
This will cause huge problems. |
Umm... would you please explain more please?
_________________
Bazinga! |
|
| Back to top |
|
|
| issac |
| Posted: Thu Apr 23, 2015 5:34 am Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
MQMIPS and MQESBGW1 are not in the same cluster.
In the topology,only MQESBGW1 and MQESBGW2 are in the same cluster. 2 MQMIPS are not connected as a same cluster... but they had the same cluster name MIPSCLUS.
_________________
Bazinga! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 23, 2015 5:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Oh. The name of the cluster, not the queue manager. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 6:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Never had 2 clusters be distinct yet have the same cluster name.
You will run into routing problems unless at least one of the clusters uses consistently a cluster alias that is distinct from the local cluster name and allows routing.
Real problems will start the moment they will want the clusters to overlap and you will have to change everything in at least one of the clusters...
Might be easier if they start with different cluster names than having to change mid course. If the cluster names are the same the only easy option is not overlapping clusters but merging the 2 clusters... and that might bring huge problems as to authorizations and distribution of messages when cluster queues with different processes have the same name across both clusters....
My advice: keep them separate. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| issac |
| Posted: Thu Apr 23, 2015 6:33 am Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
| fjb_saper wrote: |
Never had 2 clusters be distinct yet have the same cluster name.
You will run into routing problems unless at least one of the clusters uses consistently a cluster alias that is distinct from the local cluster name and allows routing.
Real problems will start the moment they will want the clusters to overlap and you will have to change everything in at least one of the clusters...
Might be easier if they start with different cluster names than having to change mid course. If the cluster names are the same the only easy option is not overlapping clusters but merging the 2 clusters... and that might bring huge problems as to authorizations and distribution of messages when cluster queues with different processes have the same name across both clusters....
My advice: keep them separate. |
Thanks very much! 
_________________
Bazinga! |
|
| Back to top |
|
|
|
|
