If you are not sure what a profile is, refer to this article.

There are a number of options can be be used with the manageprofiles.sh (Linux) or manageprofiles.bat (Windows) script.

• Backup a profile (-backupProfile)
• Create a new profile (-create)
• Delete a profile (-delete)
• Determine if a profile is valid in the registry (-validateRegistry)
• Determine if a profile is valid in the registry and updae (-validateAndUpdateRegistry)
• List profiles (-listProfiles)
• List default profile (-getDefaultName)
• List profile path (-getPath)
• Restore a profile (-restoreProfile) (this article)

The manageprofiles.sh (Linux) or manageprofiles.bat (Windows) command can be used to restore a profile that was backed up using the manageprofiles command with the -backupProfile flag. Let's say the following command was issued to create a backup of the profile named AppSrv02.

manageprofiles.sh -backupProfile -profileName AppSrv02 -backupFile /path/to/AppSrv02.xml

AVOID TROUBLE

If you will be restoring the profile on the same system that the profile exists on, and the profile directory still exists, you will need to remove the profile directory before the profile can be restored.

rm -rf ${WAS_INSTALL_ROOT}/profiles/AppSrv02

The following command is used to restore a profile.

manageprofiles.sh -restoreProfile -backupFile /path/to/backup/file

If the restoration of the profile is successful, something like this should be returned.

INSTCONFSUCCESS: Success: The profile was successfully restored.

The -listProfiles option can then be used to list the profiles on the system. In this example, there are two profiles, AppSrv01 and AppSrv02, which is the profile that was restored.

~]# ${WAS_INSTALL_ROOT}/bin/manageprofiles.sh -listProfiles
[AppSrv01, AppSrv02]

And it's always a good idea to validate the registry.

~]# ${WAS_INSTALL_ROOT}/bin/manageprofiles.sh -validateRegistry
All of the profiles in the registry are valid.