WildFly Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=Deployments= | =Deployments= | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly Deployment Concepts]] | |||
</blockquote> | |||
=Deployment Artifact Repository= | =Deployment Artifact Repository= | ||
Revision as of 19:03, 12 October 2016
Internal
Profile
Deployments
Deployment Artifact Repository
Also see WildFly CLI Deployment/Undeployment.
Paths
Configuration History
The application server maintains past versions of its configuration files. This behavior allows the operator to fall back to a certain previous configuration.
Each CLI operation increments the configuration version, and a full copy of the previous configuration is stored in $JBOSS_HOME/standalone/configuration/standalone_xml_history/current Upon reboot, the current directory is renamed to something similar to $JBOSS_HOME/standalone/configuration/standalone_xml_history/20160331-201819598 and the cycle repeats. Also see Taking and Restoring Configuration Snapshots.