Home
Licensing
Details on the licensing solution of PLA 3.0, the available licensing options, and the activation and management of licenses.
Licenses on a license server
By default, clients can access all Sentinel license servers running in the same subnet. If you operate several subnets or want to restrict the access of clients to a license server, you have to control the access accordingly.
Restrict access on the client side
If a client should only be able to access specific Sentinel license servers, you have to restrict the access accordingly. You can also configure a sequence according to which a client should connect to servers.

Get started
Explore PLA 3.0, its key features and ongoing enhancements. Learn how it fits into your environment, and how to log in and register.
User interface
PLA 3.0 supports you in your daily work by providing a set of graphical and textual user interface elements. Learn about the different elements and how to use them efficiently.
Key concepts
Details on documents and templates, the data editors and the Content editor of PLA 3.0.
Data analysis
Data analysis add-ons offer a wide range of capabilities, ranging from analytical methods over comprehensive analysis to statistical process control. PLA 3.0 also provides a set of add-ons that support and supplement data analysis add-ons.
Data import
Use data acquisition and data import add-ons to import external response values and observation data into PLA 3.0 for further processing and evaluation.
Installation
Details on the deployment and installation of licensed PLA 3.0 versions.
Licensing
Details on the licensing solution of PLA 3.0, the available licensing options, and the activation and management of licenses.
- Licensing options
  The licensing option determines the number of users who can access PLA 3.0 at the same time. It also determines the number of computers on which you can install PLA 3.0.
- Information packages
  Information packages play a central role in the installation and licensing process. They contain key data required to get PLA 3.0 up and running in your environment.
- Activate your license
  To activate your PLA 3.0 license, you install a software key on the computer or license server that should hold the PLA 3.0 license. Activating the PLA 3.0 license automatically activates the license keys for your add-ons.
- Transfer your license
  PLA 3.0 licenses are tied to the computer to which you apply the vendor-to-customer (.v2c) file. Before you change the hardware or operating system of this computer, you have to temporarily transfer the license to a different computer.
- Manage existing licenses
  Learn how to increase the number of concurrent users, replace a hardware key with a software key, or cross-upgrade from a Seat license to a Concurrent use license.
- Licenses on a license server
  By default, clients can access all Sentinel license servers running in the same subnet. If you operate several subnets or want to restrict the access of clients to a license server, you have to control the access accordingly.
  - Configure licensing across subnets
    If a Sentinel license server and its clients are running in different subnets, you have to allow clients to broadcast across the whole network.
  - Restrict access on the server side
    If only specific clients should be allowed to access a Sentinel license server, you have to restrict the access accordingly.
  - Restrict access on the client side
    If a client should only be able to access specific Sentinel license servers, you have to restrict the access accordingly. You can also configure a sequence according to which a client should connect to servers.
- Legacy protection keys
  We recommend software keys for license activation. However, we also support legacy protection keys, namely hardware-based Sentinel protection keys and hardlock keys.
Administration
Details on system administration tasks such as setup and maintenance of databases and add-ons, user accounts, access rights, and migration and update procedures.
Regulatory compliance
PLA 3.0 supports you in achieving compliance with regulations such as ISPE GAMP^® 5 and 21 CFR Part 11. It also provides options to validate PLA 3.0 in your environment.
PDF downloads
Download PDF guides of current and previous framework and add-on versions.
Sample lab
Meet the team of Stegmann Labs Inc. and use our sample laboratory to explore core features and functions of PLA 3.0.
Glossary
Find definitions of terms.

Restrict access on the client side

If a client should only be able to access specific Sentinel license servers, you have to restrict the access accordingly. You can also configure a sequence according to which a client should connect to servers.

About this task

The configuration is done in the pla.properties file of the respective client. You can edit this file in any standard text editor.

Note: We recommend you close all PLA 3.0 applications during the configuration process.

Procedure

To restrict access on the client side:

Open the pla.properties file.
Add or modify key=value pairs according to your requirements.

Important: The key=value pairs you define here filter the list of Sentinel license servers configured in the PLA License Control Center. You cannot add additional servers.

Add one value to configure a specific server, or a semicolon-separated list to configure a sequence of servers.

The following keys are available:

com.stegmannsystems.edp.license.HaspTargetIPs

Restricts the access of a client to a license server based on the IP address of the server.

Add one value to configure a specific server, or a semicolon-separated list to configure a sequence of servers. The sequence of the entries determines their priority. Entries listed first take precedence.

Example: com.stegmannsystems.edp.license.HaspTargetIPs=192.168.1.111;192.20.100.20

com.stegmannsystems.edp.license.HaspTargetHostnames

Restricts the access of a client to a license server based on the hostname of the server.

Specify the computer name only, do not add the domain. Add one value to configure a specific server, or a semicolon-separated list to configure a sequence of servers. The sequence of the entries determines their priority. Entries listed first take precedence.

Example: com.stegmannsystems.edp.license.HaspTargetHostnames=WJKA03;WDO02;EMS7

Note: If you configure hostnames and IP addresses, hostnames take precedence.

com.stegmannsystems.edp.license.Providers

Restricts the access of a client to a license server based on the provider of the protection key.

Valid values are hasp for Sentinel software and hardware protection keys and hardlock for hardlock keys.

Example: com.stegmannsystems.edp.license.Providers=hasp
Save the pla.properties file and close it.