You can place J2EE compliant applications (EAR files) or application
modules such as WAR files, EJB JAR files, or standalone RAR files in an automatic
application installation project and let rapid deployment tools deploy that
application on to a target server.
The following actions are supported when using the automatic installation
projects:
Dropping EAR files
You can place EAR files in the
automatic application installation project. The EAR file is automatically
deployed to the server by expanding into the installedApps folder of the local WebSphere
® Application
Server.
Restriction: If you did not generate deployment
code for the enterprise beans contained in the enterprise application, the
rapid deployment tool generates the deployment code with the default backend
option set to DB2UDB_V72 during the installation of your application on the
server. 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.
Deleting EAR files
When
you delete EAR files from the automatic installation project, the application
is uninstalled from the server.
Modifying EAR files
You
can place a modified version of the same EAR file in the automatic installation
project and the application is reinstalled.
Dropping module files
You
can place WAR or EJB jar files in the automatic installation project. A supporting
EAR wrapper is generated in the
gen subdirectory, and
then that EAR file is deployed to the server by expanding into the
installedApps folder
of the local WebSphere Application Server. For RAR files, a wrapper
is not created. The standalone RAR files are published to the server.
Restriction: If you did not generate deployment code for the enterprise
beans, the rapid deployment tool will generate the deployment code with the
default EJBDeploy settings, for example, backend option set to DB2UDB_V72.
If you want to set a different backend option, run the EJB deployment tools
(ejbdeploy.bat) on the EAR file prior to dropping it into the automatic installation
project.
Deleting module files
When you delete module
files from the automatic application installation project, the application
is uninstalled from the server. In addition, any supporting EAR wrapper that
was generated in the gen subdirectory is removed.
Modifying
module files
You can place a modified version of the same module
file in an automatic application installation project, then the application
is reinstalled. In addition, any supporting EAR wrapper that was generated
in the gen subdirectory is modified.