Configuring Kafka Details for Feed Applications

About this task

Note:
This feature will be available starting with version 26.1.0.IF02
Kafka configuration is a critical step in setting up a feed application. You must provide the correct Kafka cluster information, bootstrap servers, topic, and group ID to ensure successful data ingestion.

Detect uses the optional Affinium|suite|kafkaTopicPrefix and Affinium|suite|kafkaTopicConsumerGroupPrefix settings in Unica Platform. When configured, Detect adds the topic prefix to the feed topic name and the consumer group prefix to the Group ID when connecting to Kafka. You can configure either prefix or both. For configuring Kafka topic prefix values, see "Configuring Kafka Topic Consumer Group Prefix " in the Unica Platform Administrator's Guide.

Procedure

  1. In the feed application creation wizard, locate the Kafka Details section under Step 1: Configuration.
  2. Select the Kafka cluster from the Select Kafka Cluster drop-down menu.
    The system displays available Kafka clusters configured in your Detect environment. If no clusters are available, contact your system administrator.
  3. Enter the Kafka Topic name.
    1. In the Topic field, enter the topic name without the Unica Platform topic prefix (e.g., RECHARGE, transactions).
    2. Ensure the resulting prefixed topic exists on the Kafka broker. For example, if the topic prefix is DEV_, enter transactions for the broker topic DEV_transactions. Kafka topic names are case-sensitive.
    Important:
    Use a dedicated Kafka topic for each feed application. Do not configure multiple feed applications to consume from the same topic, as this can cause configuration and processing conflicts.
  4. Enter the Kafka Group ID for the consumer group.
    1. In the Group ID field, enter the consumer group name without the Unica Platform consumer group prefix (e.g., detect-feed-consumer-group).
    2. The Unica Platform consumer group prefix is added to this value to form the consumer group ID used on the Kafka broker. For example, if the consumer group prefix is DEV_, enter detect-feed-consumer-group for the broker consumer group DEV_detect-feed-consumer-group. Kafka consumer group IDs are case-sensitive.
    3. Kafka uses the Group ID to track message consumption and manage consumer group offsets. Use a unique, descriptive Group ID for each feed application so it doesn't conflict with other consumers.
  5. Click Validate Kafka Accessibility to verify the connection.
    The system tests connectivity to the Kafka cluster. A success message indicates the configuration is correct. If validation fails, verify your Kafka cluster address, topic name, and network connectivity.

Results

Kafka configuration is complete and validated. You can now proceed to configure attribute mappings.