Configuring a cluster of IBM
® Advanced servers involves several tasks, including synchronizing system clocks, configuring the cluster settings, and deploying a load balancer in front of the cluster, either deploying IBM
Load Balancer or another load balancer product.
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.
Before you can configure a cluster of Sametime
Advanced 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 Meeting server cluster, a Media Manager cluster, and an Advanced server cluster. If you want to create additional clusters for a particular product, you must deploy additional Deployment Managers.
- Sametime Community Servers
At least one Sametime Community Server must be deployed. The Community Server provides presence and awareness for chats.
- One Sametime Advanced server installed with the Network Deployment -> 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 servers installed with the Network Deployment -> 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).
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.
Parent topic: Migrating and upgrading Sametime Advanced
Clustering Sametime servers for high enterprise availability
1. Setting clocks on the upgraded Sametime Advanced servers to be clustered
Synchronize the system clocks on the servers to be clustered with an IBM WebSphere
® Application Server network deployment.
2. Clustering upgraded Sametime Advanced servers
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. Restarting the servers in the Sametime Advanced cluster
After running the Clustering guided activity, synchronize the nodes in the cluster and restart the application servers.
4. Installing IBM Load Balancer in an upgraded Sametime Advanced 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