During the development of a Web application, execute the JSP pre-compilation functionality after the completion of the Web application.

Use the cjjspc command for implementing the JSP pre-compilation. The following figure shows an example of application of JSP pre-compilation during development of a Web application:

Figure 2-5 Example of applying the JSP pre-compilation functionality when developing a Web application

Use the JSP pre-compilation functionality to compile all the JSP files included in a completed Web application at the same time. As a result, you can improve the response time of JSP initial request during execution of a Web application.

To compile all the JSP files in a Web application collectively, implement the 'Pre-compilation in each Web application method of the cjjspc command.

For the cjjspc command, see cjjspc (JSP pre-compilation) in the uCosminexus Application Server Command Reference Guide.

To improve the response time of the JSP initial request during system operation, implement the JSP pre-compilation before starting the operation. Implement the JSP pre-compilation during system operation when starting a J2EE application and when switching the J2EE applications. The following figure shows an example of application of JSP pre-compilation during system operation:

Figure 2-6 Applying the JSP pre-compilation functionality during system operations

The overview of each stage applicable to the JSP pre-compilation functionality is explained below. For details on the compilation methods using the JSP pre-compilation functionality during system operations, see 5.6.3 Substituting and maintaining J2EE applications in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

(a) When J2EE applications are started

When a J2EE application is started, you can use the JSP pre-compilation for an already imported J2EE application. Execute the JSP pre-compilation functionality to be implemented when a J2EE application is started by specifying the option for implementing the JSP pre-compilation in the cjstartapp command. If you execute this command, the JSP files included in the J2EE application are complied together before starting the J2EE application.

(b) When J2EE applications are switched

You can use the JSP pre-compilation functionality before switching the J2EE applications. Note that the method of JSP pre-compilation depends upon how the J2EE applications are switched.

• In the case of normal switching between J2EE applications
  Normal switching between J2EE applications refers to a method in which the J2EE application is stopped once and then switched to a new application.
  In the case of normal switching between J2EE applications, execute the JSP pre-compilation by specifying the option for implementing the JSP pre-compilation in the cjstartapp command, after importing the switched J2EE application. If this command is executed, the JSP files included in the J2EE application are compiled collectively before the switched J2EE application is started.
  
• In the case of switching the J2EE applications by reloading
  Switching the J2EE applications by reloading refers to a method in which a J2EE application is switched to a new J2EE application (an application in expanded format) without stopping.
  In the case you use the reload functionality to operate a J2EE application containing the JSP compilation results, and if the JSP files are modified, you can compile the modified JSP files by the cjjspc command.
  
• In the case of switching the J2EE applications by redeploying
  Switching the J2EE application by redeploying refers to a method in which a J2EE application is switched to a new J2EE application (an application in archive format) without stopping.
  The order to switch the J2EE applications by redeploying is as follows:
  
  1. Implement the JSP pre-compilation with the cjjspc command and compile all the JSP files included in the J2EE application collectively.
  2. Create an EAR file containing the JSP compilation results generated in 1.
  3. Redeploy the EAR file created in 2.

For an overview of switching J2EE applications, see 5.6.3 Substituting and maintaining J2EE applications in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide. For reloading, see 13.8 Detecting updates and reloading J2EE applications in the uCosminexus Application Server Common Container Functionality Guide.