Logging - EFTLink Framework and Core

EFTLink uses a standard java logging package - log4j2. It maintains a daily log file - eftlink-server_YYYY—MM-DD.log - and deletes log files after 30 days. Both the framework and the core log into this file.

Log files are in the log subdirectory and are created as soon as EFTLink starts. By default, info level logging is enabled. This means that key information is logged but the files are kept as small as possible.

To keep files for longer, or increase the logging level, set log4j2.xml appropriately. Edit the log4j2.xml configuration file which is in the main EFTLink directory.

For debug logging change the following entry:

<Root level="info">

to

<Root level="debug">

Logging at debug level does not noticeably affect system performance but does generate larger log files. To retain log files for longer, edit:

<Delete basePath="log" maxDepth="1">
    <IfLastModified age="30d" />
</Delete>

and alter the age parameter to several days to keep files after the current day (default is 30d).

Consider available disk space when choosing several days to retain log files.

Log file is configured in the standard log4j2.xml configuration file:

• EFTLinkGlobal - contains log information from all sources

A core may have its own log4j2.xml configuration file copied in during install to log to additional files for third-party libraries.

After installing EFTLink as a service, then starting the service, the log file will show about 16 lines, with some basic information, and log that it is deferring all initialization until POS type is known. Once a POS starts, you see details of the core started, with the settings used by the core and initialization progress logged, along with subsequent processing data.

In the case of a MultiServerLauncher / PedPooling installation, the standard log4j2.xml file requires alteration to include server appenders/loggers. See the installation document for further details.