To Upgrade Access Manager

Before You Begin

• Obtain Access Manager administrator user ID and password, LDAP user ID and password, and Directory Manager name and password for the Directory Server instance that Access Manager is using.

• Before uninstalling all other Java ES components, back up the required data. For more information about backing up other components see the upgrade guides of the respective components.

1. Log in as administrator to the machine where Java ES 4 Access Manager is installed.

2. Manually backup the Access Manager DIT (Directory Server data).

3. Stop the following Java ES 4 services:

   • Web Server

   • Directory Server

   • Directory Proxy Server

   • Application Server

   • Instant Messaging

   • Calender Server

   • Messaging Server

4. Install the Java ES 5 Access Manager.

   For Java ES 5 Access Manager installation instructions, see the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

   ---

   Note –

   Restart the machine after installing Java ES 5 Access Manager.

   ---

5. Re-customize JavaServer Pages for Access Manager.

   1. Re-apply the Release 4 customization to JavaServer Pages for the Access Manager Console and authentication user interface (UI) present in the Release 4 installation location.

   2. Copy the customized JSP files to the correct directories.

      • Console: AccessManager-base\web-src\applications\console

      • Authentication UI:

        AccessManager-base\web-src\services\config\auth\default or AccessManager-base\web-src\services\config\auth\default_locale (where locale is a locale indicator like ja)

      For more information, see the Sun Java System Access Manager Developer’s Guide.

6. Configure Access Manager.

   Configure Access Manager for your specific web container by running the amconfig.bat file. The amconfig.bat file and the associated AMConfigurator.properties input file resides in the AccessManager-base\setup directory.

   For information about the amconfig.bat file and the AMConfigurator.properties file, see the Sun Java System Access Manager Administration Guide.

   Perform the steps to reconfigure and redeploy Access Manager to the web container as described in To Reconfigure and Redeploy Access Manager.

7. Update the directory structure and schema.

   Release 5 Access Manager coexists with the Release 4 directory structure, but the structure must be modified to support Release 5 capabilities. Update the Access Manager directory structure and schema to Release 5 by running the amupgrade.bat file, which is installed in the AccessManager-base\upgradedirectory.

   1. Obtain the values of the following parameters to be requested by the amupgrade.bat:

      Parameter	Value
      Directory Server Host	Set the fully qualified name: hostname.domain.
      Directory Server Port	Specify a non-SSL port number Default: 389.
      Directory Manager DN	Default: cn=Directory Manager.
      Directory Manager Password
      Access Manager Administrator User ID Default: amadmin	Default: amadmin.
      Access Manager Administrator Password
      Enable Realm Mode	Y/N: Yes means Realm Mode is enabled and services data is migrated to new Realm tree. No (default) means services data remain in Legacy Mode.

   2. Run the AccessManager-base\upgrade\amupgrade.bat file.

      If the upgrade is successful, the script displays “Upgrade completed.”

   3. Check the following upgrade log file for information about the directory schema extensions:

      AccessManager-base\setup\AccessManager_upgrade_num.log

8. Enable the components disabled during reconfiguration of Access Manager.

9. Start Access Manager.

   Restart the web container in which Access Manager is deployed.