WildFly CLI - Taking and Restoring Configuration Snapshots: Difference between revisions
| Line 19: | Line 19: | ||
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. | 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: [[]]. | Connect to the application server with the CLI. More details on how to connect to the application server instance are available here: [[WildFly CLI Connect to a Controller|Connect to a Controller]]. | ||
Revision as of 03:52, 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: Connect to a Controller.