+

Search Tips   |   Advanced Search

Roadmap: Migrating a stand-alone server environment

If migrating from IBM WebSphere Portal V8.0.0.1 on WebSphere Application Server v8.5.5.2 to WebSphere Portal V8.5, follow a different migration process.

See the IBM Knowledge Center for canonical documentation on migration.


Pre-Migration Steps

  1. Plan the migration

    If the source and target environments are on the same system, plan for a local migration. If the source and target environments are on separate systems, plan for a remote migration. To migrate multiple environments, such as a production environment or development environment, use staging to production techniques.

  2. Backup up all tiers of the WebSphere Portal deployment.

  3. Apply the latest cumulative fix, and one of the two most recent fix packs, to both the source environment, and the target environment.

    Remove unsupported or deprecated features.

  4. Prepare the source environment

  5. To keep the earlier portal environment in production, and reduce the amount of downtime during migration, use copies of source database domains.

  6. Set up the target environment for migrating.


Migrate to WebSphere Portal v8.5

  1. Start the Configuration Wizard...

      http://your_server:10200/ibm/wizard

  2. Log in with the administrative ID for the configuration wizard profile, cw_profile, then select...

      Update or Maintain a Current Environment - Migration | Migrate a Stand-alone Server

  3. Provide information about the environment.

  4. Save the wizard selections.

  5. Choose one of the following options:

    • To run the steps remotely, click...

        Download Configuration Scripts

    • To run the steps locally...

        Start Configuration

      This option starts to run the automated steps until a manual step is encountered.

Migration is partially complete after performing the tasks in the configuration wizard. Return to the product documentation to complete the final steps of the migration process.


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

    • Post-migration tasks might be needed. 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