| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| pfaulkner |
 Posted: Fri Jun 06, 2003 1:49 pm Post subject: Configuration Question |
 |
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Can a Config Mgr support multiple Brokers and if so is this recommended?
Should each of my Brokers have it's own Config Mgr running on it's own NT box?
Just trying to figure out what hardware I need to support my test and prod environment.
thanks for any input. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Sun Jun 08, 2003 12:58 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Yes, a single ConfigMgr can support multiple brokers. Just keep adding them in the Toplology and make sure you set up all the channels between the Queue Managers.
But, I would not recommend this for managing Test/Prod environments. You really should keep a Test and a Prod environment completely isolated from each other.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Jun 08, 2003 10:29 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You will need additional license if you are creating multiple brokers on seperate machines.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| wmqiguy |
| Posted: Tue Jun 10, 2003 1:33 pm Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 145
Location: Florida
|
I agree with Eddie....but then again, I always agree with Eddie. 
Here are some quick thoughts:
1. There should be a a very tall wall between TEST and PROD. Woe to the person that screws up a PROD environment because of a testing issue (at least where I work).
2. Config Mgrs like to complete one deploy before starting another one. This means that if one broker gets a little sluggish and does not accept the deploy message it blocks the ability of the config mgr to deploy to the other. This could be bad when crossing TEST/PROD.
My advice is to:
1. Use one ConfigMgr for Brokers in your non-PROD environments and experiment a little. (Example: test #2 above by stopping BROKER_A, deploying to it, and then try to deploy to BROKER_B.)
2. Keep PROD as a simple 1 ConfigMgr = 1 Broker, until you feel comfortable with the Administration. |
|
| 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
|
|
|
|
