Product Overview
Customer Experience is now the number one differentiator in decision making when transacting online. It is crucial that you are able to monitor, understand and manage those online experiences using quantitative data and insights from your actual customer sessions.
Release Notes
Installation, Deployment, and Upgrade
Installing HCL Discover involves planning and preparing your environment, installing and configuring prerequisite software, obtaining the HCL Discover installation files, and running the HCL Discover installer.
Configuration
Configuring HCL Discover involves setting up and managing Discover user authorization and configuring Discover server components and services that process captured data.
Administration
Administering HCL Discover involves configuring and integrating the HCL Discover client framework with your web applications or mobile native applications, installing and administering the databases used by HCL Discover, defining event objects and configuring events, hit attributes, dimensions, and other object attributes used by HCL Discover to monitor mission-critical metrics of your web application's performance.
Cloud-native HCL Discover
- Cloud Native HCL Discover
  - An Introduction to Docker, Kubernetes, and Helm
    We have implemented HCL Discover using Docker, Kubernetes, and Helm.
  - ELK Overview
    The ELK Stack is a collection of three open-source products: Elasticsearch, Logstash, and Kibana.
  - Cloud Native Discover support matrix
    Before installation or upgrade, please ensure that the systems meet the recommended requirements.
  - Configuring Ingress Controller
    You can use your own ingress controller along with the corresponding ingress YAML definitions to expose services.
  - Installation, Configuration, and Deployment of Docker
    - Database Prerequisites
      HCL Discover supports the following database applications:
    - Database
      For database you can configure database in either of the following ways:
    - Configuring the configMap.yaml File for Database Parameters
      Based on the configuration chosen in DC/Docker/database.html, change the value of the following parameters in the configMap.yaml file:
    - Data Persistence for Databases
      The Kubernetes cluster will persist the data from the docker database.
    - Configuring the configMap.yaml File for Discover parameters
      Change the value of the following parameters in the configMap.yaml file:
    - Log Files
      When all the desired containers are up and running, it is considered as a best practice to check the logs for all the running services.
    - Installation and Deployment
      To install and deploy HCL Discover, you have to run just one command:
    - Deleting the Deployment
      To delete the deployment, run the following command:
  - Monitoring Deployment
    You can monitor the deployments using the Kubernetes Dashboard. The Kubernetes Dashboard is a web-based user interface. You can use the Dashboard to deploy containerized applications to a Kubernetes cluster, troubleshoot your containerized application, and manage the cluster resources.
  - Windows Support for your Amazon EKS Cluster
    If you use Amazon Web Services EKS, you cannot use Windows-managed nodes.
  - AWS cloud-specific changes in Helm chart
  - Before you contact HCL technical support
    If you encounter a problem that you cannot resolve by referring the documentation, your company's designated support contact can log a call with HCL technical support. Use these guidelines to ensure that your problem is resolved efficiently and successfully.
Notices

Configuring the configMap.yaml File for Discover parameters

Change the value of the following parameters in the configMap.yaml file:


Parameter name	Example Values
`TARGETPASS`	`C:\\Discover`
`PORTALSERVER`	`discover-portal`
`MDF_PATH`	`/mssql-data`
`TMSSERVER`	`discover-portal`
`EXPORTSERVER`	`discover-export`
`ELKSERVER`	`discover-hcl-discover-elk`
`MAILSERVER`	`discover-portal`
`REPORTSERVER`	`discover-portal`
`PROCESSING_SERVER`	`processor-0.processor.{{ .Release.Namespace }}.svc.cluster.local`
`HBRSERVER`	`hbr-0.hbr.{{.Release.Namespace }}.svc.cluster.local`
`REPLAYSERVER`	`replay-0.replay.{{.Release.Namespace }}.svc.cluster.local`
`NAMESPACE`	`{{ .Release.Namespace }}`
`PACKET_FORWARDER_HOSTNAME`	`{{ .Release.Name }}-hcl-discover-packet-fwdr`
`PACKET_FORWARDER_PORT`	`{{ .Values.service.port.packetforwarder }}`
`DNCA_HOSTNAME`	`{{ .Release.Name }}-hcl-discover-dnca`
`UI_POST_PORT`	`{{ .Values.service.port.uipost }}`
`ELK_ENABLED`	`false`
`PROCESSOR`	`processor`
`HBR`	`hbr`
`REPLAY`	`replay`
`CONTEXT`	`{{ .Values.global.sofySandboxContext }}`
`CANISTERDIR`	`""`
`DELAY`	`100`
`SPOOLDIR`	`""`
`DATACOLLECTOR`	`""`
`FORCETOREMOVE`	`""`
`REMOVEDATABASE`	`""`
`SOURCEFILEPATH`	`""`
`TRACKINGHOST`	`""`
`TRACKINGPORT`	`""`
`TRACKINGSERVICECONFIGURE`	`""`
`DBUPGRADEOPTION`	`""`
`PRIMARY_INTERFACE`	`eth0`
`DNCA_PORT`	`8080`
`HOSTNAME`	`https://discover-portal.{{ .Values.global.domain }}` Set the parameter as per the requirement of your environment. This parameter defines the public hostname of the Discover portal and is used internally for redirect and callback URL resolution.

Okta Authentication Configuration

You can use Okta as an authentication method for login. By default, Okta integration is disabled. To enable and configure Okta authentication, set the following parameters in the configmap.yaml file based on the requirements of your environment:

Note: Ensure that all values match the configuration of your Okta application.


Parameter name	Example Values
`OKTA_ENABLED`	`true`. Set to `true` to enable Okta authentication.
`OKTADOMAIN`	`https://<your-okta-domain>` The Okta domain URL.
`OKTASERVERID`	`default` The Okta authorization server ID
`OKTACLIENTID`	`<your-okta-client-id>` The Okta application client ID
`OKTACLIENTSECRET`	`<your-okta-client-secret>` The Okta application client secret.
`OKTAREDIRECTURI`	`https://<your-app-url>/callback` Redirect URI configured in Okta.
`OKTAPOSTLOGOUTURI`	`https://<your-app-url>/logout` Post-logout redirect URI