Logging

Infor Public Sector and its related applications generate several different types of logs. By default, log entries are written to text files on the server. Depending on your system configuration, logs may also be written to the SYSTEMLOG table in the database. You can use the Lookup System Logs page to review database logs.

The Logging configuration in the Configuration Editor is used to manage log settings. Using this configuration, you can fine tune your system logging by enabling or disabling different types of loggers, setting log severity levels, and specifying log destinations.

The root Logging node in the Logging configuration specifies the global log destination and the default log level for all loggers. By default the Logging Destination attribute of the Logging node is set to TextFile, meaning that logs will be written to a text file on the server.

You can change the value to Database to write logs to the database instead, or to All to write logs to both the database and text files. If text file logging is enabled, logs will be written to the file specified in the File Name attribute of each logger's child RollingFileAppender node.

The default log level is Error. For testing you may want to change this to a higher log level, such as Success or Info. You can also define different log levels for individual loggers, which will override the default.

Note: Logging has a performance impact, so you should use the lowest log level possible in a production environment.

See Logging configuration.

You may also want to delete old logs periodically to save space. To delete logs, you can set up a Purge System Logs task in the Batch Manager. This task will remove log entries from the SYSTEMLOG table after a specified number of days. Optionally, you can also use the task to delete old log files from the server.