Enhanced logging

Enhanced logging has been implemented at the application code level and is controlled by different logging levels. This approach ensures more robust logging across the application with special attention to the following areas:

• Active Directory (including logging in, logging out, current user, and connecting to AD server)

• Folder Monitor (including firing of jnotify or cron, file detection, folder creation, and database insert)

• Email Import (such as connecting to the email server, attachment download, and email change to read)

• TIFF conversion (imagemagick, graphicmagick, libtiff)

• Pick Up Service (including pickup server assignment, db query to BI table, insert to *job table, individual servers locking records, start of workflow)

• ITEXT (including start of the process, file detection, and file output)

• LibreOffice (including start of the process, file detection, and file output)

Enhanced logging is used for ERROR, INFO, and DEBUG levels, with DEBUG level providing the most detailed information about the issue.

You can change the logging level in log4j.xml (<Transact Folder>\Application) to generate more robust logs according to the requirement.

Detailed information according to the selected logging level is registered in the dcma-all and dcma_report_all files, which are located at <Transact Folder>\Application\logs.

Additionally, you can increase the default size of the logger from the initial value of 2 MB. If you are logging in INFO and DEBUG level, and would like to set the logger size to 50 MB or 100 MB instead of 2 MB, you can do this by finding the appropriate logger from the EphesoftFileAppender tag.

To increase the logger file size, modify the SizeBasedTriggeringPolicy tag and save the log4j.xml file. Restart the Transact service for the changes to take effect.