The tab-separated columns of information in each log file are static, and therefore, not configurable.

However, the information contained in these log files is very comprehensive, so you are able to easily navigate the files, and troubleshoot any issues.

The location of the log files is configurable in the Service Configuration window. Each log file contains the following columns.

• Time.

  The time and date of processing. Since processing can span across a single day, this date may be different to the date in the log file name.

• Level.

  The configured level of detail included in the log. Depending on how your log files are configured, this can be any of the following values.

  • Error. Records error events that may allow the application to continue running.

  • Warning. Records potentially harmful situations.

  • Info. Records informational messages that highlight the progress of the application at a detailed level.

  • Debug. Records fine-grained informational events that are used to troubleshoot and debug the application.

• ProcId.

  The process ID of the application.

• Memory(KB).

  The amount of memory used by the ProcessId.

• Message (Class.Method).

  The Message is information about the log entry. If there is an error, it is logged here.

  The Class and Method indicate the origin of a particular log entry.

  All three of these help identify what is causing a problem, and at what point during processing the issue occurs.

Each of the above log files is retained for a period of days configured by the "Purge log entries older than (days)" option in the Configuration Tool window.

The Thin Client Server currently does not support application logging.