For example, copy a file named hello.war to the domain-dir/autodeploy directory. To undeploy the application, remove the hello.war file from the autodeploy directory.
You can also use the Admin Console or asadmin tool to undeploy the application. In that case, the archive file remains.
Auto deploy is only available for the default server instance.
The auto deploy feature is intended for development environments. It is incompatible with session persistence, a production environment feature. Do not enable session persistence if auto deployment is enabled
In the tree component, expand the Stand-Alone Instances node.
Click server (Admin Server).
On the Applications Configuration page, configure the following:
Enable or disable auto deploy by selecting or deselecting the Enabled checkbox.
In the Auto Deploy Poll Interval field, specify how often the server checks the auto deploy directory for application or module files.
Changing the poll interval does not affect the amount of time it takes to deploy an application or module.
In the Auto Deploy Directory, if you specify the directory where you build your application, then you won’t have to copy the file to the default auto deploy directory.
The default is a directory called autodeploy in the server instance’s root directory.
By default a variable is used to eliminate the need to manually change the directory for multiple server instances. For more information on these variables, see To set the advanced domain attributes.
To run the verifier before deployment, select the Verifier.
The verifier examines the structure and content of the file. Verification of large applications is often time-consuming.
To precompile JSP pages, select Precompile.
If you do not select this checkbox, the JSP pages are compiled at runtime when they are first accessed. Because compilation is often time-consuming, in a production environment select this checkbox.