WAS v8.5 > Administer applications and their environment > Administer the Liberty profile > Administer the Liberty profile manually

Liberty profile dynamic updates

Overview

The default behavior is to dynamically apply updates to...

• Server configuration
• Running application

To change the default behavior, set the config and applicationMonitor elements in server.xml.

Dynamic updates to the server configuration

Changes to server.xml, or any files it includes, are detected by the runtime environment and applied to the active configuration. To disable, set the config element in server.xml:

< config updateTrigger="disabled"/>

Dynamic update of apps

By default, if you...

• Add, remove or modify any files within a deployed application,
• Replace the whole application with an updated version

...the previous version is automatically stopped and the new version is started. This applies to all apps, including those in the dropins directory, and those in locations defined by server.xml.

To disable dynamic update of all apps, edit server.xml and create entry...

< applicationMonitor updateTrigger="disabled"/>

Default settings for application monitoring of dropins directory...

< applicationMonitor updateTrigger="polled" 
                    pollingRate="500ms" 
                    dropins="dropins" 
                    dropinsEnabled="true"/>

...where...

updateTrigger	polled Runtime scans server.xml for changes using timing interval set by monitorInterval mbean Runtime only looks for updates when prompted through MBean call. disabled Updates are not dynamically applied.
pollingRate property values...	- ms (milliseconds)   - s (seconds)   - m (minutes)   - h (hours)
dropins	Name of the "dropins" directory.
dropinsEnabled	Boolean that determines whether the applications in the "dropins" directory are deployed.

Name and location of the "dropins" directory.

By default, the "dropins" directory is...

${server.config.dir}/dropins

To change, use either...

< applicationMonitor dropins="${server.config.dir}/applications" />
< applicationMonitor dropins="applications" />

For location, we can use...

• Any known variable
• A property in bootstrap.properties
• An absolute path
• A path relative to the server directory

Parent topic: Administer the Liberty profile manually

Related

Add an application on the Liberty profile using WebSphere Studio
Deploy applications to the Liberty profile
Liberty profile: Directory locations and properties
Liberty profile: Configuration elements in server.xml