WAS traditional collector Recipe

1. Log onto the deployment manager node (or a specific node or Base node) and ensure you're the user that runs WAS or root.
2. Change directory to somewhere outside the WAS home directory that has at least a few hundred MB free. For example:

   cd /tmp/

3. If you have a large environment, edit /opt/IBM/WebSphere/AppServer/profiles/$PROFILE/bin/collector.sh and update the -Xmx value. There is no other way than editing collector.sh because, in recent fixpacks, -Xmx1024m is specified explicitly (and IBM Java doesn't support _JAVA_OPTIONS). Note that this change will be reverted on each fixpack upgrade. For example:

     -Xmx3g \

4. Execute collector.sh by specifying the full path to it. For example, replace the path to WebSphere and $PROFILE with the profile name (e.g. the deployment manager profile):

   /opt/IBM/WebSphere/AppServer/profiles/$PROFILE/bin/collector.sh > diag_collector.txt 2>&1

5. Once it completes, review the end of the diag_collector.txt file for any obvious errors running the collector. A healthy collection ends with Return code: 0.
6. Upload *WASenv.jar and diag_collector.txt

For details, see the collector.sh documentation.

Previous Section (WAS traditional Common Diagnostic Files Recipe) | Next Section (WAS traditional runtime diagnostic trace script) | Back to Table of Contents