Generating usage report logs
Go Up to Administering AppWave Enterprise License Center Server
The Reporting Logs Export feature for ELC is provided to customers to export license usage data from ELC. Tracked usage data consists of the following:
- User/Permission Data
- Product Data
- Licenses (duration of use, initial start times, finish times, license types)
This data can be exported from ELC to two different formats:
- Comma-separated value (CSV) file with corresponding schema files
- XML with corresponding xml schema documents (XSD) file
Contents
To enable or disable ELC reporting logs
By default reporting logs are enabled.
- To disable report logging, select Configuration Properties from the main menu and set
reportLogsEnabled
tofalse
. - To enable report logging, select Configuration Properties from the main menu and set
reportLogsEnabled
totrue
To export ELC reporting logs
From the main menu select Reports, than last item - Reporting Data Export
You can also export reporting logs using the ELC command-line interface.
Running the exportlogs command with options
The exportLogs
command has the following form:
elise cmd exportLogs ( -dir <directory> ) ( -csv | -xml ) ( -purge )
The exportLogs
command has the following options:
-csv -- generates a set of comma-separated value list files and schema files containing data representative of every table in the database. Files exported using the -csv option are as follows:
lm_denial_entry.csv
lm_denial_entry.schema
lm_entry_instance.csv
lm_entry_instance.schema
lm_ip_block.csv
lm_ip_block.schema
lm_license.csv
lm_license.schema
lm_license_pool.csv
lm_license_pool.schema
lm_permission.csv
lm_permission.schema
lm_pool_entry.csv
lm_pool_entry.schema
lm_pool_type_lu.csv
lm_pool_type_lu.schema
lm_product.csv
lm_product.schema
lm_timestamp.csv
lm_timestamp.schema
lm_user.csv
lm_user.schema
- -xml-- generates an xml file of the database along with an xsd file. Files exported using the -xml option:
export.xml
lm_reporting.xsd
lm_reporting_access.xsd
– additional xsd file with Microsoft-specific attributes for importing data into Microsoft Access
- -purge -- enables users to remove/clear all records from the database with the exception of license records that are still actively in use. As a safety mechanism, using the -purge option without any other logging options, as shown below, forces a report logging export using all formats (csv, xml, db) before any data is purged.
>elise cmd exportLogs –purge
The following data shows the growth of the reporting database with respect to the total number of records in the database after 6 man months for various usage rates:
Use rate (Users / man day) | Total records added after 6 man months | Database size after 6 man months (KB) | Database Transaction log size after 6 man months (KB) |
---|---|---|---|
10 |
2650 |
2067 |
6952 |
25 |
6625 |
4849 |
14504 |
50 |
13250 |
9487 |
27092 |
100 |
26500 |
18762 |
52267 |
500 |
132500 |
92962 |
253667 |
- -dir -- used to specify an output directory for exporting logging data to. If no export directory is specified, logging data will be written to
$ELC_HOME$/export
directory.
Running the exportlogs command without options
Running the exportLogs command with no options exports reporting data to both formats as shown below:
>elise cmd exportLogs
ELC reporting logs timeout functionality
The ELC Reporting Logs export feature has been built with internal timeout functionality to prevent export from occurring during periods of high load. This is designed to prevent interruption to the mission-critical purpose of ELC, which is serving licenses to Embarcadero Concurrent and Networked Named User customers.
To troubleshoot reporting logs
In order to troubleshoot the ELC Reporting Logs functionality, please add the following to the elise.properties
file and restart ELC:
debugReportLogs = true
If errors appear in the db.log
file (located in the $ELC_HOME\logs
directory), please send the following to Embarcadero Customer Support:
- db.log file
- JDK version you are using
- OS you are running ELC on
- A description of the error(s) you are seeing
See Also
- Starting AppWave Enterprise License Center
- Using AppWave Enterprise License Center commands
- Setting up a client for named user licensing
- Setting up a client for concurrent licensing
- Interpreting the logs
- Troubleshooting the server
- Troubleshooting the client
- Using ELC reporting log data
- Questions and Answers