ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamy_5.4.0.1/50/program/jspbatch.htm

84 lines
3.9 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!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>JSP batch compiler</title>
</head>
<BODY>
<!-- Java sync-link -->
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
<h4><a name="jspbatch"></a>JSP batch compiler</h4>
<p>WebSphere Application Server - Express allows you to compile JavaServer Pages files written to the JSP specification as a batch. This improves performance by reducing the response time on the first request. For iSeries, another option to consider is to use the Pre-touch tool which can compile and load JSP class files into the Application server JVM for improved performance over the JSP batch compiler.</p>
<p>To use the batch compiler for JSP files, follow these steps:</p>
<ol>
<li>On an iSeries command line, run the Start Qshell (STRQSH) command.</li>
<li>The Qshell command prompt <strong><tt>$</tt></strong> appears.</li>
<li>To change your directory, enter <pre>cd /QIBM/ProdData/WebASE/ASE5/bin</pre></li>
<li>Run the JspBatchCompiler command.</li>
</ol>
<p>The syntax of the JspBatchCompiler command:</p>
<pre> JspBatchCompiler -enterpriseapp.name <em>name</em>
[ -instance <em>name</em> ]
[ -webmodule.name <em>name</em> ]
[ -cell.name <em>name</em> ]
[ -node.name <em>name</em> ]
[ -server.name <em>name</em> ]
[ -filename <em>jsp name</em> ]
[ -keepgenerated &lt;true|false&gt; ]
[ -verbose &lt;true|false&gt; ]
[ -deprecation &lt;true|false&gt; ]</pre>
<p>where the parameters are:</p>
<ul>
<li><p><strong>enterpriseapp.name</strong>
<br>The name of the Enterprise Application you want to compile.</p></li>
<li><p><strong>instance</strong>
<br>The name of the WebSphere instance. This parameter is required.</p></li>
<li><p><strong>webmodule.name</strong>
<br>The name of the specific Web module that you want to compile. If this argument is not set, all Web modules in the enterprise application are compiled.</p></li>
<li><p><strong>cell.name</strong>
<br>The name of the cell in which the application is deployed.</p></li>
<li><p><strong>node.name</strong>
<br>The name of the node in which the application is deployed.</p></li>
<li><p><strong>server.name</strong>
<br>The name of the server in which the application is deployed. The default is server1.</p></li>
<li><p><strong>filename</strong>
<br>The name of a single JSP file that you want to compile. If this argument is not set, all files in the Web module are compiled. Alternatively, if filename is set to the name of a directory, only the JSP files in that directory are compiled.</p></li>
<li><p><strong>keepgenerated</strong>
<br>If set to <tt>true</tt>, WebSphere Application Server - Express saves the generated .java files used for compilation on your server. By default, this is set to <tt>false</tt> and the .java files are erased after the class files have been compiled.</p></li>
<li><p><strong>verbose</strong>
<br>Indicates the compiler should generate verbose output while compiling the generated sources.</p></li>
<li><p><strong>deprecated</strong>
<br>Indicates the compiler should generate deprecation warnings while compiling the generated sources.</p></li>
</ul>
<p><strong>Note:</strong> If the names that are specified for these arguments are composed of two or more words separated by spaces, you must add quotation marks (&quot;) around the names.</p>
<p>Following compilation, compiled .class files for the JSPs in the examples Web module are found within the temp subdirectory of the instance. For example, /QIBM/UserData/WebASE/ASE5/<em>instance</em>/temp where <em>instance</em> is the name of your WebSphere instance.</p>
</body>
</html>