As an IBM enhancement to JavaServer Pages (JSP) support, IBM WebSphere Application Server provides a batch JSP compiler. Use this function to batch compile your JSP files and thereby enable faster responses to the initial client requests for the JSP files on your production Web server.
Batch compiling makes the first request for a JSP file much faster because the JSP file is translated and compiled into a servlet. Batch compiling is also useful as a fast way to resynchronize all of the JSP files for an application.
When you use the JSP batch compiler, you must either add the JAR to the WAR in the <WEB-INF>/lib directory , or add the JAR to the JVM class path to use shared libraries.
To use the JSP batch compiler for JSP files, enter the following command on a single line at an operating system command prompt:
JspBatchCompiler -enterpriseapp.name <name> [ -webmodule.name <name>] [ -cell.name <name>] [ -node.name <name>] [ -server.name <name>] [ -filename <jsp name>] [ -keepgenerated <true|false>] [ -verbose <true|false>] [ -deprecation <true|false>]
If the names specified for these arguments are comprised of two or more words separated by spaces, you must add quotation marks around the names.
where:
Represents the name of the enterprise application you want to compile.
Represents 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.
Represents the name of the cell in which the application is deployed. The default is BaseApplicationServerCell.
Represents the name of the node in which the application is deployed. The default is DefaultNode.
Represents the name of the server in which the application is deployed. The default is server1.
Represents 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.
Represents the option to save or erase the generated files.
If set to yes, WebSphere Application Server saves the generated .java files used for compilation on your server. By default, this argument is set to no and the .java files are erased after the class files have compiled.
Indicates the compiler should generate verbose output while compiling the generated sources.
Indicates the compiler should generate deprecation warnings while compiling the generated sources.