| Author |
Message
|
| kriersd |
 Posted: Wed May 04, 2005 10:02 am Post subject: Single Tier Setup |
 |
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Folks,
I am looking at setting up a single tier environment, and I have some general questions. Most of the configurations I setup are multi tier configuratioins, however, I now need to setup a production worthy single tier configurations.
First off, I believe we will get better performance if we intall two seperate queue managers even on the same physical box. One for the WAS web client and one for the Workflow server. I think this will provide better performance as opposed to one queue manager. Does anyone have any thoughts on this subject?
Next, Disk IO has always been an issue. Does anyone have a fool proof disk layout for a single tier setup with 2 disks.
Thanks 
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
 |
| Ratan |
| Posted: Wed May 04, 2005 10:20 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
First off, I believe we will get better performance if we intall two seperate queue managers even on the same physical box. One for the WAS web client and one for the Workflow server. I think this will provide better performance as opposed to one queue manager. Does anyone have any thoughts on this subject?
|
I dont think you will get any performance gain by using seperate QM for WebClient. It is a best practice to have a different QM.
_________________
-Ratan |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed May 04, 2005 11:57 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
So, what your saying is that you don't think there will be any performance gain with seperate queue managers, but it's best practice to do that anyway?
I just want to make sure I understand what your saying..
Thanks for the help.
Kriersd
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed May 04, 2005 12:00 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Yes, it is a best practice because you can manipulate your Clients QM with out affecting WF Server's QM.
Performance wise, it should be a little slower with seperate QM. negligible though.
_________________
-Ratan |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed May 04, 2005 12:48 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Thanks for the help..
Kriersd.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| koko |
| Posted: Thu May 05, 2005 1:50 pm Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
kriersd,
I had the same question some time back. I even went to IBM to give me direction. They pretty much said the same thing that Ratan is saying.
It is a best practise to seperate out the QM on which WAS connects to WF. In our case we had WAS. WF running on same physical box. Just in case we see some performance problems I wanted to seperate out WAS from WF.
I might not have added anything extra but I have IBM confirmation 
_________________
Thanks
Koko |
|
| Back to top |
|
|
| kriersd |
| Posted: Mon May 09, 2005 8:26 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Thanks guys..
I will proceed with multiple queue managers. 
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
