Monitoring IBM Rational token based licenses - KB4001a2
Israel +972 4 6308447      USA +1 619 831 0029         UK +44 203 807 9405         JAPAN +81 505 893 6263 担当:萩原

Monitoring IBM Rational token based licenses – KB4001a2

You are here:
< All Topics

Token licenses are a form of floating license, only that instead of having a pool of licenses they have a pool of tokens. When a feature is checked-out, a predefined amount of tokens is consumed. The number of consumed tokens is specific to each feature, and is apparent in the feature/Increment line in the license file. When the application is closed, the tokens are returned to the pool for other end users to use.


Changes made in TLSTOK reporting

The IBM Rational licenses are managed by the FlexLM license manager. As such, OpenLM is capable of monitoring IBM Rational license consumption and provide usage reports on the EasyAdmin web application.

The process of interfacing the FlexLM license manager is elaborated in this article.

In previous versions, OpenLM would only present the IBM Rational token feature (TLSTOK), and would not elaborate on the consumption of actual features within TLSTOK. With the latest OpenLM 3.1 update, OpenLM treats the TLSTOK feature as package, and all its token based features as part of that package.



In order to obtain IBM Rational feature usage reports, the OpenLM system must be configured to

1. Monitor the IBM Rational Flexlm license manager

2. Employ an OpenLM Broker on the license server machine and

3. Read the IBM Rational license file.

Please read the following Application note for more information:

Configuring OpenLM to interface the FlexLM license manager

Specifically relate to the “OpenLM Broker configuration for FlexLM” and “Obtaining License file information” paragraphs.


OpenLM Server configuration example

In the example below, the OpenLM Server is configured to monitor an IBM Rational license manager (‘my_lm_host’) on port 27000.


OpenLM Broker configuration example


The Broker is configured to monitor the same License server (my_lm_host) on that same port (27000). The “Watch license file” has been checked, and the IBM Rational license file’s full path has been introduced into the path text box.


License file case study

The license file in this case contains a number of licensed features within the TLSTOK package, and a single licensed feature (ibmida) that is exterior to that package.

SERVER <server_name> <MAC_address> 27000

VENDOR ibmratl

INCREMENT ibmida ibmratl <version> permanent <number> DUP_GROUP=UH \

        vendor_info= “..."IBM InfoSphere Data Architect Floating License key…”



vendor_info="... Rational Main Token Feature|0"

INCREMENT Change telelogic ...

        VENDOR_STRING=IBM:t,TLSTOK,1.0,Change,5 …


INCREMENT LT_Playback_1000VU rational …

VENDOR_STRING= …  IBM:t,TLSTOK … LT_Playback_1000VU , 69 …

The IBM Rational license file makes use of several vendor names, e.g: ibmratl, telelogic and rational. OpenLM treats all these vendor types as one, unifying usage under a single vendor name: ibmratl.


EasyAdmin Licenses window

The “Main Token feature” (TLSTOK) is displayed as a package, with a + sign on its left.

Expand the + sign to display the token based features members of TLSTOK.

The Token cost of each member feature is displayed in the ‘Cost (Tokens)’ column, which is hidden by default. make it visible by clicking the down arrow on one of the columns:

Below is an EasyAdmin ‘Licenses’ report window, concurrent with the same license file.


  • The ibmida feature standing alone from the TLSTOK package
  • 5 licenses allocated for ‘Change’ and 69 licenses for ‘LT_Playback_1000VU ’ within the TLSTOK package.


EasyAdmin “License Usage” historical report window

License Usage may be reported for both the TLSTOK ‘Main Token Feature’ as well as per member feature.


EasyAdmin “Currently Consumed Licenses” real-time usage report window

Concurrent IBM Rational license usage is presented in the “Currently Consumed Licenses” window. Note the usage of all consumed ‘ibmratl’ licenses, presented with their respective “consumed tokens”.

Previous Monitoring Bentley SELECT License Manager – KB
Next Obtaining consumption reports from cloud-based managers – KB807
Table of Contents