WildFly CLI - Taking and Restoring Configuration Snapshots: Difference between revisions
| Line 14: | Line 14: | ||
:[[WildFly_Concepts#Configuration_History|WildFly Configuration History]] | :[[WildFly_Concepts#Configuration_History|WildFly Configuration History]] | ||
</blockquote> | </blockquote> | ||
=Take a Configuration Snapshot= | |||
Before applying a configuration change - or a set of configuration changes - that could destabilize the application server instance, take a configuration snapshot as described below. | |||
Connect to the application server with the CLI. More details on how to connect to the application server instance are available here: [[]]. | |||
Revision as of 03:51, 1 April 2016
Internal
Relevance
EAP 6.4
Overview
This article describes the procedure of taking a standalone instance configuration snapshot, usually performed before a significant CLI-based reconfiguration of the application server and restoring the initial configuration in case of re-configuration failure. This mechanism relies on the fact that the application server maintains a history of its past configurations, and it is capable of taking configuration snapshots. More details about this mechanism are available here:
Take a Configuration Snapshot
Before applying a configuration change - or a set of configuration changes - that could destabilize the application server instance, take a configuration snapshot as described below.
Connect to the application server with the CLI. More details on how to connect to the application server instance are available here: [[]].