This release note covers the changes between v1.5r3 and v2.0r1 of the TASKING Local License Server. It also lists the most important features that have been added since v1.5r1.
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.
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.
Some TASKING licenses can be limited to a maximum number of parallel processes per user (seat). When the maximum number of parallel processes is reached a new client process is set to waiting until the number of running client processes under the same license seat is below the process limit.
Note that the improved handling of licenses with process limitation only works with TASKING products that have been built with this TLM version or newer.
See the release note of the respective TASKING product for the availability of this feature.
The licdstat tool and the LicD status webpage have been improved to show additional information about product licenses, such as maximum number of parallel processes.
In TASKING products built with TLM v2.0r1, you can set the
TSK_LOG_VERBOSE option in licopt.txt, or as an environment
variable, to different verbose levels.
With level 3 or higher, detailed license configuration information is shown, which is useful for debugging licensing problems. For example, it shows the environment variables or options used, the license key and the search path.
See the release note of the respective TASKING product for the availability of this feature.
You can now define a named pool of specific licenses on the local license server.
A license pool is useful to specify that the licenses for one or more products shall be grouped together. This can be the case for example when your license agreement has constraints on geographical location, such as a single site license, country license or continental license. In that case you can put all product licenses that are allowed to be used by a specific location into a license pool.
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.
The PRODUCT keyword has been deprecated, but still works for backwards compatibility.
The deny and permit rules have been extended to support a license key or a pool name.
The borrow deny and borrow permit rules have been extended to support a pool name.
The block rule has been deprecated, but is available for backwards compatibility only.
The access file is parsed for rules in this order:
bind rules to optionally enforce a key.user/system/ip.
The categories are AND-ed to find the resulting permit/deny.borrow request rules for each category user/system/ip.
The categories are AND-ed to find the resulting borrow permit/deny.Some issues in the parsing of the rules have been fixed which might affect your current access control list:
deny system all permit system all to key 1111-2222-3333-4444Old behavior: key 1111-2222-3333-4444 denied
borrow permit system all days 4 borrow permit ip all from 1111-2222-3333-4444 days 3 borrow permit ip all from 1111-2222-3333-4444 days 5Old behavior: borrow from 1111-2222-3333-4444 limited to 3 days
borrow deny system all borrow permit ip allOld behavior: everyone permitted
In TASKING products built with TLM v1.5r1 or higher, you can set the
TSK_LICENSE_WAIT option in licopt.txt to a configurable time period to wait
for a free license seat to become available instead of directly terminating when a license request is denied.
See the release note of the respective TASKING product for the availability of this feature.