| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Design question of multiple channel vs multiple queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| mchan |
 Posted: Tue Oct 11, 2011 3:07 am Post subject: Design question of multiple channel vs multiple queue |
 |
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
I'm struggling with some basic design concepts regarding arrangement of MQ channel, Queue manager, etc.
In my system, If I want to have some priority handling for privileged users, would it be logical to create separate queue manager under the same machine only to serve those users?
i.e.
Privileged MQ client -> Privileged Queue Manager (Machine A) -> Privilege Server App.
Normal MQ client -> Normal Queue Manager (on same Machine A) -> Normal Server App.
I read somewhere, for performance consideration, it is best to design having only one queue manager per machine (though you can host a lot of queues in that queue manager).
Or, does it help if I just stay with 1 queue manager per machine, but having different channel to serve different type of clients
i.e.
Privileged MQ client -> Privileged Channel -> same Queue Manager (Machine A) -> Privilege Server App.
Normal MQ client -> Normal Channel -> same Queue Manager (Machine A) -> Normal Server App.
Thanks!  |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Tue Oct 11, 2011 3:41 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
message priority exist in mqseries. maybe 1 qmgr, 1 queue, 1 application and different message priority will do ?!?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 11, 2011 4:46 am Post subject: Re: Design question of multiple channel vs multiple queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mchan wrote: |
| I read somewhere, for performance consideration, it is best to design having only one queue manager per machine (though you can host a lot of queues in that queue manager). |
The basic fact is that by spinning up another queue manager, you spin up another set of processes and more i/o with another set of logs.
| mchan wrote: |
| Or, does it help if I just stay with 1 queue manager per machine, but having different channel to serve different type of clients |
This only helps if the issue is the network and you have 2 routes to the queue manager. Otherwise the messages from both clients are stuck in the same TCP/IP stack & you're no further forward.
As my most worthy associate points out you can use message priority to get "priveldged" messages to the top of the queue. Or have 2 queues, the normal service queue having n instances of the app running against it, the privledged one having n+1 instances to ensure the messages move quickly.
In this 2nd case having 2 client channels will offer benefits; you can set the MCAUser of the normal channel to a user that can't put messages to the priority queue and stop the app "cheating". Likewise you can stop the normal app sneaking onto the priority channel.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mchan |
| Posted: Tue Oct 18, 2011 2:02 am Post subject: |
|
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
Thanks so much for your insight.
May I also ask if there is any point in having multiple listener for same queue manager from security and performance point of view..... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 18, 2011 2:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mchan wrote: |
Thanks so much for your insight.
May I also ask if there is any point in having multiple listener for same queue manager from security and performance point of view..... |
Not from those perspectives, no, at least not in v7.0.x and earlier. There may be some security advantages in v7.1 - *may*, I am not sure.
The main reason to have multiple listeners for a given qmr is to expose that qmgr on multiple addresses - unique ip/port combinations, multiple network protocols (Tcp, sna, etc...).
So you might choose to have a unique listener for an edge qmgr that is open to multiple business partners - with each listener assigned to each partner. Then you could manage traffic to each without interfering with the other.
But it's not going to make a difference to security or to performance. |
|
| 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
|
|
|
|
