Each Sametime Community server cluster has a Cluster Information document, which was created on one Sametime
® server in the cluster. Every server in the IBM
® Sametime community must have a copy of this Cluster Information document, even if the server is not part of a cluster. The document allows users to share presence and instant messaging capabilities with all other users in the community, regardless of their home server assignment.
About this task
If you have multiple clusters in a single community, there are multiple Cluster Information documents and every server in the community must have a copy of all of them. Creating separate clusters for different locations is more efficient because you avoid replicating databases in real-time across a WAN connection. For example, you could have one cluster for your Dublin office users and another for your Paris office users.
Follow these steps to copy each Cluster Information document to all other Sametime
Community servers in the community.
replicate the Configuration database. The Configuration database contains some fields that cannot be replicated to all Sametime
servers in a community.
- If necessary, open the Sametime Configuration database (stconfig.nsf) in which you created the Cluster Information document that defines the cluster.
- Copy the Cluster Information document:
- Locate "Cluster Information" in the Form Name column of the Configuration database.
- In the Cluster Information's Last Modified Date column, right-click on the date that represents the Cluster Information document you want to copy.
- Select Copy.
- Click File -> Close to close the Configuration database.
- Paste the Cluster Information document into the Configuration database on each Sametime server in the community:
- From the Lotus Notes® client, click File -> Database -> Open.
- In the Server field, type the name of another Sametime server in the community.
- Click Open.
- In the Database list, select the Configuration database (stconfig.nsf).
- Click Open.
- Click Edit -> Paste to paste the Cluster Information document into the Configuration database on this Sametime server. The document name and date will appear in the Last Modified Date column of Form Name section in the Configuration database.
- Save and close the Configuration database.
- Repeat step 3 for every Sametime server in the Sametime community.
- Repeat this set of steps until all Cluster Information documents have been copied to all servers in the community.
What to do next
Ensure that clients can access the Community Services cluster by configuring client connectivity for the Community Services cluster
Parent topic: Setting up the Sametime Community Server cluster
Previous topic: Creating a cluster document in the Configuration database (stconfig.nsf)
Next topic: Registering a Community Server cluster on AIX, Linux, Solaris, and Windows