Author |
Message
|
gmabrito |
Posted: Mon Jun 30, 2003 6:14 am Post subject: two brokers one broker database? |
|
|
 Apprentice
Joined: 19 Mar 2002 Posts: 35
|
Has anyone shared broker databases for multiple brokers? We are using a database server for our broker database instead of having local databases to reduce administration tasks. Everything seems to be working fine just wondering if anyone has come across side effects.
Thanks in advance. |
|
Back to top |
|
 |
fcotait |
Posted: Mon Jun 30, 2003 6:23 am Post subject: |
|
|
 Acolyte
Joined: 28 Feb 2002 Posts: 63 Location: Sao Paulo - Brazil
|
I already used this, but only for lab. I didn´t have any problem
For performance this isn´t recommended. See Suport Pack WebSphere MQ Integrator for [plataform] V2.1 - Performance report _________________ Filipe Cotait
IBM Certified System Administrator - WebSphere MQ
IBM Certified Specialist - MQSeries, WebSphere MQ Integrator |
|
Back to top |
|
 |
vmcgloin |
Posted: Mon Jun 30, 2003 7:27 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
We have had 3 brokers sharing a single database in production with 2.0.2 for a year now - no problems. No problems with our 2.1 brokers sharing databases either.
Now that you've mentioned it though I'm off to study the performance doc more closely before upgrading production to 2.1 on Sunday. |
|
Back to top |
|
 |
mq_series |
Posted: Mon Jun 30, 2003 8:06 am Post subject: |
|
|
Apprentice
Joined: 29 Oct 2001 Posts: 30
|
Hi,
Though we can use any number of brokers sharing a common database.But IBM books suggest using separate databases for each broker.The reason being if u use single database then all your brokers are dependent on a single database , so if you have to shut down the database for some reason then all your brokers will be down.
Regards
rkv |
|
Back to top |
|
 |
rwa |
Posted: Tue Jul 01, 2003 3:03 am Post subject: |
|
|
Voyager
Joined: 22 Jan 2002 Posts: 76 Location: Duesseldorf/Germany
|
The data model of the broker database is designed to handle multiple brokers. Therefore no side effects should be seen.
But the performance will be an issue.
The performance of a database table depends heavily on the amount of rows. Several brokers will lead to more rows in each table. Therefore the performance will decrease.
But if several databases are installed on a single server the performance will descreae also, because of the limited resources of a server.
So the desicion of hardware and software infrastructure should be made very carefully and has to depend on the demands of the users/applications. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Jul 01, 2003 6:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Another issue with using the same database for multiple brokers is software upgrades.
Particularly for the conversion to version 5 of Websphere Integrator, you will have to convert all brokers sharing the same database at the same time. So if all your production brokers are using one database, you'll have to update all of your production brokers before you can use any of them. This means if nothing else longer down time. |
|
Back to top |
|
 |
|