These procedures describe how to enable automatic JSP file reloading
for testing JSP file changes on a remote WebSphere® Portal server. If automatic
JSP file reloading is disabled, the portal server must be restarted every
time a JSP file is changed.
Tip: While this configuration is ideal for development
and testing purposes, you should disable automatic JSP reloading in a production
environment because of performance issues.
Note: Restarting the server
to pick up server configuration changes takes time. It is recommended that
all server configurations be done at the same time, to reduce the number of
server restarts required. Refer to these help topics for other possible server
configuration changes:
Follow these steps to enable automatic JSP reloading:
- On the portal server system, open the file wps_root/config/cells/node/applications/wps.ear/deployments/wps/wps.war/WEB-INF/ibm-web-ext.xmi
where wps_root is the installation directory for WebSphere Portal
and node is the hostname of the portal server system
- Within this file, find the following entry:
webappext:WebAppExtension
xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:webappext="webappext.xmi"
xmlns:webapplication="webapplication.xmi" xmlns:commonext="commonext.xmi"
xmlns:common="common.xmi" xmi:id="IBM_WPS_Ext" reloadInterval="3" reloadingEnabled="false" fileServingEnabled="true"
directoryBrowsingEnabled="false" serveServletsByClassnameEnabled="false" preCompileJSPs="false"
- Change the value for reloadingEnabled to true.
- Save the file.
- Restart the portal server.
After completing these steps, JSP files will automatically reload
when they change.
Note: In the portal test environment, reloadingEnabled is
set to true by default. If you set it to false, portal projects
would be unable to run using the portal test environment. The ibm-web.ext.xmi file
is located in the /PortalContent/WEB-INF folder of each
portal project.