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.

Before you begin

Install the first Conference Manager using the Primary Node profile, and then install one or more additional Conference Managers using the Secondary Node profile.

About this task

To cluster Conference Manager components, complete the following tasks in the sequence shown.

Attention: You must complete all of the tasks to ensure your cluster operates properly.
  1. Setting clocks on the Conference Managers to be clustered
    Synchronize the system clocks on the servers to be clustered with an IBM WebSphere Application Server network deployment.
  2. Setting up the Clustering Conference Managers guided activity
    Use the IBM Sametime System Console to create a cluster of Sametime Servers hosted on IBM WebSphere Application Server. The Sametime servers must all be running the same type of server; for example, Sametime Meeting Server, Sametime Proxy Server, Sametime Media Manager Conference Manager, Sametime Media Manager SIP Proxy/Registrar, or Sametime Advanced.
  3. Configuring the Conference Manager cluster
    Complete the configuration for clustering Sametime Media Manager Conference Manager components using a WebSphere Application Server network deployment.
  4. Setting up a WebSphere proxy server for the Conference Manager 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.
  5. Installing IBM Load Balancer for a cluster of Sametime Conference Managers
    Install a load balancer in front of a cluster of IBM Sametime servers to distribute connections among the servers. The cluster should have at least two IBM WebSphere SIP proxy servers deployed in front of it, so that the load balancer can direct connections to those proxy servers for forwarding to the individual Sametime servers in the cluster.
  6. Configuring WebSphere proxy server for load balancing in a Conference Manager cluster
    To best support high availability and provide fail over services, a cluster of IBM Sametime Media Manager servers should be fronted with at least two IBM WebSphere proxy servers and IBM Load Balancer.
  7. Updating the stavconfig.xml file on Conference Managers
    In an IBM Sametime deployment, the stavconfig.xml file hosted on each Sametime Conference Manager contains the FQDN/IP address and port information of each Sametime SIP Proxy/Registrar and Conference Manager.

What to do next

Complete the task Setting up the Video Manager Server load balancer, which is in the section "Clustering Sametime Video Manager Servers."
Parent topic: Clustering Sametime Media Manager components
Previous topic: Clustering SIP Proxy/Registrars
Next topic: Clustering Sametime Video Managers