Separate system upgrade and data migration

Use these tasks to migrate database and directory data from an existing IBM® Tivoli® Identity Manager to a separate environment that runs IBM Security Identity Manager Version 6.0.

These tasks require the installation of middleware and the upgrade and installation of IBM Security Identity Manager Version 6.0. The topics include best practices for the upgrade and migration from production environments.

Supported upgrade paths

Table 1. Upgrade paths to IBM Security Identity Manager Version 6.0
From To
IBM Tivoli Identity Manager Version 5.0 that is deployed on WebSphere® Application Server 6.1 IBM Security Identity Manager Version 6.0 that is deployed on WebSphere Application Server 7.0
IBM Tivoli Identity Manager Version 5.1 that is deployed on WebSphere Application Server 6.1 or WebSphere Application Server 7.0 IBM Security Identity Manager Version 6.0 that is deployed on WebSphere Application Server 7.0
IBM Security Identity Manager Version 6.0 that is deployed on WebSphere Application Server 7.0 IBM Security Identity Manager Version 6.0 that is deployed on WebSphere Application Server 8.5
Note: These upgrade paths do not support the migration of Tivoli Identity Manager Version 5.1 that run with either an MS SQL database or a Sun One Oracle directory server.

IBM Security Identity Manager supports data migration for both UNIX systems and Windows systems.IBM Security Identity Manager Version supports data migration among supported UNIX based operating systems. Data that resides in HP_UX environments can be migrated to any of the supported UNIX environments. However, data cannot be migrated from UNIX environments to Windows environments or from Windows environments to UNIX environments.

To migrate data, previous versions of IBM Tivoli Identity Manager must have the latest fix packs and interim fixes installed.

See the IBM Security Identity Manager product documentation to review:

  • The supported release levels and fix pack specifications for the supported operating systems.
  • Instructions for migrating adapters.

For known issues about migrating data, see Post migration troubleshooting and known issues.