Preventive Service Planning
Abstract
This tech note contains corrections, updates, and performance precautions to the ClearCase and ClearQuest 7.1.x help in the Change Management Server (CM Server) topic titled "Configuring logging."
Content
Use the following URLs to access the topic "Configuring logging" in the Rational ClearCase and Rational ClearQuest Information Centers, respectively:
Rational ClearCase Information Center:
https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/topic/com.ibm.rational.clearcase.cc_admin.doc/topics/cm_server/logging.htm
Rational ClearQuest Information Center:
https://publib.boulder.ibm.com/infocenter/cqhelp/v7r1m0/topic/com.ibm.rational.clearquest.webadmin.doc/topics/cm_server/logging.htm
Correction and additional precautions for the TSLogger section of the "Configuring logging" topic
The tslogger logging mechanism, which is the logging mechanism employed by the backend RPC process components of the CM Server, is disabled by default. Enable this logging only with the assistance of Support, and limit its use to short periods of time. The tslogger.properties file is located in <RATIONAL_HOME>/common/CM/bin (for example, C:\Program Files\RationalSDLC\common\CM\bin on Windows, and /opt/IBM/RationalSDLC/common/CM/bin on the UNIX system and Linux).
Updates to the Configuring WebSphere Application Server logging and tracing section of the "Configuring logging" topic
The out-of-the-box WebSphere Application Server logging level is set to INFO for all components by default. Only change the logging level if Support instructs you to do so to diagnose an issue. Increasing the logging level higher than INFO (such as FINE, FINER, or FINEST) for a component running in WebSphere Application Server, including the CM Server components, can adversely affect performance either when set to the higher level for too long or when set to the higher level for too many packages at one time.
- Replace this sentence:
You should set the number of log files to rotate through to at least 40, and set the log file size to at least 40 MB.
with this sentence:
You should set the number of log files to rotate through to at least 20, and set the log file size to at least 20 MB.
- Replace this sentence:
Open the com.ibm.rational.* option and select com.ibm.rational.stp.*.
with the following text:
Open the com.ibm.rational.* option and select com.ibm.rational.stp.* if you want to change the logging level for all of the CM Server packages, or select one of the packages listed under com.ibm.rational.stp to change the logging level for that specific package.
Update to the Configuring CM API logging section of the "Configuring logging" topic
Replace the following sentence:
- Changes to the logging.properties file are recognized by the CM API-based application within about 10 seconds. You do not need to stop and restart the application.
- In ClearCase and ClearQuest v7.1.0.x, changes to the logging.properties file are automatically recognized by the CM API-based portion of your application within approximately 10 seconds. You do not need to stop and restart the application.
Starting in ClearCase and ClearQuest v7.1.1.0, changes to the logging.properties file are not automatically recognized by the CM API-based portion of your application. You must stop and restart the application for these changes to take affect.
Product Synonym
ClearCase
Was this topic helpful?
Document Information
Modified date:
01 August 2018
UID
swg21326254