In this dialog it is possible to enable / disable the logging of the used server or application. Also, log file and log level can be specified.
Available log levels:
None: Deactivate the logging of the server / application.
Status: Log only server status changes and single logs for each time a report is rendered.
Error: Log includes error messages such as "report file could not be read; rendering aborted".
Warning: Log includes warning messages such as "font not found, using a replacement font".
Information: Log includes information messages such as the used JDBC driver.
Debug: Useful if you want to send bug reports to the support team. Set this log level when asked to by i-net software's technical support or if you need detailed log messages to solve a problem.
Customized: With this log level it is possible to set the log level for each server component.
Default value: Error
Please remember that in some cases a component may log more information than configured here (e.g. SetupWizard loggs at minimum on INFO)
Logging of Database Drivers
Activate/Deactivate the logging of the used database (JDBC) driver.
Default value: Deactivated
File for Logging
This log file will be used for logging instead of the standard output stream (System.out).
empty- the standard output stream is used (console).
Max Size (MB)
Specifies the maximum size (in MB) a log file should reach before being archived as <original log file name>.<index>.zip. Enter 0 to have no limit.
Default value: 100
Max Number of Archive
Defines how many archive log files are to be kept before deleting old ones when archiving. Enter 0 to not have a limit.
Default value: 10
Defines the Date Format pattern for Logging in Java syntax, e.g. dd-MM-yyyy HH:mm:ss.S
Default value: M/d H:mm:ss
The event log is a way to create a backlog of component specific incidents that have impact on the i-net Clear Reports. The log is written as a program readable CSV file in the following format:
DATE,USER ID,USER NAME,EVENT,MESSAGE,DATA
DATE: UTC formatted date
USER NAME: Information about the user who was responsible for emitting the event. Will be left empty if the user was a privileged user, aka the internal system itself.
EVENT: A unique event name
MESSAGE: A human readable message about the event
DATA: Event specific data in the form of a JSON string which requires further processing
Path of the Event Logs
The path where the event logs will be stored. Different components of i-net Clear Reports will create different event logs so that it is easier to follow specific incidents.
Creation of Debug files containing Report Query Data per report file
Create Debug Data
Activates the creation of debug files containing the requested database data of a report ("save data of the report file"). It is strongly recommended to leave this off unless you are asked to switch it on by i-net software's technical support, since it is extremely performance-intensive. If you activate "Create Debug Data", then i-net Clear Reports will create files called CCcore<engine-id> in the current directory (or in the directory that the parameter "Path for Debug Data" points to). You can read back the data with the database class DatabaseCore (append: &datasource=core.dll at the end of the report URL).
Default value: Deactivated
Path for Debug Data
The path for CCcore files. These files contain the data that is fetched from the database for this report. Even if a CCcore file might end with .rpt it is not a report file but only the data to be used for the report file.
Note: If this field remains empty, the working directory will be used.