Java and IBM Content Manager connector logging

You can use the log control utility in the system administration client to configure the log settings for the Java™ APIs.

The connector logging utilities store all program exceptions, including exceptions that are not errors. Occasionally, error messages appear in the log file that are not sent to the user. In some cases, the API or user application can recover or continue without user interaction required. The ${user.name}.dklog.log log file contains the log results from IBM® Content Manager connector actions.

The ${user.name} is the computer logon user ID that is used to qualify the log output. The logon user ID will be used to replace ${user.name} which will help to avoid output collisions from multiple users.

Important: When reading the log files, note the context within which the exceptions and messages are logged. Also, when debugging, concentrate the log results on current errors and events before them by defining constraints in the API log file. More limited searches can improve system performance.

If the system administration client is not available, you can configure the APIs by changing values in the logging configuration file; for more information, see Changing the logging configuration files for the IBM Content Manager connectors.

Note: The log4j 1.x logger has been deprecated in V8.7; do not use it with this version, or any future versions.

In the log control utility, you can change the Java default log file names, log file path settings, maximum file size, and the level of error information to send to the log file. For more information about using the log control utility to configure API logging, see Logging and tracing utility: Java APIs.