Home
HCL Digital Experience 9.5 [Legacy content]
Migrating
Successful migration requires significant planning and preparation, understanding the tools that are involved, and careful execution of the appropriate steps in the order provided.
Planning for migration
Completing a thorough plan before migrating to the latest version of HCL Digital Experience has a direct impact in the effort invested during the actual migration. Become familiar with the environment you are migrating to (target environment). Also, make sure that the environment you are migrating from (source environment) is up to date with fixes and meets the requirements for migration.
Migration considerations
There are a number of ways in which you can migrate HCL Digital Experience to a newer version. Some migration scenarios might offer a higher availability percentage over another. There are some scenarios where the migration can be done in parallel while your source environment remains in production. Other scenarios might require the production system to be disconnected just before you go live with the newly migrated system. Depending on your needs on high availability systems, you might choose one approach or another.
Migrating from Portal 8.0.0.1 on WebSphere Application Server 8.5.5.2
If you are migrating from HCL Digital Experience Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2 to HCL Digital ExperienceVersion 8.5, you must follow a different migration process.
Using staging to production techniques to complete the migration
Choose this option if you want to use staging to production techniques to migrate from Portal Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2 to HCL Digital Experience 8.5.

HCL Digital Experience 9.5 [Legacy content]
- Overview
  HCL Digital Experience provides a single access point to web content and applications, while it delivers differentiated, personalized experiences for each user across multiple touchpoints, such as web, mobile, hybrid mobile/web applications, and more.
- Supported migration paths
  Migration is supported between equivalent HCL Digital Experience offerings.
- Supported installation and upgrade paths
  Installation and upgrade is supported between equivalent HCL Digital Experience offerings.
- Getting the software
  New and existing users need to register at the HCL Software License Portal and download their entitled HCL Digital Experience package(s).
- Creating your website
  Review the following topics to understand how to create your website using the latest HCL Digital Experience.
- Installing HCL Digital Experience
  Review the planning information on HCL Digital Experience, then select your operating system and installation pattern that most reflects your business needs.
- Configuring
  Run the following tasks after you install and deploy HCL Digital Experience. They address tasks that are typically run one time and have a global effect. Some configuration changes are made more frequently or do not have a global effect. These tasks are addressed in the Administering section.
- Backup and restore
  Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications that run in production environments. Create and follow a plan for backing up and recovering data on all tiers of your HCL Digital Experience deployment. IBM Installation Manager must also be included in backup and recovery planning. If you back up the HCL Portal file structure and then install a fix pack, your HCL Digital Experience and IBM Installation Manager become out of sync after you restore the HCL Portal file system. This condition is not recoverable.
