OpenSSO Enterprise 8.0 Preliminary Upgrade Steps

Perform the procedures in the following sections before upgrading Access Manager or Federation Manager to OpenSSO Enterprise 8.0.

• Upgrading Related Components

• Backing Up Existing Access Manager or Federation Manager Files

• Setting Your JAVA_HOME and PATH Environment Variables

Upgrading Related Components

The components on the host machine of the previous release's installation must also be supported by Open SSO Enterprise 8.0. If necessary, upgrade the following components, in this order:

• Operating system

• Sun Java System Directory Server

• Access Manager web container

• JDK (must be 1.5 or later)

For a list of the supported versions of these components, see Hardware and Software Requirements For OpenSSO Enterprise 8.0 in Sun OpenSSO Enterprise 8.0 Release Notes.

If upgrading multiple instances of Access Manager or Federation Manager, upgrade these components on all host machines.

Backing Up Existing Access Manager or Federation Manager Files

Before upgrading Access Manager 7.1, Access Manager 7 2005Q4, or Federation Manager 7.0, back up the files as described in the following sections.

• To Back Up the Access Manager or Federation Manager Schema

• To Back Up the Access Manager or Federation Manager Configuration Data

• To Back Up Customized Files

• To Back Up the Federation Manager 7.0 Staging Directory

• To Modify Policy Definitions

If upgrading multiple instances of Access Manager or Federation Manager, backup these files for all instances.

To Back Up the Access Manager or Federation Manager Schema

Back up the Access Manager or Federation Manager schema (and any corresponding attribute values) that was loaded to Sun Java System Directory Server during installation. Export the data to an LDIF file using the appropriate Directory Server command.

• If backing up Directory Server 6.x, use the dsadm export command. For more information, see the dsadm(1M) man page.

• If backing up Directory Server 5.x, use the db2ldif command. For more information, see the db2ldif(1M) man page.

You will need to know the base suffix of the service management node (also referred to as the information tree) as defined in the amsamplesilent file. For information on the suffix of this node, see Configuring Different Root Suffixes for the Access Manager Information Tree and User Directory Nodes in Sun Java System Access Manager 7.1 Postinstallation Guide.

Because OpenSSO Enterprise does not require the iPlanetAMProviderConfigService and iPlanetAMAuthenticationDomainConfigService, the upgrade process removes these services from the schema. If you do not back up the schema, retrieval of these services is not possible after the upgrade is finished.

To Back Up the Access Manager or Federation Manager Configuration Data

Back up the Access Manager or Federation Manager configuration data stored in the AMConfig.properties and severconfig.xml files. The location of the files is based on your platform.

• Solaris systems: /etc/opt/SUNWam/config

• Linux systems: /etc/opt/sun/identity/config

• Windows systems (for Access Manager 7.1 only): C:\Program Files\Sun\JavaES5\identity\config

To Back Up Customized Files

Back up any files that might have been customized for your Access Manager or Federation Manager deployment, including:

• JSP files customized for the Access Manager console

• JAR files for authentication and customized modules in the AccessManager-base/lib directory, where AccessManager-base represents the base installation directory based on your platform.

  • Solaris systems: /opt/SUNWam

  • Linux systems: /opt/sun/identity

  • Windows systems (for Access Manager 7.1 only): C:\Program Files\Sun\JavaES5\identity

To Back Up the Federation Manager 7.0 Staging Directory

If you are upgrading Federation Manager 7.0, back up the Federation Manager staging directory. For information about the staging directory see the Sun Java System Federation Manager 7.0 User’s Guide.

To Modify Policy Definitions

Modify any policy definitions that meet the criteria as documented in Modifying Policy Definitions. This can be done before or after the upgrade.

Setting Your JAVA_HOME and PATH Environment Variables

The upgrade scripts and jar command require JDK 1.5 or later. Therefore, set your JAVA_HOME environment variable to point to an installed JDK version 1.5 or later. Additionally, set your PATH environment variable. For example, run the following commands if using Solaris.

JAVA_HOME=/usr/java/j2sdk1.5.0
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH;
export PATH

Confirm the changes made by running which java at the command line. Run java -version to confirm the version number.