IBM Sametime wiki
Sametime Advanced 8.5.2 IFR 1 for administrators
Sametime Standard 8.5.2 IFR 1 for administrators
Sametime Unified Telephony 8.5.2 IFR 1 for administrators
Custom Search Scope...
Administering Sametime Advanced
Administering Sametime Advanced 8.5.2 Interim Feature Release 1 documentation
You are currently viewing machine translated content. IBM translation might be available. Click
IBM Translated Product Documentation
to see what is available.
Federating the new Secondary Node to the SIP Proxy and Registrar cluster
November 23, 2011
Federate the newly installed Secondary Node into a cluster of IBM® Sametime servers.
Federate the newly installed Secondary Node into a cluster of
® Sametime servers.
About this task
The next stage in deploying a stand-alone
® 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.
(Optional) Adding a stand-alone WebSphere proxy server to the SIP Proxy and Registrar cluster
Installing an additional Sametime server as a Secondary Node in the SIP Proxy and Registrar cluster
Removing the Sametime product from the new node in the SIP Proxy and Registrar cluster
Edit the article to add or modify attachments.
Compare selected versions
Summary of changes
This version (1)
Nov 23, 2011 12:07:35 PM
Copy and paste this wiki markup to link to this article from another article in this wiki.