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 » How is ConfigMgr managed when deleted/recreated?

Post new topic  Reply to topic
 How is ConfigMgr managed when deleted/recreated? « View previous topic :: View next topic » 
Author Message
Lex
PostPosted: Fri Apr 13, 2007 10:44 am    Post subject: How is ConfigMgr managed when deleted/recreated? Reply with quote

Acolyte

Joined: 14 Nov 2006
Posts: 73

Hello guys,

I'm working on MQSI 6.0 and WebSphere MQ 6.0.

Today, I wanted to start again a new configuration. I deleted Broker (previously named BRK_PREPROD), ConfigMgr (with default name) and the QMs which they are associated to (Broker's QM: QM_EAI_PREPROD, ConfigMgr's QM: QM_CFG_MGR).

Then i named the Broker's Queue Manager differently (QM_EAI_1_PREPROD) (All the other components keeping the same name).

Then when i tried to deploy to the broker, i had a message (sorry, don't have the error number in mind) telling me the deployment failed, because the Queue QM_EAI_PREPROD associated with the broker BRK_PREPROD couldn't be found.

So i failed after creating the domain on the Message Broker Toolkit, when i have to create a broker in the domain.

I thought that after deleting the configmgr, i would erase the data in it, but apparently the configmgr still associates the broker with a now deleted Queue Manager.

I also deleted a second time the configuration and kept the same name for all components, except for the configmgr which i named this time CM_PREPROD. Then i tried to create the broker like previously, and this time it worked!!

So, what's really the way the configmgr is managed when erased / recreated? the name of the configmgr is like an instance of a database? If so, how can I reset an instance?
Back to top
View user's profile Send private message
recallsunny
PostPosted: Fri Apr 13, 2007 11:25 am    Post subject: Reply with quote

Disciple

Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts

Lex, I'm sure you'll find a lot of posts on this if you search this forum..but here is what works for me.

Deleting configmr/broker installed in Win 2k/XP env..
1) Delete the Broker & configmgr configuration using the mqsidelete cmds.
2) Delete the QM's associated with Broker/Cfgmgr
3) Delete the Databases of the Broker/Configmgr
4) Open "Regedit" modify all entries of in the Registry which still have the Broker/Configmgr info(particularly their associated QM info).

Voila! you can recreated everything cleanly.

The reason your first attempt failed may be because the broker registry entry was still holding the previous QM association.
Back to top
View user's profile Send private message
Lex
PostPosted: Sat Apr 14, 2007 3:12 am    Post subject: Reply with quote

Acolyte

Joined: 14 Nov 2006
Posts: 73

Well, the admin part is on windows and the broker part on AIX.

I deleted the registry folder corresponding to the old broker, but it didn't seem to make anything special...

I also checked if the configmgr had a bad queue associated with the broker but the answer was no, so i don't know why i had this answer
Back to top
View user's profile Send private message
PrasLearnsWBI
PostPosted: Sun Apr 15, 2007 3:48 am    Post subject: Reply with quote

Novice

Joined: 06 Apr 2007
Posts: 13
Location: Budapest, Hungary

Quote:

Deleting configmr/broker installed in Win 2k/XP env..
1) Delete the Broker & configmgr configuration using the mqsidelete cmds.
2) Delete the QM's associated with Broker/Cfgmgr
3) Delete the Databases of the Broker/Configmgr
4) Open "Regedit" modify all entries of in the Registry which still have the Broker/Configmgr info(particularly their associated QM info).


We are on Win 2K, MB 5.0.6 , WMQ 5.3
I had the same problem as you, Lex. In my case deleting all impressions of the previous QMGR and CONFGMGR and BROKER was difficult from the registry. Then i figured out that QMGR, CONFGMGR and BROKER created legacy keys in the registry.

In that case, this may be helpful.


Download PsExec from http://www.sysinternals.com/utilities/psexec.html

Create a folder in your Program Files folder and name it PsExec. Place the psexec file in the folder. Create a batch file by opening Notepad and copying and pasting the following line into it :

Start "c:\Program Files\PsExec\psexec" -i -d -s c:\windows\regedit.exe

Save the file as PsExec Regedit.bat (the important thing is the .bat extension.)

When you click on the .bat file you've created it will open regedit in such a way that you should be able to delete the legacy keys.
_________________
I wonder that I am around !!
Back to top
View user's profile Send private message Visit poster's website Yahoo Messenger
Lex
PostPosted: Mon Apr 23, 2007 4:24 am    Post subject: Reply with quote

Acolyte

Joined: 14 Nov 2006
Posts: 73

Sorry Pras, I don't understand why i should use psExec instead of launching regedit from the execute dialog box.

But you are telling me that the source of the problem is that the windows registry keep traces of the old configuration that interfer when i do a new one, right?
Back to top
View user's profile Send private message
PrasLearnsWBI
PostPosted: Mon Apr 23, 2007 4:39 am    Post subject: Reply with quote

Novice

Joined: 06 Apr 2007
Posts: 13
Location: Budapest, Hungary

Quote:

But you are telling me that the source of the problem is that the windows registry keep traces of the old configuration that interfer when i do a new one, right?


Yes Lex, I also had similar problems in the past, where the old configuration interfered with the new ones. I searched a bit and found that the registry keeps impression of every configuration that we do. And unfortunately, some of the keys in the registry were LEGACY KEYS, which we cannot delete/remove using our normal administrative privileges.

If your problem has occured because of the old configuration in the registry, i would always suggest to delete them. Thats when psExec comes handy. Its a valid tool of Windows. I do not know how it works, but it looks like that psExec creates a regedit session for you with sufficient privileges that help you delete LEGACY KEYS.

If you find another means of deleting legacy keys, then you can do it your way too.

For me, psExec helped. I hope doing this removes everybit of your old configuration.

Happy Working !!
Pras
_________________
I wonder that I am around !!
Back to top
View user's profile Send private message Visit poster's website Yahoo Messenger
madhurao
PostPosted: Thu Apr 26, 2007 3:41 am    Post subject: what is the size of this file Reply with quote

Novice

Joined: 06 Jan 2005
Posts: 17

what is the size of this file?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How is ConfigMgr managed when deleted/recreated?
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.