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 SIP Proxy/Registrars
Configuring a cluster of Sametime® Media Manager SIP Proxy/Registrars involves several tasks, including synchronizing system clocks, configuring one or more WebSphere® proxy server to operate with the cluster.
Restarting and synchronizing the SIP Proxy/Registrar cluster
Complete the configuration for clustering Sametime® Media Manager SIP Proxy/Registrars using a WebSphere® Application Server network deployment by restarting and synchronizing nodes in the cluster and restarting the application servers in the cluster.

Restarting and synchronizing the SIP Proxy/Registrar cluster

Complete the configuration for clustering Sametime® Media Manager SIP Proxy/Registrars using a WebSphere® Application Server network deployment by restarting and synchronizing nodes in the cluster and restarting the application servers in the cluster.

Restarting and synchronizing the SIP Proxy/Registrar cluster

Before you begin

About this task

Procedure