Understanding the logging interface
You can refer to the Logging interface files and objects listed here.
The IBM® Security Directory Integrator logging interface consists of the following files and objects:
| Object | Description |
|---|---|
| com.ibm.di.config.interfaces.LogConfigItem | This is the configuration object for a defined LogInterface implementation. |
| com.ibm.di.log.LogInterface | This is the interface implemented by loggers that provide access to 3rd party logging utilities. |
| com.ibm.di.server.Log | This is the utility class used by IBM Security Directory Integrator components to create the Log object. |
| <workdir>/logging.categories | Optional file to map categories to LogInterface class names. This file is not present by default. |
| com.ibm.di.log.TDILog4j | The LogInterface implementation for Log4J. |
| <installdir>/etc/log4j.properties | The log4j configuration file for IBM Security Directory Integrator main component categories (server,ce and config drivers). |
| <installdir>/etc/global.properties | A property is defined to globally enable/disable
log activities. When false, all log calls made through the IBM Security Directory Integrator Log class will be discarded. The property name is "com.ibm.di.logging.enabled". |
IBM Security Directory Integrator components obtain loggers by creating an instance of the com.ibm.di.server.Log class using a category to determine the actual logging utility and output to use. This is done to preserve compatibility with earlier versions.
The Log class will also consult the logging.categories file to see if there is a mapping between the category and a LogInterface class. By default there are no specific mappings in this file (it is not present by default) and the Log class falls back on the TDILog4J implementation.