If dynamic reloading is enabled, the server periodically checks for changes in a deployed application and automatically reloads the application with the changes. Changes are signaled by a date change to a file called .reload
that you create manually. The applications must be installed in server_root/domain/domain1/applications/
j2ee-module_or_j2ee-apps/app_or_module_name
For example: AppServer/domain/domain1/applications/j2ee-module/webapps-simple
Dynamic reloading is useful in a development environment because it allows code changes to be tested quickly. In a production environment, however, dynamic reloading may degrade performance.
Dynamic reloading is intended for development environments. It is incompatible with session persistence, a production environment feature. Do not enable session persistence if dynamic deployment is enabled.
To configure dynamic reloading:
After configuring the system to use dynamic reloading, for every application to be reloaded dynamically, create a file called .reload and put it in the application’s directory. The file does not have any content. When you change the application, change the date of the file (for example, using the UNIX touch
command), and the changes are reloaded automatically.
See Also: Using Auto Deploy