Load balancer configuration examples

The following sections describe a number of common configuration examples. All configurations require that BMC Remedy AR System servers have been properly configured.

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

Verify that the following configuration steps have been completed before you review the examples:

1. All BMC Remedy AR System servers share the same database.
2. All BMC Remedy AR System servers have the same server name (server name alias), and they have a unique name configured for server-to-server communication.
3. All BMC Remedy AR System plug-ins are configured to access the local server.
4. All BMC Remedy AR System servers are configured to listen on TCP ports that the load balancer is configured for.
5. External operations managed by the server group (such as Email Engine and Flashboards) must be must be installed locally on the BMC Remedy AR System servers that manage them.
6. BMC Remedy Alert is configured for a load-balanced environment.
   • The load-balancer IP address is mapped to the BMC Remedy AR System server IP address.
   • The server is configured to ignore the actual IP address recorded during Alert client registration.
7. Distributed Server Option (DSO) is configured for a load-balanced environment.
   Mappings have been updated to take advantage of the server group.
8. Full text search (FTS) is configured for a load-balanced environment.
   The index collection directory is accessible to all BMC Remedy AR System servers in the group.
9. Clients are configured to use the virtual address and port of the load balancer.
10. Servers are declared to be server group members, and operation rankings are configured.