| Author |
Message
|
| mk |
 Posted: Sun Jul 05, 2009 9:37 am Post subject: Communication between ConfigMGR and Broker |
 |
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Hi there,
since my DB2 problem is solved I was able to finally create the broker and place it under HA control with HP Serviceguard. I'm trying to connect to this Broker with Message Broker Toolkit but somehow I only can connect to the Configuration Manager. Everytime when I create a "Broker Reference" in the Toolkit it says that the Broker is not running. But it is.
The Broker is running on a different machine thatn the Configuration Manager.
I defined the following channels/senders & queues:
QM_ConfigMGR:
define channel(ConfToBrokers) chltype(sdr) trptype(tcp) conname('155.208.44.235(1450)') xmitq(QM_Broker)
define channel(BrokersToConf) chltype(rvcr) trptype(tcp)
define listener(QMListener) trptype(tcp) port(1450) control(QMGR)
define qlocal(QM_Broker) usage(XMITQ) replace
QM_Broker:
define channel(BrokersToConf) chltype(sdr) trptype(tcp) conname('155.208.44.234(145)') xmitq(QM_ConfigMGR)
define channel(ConfToBrokers) chltype(rcvr) trptype(tcp)
define listener(BrokerListener) trptype(tcp) port(1450) control(QMGR)
define qlocal(QM_ConfigMGR) usage(XMITQ) replace
did I miss anything? Do I have to "register" the Broker to the Configuration Manager in any way?
Any help is greatly appreciated! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Jul 05, 2009 11:00 am Post subject: Re: Communication between ConfigMGR and Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mk wrote: |
| did I miss anything? Do I have to "register" the Broker to the Configuration Manager in any way? |
You can't connect the Tookit to the broker. You connect the tookit to the config mngr and that connects to the broker once that broker is part of the config mgr's topology.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mk |
| Posted: Sun Jul 05, 2009 11:54 am Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
So do I have to configure anything more? The Configuration Manager seems not to know my remote Broker... How is the Configuration Manager connecting to the Brokers? Does it search for user defined queues and testing those?
edit: I get BIP1533E when I try to deploy anything to that broker |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jul 05, 2009 12:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mk wrote: |
| How is the Configuration Manager connecting to the Brokers? |
Using the objects you've defined, once properly configured.
| mk wrote: |
| Does it search for user defined queues and testing those? |
No.
| mk wrote: |
| edit: I get BIP1533E when I try to deploy anything to that broker |
How are you deploying, when your broker doesn't seem to be connected to a config mgr? Specifically, why do you think you'll be able to manage the broker's configuration without using a configuration manager that has control of the broker?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Jul 05, 2009 12:17 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You have to add your broker to the list of known brokers that the config manager knows about.
Select Broker Admin Perspective (the one you used to connect the Toolkit & the broker) and right click on the config manager & you will be add a broker. Once you have deployed the change in configuration and the config manager has connected to the broker successfully, you will be able to deploy to the broker. But this would have been amply covered if you had received some decent training in the prodict.
You did get some training didn't you? 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Jul 05, 2009 12:19 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
It's hard to be sure without you giving us the QM names involved, but it seems that your XMITQ names are off. The XMITQ name has to be the same name as the remote QM. From the chapter "Connecting components".
| Quote: |
| Define a transmission queue on each component's queue manager. These transmission queues collect messages ready for transmission between components. The transmission queue must have the same name as the queue manager to which it transmits messages |
Oh, and next time first build your configmgr-broker network, make sure it works, and only then put it under HA control. And it would have been better to begin with configmgr and broker on the same QM before moving on to different QMs. Start simple, add complexity, not the other way around.
Good luck  |
|
| Back to top |
|
|
| mk |
| Posted: Sun Jul 05, 2009 12:35 pm Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Ok guys,
first of all I would like to say that I tried to get this to work for hours before asking this question here. In that process I tried everything that came into my mind of what I thought that could help determing the problem.
and of course I started with broker & qm on the same machine, there it all worked fine. of course this was also without HA involved.
@hopsala: QM names involved are "QM_Broker" for the Broker and "QM_ConfigMGR" for the Configuration Manager. So I think the XMITQ names should be right.
@vitor: could you be so gracious and point out HOW those objects have to be defined?
@smdavies: already did that. I delted the connection from the Toolkit, recreated it and then it listed the broker in the "broker topology". However with the warning "broker is not running" which I don't understand. Does this mean the Configuration Manager can actually connect to the broker's QM but somehow thinks the broker is not running? Or is this just an error telling me that nothing works?
Shouldn't be an issue with the dynamic IP's I'm using for HA? I specified those IP's in the channels and currently broker and configuration manager are running under those IP adresses. |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Jul 05, 2009 12:48 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Sorry, didn't notice you wrote the QM names. Are the channels up? Do you see any messages stuck in the XMITQ? Did you check the MQ logs for errors (such as auth errors)? Did you check the event log?
You should also try sending a test message from one QM to the other, and connecting with a client to the ConfigMgr QM.
Oh, and I hope
| Quote: |
QM_ConfigMGR:
define channel(ConfToBrokers) chltype(sdr) trptype(tcp) conname('155.208.44.235(1450)') xmitq(QM_Broker)
...
QM_Broker:
define channel(BrokersToConf) chltype(sdr) trptype(tcp) conname('155.208.44.234(145)') xmitq(QM_ConfigMGR) |
is a typo. |
|
| Back to top |
|
|
| mk |
| Posted: Sun Jul 05, 2009 12:56 pm Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
yes that's a typo 
channels are all up, here's the detailed status:
QM_Broker:
AMQ8417: Display Channel Status details.
CHANNEL(BROKERSTOCONF) CHLTYPE(SDR)
CONNAME(155.208.44.234(1450)) CURRENT
RQMNAME(QM_ConfigMGR) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(QM_CONFIGMGR)
AMQ8417: Display Channel Status details.
CHANNEL(CONFTOBROKERS) CHLTYPE(RCVR)
CONNAME(155.208.44.227) CURRENT
RQMNAME(QM_ConfigMGR) STATUS(RUNNING)
SUBSTATE(RECEIVE)
QM_ConfigMGR:
AMQ8417: Display Channel Status details.
CHANNEL(BROKERSTOCONF) CHLTYPE(RCVR)
CONNAME(155.208.44.230) CURRENT
RQMNAME(QM_Broker) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(CONFTOBROKERS) CHLTYPE(SDR)
CONNAME(155.208.44.235(1450)) CURRENT
RQMNAME(QM_Broker) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(QM_BROKER)
I'm able to connect to the Configuration Manager's Queue Manager with the Toolkit.
Could you please give me a hint on how to send a test message or how to look up messages in the XMITQ?
Thank you |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jul 05, 2009 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mk wrote: |
| I delted the connection from the Toolkit, recreated it and then it listed the broker in the "broker topology". However with the warning "broker is not running" which I don't understand. Does this mean the Configuration Manager can actually connect to the broker's QM but somehow thinks the broker is not running? Or is this just an error telling me that nothing works? |
This means it's successfully connected to the broker's queue manager, determined that the broker is present but that it's not running.
Double check the broker is actually running, then try the broker logs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mk |
| Posted: Sun Jul 05, 2009 1:58 pm Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Ok, so I checked with ps -efax | grep bip if the broker is running and it is.
But I think I have an idea what causes this error... When I issue a "netstat -an | grep 1450" I geht the following on the Configuration Manager Node:
tcp 0 0 155.208.44.227.51118 155.208.44.235.1450 ESTABLISHED
tcp 0 0 155.208.44.234.1450 155.208.44.230.59561 ESTABLISHED
tcp 0 0 *.1450 *.* LISTEN
Same command on the Broker Node:
tcp 0 0 155.208.44.235.1450 155.208.44.227.51118 ESTABLISHED
tcp 0 0 155.208.44.230.59561 155.208.44.234.1450 ESTABLISHED
tcp 0 0 *.1450 *.* LISTEN
Ok so it seems there are existing connections in both ways BUT what confuses me are the IP addresses "155.208.44.230" and "155.208.44.227". Those are the IP addresses of the machines BUT I'm using dynamic IP's because of HA 
So my guess now is that the Configuration Manager actually checks IP 155.208.44.230 for a running broker but the broker is running under the IP 155.208.44.235.
Is there a way to specify the IP address on which listeners shall listen? I think that could solve my problem.
So Broker's IP is 155.208.44.235 and Configuration Manager's IP is 155.208.44.234 |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jul 05, 2009 2:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mk wrote: |
So my guess now is that the Configuration Manager actually checks IP 155.208.44.230 for a running broker but the broker is running under the IP 155.208.44.235.
|
And I should have looked at your channel definitions more closely. You've specified CONNAME in the RCVR channels; that's not going to get you very far. Look up LOCALADDR.
But if you're using HA, you're much better advised to use hostnames rather than any IP address, and let the network layer sort out the switchover.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mk |
| Posted: Mon Jul 06, 2009 12:04 am Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Guys, I forgot to grant access to my Windows user... So after issuing a setmqaut -m QM_Broker -t qmgr -p winuser +all it works!
The Warning that the Broker is not running is gone and I already changed the broker's configuration for testing and the broker actually did receive the message and changed it's configuration.
 |
|
| Back to top |
|
|
|
|
