JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle OpenSSO 8.0 Update 2 Release Notes

Document Information

Preface

1.  About OpenSSO 8.0 Update 2

2.  OpenSSO 8.0 Update 2 Patch Releases

3.  Installing OpenSSO 8.0 Update 2

OpenSSO 8.0 Update 2 Installation Overview

OpenSSO 8.0 Update 2 Patches

Planning Your Patch Operation

To Plan Your Patch Operation for OpenSSO 8.0

Overview of the ssopatch Utility

Installing the ssopatch Utility

To Install the ssopatch Utility

Backing Up an OpenSSO WAR File

Running the ssopatch Utility

To run the ssopatch utility, follow this usage:

Comparing an OpenSSO WAR File to Its Internal Manifest

To Compare an OpenSSO WAR File to Its Internal Manifest

Comparing Two OpenSSO WAR Files

To Compare Two OpenSSO WAR Files

Patching an OpenSSO WAR File

To Create a Staging Area to Patch an OpenSSO WAR File

Creating an OpenSSO WAR Manifest File

To Create an OpenSSO WAR Manifest File

Patching a Specialized OpenSSO WAR

To Patch a Specialized OpenSSO WAR

Running the updateschema Script

Before You Begin

To Run the updateschema Script

Backing Out a Patch Installation

4.  Using the Security Token Service

5.  Using the Oracle OpenSSO Fedlet

6.  Integrating the OpenSSO 8.0 Update 2 with Oracle Access Manager

Patching a Specialized OpenSSO WAR

If you have previously created a specialized OpenSSO WAR, such as an OpenSSO server only, administration console only, Distributed Authentication UI server, or IDP Discovery Service WAR, you can patch it by using the ssopatch utility.

To Patch a Specialized OpenSSO WAR

Before You Begin

The existing specialized WAR file and the OpenSSO 8.0 update 2 specialized WAR file should already be created.


Note - In the following example, the directory zip-root is the root directory for the unzipped contents of the currently deployed WAR file. The directory /u2 is the root directory for the unzipped contents of the upgraded version that will be deployed.


  1. Create a manifest file for the existing specialized OpenSSO WAR.
    1. Run ssopatch to create the OpenSSO manifest file.

      Example:

      # cd /u2/opensso/tools/patch
      # ./ssopatch -o zip-root/opensso/deployable-war/distauth.war --manifest 
      /tmp/OpenSSO.manifest

      where opensso.war is an existing OpenSSO WAR file. The ssopatch utility creates a new manifest file named manifest in the /tmp directory.

    2. To allow the WAR file to be patched, copy this new manifest file to the META-INF directory inside the opensso.war file.

      Example:

      # cd zip-root/opensso/deployable-war
      # mkdir META-INF
      # cp /tmp/OpenSSO.manifest META-INF
      # jar uf distauth.war META-INF/OpenSSO.manifest
      # rm -rf /tmp/OpenSSO.manifest
  2. Generate a manifest file for the updated specialized WAR file.

    Example:

    # cd /u2/opensso/tools/patch
    
    # ./ssopatch -o /u2/opensso/deployable-war/distauth.war 
    --manifest /tmp/OpenSSO.manifest 
    cd ../../deployable-war
    
    # mkdir META-INF
    # cp /tmp/OpenSSO.manifest META-INF
    # jar uf distauth.war META-INF/OpenSSO.manifest
    # rm -rf /tmp/OpenSSO.manifest
  3. Use the ssopatch utility to compare your old and new WAR files.

    Example:

    # cd /u2/opensso/tools/patch
    # ./ssopatch -o zip-root/opensso/deployable-war/distauth.war 
    -c /u2/opensso/deployable-war/distauth.war -override
  4. Generate a staging area for the new specialized WAR file.

    Example:

    # cd /tmp/customized_staging
    # jar cvf /patched/distauth.war *
  5. Redeploy the /patched/distauth.war file to the web container using the original deploy URI.

    Example, /distauth.