WildFly Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
* [[WildFly and JMX]] | * [[WildFly and JMX]] | ||
* [[Remoting WildFly Subsystem Concepts|Remoting]] | * [[Remoting WildFly Subsystem Concepts|Remoting]] | ||
* [[WildFly System Properties|System Properties]] | |||
* [[WildFly Paths#Overview|Paths]] | |||
=Profile= | =Profile= | ||
=Configuration History= | =Configuration History= |
Revision as of 15:01, 21 March 2017
Internal
Concepts
Profile
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.