IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment
Migrating to the same version on new hardware
Use these migration procedures to migrate your existing environment, including applications and running instances, to the same version running on new hardware.
You can migrate your environment to new hardware when migrating to a new version. These procedures describe how to migrate to new hardware without changing the product version. This remote migration case is simpler than version to version migration because the databases and infrastructure applications do not need to be migrated.
The target and source systems can be running different operating systems and can have different word lengths.
For example, you could migrate from a 32-bit Windows system to a 32-bit or 64-bit Windows, Linux, or UNIX system.
Overview
Migrating to new hardware requires the following steps.- Install the identical product version and fix level on the target system.
- Export the configuration on the source system.
- Copy the exported configuration to the target system.
- Create a new profile where the configuration can be imported.
- Import the new configuration into the target profile.
- Perform postmigration actions.
- Verify the migration.
- Migrating a stand-alone environment to the same version on new hardware
Use this procedure to migrate a stand-alone environment to the same version on new hardware. - Migrating an ND environment to the same version on new hardware with full downtime
Use this procedure to migrate an ND environment to the same version on new hardware, while incurring full downtime. - Migrating a profile to the same version on a remote system (new hardware)
Use this procedure for migrating a server profile to the same version on new hardware. - Postmigration tasks for migrating to new hardware
After migrating to new hardware, you might need to change some configuration settings that could not be updated automatically. - Verifying migration to new hardware
Verify that your migration to new hardware was successful by checking the log files and the error files for each migration step, and checking operation with the administrative console.