Chapter 1 Overview of the Upgrade Process

This chapter provides an overview of the Identity Manager upgrade process.
The information is organized as follows:

Why Upgrade?

Upgrading your release of Identity Manager provides numerous advantages, such as:

Upgrade Paths and End of Service Life

This section provides information about the upgrade paths you should follow when upgrading Identity Manager, and describes Identity Manager’s End of Service Life (EOSL) policy for the products software support.

Identity Manager Upgrade Paths

Use Table 1-1 to determine the upgrade path you must follow when upgrading to a newer version of Identity Manager.

Table 1-1 Identity Manager Upgrade Paths
Current Version	Target Version
Current Version	5.0	2005Q3M1	2005Q4M3	7.0
Waveset Lighthouse 4.1 SPx	5.0	5.0 > 2005Q3M1	5.0 > 2005Q4M3	5.0 > 2005Q4M3 > 7.0
Identity Manager 5.0 SPx		2005Q3M1	2005Q4M3	2005Q4M3 > 7.0
Identity Manager 2005Q1M3 Identity Auditor 1.0		2005Q3M1	2005Q4M3	2005Q4M3 > 7.0
Identity Manager 2005Q3M1 Identity Manager 5.5			2005Q4M3	2005Q4M3 > 7.0
Identity Manager 2005Q3M3 Identity Manager SPE 1.0			2005Q4M3	2005Q4M3 > 7.0
Identity Manager 2005Q4M3 Identity Manager 6.0				7.0



Note	When upgrading Identity Manager, you do not have to install Service Packs within a major release to upgrade to the next major release. For example, when upgrading from Identity Manager 5.0 to 6.0, you do not have to install any of the 5.0 Service Packs. Service Packs for a major release are cumulative. After upgrading to the major release, you can install the latest service pack without having to install all of the service packs for that release. For example, if you upgraded to Identity Manager 5.0, installing SP6 gives you all of the functionality provided in SP1 through SP5.

End of Service Life for Software Support

During the End of Service Life (EOSL) period, Identity Manager software support is offered in two phases:

Full Support Phase

During the Full Support Phase, Sun Microsystems, Inc. provides software support in accordance with the customer's support contract with Sun (including the applicable Service Listing) as set forth at:

However, when a software product’s EOL date is announced, customers will no longer have access to software updates and upgrades for that software product.

Limited Support Phase

During the Limited Support Phase, Sun Microsystems, Inc. provides software support in accordance with the customer's support contract with Sun (including the applicable Service Listing) as set forth at:

However, customers are not entitled to submit bugs or to receive new patches from Sun Microsystems, Inc. As with Full Support Phase, when a software product’s EOL date is announced, customers will no longer have access to software updates and upgrades for that software product.


Note	The length of the Full Support Phase varies by product. Table 1-2 provides information about the EOSL and EOL dates for older versions of Identity Manager.

Table 1-2 End of Service Life (EOSL) for Software Support
Product Name	Product Status	Last Ship Date	Phase 1 End Date	Phase 2 End Date (EOSL)	EOL Announcement
Sun Java System Identity Auditor 1.0 2005Q1	Post-RR	02/02/2007	02/2008	02/2012	08/01/06
Sun Java System Identity Manager Service Provider Edition 1.0 2005Q3	Post-RR	02/02/2007	02/2008	02/2012	08/01/06
Sun Java System Identity Manager 5.0 2004Q3	EOL	08/11/2006	08/2007	08/2011	02/07/06
Sun Java System Identity Manager 5.0 SPx 2004Q3	EOL	08/11/2006	08/2007	08/2011	02/07/06
Sun Java System Identity Manager 5.5	EOL	08/11/2006	08/2007	08/2011	02/07/06
Waveset Lighthouse 4.1			03/2006	03/2010

Phases of an Upgrade

Figure 1-1 lists the major phases of the upgrade process, summarizing the tasks that you must perform to complete each phase. This document guides you through each phase.

Example of a Typical Upgrade

For this example, assume that you are upgrading from the Identity Manager 5.0 release to the 6.0 release with the latest available 6.x service pack. (Always use the latest available service pack for the version to which you are upgrading.)

Before you start the upgrade, be sure to read the following documentation to learn about important product changes:

Identity Manager 5.x service pack Release Notes

Identity Manager Release Notes for the version (and any subsequent service packs) to which you are upgrading



Note	The product changes significantly with each major release, including new functionality and user interface changes. The original Lighthouse product was re-branded as Sun Java™ System Identity Manager for the 5.0 release.

Document your existing environment, which includes:

Your platform

Your Identity Manager installation

Your custom components

Refer to Table 1-1 and decide your upgrade target version.

For example, if your current deployment is Identity Manager 5.5 and you want to upgrade to Identity Manager 7.0, then you must upgrade first to Identity Manager 6.0 and then to Identity Manager 7.0.

Back up your existing database and Identity Manager file structure.

Backing up the database and file structure gives you the ability to reinstate your working environment, if necessary.

Create a test environment install that mimics the functionality of your production installation.

Develop a comprehensive test plan.

The goal of the test plan is to confirm that all currently utilized product functionality remains intact after the test before deploying the upgrade in the production environment.

Check the version levels of your infrastructure components (operating systems, JDK, application server, database, resource, and so on) to confirm that they will support the upgraded product.

For supported versions, see Identity Manager Installation.

Rebuild any custom java classes against the target product libraries (for example, new JAR files, new JDK, and Application Server libraries.)

Document and make any necessary changes in XPRESS, and Workflow and Form utility calls.

Remove any hotfix class files from your WEB-INF/classes directory, if any exist.

Upgrade any individual Sun Identity Manager Gateway (Gateway) or PasswordSync installations at the same time.

Complete the entire upgrade before attempting to start the application server and resuming activity.

Optional, set to manual start any active sync processes, and disable any scheduled reconciliations (if applicable) until the upgrade is complete and appears to be successful.

Upgrading from 5.x to 6.x or from 6.x to 7.0 requires a database schema upgrade. See Step 2 for more details.

If you are upgrading to Identity Manager version 6.0 or 7.0 from an earlier release, you must remove the Cryptix jars (cryptix-jceapi.jar and cryptix-jce-provider.jar) from the idm\WEB-INF\lib directory.

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

If you modified any default Identity Manager objects (for example, 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.

Be careful when you edit the super role field in the Role Form because the super role itself may be a nested role. The super and sub roles fields indicate a nesting of roles and their associated resources or resource groups. When applied to a user, the super role includes the resources associated with any designated subrole. The super role field is displayed to indicate the roles that include the displayed role.

If you extracted WPMessages.properties to the /config directory and customized the messages, you should extract and apply the customizations again. In Identity Manager 5.x the preferred way to customize messages is to use a configuration object. For more information, refer to “Rename Customized Identity Manager Repository Objects” and “Attribute Registration” in chapter 14 of the 5.0 SP3 Identity Manager Technical Deployment.

Previous Contents Index Next
Sun Java[TM] System Identitiy Manager 7.0 Upgrade