First Time Installation

Install HCL Local License Server (LLS) 5.4 on a host machine where no previous version is installed. The procedure is the same for a native installation and a Docker deployment.

Note:

For a Docker deployment, an existing installation cannot be upgraded in place.

Procedure

Go to the directory where the installer package is located. The location depends on the installer package you downloaded.


Package	Name	Location
Native, Windows	install.bat	<unzipped-installer-package>\install.bat
Native, Linux	install.sh	<unzipped-installer-package>/install.sh
Docker, Windows	install.bat	<unzipped-installer-package>\Windows\install.bat
Docker, Linux	install.sh	<unzipped-installer-package>/Linux/install.sh

From the command line, run the install.bat/sh file:
- On Windows, run the install.bat file as an administrator.
- On Linux, enter the following commands with root privileges:
```
chmod +x install.sh
```
```
./install.sh
```

Provide configuration information when prompted by the installer.

On Windows, specify the installation path for LLS when you are prompted. On Linux, the installation directory is fixed and you are not prompted for it.


Deployment	Linux	Windows
Native	Always /opt/hcl-lls. Not prompted.	Prompted.
Docker	Always /opt/hcl-lls-docker. Not prompted.	Prompted. The directory must be empty.

On Windows, avoid installing in system or user-specific directories such as C:\Program Files or C:\Windows. Install in a non-system directory, for example C:\HCL_LLS5.4.
A licenses folder is created automatically in the installation path to store license files. You can add license files at any time after installation.

Enter the TLS Certificate:

Provide the full path to the certificate file generated by the certificate utility or obtained from a third-party CA.

Example: C:\HCL_LLS5.4\certificates\server.crt
Note:
- The valid format is PEM (.crt).
- The certificate chain must follow this order: Server certificate → Intermediate certificate → Root certificate
- Keep track of TLS certificate expiry dates and renew before expiry. LLS does not send expiry notifications.
Enter the TLS Key:
- Provide the path to the private key file. Example: C:\HCL_LLS5.4\certificates\server.key
- If the key is encrypted, you can enter the passphrase when prompted.

Enter the Port Number:

Specify the port on which LLS runs. The recommended port is 443. You can also use any port between 1024 and 65535.

A fingerprint is generated automatically and is displayed in the console. The prefix depends on the deployment method:


Deployment	Prefix	Derived from
Native	`v3.lls.`	The host MAC address and the port
Docker	`v3.lls.uid.`	A per-instance value stored in the database folder, and the port

The following example shows a completed fingerprint generation for a native installation:

Enter the port number (port:443 preferred): 8080

Generating fingerprint...
Fingerprint: v3.lls.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Fingerprint generated successfully.

For a Docker deployment, the fingerprint is in the following form:

Fingerprint: v3.lls.uid.5bc916f2a1d89ada04d979c6c345143d7b04e5095f58cf8bc677eb4b2852a369
Fingerprint generated successfully.

Note:

Fingerprint details are displayed in the console and also saved to installer.txt, together with the deployment type, the port, and the TLS certificate status.
Copy the full fingerprint, including its prefix, for license activation.

Important:

The following applies to native installations, where the fingerprint is derived from the host MAC address.

The MAC address used for fingerprint generation is automatically selected from the available network interfaces at the time of installation.
If a temporary or unstable network adapter (such as Wi-Fi that may be disabled, disconnected, or removed later) is used, it can lead to fingerprint mismatch errors during license activation or future validations.
To avoid issues, ensure that a stable and permanent network interface (typically a wired Ethernet adapter) is active during fingerprint creation.

For a native installation on Linux, provide the user account that the systemd service runs under when you are prompted:
```
Please provide the username for the user account that the systemd service should run under
(Please ensure that User has the necessary execute permissions for the installation directory):
```
Note:
- The account must already exist on the machine. If the name provided is not a valid user account, the prompt is repeated.
- The account must have execute permission for the installation directory.
- Ownership of the installation directory and the licenses folder is assigned to this account.
This step does not apply elsewhere.

A confirmation message is displayed:

[SC] CreateService SUCCESS
[SC] ChangeServiceConfig2 SUCCESS
The HCL Local License Server 5.4.0 service is starting.
The HCL Local License Server 5.4.0 service was started successfully.

The installer displays the most recent line from service.log, which reports the TLS certificate status:
```
2025/11/06 10:47:11 TLS certificate [Self-Signed, PEM] is valid. Expiry date: 2026-11-06 10:47:11 +0000 UTC
```
The same status is recorded in installer.txt on a TLS Certificate Status line, and in logs/hcl_lls.log.
Press any key to close the install.bat/sh file.

LLS is now installed on your system.

TLS expiry information is also logged in <lls_install_directory>/logs/hcl_lls.log.

For a Docker deployment, the installation directory contains the following files and folders:
```
docker-compose.yml     Service definition. Do not edit.
.env                   Port setting
config.json            TLS mode and log settings
update.bat / .sh       Update the TLS certificate or the port
uninstall.bat / .sh    Uninstall
utility.bat / .sh      Generate a self-signed certificate
installer.txt          Fingerprint, deployment type, port, and TLS certificate status
service.log            Startup and license processing log
certs/                 TLS certificate and key
licenses/              License files
logs/                  hcl_lls.log, hcl_lls_features.log, hcl_lls_pools.log
database/              License database. Persistent - do not delete.
```
Important:

Do not delete the database folder. It holds the per-instance value that the fingerprint is derived from. If the folder is deleted or replaced, the fingerprint changes and the existing license files are no longer valid.

Note:

For a Docker deployment, the container restarts automatically if the host is restarted or the container stops unexpectedly.
Generate your license file. See Post-installation: Generating the license file. Place the generated license file in <lls_install_directory>/licenses.

Note:

License file management is independent of the LLS installation. You can add or remove license files at any time. Any update in the licenses folder is logged automatically in <lls_install_directory>/logs/hcl_lls_features.log.

What to do next

Verify the server installation. See Verifying HCL Local License Server Installation.
Retrieve the following details:
- The Pool ID, from <lls_install_directory>/logs/hcl_lls_pools.log or from the API endpoint https://<FQDNhostname>:<LLSport>/v1/licensepools.
- The LLS URL, from <lls_install_directory>/logs/hcl_lls_features.log, which you need to configure product licenses.

For an upgrade from an earlier version rather than a first-time installation, see Version Upgrade Behavior and Backup and Restore.