restoreConfig command

Use the restoreConfig command to restore the configuration of your node after backing up the configuration using the backupConfig command.

The restoreConfig command is a simple utility to restore the configuration of your node after backing up the configuration using the backupConfig command. By default, all servers on the node stop before the configuration restores so that a node synchronization does not occur during the restoration. If the configuration directory already exists, it is renamed before the restoration occurs. For more information about where to run this command, see the “Using command line” tools article in the information center.

If you directly make changes to the application files in the app_server_root/installedApps directory, a process known as “hot deployment”, but do not make the same changes to the application files in the app_server_root/config directory, the changes might be overwritten if you use the restoreConfig command.

Usage

The following example demonstrates correct syntax:

Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view.

restoreConfig.sh WebSphereConfig_2006-04-22.zip

Image may be NSFW.
Clik here to view.

restoreConfig.bat WebSphereConfig_2006-04-22.zip

Image may be NSFW.
Clik here to view.

restoreConfig.sh WebSphereConfig_2006-04-22.zip

The following example restores the given file to the /tmp directory and does not stop any servers before beginning the restoration:

Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view. Image may be NSFW.
Clik here to view.

restoreConfig.sh WebSphereConfig_2006-04-22.zip -location /tmp -nostop

Image may be NSFW.
Clik here to view.

restoreConfig.bat WebSphereConfig_2006-04-22.zip -location /tmp -nostop

Image may be NSFW.
Clik here to view.

restoreConfig.sh WebSphereConfig_2006-04-22.zip -location /tmp -nostop

Be aware that if you restore the configuration to a directory that is different from the directory that was backed up when you performed the backupConfig command, you might need to manually update some of the paths in the configuration directory.

Source: IBM

Image may be NSFW.
Clik here to view.