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.
Configure high capacity for chat

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

Configure high capacity for chat

About this task

Sametime supports up to 10,000 simultaneous log-ins with a standard single community pod, mux pod and proxy pod in a Kubernetes deployment. Docker deployments of Sametime support 10000 simultaneous log-ins.

The Sametime mux is used to front-end client connections between the Sametime Connect client and the Sametime Embedded client inside of HCL Notes. If you need to additional capacity for these clients, you can deploy multiple community pods inside your Kubernetes cluster. The number of community pods is defined in the values.yaml file and each additional pod supports up to 10,000 additional clients. The community pod does not axiomatically scale, it is important to estimate the number of pods needed and define the setting in the values.yaml file.

Procedure

In the values.yaml file ensure that this setting is set to true, which is the default setting:
```
enableMuxDeployment: true
```
Change the below setting to the desired number of community pods:
```
numberOfCommunityServers: 1 
```
To find the Kubernetes service that front-ends the mux issue the command:
```
 kubectl get svc | grep mux 
```
The ingress controller in a Kubernetes cluster front-ends the connection to the web and mobile clients and the proxy pod services those connections. Additionally, the community pod validates log ins and service the users as well. Sametime supports up to 10,000 simultaneous connections in a Kubernetes environment, and if more are needed, it is recommended to deploy an additional 1 ingress controller pod, 1 proxy pod and 1 community pod per 10,000 web and mobile clients.