Predefined logging configuration of a proxy

The logging of each proxy is preconfigured with the following default values after installation.

Appender

Name	Description and Recommendation
BeanConnectSysoutShort	Console appender with the destination System.out and “short” output format, i.e. without any specification of the message source. BeanConnect outputs general messages as well as warnings and error messages at this appender Recommendation: No further loggers should be added to this appender.
BeanConnectSysout	Console appender with the destination System.out and detailed output format for making easier the system diagnosis. BeanConnect outputs fatal messages for which no other appender is configured to this appender. Recommendation: No further loggers should be added to this appender.
BeanConnectLoggingFile	Rolling file appender for logging to a file with several backup files (see the section How the rolling file appender works )This appender is used for system diagnosis. BeanConnect writes detailed diagnostic logging information to this appender if necessary.This appender has three parameters: File (Relative) file name of the current logging file Default: logs/logging.txt MaxNbrBackupFiles Maximum number of backup files. If you specify 0 here, no backup files are created. Default: 10 MaxFileSizePerProcessKB Process-specific switchover threshold in KB. When the writing of a logging event causes the file size to exceed this process-specific threshold, the file is switched. The size of a logging file at switchover is thus somewhere between the values for <MaxFileSizePerProcessKB> and <number_of_processes>* <MaxFileSizePerProcessKB>. Default: 500 Recommendation: No further loggers should be added to this appender.
BeanConnectLoggingFileXML	Rolling file appender for logging to a file with multiple backup files (see How the rolling file appender works ). The output from this appender has an XML-like layout. The file can be evaluated at the Management Console (see also Display the Log4j logging file using the BeanConnect Management Console ). Although this appender is preconfigured, it is not used in the standard BeanConnect configuration. It is used for system diagnostics. If necessary, BeanConnect writes detailed diagnostic logging information to this appender. Recommendation: If required or if so requested by the system service, this appender should be assigned the same loggers as the appender BeanConnectLoggingFile.

Loggers

It is recommended not to change the logger settings.

Name	Description
Root-Logger	Level: FATAL
BeanConnect	Parent logger of all the other BeanConnect loggers Level: ERROR
BeanConnect.c	Logger for debug traces from the C components of BeanConnect Level: ERROR
BeanConnect.info	Logger for runtime information Level: INFO
BeanConnect.Datasources.OLTP	Logger for OLTP data sources Level: ERROR
BeanConnect.kdcs	Logger for debug traces of the KDCS calls from the proxy container. Level: ERROR
de.siemens and net.fsc	Parent loggers of all class-specific BeanConnect loggers that serve to output debug traces. Level: ERROR
net.fsc.tpbasics.util.L	Logger for supporting Log4j Level: WARN
net.fsc.beanta.encoding.EncoderImpl	BeanConnect's logger for encoding support Level: WARN