Logging Configuration

This page describes the Logging Configuration settings. The following properties can be set:

Log Level

Specify which level of message you want to log. Possible values are:

• Errors Only: Only errors and exceptions will be logged. This option is the default and produces the minimum amount of logging.
• Errors and Information: This level also logs additional information messages, like the data being transfered between Adapters.
• Errors, Information and Flow: This level also logs trace messages, like internal methods being called.

Categories

With this property you can specify which software components should log. Choose this option if you are an advanced user and you want to enable logging for the individual components. Click the drop-down button to display the Logging Categories dialog box, in which you define the categories for which logging is enabled.

File Name

Type here the path and name of your log file, for example C:\logging\test.log. If the directory you specify does not exist, it will be created. Leave this field empty to use the default logfile name, which is: <user.home>/.owlog/<user.name>.log

<user.home> and <user.name> are system properties that contain the home directory and user name.

If Log per Process is enabled, the file name will indicate which process is involved. In this case the default logfile name will be: <user.home>/.owlog/<user.name>_<appname>_<GUID>.log

Log per Process

This option specifies whether you want Adapter to log per process. When logging per process is enabled, each process which uses some Adapter code is logged in a separate log file.
With Log per Process enabled, different processes are logged in separate log files and the names of these log files are extended by the application name and a unique number. The file name will then have the following format: <file name>_<appname>_<GUID>.<file extension>, where <file name> and <file extension> are defined by what you filled in at File Name, <appname> is the application name that is generation this file (named after an Adapter Suite component) and <GUID> is an unique number of 15 digits to identify the process.

Example: when you are running the Server Connector for Java and you specified test.log as file name, Adapter logs this process in file: test_Java_Server_10681304540830.log.