- Migrating
  Successful migration requires significant planning and preparation, understanding the tools that are involved, and careful execution of the appropriate steps in the order provided.
  - Overview
    Migration is the process of collecting configuration data and applications from an earlier installed version of HCL Digital Experience 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 to a different (remote) server is not supported.
  - Planning for migration
    Completing a thorough plan before migrating to the latest version of HCL Digital Experience has a direct impact in the effort invested during the actual migration. Become familiar with the environment you are migrating to (target environment). Also, make sure that the environment you are migrating from (source environment) is up to date with fixes and meets the requirements for migration.
    - Supported migration paths
      Migration is supported between equivalent HCL Digital Experience offerings.
    - Hardware considerations
      There might be cases where you are completing a remote migration to a new hardware configuration. This new server might have different requirements from the current environment you are migrating from. Generally, here are some key points to consider.
    - Operating systems considerations
      There might be cases where you upgrade not just to a newer version of HCL Digital Experience but also to a different operating system version. In that case, there might be a different set of system requirements and considerations to keep in mind.
    - Migration considerations
      There are a number of ways in which you can migrate HCL Digital Experience to a newer version. Some migration scenarios might offer a higher availability percentage over another. There are some scenarios where the migration can be done in parallel while your source environment remains in production. Other scenarios might require the production system to be disconnected just before you go live with the newly migrated system. Depending on your needs on high availability systems, you might choose one approach or another.
      - Backup and recovery
        Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications that run in production environments. Create and follow a plan for backing up and recovering data on all tiers of your HCL Digital Experience deployment. IBM® Installation Manager must also be included in backup and recovery planning. If you back up the HCL Portal file structure and then install a fix pack, the HCL Digital Experience and IBM Installation Manager become out of sync after you restore the HCL Portal file system. This condition is not recoverable.
      - Local or remote migration
        Review the considerations for local and remote migrations. Plan and review your options for an appropriate migration path that is based on your current environment.
      - Automated or manual migration
        The HCL Digital Experience product documentation documents the automated migration process that is the commonly used and supported method for migrating to a new version of HCL Digital Experience. However, this approach might not be the ideal type of migration for all customers. Read the following considerations to determine which approach fits your needs.
      - Portal farm migration
        The Portal farm migration consists of disabling farm mode and running the stand-alone migration. If you are migrating a unique installation farm configuration, you must migrate each farm member. If each farm instance is a clone, you can migrate one instance, and then create clones that are based on the migrated instance. When the migration is complete, you can re-enable farm mode.
      - Multiple tier environments
        When you migrate multiple tier environments, you have two options for completing the migration process. You can choose to migrate each tier independently, or you can migrate the lowest tier and use staging to production techniques to build out the other tiers based on the migrated environment.
      - Multiple cluster environments
        If you are migrating an environment with multiple clusters, you can run the create-alias-multiple-cluster task to support multiple clusters that use different credentials.
      - Migrating from Portal 8.0.0.1 on WebSphere Application Server 8.5.5.2
        If you are migrating from HCL Digital Experience Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2 to HCL Digital ExperienceVersion 8.5, you must follow a different migration process.
        Using staging to production techniques to complete the migration
        Choose this option if you want to use staging to production techniques to migrate from Portal Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2 to HCL Digital Experience 8.5.
        Performing a manual in-place migration
        If you proceed with this method of migration for Portal Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2, be aware that you cannot use the WebSphere remote migration tool because the WebSphere version of the source and target environments are the same. This migration is an in-place migration, and the source environment will no longer be available after the migration is complete.
      - Migration from Portal Server Offering 7.0 to Portal 8.5
        You can migrate from a Portal Server Offering 7.0 to Portal 8.5. For more information about Portal Server Offering, see the Overview topic from the related links section. When you migrate from a 7.0 Server Offering-only installation to HCL Portal Version 8.5, you must complete steps that are not covered in the Configuration Wizard migration options. Instead of using the wizard to complete the final upgrade the Portal profile step, you must complete this step manually.
      - Migrating from Web Content Manager version 7.0 or 8.0
        These are the migration options available when migrating from Web Content Manager version 7.0.x or 8.0.x.
      - Library export and import and migration
        During migration, it is possible that a port conflict might occur when starting up the target environment deployment manager, node agents, or HCL Digital Experience servers.
    - Development considerations
      The goal of the migration process is to ensure that the target environment works similarly to the source environment. However, there are deprecated and unsupported features and changes in supported technical specifications that can prevent this transition from being seamless. Review the following topics for guidance on the development work that is required to maintain the functionality of the source environment and also begin preparation for enabling new features and functionality.
    - What to expect after you complete migration
      During the migration process, your portal applications, portlets, and databases are updated to the HCL Digital Experience 8.5 versions. However, not all of the new HCL Digital Experience 8.5 functionality and features are enabled by default. The following sections provide information on how various components are handled during migration, and what you can expect after the migration is complete.
  - Preparing your source environment
    Before you begin the steps for migration, you must perform some critical tasks on your source environment, such as creating back ups, installing the latest cumulative fix and one of the two most recent fix packs, and disabling automatic synchronization if you are migrating a cluster. Review the topics in this section, and perform the required tasks to ensure that your source environment remains functional and the migration completes successfully.
  - Setting up the target environment
    The migration requires you to install the required Portal and WebSphere® binary installations. To prepare your target environment, ensure that you have applied the latest cumulative fix and the most recent fix pack before you start migration. In addition, create new copies of the source databases for the target environment to use, and prepare the target environment for any custom applications that have dependencies or any other tasks that need to be performed for remote or cluster migrations.
  - Migrate data using the configuration wizard
    For Version 8.5, data, applications, databases, property files, security settings, and configuration are migrated using the Configuration Wizard. Use the roadmaps for cluster and stand-alone environments to guide you through the process.
  - Next steps
    To complete migration, you must first perform several post-migration steps that depend on how Portal is being used. After completing the post-migration steps, review the Enabling new functionality section to take advantage of the new tools available in HCL Digital Experience 8.5. Enabling new functionality should not be started until all post-migration steps have been completed.
