The restoreConfig script
The restoreConfig script restores the configuration of a node. To run this script, have a backup copy of the configuration. By default, all servers on the node stop before the configuration restores so that a node syncronization does not occur during the restoration. If the configuration directory already exists, the script renames it before restoring the configuration.
Note: The restoreConfig script only restores information for a single instance of WebSphere Application Server. For a more complete restoration of your configuration, it is recommended that you follow the procedures described in Save and restore considerations for WebSphere Application Server.
Product
The restoreConfig script is available in WebSphere Application Server and WebSphere Application Server Network Deployment.
Authority
To run this script, your user profile must have *ALLOBJ authority.
Syntax
The syntax of the restoreConfig script is:
restoreConfig backup_file [ -instance instance ] [ -nostop ] [ -quiet ] [ -logfile filename ] [ -replacelog ] [ -trace ] [ -username username ] [ -password password ] [ -help | -? ]Parameters
The parameters of the restoreConfig script are:
backup_file
This is a required parameter. The value backup_file specifies the fully qualified name of the backup configuration that you want to restore.-instance
Optional. The value instance specifies the name of the instance to which you want to restore the configuration. The default value is default.-nostop
Optional. If you specify this parameter, the restoreConfig script does not to stop the servers before it restores the configuration. By default, the script stops the servers before it restores the configuration.-quiet
Optional. If you specify this parameter, the script does not display informational messages. The default is to display informational messages while the script runs.-logfile
Optional. The value filename specifies the location and name of the log file for the script. The default value is /QIBM/UserData/WebAS5/edition/instance/logs/restoreConfig.log, where edition is Base or ND depending on which product you are running and instance is the name of the instance for which you want to restore the configuration.-replacelog
Optional. If you specify this parameter, the script replaces the log file if it exists. By default the script appends to the log file if it exists.-trace
Optional. If you specify this parameter, the script outputs additional trace information to the log file for the script. You should only specify this parameter if errors occur when you try to restore a configuration. The default is to not log additional trace information.-username
This parameter is required if security is enabled for the server. The value username specifies the user name for authentication. The script uses this parameter to stop the servers. If you specify the -nostop parameter, you do not need to specify the -username parameter.-password
This parameter is required if security is enabled for the server. The value password specifies the password for authentication. The script uses this parameter to stop the servers. If you specify the -nostop parameter, you do not need to specify the -password parameter.-help or -?
This optional paramter prints the usage statement for the script.
Examples
These examples demonstrate correct syntax:
restoreConfig /QIBM/UserData/WebAS5/Base/default/myConfig.zipThis example restores the configuration for the default instance. The script uses the configuration file called myConfig.zip in the /QIBM/UserData/WebAS5/Base/default directory.
backupConfig /QIBM/UserData/WebAS5/Base/devinst/devConfig.zip -instance devinstThis example restores the configuration for the devinst instance. The script uses the configuration file called devConfig.zip in the /QIBM/UserData/WebAS5/Base/devinst directory.