Why don’t I see license denial reports in the Flexnet ( FlexLM ) debug log file ?

OpenLM provides a mean to monitor Flexnet publisher license denials. Please see this document for clarification. It does so by extracting information from  the FlexLM debug log file.

Denial reports may not appear in the FlexLM debug log if the application’s option file contains a NOLOG line, with a DENIED flag. If this is the case, edit the option file to exclude this flag, and restart the license server. See this document for more information.

Please follow and like us:

Application Note 1032: Monitoring FlexLM license denials

General:

OpenLM monitors and optimizes the usage of various license managers (e.g.: FlexLM / Flexnet publisher, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc).

As part of FlexLM license monitoring, OpenLM also produces license denial reports, i.e.: an account of instances where the vendor daemon has declined an application’s license request. License denial is a key parameter in license maintenance and in the planning of additional license procurement.

The Denials report window

License denial information is clearly presented in the OpenLM EasyAdmin web interface, in the Reports → Denials window. It includes the details of the denial event (Denied user, Denied workstation, Time, License Server, Denied Feature, and vendor) as well as the cause for denial (e.g.: limit of available licenses reached or User on Option file exclude list)

Set up OpenLM to monitor license denials

In order to produce denial reports for monitored licenses, please:
1. Set up the OpenLM Server to monitor the License server. In this case, the host is vmw_win2008_64, its type is FlexLM, the Server port is 27000, and the time zone is Central:

2. Install the OpenLM Broker on the License server machine:
Application Note 1004: OpenLM Broker quick start guide
Make sure that the License server name is exactly (case sensitive) the same as configured in the OpenLM server configuration tool (e.g.: vmw_win2008_64). The OpenLM server in this example resides in 102.101.100.135. The Broker communication port is (by default) 7016.

3. Set the OpenLM Broker to read the Denials’ information from the Monitored application’s debug log file: Type in the filename and click the ‘Enabled’ check box in the image below. Click ‘Apply’ and “Restart Broker” to finalize the configuration.

4. Make sure the Broker indication in the EasyAdmin “License Servers” window turns green. Note the green rectangle adjacent Server name vmw_win2008_64 in the image below. If it isn’t so – wait a while and refresh the “License servers” window. If it is still red – recheck your configuration, and check for alerts in the Easy Admin → Start → Management → Alerts window.

License number surpassed: Case study

In case the number of licenses has been surpassed – the vendor daemon would deny the license request, and a license denial notification will be produced. In the case of AutoCad: this is Network license error -96.

The debug log file shows this too as a string
Licensed number of users already reached. (-4,342)
Note the last denial report at 4:12:22 (Central time US):

It would also be apparent on the EasyAdmin Denial reports window at 11:12:22, according to the difference in time zones between the location of the OpenLM Server (Europe) and the AutoCad License server (Central time, US).

This same information can be presented as a column or pie chart, according to Users, Servers, Vendors, Features or time of occurrence.

Troubleshoot: Denials do not appear in the Flexnet debug log

Denial reports may not appear in the FlexLM debug log if the application’s option file contains a NOLOG line, with a DENIED flag. If this is the case, edit the option file to exclude this flag, and restart the license server. See this document for more information.

Document Revision Table

Version Author Date Changes
0.1 – Preliminary Orik Oct 25, 2012 Preliminary
1.0 Orik Dec 17, 2012 Added troubleshoot

 

Please follow and like us:

IBM Rational – FlexNet Token based licensing

IBM Rational license management using FLEXnet

The IBM Rational License Server uses FLEXnet (FlexLM) for licensing IBM Rational products.

FLEXnet main components

The four main components of FLEXnet are:

  • The License Manager Daemon, lmgrd

  • The Vendor Daemon, telelogic

  • The client application program, in this case any IBM Rational application

  • The license file, license.dat

Mode of employment

  • When an IBM Rational product is started, the program uses the TELELOGIC_LICENSE_FILE system variable to find out the name of the computer that’s running the FLEXnet license server and the port that it’s using.

  • The program contacts the license manager on the FLEXnet license server, using the specified port. It requests a floating license and makes the request for the Telelogic vendor daemon.

  • On the FLEXnet license server, the license manager sends the request to the Telelogic vendor daemon. The Telelogic vendor daemon checks to see if any licenses are available.

  • If there are free licenses, the Telelogic vendor daemon grants a license and the program runs. If there aren’t any licenses available, the Telelogic vendor daemon refuses the request, and the program fails to start and displays a license denial message.


Token-based licensing

Token licenses are in fact a form of floating license, only that instead of having a pool of licenses – it has a pool of tokens. When a feature is checked-out, a certain amount of tokens are 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.

Advantages of Token licensing

Having the ability to apply the acquired licenses to multiple products is an appealing concept:

  • Customers are not always aware of the full array of features they may acquire. having a token based license scheme ensures customer satisfaction from the license acquisition.

  • As development stages progress, customer needs change. They may require different licensed features, and eliminate the charge of “unused” software.

  • The entire license purchasing method is simplified. Customer can add/try new software during project, without new PO or evaluation process

Rational tools’ token-based licensing

IBM Rational license types

IBM Rational includes the following license types:

DOORS, Synergy, Change, Tau, System Architect, Focal Point, Rhapsody, Publishing Engine, Logiscope and Team Webtop

IBM Rational token license file examples

  • The Increment / Change line marks the number of tokens to be consumed:

INCREMENT Change telelogic 2015.04302 30-apr-2015 1 …

VENDOR_STRING=T10-999999:t,TLSTOK,1.0,Change,5  … // 5 Tokens worth.

  • This is an INCREMENT line indicating the total number of Tokens in the license

file. In this case, it is 200:

INCREMENT TLSTOK ibmratl 2.0 30-apr-2015 200 ISSUER=IBM

Rational License Server 8.1.1

Rational License Server 8.1.1 incorporates all vendor daemons (telelogic, rational, and ibmratl) into one. This change has also been incorporated into multiple Rational products such as ClearCase and ClearQuest.


References

http://publib.boulder.ibm.com/infocenter/rational/v0r0m0/index.jsp?topic=/com.ibm.rational.license.doc/topics/r_lic_log_file.html


http://www-01.ibm.com/support/docview.wss?uid=swg27023414&aid=1

Please follow and like us: