Using an External Load Balancer

In order to integrate the Jive platform with external load balancers, configure the load balancer for cookie-based session affinity between each host running the platform. (All of the testing performed by Jive Software of load balancers is cookie-based.) If the load balancer is performing SSL session termination (recommended), configure the load balancer to route traffic to port 80 of each Jive-managed server. If the load balancer is not performing SSL session termination, configure the load balancer to route traffic to port 443 and each server configured for SSL as described in Enabling SSL Encryption.

Depending on the load balancer, it may be necessary to add JVM route information to the outgoing JSESSIONID HTTP cookies sent to remote agents. For information about using Apache HTTPD as a load balancer, see Apache's documentation about load balancer stickyness. To understand how to configure the route name (jvmRoute variable) of your node(s) in Jive, see the "Configuring the Route Name of a Node(s)" section of Changing the Configuration of an Existing Instance.

Some load balancers require a "magic" HTML file in the site root to make the node available. If your load balancer requires this, add the following line to this default configuration file /usr/local/jive/etc/httpd/sites/default.conf:

ProxyPass /magicfile.html !

To learn more about Apache's ProxyPass and how it works, see their documentation.