This section provides information on logging in the BeanConnect resource adapter. The logging facilities use Log4j by default. The scope of logging is controlled by configuration files. The following configuration files are delivered with the BeanConnect resource adapter installation:
the file
config/BeanConnect.log4j2.properties.xml
basic logging information (default)
The file
config/BeanConnect.log4j2.properties_default.xml
corresponds to the file
config/BeanConnect.log4j2.properties.xml
the file
config/BeanConnect.log4j2.properties_debug.xml
detailed logging information
the file
config/BeanConnect.log4j2.properties_error.xml
only the information on errors is logged
You can use one of these configuration files depending on your requirements.
You will find detailed information on controlling the depth of logging manually in Logging with Log4j and Diagnosis of the BeanConnect resource adapter.
Default logging in the resource adapter
After the resource adapter has been deployed, basic logging is activated automatically.
The logging files are saved in the logging directory of the application server.
The following logging files are created:
BeanConnect.logging.txt
(information for the user)BeanConnect.extlogging.txt
(logging data which you must send to system service if an error occurs.)BeanConnect.extlogging.txt.xmc
(additional logging data which you must send to the system service if an error occurs.)
Adapting logging in the resource adapter
Copy the configuration files present in the resource adapter installation to the application server's configuration directory.
To extend logging (comprehensive runtime logging):
Rename the copied fileconfig/BeanConnect.log4j2.properties_debug.xml
toBeanConnect.log4j2.properties.xml
.To restrict logging (error logging only)
Rename the copied fileconfig/BeanConnect.log4j2.properties_error.xml
toBeanConnect.log4j2.properties.xml
Application-specific logging control for the resource adapter
Adapt the file
config/BeanConnect.log4j2.properties.xml
to your requirements as described below (see Logging with Log4j and Diagnosis of the BeanConnect resource adapter).