Installing Sentinel LDK Run-time Environment on a Linux machine

NOTE When installing Sentinel LDK Run-time Environment on an end user's machine: To support your application on both 32-bit and 64-bit architectures, ensure that you provide both 32-bit and 64-bit customized Vendor libraries with the Run-time Environment installer. These libraries are contained in the following files:

>haspvlib_<vendorID>.so

>haspvlib_x86_64_<vendorID>.so

>haspvlib_armhf_<vendorID>.so

>haspvlib_arm64_<vendorID>.so

To install the Sentinel LDK Run-time Environment using RPM or DEB:

1.Go the Sentinel LDK Linux directory on your Linux machine. For more information, see the Sentinel LDK Getting Started Guide for Linux.

2.Disconnect your Sentinel HL key (if any) from the machine.

3.Open a terminal window and navigate to Linux/Redistribute/Runtime.

4.As root, enter the following command:

•For RedHat, SUSE, or CentOS 32-bit ARM systems:

rpm -i aksusbd-10.31-1.armv7hl.rpm

•For RedHat, SUSE, or CentOS 64-bit ARM systems:

rpm -i aksusbd-10.31-1.aarch64.rpm

•For RedHat, SUSE, or CentOS 64-bit Intel systems:

rpm -i aksusbd-10.31-1.x86_64.rpm

•For Ubuntu or Debian 32-bit ARM systems:

dpkg -i aksusbd_10.31-1_armhf.deb

•For Ubuntu or Debian 64-bit ARM systems:

dpkg -i aksusbd_10.31-1_arm64.deb

•For Ubuntu or Debian 64-bit Intel systems:

dpkg -i aksusbd_10.31-1_amd64.deb

NOTE All install/uninstall commands must be executed with root rights. In Ubuntu, prefix the commands with the sudo command; in other distributions, use the su utility to become root in the terminal window.

The Sentinel LDK Run-time Environment is launched.

5.Reconnect the Sentinel HL key (if any).

NOTE At this point, for older HASP HL keys, the firmware on the HL key may be automatically upgraded. During the upgrade process, the key will blink continuously. Do not remove the key while it is blinking. If you remove the key too soon, the key may no longer be visible in Admin Control Center. If the key is not visible, or if the upgrade does not occur, see Upgrading HASP HL Key Firmware.

To install the Sentinel LDK Run-time Environment from a script:

(Use this procedure if the distribution does not support RPM or DEB.)

1.Go the Sentinel LDK Linux directory on your Linux machine. For more information, see the Sentinel LDK Getting Started Guide for Linux.

2.Disconnect your Sentinel HL key (if any) from the machine.

3.Copy the package Linux/Redistribute/Runtime/aksusbd-10.31.1.tar.gz to a local directory.

4.Open a terminal window in the local directory.

5.Enter the following command to uncompress the package containing the Run-time Environment installer:

tar zxvf aksusbd-10.31.1.tar.gz

6.Enter the following command to change to the directory containing the installer:

cd aksusbd-10.31.1

7.As root, enter the command: ./dinst

The Sentinel LDK Run-time Environment is launched.

8.Reconnect the Sentinel HL key (if any).

Installing Sentinel LDK Run-time Environment in Docker

Docker containers require a different run-time configuration because they do not support system-level daemons.

The Sentinel LDK Run-time Environment installer starts the Sentinel License Manager service as a daemon. This behavior is not compatible with most Docker environments. Therefore, configure the run-time components manually.

For more information about docker support, see the Sentinel LDK Software Protection and Licensing Guide.

Before you begin:

•Ensure Docker is installed on the host machine.

•Download the aksusbd-<version>.tar.gz Sentinel LDK Linux installer. For example, aksusbd-10.31.1.tar.gz.

NOTE

>The Sentinel LDK Envelope is not natively supported on standard Alpine Linux because it requires a glibc-based runtime environment.

>To use SL AdminMode licensing or Sentinel LDK Envelope in Docker containers based on Alpine Linux, use a glibc-enabled image (for example, frolvlad/alpine-glibc), because standard Alpine Linux uses musl libc, which is not compatible with the glibc-based Sentinel LDK License Manager.

Configure SL AdminMode Runtime in Docker

SL AdminMode uses the Sentinel License Manager service (hasplmd). Use manual configuration for the License Manager because the Sentinel LDK Run-time Environment installer is not compatible with Docker.

1.Extract the Sentinel LDK installer archive.

tar -xzf aksusbd-<version>.tar.gz

For example, tar -xzf aksusbd-10.31.1.tar.gz.

The extracted package contains the License Manager binary (bin/hasplmd_x86_64) and Admin Control Center template files (bin/*.alp).

2.Create a non-root user and group in the Docker image to run the License Manager and the application.

3.Create the directories required for the License Manager and assign ownership to the non-root user:

•/etc/hasplm: Stores configuration files.

•/etc/hasplm/templates: Stores Admin Control Center template files.

•/var/hasplm: Stores vendor libraries.

•/var/hasplm/installed/<vendor_id>: Stores license files.

The <vendor_id> represents the vendor ID for your Batch Code.

4.Copy runtime files from the installer package into the container image:

•Copy hasplmd_x86_64 to the working directory.

•Copy .alp files to /etc/hasplm/templates/.

•Copy hasplm.ini to /etc/hasplm/ or map it from host machine.

NOTE To allow access to the Admin Control Center (ACC) from outside the container, provide a hasplm.ini file with the following settings in the [SERVER] section:

>Set accessfromremote = anyone to permit remote connections.

>Set accremote = 1 and adminremote = 1 to enable remote administration.

>Define a trusted_ip range to restrict access to specific networks.

5.Copy the vendor library file for the Batch Code to the following directory:

/var/hasplm/

6.Set executable permissions for the License Manager binary:

chmod +x hasplmd_x86_64

7.Expose the required port in the Dockerfile. Port 1947 or port 80 supports both the License Manager and the Admin Control Center.

8.Start the License Manager in foreground mode (-f) inside the container.

NOTE When using an entrypoint script to launch the container, use the following practices:

>Start the hasplmd_x86_64 process in foreground mode using the -f flag. This allows Docker to monitor the process state effectively.

>Implement a wait loop to confirm the License Manager is active before the script launches the protected application.

>Use pgrep -f hasplmd_x86_64 to verify the service status during the startup phase.