[WAS_8.5_CONCEPTS] Monitored directory deployment

Monitored directory deployment

With monitored directory application deployment, you can automatically deploy and update applications. The applications can be deployed and updated by adding files to a monitored directory in the following ways:

By default, monitored directory application deployment is not enabled. You can use the administrative console or wsadmin scripts to enable or disable it. When monitored directory deployment is enabled, a monitored directory is created automatically based on the installation. By default, this directory is named monitoredDeployableApps:

The polling interval specifies the number of seconds that the monitored directory is scanned for new applications.

Adding enterprise application files

You can install or update an application file by dragging or copying any of the following files to a monitored directory:

The monitored directory is scanned at a time interval based on the polling interval parameter. The status of an application file determines the action that is performed:

Adding enterprise application files by adding properties files

You can install, update, or uninstall an EAR, WAR, JAR, or SIP archive file by dragging or copying an application properties file to a monitoredDeployableApps/deploymentProperties monitored directory.

Properties files can contain all the parameters in wsadmin:

The monitored directory is scanned at a time interval based on the polling interval parameter. If a new properties file is found, the wsadmin.sh applyConfigProperties command runs automatically to install and start the application.