Upgrading on Docker
Before you begin
To install a new version or fix pack, the following conditions must be satisfied:
- HCL Sametime 12 version is installed and configured
- Sametime server has access to a MongoDB server
About this task
Creating a backup of the installation directory, allows you to return to your previous version if a problem occurs related to installing the fix pack.
Note:
- Make a backup of your key files, such as docker-compose.yml and any customized files on the system so that you can validate any custom settings from the previous installation. If you have placed files in the sametime-config folder like custom branding or TLS certificates, those files need to be restored after the fix pack is installed. For the docker-compose.yml file, after the upgrade reference the backup version and add the modifications to the new docker-compose.yml provided during the upgrade. Changes to the custom.env and .env files are retained when upgrading to version 12.0.1 and later.
- The docker-compose.yml file is replaced during the upgrade with a newer version. Do not restore this file from a previous version after the upgrade. Any needed modifications need to be implemented again in the new file version.
Procedure
-
In the directory where Sametime is installed, issue the following command to
stop the Sametime server.
docker-compose down
-
Make a copy of the Sametime installation directory as a backup before
installing the fix pack.
Copy the contents of the installation directory into another directory. For example, /sametime_install_backup where sametime_install is the Sametime installation directory.
-
Download and decompress the Sametime fix pack archive to the Sametime
installation directory.
unzip sametime_fixpack_zip -d /sametime_install_path
-
In the sametime_install directory, run the following script
to initiate the installation process.
./install.sh
- Follow the prompts to provide the required information. The install process detects if the install is an upgrade or full install.