InfoCenter Home >
4: Developing applications >
4.2: Building Web applications >
4.2.2: Developing JSP files >
4.2.2.2: JSP support and environment in WebSphere >
4.2.2.2.4: Batch Compiling JSP files >
4.2.2.2.4.2: Compiling JSP 1.1 files as a batch
4.2.2.2.4.2: Compiling JSP 1.1 files as a batch
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>-webModule<name>[-filename<jsp name>]
[-keepgenerated<true|false>][-configFile<configfile name>]
Note:
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:
- enterpriseApp
The name of the Enterprise Application you want to compile.
- webModule
The name of the specific Web module that you want to compile.
- filename
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.
- keepgenerated
If set to "yes" WebSphere Application Server will save the generated .java
files used for compilation on your server. By default, this is set to
"no" and the .java files are erased after the class files
have been compiled.
- configFile
The configFile parameter is valid only on Advanced Single Server Edition
for "Multiplatforms." Use it to specify an alternative sever
configuration file (the default is server-cfg.xml).
In a server group environment, the repository is shared with multiple instances of a WAR. This means that all the files can exist on one machine (single node - vertical cloning) or on many machines (multiple nodes - horizontal cloning). The JSPBatchCompiler tool uses the nodeName option to retrieve configuration information for that node. If the nodeName is a remote machine, the JSPBatchCompiler tool outputs the compiled classes to the localNode, not the remoteNode. An example of the path is /temp/remoteNodename/. The customer can then copy the compiled content to the remoteNode.
|
|