Log Files tab

Select the Log Files tab and complete the Transaction Log options:

Sync Write – open the log file with options that cause the write() function to block further processing until the data is physically on the disk.
Pending – the pending log file is required and contains messages that are accepted by the SFM, but have not been processed. Specify the log name and:
- Max (KB) – the maximum size, in kilobytes, of the log file. The default is 10240 or 10MB.
- LWM (%) – the percentage of the pending log file that must be used to clear the HWM alert status.
- HWM (%) – the maximum percentage of the pending log file that can be used before an alert is generated.
When a log file fills up, and the usage percentage is past the high-water mark (HWM), an alert is generated. However, after the initial alert is generated, no other alerts are generated unless the log file is cleared out to the point that its usage percentage falls below the low-water mark (LWM).

For example, let’s say the LWM is set to 60 and the HWM is set to 80. Once the HWM is set, even if the percentage of log usage hovers between 61 and 100, no alerts are generated. Once the percentage of log usage hits the LWM, the HWM alert is created, so the next time the percentage of log usage hits the HWM again, another alert is generated.
Completed – select this option to create a log file that stores completed or cancelled messages in their raw form. Specify the name and maximum size (in kilobytes) of the log file, as well. The default of 10240 is suggested but not required. If you do not specify a completed log, messages that are completed or cancelled are discarded.
AutoArchive – select this option to have completed transactions moved to an archive file for historical records. If this option is selected, enter a name and size for the archive file. When the archive file reaches the set size, it is appended with an incrementing counter and a new archive file starts.
Unrouteable – the unrouteable log file is required. This log file contains messages that have not been accepted by the SFM. Specify the name of the unrouteable log file.

Complete the following fields to define the xlog properties. The xlog stores messages related to the function of SFMs and related applications.

Limit (KB) – defines the log file limit. There is no predefined limit, but the default setting of 1024 (1MB) provides a useful log file without using too much disk space. Increase the value if you expect to use the debug option.
Depth – the number of copies of the log file that e-Biz Impact maintains. The default setting of 2 indicates that e-Biz Impact creates an additional file when the main activity log reaches its maximum size. If the second file reaches the limit, e-Biz Impact rolls back to the first file, overwriting the content.