Hitachi ID Facebook Page Hitachi ID Twitter Page Find us on Google+

Migrating to Hitachi ID Management Suite 8.0

Webinar: Review of the 8.0 Release for Identity Manager and Password Manager

Press Release: Hitachi ID Systems Releases Hitachi ID Management Suite Version 8.0

HTML Presentation: What's New in v8

Migrating to Hitachi ID Management Suite 8.0

A migration involves exporting configuration parameters from one instance and importing them into another. This differs from a patch or upgrade whereby the instance is simply upgraded in place. Migrations are usually required between major version jumps where a patch or upgrade is simply not possible.

There are three variants of a migration:

No matter which type of migration is being performed there are a number tasks to perform and considerations that must be made to ensure a successful transition.

At a high level one must:

When collecting information about your current deployment, you should take inventory of all of your management suite servers, database back-ends, target systems, other systems that may have Hitachi ID software installed on them (e.g. client components), and infrastructure used by or supporting the use of Hitachi ID software. See the "Research and analysis" sections of the full migration guide for a detailed list of components to catalog.

A well documented migration plan will help ensure that steps are not missed during the migration. The migration plan should consist of:

The last phase of the migration process involves carrying out the migration plan. This involves exporting configuration and data in the current instances, modifying that data if required to fit into the concepts of the new instance, and importing the transformed data into the new servers. Once this is done, the test plan should be executed to ensure that everything behaves as expected and once validated the switch over can be made.