Coexistence of Release 5 with Earlier Directory Data

In some deployment architectures Access Manager is deployed on multiple computer systems to provide for high availability and scalability. The Access Manager instances access the same Directory Server. It is often desirable to upgrade the Access Manager instances sequentially without interrupting service. This section discusses the procedure for performing such rolling upgrades.

Upgrading multiple instances of Access Manager installed on the same host system is not supported in the current release. If you have multiple instances on the same host, after you upgrade the main instance, you must then recreate the additional instances.

The procedure for upgrading Access Manager from Release 4 includes a step for updating directory schema to support Release 5. Release 4 Access Manager does not support Release 5 directory schema, however Release 5 Access Manager does support Release 4 directory schema.

Java ES Release 5 Access Manager and Release 4 Access Manager instances can coexist and run concurrently against the same Directory Server only if the directory schema has not yet been updated to Release 5. Therefore, in rolling upgrades, the directory schema should not be updated to Release 5 until all other steps in the upgrade procedure have first been performed for all Access Manager instances.

That is, in performing rolling upgrades, upgrade each instance of Access Manager as described Upgrading Java ES Release 5 Access Manager from Java ES Release 4, except for the step on updating directory structure and schema. When all instances have been upgraded, then that step can be performed.