Unsupported and deprecated features for HCL Digital Experience 8.5 and 9.0

Review the features that were available in previous versions of HCL Digital Experience but are no longer available.

After a migration, features that are no longer supported or are deprecated can result in unpredictable behavior. Remove unsupported and deprecated features before you start your migration. As they become available, links to more information are provided to help you move away from deprecated features.

If you are migrating from 7.0, review the unsupported and deprecated page for 8.0 too. A link is provided at that end of the page.

Unsupported features and themes

The following features and themes are unsupported in HCL Digital Experience 9.0:
Table 1. Unsupported features and themes
Category Unsupported Recommended action
Developing JSF 2.0 portlets JSF 2.0 and earlier portlets might not work when imported to a system with HCL Digital Experience 9.0 and IBM® WebSphere® Application Server 9.0. If it does not work, migrate the portlet to the JSF 2.2 level.
Site set up Web Clipper The Web Clipper portlet is no longer supported. Use the Web Application Bridge solution instead.
Developing HCL themes from a previous version The following themes are no longer supported: Portal, PortalWeb2, and Tab Menu - Page Builder. They no longer work and are no longer supported. You must manually update these themes. Merge their function into a clean copy of a Portal 8.5 theme on the target server. The PageBuilder2 and Portal 7002 themes are deprecated in 8.5.
Administering Composite applications Composite applications are no longer supported. If you have a composite application in your system and you are migrating to HCL Digital Experience 8.5, the migration fails. Ensure that all composite applications are deleted before you start the migration. When you delete a composite application, you must also run the resource cleaner, otherwise pages can still exist in the database.
Developing CAI/TAI portlets When you are migrating from one version to another, your script can contain references to the CAI/TAI portlets. These portlets are no longer available and any reference to these portlets cause your script to fail. For more information, see Virtual Portal tasks.
Developing HCL Portlet API The HCL Portlet API is no longer supported. Go to Converting HCL Digital Experience portlets (AIX IBM i Linux Solaris Windows) to learn how to convert your portlets that are based on HCL Portlet API to the Standard Portlet API. The JSR 168 standard API is still available and supported.
Developing Struts Portlet Framework The historical struts-based portlet frameworks are deprecated. Both the struts-based portlet framework based on the HCL Portlet API and the struts-based portlet framework based on the JSR 168 standard API are no longer available and are removed from support. Move all struts-based portlets that are based on this HCL framework to the Apache Struts Portlet Framework.
Integrating Brightcove player The Brightcove player is no longer supported.

Deprecated features and themes

The following features and themes are deprecated and unsupported in HCL Digital Experience 9.0:
Table 2. Deprecated features and themes
Category Deprecation Recommended action
Setting up a site Running the "Local Content Viewer" portlet (WCM Rendering Portlet) with WSRP The Local Content View portlet has no architectural replacement. Instead, use WCM Rendering portlet locally. The feature allows customers to run the content viewer on a remote portal and integrate it into a local portal. You can run the content viewer only locally.
Administering Frequent Users portlet Login filters can be used to record login activity as needed
Security OpenID authentication
Legacy Portal OpenID TAI (com.ibm.portal.auth.tai.OpenidTAI provided by HCL Digital Experience Portal)
For authentication in HCL Digital Experience Portal with an external Identity Provider use SAML/OpenID Connect TAIs provided by IBM WebSphere Application Server or custom TAIs.
Administering XMLAccess xsds for older releases (HCL Digital Experience Portal 5.0 - 7.0) Use the XML configuration interface with XML input files specified according to the latest schema file: PortalConfig_8.5.0.xsd.
Configuring Web Content Manager Ephox EditLive! Java based Rich Text Editor The Ephox EditLive! Java based Rich Text Editor has been deprecated as of HCL 8.5 CF11 and replaced by Textbox.IO. You can also use the CK Editor as an alternative to Ephox EditLive!
To continue to use Ephox EditLive! in CF11 or higher, run the following command from the wp_profile_root/ConfigEngine directory:
Windows™
ConfigEngine.bat install-editlive-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
UNIX™Linux™
./ConfigEngine.sh install-editlive-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
IBM i
ConfigEngine.sh install-editlive-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
z/OS®
./ConfigEngine.sh install-editlive-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
Note: An administrator user name and password is not required if you already specified the portal administrator user name and password with the PortalAdminId and PortalAdminPwd settings in the wkplc.properties file.

Then, from the web content authoring application, go to the Edit Settings view and add a custom editor with the following value: /wps/ephox;/jsp/html/EditLiveJavaEditor.jsp

If you rollback to CF10 or earlier. you enable Ephox EditLive! by running the following command from the wp_profile_root/ConfigEngine directory:
Windows
ConfigEngine.bat configure-wcm-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
UNIXLinux
./ConfigEngine.sh configure-wcm-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
IBM i
ConfigEngine.sh configure-wcm-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
z/OS
./ConfigEngine.sh configure-wcm-editor -DWasPassword=password -DPortalAdminId=username -DPortalAdminPwd=password
Note: An administrator user name and password is not required if you already specified the portal administrator user name and password with the PortalAdminId and PortalAdminPwd settings in the wkplc.properties file.
Developing Enabler, Builder, and Mashups components and API The Mashup Enabler and the Builder components are deprecated. The Mashups Enabler and the Builder API are deprecated.
Personalization LikeMinds The LikeMinds services and database domains are deprecated.
Go to Active Site Analytics to learn how to configure a variety of analysis tools to support your Digital Experience platform requirements.
Personalization Feedback The Feedback database domains are deprecated.
Go to Active Site Analytics to learn how to configure a variety of analysis tools to support your Digital Experience platform requirements.
Security Active Credentials Active credentials are deprecated from the Credential Vault portlet. Passive credentials are still available.
Administering Shared private pages The Sharing private pages service is deprecated.
Go to Managing Pages for the set of services available in HCL Digital Experience 8.5 and 9 releases.
Administering Parallel Portlet rendering The Parallel Portlet rendering feature is deprecated. See the HCL Digital Experience Performance Tuning Guide for recommendations to optimize digital experience application performance.
Security Stand-alone LDAP user registry The stand-alone LDAP user registry configuration is deprecated. Instead, configure the federated LDAP user registry. If you upgraded from HCL Digital Experience 7.0 or 8.0 with a stand-alone LDAP user registry, you can continue to use your stand-alone LDAP user registry. However, run the wp-modify-federated-security to change to a federated LDAP user registry.
Administering URL mappings URL mappings are deprecated. If you upgrade from HCL Digital Experience 8.0 to 8.5, you can continue to use your existing URL mappings, but creating new URL mappings is no longer supported. Use vanity or friendly URLs.
Installation Full and Base installation options Before HCL Digital Experience 8.5, a customer chose either a full deployment with all the same pages and artifacts or a base deployment to customize their portal. Starting with HCL Digital Experience 8.5, the Configuration Wizard installs the full deployment. Customers can then remove pages to customize their portal. Then, they can package their customizations as a Portal Application Archive (PAA) file. Finally, customers can install their production server, run the empty-portal task, and install the customization PAA file.
Security LTPA version 1 token support The LTPA version 1 token is deprecated. WebSphere Application Server 8.5.5. disables the LTPA version 1 token by default. If you are integrating with third-party applications that rely on LTPA version 1, update the application to support LTPA version 2. If you cannot update the application, you must manually re-enable LTPA version 1 support after you complete the migration. For information on updating your application to support LTPA version 2, see the documentation for the application.