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 » Broker table name

Post new topic  Reply to topic
 Broker table name « View previous topic :: View next topic » 
Author Message
KIT_INC
PostPosted: Wed Jul 23, 2008 5:49 am    Post subject: Broker table name Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

We are planning to migrate from WMB V6.0 to V6.1
In the installation manual, it says
"Multiple brokers in the same installation can access the same database, if appropriate, because all tables are qualified by the broker name...."
On my test PC (WinXP), I have both WMB V60 and V61 installed. The V60 broker (BRK60) and the V61 broker (BRK61) are using the same database (Oracle XE 10). However in my XE database, I do not see any table with BRK60 or BRK61 as part of the name. Did I miss something ?
How can I tell which table is for which broker?
Back to top
View user's profile Send private message
sridhsri
PostPosted: Wed Jul 23, 2008 7:27 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

If I am not mistaken, the table names remain the same. Each table maintains a column which contains the broker name.
Back to top
View user's profile Send private message
KIT_INC
PostPosted: Wed Jul 23, 2008 7:57 am    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

So the manual is wrong ?
Back to top
View user's profile Send private message
sridhsri
PostPosted: Wed Jul 23, 2008 8:02 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I quote from the manual
Quote:
The tables are created when you create the first broker. When you create further brokers specifying the same database, new rows are created for each broker. Every row created in the table includes the broker name, therefore each row is unique to a single broker.


So, the manual is not wrong.
Back to top
View user's profile Send private message
KIT_INC
PostPosted: Wed Jul 23, 2008 9:07 am    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

Perhaps I do not know how to read the table. I can see column name of brokeruuid but not brokernames. I think the manual is referring to brokeruuid as brokername.
Back to top
View user's profile Send private message
sridhsri
PostPosted: Wed Jul 23, 2008 9:14 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I am sure there is a table which stores both brokeruuid and brokername. It is only the brokeruuid which is referred to in all other tables.
Back to top
View user's profile Send private message
sridhsri
PostPosted: Wed Jul 23, 2008 9:19 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

On second thoughts, I think the brokername and brokeruuid is stored in the confgmgr database. The broker tables only have the brokeruuid. If you want to see the contents of the configmgr database, you'll have to (on windows) open
"C:\Documents and Settings\All Users\Application Data\IBM\MQSI\components\ConfigMgr\BERNARD"

BERNARD is the derby database. You could use the executable jar - derbytools.jar. This contains an executable class called - org.apache.derby.tools.ij. This should take you to the ij prompt. There you will have to use the connect command to connect to BERNARD. a list table command should tell you which table to look at (i used to know what the table name was).
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Jul 23, 2008 10:49 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Of course, the configmgr repository is an internal repository and as such should be left alone by anyone other than IBM support...

And one shouldn't assume that it will remain a Derby database, or a database at all.
Back to top
View user's profile Send private message
sridhsri
PostPosted: Wed Jul 23, 2008 10:57 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I completely agree with mqjeff. But if curiosity gets the better of you, I found the table and column you are looking for. The broker details are stored in the CBROKER table on the Config Manager. The column name is CNAME. Due to restrictions with Derby, you must stop the config manager before you can connect to this database.
Back to top
View user's profile Send private message
KIT_INC
PostPosted: Thu Jul 24, 2008 5:04 am    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

Thanks a lot sridhsri for the explanation. I am learning a lot here on this forum. I have difficuties getting derbytools.jar to run. Is there any pointer to doc that describe how class path and parameters should be set?
I am getting " The jar file is missing the manifest entry for the main class: derbytools.jar" error. I am running it from C:\Program Files\IBM\MQSI\6.0\classes>
Back to top
View user's profile Send private message
sridhsri
PostPosted: Thu Jul 24, 2008 5:42 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I set derby.jar and derbytools.jar to the classpath in the MQSI Command console and it worked fine. Perhaps you could also try that.
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 » Broker table name
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.