| Author |
Message
|
| Kusch |
 Posted: Fri Nov 07, 2008 4:15 pm Post subject: Broker can't see other Brokers in the collective |
 |
|
Newbie
Joined: 27 Aug 2008
Posts: 5
|
Hi,
I am totally new to this field. I got a cookbook but somehow it doesn't work so good. It is a sub/pub environment. The collective exists for a while and I am suppose to add a broker.
I created the broker on the node, then in the workbench I created the broker, added an execution group with message flow. Then added this broker to the collective I deployed after every single step.
Then followin my instruction: I am suppose to change the properties of the broker with
mqsichngeproperties BROKER -o Dynam... -n interbrokerHost -v servername
This is what I did.
But when I run: mqsibrowse BROKER -t bnbrconnections, the output inidicates that the broker can't see the other ones. The output shows only the connection class mq, but not the connection class ip.
What did I miss ? Any suggestions highly appreciated. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Nov 07, 2008 10:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To add a broker to a collective, the easiest way is to have the collective be at the same time an MQ Cluster. In order for the collective concept to work each broker queue manager in the collective needs to have a default route to every other broker queue manager in the collective. This is why I suggest that you have collective = MQ Cluster on top of the broker setup.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kusch |
| Posted: Sat Nov 08, 2008 5:14 pm Post subject: |
|
|
Newbie
Joined: 27 Aug 2008
Posts: 5
|
Hi,
Thanks for your reply
I am not permitted to change from distributed messaging to MQ cluster at this point. Refering to the default route: is this set up by creating the channels between the brokers ?
All these channels run without a problem. Or is there something else I have to do ?
I don't know how to troubleshoot this at all. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Nov 08, 2008 6:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Kusch wrote: |
Hi,
Thanks for your reply
I am not permitted to change from distributed messaging to MQ cluster at this point. Refering to the default route: is this set up by creating the channels between the brokers ?
All these channels run without a problem. Or is there something else I have to do ?
I don't know how to troubleshoot this at all. |
The channels are only 1 part of a default route.
For the default route to qmgr X to exist you need to have a "default" way to route to qmgr X.
So obviously you need:
- a channel to qmgr X, or a channel to a qmgr that has a default route to qmgr X
- For this channel to use an XMITQ that has the name of qmgr X, or create a qmgr Alias for qmgr X (see intercommunications manual link to Info Center at top of page)
So you will either have direct communications to the qmgr, or you will have to do a multihop. If you do use a multihop I suggest you use the configmgr's qmgr as the additional hop. The configmgr's qmgr should have a default route to each of the broker's qmgr.
So now you have setup a sending route to each of the qmgrs in the collective. As you are not allowed to use an MQCluster you will also have to create a default route from EACH of qmgrs in the collective to EVERY OTHER qmgr in the collective.
If you ask me, much easier on the admin to have the collective equal an MQ cluster.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kusch |
| Posted: Mon Nov 10, 2008 1:39 pm Post subject: |
|
|
Newbie
Joined: 27 Aug 2008
Posts: 5
|
I agree, a lot of work. Anyway, I did all that and I think the broker are seeing each other via Mq but not the other way. What I mean by that is when I run mqsibrowse BROKER -t bnbrconnection on one of the brokers in the collective, I get following for the newly added broker:
Neighbor ID Connection ID ConnectionClass ConnectionInfo
8b66188... ip1..........................ip.................:1507
8b66188... 1............................mq................2:QMGR1:SYSTEM.BR..
In the connectionInfo field of all the other broker it displays the hostname and 1507.
Telnet to port 1507 was successful to the brokers in the collective, it only failed to the newly added broker. Is there any communication going on on that port in regard to brokers ? Is there suppose to be a listener running ?
Or am I on the wrong track ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 10, 2008 2:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Check out the toolkit in the add broker or broker properties. 1507 is a special broker port for the interbroker port number... so if you're going across firewalls you might have to open that port too.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kusch |
| Posted: Mon Nov 10, 2008 3:27 pm Post subject: |
|
|
Newbie
Joined: 27 Aug 2008
Posts: 5
|
Thanks a lot for your support fjb_saper !
It was not the port. Firewall wasn't blocking anything.
I thought before I call it a day today, I will simply restart the brokers again and make another deploy. After that they can see each other now. Can you believe it ?
I am just relieved that it works now. I have to add another broker in several weeks. I hope that one will go smoother 
Thanks again for you help !! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 10, 2008 8:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To make it go way smoother, make sure the MQ communication is in place before you try to add it to the collective.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
