Home
HCL Sametime® Administration Guide 12
Planning
This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
Clustering and high availability
High availability and high capacity configuration for Sametime is achieved in different ways depending on which component is being configured for HA. See the topics below to learn more about chat, meetings and MongoDB.
Configuring MongoDB for high availability

HCL Sametime® Administration Guide 12
- 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.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
  - Sametime versus Sametime Premium
    Depending on the Sametime product that is installed, detemines which Sametime features are available. HCL Sametime provides secure real-time communication across devices, and HCL Sametime Premium expands those features to include video and file sharing.
  - Prerequistes
    Before you being the install process, ensure that your environment includes all prerequistes and system requirements.
  - Platforms
  - Meeting server FAQ
    The Meeting server routes media traffic.
  - Planning the network topology and connectivity
    This topic explains how Sametime components are connected and the default ports that are used. There are also example topologies to illustrate how Sametime can be deployed in different scenarios.
  - Network planning for meetings
  - Clustering and high availability
    High availability and high capacity configuration for Sametime is achieved in different ways depending on which component is being configured for HA. See the topics below to learn more about chat, meetings and MongoDB.
    - Configure high capacity for chat
    - Configure high capacity for meetings
      High availability is supported for the front-end web traffic to the Kubernetes cluster. You can deploy multiple front-ends on different physical and virtual nodes pointing to the same back-end in order to distribute load and survive a node outage.
    - Configuring MongoDB for high availability
  - Managing Sametime features
    HCL Domino users are entitled to limited use of HCL Sametime chat capabilities.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Configuring MongoDB for high availability

About this task

Beginning in Sametime 12.0, MongoDB clustering is handled during the install process for both Docker and Kubernetes.

Note: In the MongDB URL, if the user name or password includes the following characters, they must be converted by using a percent sign: / ? # [ ] : @.

Configuring MongoDB clustering on Docker

About this task

In the custom.env configuration file on the Sametime server, update the MONGO_ URL field. For information about how to create the MongoDB URL, see the Connection String URI Format topic in the MongoDB documentation.

Configuring MongoDB clustering on Kubernetes

Procedure

Provide a single node MongoDB information while running the prepareDeployement script.
When the prepareDeployement process is complete, prepare your MongoDB cluster URL. For how to prepare the MongoDB URL, see the Connection String URI Format topic in the MongoDB documentation.
Use Base64 encoding to encrypt your MongoDB URL.
You can review online websites that provide Base64 encoding or you can set up one on your own.
Use the kubectl command to update the sametime-meetings-global-secrets secret configuration file.
```
kubectl edit secret sametime-meetings-global-secrets
```
Inside the sametime-meetings-global-secrets, locate the MongoConnectionUrl section. Replace the value for it with the value from Step 3.
Save your changes.