Adding a server to the Community Server cluster
You can add IBM® Sametime® Community Servers to an existing cluster.
Procedure
- Follow these steps to ensure sure that all databases have
the same replica ID.
- Add the Sametime Community Server to the IBM Domino® server cluster following the guidelines described in Creating a Domino server cluster.
-
Update the Cluster Information document and copy the updated document to all Sametime Community servers in the community:
-
Add the name of the new Sametime server to the
List of Servers in Cluster field in the Cluster Information document in the
Configuration database (stconfig.nsf) on one Sametime
server.
Enter the server name in the Domino full canonical name format (for example, cn=servername/ou=organizational unit/o=organization). Do not use the fully qualified DNS name in this field.
The list includes every Sametime server in the cluster; separate the server names with a semicolon and a space as shown in the following example:
cn=sametimeserver1/ou=west/o=mycompany; cn=sametimeserver2/ou=west/o=mycompany
-
Copy the updated Cluster Information document and paste it into the Configuration database on
every Sametime server in the community (both clustered
servers and non-clustered servers).
Note: After pasting the new Cluster Information document in the Configuration database, you can delete the previous version of the Cluster Information document.
-
Add the name of the new Sametime server to the
List of Servers in Cluster field in the Cluster Information document in the
Configuration database (stconfig.nsf) on one Sametime
server.
- Optional: You can deploy a stand-alone Sametime Community Mux to
ensure the connection load for your Community Services cluster is
handled efficiently. However, if you do not deploy another Community
Services multiplexer, the existing Community Services multiplexers
can still make Connections to the newly added Sametime server.
If you deploy a stand-alone Sametime Community Mux, make sure to update the Community Connectivity configuration document on every Sametime server in the cluster and include the IP address of the new multiplexer.
-
Ensure that Names.nsf and all secondary directories specified in the Directory Assistance
database replicate to all other Domino servers.
If you have other Domino servers outside the Sametime cluster, ensure that Names.nsf and the secondary directories are included in the usual replication schedule between servers.
If you only use Domino servers for the Sametime cluster, or you do not have a centralized replication topology, set up a weekly replication schedule for a time when the Sametime servers are not very busy. Replicate in a Pull-Pull style.