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 domain-dir/applications/j2ee-modulesmodule-name or domain-dir/applications/j2ee-apps/app-name
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 only available for the default server instance.
Dynamic reloading is intended for development environments. It is incompatible with session persistence, a production environment feature. Do not enable session persistence if dynamic reloading is enabled.
In the tree component, expand the Stand-Alone Instances node.
Click server (Admin Server).
On the Applications Configuration page, configure the following:
Reload: Enable or disable dynamic reloading with the Enabled checkbox.
Reload Poll Interval: Specify how often the server checks for changes in the deployed applications.
Admin Session Timeout: Specify the amount of time before the Admin Session times out and you have to log in again.
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.