Question & Answer
Question
Answer
Default Installation Locations
Basic Verification Information
Gathering Diagnostic Logs for ClearQuest Web on Microsoft Windows
Gathering Diagnostic Logs for ClearQuest Web on Linux or UNIX
ClearQuest Web Server Diagnostic Logging and Information
Default Installation Locations
These are the default installation directories for Rational home and Rational common components.
If you are using a non-default installation path, keep that in mind when reviewing these instructions. RATIONAL_HOME refers to the location where Rational products are installed. 32-bit Windows: 64-bit Windows: Linux/UNIX: RATIONAL_COMMON refers to the location where common components are installed. 32-bit Windows: 64-bit Windows: Linux/UNIX: Note: On some UNIX operating systems, the path might have a lowercase "ibm" directory. You can also access the Rational home and common directories using these symbolic paths:
|
Basic Verification Information
Note: With steps 2 through 5, if you do not receive the expected verification that the software is running correctly, take a screenshot or save the message to file for IBM Support.
|
Gathering Diagnostic Logs for ClearQuest Web on Microsoft Windows
NOTE: If you are on ClearQuest 8.0.0.5 and later versions, you can enable, disable, and change ClearQuest Core trace setting dynamically without having to stop and restart the ClearQuest Web service. This is done by adding the Reset register key to the ClearQuest Core diagnostic keys. Here is an example of how to set it in the trace file:
"Trace"="CQRPC;THREAD;SQL;SESSION;HOOKS;THROW;EDIT;RESULTSET;API;PERL;DB_CONNECT;DBDESC;LICENSE" NOTE: This key location is only applicable when WebSphere Application Server (WAS) service is run as the "local system" account. If the WAS profile service is not running as "Local System" account, then the user must log onto the machine as the user that is running the web service, and add the key to the following location: [HKEY_CURRENT_USER\Software\Rational Software\ClearQuest\Diagnostic] To disable tracing (without restarting ClearQuest Web), change the value of at least Output to an empty string. The other values can remain or also be cleared; they will have no effect if there is no specification of where to send the trace output. To stop dynamic changes, change the value of Reset to an empty string. Doing so is the same as if "Reset" does not exist. |
Gathering Diagnostic Logs for ClearQuest Web on Linux or UNIX
|
ClearQuest Web Server Diagnostic Logging and Information
These sections instruct you on how to prepare the diagnostic information for gathering along with the ClearQuest Web Server information. You should only follow these instructions at the request and guidance of a ClearQuest Support Engineer.
Collecting MBean attribute information You can configure the ClearQuest Web Server using a variety of different variables called MBean attributes. When experiencing problems with the ClearQuest Web Server, it is worth verifying that these attributes are correctly established. Incorrect attribute values can cause problems with the starting or stability of the server processes. You can send IBM Rational Support a summary of your custom MBean configuration settings with these instructions:
More information on proper MBean configuration You can find more information about this in these documents:
Increasing ClearQuest Web Server logging levels These are the steps for increasing the logging level detail on the ClearQuest Web Server. By changing the logging level, you are increasing the trace output and diagnostic information in the ClearQuest Web Server logs. With these instructions, you will also verify that file count and file size of these logs is sufficient for reproducing a problem during a trace. Increasing the diagnostic detail can affect system performance. This should only be done for short periods of time. Be sure to restore logging to original settings when such detail is not needed.
Restoring standard ClearQuest Web Server logging levels These are the steps for restoring the logging levels of the ClearQuest Web Server to their original state.
|
Was this topic helpful?
Document Information
Modified date:
22 May 2020
UID
swg21638434