Logging Configurations
| When a logfile is locked by another process, the logging can't be written into the logfile. Therefore it is recommended to view a logfile using the Logging option in the Processed menu item or alternatively using Notepad and not Microsoft Word, since this last application will lock the logfile. |
In this tab the available logging configurations are shown to the administrator. As with the basepaths configurations new configurations can be added, existing
ones viewed, edited, copied or removed. When add, edit or copy is selected the dialog shown under General logging
settings will appear.
In the tab General logging settings the events to log can be selected. In the tab Days to keep logging settings the
time before deleting the log entries can be set in days and in the tab Transaction logging settings the actual
transactions can be logged in a database. For logging of transaction a transaction database is required. This can be
added in the databases screen of the
ControlCenter
General logging settings
- Clean time: The Batch Controller starts its daily cleaning process of report and log files at the set time.
- Enable windows event logging: If enabled, event entries will be written in the Windows event logs.
- Enable statistics: If enabled, statistics are saved in the system database.
- Enable library statistics: If enabled, statistics about library usage are saved.
- Enable webservice statistics: If enabled, statistics about Consumable Webservices are saved.
- Add DLL calls to caller log: If enabled, information about calls to DLL files are added to the caller log.
- Include deleted reports: If enabled, information about deleted reports are added to logs.
Days to keep logging settings
- Days to keep jobs history: Sets the number of days to keep information about job execution. After this period, the relevant records are deleted by the Batch Controller. If this value is changed, the new setting only applies to jobs executed afterwards.
- Days to keep failed job history: Sets the number of days to keep information about failed job execution.
- Days to keep logfiles: Sets the number of days for the Batch Controller to keep log files.
- Days to keep prints: Sets the number of days for the Bath Controller to keep prints. If set
to less than 25, job output that is not actually printed will be saved for 25 days. This setting is overruled if a
job dynamically assigns a new value to the printer ID property DAYSTOKEEP.
If multiple print jobs use the same print file, the print file is stored until all the print jobs' "Days to keep" have expired. - Days to keep messages: Sets the number of days for the Batch Controller to keep messages in the system database.
- Days to keep logging information: Sets the number of days to keep logging information in the database.
- Days to keep statistics: Sets the number of days to keep statistics in the database.
Transaction logging settings
- Enable transaction logging: If enabled, database transactions are logged in a separate database. Note: The database in which these logs are stored first needs to be created.
- Transaction database: Select the correct transaction database for this configuration.
- Days to keep transaction logging: The number of days transaction logs are kept in the transaction database.
- Enable library transaction logging: If enabled, library transactions are also logged in the transaction database.