HOW TO UPGRADE SUN IDENTITY MANAGER PRODUCT

Here in am going to explain you the Basic thing About When you upgrade the Identity manager from Existing Version to New Version just Take care of following Things..

Identity Manager Upgrade Process

• The process for upgrading Identity Manager is as follows:Prepare for the upgrade >-
  
  > Document existing environment
  > Determine upgrade version
  > Document customizations
  
• Develop an upgrade plan
  
  > Create test environment
  > Upgrade test environment
  > Verify correct upgrade

• Production environment deployment
  
  The procedure for updating Identity Manager is as follows:
  
  > Develop Production rollout plan
  > Execute the plan

Back up Identity Manager

> File system
> Database

• Preserve local changes (customizations)
• Upgrade the software
• Set the license key (if necessary)
• Confirm that the local changes have been restored
• Restore any additional customizations

Identity Manager Tools for Upgrade

• Describe the issues associated with upgrades
• Describe the file system assessment tool
• Describe the repository object assessment tool
• Use assessments and snapshots

Issues With Upgrades Problem:

• Difficult to determine what files have been modified creating problems in upgrades
• Difficult to determine what objects have been modified when problems are reported to support

Solution:

• lh assessment
• Snapshot

Types of Changes

• Files on the file system:

JavaServer Pages™ (JSP™ pages)
Cascading Style Sheets (CSS)
Property files
Resource bundles
Service packs

• Repository objects:

Roles
User forms
Configuration objects

File System Inventory

The lh assessment tool:

• Cannot be used in the UI because APIs are not available in application servers.
• Uses initial checksums kept in idm.jar (per file system object)
• Determines actually modified files, not just a timestamp change
• Checks for Java classes as well (WEB_INF/classes/com)
• Uses the WSHOME environment variable
• Creates output that can be saved to a file

Inventory Sub-commands lh assessment

• inventory – a (files added)
• inventory – m (files modified)
• inventory – d (files deleted)
• inventory (all files added, deleted or modified)
• installed (list installed releases, service packs, and hot fixes)

Repository Object Changes

Administrative Interface using the Debug Pages:

:PORT">http://:PORT NUMBER/IDM CONTEXT/debug

• The baseline.xml file is shipped with each release.
• Administrators can create additional snapshots that can be compared.
• Most objects and object attributes are saved to a separate object in the database:

No users
No resources

• Snapshot processing goes through internal caches. (This might cause some inconsistencies.)
• Snapshots can be exported to a file.
• A snapshot is not a rollback.

Repository Objects Captured

TaskDefinitions
Roles
Configuration
Objects
AdminRole
AdminGroup
EmailTemplate
Policy
ResourceForm
ResourceAction
Rule
TaskTemplate
UserForm
RemedyConfig

Snapshot Compare

• You have the ability to compare two snapshots to determine object differences.
• A baseline snapshot called baseline.xml is available in the idm/sample directory.
• Import the baseline snapshot.
• Create another snapshot.
• Compare the two.