+

Search Tips   |   Advanced Search

Roadmap: Migrate a stand-alone server environment


Who should use this roadmap?

Use this roadmap if we are:

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 migrating to HCL Portal 9.5. For more information, see Supported migration paths.


Plan for migration

Gather information and create a plan for migration.

Check the requirements and considerations for migration. Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications that are running in production environments. Create and follow a plan for backing up and recovering data on all tiers of the HCL Portal deployment. Don't forget to remove unsupported or deprecated features before you start migration. To migrate multiple environments, such as a production environment or development environment, we can 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. 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.


Set up the target environment

Attention: Before we run the migration, install interim fix PI50840. Set up the target environment for migrating to the latest version of HCL Portal.


Migrate to the latest version of HCL Portal

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

  1. To get the latest updates for the wizard, apply the most recent cumulative fix. For more information about applying the latest fix pack, see Combined Cumulative Fix overview.

    Note: Skip this step, if we have the most recent fix pack applied.

  2. Access the Configuration Wizard using the target environment and system host name. Go to: http://your_server:10200/hcl/wizard.

    Note: If working with HCL Portal 8.5 or 9 software level prior to CF18, the wizard address will be: http://your_server:10200/ibm/wizard. After installing CF18, the configuration wizard will automatically be adjusted to http://your_server:10200/hcl/wizard.

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

  4. Select Migrate to a New Version > Migrate a Stand-alone Server.
  5. Provide information about the environment.

  6. Save the wizard selections.
  7. 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.

Migration is partially complete after you do the tasks in the configuration wizard. We must 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. More tasks must be completed 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 topic: HCL Portal roadmaps for migration