| Author |
Message
|
| wbi_telecom |
 Posted: Wed Feb 15, 2006 1:14 pm Post subject: Problem in connecting to Config manger from broker toolkit |
 |
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
Environment
OS :- Windows XP
MQ 5.3 (CSD 10)
DB2 7.1
WBIMB 5.0, CSD 3
I am using same queue manager for config manager and broker. I created the DBs for config manager and broker and was able to create config manager and broker.
However I am not able to connect to config manager from the toolkit. Even though the error says that configuration manager is not avaialable but I can see the config manager service running.
Have I missed something?
Thank you
Here is the error message that I get
ConfigManagerProxy information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'db2admin@xyz' does not have authority to view the object. (UUID='', required attribute='name') |
|
| Back to top |
|
 |
| dilse |
| Posted: Wed Feb 15, 2006 2:26 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
| Did you check to see if your username is in mqb* groups and also make sure your username has Adminstrator rights on your computer. Also did you see if there are any errors in Event viewer that explains the situation? Let us know. |
|
| Back to top |
|
|
| Krayvyn |
| Posted: Wed Feb 15, 2006 2:30 pm Post subject: Already part of MQB groups? |
|
|
Novice
Joined: 08 Jun 2005
Posts: 12
|
I had a similiar issue where my user was part of the mqb groups.
I manually included the user (e.g. db2admin) in the MQ MCA user ID for the SYSTEM.BKR.CONFIG channel. That seemed to fix my problem.
Let me know how that works. Definitely not an expert but hopefully that helps. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 15, 2006 3:27 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are two completely different sets of authorizations that come into play when connecting a Toolkit to a ConfigMgr.
One is the ConfigMgr authorization - either through the groups or these days through the ACLS.
The other is MQ authorization - through membership in the mqm group on the configmgr machine or through an appropriate application of setmqaut commands.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Thu Feb 16, 2006 2:15 pm Post subject: Thanks Krayvyn |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
I did as suggested by Krayvyn and it worked like a charm.
BTW my user id was part of all the broker groups as well as the Administrator group. Still it was not working.
It started working the moment I put the id in the MQ MCA user ID for the SYSTEM.BKR.CONFIG channel |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 16, 2006 2:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This means that the problem was with the MQ authorities and not with the broker authorities.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmaniac |
| Posted: Thu Feb 16, 2006 2:36 pm Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
I had the same problem,I have stopped the configmgr and broker,
Applied CSD 07 for WBIMB 5.0,restared the server and
The Toolkit was working fine then..
Try this and check |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Thu Feb 16, 2006 2:42 pm Post subject: MQ Authorities |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
| The user id was part of mqm group as well. Shouldn't that take care of the MQ Authorities? |
|
| Back to top |
|
|
| mqmaniac |
| Posted: Thu Feb 16, 2006 2:42 pm Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
Check the application log and check to see if any errors refer to "JNI".
This may happen due to system's JRE and IBM java Plugin. |
|
| Back to top |
|
|
| fschofer |
| Posted: Thu Feb 16, 2006 2:46 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| pulaparty |
| Posted: Thu Feb 16, 2006 7:45 pm Post subject: |
|
|
Novice
Joined: 29 Jan 2006
Posts: 15
|
| I guess the userid used for broker setup doesn't have the access on DB2. Try granting the access to the relevant DB2 tables, or, try to run the DB2 service in the windows services as .\brokerUserID. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Mon Feb 20, 2006 1:03 pm Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
| The problem got resolved as soon as I did what Krayvyn had suggested. I was surprised because I have been working with MQ broker for quite some time now (back in the days when it was known as MQSI) but never had to so something like this as part of installation set up. |
|
| Back to top |
|
|
|
|
