Use this information to troubleshoot administrative tasks
for Report Server for ClearQuest®.
Task |
How to... |
Manually updating an RCQR.jar file |
Manually updating the jar files is not recommended but if
doing so is necessary, ensure that after you update the \RationalSDLC\ClearQuest\RCQR\server\rcqr-update-site or
the reportalprofile\classes directory, you also
clean up the reportalprofile\temp directory.
|
Modifying the log trace level |
Log levels for the cqregistry.jar file can be set from the
WAS admin console:- Start the WAS Admin console.
- Click TroubleShooting >> Logs and Trace.
- Click server1.
- Click Change Log Details Levels.
- In the list of classes available, look for the com.ibm.rational.cq.was.userregistry.CQUserRegistry file
and change the log level. Logs for log levels below FINE go to the trace.log file.
To set the log levels for other classes: - Open the RationalSDLC/clearquest/RCQR/server/log4j_was.properties
file.
- Set the component log level:
# Set component log level
log4j.logger.com.ibm.rational.project.service.ProjectRestService=WARN
log4j.logger.com.ibm.rational.report.service.DataSourceRestService=WARN
log4j.logger.com.ibm.rational.report.service.ReportRestService=DEBUG
log4j.logger.com.ibm.rational.report.service.ReportCategorizationRestService=DEBUG
log4j.logger.com.ibm.rational.security.service.SecurityRestService=WARN
log4j.logger.com.ibm.rational.user.service.UserManagementService=WARN
log4j.logger.com.ibm.rational.user.service.UserRestService=DEBUG
log4j.logger.com.ibm.rational.user.registry.cq.CQUserRegistryService=DEBUG
Normally,
the log level should be set to WARN. When a problem needs to be debugged,
to capture more information set the log level to DEBUG.
|
Correcting the port number for the link for snapshots |
Add the following two properties to the /RationalSDLC/clearquest/RCQR/server/teamserver.properties file:com.ibm.team.repository.server.repourl.port.http = 15080
com.ibm.team.repository.server.repourl.port.https = 15443
|