License usage reports
Use the web-based reporting application to create various helpful reports that are based on license server artifacts. The generated reports help you evaluate and track license usage for the IBM® Engineering Lifecycle Management (ELM) or IBM Rational® products that are used in your organization.
Use the reporting application to track and report license usage on ELM or IBM Rational products that are served by the License Key Server and the IBM Engineering Lifecycle Management (ELM) license server. You can also get a consolidated view of all the license servers in your organization. Based on the license server artifacts, the reporting application creates various useful reports to track and report license usage.
The reporting solution is based on the License Key Server
lmgrd.log log file.
lmgrd.log,
lmgrd.log.back, and ibmratl_timestamp.log) and
option files (such as ibmratl.opt) are the source of data for the reporting tool.
Do not delete or modify these files. Doing so results in license usage reporting inaccuracies. For
more information, see technical document http://www.ibm.com/support/docview.wss?uid=swg21671165.- The reporting feature does not track license usage for Atria licenses, flex-based authorized user licenses, and nodelocked licenses.
- Also, read the technical document Planning shutdown of the license server with respect to reporting and outstanding license usage data.
- For more information about accessing multiple instances of the same product where the product instances are started through different UNIX or Linux® terminals, see the License Key Server Administration and Reporting Tool reports less license usage under a specific rare scenario technical document.
- If your license server log file contains product names that are logged in Japanese and you try to run token reports for ELM products, the reporting tool cannot process the product names. To resolve this issue, complete the steps in technical document http://www.ibm.com/support/docview.wss?uid=swg21667198.
Data that is used to generate a scheduled report
The report that the scheduler generates is slightly different from a manually generated report. The difference is in the duration of the data that is queried by the scheduler. To enter dates for the data duration, go to the Select Duration section on the Parameters tab.
The data duration for scheduled reports uses a sliding window of time. The end date of the data duration is always relative to the time the schedule runs. For example, if the schedule runs at 3 PM and the effective data duration end date is defined as Same Day, the data duration end date is 3 PM. If the data duration end date is defined as 3 Weeks Earlier, the effective data duration end date is 3 PM on the date that is three weeks earlier.
The end date keeps sliding along with the time of the run of the schedule to ensure that the latest data is included in the scheduled report.
You can define the data duration start date to be either a specific date or a date relative to the data duration end date. Defining the data duration start date allows the flexibility to either slide the start date along with the end date or make it a specific value to highlight the beginning of an important period.
You can go back any number of days, months, quarters, weeks, and years. You can also define the start date to be the same day as the end date.
The data duration start date always begins at the start of the day: 00:XX hours, where XX represents the difference in minutes corresponding to the GMT.
Similarly, the data duration end date always ends at the close of the day: 23:XX hours, where XX represents the difference in minutes corresponding to the GMT.