News
Abstract
This document describes how to use the IBM Support Assistant Lite (ISA Lite) for IBM Rational ClearQuest 7.0. This is a tool that provides an automated way for you to gather initial data needed for the Rational support team to analyze problems.
Content
ISA Lite for Rational ClearQuest 7.0 is a customized subset of the IBM Support Assistant Workbench that provides automated data collection capability specific for Rational ClearQuest 7.0. If you do not have IBM Support Assistant Workbench installed and need to provide information for our support team, you can use this tool to quickly gather information using ISA Lite for Rational ClearQuest 7.0
*Update*: The ISALite collector has been updated to include:
- Capability to handle collection 64 bit systems & Windows 7
- Fix - system event log collection
Prerequisites |
Downloading and Launching ISA Lite |
Using ISA Lite |
Data Collection Options |
Details: Rational ClearQuest Web Collectors |
Details: Rational ClearQuest Client Collectors |
Data Collector Completion Options & Uploads |
- You need an IBM ID and password to download ISA Lite. Register here if you do not already have one.
- Please use the JAVA JRE that comes with ClearQuest. This information is listed: here.
Downloading and Launching ISA Lite
- Download ISA Lite for Rational ClearQuest 7.0 from: https://www.ibm.com/services/forms/preLogin.do?source=swg-isalite&S_PKG=isalrcq70
- Extract the .zip file in a folder.
- If your platform does not have unzip utility, you can use jar to unzip file: jar xf ISALiteforRationalClearQuest_7.0_20110923_134.zip
- Open a command prompt, or shell. All information below must be run from the command prompt.
- Change directory: cd <extracted location>/ISALite.
- Windows:
- If Java is available in your path , simply run: runISALite.bat
- If Java is not available on your path, ISA Lite will prompt you for the path. This path should contain a "bin" or a "jre" directory. You can also set JAVA_HOME before running ISA Lite:
- Example: set JAVA_HOME=C:\Program Files\Rational\Common\java
- Once this is completed, run: runISALite.bat or runISALite.bat -console to run in console mode.
- In ksh: chmod a+x *.sh to ensure .sh files in ISALite folder can be executed.
- If Java is available in your path , simply run: ./runISALite.sh
- If Java is not available on your path, ISA Lite will prompt you for the path. This path should contain a "bin" or a "jre" directory. You can also set JAVA_HOME before running ISA Lite:
- Example (in ksh) export JAVA_HOME=/opt/rational/common/java
- If you are running in a desktop environment: run: ./runISALite.sh
- If you are running in a console / terminal environment, run: ./runISALite.sh -console
Linux / Unix
Using ISA Lite (non-console mode)
- Select a data collector to run. Details for each collector are listed below.
- Fill in the Filename field.
- Click the Collect Data button to start data collection.
- (Optional) Click on "Show execution details" to see the collector execution details.
- When finished, simply close the window.
Example:
To automate ISA collection and/or to run silently, please review the following two documents that discuss performing a silent recording, and a silent playback via command line:
http://www.ibm.com/support/docview.wss?uid=swg27017356
see section : Using ISALite for Remote Collection / "To further simplify ..."
http://www.ibm.com/developerworks/websphere/techjournal/0809_supauth/0809_supauth.html
see : "Silent Collection"
Using this technique you can record an ISA execution, and subsequently playback via command line silently.
Data Collection Options
This is a listing of the data collectors included in the package as well as a high level description of its functionality.
Collector Name | When do you use this collector? |
| Use this collector to gather data for troubleshooting ClearQuest integration issues with Rational Test products. Detailed description: Rational ClearQuest Integration Collector |
| Use this collector to gather data necessary to debug general CQ web server problem without restarting services. Follow link for more information on: Data gathered by collector and detail walk thru. |
| Use this collector to gather data necessary to debug general CQ web core server problem. Services will be restarted to enable CQ core trace. Follow link for more information on: Data gathered by collector and detailed walk thru |
| Use this collector to gather data necessary to debug general CQ web server performance issues. Services will be restarted to enable CQ core trace specific to performance issues. The enablement settings are as follows:
Linux Follow link for more information on: Data gathered by collector and detail walk thru. |
| Use this collector to gather data necessary to debug general CQ web server database connection issues. Services will be restarted to enable CQ core trace specific to database connection issues. The enablement settings are as follows:
Linux
Follow link for more information on: Data gathered by collector and detail walk thru. |
| Use this collector to gather data necessary to debug CQ web server issues, providing capability to set customized trace setting. Services will be restarted. Follow link for more information on: Data gathered by collector and detailed walk thru |
| Use this collector to gathers data necessary to debug general CQ client issues without problem recreation. Follow link for more information on: Data gathered by collector and detailed walk thru. |
| Use this collector to gathers data necessary to debug general CQ client issues with problem recreation using default trace settings. The collector will enable ClearQuest core trace and prompt for problem recreation. When completes, data is gathered and trace is disabled. Follow link for more information on: Data gathered by collector and detailed walk thru. |
| Use this collector to gathers data necessary to debug general CQ client issues with problem recreation using customizable trace settings. The collector will enable ClearQuest core trace and prompt for problem recreation. When completes, data is gathered and trace is disabled. Follow link for more information on: Data gathered by collector and detailed walk thru. |
| Use this collector for Rational Common Licensing issues. The data collected provides our support team initial information to assess FlexLM licensing issues. Detailed description: Rational FlexLM data collector. |
| Use this collector to gather WinMSD information for our support team. The collector executes msinfo32.exe on windows system and gathers the output. An upload option is provided. This information helps the support team to get a better understanding of user's environment. |
At the end of the data collection, you'll have an option to upload the data collected to IBM if you have a PMR available. Please see Data Collector Completion Options & Uploads for additional information.
Details: Rational ClearQuest Web Collectors
The Rational ClearQuest Web collectors enables a user to automatically gather the data specified by MustGather ClearQuest Web Server. Additionally, this tool also gathers system information that can help our support engineers with troubleshooting ClearQuest web issues. Five collection options are provided.
Basic collection without trace or problem recreation: Collection with trace enablement for problem recreation
- Rational ClearQuest Web General Collector
- Rational ClearQuest Web General Performance Collector.
- Rational ClearQuest Web Database Connection Issues Collector
- Rational ClearQuest Web - Customized Trace Collector
- You'll need to run these collectors with appropriate permissions to restart server services
- You'll need to have appropriate permission to update:
- Windows: Registry - to enable core trace settings.
- Linux / Unix : ClearQuest web services start up files.
IMPORTANT: For the above collectors, ClearQuest Web Services will be restarted.
Data Collected by Rational ClearQuest Web Collectors
Listing of data collected by the set of Rational ClearQuest Web Collectors.
- Basic system information
- A subset of Installation Manager information. This is relevant when you have other Rational products installed.
- Windows: Registry information, system Event logs, mem and systeminfo.
- Linux or Unix System
- uname -a
- umask
- df - m
- env
- ps -aef
- For OS mem information:
- Linus: free -m
- AIX: bootinfo –r
- SunOS/Solaris: /usr/sbin/prtconf | grep "Memory size"
- Linux/Unix Specific ClearQuest information
Folder | File | Description |
/IM/InstallationManager | *.* | Basic installation information only. Files: installed.xml, installRegistry.xml, installed.xsd, and installed.xsl |
Folder |
| Description |
/ | regfile.rational.software.export.txt | Registry export of key: [HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software] |
regfile.rational.software.export_ANALYSIS.txt | Listing of product entries listed under registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software] | |
regfile.sware.uninstall.export.txt | Registry export of key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall] | |
regfile.sware.uninstall.export_ANALYSIS.txt | Listing of product entries and version in above key that contains "Publisher"="Rational Software" | |
win_mem_out.txt | Output of mem | |
win_systeminfo_out.txy | Output of systeminfo | |
/system_info | *.* | System event files |
Folder |
| Description |
/ | Linux_UnixSystemInfo.txt | Gathers output from the following execution: |
Folder | File | Description |
/CQDB_registry | *.* | ClearQuest DB registry information. Collect if available. |
- ClearQuest configuration and log files specified by MustGather ClearQuest Web Server.
Folder | File | Description |
/<product_install> | *.* | Configuration and logs gathered from the <product_install> directory. |
- ClearQuest web trace output.
- Windows: C:/cq_trace.log
- Linux/Unix: /tmp/cq_trace.log
- Windows: In the enable registry file, look for entry "output"
- Linux/Unix: In the "after/start_cqreg.sh" file, look for file specified by CQ_DIAG_OUTPUT
- ClearQuest web data relating to enabling and disabling trace setting.
- Logging.xml files before and after trace enablement.
- Windows: registry file that enables trace
- Linux/Unix system: start_cqreg.sh files before and after trace enablement in directories "before" and "after"
- Logging.xml files before and after trace is disabled.
- Windows: registry file that disables trace
- Linux/Unix system: start_cqreg.sh files before and after trace is disabled in directories "before" and "after"
NOTE: existing logs of similar patterns are also collected.
Folder | File | Description |
/ or /tmp or <user_specified> | cq_trace.log* | Trace output. By default, trace output are set to NOTE: If the user had specified a different location or file name, then that information is used to gather the trace output. To determine where the trace output is located, please see /trace_settings/enable/*.*. |
These set of data are specific to the trace enabling collectors.
Folder | File | Description |
/ | LOCATION_OF_PREVIOUS_LOGS.txt | This file contains the location of the target log directory in which old logs are moved to. This is available only If the user has indicated to move the logs during problem recreation. |
/trace_settings /enable | *.* | Trace settings used to enable trace . Listing includes: |
/trace_settings /disable | *.* | Trace settings used to disable trace . Listing includes: |
Detailed Walk thru for Rational Web General Collector - No Service Restart
- This collector gathers all above data without enabling/disabling trace settings.
Introduction
The collector will first inform you what it is going to collect. Click OK to proceed.
The collector will run to completion and request feedback and ftp options.
Please continue to Data Collector Completion Options & Uploads for additional information.
Detailed Walk thru for the Web General Collector , Performance Collector and Data Connections Issues Collector.
- This set of collectors will restart ClearQuest web services to enable trace settings, specified by the individual collectors. User is then asked to recreate the problem they had encountered. Once the problem recreation is completed, trace is disabled and the data listed above are gathered.
- Select 'OK' - If you like the logs to be moved - provide a directory location in which you have write permission.
- Select 'Skip' - If you do not want the logs to be moved.
Introduction
- The collector will first inform you what it is going to collect. Click OK to proceed.
Problem Recreation
- Prompt: Move Existing Logs
This prompt is available for Rational ClearQuest Web collectors that enables trace. This allows old trace and log files to be moved to a target directory. Logs will be moved once the collector is ready to restart ClearQuest services.
Prompt : ClearQuest Web Service has been Enabled & Please Recreate the ClearQuest Web Server Issue
This is to let you know that ClearQuest Web Services has been enabled.
Please complete problem recreation. When you are finished, click OK and this will disable trace, and data collection will start. The collector will run to completion and request feedback and ftp options.
Please continue to Data Collector Completion Options & Uploads for additional information.
Detailed Walk Thru for Rational ClearQuest Web - Customized Trace Collector
- This collector will restart ClearQuest web services to enable trace settings that are provided by the user. User is then asked to recreate the problem they had encountered. Once the problem recreation is completed, trace is disabled and the data listed above are gathered.
- Enable CQ CoreTrace field: provide a registry file that contains the appropriate trace settings. By default, a general trace setting registry file has been provided.
- Disable CQ CoreTrace field: provide a registry file that resets the trace settings. By default, a general trace disable setting registry file has been provided.
Introduction
The collector will first inform you what it is going to collect. Click OK, to proceed
Provide your trace settings
- Windows:
Select OK to continue.
Linux/Unix :
In each field, provide the appropriate settings for these environment variables to be set within start_cqreg.sh By default, these are settings for the general web server issues.
NOTE: blanks or "" are not accepted.
Please continue to Data Collector Completion Options & Uploads for additional information.
Details: Rational ClearQuest Client Collectors
The Rational ClearQuest Clients collectors enables a user to automatically gather the basic system information and ClearQuest RCP data that will provide initial diagnostic information for the Rational support team. There are three collection options.
- Basic collection without trace or problem recreation: Collection with trace enablement for problem recreation:
Data Collected by Rational ClearQuest Web Collectors
- Basic system information as stated above.
- If on the same system - configuration files specified by MustGather ClearQuest Web Server. NOTE: This does not include the log files.
- ClearQuest Client RCP information
Folder | File | Description |
/ClearQuest_RCP | *.* | Gathers information relating to clearquest rcp product. These includes product configuration information and ini files. |
- ClearQuest client 7.0 trace output.
- Windows: C:/cq_trace.log
- Linux/Unix: /tmp/cq_trace.log
- Windows: In the enable registry file, look for entry "output"
- Linux/Unix: In the "after/start_cqreg.sh" file, look for file specified by CQ_DIAG_OUTPUT
- ClearQuest web data relating to enabling and disabling trace setting.
Folder | File | Description |
/ or /tmp or <user_specified> | cq_trace.log* | Trace output. By default, trace output are set to NOTE: If the user had specified a different location or file name, then that information is used to gather the trace output. To determine where the trace output is located, please see /trace_settings/enable/*.*. |
These set of data are specific to the trace enabling collectors.
Folder | File | Description |
/trace_settings /enable | *.* | Windows registry file that enables trace is recorded. |
/trace_settings /disable | *.* | Windows registry file that disable trace settings is recorded. |
Detailed Walk Thru for Rational ClearQuest Client General Collector
- This collector gathers all above data without enabling/disabling trace settings.
Introduction
The collector will first inform you what it is going to collect. Click OK, to proceed
Click OK to continue.
The collector will run to completion and request feedback and ftp options.
Please continue to Data Collector Completion Options & Uploads for additional information.
Detailed Walk Thru for Rational ClearQuest Client - General Trace Collector
- This collector gathers all above data and will enable trace with default trace settings. Collection happens after trace has been disabled.
Introduction
The collector will first inform you what it is going to collect. Click OK, to proceed
- Prompt: Please close all instances of ClearQuest Clients.
- Select 'OK' once you've provided the full path to the ClearQuest client program.
- Select 'Skip' if you would like to skip this step. This would mean you will not be able to gather problem recreation data through this collector tool.
Before trace settings is enabled, all instances of ClearQuest Client needs to be closed. Once you have completed that task, click OK to proceed.
Launching ClearQuest client for problem recreation:
Due to difference in how environment and trace settings are enabled on Windows and Linux / Unix systems, a different set of instruction is provided.
- Windows
At this point, ClearQuest client trace has been enabled. You'll need to launch the ClearQuest Client you have an issue with and recreate the problem you had encountered.
Click OK once you've done so.
Linux/Unix
The collector will require that you provide a path referencing the ClearQuest client program you are having issues with. This allows the collector to launch the client you've specified with the debug trace settings you've provided
At this point, the collector will attempt to launch your script with appropriate trace settings enabled in the environment. Please re-create your problem with the client program that has been launched by the tool. Click on OK when you've completed problem recreation.
Example shown here indicates the parameters that were provided by default.
This asks you to close the client program that you (or the collector) had launched.
Click 'OK' to continue and disable trace settings.
Please continue to Data Collector Completion Options & Uploads for additional information.
Detailed Walk Thru for Rational ClearQuest Client - Customized General Collector
This collector gathers all above data and will enable trace with user provided trace settings. Collection happens after trace has been disabled.
- Introduction
- Enable CQ CoreTrace field: provide a registry file that contains the appropriate trace settings. By default, a general trace setting registry file has been provided.
- Disable CQ CoreTrace field: provide a registry file that resets the trace settings. By default, a general trace disable setting registry file has been provided.
The collector will first inform you what it is going to collect. Click OK, to proceed
Provide your trace settings
- Windows:
Linux/Unix :
In each field, provide the appropriate settings for these environment variables. These will enable trace for the ClearQuest client, when launched with these environment settings. By default, these are settings for the general client issues. NOTE: blanks or "" are not accepted.
Please continue to Data Collector Completion Options & Uploads for additional information.
Data Collector Completion Options & Uploads
When the collector is completed, it will request feedback about ISA. Select Yes, to provide feedback. Select No to continue.
You'll also be provided with data upload options. This will allow you to send the collected data to IBM or another location via FTP or HTTPS.
IMPORTANT: To upload information to IBM, you'll need to have a PMR number. This is obtained when you work with our support team. If you do not have a PMR number, but do have support contract, you can leverage the Software Support page to open a service request and included the collected data with the service request.
IBM Service Request Page: https://www.ibm.com/support/servicerequest/
The upload options are:
- Send the Logs to IBM using secure transfer (HTTPS). You'll need an PMR number to transfer the data to IBM. This sends the collected data to IBM Support team through the HTTPS protocol.
- FTP the Logs to IBM Support (unencrypted). You'll need an PMR number to transfer the data to IBM. This sends the collected data to IBM Support team through the FTP protocol. This is a less secure option.
- FTP the Logs to a Different Location (unencrypted) This allows you to send the collected data to another location via FTP. You'll need to provide the target FTP location and appropriate authentication to access it.
- Do Not FTP the Logs. Do nothing.
Click OK to continue. If you choose options other than "Do Not FTP the Logs" above, you will need to fill in additional information required to complete the upload.
When the collector completes, the .zip file is created at the location specified in Output File name. You can use any unzip tool to extract the files to examine the content of collected data.
Related Information
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21409491