Home
HCL Sametime® Administration Guide 12.0.1
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 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 autoscaling for recorder
A recorder is used when a meeting is being recorded and when live streaming a video. The Kubernetes autoscaler adjusts the use of recorder pods based on settings in the recorder.yaml file.

HCL Sametime® Administration Guide 12.0.1
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- What's new
  HCL Sametime and HCL Sametime Premium 12.0.1 provide many new features, enhancements and fixes to servers and clients. Additional releases to version 12.0.1 also provides updates to the product.
- 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, certain Sametime features might be 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 begin the install process, ensure that the environment includes all prerequistes and system requirements.
  - Platforms
    Docker and Kubernetes have different goals and outcomes. The decision about which platform to use depends on your end goal.
  - Meeting server FAQ
    The Meeting server routes media traffic.
  - Sametime clients
    Several client types are supported providing flexibility in how users can access chats and meetings. A single deployment can implement several client types.
  - 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
      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 10,000 simultaneous log-ins.
    - 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 autoscaling for recorder
        A recorder is used when a meeting is being recorded and when live streaming a video. The Kubernetes autoscaler adjusts the use of recorder pods based on settings in the recorder.yaml file.
      - Configuring autoscaling for video
        The Kubernetes autoscaler adjusts the use of video pods based on the configured values in the video.yaml file.
    - Configuring MongoDB for high availability
      This topic covers the steps on how to configure MongoDB for high availability.
- Installing
  This section provides information on installing the servers for Sametime and Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server. Configuration tasks are dependent on the deployment environment.
- 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 removed, follow the procedure for the platform that Sametime is installed on.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Configuring autoscaling for recorder

A recorder is used when a meeting is being recorded and when live streaming a video. The Kubernetes autoscaler adjusts the use of recorder pods based on settings in the recorder.yaml file.

Before you begin

To deploy the autoscaler, Prometheus must be installed. See Installing Prometheus for the details.

About this task

When a recorder is being used in a meeting, it is dedicated to that meeting until the user stops the recorder or the meeting is stopped. At that time, the recorder is available to be used again. For example, if two recorders are deployed, only two meetings can be recorded at the same time. A recorder is not available until one of the meetings ends. The live streaming feature is also handled by the recorder.

Estimate how many recorders you may need and define the minimum and maximum number of recorder pods that are used by the autoscaler.

Procedure

Change directories to installation_directory/ /kubernetes/autoscaling directory. Where installation_directory is the directory the install package is located.
Open the recorder.yaml file for editing.
Configure the minimum number and maximum number of recorders by adjusting the following settings.
```
minReplicas: minimum_value
maxReplicas: maximum_value
```
For example:
```
minReplicas: 2 
maxReplicas: 10
```
Save and close the file.
To deploy the recorder autoscaler, run the following command from the autoscaling directory.
```
kubectl apply -f recorder.yaml
```
If the autoscaler has already been deployed, you can adjust the number of recorder pods available. The following command can be used to adjust the number of recorders.
```
kubectl edit hpa recorder
```

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.