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. You can run this command from the install_root/bin directory of a WebSphere Application Server installation or a Network Deployment installation. WebSphere Application Server
In a UNIX or Linux environment, 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 backup and restore the configuration.
For AIX only, if you are using a logical directory for was_install/config, the restoreConfig will not work.
If you make changes to the application files in the was_install/installedApps directory but do not make the same changes to the application files in the was_install/config directory, the changes may be overwritten if you use the restoreConfig command. This is known as hot deployment.
Syntax
The command syntax is as follows:
restoreConfig <backup_file> [options]where backup_file specifies the file to be restored. If you do not specify one, the command will not run.
Parameters
The following options are available for the restoreConfig command:
Usage scenario
The following example demonstrates correct syntax:
restoreConfig WebSphereConfig_2003-04-22.zipThe following example restores the given file to the /tmp directory and does not stop any servers before beginning the restoration:
restoreConfig WebSphereConfig_2003-04-22.zip -location /tmp -nostop