Hosting client files for Sametime on Docker or Podman

Sametime clients can be configured by administrators using a managed-settings.xml or managed-community-configs.xml file which is hosted by a web server. Additionally, the Sametime client can be pre-configured with settings such as the hostname, port, etc. The client package can be hosted on a web server for download. This topic has the steps to host files in the Sametime web container for Docker or Podman.

Before you begin

Ensure that you can access the client files and the Sametime server.
Prior to placing the managed-settings.xml or managed-community-configs.xml on Docker or Podman, open the file using a browser and ensure it is not producing any syntax errors. If errors are present, they should be resolved first.

About this task

The Docker and Podman commands are similar. The only difference is that docker precedes the command when issued in a Docker environment and podman precedes the name in a Podman environment. Example commands used in the Sametime documentation are shown using Docker. For Podman, change docker to podman.

Procedure

Shut down the Sametime server.
```
docker-compose down
```
Run the following command to copy the managed-settings.xml or managed-community-configs.xml file into the sametime-config/web/downloads directory.
```
cp SametimeClient.exe sametime-config/web/downloads/.
```
The managed-settings.xml file must be named managed-settings.xml. If you require more than one managed-settings.xml file, you must place those files in different folders on the web server.
Optional: Create additional directories in the downloads folder. For example, create a folder named default under that tree.
```
sametime-config/web/downloads/default/
```
The Sametime client looks in the folder specified in the policy for both a managed-settings.xml and a managed-community-configs.xml. If you are using both types of files, the URL defined in the policy must be scoped to the folder path where the two files reside.
If you need to support multiple policies containing different managed-settings.xml and managed-community-configs.xml files, then place them in folders with different names.
For example:
```
http://www.example.com/default 

http://www.example.com/nomeetings
```
Note: Do not use the following special characters in your folder names
- Ampersand (&)
- Apostrophe(‘)
- Quotation mark (“)
- Greater than character (>)
- Less than character (<)
- backslash character (\)
- Forward slash (/)
- spaces ( )
- hash symbol (#)

What to do next

Updating the client policy to include the managed settings URL.