Recovering from profile update errors

Review this topic if you encounter profile update errors while upgrading from IBM® Business Process Manager V8.0.1 to IBM Business Process Manager V8.0.1.x.

Identifying profile update errors

If the error message "The packages are updated with warnings" is displayed on the Installation Manager summary panel (GUI installation) or on the command line (silent installation), check the <install_root>/logs/bpm/update/installconfig_<product_ID>_profileMaintenance.log file, where <product_ID> is the product identifier, for example, Adv.server. If it contains the message Result of executing [...]BPMProfileMaintenance.ant was: false, a profile update error has occurred.

If multiple profiles in the installation are being updated, search for the first occurrence of profileName= before the error to know with which profile this error is associated. Fix the cause and then follow the appropriate steps for that profile type.

When you upgrade an installation on the Windows XP operating system, you must check the installconfig_<product_ID>_profileMaintenance.log file, even if the Installation Manager reported that the packages are updated.

Tip: For network deployment environments, the most likely cause of an error is that a connection to the deployment manager cannot be established.

Stand-alone profiles and deployment manager profiles

To recover from a stand-alone or deployment manager profile update error, complete the following steps.

Make sure the stand-alone application server or the deployment manager is stopped.
Change directories to <install_root> where the profile update error has occurred and run one of the following commands as appropriate for your platform:
- bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
- bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
Where <profile_name> is the name of the stand-alone profile or deployment manager profile that had update errors.

Federated profiles

To recover from a federated profile update error, complete the following steps.

Make sure that the deployment manager has been started. This step is necessary because the BPMProfileUpgrade.ant script must connect to the central configuration repository on the deployment manager to make the updates.
Change directories to <install_root> where the profile update error has occurred, and run one of the following commands as appropriate for your platform:
- bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
- bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
where <profile_name> is the name of the federated profile that had update errors.
If you are updating a federated node when WebSphere administrative security is enabled, you must also supply the -Duser=<userID> -Dpassword=<password> parameters, where <userID> is a user ID from the user registry that has administration authority and <password> is the password for that user ID.

Clusters

Follow the steps in the topic "Upgrading clusters" for any cluster that had upgrade errors.

Rolling back the upgrade

You can use the IBM Installation Manager for WebSphere Software to roll back this upgrade.

If you roll back the upgrade, the IBM Installation Manager does not roll back upgrades from profiles because you might have configured the profile after installing the upgrade.

Attention: Profiles might not be usable after rolling back the upgrade.

To restore an original profile, use the restoreConfig command to restore your backup.

Before running the restoreConfig command, export any custom enterprise applications that you have installed since you ran the backupConfig command. After you run the restoreConfig command, reinstall the exported enterprise applications and redo any other applicable configuration changes that you made since you ran the backupConfig command.