Run the ssopre80upgrade script (ssopre80upgrade.bat on Windows) when you are upgrading package based installations; for example, instances of Access Manager installed using Java Enterprise System (JES) 4 or JES 5 will put Access Manager packages on the host machine but a WAR that has been downloaded and deployed will not. ssopre80upgrade prepares the system for upgrade by:
Backing up existing Access Manager or Federation Manager files (such as logs and configuration files).
Removing the Access Manager 7.1 or Access Manager 7 2005Q4 packages (except on Windows systems).
Removing the Federation Manager 7.0 packages.
Removing the SAMLv2 Plug-in package.
Updating the /var/sadm/install/productregistry file to reflect the removal of the Java Enterprise System Access Manager packages.
Entering path names on Windows When you run the ssopre80upgrade.bat script, replace each backslash (\) in path names to a forward slash (/). For example, for C:\sun\opensso\config, you would enter C:/sun/opensso/config.
This procedure assumes you are still logged in to the host machine as super user.
Copy (and rename by adding the .bak extension) the previous version's configuration files (AMConfig.properties and serverconfig.xml) to the /zip-root/opensso/upgrade/config directory.
# cp AMConfig.properties AMConfig.properties.bak # mv AMConfig.properties.bak /zip-root/opensso/upgrade/config/ |
This step is needed for the next procedure, Modifying ssoUpgradeConfig.properties and AMConfig.properties.bak.
If upgrading a Linux-based installation, copy the ssoupgrade file to a new directory (for example /tmp/ssoupgrade). After executing ssopre80upgrade add values for the following attributes in the ssoupgrade file and return the modified script to the /zip-root/opensso/upgrade/scripts directory for execution in Upgrading the Existing Access Manager or Federation Manager Schema.
LIB_DIR=STAGING_DIR: path to the directory created in Creating a Staging Directory and OpenSSO Enterprise 8.0 Upgrade WAR. For example: LIB_DIR=/staging
CONFIG_DIR=OSSO_CONFIG_DIR: path to the configuration directory for the newly upgraded instance. For example: CONFIG_DIR=/amserver
UPGRADE_DIR=OSSO_UPGRADE_DIR: path to the upgrade directory in the exploded opensso.zip. For example: UPGRADE_DIR=/zip-root/opensso/upgrade
Change to the /zip-root/opensso/upgrade/scripts directory.
Run the ssopre80upgrade script.
On Solaris and Linux systems, enter ./ssopre80upgrade. On Windows systems, enter ssopre80upgrade.bat. The script checks whether you are upgrading an instance of Access Manager or Federation Manager.
# check_instance isFM is : false # A log of the ssopreupgrade process can be found in /var/sadm/install/logs/Sun_Java_System_Access_Manager_ upgrade_log.03101744 |
When prompted, accept the default values or provide information based on the deployment.
Directory Server fully qualified host name
Directory Server port
Top-level administrator DN (uid=amAdmin,ou=People,dc=sun,dc=com)
Top-level administrator (uid=amAdmin,ou=People,dc=sun,dc=com) password
Directory to store backup files (/opt/SUNWam)
OpenSSO Enterprise 8.0 configuration directory is the path to the configuration directory for the original instance of Access Manager that you are upgrading. For example: /etc/opt/SUNWam
OpenSSO Enterprise 8.0 upgrade directory is the path to the exploded OpenSSO ZIP. For example: /zip-root/opensso
OpenSSO Enterprise 8.0 staging directory is the path to the directory in which the OpenSSO WAR was exploded. For example: /staging
OPTIONAL: Access Manager installation directory (Windows only)
OPTIONAL: Federation Manager 7.0 staging directory (Federation Manager only)
After the final value is entered, ssopre80upgrade removes the previous version of the server software and its packages.
If upgrading a Linux installation remember to edit ssoupgrade and return it to the /zip-root/opensso/upgrade/scripts directory.