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® Bandwidth Managers
Deploy and cluster IBM® Sametime® Bandwidth Manager servers using IBM WebSphere Application Server 7.
Setting up a WebSphere® SIP proxy server for the Bandwidth Manager cluster
To perform routing and caching tasks for an IBM® Sametime® Bandwidth Manager cluster, install IBM WebSphere® Application Server on an additional secondary node, federate it to the cell, and then configure that node for use as a WebSphere SIP proxy server.
Federating a node into the Bandwidth Manager cell
Adding each new node to the IBM® Sametime® Bandwidth Manager cell allows you to administer the cluster from the Deployment Manager's Integrated Solutions Console. You will not be able to log in to a node's Integrated Solutions Console after federating the node to a cluster.

Federating a node into the Bandwidth Manager cell

Adding each new node to the IBM® Sametime® Bandwidth Manager cell allows you to administer the cluster from the Deployment Manager's Integrated Solutions Console. You will not be able to log in to a node's Integrated Solutions Console after federating the node to a cluster.