Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows

Pre-Upgrade Tasks

Before you upgrade Access Manager, perform the procedures described in the following sections:

Upgrading Access Manager Dependencies

All Java ES components on a computer system and in a computing environment should be upgraded to Java ES Release 5. Access Manager has hard upgrade dependencies on only a couple of shared components.

If you choose to upgrade Access Manager product component dependencies, you should do so in the order below,skipping any components that might already have been upgraded, before you upgrade Access Manager. Upgrade of shared components is normally achieved automatically by the Java ES installer.

  1. Shared Components. All shared components required by Access Manager are upgraded automatically by the Java ES installer when you perform an upgrade of Access Manager to Release 5.

  2. Directory Server (optional). Instructions for upgrading Directory Server to Release 5 are provided in Chapter 2, Directory Server.

    Make sure that the Release 5 Directory Server uses the same port as of Release 4 Directory Server.

  3. Web Container Software (optional). Instructions for upgrading Web Server or Application Server are provided in Chapter 4, Web Server and Chapter 6, Application Server respectively.

    If web container software is not upgraded before Access Manager, the upgrade procedure will configure and redeploy Access Manager to the existing web container.

    Make sure that the Release 5 web container uses the same port as of Release 4 web container.

Backing Up Directory Server Data

The Access Manager upgrade process uses scripts that modify Directory Server schema. Therefore, before you upgrade Access Manager, back up your Directory Server data using the Directory Server Console or a command-line utility such as db2bak.

For more information about backing up Directory Server, see the Sun Java System Directory Server Administration Guide.

Back Up Release 4 Access Manager Configuration Information

Because the reconfiguration of Release 5 Access Manager software requires the reconfiguration of the Release 4 version, you should back up configuration files to a known location. The following Web container configuration files should be backed up:

ProcedureTo Verify Current Version Information

    Type the following command.

    AccessManager-base\bin\amadmin --version

    The outputs that indicate the Access Manager version are:

    Release 5

    Access Manager 7.1

    Release 4

    Access Manager 7 2005Q4