| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to be cheap and safe: 2 QMs on 1 Server |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Jun 05, 2003 7:07 am Post subject: How to be cheap and safe: 2 QMs on 1 Server |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If I have a WIN2000 server that I want to install 2 Queue managers on (1 for DEV testing and 1 for QA testing), what are the things I can do to make the possibility of one environment effecting the other one as slim as possible?
I plan on having the C drive used for O/S stuff, the E drive will be for DEV and the F drive will be for QA.
I know I can easily choose what the log paths should be at QM creation time, so I can keep QA and DEV logs separate. But what about all the other files? At install time, you have to choose where to keep all this stuff, so the DEV and QA files would all be on the same drive. Is this an issue? Any way to separate them?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mcruse |
| Posted: Thu Jun 05, 2003 11:49 pm Post subject: |
|
|
Novice
Joined: 15 Apr 2002
Posts: 13
Location: Germany
|
Both queue managers will use the same PGMFOLDER, DATFOLDER and LOGFOLDER. The information about this is not stored in a qm.ini it is stored in the registry 
And there is much more stored (status ...) than in the qm.ini
And last but not least there is only one service "IBM MQSeries".
In case of this I think it will be impossible for you to run two independet queue managers on one server.
wkr
Markus |
|
| Back to top |
|
|
| interactivechannel |
| Posted: Fri Jun 06, 2003 12:13 am Post subject: |
|
|
Voyager
Joined: 20 May 2003
Posts: 94
Location: uk
|
| Have a look in the System Administration Guide. Modifying DefaultPrefix=directory_name will allow you to put the queue manager data where you want. |
|
| Back to top |
|
|
| Tibor |
| Posted: Fri Jun 06, 2003 12:20 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Markus,
Sorry, but there is a lot of bad info in your letter:
| Quote: |
| Both queue managers will use the same PGMFOLDER, DATFOLDER and LOGFOLDER. The information about this is not stored in a qm.ini it is stored in the registry |
All qmgrs folder may be in different folder, because this is stored in registry! OK, code base is common, but this is not problematic, just look an RDBMS.
| Quote: |
| And last but not least there is only one service "IBM MQSeries". |
This service name "IBM MQSeries" is not a queue manager process, only a frame application to handle all queue manager instance. Each queue manager can start / stop independently others.
You may confuse this solution with e.g. an Oracle instance - it's define separate service for all database.
| Quote: |
| In case of this I think it will be impossible for you to run two independet queue managers on one server. |
We are using on Win-based box to run multiple queue managers without any problem.
Tibor |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jun 06, 2003 4:29 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Tibor,
I agree, we to have some servers with multiple queue managers running with absolutly no problems for a couple of years.
But this is the first time we will have queue managers that serve different test environments together. They are even considering only providing one server for DEV, QA and PRODUCTION. 
Now technically, I know its no big thing to have 3 testing environments on one server. I'll just define the channels in and out of the QMs correctly.
I am just worried that somehow the app in DEV can crash the DEV QM, and bring down QA and PROD with it.
I am looking for ways to minimize (eleiminate?) that possability.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jun 06, 2003 5:30 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
interactivechannel,
The tip you gave seems to apply to all QMs on the system (Unix only too). I am looking for a way on Windows to have QM1 on Server1 be on Drive E, and QM2 on Server2 be on Drive F.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jun 06, 2003 5:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
From an upgrade standpoint, I would be very very concerned about having production and test/uat run on the same machine. How can you test an upgrade without impacting production? I'm sure you know this, though.
From a more general point of view, I've been running TEST(integration testing, that is) and UAT queue managers on the same machine without jumping through any of the hoops that you are trying to do for a while now without any major issues. I don't know your client requirements, so I can't evaluate how important it is to them that UAT not get interrupted by test processing and vice versa. Normally, though, I don't expect you'll have problems even if you don't take the extra steps to put each QM on a different drive (to the extent that it's possible, that is).
Where you're more likely to run into apps running on test interferring with another queue manager on the same machine is if your apps are either resource intensive or running in trusted mode. If someone is running an app on the server in the test environment, and it goes into a loop that takes up all available memory on the machine... both environments are impacted. If all your apps are client apps (or at least developed to the point of being ready for integration testing as client apps), I don't think there will be problems.
If cost is a concern to your client, IBM tends to provide less expensive licensing for development environments than production environments. At least, that's been my experience. And financial cost for maintaining additional environments should always be weighed against potential business losses if an otherwise avoidable incident occurs that affects production. I'm sure you know that, but again I don't know your clients... 
Last edited by jefflowrey on Fri Jun 06, 2003 9:02 am; edited 1 time in total |
|
| Back to top |
|
|
| interactivechannel |
| Posted: Fri Jun 06, 2003 7:05 am Post subject: |
|
|
Voyager
Joined: 20 May 2003
Posts: 94
Location: uk
|
| The DefaultPrefix is only looked at when you create the queue manager, so set it to E: and create a queue manager, then set it to F: and create the other. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jun 06, 2003 8:11 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Does this also work on Windows?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jun 17, 2003 7:19 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
IBM says this can't work:
| Code: |
Action taken: Hello Peter, Even though you have 3 hard drives on a particular server,MQ can be onlyinstalled once. However, what you can do is to use MQ default prefix settings in the registry to specify a location of a que manager and the logs. Is there any particular reason that customer would like to have this configuration? Will this box be used for production later? Thanks, -IL03087 -5724B4100 - 03/06/09-21:37-
RESPOND ELECTRONICALLY:
They do not want to spend the money to provide a seperate server for PROD, QA and DEV. They want to have all 3 active queue managers running at the same time. I am looking for ways to minimize the risk of one QM effecting the other. Please expound on the "MQ default prefix setting in the registry" if this will accomplish what I am looking for. I looked in the System Admin Guide and found the following:
In WebSphere MQ for Windows, the default prefix is C:\Program\Files\IBM\WebSphere MQ. Use the WebSphere MQ Services snap-in if you want to change this. It is set on the All Queue Managers page of the WebSphere MQ properties. Would setting this before creating a QM force it and all its files to a particular drive on my server?
-IBM -5724B4100 - 03/06/10-11:39- -IBM -5724B4100 - 03/06/10-12:52- Action taken:
Hello Peter,
Please convey to customer that what they would like to do is really imposible because default prefix is pointing to a single location where all que managers will be defined. There are no means provided to specify default prefix for each que manager. The only thing that you can do is alter the default prefix to point to adifferent drive, but then only that particular environment will be accessable.Other two drives will have que managers (i.e. DEV and QA) that will not be accessable as default prefix will not be pointing to it. Please let me now if you have additional questions. Thanks, Yana -IL03087 -5724B4100 - 03/06/11-09:00- RESPOND ELECTRONICALLY:
So you are saying that not only does the default prefix tell MQ where to build a QM and all its files, but also tells MQ where to "run". In other words I could create QM1 on the C drive, change the default prefix to D:, and then create QM2, which would be built on the D drive. But the only QM that would work would be the QM that lives in the directory that the prefix is currently pointing to?
=PEARSON, TIFFANIE I. -5724B4100 - 03/06/11-13:29- =PEARSON, TIFFANIE I. -5724B4100 - 03/06/11-13:29- Action Taken: Update noted. Hi
Peter,
That is correct. Where MQDEFAULTPREFIX is pointing determines where MQ will run from. On startup, MQ reads the parameters in the mqs.ini & sets up according to what it finds there. In actuality, if you were to change the MQDEFAULTPREFIX after creating a qmgr, you would need to cycle the qmgr for the change to take effect before creating another qmgr. However, the qmgr that you created previously would then become inaccessible since the location had changed. Hope this helps. - Thanks, Tiffanie
|
_________________
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
|
|
|
|
