This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Configuring a load balancer with a firewall, web servers, a second load balancer, and multiple AR System servers

In this example, client requests pass through a firewall and into a load balancer. The first load balancer directs web requests to the web servers. Web server requests to the BMC Remedy AR System servers are directed through a second load balancer. The three servers share a single database, as shown in the following figure.

Load-balancer configuration with a firewall, web servers, AR System servers, and two load balancers

(Click the image to expand it.)

Notes

For versions 7.6.04 or later, BMC recommends configuring the load balancer that is located between the web servers and BMC Remedy AR System servers without setting a sticky bit. In versions earlier than 7.6.04, BMC recommended setting the sticky bit to activate session affinity to route all connections from one web server to the same BMC Remedy AR System server. For more information, see Scenarios for load balancing between the web servers and BMC Remedy AR System servers.

If you use other BMC products that also support load balancing without setting the "sticky" bit, make sure your BMC Remedy AR System server and other BMC product(s) use the same version. For example, BMC Atrium CMDB supports configuring the load balancer without setting a "sticky" bit for version 7.6.04 Service Pack 1 or later, and does not support it for version 7.6.04. If you configure load balancing without setting a "sticky" bit for both of these products, your AR System server must also use the matching 7.6.04 SP1 or later version.


This type of configuration can also be used with a WAN, DMZ, or LAN as shown in the following figure. Client requests pass through the firewall and into the first load balancer. The load balancer routes the traffic to one of the web servers. BMC Remedy AR System requests from the web servers pass through the first load balancer, then through the firewall, and finally to the second load balancer. The second load balancer then routes the request to one of the BMC Remedy AR System servers in the group.

Load-balancer configuration with a WAN, a firewall, web servers, AR System servers, and two load balancers

(Click the image to expand it.)



For better throughput, such as might be required in a high-performance environment, you can add a second firewall, as shown in the following figure. AR System server traffic from the web servers is routed through the second firewall. AR System server traffic from web servers follows a different route from that of incoming BMC Remedy AR System client requests, thereby reducing the likelihood of a network bottleneck in the load balancer.

Load-balancer configuration with a WAN, two firewalls, web servers, AR System servers, and two load balancers

(Click the image to expand it.)

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments