| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Design Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Thu Nov 17, 2005 11:13 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You only need one configmgr for your entire system.
Most people tend to use one config mgr per environment - dev, test, prod, etc.
But you don't need to do that - it's just somewhat easier to manage security and change control that way.
It is a very bad waste of resources and staff time to have more than one configmgr per environment, and even worse to have one configmgr for each broker.
You should go back and read the overview documentation again.
Also in v6 of Broker, you can have more than one configmgr per machine.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Nov 17, 2005 11:26 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| You only need one configmgr for your entire system. |
And how do you handle testing of FixPacs, CSDs, or Refreshes (depending on the flavour of the day) where the level needs to match the Broker, and you can't upgrade your production broker until it's been through all the usual Test/QA cycle.
I hit something similar trying to move to a later version of a SupportPac, as all the Toolkits, and the Brokers had to upgraded together. I'll let you guess what my management said about that. Or perhaps you heard the laughter. 
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 17, 2005 11:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| EddieA wrote: |
| Quote: |
| You only need one configmgr for your entire system. |
And how do you handle testing of FixPacs, CSDs, or Refreshes (depending on the flavour of the day) where the level needs to match the Broker, and you can't upgrade your production broker until it's been through all the usual Test/QA cycle. |
I didn't say I'd do that... I just said it's possible.
And I did say
| Quote: |
| it's just somewhat easier to manage security and change control that way. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| CoolDude |
| Posted: Sat Nov 19, 2005 10:09 am Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
If your budget allows, I suggest that you have seperate streamlines/pipelines, then you can have one ConfigurationManager per environment per pipeline.
If you have only one Configuration Manager per environment for multiple brokers..it might get messy(depending on the way you deploy to multiple brokers) if you have some common subflows.
Thanks.
_________________
Correct Me from Wrong  . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Nov 19, 2005 10:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| 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
|
|
|
|
