This documentation supports the 9.0 version of Remedy Action Request System.

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

What a load balancer does

A load balancer is a transparent network device that distributes the traffic from multiple clients to several servers, preventing BMC Remedy AR System servers from becoming overloaded. Distributing workload among several BMC Remedy AR System servers can lead to performance benefits and cost savings. Buying many smaller machines is far less expensive than paying for a single high-performance machine. Since load balancers redirect incoming traffic, they are sometimes referred to as redirectors.

A load balancer also provides high availability through redundancy and fail-over protection. Fail-over is the process of moving operations from one server to another upon service or machine failure. If one BMC Remedy AR System server becomes unavailable for software reasons or if the machine hardware fails, other BMC Remedy AR System servers in the group (or cluster) can take over the workload. Users will not be aware of any problems, nor will they experience any downtime.

Most load balancers work on the TCP level of the network protocol and can therefore balance the load of many applications that use this protocol. Some examples include HTTP, FTP, and the BMC Remedy AR System server. The load balancer is transparent to users, so the client application cannot see it and is unaware that the client requests are being load-balanced.

You can think of the load balancer as a virtual system, or as a super BMC Remedy AR System server in this case. The load balancer is given a virtual IP address and a DNS name, either of which is used by BMC Remedy Mid Tier clients when connecting to the group of load-balanced BMC Remedy AR System servers. Both the short and long DNS names must be resolvable. (Long DNS names are fully qualified with a domain.) When a client request is received, the load balancer passes the request to one of the actual BMC Remedy AR System servers within the group. The chosen BMC Remedy AR System server performs the work and sends the results to the client. This balancing of connections spreads out the client requests evenly and distributes the load.

Note

For performance reasons, the BMC Remedy AR System API clients establish a connection with the BMC Remedy AR System server and keep the connection until the session is terminated or the connection is interrupted.

Was this page helpful? Yes No Submitting... Thank you

Comments