Configuring Session Affinity on a Load Balancer

Jive requires session affinity to be configured on your load balancer.

Session affinity on the load balancer is required. For an F5 BigIP load balancer, you can simply use a default cookie persistence profile. See the recommended F5 settings elsewhere in the documentation. If you have another type of load balancer, which doesn't create its own cookies for session affinity, you can use the JSESSIONID cookie that Jive sets. See the Apache HTTPD documentation for examples.

To configure session affinity:

Set a route string for each balancer member in your load balancer configuration. For example, use the string node01 in the balancer pool configuration for myapp-wa01.internal.mycompany.com.
Set the corresponding startup property on that web application node. If you used the route string node01, you might set:
jive set webapp.app_cluster_jvmroute node01
Follow the same pattern for your other web application nodes.
Restart the web application on all the web application nodes.