Step 3: Document Your Custom Components

Use the worksheets provided in Chapter 7, Assessment Worksheets to inventory your custom components, including the following:

• Customized Database Table Definitions

• Custom File System Objects

• Custom Repository Objects

• If you are using the Identity Manager IDE or an older version Consolidated Build Environment (CBE), these component customizations should already be part of your baseline. In this case, the CBE baseline serves as your documentation.

• If your current Identity Manager installation has a large amount of custom work, contact Sun Professional Services for assistance with your upgrade.

Customized Database Table Definitions

Version 7.1 and version 8.0 of Identity Manager made significant changes to the Identity Manager database table definitions.

If you previously modified the database table definitions for the Identity Manager repository, you must decide whether to make the same modifications to the new and updated tables.

Custom File System Objects

You might need to update your customized file system objects to enable them to function properly with later Identity Manager releases. List any customized file system object names that are in your environment as explained in the following sections.

Modified JavaServer Pages Files

Recent Identity Manager versions might contain API changes. If you have modified .jsp files in your installation, you might have to update them when upgrading. You must update any JSP that was supplied by Identity Manager and changed during a deployment (or a custom JSP that uses Identity Manager APIs) to work with the new JSP structure and API changes for the target release.

For a detailed description of API changes, see the Identity Manager Release Notes for the release to which you are upgrading.

Use the inventory -m command (described on Identity Manager Assessment Tools) to identify any JSP modifications made in your deployment.

For more information about JSP customizations, see Chapter 11, Editing Configuration Objects, in Sun Identity Manager 8.1 Technical Deployment Overview.

Modified Waveset.properties File

Record any changes that you made to the default Waveset.properties file.

Modified WPMessages.properties File

Record any changes that you made to the default WPMessages.properties file.

Customized Property Files

Record any changes that you made to other property files on your system.

Custom Resource Adapters (and Other Custom Java)

You might have to recompile your custom resource adapters, depending on the target Identity Manager version. All custom Java code that uses Identity Manager APIs (including custom resource adapters) requires a recompile during upgrading. Also, consider other Java classes that use the Identity Manager library.

Modified Stylesheets

Record any changes that you made to the Identity Manager stylesheets.

Custom Repository Objects

You might have to maintain customized repository objects to enable them to function properly with target Identity Manager releases. Record any customized repository objects that are in your environment as explained in the following sections.

You can use the Identity Manager SnapShot feature to create a baseline or snapshot of the customized repository objects in your deployment, which can be very useful when planning an upgrade. See Step 5: Take a Snapshot for more information.

Modified Forms

You might have to update customized forms to take advantage of current product enhancements.

Modified Workflows

You might have to update customized workflows to take advantage of current product enhancements.

Modified Email Templates

You might have to export customized email templates to take advantage of current product enhancements.

Custom Repository Schema

Significant schema changes occurred between Version 7.0 and Version 8.0 of Identity Manager. If you are upgrading from an earlier version of Identity Manager, you must update your schema.

Other Custom Repository Objects

Record the names of any other custom repository objects that you created or updated. You might have to export these objects from your current installation and then reimport them to the newer version of Identity Manager after upgrading.

The SPML 2.0 implementation in Identity Manager changed in version 8.0. In previous releases, the SPML objectclass attribute used in SPML messages was mapped directly to the objectclass attribute of Identity Manager User objects. The objectclass attribute is now mapped internally to the spml2ObjectClass attribute and is used internally for other purposes.

During the upgrade process, the objectclass attribute value is automatically renamed for existing users. If your SPML 2.0 configuration contains forms that reference the objectclass attribute, you must manually change those references to spml2ObjectClass.

Identity Manager does not replace the sample spml2.xml configuration file during an upgrade. If you used the spml2.xml configuration file as a starting point, be aware that this file contains a form with references to objectclass that you must change to spml2ObjectClass. Change the objectclass attribute in forms (where it is used internally), but do not change the objectclass attribute in the target schema (where the attribute is exposed externally).

You can use the Identity Manager SnapShot feature to copy the following, specific object types from your system for comparison:

For specific instructions, see Step 5: Take a Snapshot.