Configuring a hardware load balancer with AR System

A hardware load balancer can improve the scalability and availability of AR System. A 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 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.

Related topics

Load-balancers-in-BMC-Helix-Innovation-Suite

Best practice
If an escalation or archive operation results in a fail-over from one server to another, escalations or archives running at a fixed time might be skipped or might run twice. An escalation or archive activity might be skipped if it is scheduled to run while the operation is making the transition from one server to another. An escalation or archive activity might be skipped or run twice if the system clocks on the relevant systems are skewed—that is, if the clock settings differ enough to cause a fixed time to be missed or encountered twice.

See the following topics for more information about configuring a load balancer:

Action

Reference

Understand how load balancing works in a containerized environment to provide a high-available infrastructure.

Understand how to configure a load balancer with an example of configuring an F5 load balancer.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*