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.

Considerations for configuring load balancers with AR System servers

The load balancer acts like a NAT device that routes any TCP or UDP traffic. Since the AR System server uses an ONC-RPC implementation that is layered on top of TCP/IP, AR System server traffic can be load balanced. Because of the nature of the client/server interaction within BMC Remedy AR System, setting the sticky bit is not required. While the sticky bit allows for the spreading of the workload from multiple clients, it does reduce the balancing that can occur.

For more information on common configuration examples for load balancers, see Load balancer configuration examples.

BMC Remedy AR System includes the capability for automatic fail-over of special operations and the sharing of floating licenses among the servers. Server groups are independent of load balancing, but the concepts are complementary.

To enable load balancing across multiple AR System servers, configure each server as outlined in Configuring AR System servers.

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.