Configuring CDM Tenants and Connections

Enable Customer Data Model (CDM) support for a tenant, and configure database connections, data sources, cloud storage endpoints, and ingestion pipelines in the HCL Customer Data Platform (CDP) Administration Console.

The CDM Configuration interface enables administrators to integrate enterprise data warehouse schemas, historical event logs, demographic views, and profile pipelines into HCL CDP. Configuring these settings allows downstream CDP services, including segment builders and profile lookups, to query underlying transactional and relational data stores directly.

What the CDM Tenant Option Enables

Selecting CDM Tenant enables CDM-related capabilities for the tenant. After you configure and save the CDM connections and data sources, users can access mapped CDM data through the following features:

  • Profile Properties: Map profile attributes to CDM profile columns. See Adding custom profile properties in HCL CDP User Guide.
  • Additional Properties: Register attributes from CDM tables and views for use in segmentation. See -Managing additional properties in HCL CDP User Guide.
  • Custom Events: Configure the CDM-related event property fields. See Managing custom events in HCL CDP User Guide.

Enable this option and complete the tenant configuration before users set up CDM-backed properties or custom event fields.

Prerequisites

Before configuring CDM tenant settings, ensure you have:

  • Administrator access to the HCL CDP Administration Console.
  • The target database connection string (JDBC URL), valid credentials, and driver class name.
  • AWS Athena schemas, catalogs, and Amazon S3 export and publish bucket names.
  • Target database names, catalogs, and table or view names for profile, demographic, event, conversion, and transaction data.

Procedure

To enable and configure CDM for a tenant, follow the steps below:

  1. Sign in to the HCL CDP Administration Console with administrator credentials.
  2. From the main navigation menu, go to List of Clients. Search for Tenant and click EDIT.
  3. Select the CDM Tenant checkbox to enable Profile Properties, Additional Properties, and CDM-related event fields in Custom Events for the tenant.
  4. Complete the configurations in the four sections described below.

Step 1: Configure Database Connection

Expand the 1. Database Connection section, and specify the database connectivity parameters:

Field Description
JDBC URL Enter the full JDBC connection string (for example, jdbc:oracle:thin:@//<host>:<port>/<service_or_sid>).
Username Enter the database user account name.
Password Enter the database password.
Driver Class Enter the fully qualified Java class name of the database driver (for example, oracle.jdbc.OracleDriver).
Export Type Select the target export mechanism from the list (for example, S3).

Step 2: Configure Data Sources and Table Mappings

Expand the 2. Data Sources section to map relational datasets, such as Event, History, Conversion, Demographic, and Transaction.

To add a new data source group, select + ADD DATA SOURCE. For each data source block, specify the following details:

Field Description Example Values
Data Source The internal identifier for the data source. Event, History, Conversion, Demographic, Transaction
Database The target database name containing the source tables. segmentdb_6676, cdm_publish_db
Catalog The data catalog name. iceberg, oracle_enterprice
Display Name The user-friendly label displayed in the CDP UI. Event, History, Conversion, Demographic, Transaction

Under each data source block, define the associated tables:

  • Type: Enter the table mapping category (for example, other, __fixed__, or cdmprofiles).
  • Table Names (comma separated): Enter one or more comma-separated table or view names (for example, vw_contacthistory, vw_responsehistory, vw_fact_conversion, vw_profile, or fact_transactions).

Select + ADD TABLE MAPPING to associate additional table types and names with the current data source. To remove a table mapping or data source, select the Delete (trash can) icon.

Step 3: Configure CDM and Athena Endpoints

Expand the 3. CDM Configuration section to establish query catalog metadata and cloud storage bucket locations:

Field Description Example Value
Athena Schema The schema used by Amazon Athena. profile_db
Athena Catalog The catalog engine used by Athena. data_iceberg
Export Bucket The Amazon S3 bucket name designated for data exports. s3-export
Publish Bucket The Amazon S3 bucket name designated for published data sets. s3-export
CDM Publish Schema The published schema location for CDM data. profile_db
CDM Catalog The published catalog name for CDM data. oracle_db
Athena Database The database name referenced by Athena queries. segmentdb_tenant
Note:
If additional custom parameters are required, select + ADD FIELD.

Step 4: Configure Profile Pipeline

Expand the 4. Profile Pipeline Configuration section to define the ingestion and ID resolution targets.

Under Profile, configure the base profile storage details:

  • Database Name: Enter the database where profile data is ingested (for example, cdm_ingest_db).
  • Attribute Table Name: Enter the profile view or table name (for example, vw_profile).

Under ID Mapping, configure identity resolution settings:

  • Database Name: Enter the database storing identity mappings (for example, cdm_ingest_db).
  • Attribute Table Name: Enter the identity mapping table name (for example, id_mapping).
  • Upsert Columns (comma separated): Enter the key columns used for record deduplication and upserts (for example, old_id).

Select UPDATE to persist the tenant configurations.

Verification

To verify that the CDM tenant configuration is active:

  1. Navigate to Segmentation > Segments.
  2. Select Create Segment.
  3. In the segmentation canvas attribute browser, verify that the configured data sources (Demographic, Transaction, History, Conversion) and their respective columns appear in the attribute hierarchy.
  4. Confirm that Profile Properties and Additional Properties are available, and that the CDM-related fields appear when adding a custom event property.