In this section:

Introduction

Two distributions of License Server are available:

A self-deployed distribution packaged with its own Apache Tomcat server
A web archive (.war) distribution for deploying to your own servlet container

Both distributions include the User Administration module (pstsec), which enables you to manage user access to Parasoft applications and license tokens.

Host Requirements

The License Server host machine should meet the following minimum hardware requirements:

RAM: 2GB
Disk space: 1GB
Linux or Windows (64-bit only)

The are no additional requirements for the self-deployed distribution.

A distribution with Linux kernel 3.10 or above is required to use the v2 license (beta).

Web Archive Deployment Requirements

Your environment should meet the following requirements to deploy the .war distribution:

The host machine should meet the Host Requirements
Linux or Windows (64-bit only)
Tomcat 9.0.x configured for SSL over port 8443. Refer to the Apache Tomcat documentation for details on configuring Tomcat: Apache Tomcat SSL/TLS Configuration HOW-TO topic.
Java 8 - License Server has been tested with the following distributions:
- Oracle JDK
- Zulu OpenJDK

License Server Structure

The License Server distribution contains an app directory and a data directory. This structure facilitates greater reliability when deploying License Server to containerized systems, such as Docker.

The app directory contains the Tomcat server, startup and shutdown scripts, and other files responsible for running License Server.
The data directory contains log files, configuration files, and other files responsible for ensuring that License Server runs as intended.

Installing the Self-deployed License Server Distribution

Extract the contents of the installation package to any location. The <LS_INSTALL>/app directory includes the JRE, Tomcat, and scripts for starting and stopping the server.
Run the startLS script as an administrator to launch License Server. The application will run on the Tomcat server shipped in the installation package.
Open a browser and go to one of the following URLs to access the License Server interface:
- http://<HOST>:8080/licenseserver
- https://<HOST>:8443/licenseserver
Log into License Server using the default user name and password (admin/admin). We recommend changing the default once you log in.

Run the stopLS script located in the 'license-server' directory to stop License Server.

Deploying License Server to a Custom Tomcat Server

Extract the contents of the distribution archive and copy the licenseserver.war and pstsec.war files into your <TOMCAT>/webapps directory. The applications will be deployed when Tomcat starts.

Log into License Server at https://<host>:8443/licenseserver using the default username and password (admin/admin). We recommend changing the default after logging in.

Log into User Administration at https://<host>:8443/pstsec using the default username and password (admin/admin). We recommend changing the default after logging in.

Deploying Licenser Server Inside a Docker Image

License Server cannot be re-deployed or hosted by another Docker environment once you run it inside a Docker container. Use the following command to start a container from the image the first time:

docker run -i -t <image>

You will need to include the container ID to stop and start the Docker container hosting License Server. Use the following command to get the container ID based on the image from Docker.

docker ps

Run the following command to shut the container down:

docker stop <containerId>

Run the following command to start the container back up:

docker start <containerId>

Removing the Docker container and spawning a new container from the image, even with mapped persistent storage, is not supported.

HASP Key Support

You can install Parasoft software on different machines and use a USB HASP Key to provide a machine ID when connecting to License Server. The USB dongle provides a stable machine ID for License Server so that the rest of the hardware can be changed without needing to request new licenses from Parasoft. Contact your Parasoft representative for additional information.

Enabling HASP Key on Windows

Run the stopLS.bat script located in the <LS_INSTALL>/app directory to stop Tomcat Server.
Open stopLS.bat file in an editor and add the -DuseExternalLock=true argument to the JAVA_OPTS configuration:
```
set JAVA_OPTS=%JAVA_OPTS% -DuseExternalLock=true 
```
Run the startLS.bat script located in the <LS_INSTALL>/app directory to start Tomcat Server.

When the USB HASP key is removed, the machine ID will revert to the original ID. As a result, License Server will no longer provide licenses.

Enabling HASP Key on Linux

Run the stopLS.sh script located in the <LS_INSTALL>/app directory to stop Tomcat Server.
Open stopLS.sh file in an editor and add the -DuseExternalLock=true argument to the JAVA_OPTS configuration:
```
export JAVA_OPTS=%JAVA_OPTS% -DuseExternalLock=true 
```
By default, USB devices are configured with 66* permissions, but USB HASP keys require 666. Locate the udev.rules file responsible for USB devices on your Linux distribution and modify the usb_device entry to use MODE="0666". On Ubuntu 18.04, for example, the configuration would be set in the 50-udev-default.rules file located in the /lib/udev/rules.d/ directory.
Execute the following command:
```
udevadm control --reload-rules 
```
Plug the USB HASP key into your machine. If the USB HASP key is already plugged in, run the following command as the root user to programmatically insert key:
```
udevadm trigger 
```
Run the startLS.sh script located in the <LS_INSTALL>/app directory to start Tomcat Server.