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 Two OpenSSO WAR Files
To Compare Two OpenSSO WAR Files
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
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 determine if an OpenSSO WAR file has been customized or modified since it was downloaded.
The ssopatch utility generates a new internal manifest file and then compares this internal manifest against the manifest stored inside the original OpenSSO WAR file in the META-INF directory.
Run ssopatch to compare the OpenSSO WAR file to its internal manifest. For example:
./ssopatch -o /zip-root/opensso/deployable-war/opensso.war Generating Manifest for: /zip-root/opensso/deployable-war/opensso.war Comparing manifest of Internal (Enterprise 8.0 Build 6(200810311055)) against /zip-root/opensso/deployable-war/opensso.war (generated-200905050855) File not in original war (images/login-origimage.jpg) File updated in new war (images/login-backimage.jpg) File updated in new war (WEB-INF/classes/amConfigurator.properties) Differences: 3
This example shows these changes to the original WAR file:
images/login-origimage.jpg is in opensso.war but was not found in the original manifest.
images/login-backimage.jpg has been customized in opensso.war from the original manifest.
WEB-INF/classes/amConfigurator.properties file has been customized in opensso.war from the original manifest.