In order to generate real time reports in ART tool, you need consistent and accurate data of License server logs. It is the log file that record license checkout,check-in,denial and other critical data used to generate reports in ART tool.Prior to RLKS 8142, each time when you restart License server service, it overwrite existing content of log(lmgrd) file with new data.
Seeing loss of critical log data, a new log mechanism was developed and implemented in RLKS ART 220.127.116.11. Let me give you a brief high level overview of ART tool before we dive deep into the new log mechanism implemented in 18.104.22.168.
RLKS Administration and Reporting tool (ART) mainly comprises of two core components:
RLKS Admin agent
In order to do license usage reporting of a License server, you would have to install RLKS Agent on each license server machine.When you run “RLKS Admin Agent” service, it starts converting license server log (lmgrd) file data into RDF/TTL files per hour. In the background, these files are used by ART server to generate license usage reports.
RLKS ART server
ART server pulls up data from “Admin Agent” machine to generate reports. It polls RLKS Admin Agent every 60 seconds. You can generate various kinds of license usage reports like Peak usage, Peak denial, and Token distribution etc. for floating and token licenses over a period of time. A typical deployment scenario of ART is shown below:
Now you have a high level overview of ART tool, let me explain how you can kick in new log mechanism on a License server. It starts when you click ‘Start Reporting’ (as shown below) service against the respective License server in ART reporting tool. This action also creates below mentioned files under the installation directory of License server:
Existing log(lmgrd) file switch to a new file having the name ibmratl_TIMESTAMP.log. Floating and Token license checkout and check-in information goes inside this file. Each ibmratl_TIMESTAMP.log file can store a maximum of 500M of data. Once the file touches its max limit, it switches and creates a new ibmratl_TIMESTAMP.log file.
The RLKS Agent checks if a backup file(lmgrd.log.backup) exists for the configured log file. If the backup file exists, the file continues to be used as a backup.
This file is created if it is not present in the installation directory of license server and adds below content in the file.
DEBUGLOG +"C:\Program Files (x86)\IBM\RationalRLKS\common\ibmratl_TIMESTAMP.log"
This functionality assures that data in the Rational License Key Server log files are not overwritten when the Rational License Key Server is restarted, either as part of a planned shutdown or during the import of new license file. In a longer period of time, you can track your license data and generate real time license usage reports at any point of time with minimal chances of error.