| ISA Lite for Rational ClearCase v7.1 is a customized subset of the IBM Support Assistant Workbench that provides automated data collection capability specific for Rational ClearCase V7.1. If you do not have IBM Support Assistant Workbench installed and need to provide information for our support team, you can use this to quickly gather information using ISA Lite for Rational ClearCase V7.1.
This package contains the following data collection options:
Rational ClearCase
General
- Installation Manager Collector
- ClearCase General Collector - Full
- ClearCase General Collector - Quick
- WinMSD Collector (Windows)
Server
- General Change Management Server Collector
- Server Configuration Collector
- Server Processes Trace Collector
Client
- ClearCase Remote Client Trace Collector
At the end of data collection, you'll have an option to send the data directly to IBM, or to a different location. This is optional. To check what has been collected, extract the .zip file that is created when the collector completes. Details of what is collected as well as collector walk through are described below. Prerequisites - You need an IBM ID and password to download ISA Lite. Register here if you do not already have one.
- You need Java JRE 1.4.2 or greater on your machine to run ISA Lite
Downloading and Launching ISA Lite - Download ISA Lite for Rational ClearCase V7.1 from: https://www.ibm.com/services/forms/preLogin.do?source=swg-isalite&S_PKG=isal131rcc71
- Extract the .zip file in a folder.
- If your platform does not have unzip utility, you can use jar to unzip file: jar xf ISALiteforRationalClearCase_7.1_20091014.zip
- In the same folder, cd ISALite
Windows: - If Java is available in your path , simply run: runISALite.bat
- If Java is not available on your path, you'll need to set JAVA_HOME first:
- set JAVA_HOME=<your full path to Java> This path should point to the bin directory in your Java installation, containing java.exe. No quotes.
- Example: set JAVA_HOME=C:\Program Files\IBM\RationalSDLC\common\JAVA5.0\jre
- Once this is completed, run: runISALite.bat
Linux / Unix - If Java is not available on your path, you'll need to set JAVA_HOME first:
- In ksh: export JAVA_HOME=<your full path to Java> This path should point to the bin directory in your Java installation, containing java
- Example: export JAVA_HOME=/opt/rational/common/java/jre
- You may need to execute : chmod a+x *.sh to ensure .sh files in ISALite folder can be executed.
- If you are running in a desktop environment: run: ./runISALite.sh
- If you are running in a console / terminal environment, run: ./runISALiteConsole.sh
Using ISA Lite (non-console mode) - Select a data collector to run.
- Fill in the Output Filename field.
- Click the Collect Data button to start data collection.
- When finished, simply close the window.
General Collectors These are the set of collectors that deals with general ClearCase issues.
Installation Manager Collector Use this collector for general IBM Installation Manager issues. This can be used to collect information when running into install issues on products that leverages IBM Installation Manager as an install platform.
Full Collector - Full System and CC data collection Use this collector to gather general ClearCase and system information, including WinMSD (if windows), or full lsview / lsvob. Its recommended that you run this with administrator privileges. This will enable files to be collected that may not be accessible by regular account. Error can occur due to inability to gather restricted files.
Quick Collector - System and CC data collection Use this collector to gather general ClearCase and system information. This includes slightly less information than the Full collector. Its recommended that you run this with administrator privileges. This will enable files to be collected that may not be accessible by regular account. Error can occur due to inability to gather restricted files.
WinMSD Collector This is a Windows only data collector. Use this collector to gather WinMSD information on your system.
Server Collectors These are the set of collectors that is use with the ClearCase Change Management Server.
Server Processes Trace Collector Use this data collector to enable process trace on the Change Management Server. User will be prompted to recreate the server issue found, and when completed, to continue with the data collection tool to disable trace settings and gather information. Its recommended that you run this with administrator privileges. This data collector WILL restart your Change Management Server to enable and disable trace settings.
Client Collectors This is the collector that is to be used with issues with ClearCase Remote Client.
ClearCase Remote Client Trace Collector This data collector is used for reproducing problems with ClearCase remote client (CCRC) issues. The data collector will prompt user to launch the selected CCRC product with tracing enabled and debug options. When user completed error reproduction, continue with the data collection so that collector will reset appropriate trace settings and collect data. Its recommended that you have administrator access so that trace settings on common component can be set.
Details: ClearCase Remote Client Trace Collector
This data collector is used for reproducing problems with ClearCase remote client (CCRC) issues. The data collector will prompt user to launch the selected CCRC product with CM API tracing enabled and debug options. When user completed error reproduction, continue with the data collection so that collector will reset appropriate trace settings and collect data. CM API Trace settings: - File modified: <JDK found>/lib/logging.properties
- Settings to enable trace:
com.ibm.rational.stp.common.internal.util.CMLogger.level = INFO com.ibm.rational.stp.common.internal.util.LogHandler.pattern = %h/CMLogger%g.log com.ibm.rational.stp.common.internal.util.LogHandler.limit = 20000000 com.ibm.rational.stp.common.internal.util.LogHandler.count = 20 com.ibm.rational.stp.common.internal.util.LogHandler.append = true com.ibm.rational.stp.common.internal.util.LogHandler.formatter = java.util.logging.SimpleFormatter com.ibm.rational.stp.common.internal.util.CMTracer.level = FINER com.ibm.rational.stp.common.internal.util.TraceHandler.pattern = %h/CMTracer%g.log com.ibm.rational.stp.common.internal.util.TraceHandler.limit = 20000000 com.ibm.rational.stp.common.internal.util.TraceHandler.count = 20 com.ibm.rational.stp.common.internal.util.TraceHandler.append = true com.ibm.rational.stp.common.internal.util.TraceHandler.formatter = java.util.logging.SimpleFormatter - Settings to disable trace:
com.ibm.rational.stp.common.internal.util.CMTracer.level = OFF Debug trace for CCRC (.options) :
More information about enabling trace for CCRC is documented here:
IMPORTANT: The tool updates logging.properties of the JDK used for the web client to enable / disable trace.
- JDK is searched in following order: -vm from product.ini file , <product_install>/jdk/jre. If these does not result in a valid JDK, user will be prompted.
- You'll need to run this collector with appropriate access as it modifies the logging.properties file which may have access restrictions.
Data Collected Detailed Walk Thru for "ClearCase Remote Client Trace Collector " Introduction The collector will first inform you what it is going to collect. Click OK, to proceed  Select the CCRC instance. The collector then prompts you to select the CCRC instance that you have a concern with. 
This list is determined from IBM Installation Manager or default locations for legacy installed. If you had unzipped CCRC onto an existing Eclipse instance, you'll need to select "Others (specified below)", and fill in the full path to the eclipse.exe (or eclipse) that you are using.
If the collector cannot determine what CCRC you are using base on the information available on the system, you'll get a slightly different dialog. Again, please fill in the full path to the eclipse.exe or eclipse that you are using.  Select JDK you are using. You'll need to specify the JDK you are using if the collector cannot determine this information from the CCRC you've selected.
Please specify the full path to the JDK that contains a bin and a lib directory.  Reproducing the Problem and Data Collection Here all the setup are completed, and the tool prompts you to recreate the problem. If you are running ISA Lite GUI - the tool will launch the CCRC instance for you. If you are not running ISALite GUI, you'll have to manually launch CCRC with -debug option. 
Click OK to launch CCRC with -debug options. Click Skip if you want to skip this step.
When you've completed re-creating the problem, please exist CCRC. 
Click OK to continue. This will disable trace settings and collect trace and workspace data.
The collector will run to completion and request feedback and ftp options.
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 4 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.
|