Welcome
Installation
Learn more about HCL Detect installation and deploying core components of the product.
Preinstallation Configurations
Preinstallation Configurations on Application Servers

Getting Started
Welcome to the documentation for HCL Detect, where you can find information about how to install, maintain, and use this service.
Installation
Learn more about HCL Detect installation and deploying core components of the product.
- Installation Overview
  From release 26.1.0, HCL Detect is available for on premises installation.
- Planning the Detect Installation
  When you plan your Detect installation, ensure that you have set up your system correctly, and that you have configured your environment to deal with any failures.
- Preinstallation Configurations
  - Preinstallation Configurations on Application Servers
    - Information for creating JDBC connections
      Use default values when you create JDBC connections if specific values are not provided. For more information, see the application server documentation.
- Installation
  You must run the Unica installer to start the installation of Detect. The Unica installer starts the product installer during the installation process. Make sure that the Unica installer and the product installer are saved at the same location.
- Post Installation Configurations
  After you install Detect, complete post-installation updates for runtime components and configuration files.
- Run End-to-End Ingestion Validation
  Validate the complete data path from event ingestion to pipeline execution and destination delivery.
- Disable or Uninstall
  You can choose to disable Detect or uninstall it.
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
Working with the System
The section provides comprehensive instructions for creating, configuring, and managing marketing events. It covers topics such as defining audience conditions, setting up triggers, deploying events, and tracking their performance. Additionally, this section includes explanations of key terminology and offers advanced options to optimize event management.
System Data Model
This section provides detailed information about the internal tables used within the Detect module. It includes descriptions of each table's structure, purpose, and relationships, aiding administrators and developers in understanding and managing the underlying database schema effectively.

Preinstallation Configurations on Application Servers

Configuring the web application server for your JDBC driver

The web application server where you plan to deploy Detect must contain the correct JAR file to support JDBC connections. This enables your web application to connect to the system tables. The location of the JAR file must be included in the class path of the web application server.

Creating JDBC Connections in the Web Application Server

The Detect web application uses JDBC connections to communicate with the system table database and with the Unica Platform. In the supported Tomcat flow, the installer creates detect.xml when datasource creation is selected.

About this task

When prompted during installation, provide the Tomcat application server installation directory so the installer can create datasource configuration under <Tomcat_Home>/conf/Catalina/localhost.

Important: For the connection to the database holding the Unica Platform system tables, you must use UnicaPlatformDS as the JNDI name.

If you expect to have many concurrent users in Detect, you may need to increase the number of connections in your web server. For best results, set your web server to allow 50 connections.