You can customize the configuration of TSlogger, the package
used to log Change Management (CM) Server backend ONCRPC server processes.
About this task
While the default settings for TSlogger logging and tracing
do not require modifications, you can customize these settings by
editing some of the properties in the file tslogger.properties.
The file contains labeled areas where you can modify the property
values and a corresponding range of valid values. The TSlogger logging
mechanism is disabled by default to avoid problems that can occur
under heavy load of the CM Server. These problems include requests
that might take up to 10 minutes to respond or requests that might
fail when TSlogger is enabled.
The
tslogger.properties file
is located here:
- On Windows:
- \Program Files\IBM\RationalSDLC\common\CM\bin\tslogger.properties
- On the UNIX System and Linux:
- /opt/rational/common/CM/bin/tslogger.properties
The log and trace files are written to the following
locations:
- On Windows:
- \Program Files\IBM\RationalSDLC\common\CM\logs\server1\ccrpc (and \cqrpc)
- On the UNIX system and Linux:
- /opt/rational/common/CM/logs/server1/ccrpc (and /cqrpc)
The log and trace files include:
- SystemOut.log
- General log output, disabled by default.
- SystemErr.log
- Error/exception output, disabled by default.
- trace.log
- Trace output, disabled by default.
As the log and trace files fill up, output rotates
to the next file. Once the maximum number of files in the rotation
is reached, the oldest file is removed to make room for the next file.
Summary
of the logging levels:
- OFF: Disable all logging and tracing.
- ERROR: Corresponds to SEVERE in JSR47.
- WARNING: Corresponds to WARNING in JSR47.
- INFO: Corresponds to INFO in JSR47.
- DEBUG_MIN: Corresponds to FINE in JSR47.
- DEBUG_MID: Corresponds to FINER in JSR47.
- DEBUG_MAX: Corresponds to FINEST in JSR47.
- ALL: Enable all levels of logging and tracing.