Home
HCL Sametime® Administration Guide 12
Configuring
This section provides information on configuring the HCL Sametime server.
Updating the time-to-live index for persistent chat
The time-to-live (TTL) setting defines how long the chat history is stored in the database. The default value is 90 days. However, administrators can update the value based on the organization's preferred setting.

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.
- 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.
  - Adding corporate branding to meeting pages
    You can customize meetings to reflect your company's branding and visual presence.
  - Adding virtual backgrounds to the global library
    By default, you can customize your meetings with virtual backgrounds and themes. As an administrator, you can choose which backgrounds and themes are available to all users.
  - Configuring the recorder on Docker and Kubernetes instances
    Each recorder instance requires access to a unique ALSA loop-back device on the host. To accomplish this, you must run a series of commands on any node that hosts a recorder pod.
  - Configuring alternate STUN servers
    Sametime Meetings uses public Google STUN servers by default. To use different STUN servers, you must complete this procedure before installing Sametime Meetings.
  - Setting up business cards
    You can configure the Sametime 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. Business card information also displays at the top of an active chat window.
  - Configuring LDAP
    Sametime supports LDAP directory servers as the user repository.
  - Updating the time-to-live index for persistent chat
    The time-to-live (TTL) setting defines how long the chat history is stored in the database. The default value is 90 days. However, administrators can update the value based on the organization's preferred setting.
  - Managing secrets in Kubernetes
    Sensitive information such as passwords, service account names, certificates, and other confidential data needed by Sametime pods are stored in secrets. In addition to helm charts and configuration map, the Sametime configuration is also derived from secrets.
  - Applying configuration changes in Docker
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  - Applying configuration changes in Kubernetes
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  - Chat
    This section contains Chat configuration considerations.
  - Meetings
    This section will discuss Meetings configuration steps specific to the HCL Sametime Meetings server.
  - Integrating with other applications
    Integration with an application such as Verse prior to Sametime 12.0 requires the legacy web-client interface. Beginning in Sametime 12.0 the legacy web-client is not enabled by default, but can enabled when needed for integration with other products.
- 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

Updating the time-to-live index for persistent chat

The time-to-live (TTL) setting defines how long the chat history is stored in the database. The default value is 90 days. However, administrators can update the value based on the organization's preferred setting.

Before you begin

The TTL index in MongoDB must be rebuilt. For more information, refer to Manage Indexes in the MongoDB documentation.

About this task

To update the TTL settings used by the Sametime server involves modifying the following files.

custom.env for Docker
helm/values.yaml for Kubernetes

Note: These values are case sensitive and must be entered as shown below.

Procedure

Modify the configuration file. The minimum value is 1.
- For Docker, update the CLI__ChatLogging__CL_MONGO_HISTORY_TTL parameter. In the following example, the value is set to 7 days.
```
CLI__ChatLogging__CL_MONGO_HISTORY_TTL=7
```
- For Kubernetes, update the CLI__ChatLogging__CL_MONGO_HISTORY_TTL parameter. In the following example, the value is set to 7 days.
```
CLI__ChatLogging__CL_MONGO_HISTORY_TTL: 7
```
Modify the Convomap Max Days configuration value to match the MongoDB TTL value. The minimum value is 1.
- For Docker, update the STI__convomap__CONVOMAP_MAX_DAYS parameter. In the following example, the value is set to 7 days.
```
STI__convomap__CONVOMAP_MAX_DAYS=7
```
- For Kubernetes, update the STI__convomap__CONVOMAP_MAX_DAYS parameters. In the following example, the value is set to 7 days.
```
STI__convomap__CONVOMAP_MAX_DAYS: 7
```
You can update the STI__convomap__CONVOMAP_MAX_HOURS parameter to add hours to the time frame. In the following examples, the value is set to 2 hours.
- Docker:
```
STI__convomap__CONVOMAP_MAX_HOURS=2
```
- Kubernetes:
```
STI__convomap__CONVOMAP_MAX_HOURS: 2
```
In the Mongo shell, run the following commands.
```
use chatlogging
```
```
db.EVENTS.getIndexes()
```
```
db.EVENTS.dropIndex("TimeStamp_1")
```
The db.EVENTS.dropIndex command defines the name of the index to drop. The value is TimeStamp_1.
Restart the Sametime server to apply the changes. The TTL index is updated with the new value.
For more information, refer to Starting and stopping servers.
Run the following command to confirm that the value for TimeStamp_1 is updated.
```
db.EVENTS.getIndexes()
```