| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Sharing Config Mgr and Broker for Devl/Test environments |
« View previous topic :: View next topic » |
| Author |
Message
|
| migerrits |
 Posted: Tue Jul 08, 2003 6:10 am Post subject: Sharing Config Mgr and Broker for Devl/Test environments |
 |
|
Apprentice
Joined: 13 Dec 2002
Posts: 35
Location: Canada
|
We're working with an outside contractor on a WMQI installation and would like to have a single Development / Test environment on a Config
Manager/Broker pair so that the contractor can work with Development-level objects but cannot touch the Test objects.
We're thinking about this because we'd like to maintain control over the Test environment while letting the contractor do Development work without harming the Test environment, but all on the *SAME* Config Manager/Broker setup.
I can't find anything in the docs that say that we can do this. I've suggested that the contractor should use PCs for the Mgr/Broker setup, rather than servers, for their separate environment. The contractor can then export message flows and sets for us to import into the Test environment. I'm all for completely separate environments, but the managers have other issues to think of, such as cost. 
Does my idea sound like a good plan?
Thanks! 
Mike |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 08, 2003 6:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
To the best of my knowledge, there is no way to secure access to individual brokers on the same ConfigMgr. If you have access to one broker being used by a ConfigMgr, you have access to all of them.
That doesn't mean you can't have two brokers on the same machine being controlled by different ConfigMgrs. You just can't have two ConfigMgrs on the same machine.
So you could set up a separate development ConfigMgr on a workstation, and have it control the development Broker on your test machine. The Test broker on that machine is controlled by the test ConfigMgr on the same machine. This will also allow you to manage the security of the development environment in house, and allow the contractor to only install Control Centers on their machines. The only risk you then run of the development environment impacting the test environment is that the development broker will use up computing resources being used by the test broker.
My understanding is that licensing is done by where the broker is running, and not on ConfigMgrs or Control Centers - so that the configuration I talk about is all under the same single broker machine license. But you should verify this with your IBM sales rep. |
|
| Back to top |
|
|
| migerrits |
| Posted: Tue Jul 08, 2003 6:56 am Post subject: |
|
|
Apprentice
Joined: 13 Dec 2002
Posts: 35
Location: Canada
|
Thanks, Jeff! What you say is pretty much what I guessed, but it's good to have someone back up my thoughts.
-mike |
|
| 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
|
|
|
|
