MQSeries.net :: View topic

dutchman · Posted: Mon Sep 24, 2001 10:46 am Post subject:

Dear all - I'm trying to work out a scheme that allows several development departments to share a common hardware kit in order to keep the number of licences (and hence capacity units) down. Currently, an MQSI project that is nearing completion has a number of Netfinity servers , one for each
environment , e.g.

development
integration testing
user testing
etc

Broker and ConfigMgr reside on different boxes.
A second project wants to come onboard using the same kit, but the first project is a little 'nervous' about that. I can only see these options available to us :

Opt1.Create a new broker with its own database (and new queue manager), on
the same machine.
Maybe use a unique userid?
Continue to use the existing Configuration Manager.
OR
Opt2. As per 1. but use a new Configuration Manager (with a new queue manager), which by definition requires a different Windows/NT machine as you can only have 1 ConfigMgr per box.
Fortunately, there are no MQSI licencing issues here.
OR
Opt3.Use the existing broker, and create unique execution groups for the second project (Don't like this one very much).

These are the issues I can see :
Iss1: It is inevitable that an 'increased' strain will be placed on the broker box, because more developers will be 'deploying' and more brokers are running.
Iss2: What about security? How do you stop the accidental/deliberate use of a message flow belonging to project 1 by project 2, and vice versa?
Iss3: By sharing kit, one 'rogue' application can affect all parties.

I look forward to hearing from people with
their solutions ... cheers ... Ruud