Disable Page Checks Use Custom JSP Tags Precompile JSPs

18 Tuning Web Applications 18-1 18 Tuning Web Applications The following sections contain Oracle best practices for tuning Web applications and managing sessions: ■ Section 18.1, Best Practices ■ Section 18.2, Session Management ■ Section 18.3, Pub-Sub Tuning Guidelines

18.1 Best Practices

■ Section 18.1.1, Disable Page Checks ■ Section 18.1.2, Use Custom JSP Tags ■ Section 18.1.3, Precompile JSPs ■ Section 18.1.4, Disable Access Logging ■ Section 18.1.5, Use HTML Template Compression ■ Section 18.1.6, Use Service Level Agreements ■ Section 18.1.7, Related Reading

18.1.1 Disable Page Checks

You can improve performance by disabling servlet and JDP page checks. Set each of the following parameters to -1: ■ pageCheckSeconds ■ servlet-reload-check-secs ■ servlet Reload Check These are default values for production mode.

18.1.2 Use Custom JSP Tags

Oracle provides three specialized JSP tags that you can use in your JSP pages: cache, repeat, and process. These tags are packaged in a tag library jar file called weblogic-tags.jar . This jar file contains classes for the tags and a tag library descriptor TLD. To use these tags, you copy this jar file to the Web application that contains your JSPs and reference the tag library in your JSP. See Using Custom WebLogic JSP Tags cache, process, repeat in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server. 18-2 Performance and Tuning for Oracle WebLogic Server

18.1.3 Precompile JSPs

You can configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up by setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor. To avoid recompiling your JSPs each time the server restarts and when you target additional servers, precompile them using weblogic.jspc and place them in the WEB-INFclasses folder and archive them in a .war file. Keeping your source files in a separate directory from the archived .war file eliminates the possibility of errors caused by a JSP having a dependency on one of the class files. For a complete explanation on how to avoid JSP recompilation, see Avoiding Unnecessary JSP Compilation at http:www.oracle.comtechnologypubarticlesdev2arch200501j sp_reloaded.html .

18.1.4 Disable Access Logging