Home
Welcome to the HCL Sametime® 11.6 administration documentation
Configuring
This section provides information on configuring the servers for HCL Sametime 11.6.
Clustering
This section will discuss clustering steps specific to the HCL Sametime Community server.
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.
Ensuring all Community Servers have the same settings

Welcome to the HCL Sametime® 11.6 administration documentation
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
  - Setting up business cards
    You can configure the Sametime Community Server so that business card information about an individual displays when a user hovers over a name in a chat window or a contact list.
  - Community Services
    This section will discuss configuration steps specific to the HCL Sametime Community server.
  - Clustering
    This section will discuss clustering steps specific to the HCL Sametime Community server.
    - 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.
      - Assigning users to a Home Sametime Server 
        This topic discusses the concept of the Home Sametime Server setting, its purpose, use and configuration. 
      - Create the Domino cluster
      - Creating a cluster document in the Configuration Database
        The Sametime cluster document enables the servers in a cluster to operate as part of the cluster, and enables the servers outside of the cluster (but within the community) to communicate with the cluster.
      - Copying a cluster document to all Sametime Community Servers
        Each Sametime Community Server cluster has a Cluster Information document, which was created on one Sametime server in the cluster. Every server in the 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.
      - Setting up the load-balancing network device
      - Enabling scheduled replication
        When clustering Domino servers, the cluster replicator task will keep the databases synchronized, but it is a best practice to also schedule a periodic replication.
      - Ensuring all Community Servers have the same settings
  - Meetings
    This section will discuss Meetings configuration steps specific to the HCL Sametime Meetings server.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Ensuring all Community Servers have the same settings

About this task

Your Sametime servers should be configured identically so that the user has the same experience regardless of which server they connect to. As a best practice you can configure one server, then copy and paste those settings to the other cluster members:

See this topic for databases to replicate: Enabling scheduled replication.

The stconfig.nsf database should be a unique database on each server but the following documents should be copied from one server to the others:

ClusterInformation
LDAPServer
Examine the CommunityConnectivity settings document and determine if some of the settings should be carried over to the other cluster members. Some of the settings may be unique to each server, so do not copy and paste this document.

Using the OS, copy and paste these documents from the Domino program directory to the other cluster members:

Policies.user.xml
Policies.server.xml
Userinfoconfig.xml
Chatlogging.ini

If you have multi-tenancy enabled, the file customizedMultitenancy.ini should be identical among all cluster members.

Open the sametime.ini and check for the following:

The [Directory] section contains tuning parameters that should be the same across all servers.
The ST_Community_ID should be the same.
VPMX_CAPACITY should be the same.
All Client Types settings should be the same.
All settings in the section [ST_BB_NAMES] should be the same

Note: Some settings are unique in the sametime.ini to the server on which it resides. Do not overwrite sametime.ini with a file from a different server.

Check the security configuration of the server. When your servers are clustered, it is a best practice to use a Subject Alternative Names (SAN) certificate they can share. Each server should be configured with the same level of security so that when a user fails over from one server to another, their experience does not change.

See the Securing Connections topic and sub-topics if you are unfamiliar with these settings.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.