ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Load balancing message broker from Data Power

Post new topic  Reply to topic
 Load balancing message broker from Data Power « View previous topic :: View next topic » 
Author Message
touchofcrypticthunder
PostPosted: Wed May 23, 2012 10:23 am    Post subject: Load balancing message broker from Data Power Reply with quote

Apprentice

Joined: 08 Jul 2009
Posts: 30

Current Integration Architecture:
--------------------------------------
We have Message Broker(V7.0.0.3) in the integration layer which integrates Front End UI with backend SAP systems. Data Power is used as security gateway between UI and rest of the systems (Broker and SAP). We have 4 brokers in Prod which are load balanced from Data Power. All the messages flows (services) are deployed to SINGLE execution group in each production broker.

To summarize:

UI -> DP -> MB ->SAP -----
|
UI <- DP <- MB <- SAP <---

Changes planned:
---------------------
To make the Message Brokers more robust and HA, we are planning to distribute the message flows to multiple execution groups in each Broker server.

Challenges forecasted:
---------------------------
All the Message Broker integrations are webservice based, each message flow is using SOAP Input node. Now if we move message flows to different EG's, SOAP port is going to change which inturn affects the routing in Data Power. Initially we assumed that we can configure all the EG's to make use of Broker wide listener port as SOAP Port which would have very minimal changes to be done in Message Broker and Data Power routing would remain unaffected. But it turned out to be false. Only HTTP Nodes can make use of broker wide listener port and SOAP nodes are always binded to EG port which is different for different EG.

We have come up with following solutions:
1. Create wrapper flow for each Main message flow and these wrapper flows are deployed to SINGLE execution group where all the flows are deployed currently. These wrapper flows will route the requests to the actual message flows which will be distributed to other EG's. This requires NO changes in Data Power.

2. Create Load Balancer groups in Data Power for each Execution group and build the routing logic based on message flow service (WSDL) in Data Power.

Please provide your inputs and suggest best solution.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed May 23, 2012 10:33 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

For example, you could use the HTTP Proxy Servlet that comes with broker, deploy that to a container, and have DP access that instead of the EG listeners directly.

For example you could install IHS or Apache in a couple of locations and manually configure the http servers to do routing and loadbalancing.

For example you could configure one or more F5 switches to know how to route to the right EG listener based on the URL.
Back to top
View user's profile Send private message
mqxplorer
PostPosted: Fri Oct 14, 2016 12:45 pm    Post subject: Reply with quote

Master

Joined: 22 Jun 2009
Posts: 206

mqjeff wrote:
For example, you could use the HTTP Proxy Servlet that comes with broker, deploy that to a container, and have DP access that instead of the EG listeners directly.

For example you could install IHS or Apache in a couple of locations and manually configure the http servers to do routing and loadbalancing.

For example you could configure one or more F5 switches to know how to route to the right EG listener based on the URL.


I am trying to implement the load balancing option with DataPower between IIB servers ... It is the first example option above.

I was reading through the information center and found below text ..

Code:
In order that the HTTP proxy servlet can access the SOAPInput and SOAPReply nodes, you must enable the broker listener for each integration server where message flows with SOAP nodes are deployed.


http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac69420_.htm

If SOAP / HTTP nodes use EG/Integration server level ports (EmbeddedListener), we cannot use the DP option. Is that correct? Can't we use the DP option for Load balancing with HTTP Proxy servelet, if the SOAP/HTTP nodes use emebeded listener?

Thanks
mqxplorer
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Oct 14, 2016 9:33 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Please do not open a 4 year old thread.
We prefer that a new thread is opened and if needed, the old thread is referenced unless,.... you are running V7 like the original post indicated.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Load balancing message broker from Data Power
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.