Collector Tool

Run the collector tool with the -Summary option to produce a lightweight text file and console version of some of the information in the Java archive (JAR) file that the tool produces without the -Summary parameter.

The collector summary option produces version information for the WebSphere Application Server product and the operating system as well as other information. It stores the information in the Collector_Summary.txt file and writes it to the console.

To run the collector summary option, start from a temporary directory outside of the WebSphere Application Server product installation root directory and enter one of the following commands:

[Linux][AIX HP-UX Solaris]app_server_root/bin/collector.sh -Summary

[Windows]app_server_root \bin\collector.bat -Summary

The collector tool is part of a strategy of making problem reporting as easy and complete as possible.

There are two phases of using the collector tool.

The first phase runs the collector tool on your WebSphere Application Server product and produces a Java archive (JAR) file.

The IBM Support team performs the second phase, which is analyzing the Java archive (JAR) file that the collector program produces.

Procedure

Run the collector tool.

Log on to the system as root or a member of the administrator group on a Windows platform.

Verify that Java 1.2.2 or higher is available in the path.The collector program requires Java code to run. It also collects data about the IBM Developer Kit, Java Technology Edition in which it runs.If there are multiple Developer Kits on the system, verify that the one that the WebSphere Application Server product uses is the one in the path for the collector program.

If the Developer Kit being used by the WebSphere Application Server is not available, put another Developer Kit in the path for the collector program so that you can collect everything except data about the Developer Kit that WebSphere Application Server Network Deployment is using.

Verify that all necessary information is in the path being used by the collector program and that you are not running the program from within the WebSphere Application Server product installation root directory.

Make a working directory where you can start the collector program.

Make the working directory the current directory.

Run the collector program . .

app_server_root\bin\collector.bat

app_server_root\bin\collector.bat -profileName profile_name

profile_root\bin\collector.bat

app_server_root\profiles\dmgr\bin\collector.bat

Issuing the command from the profile also runs the setupCmdLine.bat/sh file in the profile’s bin directory. This file sets an environment parameter that the collector uses to determine which profile’s data to collect.

Results

The collector program creates the Collector.log log file and an output JAR file in the current directory.

The name of the JAR file is  host_name-cell_name-node_name-profile_name.JAR

The Collector.log log file is one of the files collected in the host_name-cell_name-node_name-profile_name.JAR file.

What to do next

Send the host_name-cell_name-node_name-profile_name.JAR file to IBM Support for analysis.

Collector tool output

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 that are located under directory root in the JAR file

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