Automatically installing applications on WebSphere Application Server v6.x

The automatic installation configuration creates a single monitored directory that listens for fully composed EAR files or application module such as WAR, EJB JAR files, or standalone resource adapter archive (RAR) files.

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

  • 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.x:

Related concepts
Rapid deployment of J2EE applications

Feedback