Introduction to Upgrading Access Manager

When upgrading Java ES Release 4 Access Manager to Release 5, consider the following aspects of the upgrade process:

• General Upgrade Approach. The upgrade is performed by installing Release 5. Reconfiguration of Access Manager is subsequently performed using the amconfig.bat file, and directory schema is migrated using the amupgrade.bat file.

• Upgrade Dependencies. Access Manager has dependencies on a number of Java ES shared components and other products, as listed in Table 1–7.

  In addition, Release 5 Access Manager is dependent upon Directory Server, Web Server, or Application Server, as described in Access Manager Dependencies. Because these are soft upgrade dependencies, upgrade of these components is optional with respect to upgrade of Access Manager to Release 5.

• Backward Compatibility. Release 5 Access Manager is compatible with Release 4. Access Manager 7.1 will continue to work with Release 4 Access Manager configuration for existing features. New features that access new configuration data required upgrading of Access Manager data. These features include Java ES monitoring and feature improvements in authentication, policy, and delegation.

• Upgrade Rollback. No utility exists for rolling back the Access Manager upgrade. Do not to uninstall Release 4 Access Manager. In order to restore Release 4 Access Manager, you should manually backup the Directory Server data. The best approach to rollback is to create a parallel installation using backed-up configuration files, and testing this parallel installation before performing the upgrade. This process enable you to revert to the parallel installation if necessary.