About this task
If you place EAR files inside this monitored directory,
the EAR file is automatically deployed to the server. If you delete
the EAR file from the monitored directory, that application is uninstalled
from the server. If you place WAR or EJB jar files in the monitored
directory, the rapid deployment tool generates the necessary EAR wrapper
and then publishes that EAR file on the server. For RAR files, a wrapper
is not created; the standalone RAR files are published to the server.
Restrictions
- You can use the rapid deployment
tools for packaging applications at J2EE 1.3 or 1.4 specification-levels.
However, the rapid deployment tools do not support Java EE 5.0 (or later) nor J2EE 1.2 specification-level.
For tools support of deploying Java EE 5 and later modules, you can
use the monitored directory starting in WebSphere Application Server
V8.0 release. For more details about the monitored directory, see Ways to install enterprise applications or modules and Installing enterprise application files by adding them
to a monitored directory topics.
- The rapid deployment tools do not automatically configure server-specific
functions for an application. You need to create and manage the server-specific
configurations through the WebSphere® administrative
console. Examples of server-specific configurations include setting
up ports, security role mappings, or data sources.
- If you did not generate deployment code for the enterprise beans
or enterprise application containing enterprise beans, the rapid deployment
tool generates the deployment code with the default backend option
set to DB2UDB_V82. If you want to set a different backend option,
run the EJB deployment tools (ejbdeploy.bat) on the EAR file before
dropping it into the automatic installation project.
To automate the installation of applications on WebSphere Application Server
v6.0 or later: