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.
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.
The backupConfig command
does not save file permissions or ownership information. The restoreConfig command
uses the current umask and effective user ID (EUID) to set the permissions
and ownership when restoring a file. If it is required that the restored
files have the original permissions and ownership, use the tar command
(available on all UNIX or Linux systems) to back up and restore the configuration.
If you are using a logical directory for app_server_root/config, the restoreConfig command will not work.
restoreConfig <backup_file> [options]where backup_file specifies the file to be restored. If you do not specify one, the command will not run.
The following options are available for the restoreConfig command:
The following example demonstrates correct syntax:
restoreConfig 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:
restoreConfig 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 may need to manually update some of the paths in the configuration directory.