Trace event logs
Verify Identity Access provides configurable tracing capabilities that can aid in problem determination. Unlike message logs, trace logs (or tracing) are not enabled by default.
Trace data is intended primarily for use by IBM® Software
Support. Trace data might be requested as part of diagnosing a reported problem. However,
experienced product administrators can use trace data to diagnose and correct problems in a Verify Identity Access environment.
Attention: Use
trace with caution. It is intended as a tool to use under the direction of IBM Software Support. Messages from tracing are sometimes cryptic, are not
translated, and can severely degrade system performance.
Trace logs are best suited to situations where a problem is easily reproduced, is short-lived in duration, and can be produced without significant trace generation from other system activity. Enabling tracing can adversely affect the performance of Verify Identity Access and its associated products and applications.
Tracing can be activated when servers, daemons, and applications start by using tracing configuration files and Java™ properties files. In some cases, tracing can be activated dynamically by using the server task trace command with the set option.
Note: Tracing from the C-language portions of Verify Identity Access is controlled through tracing
configuration files. Similarly, tracing from the Java language
portions of Verify Identity Access is controlled through
Java properties files. When relevant, the distinction between
these two methods of trace handling is mentioned.