Supported migration paths | HCL Digital Experience
Migration is supported between equivalent offerings. Starting with CF17, additional migration options are supported for HCL Portal server and Web Content Manager offerings.
The following table summarizes supported migration paths:
You can also migrate from a Server install to the Enable or Extend versions of
HCL Portal.
Note for new HCL customers: New users follow the
proven stable path, which is to install HCL Digital Experience Version 8.5 and
CF13, and add HCL Digital Experience Version 9.0 and CF17 to it to upgrade. Also,
new users can also install directly to IBM®
WebSphere® Application Server Version 9.0
out-of-the-box. New customers need to be on HCL Digital ExperienceVersion 9.0 and
CF17 before installing Version 9.5.
Note for V8.5 customers: The new HCL Digital
Experience is built on top of Version 8.5. HCL Digital Experience Version
9.0 adds IBM®
WebSphere® Application Server Version 9.0
support. As such, existing customers on Version 8.5 need to migrate first to HCL Digital
Experience 8.5 and update the version by installing CF13. To go to Version 8.5 to
Version 9.0, current users simply add Version 9.0 and migrate their profile from IBM®
WebSphere® Application Server 8.5 to
Version 9.0.
Note for V9 customers: You cannot migrate
directly to HCL Digital Experience Version 9.0 without installing HCL Digital
Experience 8.5 base and update it with CF13. At this point, customers can go from
Version 9.0 to the latest HCL Digital Experience by updating current version to
CF17, and then install HCL Digital Experience Version 9.5. Afterwards, you can keep
your profile at the current level or migrate your profile to IBM®
WebSphere® Application Server Version
9.0.2
Offering | WebSphere® Portal Express® Version 8.5 | WebSphere® Portal Version 8.5 (Server) | WebSphere® Portal Version 8.5 (Enable, Extend) | Web Content Manager Version 8.5 | WebSphere® Portal Version 9.0 (Enable, Extend, Server) |
---|---|---|---|---|---|
HCL Portal Express Version 7.x | Supported | Not Supported | Not Supported | Supported | Not Supported |
HCL Portal Server Version 7.x (Server) | Not Supported | Supported | Supported | Not Supported | Not Supported |
HCL Portal Server Version 7.x (Enable, Extend) | Not Supported | Supported | Supported | Supported | Not Supported |
Web Content Manager Version 7.x | Not Supported | Not Supported | Not Supported | Supported | Not Supported |
WebSphere® Portal Express® Version 8.0 on WebSphere® Application Server Version 8.0 | Supported | Not Supported | Not Supported | Supported | Not Supported |
WebSphere® Portal Server Version 8.0 (Server) on WebSphere® Application Server Version 8.0 | Not Supported | Supported | Supported | Not Supported | Not Supported |
WebSphere® Portal Server Version 8.0 (Enable, Extend) on WebSphere® Application Server Version 8.0 | Not Supported | Supported | Supported | Supported | Not Supported |
Web Content Manager Version 8.0 on WebSphere® Application Server Version 8.0 | Not Supported | Not Supported | Not Supported | Supported | Not Supported |
WebSphere® Portal Server Version 8.0 (Server) on WebSphere® Application Server Version 8.5.0 | Not Supported | Supported | Supported | Not Supported | Not Supported |
WebSphere® Portal Server Version 8.0 (Enable, Extend) on WebSphere® Application Server Version 8.5.0 | Not Supported | Supported | Supported | Supported | Not Supported |
Web Content Manager Version 8.0 on WebSphere® Application Server Version 8.5.0 | Not Supported | Not Supported | Supported | Supported | Not Supported |
Note for Version 6.1 customers: If you are currently on Version
6.1, you must perform a two-step migration from Version 6.1 to Version 8.0, and then from
Version 8.0 to 8.5. Go to the HCL Knowledge Base document, Migrating from HCL Portal 6.1 to Portal 8.0, for
guidance on the two-step migration process. Then proceed to the Digital Experience Help
Center Migration
Overview to migrate from HCL DX Portal and Web Content Manager Version 8 to
8.5.
Important Fix Pack Requirements: Migration is supported from the
two most recent fix packs for HCL Portal Version 7.0.0.2 and Version 8.0.0.1. However, you
must apply the latest cumulative fix to your source environment. Your target environment must
also have the latest cumulative fix and the most recent fix pack applied.
If you are not sure which earlier version is installed, run the following command on the
earlier portal server:
- Windows™: wp_profile_root\PortalServer\bin\WPVersionInfo.bat
- UNIX™Linux™: wp_profile_root/PortalServer/bin/WPVersionInfo.sh
- IBM® i: wp_profile_root/PortalServer/bin/WPVersionInfo.sh
- z/OS®: PortalServer_root/bin/WPVersionInfo.sh
When you migrate to Version 8.5, HCL Portal
automatically migrates the following applications and configuration data:
- Security configuration
- Access control
- Portal behavior
- Portlet applications
- Customized portal resources, such as themes and skins, pages, and portlets
- Personalized content
- Virtual portals
Note: You cannot upgrade the source portal with a fix pack after migration if you intend to
remigrate the JCR. For example, if your source portal is Version 7.0.0.1 and you migrate it to
Version 8.5, you cannot then upgrade the source
portal to Version 7.0.0.2 and remigrate the JCR. This path is not supported.