Welcome
Extending Platform
This section guides developers on customizing and extending Detect solutions. It covers the solution's folder structure, configuration files, integration methods, and provides insights into the Detect Expression Language and its built-in functions.
drive.json File
This page explains the structure and purpose of the drive.json file used in HCL Detect. It outlines required configurations including database settings, user profiles, communication parameters, system health metrics, and other operational settings. Proper setup of this file is essential before launching the application.
Tomcat Configuration
This page provides details on configuring Tomcat settings, including host name, port numbers, startup timeout, and certificate options for HCL Detect.

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.
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 Platform
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.
Extending Platform
This section guides developers on customizing and extending Detect solutions. It covers the solution's folder structure, configuration files, integration methods, and provides insights into the Detect Expression Language and its built-in functions.
- Folder Structure
  This section provides an overview of the basic solution folder structure. It describes the contents of each folder and their purpose.
- drive.json File
  This page explains the structure and purpose of the drive.json file used in HCL Detect. It outlines required configurations including database settings, user profiles, communication parameters, system health metrics, and other operational settings. Proper setup of this file is essential before launching the application.
  - Audience Criteria
    This section explains about configuring the parameters like timeouts, query limit, bucket size for chart, and reporting options for audience criteria.
  - Campaign Actuator
    This section allows configuring the core components of the Campaign Actuator, including data ingestion from multiple feeds, data processing based on triggers, event execution aligned with contact policies.
  - Feed Applications
    This section allows configuring feed applications and their corresponding parameters to establish data input sources.
  - Tomcat Configuration
    This page provides details on configuring Tomcat settings, including host name, port numbers, startup timeout, and certificate options for HCL Detect.
- Configurations
- Integrations
- Solution Source Code
  This page outlines the structure and components of a solution source in HCL Detect. It details how solutions are packaged, including profiles, feed models, applications, and configurations, enabling deployment and reuse across different environments.
- Detect Expression Language
- Detect Expression Language Built-in Functions
Platform 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.
PDF

Tomcat Configuration

This page provides details on configuring Tomcat settings, including host name, port numbers, startup timeout, and certificate options for HCL Detect.

Configure tomcat host name, port number, startup timeout, and signed certificate details.

 "tomcatConfiguration": {
            "hostname": "{hostname}",
            "httpsEnabled": true,
            "port": 8443,
            "shutdownPort": 8009,
            "startupTimeoutInSeconds": 120,
            "usingSelfSignedCertificate": true
        }

port: set the default tomcat port number.

shutdownPort: set the tomcat shutdown port number.

startupTimeoutInSeconds: specify the maximum allowable time in seconds for Tomcat to startup.

usingSelfSignedCertificate: set true to use the self signed certificate for Tomcat.