Updating Web Modules

A typical iterative development cycle involves deploying a web module and then making changes to the application components. To update a deployed web module, you must do the following:

1. Recompile any modified classes.

2. If you have deployed a packaged web module, update any modified components in the WAR.

3. Redeploy the module.

4. Reload the URL in the client.

Dynamic Reloading

If dynamic reloading is enabled, you do not have to redeploy an application or module when you change its code or deployment descriptors. All you have to do is copy the changed pages or class files into the deployment directory for the application or module. The deployment directory for a web module named context-root is domain-dir/applications/context-root. The server checks for changes periodically and redeploys the application, automatically and dynamically, with the changes.

This capability is useful in a development environment, because it allows code changes to be tested quickly. Dynamic reloading is not recommended for a production environment, however, because it may degrade performance. In addition, whenever a reload is done, the sessions at that time become invalid and the client must restart the session.

To enable dynamic reloading, use the Admin Console:

1. Select the Applications Server node.

2. Select the Advanced tab.

3. Check the Reload Enabled box to enable dynamic reloading.

4. Enter a number of seconds in the Reload Poll Interval field to set the interval at which applications and modules are checked for code changes and dynamically reloaded.

5. Click the Save button.

In addition, to load new servlet files, do the following:

1. Create an empty file named .reload at the root of the module:

   domain-dir/applications/context-root/.reload

2. Explicitly update the .reload file’s time stamp each time you make these changes. On UNIX, execute

   touch .reload