WildFly Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 13: | Line 13: | ||
* [[WildFly System Properties|System Properties]] | * [[WildFly System Properties|System Properties]] | ||
* [[WildFly Paths#Overview|Paths]] | * [[WildFly Paths#Overview|Paths]] | ||
* [[WildFly Profile]] | |||
=Profile= | =Profile= | ||
Revision as of 20:04, 7 July 2017
Internal
Concepts
- Networking
- Deployments
- Security
- Domain Mode
- WildFly and JMX
- Remoting
- System Properties
- Paths
- WildFly Profile
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.