Auto-reload setting of your Web module

The first part of the delay is the auto-reload setting of the Web module. This can be defined using the following methods: Application Server Toolkit (ASTK)

Open the deployment descriptor editor, and then click the IBM Extensions tab. Here one can set whether reload is enabled and how often reloading should occur. Manual editing of non-deployed application

The auto-reload settings (reloadInterval and reloadEnabled) can be changed by manually editing the ibm-web-ext.xmi deployment descriptor file in the WEB-INF directory of the Web module. Manual editing of already deployed application

The auto-reload settings of an already deployed application can be changed by manually editing the ibm-web-ext.xmi deployment descriptor in the WEB-INF directory of the deployed Web module.

As a result of the application dynamic reloading feature provided in WebSphere 5.1, manual changes to the above deployment descriptor will be automatically detected and loaded into the runtime, except for the following cases:

Change reloadEnabled setting (true or false)

Set reloadInterval setting to zero

When reloading is enabled, WebSphere monitors the classpath of the Web application and whenever a component update is detected, all components (JAR or class files) are reloaded.

The longer the reload interval, the longer it will take for the Web module to use the new components. Although new information will appear in the plugin-cfg.xml file, updated Web module components are not used until they have been reloaded.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.