To Create a Staging Area to Patch an OpenSSO Enterprise WAR File (Sun OpenSSO Enterprise 8.0 Update 1 Release Notes)

Sun OpenSSO Enterprise 8.0 Update 1 Release Notes

To Create a Staging Area to Patch an OpenSSO Enterprise WAR File

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 1 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.

`ssopatch` Results	Explanation and Action Required
`File not in original war filename`	The indicated file does not exist in the original WAR file but is in the latest version of the WAR file. Action: None
`File updated in new war filename`	The indicated file exists in both the original and new WAR files and has been updated in the latest version of the WAR file. No customizations have been done in the original WAR file. Action: None
`File customized filename`	The indicated file exists in both WAR files, has been customized in the original version of the WAR file, but has not been updated in the latest version of the WAR file. Action: None
`May require manual customization filename`	The file exists in both WAR files, has been customized in the original version of the WAR file, and has been updated in the latest version of the WAR file. Action: If you want your customizations in the file, you must manually add them to the new updated file in the staging directory.
`File was customized in original, but not found in new war`	The file existed in the original WAR file, but is not in the new WAR. Action: None.

Next Steps

Create a new OpenSSO Enterprise 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 Enterprise 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 Enterprise 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.