Welcome
Installation
Learn more about HCL Detect installation and deploying core components of the product.
Post Installation Configurations
After you install Detect, complete post-installation updates for runtime components and configuration files.
Post Installation Configurations on Unica

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
- 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.
  - Post Installation Configurations on Application Servers
    After installing HCL Detect, complete the required Apache Tomcat updates.
  - Post Installation Configurations on Unica
  - Other Post Installation Configurations
  - Validate Kafka and Datasource Configuration
    Validate messaging and datasource configuration required for functional verification of Detect.
  - Setting up a master profile
    Setting up a master profile is a prerequisite for creating profile entities through the CLI or Swagger REST API. This process involves identifying the profile database and configuring the datasource within the Unica Platform.
  - Initialize Profile and Feed Metadata
    Create baseline profile and feed metadata by using supported Detect CLI commands.
- 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.

Post Installation Configurations on Unica

Granting the `asm_admin` user access to HCL Detect

The default admin user (asm_admin) can access HCL Detect configuration properties automatically. However, there are no default users with access to the HCL Detect application until you configure them.

About this task

Complete the following steps to grant the admin user access to HCL Detect:

Procedure

Select Settings > User groups > New Group, and enter group name and description.
Assign users and roles such DetectAdmin, to the created group.
Log back in using the user credentials.
Verify that you have access to HCL Detect features.
For more information about assigning user roles and permissions, refer Unica Platform Adminstrator Guide.

Setting up System Users

To administer security across all users of Unica Platform, a user account must exist that has access to all security settings and user accounts in the system.

About this task

By default, this user account is platform_admin. This user account does not belong to any one partition; instead, it has access to all user accounts in all partitions.

The administrator can create additional users with the same level of access. To be a partition superuser, an account must have Admin access to the Unica Platform and have full access to the Users, User Groups, and User Permissions pages.

Procedure

On Linux™, for the Alternate Login attribute of the system user, enter the Linux™ name for a user in a group that shares privileges with the Linux™ users of Detect.