Tracing and FFDC

This is a logging library similar to Log4J, but which is used inside IBM® Security Verify Directory Integrator specifically for tracing and First Failure Data Capture (FFDC).

In addition to the user-configurable logging functionality described in Logging and debugging, IBM® Security Verify Directory Integrator is instrumented throughout its code with tracing statements, using the JLOG framework. To which extent this becomes visible to you, the end user, depends on a number of configuration options in the global configuration file jlog.properties, and the Server command line option -T.

Note: Normally, you should be able to troubleshoot, debug and support your solution using the logging options described in the section, Logging and debugging. However, when you contact IBM Support for whatever reason, they may ask you to change some parameters related to the tracing functionality described here to aid the support process.

• Tracing Enhancements
  Most Connectors and Parsers have entry and exit trace statements. A number of classes on the IBM® Security Verify Directory Integrator server have trace statements added to the listed items.
• Understanding Tracing
  Tracing is done in the code of IBM® Security Verify Directory Integrator using JLOG's PDLogger object. PDLogger or the Problem Determination Logger logs messages in Logxml format (a Tivoli® standard), which IBM Support understands and for which they have processing tools.
• Configuring Tracing
  You can use the jlog.logger.level property in the jlog.properties file to set the required trace level.