Configuring a cluster of IBM
® Meeting Servers involves several tasks, including synchronizing system clocks, configuring the cluster settings, and configuring an IBM WebSphere
® proxy server for the cluster, as well as optionally deploying an IBM
Load Balancer in front of 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
Meeting Servers, you must have installed the following servers:
- The Sametime System Console
This server can function as the Deployment Manager for the vertical or horizontal cluster scenarios described in this procedure.
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.
- (Optional) Sametime Community Servers
At least one Sametime Community Server must be deployed if you want to provide presence and awareness for users attending online meetings.
- One Sametime Meeting Server 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). The Primary Node must already be registered with the Sametime System Console. Registration happens automatically on AIX® Linux™, Solaris, and Windows™, but on IBM i, you run the registration utility to register servers.
- (Horizontal cluster only) One or more Sametime Meeting Servers installed with the Secondary Node option.
Secondary nodes are used to horizontally scale your cluster across multiple physical systems. These additional nodes act as containers for additional cluster members, which 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 (one cluster member on each Secondary Node, plus one cluster member or one vertical cluster on the Primary Node). Secondary Nodes must already be registered with the Sametime System Console. Registration happens automatically on AIX Linux, Solaris, and Windows, but on IBM i, you run the registration utility to register servers.
About this task
There are several tasks involved in creating a cluster; complete them in the sequence shown here:
Complete all of the tasks to ensure your cluster operates properly.
What to do next
Proceed to Preparing the Sametime Meeting server for users
Parent topic: Installing a Sametime Meeting Server
Previous topic: Verifying a Sametime Meeting Server installation
Next topic: Deploying Sametime Meeting Server and Sametime Proxy Server on the same computer
Clustering Sametime servers for high enterprise availability
Registering a Sametime Meeting Server on IBM i with the Sametime System Console sta852ifr1
1. Setting clocks on the servers to be clustered
Synchronize the system clocks on the servers to be clustered with an IBM WebSphere
Application Server network deployment.
2. Clustering Sametime servers running on WebSphere Application Server
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 cluster
Complete the configuration for clustering IBM
Sametime Meeting Servers using an IBM WebSphere
Application Server network deployment.
4. 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.
5. Installing IBM Load Balancer in a Meeting Server 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