WebSphere Application Server does not support the modification of deployment descriptor extension parameters through the Administrative Console or through administrative scripting.

To add, change or delete JSP engine configuration parameters, complete the following steps:

1. Open the WEB-INF/ibm-web-ext.xmi file. JSP engine configuration parameters are stored in a web module's configuration directory or in a web modules's binaries directory in the WEB-INF/ibm-web-ext.xmi file. Open the WEB-INF/ibm-web-ext.xmi file from:

   • The configuration directory, as in the following example:

     /QIBM/UserData/WebSphere/AppServer/V6/
     edition/profiles/profileName/
     
     config/cells/cellName/applications/enterpriseAppName/deployments/
     
     deployedName/webModuleName/WEB-INF/ibm-web-ext.xmi 

   • The binaries directory if an application was deployed into WebSphere Application Server with the flag "Use Binary Configuration" set to true. An example of a binaries directory is:

     /QIBM/UserData/WebSphere/AppServer/V6/edition /profiles/profileName/
     
     installedApps/nodeName/
     applicationName.ear/applicationName.war/
     
     WEB-INF/ibm-web-ext.xmi 

2. Edit the WEB-INF/ibm-web-ext.xmi file.

   • To add configuration parameters, use the following format: xmi:id="JSPAttribute_6" name="parametername" value="parametervalue"/>

   • To delete configuration parameters, either delete the line from the file, or enclose the statement with <!-- --> tags.

3. Save the file.

4. Restart the Enterprise Application. It is not necessary to restart the server for parameter changes to take effect. However, some JSP engine configuration parameters affect the Java source code that is generated for a JSP. If such a parameter is changed, then retranslate the JSP files in the Web module to regenerate Java source. You can use the batch compiler to retranslate all JSP files in a Web module. The batch compiler uses the JSP engine configuration parameters that you have set in the ibm-web-ext.xmi file, unless you specifically override them. The topic JSP engine configuration parameters identifies the parameters that affect the generated Java source.

ExampleWEB-INF/ibm-web-ext.xmi

<?xml version="1.0" encoding="UTF-8"?>
<webappext:WebAppExtension xmi:version="2.0" xmlns:xmi=http://www.omg.org/XMI
   xmlns:webappext="webappext.xmi" xmlns:webapplication="webapplication.xmi" xmi:id="WebAppExtension_1"   
   reloadInterval="9" reloadingEnabled="true" defaultErrorPage="error.jsp" additionalClassPath="" 
   fileServingEnabled="true" directoryBrowsingEnabled="false" serveServletsByClassnameEnabled="true" 
   autoRequestEncoding="true" autoResponseEncoding="false"
   <webApp href="WEB-INF/web.xml#WebApp_1"/>
   <jspAttributes xmi:id="JSPAttribute_1" name="useThreadTagPool" value="true"/>
   <jspAttributes xmi:id="JSPAttribute_2" name="verbose" value="false"/>
   <jspAttributes xmi:id="JSPAttribute_3" name="deprecation" value="false"/>
   <jspAttributes xmi:id="JSPAttribute_4" name="reloadEnabled" value="true"/>
   <jspAttributes xmi:id="JSPAttribute_5" name="reloadInterval" value="5"/>
   <jspAttributes xmi:id="JSPAttribute_6" name="keepgenerated" value="true"/>
   <!--<jspAttributes xmi:id="JSPAttribute_7" name="trackDependencies" value="true"/> -->
   <jspAttributes xmi:id="JSPAttribute_8" name="jspCompileClasspath" value=""/>
 
</webappext:WebAppExtension>

Note: The integer n in JSPattribute_n has to be unique within the file.

Sub-topics
JSP engine
JSP engine configuration parameters

Related concepts
JavaServer Pages
Global tag libraries

Related reference
dbmodify tag JavaServer Pages syntax
JSP batch compiler tool
Web applications: