Analyzing collector tool output
The first step in using the collector tool on your WebSphere Application
Server product is to run the tool to Running the collector tool. The second
step in using the collector tool is to analyze its output. The preferred method
of performing this analysis is to send the JAR file to IBM Support for analysis.
However, you can use this topic to understand the content of the JAR file
if you perform your own analysis.
You can view the files contained in the JAR file without extracting the
files from the JAR file. However, it is easier to extract all files and view
the contents of each file individually. To extract the files, use one of the
following commands:
- jar -xvf WASenv.jar
- unzip WASenv.jar
Wasenv.jar stands for the name of the JAR file that the collector
tool creates.
The JAR file contains:
- A collector tool log file, collector.log
- Copies of stored WebSphere Application Server files and their full paths
- Operating system information in a directory named OS
- Java information in a directory named Java
- WebSphere Application Server information in a directory named WAS
- Collector shell script (or batch file ) execution information in a directory
named debug
- MQ information in a directory named MQ, if you installed WebSphere
MQ or the embedded messaging feature
- A JAR file manifest

Gathering information with the Collector tool
Collector tool

Running the collector tool

Warning: no string named [rtrb_collectorsumm] found.![[Version 5.0.2 and later]](../../v502x.gif)
Searchable topic ID:
ctrb_readct
Last updated: Jun 21, 2007 4:55:42 PM CDT
WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ctrb_readct.html