Version Upgrade Behavior
On Windows and Linux, an existing HCL Local License Server (LLS) installation can be upgraded to a later version, and the licenses, logs, TLS certificate, and port are retained. A Docker deployment cannot be upgraded in place.
Windows
Only one LLS instance should be present on the host before an upgrade. If more than one version is present on the same machine, uninstall the versions that are no longer needed before running the installer.
Version upgrade is supported on Windows. If an earlier version is already installed, the installer detects it and offers to upgrade:
Detected installed service: HCL Local License Server 5.3.0
Installed version: [5.3.0]
Existing installation directory: "C:\LLS_Directory"
Do you want to upgrade to 5.4.0? (Y/N): Y
If the upgrade continues, the installer then asks whether to install in the same directory:
Upgrade in the same directory (C:\LLS_Directory)? (Y to use same, N to customize):
- Type Y to upgrade in the existing directory.
- Type N to specify a different installation directory.
In both cases a backup of the earlier version is created in the backup directory and restored into the new version automatically, so the license files, logs, TLS certificate, and port setting carry over. The installer does not prompt for the certificate, key, or port. For details of what is preserved and where the backup is stored, see Backup and Restore.
No confirmation is requested for restoring the backup during a version upgrade. The backup is always restored as part of the version upgrade behavior.
Linux
Version upgrade is supported on Linux from 5.3 and its patch releases, such as 5.3.1. If a supported version is already installed, the installer detects it and offers to upgrade:
Detected installed service: HCL-Local-License-Server-5.3.0
Installed version: [5.3.0]
Existing installation directory: "/opt/hcl-lls"
Do you want to upgrade to 5.4.0? (Y/N): Y
A backup of the earlier version is created in the backup directory and restored into the new version automatically, so the license files, logs, TLS certificate, and port setting carry over. The installer does not prompt for the certificate, key, or port. For details of what is preserved and where the backup is stored, see Backup and Restore.
LLS installs into /opt/hcl-lls on Linux, and the installer does not prompt for an installation directory.
Versions earlier than 5.3 cannot be upgraded, because they are not installed in /opt/hcl-lls, which is the directory the upgrade acts on.
Do not run the 5.4 installer over such an installation. The installer may detect the old service by name and offer to upgrade, but the two are not compatible and the installation malfunctions. Uninstall the earlier version first, using the steps that follow.
To move to 5.4 from a version earlier than 5.3:
- Copy the license files and the TLS certificate and key from the existing installation directory to a safe location.
- Uninstall the earlier version by running the uninstall.sh file from its installation directory.
- Remove the earlier installation directory if it still exists.
- Install 5.4. See First Time Installation.
Docker
A Docker deployment cannot be upgraded in place and always requires a new installation.
Backup and restore does not apply to a Docker deployment. Before you remove the existing deployment, copy the license files from the licenses folder and the TLS certificate and key from the certs folder to another location.
The database folder cannot be carried over to a new deployment. It holds the value the fingerprint is derived from, and that value is generated afresh when a new deployment is installed. A new deployment therefore has a new fingerprint, and a new license file must be generated from MHS. The logs folder cannot be carried over either.
Installing an earlier or identical version
The installer does not install a version that is the same as, or earlier than, the version already installed. A message similar to the following is displayed and the installation stops:
You already have a higher or the same version [5.4.0] installed. If you still wish to
downgrade to [5.3.0], we recommend uninstalling the existing version manually by running
the uninstall script from the existing installation directory and then try installing again.
To install an earlier version, uninstall the current version first by running the uninstall.bat/sh file from its installation directory, and then run the installer for the required version.
Running the uninstall.bat/sh file creates a backup, so the installer for the earlier version detects it and displays a prompt to restore the licenses, logs, certificate, and port. See Backup and Restore.