TASKING Local License Server v2.1r1
Release Note

Scope

This release note covers the changes between v2.0r1 and v2.1r1 of the TASKING Local License Server. For release notes prior to v2.1r1, please see the TASKING License Management online documentation

Contents

Important Information

You do not need to install the TASKING Local License Server if the licenses for your TASKING products are serviced by the TASKING Remote License Server, or if you use a node-locked client based license.

The TASKING Local License Server is protected with a node-locked license. Therefore, you cannot move the TASKING Local License Server to another computer once the node-locked license has been acquired.

It is strongly adviced that you update to the latest TASKING Local License Server to experience the latest licensing features in TASKING products and to mitigate any potential incompatibilities with the latest Microsoft Windows versions and Linux distributions.

It is advised that you install the TASKING Local License Server before you install products that require this server.

It is advised to install the TASKING Local License Server as a service on Windows, or as a daemon on Linux and on a computer which is permanently running, otherwise TASKING products which use the server cannot get a license.

If you like to setup up a TASKING Local License Server, we kindly refer you to the TASKING License Management manual or the TASKING License Management (TLM) Support page on our website for more information.

TASKING Local License Server is a 64-bit product. It shall be installed on 64-bit versions of the Microsoft Windows or Linux operating system.

New in v2.1r1

Support for TASKING winIDEA

This version of the TASKING Local License Server also supports new releases of TASKING winIDEA products.

See the respective TASKING winIDEA product for additional information.

Support for Licenses in Multiple License Pools

With this version of the Local License Server you can now specify that a particular license can be part of multiple license pools.

This allows you to define license pools for different geographic regions and include a global license.

You can do this by specifying multiple POOL names on a single line.

For example:

POOL-EURO-PE__-____
# put your country licenses for Europe here
  ...

POOL-ASIA-____-____
# put your country licenses for Asia here
  ...

POOL-USA_-____-____
# put your country licenses for USA here
  ...

POOL-EURO-PE__-____ POOL-ASIA-____-____ POOL-USA_-____-____
# put your global licenses here
  ...

Pool names for TASKING products built with TLM v1.5r1 or higher have the syntax POOL-name, where the name is free to choose from 1 up to 14 characters. Pool names are also supported with existing TASKING products that have been built with an older version of TLM, as long as you use the new local license server and specify the pool names in the fixed format
POOL-xxxx-xxxx-xxxx.
Note that you also need to use this fixed pool name format if you are mixing older and newer TASKING products.

Support for Licenses with a Software Maintenance End Date

Support has been added to use licenses with a specified software maintenance end date.

Better Support for Comments

In all license files (licopt.txt, licdopt.txt, licfile.txt, licdfile.txt, licdaccess.txt) you can add comments, not only on a separate comment line, but also at the end of a line. Comments start with the # character.

For example:

# sample comment in a licdaccess.txt file
deny user all
permit user eric # allow access to user eric only

Wait for Available Process

In TASKING products built with TLM v2.1r1, you can set the TSK_PROCESS_WAIT option in licopt.txt, or as an environment variable, to the parallel process time-out (default: unlimited). This specifies the number of seconds the system is allowed to wait for a process to run if the maximum number of parallel processes permitted by the license is already running.

See the release note of the respective TASKING product for the availability of this feature.

Fixed Issues in v2.1r1