Containerization Limitations/Requirements

This section describes the limitations and requirements for deploying HCL Digital Experience 9.5 on container platforms.

  • HCL Digital Experience 9.5 is supported on Docker, Red Hat OpenShift, and Amazon Elastic Kubernetes Service (EKS).
    • Other Kubernetes platforms are not fully supported. The HCL Operator is not likely to work, however, support for additional Kubernetes as a service (KaaS) is ongoing.
    • Additional features and functions may be tied to the use of the HCL Operator for deployment.
    • HCL highly recommends following the deployment strategies outlined within this documentation. HCL Digital Experience 9.5 containerization is focused on deployment and it uses an operator-based deployment. The goals are:
      • (a) to introduce a supported containerized deployment that HCL can continually extend,
      • (b) to provide customers with the best possible experience; and
      • (c) to provide a high level of customization in the deployment and continue to expand on that, along with increased automation.
      Customers need to follow the recommended deployment model to ensure the availability of future functions and prevent potential conflicts.
  • Supported platforms
    • HCL Digital Experience 9.5 container release is verified and supported on:
      • 1. Red Hat OpenShift 4.1
      • 2. Red Hat OpenShift 4.2
    • HCL Digital Experience 95_CF171 container release is verified and supported on:
      • 1. Red Hat OpenShift 4.1
      • 2. Red Hat OpenShift 4.2
      • 3. Native Kubernetes verified on Amazon EKS 1.14
  • Supported databases
    • Oracle Database
    • IBM DB2
    • Microsoft SQL Server
    • Apache Derby
      Note: HCL Digital Experience is a database-intensive application, it is not recommended to use Apache Derby for production use. For specific versions of these databases, see Detailed system requirements.
  • Supported file system
    • Requires an AccessMode of ReadWriteMany.
    • Requires a minimum of 40 GB, with the default request set to 100 GB.
    Note: HCL Digital Experience is input-output (I/O) intensive and requires a high performing file system for optimization.
  • ConfigEngine and ConfigWizard should only be used when there is a single instance

    When more than one instance is running, the ConfigEngine is disabled and the ConfigWizard route is removed. As an example, the Site Builder is calling the ConfigEngine in the background. But because multiple instances are running, an Error 500 occurs because the ConfigEngine is disabled. All ConfigEngine.sh tasks should be run in configure mode with only one instance running.

  • JavaServer Faces (JSF) portlet bridge

    With DX 9.5 CF_171 and later, WebSphere Application Server 9.0.5.2 is included and that fix pack removed the IBM JSF portlet bridge. If you are using JSF portlets and leverage the JSF portlet bridge, we recommend to wait until HCL releases the DX container with the HCL JSF portlet bridge before moving to a container-based deployment.