Configuring a cluster of IBM
® Media Manager "Conference Manager" components involves several tasks, including synchronizing system clocks, configuring one or more IBM WebSphere
® proxy servers to operate with the cluster.
Before you begin
You can create two types of clusters:
- A Vertical cluster resides on the Primary node and includes two or more cluster members, which run the same application.
- A Horizontal cluster includes a Primary node plus one or mode Secondary nodes, all running the same application. Each node contains one cluster member.
It is suggested that you configure WebSphere
Application Server Network Deployment with a single subnet for network traffic. You can use one Network interface card (NIC) on a physical machine or logical partition (LPAR). You can also reference a single Domain name system (DNS) server in the network configuration for the physical machine or LPAR.
Before you can configure a cluster of Sametime
Media Manager "Conference Manager" components, you must have installed the following servers:
- Sametime System Console
This server will function as the cluster's Deployment Manager; the console can function as the Deployment Manager for multiple clusters.
Attention: Each Deployment Manager (including the Sametime System Console when it is used as a Deployment Manager) can support one cluster of each Sametime product. For example, a single Deployment Manager can support a Sametime Proxy server cluster, a Media Manager cluster, and a Meeting server cluster. To create additional clusters for a particular product, install the first server using Cell as the configuration type, which designates it as the Deployment Manager and the primary node for the cluster.
- Sametime Community Server
At least one Sametime Community Server must be deployed to provide presence and awareness for users attending online meetings.
- Sametime Meeting Server
At least one Sametime Meeting Server must be deployed to host online meetings where the audio and video features will be used.
- Sametime Media Manager "Packet Switcher" component
At least one Packet Switcher component must be deployed to route audio and video data to participant endpoints. You can deploy multiple Packet Switchers, but they cannot be clustered (the Conference Managers will balance the load among multiple Packet Switchers).
- One Sametime Media Manager "Conference Manager" component, installed with the Primary Node option.
Every cluster requires exactly one Primary Node. The application server on the Primary Node will function as the cluster's application template. All other application servers in the cluster (nodes and cluster members) will be duplicated from the Primary Node's application server. The Primary node's application server can only belong to one cluster. The Primary Node can be used as a container for additional cluster members when creating a vertical cluster (multiple cluster members on the same physical system).
- (Horizontal cluster only) One or more Sametime Media Manager "Conference Manager" components, installed with the Secondary Node option.
Secondary nodes are used to horizontally scale your cluster across multiple physical systems. These additional nodes act as a container for additional cluster members, which are can be used to balance loads and provide failover within the cluster. During the clustering process, you can deploy additional product application servers on any Secondary Nodes within the cluster, creating a horizontal cluster.
To cluster Conference Manager components, complete the following tasks in the sequence shown:
You must complete all of the tasks to ensure your cluster operates properly.
Parent topic: Clustering Sametime Media Manager components
Previous topic: Clustering SIP Proxy and Registrar components
Next topic: Managing multiple Packet Switcher nodes in a cluster with the Sametime System Console
Clustering Sametime servers for high enterprise availability
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. Clustering Conference Managers
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 and Registrar, or Sametime Advanced.
3. Configuring the Conference Manager cluster
Complete the configuration for clustering IBM
Sametime Media Manager Conference Manager components using an IBM 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. Configuring the Packet Switchers to access the cluster's WebSphere proxy server
After you create clusters of IBM
Sametime Media Manager Conference Manager and SIP Proxy and Registrar components, configure the Packet Switcher components to communicate with the cluster through the IBM WebSphere
6. Installing IBM Load Balancer for the Conference Manager cluster
Install and configure IBM
Load Balancer to distribute workload among a cluster of these type of servers: Sametime
Proxy Server, Sametime
Meeting Server, Media Manager Conference Manager, or Media Manager SIP Proxy and Registrar, and Sametime
7. 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 components should be fronted with at least two IBM WebSphere
proxy servers and IBM
8. Adding load balancer ports to the virtual host alias for the Conference Manager cluster
After creating an IBM Sametime
Media Manager Conference Manager cluster, add the load balancer ports that you created for the cluster’s IBM WebSphere
proxy servers to the default_host
alias in the cluster’s virtual host
9. Updating the stavconfig.xml file on Packet Switchers and Conference Managers for a load-balanced SIP Proxy and Registrar cluster
In an IBM Sametime
deployment, the stavconfig.xml
file hosted on each of the Media Manager’s Packet Switcher and Conference Manager components contains the IP address and port information for needed for connecting to the deployment’s SIP Proxy and Registrar components. If the SIP Proxy and Registrar component is clustered and uses a load balancer, you must update the stavconfig.xml
to use the load balancer’s IP address and port.