| Administering the Platform / Operations Cookbook | |
In order to integrate the Jive platform with an external load balancer, configure the load balancer for cookie-based session affinity between each host running the platform. (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 a Load Balancer. You may also wish to configure SSL encryption between the load balancer and each web application node. See Configuring SSL Between a Load Balancer and Web App Nodes for more information.
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.