| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB6 ConfigMgr database |
« View previous topic :: View next topic » |
| Author |
Message
|
| billybong |
 Posted: Mon Oct 31, 2005 2:15 am Post subject: WBIMB6 ConfigMgr database |
 |
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
It seems like a silly question but since I've searched everywhere without an answer I gave up and posted it instead.
Can you use another DB than DB2 for your configmgr in WBIMB6? If so, which? The same as for the broker? DB2, Oracle, Sybase, SQL Server? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Oct 31, 2005 2:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The config mgr in v6 doesn't have a database.
The only options on mqsicreateconfigmgr in v6 about databases are about providing information to migrate configmgr info out of a v5 database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Oct 31, 2005 2:54 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| jefflowrey wrote: |
| The config mgr in v6 doesn't have a database. |
I think you need to rephrase that. the config mgr in v6 has no 'external' database (actually it is using Derby as an integrated database)
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| billybong |
| Posted: Mon Oct 31, 2005 4:12 am Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
| Wow, must have slept during that part of the seminar. Thanx guys! |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Oct 31, 2005 5:40 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Michael Dag wrote: |
| the config mgr in v6 has no 'external' database (actually it is using Derby as an integrated database) |
By the way, I wouldn't rely on the internal CM database format being based on Derby (e.g. in scripts). The DB manager is deliberately not specified.
Any CM database manipulation stuff that you may ever need to do should all be done using the Config Manager Proxy API. If you use any Derby/JDBC specific tools to hack around the CM database, you're liable to end up with a fried Config Manager. |
|
| 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
|
|
|
|
