POS Thin Client

Log files are permanently written during POS Client operation. When a defined file size is reached, the log files are packed and later deleted. The following files exist:

  • <POS_ROOT>/log/pos.log: Contains logs for POS Client and Loyalty Engine
  • <POS_ROOT>/log/terminal.log: Contains logs for EFT communication

Configuration File Name, Max. File Size Etc.: pos.log

File name:

  • An unpacked log file has the following format: pos.log
  • Packed log files have the following format: pos.log-[JJJJMMDD].zip

There are several parameters to influence the storage duration, file size, etc.:

  • maxBytes: Max. file size in bytes. If it is exceeded, the file is packed and a new file is created.
  • maxCount: Max. number of files. If it is exceeded, the files are deleted.
  • maxAge: Max. age of files. If it is exceeded, the corresponding files are deleted.

Configuration file:

<POS_ROOT>/config/parameter/custom-appender.xml :

<param name="maxBytes" value="10485760" />
<param name="maxCount" value="1000" />
<param name="maxAge" value="30d" />

Configuration File Name, Max. File Size Etc.: terminal.log

File name:

  • An unpacked log file has the following format: terminal.log
  • Packed log files have the following format: terminal.log-[JJJJMMDD].zip

There are several parameters to influence the storage duration, file size, etc.:

  • maxBytes: Max. file size in bytes. If it is exceeded, the file is packed and a new file is created.
  • maxCount: Max. number of files. If it is exceeded, the files are deleted.
  • maxAge: Max. age of files. If it is exceeded, the corresponding files are deleted.

Configuration file:

<POS_ROOT>/config/parameter/terminal-appender.xml :

<param name="maxBytes" value="10485760" />
<param name="maxCount" value="1000" />
<param name="maxAge" value="30d" />

Configuration of Outputted Log Levels

The log level can be set differently for the individual components. Therefore, it can be defined whether outputs of a particular category (=level) are written or not.

The following log levels are available:

  • TRACE
  • DEBUG
  • INFO
  • WARNING
  • ERROR
  • FATAL

If INFO is set, all messages of the level INFO and higher are outputted.

OFF disables the logging completely.

Configuration file:

<POS_ROOT>/config/parameter/logging.properties, e.g.:

# HAL
log.level.com.gk_software.pos.hal=DEBUG
log.level.com.gk_software.pos.pos_hal.input=DEBUG
log.level.gk.cashterminal=DEBUG
log.level.gk.javapos=DEBUG
# remoting
log.level.org.apache.cxf=OFF
# commons http client
log.level.httpclient.wire=DEBUG
log.level.org.apache.commons.httpclient=DEBUG
# http client - svs
log.level.org.apache.http.impl.conn=DEBUG
log.level.org.apache.http.impl.client=DEBUG
log.level.org.apache.http.client=DEBUG
#ui - xml printouts
log.level.com.gk_software.pos.ui=OFF
log.level.com.gk_software.pos.ui.swing.service=OFF
log.level.com.gk_software.pos.ui.swing.adapter=INFO

Log Output on the Console

In the configuration file <POS_ROOT>/config/parameter/logging.properties , it is possible to set which messages are displayed on the console.

By default, only STDERR messages are displayed. Normal STDOUT messages are suppressed:

  • true = Output suppressed
  • false = Output allowed

Configuration file:

<POS_ROOT>/config/parameter/logging.properties :

 drop.appender.GK_STDOUT.enabled=true drop.appender.GK_STDERR.enabled=false