DX Compose limitations

Know the existing limitations of Digital Experience (DX) Compose.

Deployment

You cannot deploy the Core container used in the DX offerings deployment and the DX Compose WebEngine Core container together on the same deployment.
The only supported databases are DB2 and Derby.
It is not possible to use the Remote Search service provided with HCL DX offerings in DX Compose. DX Compose provides support for OpenSearch.
No ReadWriteMany (RWX) shared volume is used.
Portal Application Archive (PAA) deployment is not supported.

DX Compose does not operate on the IBM WebSphere Application Server (WAS). DX Compose administrators should use the Helm chart to make changes they used to perform in the WebSphere Application Server Admin Console. The Open Liberty Admin Console has limited functionality but can be leveraged for starting/stopping applications, investigating the configuration, and monitoring.
Open Liberty does not provide wsadmin scripting.
Configuration in resource environment providers, which was earlier managed with the DX Offerings WAS console, is managed with Helm charts in DX Compose.
There is no ConfigEngine or Configuration Wizard with DX Compose. All configuration must be done through the Helm chart.
A limited set of dxclient commands is supported. DXClient Limitations

You cannot deploy Java-based applications such as portlets, EAR-based themes, and WCM extensions.
Social Media Publisher, Content Template Catalog (CTC), and other WCM extensions are not supported except Multilingual Solution.
Digital Data Connector is not supported.
WCM AI Sentiment Analysis in the WCM Authoring user interface (UI) is not supported with the TinyMCE Rich text editor but is supported with CKEditor.

Creating, updating, and deleting users and groups using the DX Compose Admin UI, REST APIs, or scripting tools are not supported with this initial release.
Lookaside database, application groups, custom user registries, and transient users are not supported.