85 lines
4.8 KiB
HTML
85 lines
4.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Collect data for IBM Service</title>
|
||
|
|
</head>
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
<h5><a name="qshcollect"></a>Collect data for IBM Service</h5>
|
||
|
|
<p>WebSphere Application Server - Express includes a Qshell script that collects
|
||
|
|
information about your WebSphere Application Server - Express installation
|
||
|
|
and packages it in a JAR file that you can send to IBM Customer Support to
|
||
|
|
assist in problem determination and analysis. The information includes logs,
|
||
|
|
property files, configuration files, operating system and Java data, and prerequisite
|
||
|
|
software presence and levels. For information on running Qshell scripts, see <a href="../admin/qshadm.htm">Configure
|
||
|
|
Qshell to run WebSphere Application Server - Express scripts</a>.</p>
|
||
|
|
<p>To collect as much data as possible, the collector script is designed to run
|
||
|
|
to completion regardless of errors such as files or commands not found.</p>
|
||
|
|
<p><strong>Note:</strong> You should only run the collector tool when requested
|
||
|
|
to by IBM Service personnel.</p>
|
||
|
|
<p><strong>Authority</strong></p>
|
||
|
|
<p>To run this script, your user profile must have *ALLOBJ authority.</p>
|
||
|
|
<p><strong>Usage</strong></p>
|
||
|
|
<p>To run the collector script, follow these steps:</p>
|
||
|
|
<ol>
|
||
|
|
<li>
|
||
|
|
<p>On the CL command line, run the STRQSH (Start Qshell) command.</p>
|
||
|
|
</li>
|
||
|
|
<li>
|
||
|
|
<p>Run the cd command to change to the directory that contains the script:</p>
|
||
|
|
<pre>cd /home/myprofile</pre>
|
||
|
|
</li>
|
||
|
|
<li>
|
||
|
|
<p>Run the collector script:</p>
|
||
|
|
<pre>/QIBM/ProdData/WebASE/ASE5/bin/collector -instance <em>myInstance</em> JarOutName <em>jarfile</em></pre>
|
||
|
|
<p>where <em>myInstance</em> is the name of the instance for which you want
|
||
|
|
to collect information.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<p><strong>Syntax</strong></p>
|
||
|
|
<p>The syntax of the collector script is:</p>
|
||
|
|
<pre>[<em>fully_qualified_directory</em>]/collector -instance <em>instance</em>
|
||
|
|
[ -JarOutName <em>jarfile</em> ] [ -Summary ] [ -IncludeInstalledApps ]</pre>
|
||
|
|
<p>where <i>fully_qualified_directory</i> is the directory that contains the
|
||
|
|
script.</p>
|
||
|
|
<p><strong>Parameters</strong></p>
|
||
|
|
<p>The parameters of the collector script are:</p>
|
||
|
|
<ul>
|
||
|
|
<li>
|
||
|
|
<p><strong>-instance</strong> <br>
|
||
|
|
This is a required parameter. The value <em>instance</em> specifies the
|
||
|
|
name of the WebSphere Application Server - Express instance for which you
|
||
|
|
want to collect information. </p>
|
||
|
|
</li>
|
||
|
|
<li>
|
||
|
|
<p><strong>-JarOutName</strong> <br>
|
||
|
|
This is an optional parameter. The value <em>jarfile</em> specifies the
|
||
|
|
fully qualified path name of the JAR file to which the collector tool writes
|
||
|
|
the output. The location of the JAR file must be outside of the /QIBM/ProdData/WebASE/ASE5
|
||
|
|
directory structure for the product. By default, the script creates a JAR
|
||
|
|
file in the current working directory. The default file name is WASenv.jar.</p>
|
||
|
|
<p>It is recommended that you specify the -JarOutName parameter.</p>
|
||
|
|
<p><strong>Notes:</strong></p>
|
||
|
|
<ul>
|
||
|
|
<li><p>If you specify a jar file name that exceeds sixty characters, it is truncated to the first sixty characters of the name.</p></li>
|
||
|
|
<li><p>The QEJBSVR user profile must have *RWX authority to the directory to contain the output jar file.</p></li>
|
||
|
|
</ul></li>
|
||
|
|
|
||
|
|
<li><p><strong>-Summary</strong>
|
||
|
|
<br>This optional parameter is supported in versions 5.0.2 and later. If you specify this option, the script generates a summary report of the WebSphere Application Server - Express version and fix level, in addition to information about the i5/OS release level and Java Development Kit level. The summary report is written to the display as well as to file Collector_Summary.txt in the current working directory. When you report a problem to IBM Support, include the Collector_Summary.txt file or output. When you run the collector script with the -Summary parameter, the script does not generate a JAR file.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-IncludeInstalledApps</strong>
|
||
|
|
<br>This optional parameter is supported in versions 5.0.2 and later. By default, the installedApps directory for your instance is not included in the JAR file that the collector tool generates. Specify the -IncludeInstalledApps parameter if you want to include the installedApps directory the generated JAR file.</p>
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
<p><strong>Example</strong></p>
|
||
|
|
<pre>collector -instance testinst -JarOutName /home/myprofile/testinst_svc.jar</pre>
|
||
|
|
<p>This example collects information on the instance testinst and writes the
|
||
|
|
output to testinst_svc.jar in the /home/myprofile directory.</p>
|
||
|
|
</body>
|
||
|
|
</html>
|