Built-in troubleshooting features

You can find information about some built-in troubleshooting features elsewhere in the IBM® Security Verify Directory Integrator Version 10.0.0 documentation library.

See the following sections for the information about these features:

Logging IBM® Security Verify Directory Integrator relies on log4j as a logging engine. It is a very flexible framework that lets you log to file, NT eventlog, Unix syslog and more, and can be tuned so it suits most needs. It can be a great help when you want to troubleshoot or debug your solution.

For information about IBM® Security Verify Directory Integrator logging, see the "Logging and debugging" section in the Installing and Administering section of the product documentation.

To see examples of the logging windows of the Configuration Editor see the "Configuration Editor" section in the Configuring Directory Integrator section of the product documentation.

AssemblyLine Auto Dump The property com.ibm.tdi.autodump.directory is a property you can set in

global.properties or

solution.properties. It enables AssemblyLine state dumps to be performed automatically when an AssemblyLine terminates abnormally. The state dump contains valuable information about the state of the AssemblyLine at the time of termination such as JavaScript variables and other useful information. The value of this property should be a relative or absolute path to an existing directory. For default installations it is useful to specify "logs" so that the dumps end up in the same directory as the other logs. The log for each AssemblyLine is named after the AssemblyLine itself. The dump is appended to existing files.

Debugging IBM® Security Verify Directory Integrator Version 10.0.0 offers an AssemblyLine debugging tool called the AssemblyLine Stepper. The AssemblyLine Stepper allows you to:

1. Define breakpoints for AssemblyLines.
2. Pause AssemblyLine processing at the defined breakpoints to examine the AssemblyLine for errors.

The AssemblyLine Stepper is part of the Configuration Editor. For more information about how to use the AssemblyLine Stepper, refer to the "Configuration Editor" section of the Configuring Directory Integrator section of the product documentation.

Tracing and First Failure Data Capture (FFDC) IBM® Security Verify Directory Integrator is instrumented throughout its code with tracing statements, using the JLOG framework, 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).

For information about IBM® Security Verify Directory Integrator logging, see the "Tracing and FFDC" section in the Installing and Administering section of the product documentation.

Sandbox IBM® Security Verify Directory Integrator includes a Sandbox feature that enables you to record the operation of one or more Connectors in an AssemblyLine for later replay without the necessary data sources being available. This feature uses the System Store.

This feature can be very useful when providing support materials. Often, the time to reproduce the environment for an AssemblyLine and the state of data sources to reproduce a condition can be quite comprehensive. With a sandbox database with a recorded session, a support person can run the AssemblyLine without having access to all data stores the AssemblyLine requires. In addition, the AssemblyLine configuration can be modified to print out more information if that is necessary. The only change that cannot be done to the AssemblyLine configuration is to make additional calls or reorder the calls to recorded components. This would cause an error during playback as calls to the connector would not match the next expected call to the connector.

For more information, see the section called "Debugging features in IBM® Security Verify Directory Integrator" in Configuring Directory Integrator section of the product documentation.

Performance Test and Debug Utilities IBM® Security Verify Directory Integrator Version 10.0.0 includes Performance Test and Debug Utilities tools. The Performance Test tool monitors the system-level parameters and the server, records and logs information for the system and server at specified intervals of time. Performance test parameters are then used for throughput measurement and capacity planning.

The Debug Utilities tool identifies memory usage and memory leaks in specific IBM® Security Verify Directory Integrator components by collecting information at specific intervals and upon certain actions.

See Performance Test Utilities and Debugging for more information about IBM® Security Verify Directory Integrator benchmarking tools.