This guided activity takes you through the steps for clustering new IBM
® servers hosted on IBM WebSphere
® Application Server. The servers you add to the cluster must all be running the same Sametime
product application; for example, Sametime
Meeting Server, Sametime
Proxy Server, Sametime
Media Manager Conference Manager, Sametime
Media Manager SIP Proxy and Registrar, or Sametime
Before you begin
- Install the Sametime System Console and two or more Sametime servers of the same product type; then start the Sametime System Console and all of the servers you plan to cluster.
This guided activity applies to the following Sametime
servers if they are installed in your deployment.
- Sametime Proxy Server
- Sametime Meeting Server
- Sametime Media Manager
Clustering is not available for the Packet Switcher; it is also not available for an "All Components" installation of the Media Manager, which includes the Packet Switcher. The Conference Manager components and the SIP Proxy and Registrar components must be installed and clustered on dedicated computers.
- Sametime Advanced
- Run the backupConfig utility for the Deployment Manager, the Primary Node, and any Secondary Nodes before beginning the cluster guided activity. The utility is located in the bin folder under the profile of each server. The utility automatically shuts down any running servers in the profile, so you must restart the severs after running the utility. Use the restoreConfig utility to restore the configuration if the changes need to be undone. For more information on backupConfig and restoreConfig, see the WebSphere Application Server Information Center.
About this task
Multiple product clusters are not supported on a single computer; however, vertical clusters (all cluster members installed on the Primary Node) are supported when each product cluster is on a dedicated computer. A horizontal cluster is defined as a cluster with each cluster member having a dedicated computer (one on the Primary Node and one on each Secondary Node).
Note that you cannot use this activity to cluster Sametime
Community Servers (see "Clustering Sametime
Community Servers") or Sametime
Gateway servers (see "Installing Sametime
Gateway servers in a cluster").
Configure a cluster of one type of product server to improve performance with high availability, and to provide failover. You can create a horizontal cluster in which each node is hosted on a separate computer, as well as a vertical cluster with multiple cluster members hosted on the Primary Node.
These instructions generally assume that you will use the Sametime
System Console as the cluster's Deployment Manager, which provides a single Integrated Solutions Console for all WebSphere
administrative functions for all servers participating in the cell – this simplifies the administrative experience. If you deploy clusters for both Sametime
Meeting Server and Sametime
Advanced Server, then at least one of those clusters require a dedicated Deployment Manager.
If you are creating or updating a cluster that does not use the Sametime
System Console as the Deployment Manager, it is necessary to ensure that the Deployment Managers are able to create SOAP connections to each other. A firewall should not be blocking the SOAP port and the host names should be resolvable. Also the System Console needs to access any standalone primary node’s application port and a primary node needs to access its Deployment Manger's SOAP port. The port assignments may be different so it is important to verify them in the Integrated Solutions Console. The Deployment Manager ports are under the System Administration -> Deployment Manager -> Ports section. A server's ports can be checked by selecting the server in the Servers view of Integrated Solutions Console. The SOAP ports are called SOAP_CONNECTOR_ADDRESS and the application ports are WC_defaulthost and WC_defaulthost_secure.
Parent topic: Clustering Sametime servers running on WebSphere Application Server
- Cluster WebSphere Application Servers.
Click Next to begin the clustering activity.
- Select Product to Cluster.
Select the product server to cluster, and then click Next.
The list only displays Sametime products for which one or more servers have been installed and registered with the Sametime System Console. If you installed servers using deployment plans, they are registered with the console automatically. If you did not use a deployment plan, you must manually register the servers with the console before proceeding as you would if installation failed (see "Registering a Sametime Proxy Server, Media Manager, Meeting Server, or Sametime Advanced manually on AIX, Linux, Solaris, and Windows" in the Troubleshooting section).
- Select or Create a Cluster.
To create a cluster:
- Click Create Cluster if you are setting up a new cluster.
- Type a descriptive name for the cluster in the Cluster Name field.
For example, if you are creating a cluster of Sametime Meeting Servers, you will probably want to indicate that in the cluster name so you can easily identify it later.
- Click Next.
To modify an existing cluster; for example, to add a new cluster member:
- Click Select Existing Cluster.
- Select a cluster in the Cluster Name list.
If you are going to add a node or cluster member to the cluster, you must use the same Sametime product. For example, you cannot add a Sametime Meeting Server cluster member to a cluster of Sametime Proxy Servers.
- Click Next.
- Select the Deployment Manager.
In the Select Deployment Manager list, select the Sametime System Console as the cluster's deployment manager, and then click Next.
Every cluster must have exactly one Deployment Manager; the Sametime System Console can function as the Deployment Manager for multiple clusters. Remember that if you will create clusters for both Sametime Proxy Server and Sametime Meeting Server, at least one of those clusters requires a dedicated Deployment Manager; this is only true when your deployment will include both types of cluster.
- Create the Cluster with the Primary Node.
You created and federated a primary node when you installed the first server for this product. Make sure that the Primary Node's application server is running. Click Create cluster to configure the cluster settings, and then click Next.
Do not click anywhere on the browser until the operation completes or it may interrupt the clustering process.
- Select One or More Secondary Nodes.
If you are creating a horizontal cluster where each node is hosted on a separate computer, add one or more secondary nodes to the cluster. You created and federated the secondary nodes when you installed them. In the Secondary Node Name list, click the node you want to add to the cluster and click Next.
- Add Cluster Members.
If you are creating a vertical cluster where multiple copies of the application are hosted on a single computer, add one or more "cluster members" to the Primary Node. If you are creating a horizontal cluster, add one cluster member to each of the secondary nodes you federated in the previous step.
The table lists Cluster Members, the Node that the cluster resides on, and the Status of each cluster member. Each node in the cluster needs to have at least one cluster member created on it for the node to be used in the cluster. The status of a Cluster Member will be "Clustered" if the cluster member has been completely configured on the node. If the status is "Ready to Cluster", select the Cluster Member and use the "Add to Cluster" button to finish configuring the cluster member.
- To add new cluster member, click New.
- Select the default name generated for the cluster member or enter your own cluster member server name.
- Select the Primary Node to create the cluster member on.
- Click Add to Cluster.
The status will change from "Ready to cluster" to "Clustered".
- Click Next.
For each Secondary Node you added in the previous step, a cluster member is prepopulated into the table for you, one on each of the Secondary Nodes.
- Select the default cluster member name for each server or update with your own name, and verify that the nodes the cluster member servers will be created on are correct for your topology.
- One at a time, select each cluster member and click Add to Cluster.
Do not proceed until the current cluster member's status changes from "Ready to cluster" to "Clustered"; then you can add the next cluster member.
- If you want to add more cluster members, click New to add another row to the table, and then fill out the information accordingly.
- Click Next.
- Deployment Summary.
Click Finish to save the cluster configuration.
Continue with the cluster configuration tasks described in the Sametime information center.