r4 - 2019-01-11 - 13:48:20 - ShubjitNaikYou are here: TWiki > 
Deployment Web > DeploymentInstallingUpgradingAndMigrating > InstallProxyServers > CompareProxyServers
Deployment Web > DeploymentInstallingUpgradingAndMigrating > InstallProxyServers > CompareProxyServers What Reverse Proxy Server and Load Balancer to Use? 
Authors: ShubjitNaik, DineshKumar, JimRuehlin Build basis: CLM 6.0.6
Page contents
This article will focus on the benefits and limitations of different Reverse Proxy Servers and Load Balancers supported by IBM Collaborative Lifecycle Management and Continuous Engineering Solutions.
For more Information visit Understanding Reverse Proxy The only supported and tested Reverse Proxy server with CLM and CE Deployment is : However, we have customers who have worked with other Proxy Servers for CLM and CE Deployment and we have listed them below :
Load balancer is a requirement for a clustered setup where there are multiple instances of the same application is running connecting to the same database. Currently for version 6.0.6 and the only application that can be setup as a cluster is Rational Team Concert. If you do not use Rational Team Concert you would not be needing a Load balancer.
The supported and tested Load Balancers with Rational Team Concert Clustered Setup are:
The following tables lists the key differences between IHS and HAProxy
Reverse Proxy
A Reverse Proxy is a gateway for servers, and enables one web server to provide content from other servers transparently. It can redirect the traffic to specific applications based on the configuration related to the context root in the URL. Example /ccm, /rm etc. For a distributed deployment, where each application from the stack within the CLM/CE deployment is deployed on its own server, to maintain a single Public URL and hide the underlying deployment you should use a Reverse proxy server.For more Information visit Understanding Reverse Proxy The only supported and tested Reverse Proxy server with CLM and CE Deployment is : However, we have customers who have worked with other Proxy Servers for CLM and CE Deployment and we have listed them below :
Load Balancer
A Web server that takes cares of redirecting and balancing incoming traffic, based on configured algorithms, between different nodes in a Clustered Setup.Load balancer is a requirement for a clustered setup where there are multiple instances of the same application is running connecting to the same database. Currently for version 6.0.6 and the only application that can be setup as a cluster is Rational Team Concert. If you do not use Rational Team Concert you would not be needing a Load balancer.
The supported and tested Load Balancers with Rational Team Concert Clustered Setup are:
The following tables lists the key differences between IHS and HAProxy
| As a Reverse Proxy | Supported and Tested - The major advantage of using IBM HTTP Server is that a single server can be used as a Reverse Proxy and as the Load Balancer |
Not Supported or Tested with Jazz deployment |
| IBM HTTP SERVER | HAPROXY | |
|---|---|---|
| Support | IBM Support | Forum Support (Community Edition) |
| Operating Systems | Can be installed on Windows, Linux and AIX Platforms | Can be installed on Linux Platforms Only |
| CLM Versions | CLM/CE 6.0.5 Onwards | CLM/CE 6.0.4 Onwards |
| Load Balancing | The following Load Balancing Policies are support by IHS, The default load balancing type is Round Robin. Round Robin - The Round Robin implementation has a random starting point. The first application server is picked randomly. Round Robin is then used to pick application servers from that point forward. This implementation ensures that in multiple process-based web servers, all of the processes do not start by sending the first request to the same Application Server. Random The Random implementation also has a random starting point. However with this implementation all subsequent servers are also randomly selected. Therefore, the same server might get selected repeatedly while other servers remain idle. |
HAProxy supports a rich set of Load Balancing algorithms other than Round Robin and the default is Leastconn. Following are a few examples: Leastconn - The server with the lowest number of connections receives the connection. Round-robin is performed within groups of servers of the same load to ensure that all servers will be used. This algorithm is dynamic, which means that server weights may be adjusted on the fly for slow starts for instance. Source -The source IP address is hashed and divided by the total weight of the running servers to designate which server will receive the request. This ensures that the same client IP address will always reach the same server as long as no server goes down or up. This algorithm is static by default, which means that changing a server's weight on the fly will have no effect, but this can be changed using "hash-type". |
| High Availability | YES | YES |
| Monitoring | External Tools can be used | Statistics Reports is Bundled with HAProxy UI. External Tools can be used as well |
Related topics: Deployment web home, Installing Proxy Servers
External links:
-
Deployment web
-
Planning and design
- Installing and upgrading
- Migrating and evolving
- Integrating
- Administering
- Monitoring
- Troubleshooting
Community information and contribution guidelines 
Topic list 
Search 
Advanced search 
Notify 
RSS 
Atom 
Changes 
Statistics 
Web preferences 
NOTE: Please use the Sandbox web for testing - To do
-
Under construction
-
New
-
Updated
-
Constant change
- None - stable page
- Smaller versions of status icons for inline text:
-
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.