Clustering Community Servers

Community server clusters allow you to have high capacity and fail over/redundancy for Community services. For more information on clustering and capacity planning, see planning section in Community Services. Sametime leverages the Domino clustering feature to keep the VPUserInfo.nsf database replicated and up to date on participating servers. The user’s privacy configuration and contacts are stored in this database.

Before you begin

  • The Domino server on which the Sametime server is installed must be registered in the same Domino domain as the other servers participating in the cluster.
  • A network device is required to front-end the cluster, this can be an IP sprayer, load balancer, or round robin DNS.
  • All Sametime Community servers must be able to connect to each other on ports 1352 and 1516. This is required for the full mesh topology discussed in the planning topic for Community Services.
  • The Sametime Community servers should be installed and functioning properly (able to login as a user and chat).
  • The community ID must be the same for all servers.
  • The VP_SECURITY_LEVEL setting in the sametime.ini must be the same on all participating servers.
  • All Sametime servers must share the same directory settings for LDAP or native Domino server.

About this task

  • Only 6 servers are supported in a cluster.
  • You can install up to 5 standalone muxes per Community server. The muxes can service more than one Community server.
  • Participating servers should be collocated.