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.
Setting up a WebSphere® proxy server for the cluster
Set up an IBM® WebSphere® proxy server for use with a cluster of IBM Sametime® servers. The proxy server can be hosted on a product node, or on a separate computer; it performs routing and caching tasks for the servers in the cluster.
Reconfiguring ports for a WebSphere® proxy server hosted on a product node
If the IBM® WebSphere® proxy server is hosted on the same computer as an IBM Sametime® product, reconfigure ports to avoid a conflict.

Reconfiguring ports for a WebSphere proxy server hosted on a product node

If the IBM® WebSphere® proxy server is hosted on the same computer as an IBM Sametime® product, reconfigure ports to avoid a conflict.

About this task

There are two possible deployment scenarios when changing these port settings.

One, the Sametime SIP Proxy/Registrar and the WebSphere SIP Proxy reside on different servers and both use the same SIP ports, for example, non-secure port 5080 and secure port 5081.
Two, the SIP Proxy/Registrar and the WebSphere SIP Proxy reside on the same server. In this case, the WebSphere SIP Proxy is using one set of SIP ports, for example, non-secure port 5080 and secure port 5081. The SIP Proxy Registrar is using another set of ports, for example, non-secure port 5082 and secure port 5083.