Migration overview

Migration is the process of collecting configuration data and applications from an earlier installed version of IBM WebSphere Portal and merging them into a newer installed version. So that the new environment is identical to the earlier environment. For the z/OS platform, the new version must be on the same server as the earlier version.

Migration is different from upgrading. With upgrading, you replace an existing installed out-of-date version files with current files. With migration, you install the new version of a product alongside of the earlier version and then copy data from the earlier version to the new version. Migrating information from the earlier version to the new version lets we use that information in the new version without having to re-create it from scratch. Migration also lets you carry forward customizations that were implemented in the earlier portal, so that we can continue to use them in the new portal.

WebSphere Portal also supports integration with additional products to extend core functionality. If the earlier portal environment is configured to work with one or more supported products that provided integrated features, you need to follow the migration procedures for the integrated product.

Migrated elements are not automatically upgraded to use features available in the new version. Taking advantage of new functionality that was not available in the earlier portal requires additional attention after migration is complete.

We can migrate to WebSphere Portal v8.0 from either Version 6.1.x or 7.x. See Supported migration paths.

Notes

• Migration can be performed locally or remote.

• Migration can be non-destructive and allow both the source and target to run simultaneously.

• WCM Support can be added to a Portal Server during migration.

• Migration is only supported from the two previous main versions.
  • v6.1 --> v8 is supported
  • v7 --> v8 is supported
  • v6 --> v8 is not supported

• Migration is not cross platform.
  • v7 on Linux . v8 on Linux is supported
  • v7 on Windows . v8 on Linux is not supported
  • Platform changes should be done as a separate task before or after migration.

• Migration does not allow changing cell or node names.
  • Cell and node name changes should be done as a separate task before or after migration.

Migration walkthru

1. Prepare source and target environment
2. Import source Portal Profile to target environment
3. Connect target environment to copies of the Databases
4. Upgrade the target Portal Profile
5. Post migration steps

Parent: Migrate
Related: Migrate Portal on AIX IBM i Linux Solaris Windows
Migrate Portal on z/OS
Set up the target environment
Post-migration activities
Plan for migration