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.
Deploying IP routing load balancers
Install an IP routing load balancer according to the product instructions.
Using the TLS protocol with IP routing load balancing
Complete the configuration to run TLS SIP traffic through IP routing load balancing.
Routing TLS SIP traffic through an IP routing Load Balancer
To run TLS SIP traffic through an IP routing Load Balancer, first enable SNAT (Secure Network Address Translation) and apply it to the virtual servers. Then configure the WebSphere® SIP proxy server to use the same SSL certificates as the IP routing Load Balancer.

Routing TLS SIP traffic through an IP routing Load Balancer

To run TLS SIP traffic through an IP routing Load Balancer, first enable SNAT (Secure Network Address Translation) and apply it to the virtual servers. Then configure the WebSphere® SIP proxy server to use the same SSL certificates as the IP routing Load Balancer.

Before you begin

You should already have created virtual servers for TLS traffic over TCP. For instructions, see page 21 of the article linked on the following page:

Achieving High Availability with WebSphere Application Server SIP Container and F5 BIG-IP Local Traffic Manager