2. OpenSSO 8.0 Update 2 Patch Releases
3. Installing OpenSSO 8.0 Update 2
OpenSSO 8.0 Update 2 Installation Overview
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
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
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
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
Use this procedure to create a new staging area, where an original WAR file is merged with a new WAR file.
This operation compares the manifests for each WAR file and then shows:
Files customized in the original WAR file
Files updated in a new WAR file
Files added or removed between the two WAR file versions
The ssopatch then copies the appropriate files to a staging directory, where you must add any customizations before you create and deploy the new patched WAR.
Although the ssopatch does not modify your original opensso.war file, it is recommended that you back up this file, in case you need to back out the patched opensso.war file.
Run ssopatch to create the staging area. For example:
./ssopatch -o /zip-root/opensso/deployable-war/opensso.war -c /u1/opensso/deployable-war/opensso.war --override -s /tmp/staging Generating Manifest for: /zip-root/opensso/deployable-war/opensso.war Original manifest: Enterprise 8.0 Build 6(200810311055) New manifest: Enterprise 8.0 Update 2 Build 6.1(200904300525) Versions are compatible Generating Manifest for: /u1/opensso/deployable-war/opensso.war Comparing manifest of /zip-root/opensso/deployable-war/opensso.war (generated-200905051031) against /u1/opensso/deployable-war/opensso.war (generated-200905051032) File was customized in original, but not found in new war. Staging area using original war version (samples/saml2/sae/header.jsp) File was customized in original, but not found in new war. Staging area using original war version (WEB-INF/template/opends/config/upgrade/config.ldif.4517) File was customized in original, but not found in new war. Staging area using original war version (WEB-INF/template/opends/config/upgrade/schema.ldif.4517) Differences: 1813 Customizations: 0
In this example, /tmp/staging is the staging area where ssopatch copies the files.
Update the files as needed in the staging-area, using the results of the previous step.
Use the following table to determine the action you might need to take for each file before you generate a new patched WAR file.
|
Next Steps
Create a new OpenSSO WAR file from the files in the staging area. For example:
cd /tmp/staging jar cvf /patched/opensso.war *
where /patched/opensso.war is the new patched OpenSSO WAR file
Redeploy the /patched/opensso.war file to the web container using the original deploy URI. For example, /opensso
OpenSSO configuration changes. A new OpenSSO WAR file might have configuration changes that were not in your original WAR file. Any configuration changes, if any, will be documented separately for each patch. Check the patch documentation and the Sun OpenSSO Enterprise 8.0 Release Notes for more information about any configuration changes. (The version string in the OpenSSO manifest file will change, even if there are no configuration changes in the new WAR file.)
If you need to back out your patched version, undeploy the patched WAR file and then redeploy your original WAR file.