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.
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 Conference Manager node
If the IBM® WebSphere® proxy server is hosted on the same computer as an IBM Sametime® Conference Manager, reconfigure ports to avoid a conflict.
Verifying that the port collision has been resolved
After resolving port collisions between IBM® WebSphere® proxy server and IBM Sametime®, verify that the port settings are now correct.

Verifying that the port collision has been resolved

After resolving port collisions between IBM® WebSphere® proxy server and IBM Sametime®, verify that the port settings are now correct.

About this task

Start the servers in the cluster; clear the WebSphere proxy server's logs before starting that server, and then check the logs for errors that may indicate a port collision.

Procedure

Start all of the servers and processes in the cluster except for the WebSphere proxy server where you just resolved the ports conflict.
Clear all of the WebSphere proxy server logs.
Start the WebSphere proxy server.
Check the WebSphere proxy server log for any errors indicating a possible port collision; for example:
- ADMU3028I
- TCPC0003E
- The port may already be in use

What to do next

If other nodes in the cluster have both Sametime and WebSphere proxy server, be sure to check those nodes for possible port conflicts as well before continuing proceeding to the next task.