ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB-tookit -> cfgmanager cant discover broker.

Post new topic  Reply to topic Goto page Previous  1, 2
 WMB-tookit -> cfgmanager cant discover broker. « View previous topic :: View next topic » 
Author Message
chids
PostPosted: Wed Mar 04, 2009 1:20 am    Post subject: Reply with quote

Novice

Joined: 09 Oct 2006
Posts: 22
Location: Stockholm, Sweden

Blomman wrote:
Problem solved!

Somehow the CFGmanager and WMB got different UUIDs.....
I recreated the broker and now it works fine.

Txh for the input.

Regards!
//Michael


Sorry if this is a bit late in the discussion but did you try to adopt the broker using the Configuration Manager Proxy API Excerciser?

Quote:

In previous releases of WebSphere Message Broker if a broker became orphaned from its Configuration Manager it was not possible to connect it to a new Configuration Manager. In WebSphere Message Broker V6.1 this limitation has been removed. It is now possible to associate an existing broker with a specific Configuration Manager. A broker can only be associated with one configuration manager at a time and it is not recommended to use this adopt a broker facility to migrate a broker from development all the way to production by simply changing the configuration manager that it is associated with.
To adopt a broker, use the adoptBroker method of the TopologyProxy class (TopologyProxy.adoptBroker()). This nethod requests that a new configuration manager take over management of a broker previously managed by another configuration manager. You can use the Configuration Manager Proxy (CMP) API Exerciser sample for guidance here. When adopting a broker in this way, the state in the run-time broker supersedes any information in the configuration manager.
from Tim Dunn's article "What's new in WebSphere Message Broker V6.1" @ http://www.ibm.com/developerworks/websphere/library/techarticles/0802_dunn/0802_dunn.html
_________________
/mårten.
-- http://marten.gustafson.pp.se/
-- marten.gustafson@gmail.com
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
Blomman
PostPosted: Wed Mar 04, 2009 11:40 pm    Post subject: Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

chids wrote:
Blomman wrote:
Problem solved!

Somehow the CFGmanager and WMB got different UUIDs.....
I recreated the broker and now it works fine.

Txh for the input.

Regards!
//Michael


Sorry if this is a bit late in the discussion but did you try to adopt the broker using the Configuration Manager Proxy API Excerciser?

Quote:

In previous releases of WebSphere Message Broker if a broker became orphaned from its Configuration Manager it was not possible to connect it to a new Configuration Manager. In WebSphere Message Broker V6.1 this limitation has been removed. It is now possible to associate an existing broker with a specific Configuration Manager. A broker can only be associated with one configuration manager at a time and it is not recommended to use this adopt a broker facility to migrate a broker from development all the way to production by simply changing the configuration manager that it is associated with.
To adopt a broker, use the adoptBroker method of the TopologyProxy class (TopologyProxy.adoptBroker()). This nethod requests that a new configuration manager take over management of a broker previously managed by another configuration manager. You can use the Configuration Manager Proxy (CMP) API Exerciser sample for guidance here. When adopting a broker in this way, the state in the run-time broker supersedes any information in the configuration manager.
from Tim Dunn's article "What's new in WebSphere Message Broker V6.1" @ http://www.ibm.com/developerworks/websphere/library/techarticles/0802_dunn/0802_dunn.html


Nice input!
I was actually starting to use the CMP(BrokerProxy.setUUID() method), but then i suddenly got lazy and just recreated the broker....

//Michael
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB-tookit -> cfgmanager cant discover broker.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.