What are concurrency and activation counts?
A single LDK license can permit multiple RIPs to be run concurrently. This has some similarities with the use of permit files in HLS, but allows for significantly more flexibility.
Each RIP license has a defined activation count and concurrency:
The activation count defines the number of computers that the license can be activated on. This sets the number of instances of the LDK licensing server that can run concurrently.
- Each activation results in a different Protection Key ID, because the Protection Key ID uniquely identifies the association of the license with a single computer (or dongle).
- The concurrency of a license defines the number of RIPs that are allowed to obtain their entitlement to run from a single activation on a single LDK licensing server.
The maximum number of RIPs that can be run from a single RIP license is therefore the product of the activation count, multiplied by the concurrency.
Normal LDK licenses for most OEMs will allow a single activation and a concurrency of 1, meaning that they will enable one RIP.
Do all RIPs need to be on the same computer?
Each license defines whether RIPs must be running on the same computer as the LDK licensing server (nodelocked licenses) or can run on other computers, communicating with LDK across the network (floating, or network licenses).
This enables two basic models (although variations are possible):
- A single instance of the LDK Server runs on one machine and serves licenses to RIPs running on other machines (and optionally also the computer on which the LDK Server is running). This would use 1 activation, multiple concurrency and floating licenses.
- Every computer in an installation runs both an LDK Server and one or more RIPs, with the RIPs obtaining their licenses from the local LDK Server. This would use multiple activations (one per computer), single or multiple concurrency (depending on the number of RIPs per computer) and node‐locked licenses.
If you believe that using licenses that will enable multiple RIPs across a network are appropriate for any of your current or potential use cases contact your account manager. Note, however, that network licenses on arbitrary networks should be treated as beta status until further information is available. More information on setting up a system on multiple computers (including remote use of the LDK Server) is set out in Technote Hqn089—“Securing multiple RIPs using the Sentinel LDK”.
How are RIP serial numbers set when a single license provides multiple licenses?
All of the RIPs enabled from a single license, whether using multiple activations, a concurrency higher than 1 or both, will have the same RIP serial number.
This is the same as when using HLS permit files, where every RIP licensed through a single permit file has the same RIP serial number.
How do I add an option to a license with multiple activations?
If you add a plugin, layered option, localization and so on to an activated license (identified via its Protection Key ID) it will be applied to all RIPs licensed from the LDK licensing server running on that activation. If the RIP license allows for multiple activations, you will receive a Product Key for a Protection Key Update for every one of those Protection Key IDs that has already been activated. This is intended to ensure that all RIPs from a single license are kept in synch, with the same set of options, plugins, and so on.
As an example, if you have a license with three activations and a concurrency of four it will allow you to run 12 (3 x 4) RIPs. If you then purchase TrapPro to add to that license it may cost 12 times as much as the standard license for a single copy of TrapPro.
Can I activate multiple licenses on a single computer?
It is possible to activate multiple, independent Harlequin RIP licenses on a single computer and then to run multiple RIPs using those licenses, which would allow different RIPs to be given different serial numbers.
You should be aware that each RIP will be given thelicenses in the order in which they were activated when started up; if you do not start up the RIPs in the same order every time, each RIP will get different licensed options and a different serial number each time, which may cause problems.
For this reason if you need to run multiple RIPs on the same computer, it is recommended that you use a single LDK license with multiple concurrency, rather than multiple, independent licenses.
This is exactly the same as if multiple HLS RIP licenses were used on the same computer.
How do these options interact with VM usage?
It is possible to set up the LDK Server on one computer and run one or more RIPs on additional computers, using network licenses.
The choice of a soft‐lock or a VM‐lock must be defined for the operating system on which the LDK Server itself is running, not the RIPs themselves.
It is therefore possible to run an LDK Server on a bare‐metal OS with a soft‐lock, serving licenses across the network to enable RIPs running on VMs on other computers. In comparison with using a VM‐lock locally on each computer this has the advantages that:
- The soft‐lock may be re‐hosted for planned computer upgrades.
- The RIPs may run in VMs in a cluster environment that moves them dynamically from one physical host to another, or that changes their MAC addresses.
Conversely, it also means that:
- There is a single point of failure for multiple RIPs — the LDK Server.
- A fault in network access between RIPs and the LDK Server will prevent the RIPs from running.