Run the collector tool

 

Overview

To run the collector tool:

 

Procedure

  1. Log on to the system as root (or Administrator in a Windows platform).

  2. 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 WAS 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, putting another Developer Kit in the path for the collector program lets you collect all data except information about the Developer Kit.

  3. 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 WAS product installation root directory.

    1. If this system is a Linux or UNIX-based platform, verify that the path contains:

      • /bin

      • /sbin

      • /usr/bin

      • /usr/sbin

    2. If this system is a Windows platform, include regedit in the path.

  4. Create a work directory where one can start the collector program.

  5. Make the work directory the current directory. The collector program writes its output JAR file to the current directory. The program also creates and deletes a number of temporary files in the current directory. Creating a work directory to run the collector program avoids naming collisions and makes cleanup easier. We cannot run the collector tool in a directory under the WAS installation directory.

  6. Run the collector program by entering the command: collector from the command line.

    Using the collector command with no additional parameters gathers one copy of the node data and data from each server in the node, and stores them in a single JAR output file. To gather data from a specific server in the node, use the command collector.bat/sh -servername servername, where servername is the name of the problem server.

    Note:

    Set the path correctly to use the non-qualified version of the command. For Linux and UNIX-based platforms, install_root/bin must be in the path to locate the collector.sh command. For Windows platforms, install_root\bin must be in the path to locate the collector.bat command.

    The WAS installation root directory is determined at installation. It is identified in the setupCmdLine.sh file (or the setupCmdLine.bat file on a Windows platform).

    We can enter a fully qualified path to the collector command. For example, enter this command in a default installation on a Windows platform 

    c:\WebSphere\AppServer\bin\collector.bat

 

Result

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

The name of the JAR file is based on the hostname and package of the Application Server product, in the format: hostname-cellname-nodename-profile.

The Collector.log log file is one of the files collected in the hostname-cellname-nodename-profile file.

 

What to do next

Send the hostname-cellname-nodename-profile file to IBM Support for analysis.

 

See Also


Gathering information with the Collector tool
Analyzing collector tool output

 

See Also


Collector summary