Creating a cluster document in the Configuration database (stconfig.nsf)

The cluster document enables the servers in a cluster to operate as part of the cluster, and enables servers outside of the cluster (but still within the community) to communicate with the cluster.

About this task

Creating a cluster document in the IBM® Sametime® Configuration database (stconfig.nsf) is one of the tasks associated with Setting up a Community Services cluster without clustering the Meeting Services.

The Sametime administrator must manually create a cluster document in the Sametime Configuration database (stconfig.nsf) on a Sametime server in the Community Services cluster. The cluster document defines the Community Services cluster.

The cluster document stores the following information:

  • The Community Services cluster name.
  • The DNS name assigned to the rotating DNS system or IBM WebSphere® Edge Server that performs the load-balancing operations.
  • A list of all servers in the Community Services cluster.

To create the cluster document in the Sametime Configuration database:

Procedure

  1. Using an IBM Notes® client, open the Sametime Configuration database (stconfig.nsf).
  2. Click Create > Cluster Information.
  3. In the Cluster Name field, type the cluster's name.

    The cluster is named at your discretion. You can name the cluster after one of the servers in the cluster, but it is not mandatory. If you do name the cluster after one of the servers in the cluster, keep the following points in mind:

    • You might save time when you add the cluster name to the Sametime server field of each user's Person document to configure client connectivity because users will already have that server name listed in their Person documents (or LDAP directory person entries).
    • You might choose to use the IBM Domino full canonical name of the server (for example, cn=servername/ou=organizational unit/o=organization) but it is not required.
    • You might choose to use the DNS name of the server but again, it is not required.
    • The cluster name must not contain a comma or a space.
  4. In the DNS Name field, enter the fully qualified DNS name for the cluster. This name must be the DNS name of the rotating DNS system or the WebSphere Edge Server Network Dispatcher that performs the load balancing operations for the clustered Community Services.
  5. In the List of Servers in Cluster field, type the names of all the servers that are part of the cluster. The names must be entered in the IBM Domino full canonical name format (do not use the fully qualified DNS names in this field). Separate the server names with a semicolon and a space, as in: cn=sametimeserver1/ou=west/o=acme; cn=sametimeserver2/ou=west/o=acme
    Tip: The surest method of determining the correct name of the server is to open into the sametime.ini file and copy the server's name from the SametimeCluster field.
  6. Save and close the cluster document.

    Leave the Configuration database open. In the next procedure, you will copy the new Cluster Information document to all other Sametime servers within the Sametime community (because the stconfig.nsf database is not replicated).