Using external load balancer

In order to integrate the Jive platform with an external load balancer, you configure the load balancer for cookie-based session affinity between each host running the platform.

For more information on setting up cookie-based session affinity, see Configuring session affinity on load balancer. Note that all Jive's testing of load balancers is cookie-based. As of Jive 7, the load balancer is required to perform SSL session termination as described in Configuring SSL on load balancer. You may also wish to configure SSL encryption between the load balancer and each web application node. For more information, see Configuring SSL Between a Load Balancer and Web App Nodes.

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 more information about using Apache HTTPD as a load balancer, see Apache's documentation about load balancer stickiness at http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html#stickyness_implementation. For more information on how to configure the route name (jvmRoute variable) of your nodes in Jive, see Configuring JVM route name of nodes.

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 !

For more information about Apache's ProxyPass and how it works, see Apache Module mod_proxy at http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass.