| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration Manager Planning issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| sieijish |
 Posted: Mon Feb 21, 2005 3:03 am Post subject: Configuration Manager Planning issue |
 |
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
We have the the following WBI MB Infrastructure
Devmt Environmet
1 IBM p-615 Server
Model Environment
3 IBM p-630 Servers, Clustered.
Prod Environment
3 IBM p-650 Servers, Clustered.
And now since Configuration Manager cannot be installed on AIX machines and only one configMgr can exist on a single box, I have to request additional hardware with windows OS for hosting the Configuration Manager.
That is 3 more additional machines - one for Devmt Broker domain, Model domain & prod domain.
Isn't this an over-kill? Also it adds to the software maintenance overhead (os, db2, mq, wbimb on 3 more boxes).
Is there any better solution than going for 3 more machines?
I have seen some pointers in this forum that all the brokers can be managed from a single configuration manger? Does that solutions work without UserNameServer. Also, in that solution, how do I seperate my devmt, model & production domain?
What is the best practice for this? |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Mon Feb 21, 2005 3:41 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
you can manage multiple brokers from one configuration manager, however for various reasons like different environments, version control, etc I would advise against sharing a configuration managers for different environments.
if for example you had 2 development brokers they could be managed from one configuration manager
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 21, 2005 4:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Version 5 includes access control lists for broker security, providing very fine detail over and above the five groups in traditional broker security.
If you are willing to manage this, you can specify that user A can only work with broker 1 in Dev, and not anything in test or prod, and likewise with other users and groups and resources.
Read up on mqsicreateaclgroup and etc. in the documentation.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sieijish |
| Posted: Mon Feb 21, 2005 6:08 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
Thanks for the suggestions.
The real issue here is additional harward & maintenance costs. Ideally, I would have used a single windows box to run 3 seperate configuration manager services to manage the 3 domains (devmt, model, prod).
Any good reason why IBM put the limitation that only a single configuration manager can run on a single box? createconfigmanager doesn't take the 'name' either. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 21, 2005 6:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The point of my suggestion re: access control lists is that you could then use one config manager for all three environments.
I guess I forgot to actually state my point... 
The reason that the mqsicreateconfigmgr doesn't take a name parameter is exactly because you can only have one per box. I suspect that the limitation of one per box is because of the security role that the config manager plays - and the limitations in the old group/role security model. If you can only have five or six roles, and each role is uniquely determined by membership in a fixed name group... then how can you have different security policies for two config managers on the same box? And if you can't have different security policies... what good is more than one config manager?
Again, the new access control lists don't have the same restrictions.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
