Gather information with the collector tool

 

+

Search Tips   |   Advanced Search

 

Overview

The collector tool gathers information about a WAS installation and packages it in a JAR file that can be sent to IBM Customer Support. Information in the JAR file includes...

IBM includes the collector tool in the product code.

There are two phases of using the collector tool.

  1. Run the collector tool on the WAS system and produce a JAR file.

  2. IBM Support analyzes the JAR file produced by the collector program.

There are two ways to run the collector tool.

Run the collector tool as the root user or administrator user to ensure access to system files.

The collector tool collects information about the default profile if you do not use the optional parameter to identify another profile.

 

Traverse the system to gather relevant files and command results.

  1. Log on to the system as root or a member of the administrator group on 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 WAS 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 WAS ND is using.

  3. Verify that all necessary information is in the path being used by the collector program...

    • For Unix verify that the PATH contains...

      • /bin
      • /sbin
      • /usr/bin
      • /usr/sbin

    • For Windows include regedit in the path.

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

  5. Make the working directory the current directory.

  6. Run the collector tool.

    To gather one copy of profile data...

    app_server_root/bin/collector.sh|bat

    To gather data from a specific profile...

    app_server_root/bin/collector.sh|bat -profileName profile_name

    To gather data from a specific server...

    app_server_root/bin/collector.sh -servername server_name

    To gather data for a particular server in a particular profile.

    app_server_root/bin/collector.sh -servername server_name -profileName profile_name

    You can run the collector tool located in a profile's bin directory...

    profile_root/bin/collector.sh

    Issuing the command from the profile also runs...

    profile_root/bin/setupCmdLine.bat|sh

    ...which sets environment variables used by the collector.

    To collect data for the deployment manager...

    app_server_root/profiles/dmgr/bin/collector.sh

  7. The collector program creates the following output in the current working directory...

    hostname-cellname-nodename-profilename.jar

    The Collector.log log file is one of the files collected.

 

What to do next

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


Collector tool output
collector command - summary option