Default POSLog.ini and XPSLog.ini
The default poslog.ini
provided with SAP POS 2.3 writes all log messages to a single posclient.log
, this includes messages that were previously written to the XCPT.log
, APPLY.log
,
and EVENT.log
. Transaction Object logging (both POS and component), also write to the posclient.log
file.
Optionally, logging can be enabled for OPOS device logging, and the various SAP POS User Exits. The default poslog.ini
file is as follows:
Syntax
#FileHandler.<HandlerName>.pattern=Log File Name (for example, logs/posclient.log)
#FileHandler.<HandlerName>.archive=true to archive log files to upload/keep#/logs directory
#FileHandler.<HandlerName>.limit=maximum log file size
#FileHandler.<HandlerName>.count=# of log files to maintain
#Logger.<FeatureName>.fileHandler=<HandlerName>
#Logger.<FeatureName>..level=log level, one of SEVERE, WARNING, INFO, CONFIG, FINE, FINER, or FINEST
FileHandler.FH1.pattern=logs\\posclient.log
FileHandler.FH1.archive=true
FileHandler.FH1.limit=500000
FileHandler.FH1.count=5
FileHandler.FH2.pattern=logs\\UE.log
FileHandler.FH2.archive=false
FileHandler.FH2.limit=100000
FileHandler.FH2.count=2
FileHandler.FH3.pattern=logs\\EFT.log
FileHandler.FH3.archive=true
FileHandler.FH3.limit=100000
FileHandler.FH3.count=2
FileHandler.FH4.pattern=logs\\OPOS.log
FileHandler.FH4.archive=false
FileHandler.FH4.limit=100000
FileHandler.FH4.count=2
#
#
# Log Features to control logging to file handlers
# defined above.
#
#
#
# Default logger is used when an attempt is made to
# log a message with an unconfigured feature.
# WARNING level will log severe and warning messages to the posclient.log
#
Logger.DEFAULT.fileHandler=FH1
Logger.DEFAULT.level=WARNING
# Default configuration combines the Exception, Event, Browser, and Transaction
# Object entries into a single log file named "posclient.log".
Logger.XCPT.fileHandler=FH1
Logger.XCPT.level=INFO
Logger.EVENT.fileHandler=FH1
Logger.EVENT.level=INFO
Logger.SAPTXNOBJ.fileHandler=FH1
Logger.SAPTXNOBJ.level=INFO
Logger.TXNCOMP.fileHandler=FH1
Logger.TXNCOMP.level=INFO
Logger.BROWSER.fileHandler=FH1
Logger.BROWSER.level=WARNING
#
# User Exit logging (Promotion and Services Engines)
#
Logger.PROMO.fileHandler=FH2
Logger.PROMO.level=FINE
Logger.SERVICES.fileHandler=FH2
Logger.SERVICES.level=FINE
#
# Default configuration is to have the EFT and PinPad User Exits write to
# an 'EFT.log' Implementations can optionally add content to the
# log via a call back (it may or may not use this feature).
#
Logger.EFT_UE.fileHandler=FH3
Logger.EFT_UE.level=INFO
Logger.EFT_IMP.fileHandler=FH3
Logger.EFT_IMP.level=INFO
Logger.PINPAD_UE.fileHandler=FH3
Logger.PINPAD_UE.level=INFO
Logger.PINPAD_IMP.fileHandler=FH3
Logger.PINPAD_IMP.level=INFO
#
# Following are all the OPOS log features (currently configured to use same
# file handler so will write to same log file)
#
Logger.PRINTER.fileHandler=FH4
Logger.PRINTER.level=WARNING
Logger.DRAWER.fileHandler=FH4
Logger.DRAWER.level=WARNING
Logger.MICR.fileHandler=FH4
Logger.MICR.level=WARNING
Logger.MSR.fileHandler=FH4
Logger.MSR.level=WARNING
Logger.KEYBOARD.fileHandler=FH4
Logger.KEYBOARD.level=WARNING
Logger.DISPLAY.fileHandler=FH4
Logger.DISPLAY.level=WARNING
Logger.LOCK.fileHandler=FH4
Logger.LOCK.level=WARNING
Logger.SCALE.fileHandler=FH4
Logger.SCALE.level=WARNING
Logger.SCANNER.fileHandler=FH4
Logger.SCANNER.level=IWARNING
Logger.FISCAL_PTR.fileHandler=FH4
Logger.FISCAL_PTR.level=WARNING
#
# DEBUG logging Features, enabled as required. Currently all written
# to the posclient.log file.
#
# Debug logging of MixMatch processing
#
#Logger.MIXMATCH.fileHandler=FH1
#Logger.MIXMATCH.level=WARNING
#
# Debug logging of FindFiles function
#
#Logger.FindFiles.fileHandler=FH1
#Logger.FindFiles.level=FINE
#
# Logging of the capture of signatures and printing of signatures.
# Useful to debug any printing/capture of signatures.
# Only logs at FINE level
#
#Logger.Signatures.fileHandler=FH1
#Logger.Signatures.level=FINE
#
# Logging of interactions between POS and IPOS_TC (Signature Capture device).
#
#Logger.IPOS_TC.fileHandler=FH1
#Logger.IPOS_TC.level=FINE
#
# If the following logger is configured, it will also install a handler for invalid parameter checks
# that will log the error, and allow the application to continue even though a parameter to one of the
# '_s' methods was bad. The subsequent behaviour can be unexpected, though.
#
#Logger.PARAMETERS.fileHandler=FH1
#Logger.PARAMETERS.level=FINEST
The default xpslog.ini
file is as follows:
Syntax
#FileHandler.<HandlerName>.pattern=Log File Name (for example, logs/xcpt.log)
#FileHandler.<HandlerName>.archive=true to archive log files to upload/keep#/logs directory
#FileHandler.<HandlerName>.limit=maximum log file size
#FileHandler.<HandlerName>.count=# of log files to maintain
#Logger.<FeatureName>.fileHandler=<HandlerName>
#Logger.<FeatureName>.displayToConsole=true|false (not valid for POS)
#Logger.<FeatureName>.level=log level, one of SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST
#FileHandler.FH1.pattern=logs\\xcpt.log
#FileHandler.FH1.archive=true
#FileHandler.FH1.limit=500000
#FileHandler.FH1.count=5
FileHandler.FH2.pattern=logs\\crsrv.log
FileHandler.FH2.archive=true
FileHandler.FH2.limit=1000000
FileHandler.FH2.count=5
#FileHandler.FH3.pattern=logs\\event.log
#FileHandler.FH3.archive=true
#FileHandler.FH3.limit=100000
#FileHandler.FH3.count=5
#FileHandler.FH4.pattern=logs\\apply.log
#FileHandler.FH4.archive=true
#FileHandler.FH4.limit=100000
#FileHandler.FH4.count=5
FileHandler.FH5.pattern=logs\\xps.log
FileHandler.FH5.limit=1000000
FileHandler.FH5.count=5
FileHandler.FH6.pattern=logs\\sql.log
FileHandler.FH6.limit=1000000
FileHandler.FH6.count=5
# Default configuration combines most log entries into XPS.LOG.
Logger.XCPT.fileHandler=FH5
Logger.XCPT.displayToConsole=true
Logger.XCPT.level=FINE
Logger.CRSRV.fileHandler=FH2
Logger.CRSRV.displayToConsole=true
Logger.CRSRV.level=FINE
Logger.EVENT.fileHandler=FH5
Logger.EVENT.displayToConsole=true
Logger.EVENT.level=FINE
Logger.APPLY.fileHandler=FH5
Logger.APPLY.displayToConsole=true
Logger.APPLY.level=FINE
Logger.XPS.fileHandler=FH5
Logger.XPS.displayToConsole=true
Logger.XPS.level=INFO
Logger.APPLICATION.fileHandler=FH5
Logger.APPLICATION.displayToConsole=true
Logger.APPLICATION.level=INFO
Logger.TRICKLE.fileHandler=FH5
Logger.TRICKLE.displayToConsole=true
Logger.TRICKLE.level=INFO
Logger.COMMUNICATION.fileHandler=FH5
Logger.COMMUNICATION.displayToConsole=true
Logger.COMMUNICATION.level=WARNING
Logger.TLOG_UPLOADER.fileHandler=FH5
Logger.TLOG_UPLOADER.displayToConsole=true
Logger.TLOG_UPLOADER.level=WARNING
Logger.SQL.fileHandler=FH6
Logger.SQL.displayToConsole=false
Logger.SQL.level=WARNING
#
# If the following logger is configured, it will also install a handler for invalid parameter checks
# that will log the error, and allow the application to continue even though a parameter to one of the
# '_s' methods was bad. The subsequent behaviour can be unexpected, though.
#
#Logger.PARAMETERS.fileHandler=FH1
#Logger.PARAMETERS.level=FINEST
#
# Default logger is used when an attempt is made to
# log a message with an unconfigured feature.
# Will log severe and warning messages to the xps.log
Logger.DEFAULT.fileHandler=FH5
#
Logger.DEFAULT.displayToConsole=true
Logger.DEFAULT.level=WARNING