Setting up load balancing for a cluster of Sametime Meeting Servers
Install a load balancer in front of a cluster of IBM® Sametime® Meeting servers to distribute connections among the servers. The cluster should have at least two IBM WebSphere® HTTP proxy servers deployed in front of it, so that the load balancer can direct connections to those proxy servers for forwarding to the individual Sametime servers in the cluster.
About this task
If you do not want to use IBM Load Balancer, any load balancing mechanism that supports HTTP load balancing with session affinity can be used with a Sametime Meeting Room cluster.
By default, load balancers will route HTTP requests between the cluster members, so that a single client may be routed to different cluster members for subsequent requests rather than continuing to be routed to the same cluster member. Since a client typically accesses an online meeting every 30-40 seconds during the session, enable server affinity or "sticky time" for a Sametime cluster so that the client continues to access the same server during a single meeting.
IBM recommends a "sticky" time configuration of 60 seconds for a Sametime cluster.