Why and when to perform this task
To run the collector tool:Steps for this task
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.
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 WebSphere Application Server installation root directory is determined at installation. It is identified in the setupCmdLine.sh file (or the setupCmdLine.bat file 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.Related concepts
Gathering information with the Collector tool
Analyzing collector tool output
Related reference
Collector summary