In order to integrate the Jive SBS platform with external load balancers, configure the load balancer for session affinity between each host running the platform. If the load balancer is performing SSL session termination (recommended), the load balancer should be configured to route traffic to port 80 each Jive managed server. If the load balancer is not performing SSL session termination, the load balancer should be configured to route traffic to port 443 and each server configured for SSL as described in the above cookbook recipe.
Depending on the load balancer, it may be necessary to add JVM route information to the outgoing JSESSIONID HTTP cookies sent to remote agents. In this case, add a jvmRoute attribute to the Engine element of the server.xml file located in the application’s conf directory (/usr/local/jive/applications/sbs/conf/server.xml by default). For example, to name the route “r1”, the server.xml Engine element would read:
<Engine defaultHost="localhost" name="Catalina" jvmRoute="r1">
When configuring multiple nodes with jvmRoute attributes, each node should have a different value.