Configuring HCL MX Foundry for integration with HCL Digital Experience

Configuring Ingress for HCL Digital Experience and HCL MX Foundry

You can use an optional Ingress with HCL Digital Experience. While an Ingress is not required to run HCL Digital Experience, it can be configured to be reused by HCL MX Foundry to handle the routing for both products and make them available on the same host.

1. Set up the Ingress for HCL Digital Experience. For more information, refer to the optional Ingress documentation.

2. Configure HCL MX Foundry to use the existing Ingress controller. The following sample values for HCL MX Foundry configure the Ingress to use an SSL connection using the provided custom certificates.

   • The certificate in customCert must match the certificate used for the Ingress configuration of HCL Digital Experience. The cer and key file must be located in the apps/certs directory of the MX Helm chart.
   • The class in this configuration refers to the class name of the deployed Ingress controller.

   • The serverDomainName must match the hostname that the Ingress is available at:

     ingress:
       enabled: true
       protocol: "https"
       port: "443"
       class: "nginx"
       tls:
         enabled: true
         customCert:
           cert: "certs/your-ssl-cert.cer"
           key: "certs/your-ssl-cert.key"
     serverDomainName: "your-mx-and-dx-host.com"
     

   Refer to the HCL MX Foundry Configuration documentation for more details on the used values.

After applying the configuration, both HCL Digital Experience and HCL MX Foundry can be accessed using the provided hostname.