- Integrating
  Integrate HCL Digital Experience with software such as HCL Sametime to enable your users to collaborate more easily. You can also use the unified task list portlet to integrate HCL with your backend business process software, such as IBM Process Server.
- Administering
  Use the administration tools that are provided with the HCL Digital Experience to do various day-to-day administration tasks.
- Securing
  Security tasks include setting up property extension databases and custom user repositories, configuring and activating SSL, and configuring authentication. In addition, tasks such as activating Federal Information Processing Standards (FIPS) and NIST SP800-131a security modules and configuring external security managers such as Security Access Manager might be required to secure your portal environment.
- Monitoring
  HCL Portal includes tools and features to help you monitor the portal site.
- Setting up a website
  Setting up a website includes, creating pages, adding navigation, setting up search, and adding content to the site. Themes are used to customize the portal's look-and-feel. Out-of-the-box templates and the site wizard can help you set up your portal site faster. You can add wikis and blogs to your site and let users tag and rate content on your site.
- Staging to production
  During portal solution development, the solution is initially developed, tested, and refined on one server or a limited number of servers. The solution is deployed later on live systems, referred to as the production environment. The process of moving the solution from the development environment to the production environment is called staging.
- Developing
  This section includes developer documentation on extending applications and development assets for HCL Portal and HCL Web Content Manager.
- Docker and Containerization
  Find topic information about Docker and Containerization for HCL Digital Experience.
- Practitioner Studio
  Practitioner Studio is a newly designed user experience for HCL Digital Experience. Please see the following pages to understand how the new navigation is organized.
- HCL Experience API
  This shows developers how to provision, configure, and use the HCL Experience API with the HCL Digital Experience 9.5 platform.
- HCL Content Composer
  The HCL Content Composer delivers simplified processes for creating and managing Digital Experience site content.
- HCL Digital Asset Management
  HCL Digital Asset Management (DAM) adds a central platform to store and include rich media assets in Digital Experience site content to present engaging, consistently branded experiences across digital channels.
- The Woodburn Studio demo site
  The Woodburn Studio is a website that demonstrates the use of some of the popular HCL Digital Experience features.
- Reference
  View information that can help you use our product documentation including terms of use, trademarks, and more.

Using staging to production techniques to complete the migration | HCL Digital Experience

Choose this option if you want to use staging to production techniques to migrate from Portal Version 8.0.0.1 on WebSphere® Application Server Version 8.5.5.2 to HCL Digital Experience 8.5.

About this task

You can set up a staging server with a Portal 8.0.0.1 and WebSphere® Application Server 8.0.0.5 installation, and use the staging to production tools to create a new environment that is based on the source environment.

Procedure

Install Portal 8.0.0.1 and WebSphere® Application Server 8.0.0.5 on a staging server with the same operating system as the source server.
Use the HCL Portal staging to production tools to deploy a stand-alone server that is based on the source server.
Install the HCL Digital Experience 8.5 and WebSphere® Application Server 8.5.5.2 binary files on the target server.
Access the Configuration Wizard on the target server, and click Migrate to a New Version > Migrate a Stand-alone Server.
Optional: When you complete the migration of the stand-alone staging server, you can build it into a cluster if needed.