Step 9: Analyze the Changes

You must analyze the changes made by the Identity Manager product upgrade, and update your configurations and customizations accordingly. For example:

• If you modified any JSP files or stylesheets, you must merge these changes into the new JSP files or stylesheets.

• If your Identity Manager application baseline includes Identity Manager product JARs and third-party JARs, you might have to update these JARs in the baseline. Your baseline should also include the SQL scripts that are used to create or update your database tables.

• If you modified any of the default Identity Manager objects (such as the Default User Form), the upgrade process moves those objects into the savedObjects directory. To facilitate future upgrades, rename the modified objects with a custom name, and reference that name in the SystemConfiguration object.

• If you extracted WPMessages.properties to the /config directory and customized any of the messages, you must extract and reapply these customizations.

You must carefully analyze changes made to repository objects during the Identity Manager product upgrade. For example:

• If the Identity Manager product upgrade modified configuration objects that are in your source-control baseline, you must merge these changes into your configuration baseline. For more information, see Step 14: Merge Changes Back Into Source Control.

• If the Identity Manager product upgrade modified configuration objects that are not currently in your baseline, you must add these objects to your application baseline. If you do not add these configuration objects to your application baseline, then you must make other plans to incorporate these changes, such as including the appropriate objects or commands within the subset of update.xml that your upgrade procedure imports in each environment.

---

Tip –

You might decide that you can safely ignore these object changes, but in most cases it is considered a best practice to add these configuration objects to your baseline.

---

• If the Identity Manager product upgrade modified objects in the repository that are not configuration objects, then these objects should not become part of your source-control baseline. For example, the Identity Manager update.xml file might refresh TaskInstance objects, User objects, Account objects, or Entitlement objects.

  Identity Manager Engineering generally avoids updating these object types because there can be so many instances of each type, but in some cases changes are necessary or justified. In such cases, include executing an appropriate subset of the Identity Manager update.xml file in your baseline and in your upgrade process. Use this update.xml subset to update repository objects that are not part of your baseline.

After upgrading, restore any customized files and objects.

Restoring Customized Files

During the upgrade, Identity Manager automatically copies all customized files, such as JSP and HTML files, into the following directory:

$WSHOME/patches/Sun_Java_System_Identity_Manager_Version_Date_/savedFiles

The following table describes the files in this directory.

Table 3–1 savedFiles Directory File Structure

File Name	Description
changedFileList	File containing a list of all saved customized files.  This file also contains a list of files (installed with your older version of Identity Manager) that will be overwritten when files of the same name are installed during upgrade.
notRestoredFileList	File containing a list of all customized files that are not restored during the upgrade process.
notInstalledFileList	File containing a list of newer version files that are not installed during the upgrade process.

The upgrade might add some files that were also installed with your original Identity Manager installation. Before overwriting the older files, Identity Manager automatically saves them in the savedFiles directory. See the changedFileList file for a list of these files.

Identity Manager automatically restores most of the files listed in changedFileList during the upgrade process, but does not restore all of them. See the notRestoredFileList for a list of these files. When restoring customized files, Identity Manager overwrites the newer version of the files that were installed during the upgrade.

You might have to manually restore some of your file customizations. Review the notRestoredFileList file to see a list of the files that were not restored during upgrade. If you must manually restore any customized files, edit the new file that was installed during the upgrade to incorporate your customizations, and then save the newly edited file.

Restoring Customized Objects

If you have configured your form and process mappings in the system configuration, you will not have to restore those object customizations after the upgrade. If you have customized objects that are not listed in the system configuration, then you must manually restore these objects by importing the XML for these objects.

As a safety measure, Identity Manager automatically saves many of the commonly customized objects to files when you import update.xml. These files are saved to subdirectories in the WEB-INF/savedObjects directory. These subdirectories are named with a time stamp of the time at which the import was performed.

Importing update.xml can create up to three subdirectories in the savedObjects directory. You can manually import the object XML files to restore object customizations.