Skip to content

What's new in CF225

The following features and updates are available to customers installing HCL Digital Experience (DX) Compose Container Update CF225 on supported platforms:

Upgrade steps using Helm now available

Documentation on how to upgrade the configuration of an HCL DX Compose 9.5 CF224 or later deployment using Helm is now available. For more information, see Upgrading Helm deployment.

Custom PVCs now supported

Starting with CF225, you can configure additional Persistent Volume Claims (PVCs) for the WebEngine stateful set. You can also specify the directories where they will be be mounted in the main containers of all WebEngine pods. For more information, see Configuring additional WebEngine persistent volumes.

Documentation for changing the WebEngine URI

Instructions for changing the default WebEngine Uniform Resource Identifier (URI) after installing HCL DX Compose are now available. For more information, see Changing the WebEngine context root or home URI.

Using DDC for integration

You can use the Digital Data Connector (DDC) for the HCL DX Compose framework to integrate data from external data sources to your DX Compose pages. Documentation for integrating HCL Volt MX Foundry to DX Compose using DDC is now available. For more information, see Integrating DDC in DX Compose and Connecting to HCL Volt MX Foundry through DDC.

User session tracking and reporting

You can configure user session tracking, view DX Compose 9.5 user session consumption, and manually export a report of the number of sessions used in specified time periods. Note that user session tracking and reporting support the protection of the Personally Identifiable Information (PII) of users. Data such as the User ID and the IP Address are not stored in the server logs or presented in user session usage reports. For more information, see Tracking user session consumption and exporting usage reports.

OIDC authentication in DX Compose

You can configure DX Compose to use an OpenID Connect (OIDC) identity provider. In this scenario, users can log in to the OIDC identity provider and not DX Compose. Note that currently, users authenticated to DX Compose must reside in the DX Compose user registry, generally an LDAP server. For more information, see Configuring DX Compose to use an OIDC identity provider.

Initial DX Compose performance tuning

Documentation for tuning the initial DX Compose performance is now available. The guide identifies the Helm charts that provide initial tuning for various WebEngine production scenarios. You can also find the Helm command used to update those WebEngine environments. Note that you can only determine the optimal settings for DX Compose after any changes or additions are complete. For more information, see Tuning the initial DX Compose performance.

Adjustment of seedlists for access control changes

A new option is available where you can have the seedlist return items affected by library access control changes. To enable this feature, set seedlistUpdateLibrariesForAccessControl=true in ConfigService.properties. For information on how to update or add properties in ConfigService.properties using Helm, see Updating DX Compose WebEngine properties using Helm values. For more information on the seedlistUpdateLibrariesForAccessControl property, refer to Crawling web content with search seedlists.

DXClient - LiveSync enabled for Presentation Templates

LiveSync now supports Presentation Templates. For more information, see DXClient and LiveSync.

Search V2 - Styling customizations

You can customize Search V2 by providing custom CSS modules. For more information, see Customizations for Search V2.

Custom liveness probe target value

In previous releases, the liveness probe target values are fixed because they are specific to the application and should not be changed. Starting CF225, Core provides a customProbeURL value that allows you to configure the liveness probe target value. If the customProbeURL is empty, the liveness probe target value for Core is "/ibm/console" by default. For more information, see Probes configuration in values.yaml file.