Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Clustering servers for high availability and failover
You can provide failover and load balancing in your deployment by creating a cluster of multiple IBM® Sametime® servers of the same type. All Sametime servers can be clustered except for the Sametime System Console, and the Video MCU and TURN Server components of the Sametime Media Manager.
Clustering Sametime® Media Manager components
The IBM® Sametime® Media Manager includes several components. You can install the components separately and optionally cluster some of them.
Clustering Conference Manager components
Configuring a cluster of IBM® Sametime® Media Manager "Conference Manager" components involves several tasks, including synchronizing system clocks, configuring one or more WebSphere® proxy servers to operate with the cluster.
Configuring WebSphere® proxy server for load balancing in a SIP Proxy/Registrar cluster
To best support high availability and provide fail over services, a cluster of IBM® Sametime® Media Manager servers should be fronted with at least two IBM WebSphere® proxy servers and IBM Load Balancer.
Load balancing with IP forwarding
Configure the IBM® WebSphere® SIP proxy server that fronts the Sametime® Media Manger in an IP forwarding load balancing environment.

Load balancing with IP forwarding

Configure the IBM® WebSphere® SIP proxy server that fronts the Sametime® Media Manger in an IP forwarding load balancing environment.