Tracing for the Tivoli
Directory Integrator processes is similar to tracing for WebSphere
® Application Server. The trace output is recorded in the ibmdi.log
file in the <tdi_installation_directory>\logs
Trace settings are configured in the etc\log4j Java
™ logging component. The following tracing levels are available, in order of lowest to highest severity:
When a given level is enabled, all levels that are lower in severity are automatically enabled. For more information about how to configure tracing, refer to the following web page: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_7.1/adminguide84.htm#wq553
Depending on the tracing level enabled, the output can be very lengthy, so try to perform small operations only when tracing is enabled.
Profiles service layer logging
If you are troubleshooting a Profiles or Tivoli
Directory Integrator problem and are unsure about the cause of the problem, the best strategy is to start with a general trace setting at the lowest severity level. If you run a targeted task at a low severity setting, then you might get more information about the problem to help narrow down the trace configuration. The most general trace setting to use to encompass the set of Profiles service classes is:
To confine tracing to just the Tivoli
Directory Integrator operations, include the following line in the etc\log4j.properties
file. The classes in this place in the hierarchy are primarily used as the interface between the assembly lines and connectors and the service layer. This level of tracing might also help identify issues in the calling Tivoli
Directory Integrator constructs.
You might also want to enable event log tracing. Whenever database operations are performed, they are recorded in the event log. By enabling tracing at this level, you can see indirectly what was done via the service level API to the database. To enable event log tracing, include the following line in the etc\log4j.properties
This setting is very verbose, so be sure to enable it for targeted operations.
Database layer logging
It is often useful to enable tracing at the database layer to troubleshoot problems. To enable database tracing, include the following line in the etc\log4j.properties
The log files produced by running Profiles Tivoli
Directory Integrator assembly lines are all stored in the logs
subdirectory of the solution. Most assembly lines create a log file that is specific to the assembly line, for example, PopulateDBFromDNFile.log
When a task is run at a subsequent time, based on the logging implementation of the assembly line, the logs are either renamed with an incremented trailing digit or named with a date suffix to ensure that previous logs are preserved.
All other output, in addition to some assembly-line output, is recorded in the logs\ibmdi.log
file. Standard output and error information is recorded in this file by default, but you can modify this configuration in the etc\log4j.properties
file. For more information, refer to the Tivoli
Directory Integrator documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc_7.0/welcome.htm
When set to true, this property prints additional debug information to the ibmdi.log
file. You can use this property to track issues and capture more detailed information related to mapping and data validation in the log file.
Setting this property to true provides two types of information:
- Mapping details relating to the LDAP and Profiles databases.
By checking this information, you can find out if you have any incorrect attribute mappings.
- The validation result of each attribute
By checking this information, you can find out which field did not pass the validation and verify the value of this field.
The prefix of the error message indicates which component the error message is associated with. For example, the CLFRN prefix is used to identify error messages from all Profiles components. The CTGDIS prefix is used to identify error messages associated with Tivoli Directory Integrator. You might also see error messages from other components in the log files. To find out more about these error messages, refer to the Error codes section of the product documentation.
In addition to the prefix identifier, the last letter of the error message code indicates the severity of the message. For example, a code ending with an I is an informational message. Error and warning codes are designated by E and W respectively.