![]() | |
|
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:
Adding enterprise application files
Adding enterprise application files by adding properties files
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
:
For base application servers, the monitored directory is
profile_root/profile_name/monitoredDeployableApps/servers/server_name
.
For deployment managers, several monitored directories are in the deployment manager profile directory:
monitoredDeployableApps/servers/server_name
monitoredDeployableApps/nodes/node_name/servers/server_name
monitoredDeployableApps/clusters/cluster_name
For properties files, the monitored directory is
monitoredDeployableApps/deploymentProperties
.
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:
Enterprise archive (EAR)
Web archive (WAR)
Java archive (JAR)
Session Initiation Protocol (SIP) archive module
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:
Installation
If an application file is added to the monitored directory, the application is installed and started.
Update
If an existing application file is updated in the monitored directory, the application is stopped, the update is installed, and then the updated application is started.
Uninstallation
If an application file is removed from the monitored directory, the application is stopped and uninstalled.
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
:
Application deployment actions:
Install
Update
Edit
Uninstall
Application installation options
Application installation bindings and extensions
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.
![]() ![]() ![]() |