| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Multiple people need to deploy to same brokers --> help! |
« View previous topic :: View next topic » |
| Author |
Message
|
| kumarp |
 Posted: Thu Jul 29, 2004 11:55 am Post subject: Multiple people need to deploy to same brokers --> help! |
 |
|
Novice
Joined: 20 May 2003
Posts: 23
|
Hi,
We have a simple WBIMB 5.0 setup right now --> three test and one production broker, all on z/OS, and all controlled by the configuration manager and toolkit on my Windows workstation. Up til now, I was the only one on our team working with WBIMB, but now we have other people on our team who would like to deploy flows to the same brokers. What I'm trying to figure out is the best way to restructure our environment.
We are thinking of creating a new configuration manager on a separate windows workstation that will always be available, so each of us can connect to it from our own WBIMB toolkits. Does this sound like a viable solution? I realize that doing this will require us to remove all configuration data from our brokers (on z/OS, we'll run the job BIPJRSTC for each broker to bring it back to it's original state after installation) and redeploy everything using the new configuration manager.
Any thoughts on this? Are there best practices? Can anyone give me some advice or point me to some resources?
Also, what are your thoughts on having test and production brokers controlled by the same configuration manager? Good idea or bad? And if we decide to have our test and production brokers on separate config. managers, can the config managers at least be on the same windows machine, or is it just one config. manager per windows machine?
Thanks! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jul 29, 2004 1:22 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's one config manager per windows machine, because the ConfigMgr service has a fixed name.
That said, it used to be necessary (that is, recommended practice...) to have separate configuration managers for each environment (dev, test, prod). But in version 5 there is a new set of ACL commands that may provide the granularity of security that you need - in that you can separate user permissions based on broker and execution group (at least according to the manual) rather than merely by role membership.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jul 29, 2004 3:28 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Also, what are your thoughts on having test and production brokers controlled by the same configuration manager? Good idea or bad?
|
Since at 5.0 you can set up security at such a granular level, you will be able to prevent your developers from accidently/maliciously connecting to the Production broker and deploying. But that means you are going to have to maintain all those security groups. Far easier and safer I think to just have a dedicated box for each environment and restrict access to the production machine as a whole.
And, even for the person that does have legitimate access to both TEST and PROD, you know sooner or later someone is going to deploy to the wrong broker by accident. A separate machine makes that less likely.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
