| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Server as client ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| objectthinker06 |
 Posted: Mon Mar 29, 2010 12:16 pm Post subject: MQ Server as client ? |
 |
|
Novice
Joined: 15 Aug 2006
Posts: 15
|
We have two Linux systems that have MQ Server software installed on 'em , say: system A and system B. Each system can have its own Queue Manager. However, it is preferred to have system A connect to system B in MQ Client mode. Is this possible?If so, how can this be done? The idea is to use h/w load balancer to load balance connections from system A to system B server when connected in client mode. Also note that the JMS program that drops messages on system A cannot connect to system B straight due to legal issues.
Thanks, |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 29, 2010 1:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Any JMS app can connect to any queue manager via client irrespective of which queue manager (if any) is installed on the local system. It's simply a question of defining the connection target appropriately.
Likewise if you want your JMS to connect to system A and the messages to be forwarded to system B that's a configuration issue.
I don't understand how you plan to use a load balancer, or why you think it will work (or help).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| objectthinker06 |
| Posted: Mon Mar 29, 2010 3:30 pm Post subject: |
|
|
Novice
Joined: 15 Aug 2006
Posts: 15
|
| Well the application that connects to MQ system A is really an appliance - data power. However, MQ system A if connected in client mode to system B, then they can be load balanced through a h/w load balancer. The alternative to client mode is to create sender/receiver channels and cluster the queue managers on system A and system B for work load balancing which is not preferred. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 29, 2010 3:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| objectthinker06 wrote: |
| The alternative to client mode is to create sender/receiver channels and cluster the queue managers on system A and system B for work load balancing which is not preferred. |
Queue managers only connect to each other via sender/receiver channels or server/requester channels, cluster sender/receiver, etc, etc but don't establish client connections to each other.
Note that WMQ channels don't work well (or at all) through a hardware load balancer.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Mar 29, 2010 4:20 pm Post subject: Re: MQ Server as client ? |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| objectthinker06 wrote: |
| The idea is to use h/w load balancer to load balance connections from system A to system B server when connected in client mode. |
I don't get it. Load balancing is choosing between multiple destinations, not a single destination.
Maybe the load balancing you need can be found in Queue Manager Clusters. Check out the manual devoted to that subject (links at top of this page).
"Client mode" refers to how an application connects to a qmgr. It helps to talk about applications, queues and queue managers rather than "systems". I think it's the mention of abstract "systems" that could be the cause of some confusion here. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 29, 2010 7:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| objectthinker06 wrote: |
| Well the application that connects to MQ system A is really an appliance - data power. However, MQ system A if connected in client mode to system B, then they can be load balanced through a h/w load balancer. The alternative to client mode is to create sender/receiver channels and cluster the queue managers on system A and system B for work load balancing which is not preferred. |
Let me remind you that sometimes there is reasons to not use load balancing... It seems that here you have 2 qmgr A and B and a Data Power appliance C. A and B are standalone qmgrs and you would like to load balance the connections from C to A and B. A and B essentially have the same role and process against a request / reply model.
This is feasible. Remember however that you should probably use a V7 channel table for load balancing instead of some additional hardware as MQ usually does not like HW load balancing...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 30, 2010 6:03 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| However, it is preferred to have system A connect to system B in MQ Client mode. |
I suppose it might be worth an attemtp at clarity here.
Queue managers don't connect to other queue managers. The queue manager doesn't care which channels go where, and has little/no direct involvement in channel activity. Rather, message channels interconnect two queue maangers. This last sentence sounds like splitting a hair (or hare), doesn't it? Read on.
Message channel agents (MCAs) connect to their counterpart MCA on the other end of a channel. This holds true for both point-to-point channels and client channels.
MCAs, as the name implies, act as agents for applications and the messages the applications create.
On the sending end of a channel, QRemote definitions resolve to a transmission queue. This transmission queue is monitored by the sending MCA, which transmits the messages to the MCA on the receiving end MCA.
The receiving end MCA, acting as an agent for the application and originating user), puts the message in the appropriate destination queue (or DLQ).
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
