Federate the newly installed Secondary Node into a cluster of IBM
® Sametime servers.
About this task
The next stage in deploying a stand-alone IBM WebSphere
® proxy server is to federate the new Sametime node into the existing cluster. For this task, you will use the Clustering guided activity, selecting the "Select Existing Cluster" option (in Step 3) and then choosing the appropriate cluster.
When you run the cluster guided activity there are phases: first, the proxy server is federated to the cluster's Deployment Manager; then the proxy server is added into the cluster as a new member. Be sure to complete all steps in the guided activity to properly add the proxy server to the cluster.
Adding the additional WebSphere proxy server to the Meeting Server clusterParent topic: (Optional) Adding a stand-alone WebSphere proxy server to the cluster
Previous topic: Installing an additional Sametime server as a Secondary Node
Next topic: Removing the Sametime product from the new node
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.