| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration Manager was unable to register for internal |
« View previous topic :: View next topic » |
| Author |
Message
|
| raghug |
 Posted: Mon May 19, 2008 12:04 pm Post subject: Configuration Manager was unable to register for internal |
 |
|
Acolyte
Joined: 19 Jul 2006
Posts: 60
Location: NJ
|
Hi all
The Configuration Manager was unable to register for internal subscriptions with broker 'MQDSGEN01'.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker 'MQDSGEN01' was not successful. This means that Message Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to broker 'MQDSGEN01'.
let me know any one have idea
Thanks
Raghu |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon May 19, 2008 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This is because the userid that is running the config mgr is unknown to the OS running the broker. Does not matter if you have an ACL authorizing the work... Don't remember if a channel mcauser will fix it, but I found something in the logs pointing to that effect.
So far the only disadvantages I have seen are in the subscription panel and this cryptic message after deployment...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| raghug |
| Posted: Mon May 19, 2008 1:57 pm Post subject: Yes you are right |
|
|
Acolyte
Joined: 19 Jul 2006
Posts: 60
Location: NJ
|
Yes you are right I saw below message in IBM infocenter please let me know how wpould I solve
Message BIP1536
Scenario: You have defined a Configuration Manager to run with one user ID, and you have defined a broker to run on a different computer with a different user ID. Deployment is successful but error message BIP1536 is issued when you deploy message flows to the broker.
Explanation: The Configuration Manager is unable to register for internal subscriptions with the broker because the broker is running under one ID and the Configuration Manager is running under another ID. The broker and the Configuration Manager relay internal messages back and forth via publish/subscribe. These messages are carried through WebSphere MQ, which requires certain authorizations.
Solution:
Ensure that the broker's user ID is a member of the mqm and mqbrkrs groups.
Define the broker's user ID on the computer where the Configuration Manager is running.
Define the user ID used by the Configuration Manager on the computer where the broker is running.
Ensure that all IDs are in lowercase so that they are compatible between computers. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 19, 2008 7:11 pm Post subject: Re: Yes you are right |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| raghug wrote: |
Solution:
Ensure that the broker's user ID is a member of the mqm and mqbrkrs groups.
Define the broker's user ID on the computer where the Configuration Manager is running.
Define the user ID used by the Configuration Manager on the computer where the broker is running.
Ensure that all IDs are in lowercase so that they are compatible between computers. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
