WAS v8.5 > Reference > SetsGlobal deployment settings page
Use this page to manage settings that apply to all applications or to a subset of application types.
We can also use this page to change settings for monitored directory deployment.
Restriction: Monitored directory deployment is available only on distributed or z/OS operating systems. It is not supported on IBM i operating systems.
To view this dmgr console page, click Applications > Global deployment settings.
Monitor directory to automatically deploy applications
Whether to enable monitored directory deployment.
We can use monitored directory deployment to install or update an enterprise application file on an application server, or to uninstall an application file that was previously installed using monitored directory deployment.
We can install or update an application file by dragging or copying an EAR, web archive (WAR), JAR, or Session Initiation Protocol (SIP) archive (SAR) to a monitored directory. The application file must conform to the Java EE specification. To uninstall a deployed application file, remove it from the monitored directory.
We can also install, update, or uninstall an application file by dragging or copying an application properties file to a monitored directory. The properties file must specify the deployment actions to be performed.
By default, monitored directory deployment is disabled.
Information Value Data type Boolean Default false (clear checkbox)
Monitored directory
Directory to use for monitored directory deployment. The default monitored directory is monitoredDeployableApps. Using this setting, we can specify a different default monitored directory.
For deployment by dragging or copying an enterprise application file to a monitored directory, the directory to which you add enterprise application files depends upon the product profile:
- For base (stand-alone) application servers, the default monitored directory is the monitoredDeployableApps/servers/server_name directory of the application server profile.
For deployment using properties files, the monitored directory is a subdirectory, named deploymentProperties, of the directory specified by this setting; for example, monitoredDeployableApps/deploymentProperties.
To change the default monitored directory, specify a different directory path for this setting. List the entire value for the directory, including the environment variable. Select the Monitor directory to automatically deploy applications option to change this setting.
To view the default value, after a non-default value is set, clear the field.
Information Value Data type String Default ${USER_INSTALL_ROOT}/monitoredDeployableApps
Polling interval
Number of seconds that elapse before the product scans a monitored directory for new applications.
WAS v8.5 scans a monitored directory for new applications no more frequently than every 5 seconds, by default.
To change this setting, specify a value of 5 or higher. WAS v8.5 changes 0 (zero) or negative values to 5 when the server starts. Monitor directory to automatically deploy applications must be enabled to change this setting.
To view the default value, after a non-default value is set, clear the field.
Information Value Data type Integer Default 5
Related concepts:
Ways to install enterprise applications or modules
Related
Set monitored directory deployment values
Install enterprise application files by adding them to a monitored directory
Install enterprise application files by adding properties files to a monitored directory