|
| |
| Sun Java[TM] System Identitiy Manager 7.0 Upgrade | |
Chapter 2
Preparing to Upgrade Identity ManagerCareful preparation allows for a smoother upgrade path. Listing your goals for the upgrade can help you make decisions that are in line with your company’s needs.
This section describes how to prepare to upgrade Identity Manager.
The information is organized into the following sections:
Documenting the Existing EnvironmentUpgrading to a more-recent Identity Manager release might affect the make-up of your current environment. By assessing and documenting your platform, Identity Manager installation, and custom work as described in this section, you can determine the best path and extent of complexity for your upgrade.
Document Your Platform
To determine the best upgrade path, use the worksheets provided in Appendix A, "Assessment Worksheets" to inventory the components of your current platform, including:
Application Servers
Record the application server version and note any additional service packs. In addition, record the following:
Database Servers
Record the database server version and note any additional service packs.
Sun Identity Manager Gateway
Verify which Sun Identity Manager Gateway version you are running by performing the following steps, and then record the information:
Java Runtime Environment
Record the currently installed JDK version that the lh console requires.
Supported Resources
Record supported resources names, versions, and note any additional service packs.
Web Servers
Record the Web server version and note any additional service packs.
Document Your Identity Manager Installation
To determine the best upgrade path, use the worksheets provided in Appendix A, "Assessment Worksheets" to inventory the components of your current Identity Manager installation.
The following sections describe methods for collecting this information:
Identity Manager Version
You can use the Identity Manager Console to verify the version number of your current Identity Manager installation (version 5.0 SP4 and later).
Identity Manager Assessment Tools
Identity Manager provides the following utilities to list and record your installation information:
You can access both utilities by entering the following command:
lh assessment
installed Utility
The installed utility searches the $WSHOME/patches directory for manifests and provides version information for releases, service packs, and hotfixes.
To use the installed utility:
- Change directory to the Identity Manager $WSHOME/patches directory.
- At the prompt, type
installed [option] [option]...
The following table lists the options you can use with this command.
inventory Utility
The inventory utility inspects the file system for files that were added to or deleted from the system, using files that are packaged in the release. This utility determines which files are changed based on the manifest that shipped with Identity Manager.
Document Your Custom Components
To determine the best upgrade path, use the worksheets provided in Appendix A, "Assessment Worksheets" to inventory your custom components, including:
Custom File-System Objects
You might need to update 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, including:
Modified JSPs
Recent Identity Manager versions might include API changes. If you have modified JSPs in your installation, you might have to update them when upgrading. You must update any JSP that was shipped with the product 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 more information about JSP customizations, see Appendix A, “Working with Configuration Objects,” in the Sun Java System Identity Manager Technical Deployment Overview.
Modified waveset.properties File
Record any changes that you made to the default waveset.properties file.
Modified wpmessages.properites 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.
Customized Resource Adapters (and Other Custom Java)
You might have to recompile your customized resource adapters, depending on the target Identity Manager version. All custom Java that uses Identity Manager APIs (including custom resource adapters) require a recompile during upgrading. Also, consider other Java classes that use the Identity Manager library.
Modified Stylesheets
Record any changes that you made to Identity Manager stylesheets.
Custom Repository Objects
You might have to sustain customized repository objects to enable them to function properly with target Identity Manager releases. Record any customized repository objects that are in your environment, including:
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
A schema change occurred with Identity Manager 7.0. 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 re-import them to the newer version of Identity Manager after upgrading.
Choosing the Upgrade VersionAfter completing your inventory assessments, you must decide which Identity Manager version fulfills your requirements. Some users prefer the latest version, while others prefer more mature versions that already have service packs available.
In general, you should upgrade to the most recent Identity Manager release that is available during your testing time frame. For example, assume that:
The projected start of your test cycle is July 15. And the next new Identity Manager release is scheduled for July 10. The currently available Identity Manager release is 5.0 SP6. You should start with 5.0 SP6 in development and initial testing, but switch to the current release before starting the formal test cycle.
After choosing the target Identity Manager release, you must determine whether your current platform is supported at the upgrade level:
Table 1-1 lists suggested upgrade paths, depending on your current version.