Home
HCL Sametime® Administration Guide 12
Administering
This section provides information on administering on Sametime environments.
Configuration files
Configuration files are used to maintain information used by the Sametime server for various reasons. In Sametime v12, configuration files are generated on demand based on information in the container management configuration file based on the whether you are using Docker or Kubernetes.

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.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
  - Managing Sametime clients
    This section provides information on managing Sametime clients.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
  - Testing Sametime chat and meeting clients
    This article assumes that you have successfully installed and configured Sametime or Sametime Premium.
  - Starting and stopping the Sametime server
    Starting and stopping the Sametime server involves starting and stopping the Sametime services running in the container management system.
  - Starting and stopping MongoDB
  - Managing policies
    Sametime policies allows administrators to control user access to features.
  - Configuration files
    Configuration files are used to maintain information used by the Sametime server for various reasons. In Sametime v12, configuration files are generated on demand based on information in the container management configuration file based on the whether you are using Docker or Kubernetes.
  - Enabling multi-tenancy
    Multi-tenancy allows multiple organizations to be part of the Sametime community. With multi-tenancy, Sametime users can chat, add users and groups to contact lists, and have awareness of users in their organization or in other organizations that are configured to be visible to them.
  - MongoDB
    This section provides information relating to administering MongoDB.
  - Managing Sametime Meetings
    This topic explains the features you can enable or disable for meetings. Currently, the settings that you can change are global settings that apply to the entire server. User policies cannot control the settings.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
- 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

Configuration files

Configuration files are used to maintain information used by the Sametime server for various reasons. In Sametime v12, configuration files are generated on demand based on information in the container management configuration file based on the whether you are using Docker or Kubernetes.

In releases prior to version 12, there were several configuration files used by different Sametime servers. Now, the container management system generates configuration files as needed based on information of its primary configuration file.

The following table shows the configuration file used by Docker and Kubernetes.

Table 1. Primary configuration files used by the container management system
Environment	File name
Docker	custom.env
Kubernetes	values.yaml

Configuration values can be modified. Where a modification can be done it is covered in the appropriate topic. For example, updates to LTPA keys are covered in the enabling_sso_ltpa.html topics.