Creating a Staging Directory and OpenSSO Enterprise 8.0 Upgrade WAR

After unzipping opensso_enterprise_80.zip, you will find opensso.war in /zip-root/opensso/deployable-war. Now create a staging directory into which opensso.war can be exploded. If you customized any files in your previous Access Manager or Federation Manager deployment, you will need to apply these customizations to the files in the staging directory.

Even if you have not customized your previous deployment, you must create a staging directory as the path to this directory is used for input when running the upgrade scripts.

To Create a Staging Directory and OpenSSO Enterprise 8.0 WAR

Before You Begin

This procedure assumes you are still logged in to the host machine as super user.

1. Create a staging directory for the new WAR.

   ---

   Caution –

   Do not create the staging directory in the tmp directory.

   ---

   # mkdir /staging

2. Extract the files from opensso.war into the staging directory.

   # cd /staging # jar xvf /zip-root/opensso/deployable-war/opensso.war

3. (Optional) Add any customized files from your previous Access Manager or Federation Manager deployment to the OpenSSO Enterprise WAR staging directory.

   For example, copy any modified JSP files for the Administration Console to the staging directory.

   ---

   Note –

   Be sure to remove the file you are replacing.

   ---

4. Create a new WAR from the files in the staging directory.

   The name of the new WAR must use the same deployment URI as the previously installed Access Manager or Federation Manager instance. For example, if the previous instance is deployed with the /amserver URI, the new WAR must be named amserver.war.

   # jar cvf /zip-root/opensso/deployable-war/amserver.war *