|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
HTTP Topology for Broker |
« View previous topic :: View next topic » |
Author |
Message
|
vaishnav.piyush |
Posted: Tue Jan 29, 2013 4:53 am Post subject: HTTP Topology for Broker |
|
|
 Novice
Joined: 16 Mar 2009 Posts: 14
|
Hi
We are designing the HTTP Topology for our Message Brokers (v8.0.0.0, likely to upgraded to 8.0.0.1). These are two identical brokers meant to be used for load balancing.
I have been reading matter on the internet and I now need a clear understanding on two main architectural decision that we must make.
1. Broker Wide Port or Execution Group Embedded Port ?
Is it beneficial to use Broker wide http port (for both HTTP and SOAP over HTTP) or Execution Group embedded port ? Does it impact performance if we use Broker wide port. For instance, if a particular web-service listening on broker wide port is slow, will it impact all other web services listening on that port ?
2. Whether to use an external web-server ?
Since we intend to have two load balanced brokers, we can use the external web-server for load balancing as well. In this case, can we use EG embedded ports also ?
We also have the option to use internal web-container of broker along with a load balancer like F5.
I am looking for some suggestions based on experience that we have in this forum. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Jan 29, 2013 5:38 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
1. Execution Group Embedded Port
2. http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbe55180_.htm
Quote: |
WebSphere® Message Broker is frequently a component in Service Oriented Architecture (SOA) patterns that include external web servers and other HTTP solutions. Learn about the facilities that WebSphere Message Broker provides to help you to configure your web server infrastructure, and which configuration option best fits your existing topology.
The following diagram shows a web server topology that uses a web server plug-in generated in WebSphere Application Server to handle HTTP and HTTPS connections with an application server. The web clients use HTTPS to communicate with the web server, and the WebSphere Application Server plug-in forwards traffic over HTTP to one of two application servers. This topology provides simplified administration: the clients connect to a single endpoint, and all client security is handled in a single place. The plug-in can be used to handle load-balancing and failover between the two application servers. |
The InfoCentre is a very useful place to acquire knowledge. Training also is someplace you can learn neat stuff. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
vaishnav.piyush |
Posted: Tue Jan 29, 2013 6:23 am Post subject: |
|
|
 Novice
Joined: 16 Mar 2009 Posts: 14
|
lancelotlinc wrote: |
1. Execution Group Embedded Port
|
What is the reason you recommend EG embedded port ? Have you observed performance problems or any other issues ?
Yes I have gone through this and other matter available in Infocenter. It talks about how to use external web-server, but nowhere it talks about why external web-server should be used.
This topic is grouped under "Configuring for High Availability". One can even achieve this using a load balancer like F5. We have a load balancer available in the landscape. Do we still need a web-server ?
On another note, can we use Execution Group embedded ports with external web server. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Jan 29, 2013 6:29 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
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
|
|
|
|