WildFly Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
=Configuration History= | =Configuration History= | ||
The application server maintains past versions of its configuration files. This behavior allows the operator to fall back to a certain configuration version from the past. Each CLI operation increments the configuration version, and a full copy of the previous configuration is stored in <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/current</tt> Upon reboot, the <tt>current</tt> directory is renamed to something similar to <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/20160331-201819598</tt> and the cycle repeats. | The application server maintains past versions of its configuration files. This behavior allows the operator to fall back to a certain configuration version from the past. | ||
Each CLI operation increments the configuration version, and a full copy of the previous configuration is stored in <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/current</tt> Upon reboot, the <tt>current</tt> directory is renamed to something similar to <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/20160331-201819598</tt> and the cycle repeats. | |||
Revision as of 03:36, 1 April 2016
Internal
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 configuration version from the past.
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.