restoreConfig command

Use the restoreConfig command to restore the configuration of our 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.

Syntax:

cd profile_root/bin
restoreConfig.sh /path/to/backup_file.zip [options]

Options

-help	Print a usage statement
-location directory_name	Directory where the backup file is restored. The location defaults to app_server_root/config
-logfile file_name	Location of the log file to which trace information is written By default, the log file is named restoreConfig.log and is created in the logs directory.
-nostop	Tell the restoreConfig command not to stop the servers before restoring the configuration
-password password	Password for authentication if security is enabled in the server
-profileName profile	Define the profile of the Application Server process in a multiple-profile installation The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.
-quiet	Suppress the progress information that the restoreConfig command prints in normal mode
-replacelog	Replace the log file instead of appending to the current log
-trace	Generate trace information into the log file for debugging purposes
-username user_name	User name for authentication if security is enabled in the server; acts the same as the -user option
-user user_name	User name for authentication if security is enabled in the server; acts the same as the -username option
-?	Print a usage statement

The following example demonstrates correct syntax:

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:

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

The following example restores the configuration stored in...

/home/mydir/profileBackup.zip

...to the configuration for profile profile:

restoreConfig /home/mydir/profileBackup.zip -profileName profile

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

Notes

If we directly make changes to the application files in...

app_server_root/installedApps

...a process known as "hot deployment", but do not make the same changes to the application files in...

app_server_root/config

...the changes might be overwritten.

For Linux 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.

For AIX if we are using a logical directory for app_server_root/config, the restoreConfig command will not work.