Home
HCL Sametime® Administration Guide 12.0.1
Administering
This section provides information on administering on Sametime environments.
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.

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.
- 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.
  - 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 allow administrators to control user access to features.
  - Configuration files
    Configuration files maintain information used by the Sametime server for various reasons.
  - 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.
  - Using the Sametime Database utility
    The Sametime Database utility is used to synchronize the information with that of the Sametime server database.
  - 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.
- 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

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.

About this task

To manage the Sametime server on Docker, you use the docker-compose command.

To start the Sametime server on Docker, run the following command.
```
docker-compose up -d
```
To stop the Sametime server, run the following command.
```
docker-compose down
```

On Kubernetes, scaling the pods can be used to start and stop the Sametime service. The kubectl scale command is use.

Scale the pod to one, starts the service.
```
kubectl scale deploy deployment_name --replicas=1
```
Scale the pod to zero, where pod_deployment_name is the pod name.
```
kubectl scale deploy deployment_name --replicas=0
```

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.