+

Search Tips   |   Advanced Search

Roadmap: Migrating a clustered environment

Use this roadmap if we are migrating a clustered environment from v7.0.0.x to v8.5. If we are migrating from IBM WebSphere Portal V8.0.0.1 on WAS v8.5.5.2 to WebSphere Portal v8.5, follow a different migration process.

Apply the latest cumulative fix and one of the two most recent fix packs to the source environment, and the latest cumulative fix and the most recent fix pack to the target environment before we can migrate to WebSphere Portal v8.5. See:

Before starting, check the requirements and considerations for migration.
Create and follow a plan for backing up and recovering data on all tiers of the WebSphere Portal deployment.
Remove unsupported or deprecated features before starting migration.

To migrate multiple environments, such as a production environment or development environment, use staging to production techniques.

Plan a local migration if the source and target environments are on the same system, and plan for a remote migration if the source and target environments are on separate systems.


Prepare the source environment


Prepare the source portal to use for migration.

Review the considerations for a multiple cluster environment for information on supporting multiple clusters that use different database credentials.

To keep the earlier portal environment in production and reduce the amount of downtime during migration copy the earlier portal server JCR and Release domains.

The target environment initially uses the same ports as the source environment. Disable automatic synchronization


Set up the target environment

Set up the target environment


Migrate to WebSphere Portal v8.5

Start the Configuration Wizard to migrate data, applications, databases, property files, security settings, and more.

  1. During a cluster migration, we might need to enter information into the Configuration Wizard more than once. Use the following worksheet to identify the information that is entered multiple times, and use these values during the migration process.

    Field description: Value:
    dmgr host name
    dmgr cell name
    dmgr node name
    Administrator user name
    Administrator password
    Soap port

  2. Access the Configuration Wizard. Go to: http://your_server:10200/ibm/wizard.

  3. Log in to the Configuration Wizard with the administrative ID for the configuration wizard profile, cw_profile.

  4. Select Update or Maintain a Current Environment - Migration > Migrate a Cluster Step 1: Migrate the dmgr Profile.

  5. Provide information about the environment.

  6. Save the wizard settings.

  7. Click Download Configuration Scripts to run the steps on the deployment manager.

  8. After completing the steps from Step 1, select Update or Maintain a Current Environment - Migration > Migrate a Cluster Step 2: Migrate Node Profiles.

  9. Provide information about the environment.

  10. Save the wizard settings.

  11. Choose one of the following options:

    • Click Download Configuration Scripts to run the steps remotely.

    • Click Start Configuration to run the steps locally. This option starts to run the automated steps until a manual step is encountered.

  12. Complete these steps on all nodes.

  13. After completing the steps for Step 2, select Update or Maintain a Current Environment - Migration > Migrate a Cluster Step 3: Upgrade Node Profiles.

  14. Provide information about the environment.

  15. Save the wizard settings.

  16. Choose one of the following options:

    • Click Download Configuration Scripts to run the steps remotely.

    • Click Start Configuration to run the steps locally. This option starts to run the automated steps until a manual step is encountered.

  17. Complete these steps on all nodes


Next steps

Migration is not complete until you review the Next steps section in the product documentation. Complete the post-migration activities and enabling new functionality tasks that are applicable to the environment. Do not complete any of the enabling new functionality tasks until all post-migration activities tasks are finished.

  • Documentation resources: Next steps

    • More tasks might be needed depending on how you customized the source portal environment and which components we used. For example, if we use a virtual portal, then complete the virtual portal post-migration activities.

    • New functionality that was not available in the earlier portal version requires extra attention after migration is complete.

After completing the tasks in the Next steps section of the product documentation, migration is complete.


Parent Roadmaps for migration