Author |
Message
|
broker_new |
Posted: Wed Oct 03, 2012 7:38 am Post subject: WMBv8.0.0.1-> WebServices Load Balancing |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Hi Guys,
We have designed the new Broker environment to be highly available using Multi Instance Queue Manager and Message Broker.
1. WebSphere MQ 7.5
2. WebSphere Message Broker 8001
========================
Node A | Node B |
========================
-BrokerA | - BrokerB |
---- EGA(7100) | ----EGB(7200)|
1)How would we really load balance the web services across these two active brokers BrokerA and BrokerB.
2)If we have a native load balancing mechanism in message broker....If we failover BrokerA to NodeB..which means the BrokerA and BrokerB running on the NodeB..how will the load balancing works?
Any inputs from the Experts?
 _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Oct 03, 2012 7:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
McueMart |
Posted: Wed Oct 03, 2012 8:25 am Post subject: |
|
|
 Chevalier
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
|
mqjeff - I think your links answer question 1), but im also not 100% sure how question 2) should be solved.
As the OP mentions, if Broker A fails over to Node B, you will now have Broker A & B (listening on ports 7100 & 7200 respectively), running on Node B.
You HTTP load balancer (mod_proxy whatever) will detect that port 7100 on Node A is no longer working, but how will it know to now start balancing between 7100 & 7200 on Node B?
Please enlighten! |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Oct 03, 2012 8:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
In theory you would simply say that all Broker A flows can live at two addresses(machine 1 & 2), and then the load balancer would spray them to whatever location was active.
I *expect* that the new function in FP1 of v8 (the second link) is MI aware at that level, and I am *hopeful* that the proxy servlet is. |
|
Back to top |
|
 |
broker_new |
Posted: Wed Oct 03, 2012 10:06 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
looks interesting...so we are relying on an application/web server to provide load balancing of the web services...what happens if there is any maintenance planned for the app/web server...aren't we inserting one more point of failure? _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Oct 03, 2012 10:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Again, the load balancer should mostly be aware of which address for each broker is currently available (or unavailable) and only balance traffic between active locations. This is in the same way that you might have five WAS application servers but only three of them running currently, it would know not to try the dead ones.
*SHOULD* to the best of my knowledge, but I've not tested nor solidly reviewed the docs. |
|
Back to top |
|
 |
NealM |
Posted: Wed Oct 03, 2012 10:41 am Post subject: |
|
|
 Master
Joined: 22 Feb 2011 Posts: 230 Location: NC or Utah (depends)
|
...or instead of a bunch of WAS servers, you could opt for one nice reliable DataPower appliance to do your load balancing.... |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Oct 03, 2012 10:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
NealM wrote: |
...or instead of a bunch of WAS servers, you could opt for one nice reliable DataPower appliance to do your load balancing.... |
I wasn't advocating the use of a bunch of was servers. I was using a bunch of was servers as an analogy.
The proxyservlet does require a bunch of was servers - but that's why I don't like it very much. It's much cleaner to just have a couple of HTTP servers and a network loadbalancer in front of those. |
|
Back to top |
|
 |
broker_new |
Posted: Wed Oct 03, 2012 12:18 pm Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
ok..As per my understanding there is nothing in built in Message Broker to handle within the product itself.
We have to rely on the HTTP Servers or an network load balancer to handle this. I will open a requirement to add this feature in upcoming releases. _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
|