| Author |
Message
|
| sumit |
 Posted: Tue Jun 12, 2012 2:37 am Post subject: Domain-ConfigMgr-Broker intercommunication |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Hi,
I am stuck with some very basic questions/doubts and need your help here. There are multiple queries hence you may find this post a little longer than the usual ones.
Details
MQ-7.0.1.7
MB 6.1
OS - Windows XP (sorry, can't change)
I have installed MB on my Windows machine. Created configuration manager(CMGR) on a queue manager CMGR and started it. Did database (BRK1) setup and authorized the broker user id to access the database.
Now, I created a domain connection and gave the details of the configmgr. While trying to connect, it gave me an error -
| Quote: |
BIP0889E with reason: "While the message broker toolkit was able to connect to the config mgr's qmgr (CMGR), no response from the config mgr received. This implies that the config mgr is not running.
Ensure that the config mgr is running and that it can be reached from msg broker toolkit.If the config mgr is simply running slowly, try increasing the time the msg broker toolkit waits for config mgr messages using the broker admin perferences." |
I've checked that all the services are running, the broker id has access on the queue manager and is part of all the groups. I have searched google and checked the MB infocenter but no joy.
When I looked for local help, I was informed that I have to create broker before making the domain. (though I wonder why?  ). I followed the advice and created it, used a different queue manager for broker (BROKER_QMGR_v6) and again tried making the domain, but the result was same. I was again informed that the queue manager for both the config mgr and the broker must be same (I again wondered why, it may be best practice but I doubt if it is must )
I again followed the advise and used the same qmgr for the config manager as was used for broker. Result, same error.
My queries are-
1. How to resolve the error that I am getting?
2. Is it fine to have separate qmgrs for config mgr and the broker?
From infocenter-
| Quote: |
Enter the following command to create the Configuration Manager:
mqsicreateconfigmgr CMGR01 -i wbrkuid -a wbrkpw -q WBRK_QM If you are using different names or values for any parameter on this command, you must replace the appropriate values with your own.
In the command above:
WBRK_QMIs the name of the WebSphere MQ queue manager that will host the Configuration Manager. This is created if it does not exist. |
3. How is creating a domain dependent on the presence of broker? (keeping in mind the machine is new and I am going to start fresh development work)
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| kash3338 |
| Posted: Tue Jun 12, 2012 3:45 am Post subject: Re: Domain-ConfigMgr-Broker intercommunication |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| sumit wrote: |
My queries are-
1. How to resolve the error that I am getting?. |
The error may be because of this,
| Quote: |
| You cannot connect to a Version 2.1 Configuration Manager. An error is thrown, and you will not be able to populate the domain with brokers or topics, or connect to it using the workbench.. |
| sumit wrote: |
2. Is it fine to have separate qmgrs for config mgr and the broker? |
Yes.
| sumit wrote: |
3. How is creating a domain dependent on the presence of broker? (keeping in mind the machine is new and I am going to start fresh development work) |
Creating a domain is not dependent on presence of a local Broker.[/quote] |
|
| Back to top |
|
|
| sumit |
| Posted: Tue Jun 12, 2012 5:22 am Post subject: Re: Domain-ConfigMgr-Broker intercommunication |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| kash3338 wrote: |
The error may be because of this,
| Quote: |
| You cannot connect to a Version 2.1 Configuration Manager. An error is thrown, and you will not be able to populate the domain with brokers or topics, or connect to it using the workbench.. |
|
A new configuration manager was created on MB v6.1
_________________
Regards
Sumit |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 12, 2012 5:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Delete all of the broker objects that you've created. Make sure you instruct the delete command to remove the repositories in question.
Start from scratch.
Create a queue manager CFGMGRQM. Create a queue manager BKRQM.
Create a bidirectional sdr/rcvr pair between them, with XMITQs named after the relevant broker. I.e. create an XMITQ on CFGMGRMQ named BKRQM and a sender that uses that XMITQ. And then do the reverse on BKRQM.
Then create and start a configmgr that uses CFGMGRQM as it's queue manager.
Then create and start a Broker that uses BKRQM as it's queue manager.
Then connect to the Configmgr from your toolkit and then create the broker OF THE SAME NAME as the broker you already created.
You aren't really "creating" the broker when you create the domain. You're actually *registering* it with the ConfigMgr. |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Jun 13, 2012 12:47 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| mqjeff wrote: |
Delete all of the broker objects that you've created. Make sure you instruct the delete command to remove the repositories in question.
Start from scratch.
Create a queue manager CFGMGRQM. Create a queue manager BKRQM.
Create a bidirectional sdr/rcvr pair between them, with XMITQs named after the relevant broker. I.e. create an XMITQ on CFGMGRMQ named BKRQM and a sender that uses that XMITQ. And then do the reverse on BKRQM.
Then create and start a configmgr that uses CFGMGRQM as it's queue manager.
Then create and start a Broker that uses BKRQM as it's queue manager. |
Done
| mqjeff wrote: |
| Then connect to the Configmgr from your toolkit and ... |
Same error
_________________
Regards
Sumit |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Jun 13, 2012 12:54 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Earlier, I had MB 8 Demo version installed on my machine. When the trial period got over, I uninstalled it and installed MB 6.1.
If that helps...
_________________
Regards
Sumit |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 13, 2012 1:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Then the configmgr is not running. |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Jun 13, 2012 2:17 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
I have started the configuration manager from command prompt and can see that it's process is running in services.msc. Both the config mgr qmgr (CMGR_QM) and broker qmgr (BRK_QM_1). The respective sdr/rcvr channels are in inactive mode (they were running when I started them) and the listener is up as well.
Here are the commands that I used-
crtmqm CMGR_QM
STRMQM -ss CMGR_QM
CRTMQM BRK_QM_1
STRMQM -ss BRK_QM_1
mqsicreateconfigmgr CMGR -q CMGR_QM -i wuser -a xxx
mqsistart CMGR
mqsicreatebroker BRK_1 -q BRK_QM_1 -i wuser -a xxx -n BRK1
mqsistart BRK_1
_________________
Regards
Sumit |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Jun 13, 2012 2:20 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
More information, after installing MB 6, the mqsi commands were not running on the Broker command console. I googled and kept a copy of mqsiprofile.cmd file at C:\Documents and Settings\All Users\Application Data\IBM\MQSI\Common\profiles.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 13, 2012 4:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| sumit wrote: |
| More information, after installing MB 6, the mqsi commands were not running on the Broker command console. I googled and kept a copy of mqsiprofile.cmd file at C:\Documents and Settings\All Users\Application Data\IBM\MQSI\Common\profiles. |
No, that's not the right thing to do.
Among other reasons, the only thing that causes any scripts in that directory to be executed is the mqsiprofile itself.
The fact that you can see the ConfigMgr process running does not mean that the configmgr is running. It may, for example, be abending frequently and is only around long enough for you to observe that it's running before it dies and restarts. |
|
| Back to top |
|
|
|
|
