Home
Administrator Guides
Administrator Guide
Unica Campaign integration with Kafka
Campaign|partitions|partition[n]|Kafka| Campaign
This category contains properties to configure the kafka used in Campaign for the selected partition.

Administrator Guides
- Administrator Guide
  - Unica Campaign administration overview
    The Settings menu provides access to most of the tasks that Unica Campaign administrators typically perform.
  - Security in Unica Campaign
    Security policies control user access to the objects and features in Unica Campaign.
  - Database table administration
    Unica Campaign administrators must perform initial one-time tasks and routine administration tasks that pertain to database tables.
  - Customizing campaigns
    Administrators can customize campaigns by using custom campaign attributes, initiatives, and products.
  - Offer template concepts
    Before administrators perform offer template management tasks, there are several important concepts to understand.
  - About audience level administration
    Unica Campaign is delivered with a single audience level called Customer. You can define any additional audience levels that you need. Audience levels let flowchart designers target specific groups, such as Households, in marketing campaigns.
  - Before you begin working with contact history
    Contact history is stored in the Unica Campaign system database in separate tables by audience level. Therefore, you need to set up audience levels before you begin working with contact history.
  - Response history administration
    Before you begin working with response history, you should read the audience level administration topics and set up required audience levels.
  - Monitoring and controlling flowchart runs
    Choose Campaign > Monitoring and use the All monitored runs page to view the status of all active flowcharts and suspend, resume, or stop flowchart runs.
  - Dimension hierarchy concepts
    A dimension hierarchy is a data construct that groups data into bins based on value ranges. Dimension hierarchies are the basis for a variety of reports.
  - Triggers administration
    Unica Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
  - Unica Campaign log files
    Unica Campaign records information in several different log files.
  - JVM Parameters
  - About codes in Unica Campaign
    Each campaign, cell, offer, and treatment in Unica Campaign has an identifying code that is generated by code generators, and conforms to a specified format.
  - Accessing the Advanced settings
    When a flowchart is open for editing, administrators can choose the Advanced settings option on the Admin menu to make administrative changes that affect only the current flowchart.
  - Unica Campaign integration with other products
    Unica Campaign optionally integrates with a number of other products.
  - Unica Campaign integration with Kafka
    - Campaign|partitions|partition[n]|Kafka| Campaign
      This category contains properties to configure the kafka used in Campaign for the selected partition.
  - Unica Campaign listeners
    The listener is a key component of Unica Campaign. It provides an interface between front-end clients and back-end analytical server processes.
  - Unica Campaign utilities
    Administrators use the Unica Campaign utilities to manage listeners, sessions, and flowcharts, and perform other important administrative tasks.
  - Configuring the ACOOptAdmin tool
    Configure the ACOOptAdmin tool to run Unica Optimize sessions from the command line.
  - Non-ASCII data in Unica Campaign
    Unica Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the application.
  - Configuration properties for Unica Campaign
    The configuration properties of Unica Campaign are located at SettingsConfiguration. For more details on the configuration properties, see the Campaign Administrator Guide.
  - About special characters
    Some special characters are not supported in any Unica Campaign object names. In addition, some objects have specific naming restrictions.
  - Introduction to character encodings
    This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Unica Campaign.
  - About Unica Campaign Error Codes
    Unica Campaign notifies users of error events when they occur with error messages that consist of a code number and error text.
  - Troubleshooting
- System Tables

Campaign|partitions|partition[n]|Kafka| Campaign

This category contains properties to configure the kafka used in Campaign for the selected partition.

KafkaBrokerURL

Description: Kafka server being used with Journeys application. Example is IP-0A862D46:9092

SaslMechanism

Description

SASL mechanism used for client connections.

Possible values:: PLAIN: This is default value, Use this if client connection is without Kerberos authentication.; GSSAPI: Use this if client connection is with Kerberos authentication.

CommunicationMechanism

Description

Specify the connection mechanism to connect to Kafka server.

Possible Values:: SASL_PLAINTEXT_SSL - Use this to connect to kafka with username/ password and SSL enabled.; NO_SASL_PLAINTEXT_SSL - Use this to connect kafka with no authentication and no SSL.; SASL_PLAINTEXT - Use this to connect kafka with username and password only.; SSL - Use this to connect kafka without username/password but with SSL.

Default value:: NO_SASL_PLAINTEXT_SSL

KafkaKeyFile

Description: Specify the client key file if connection mechanism is using SSL.; Example: /opt/Unica/Kafkakeys/client_key.pem

KafkaCertificateFile

Description: Specify the certificate file if connection mechanism is using SSL.; Example: / opt/Unica/Kafkakeys/client_cert.pem

CertificateAuthorityFile

Description: It is signed certificate of Kafka Server, it is required when connection mechanism is using SSL.; Example - /opt/Unica/Kafkakeys/ca-cert

UserForKafkaDataSource

Description: Marketing Platform user contains the datasource credentials for Kafka while connecting with username / password

KafkaDataSource

Description: DataSource containing the kafka user credentials.

TopicName

Description

Journeys designated topic for Campaign to push data to Journey.

Default value:: STREAMING_IMPORT
Note: Please do not change this as it would send data to Kafka topic which is not being used in Campaign.

NumberOfPartitions

Description: Number of partitions supports Kafka to hold user exported data.

NumberOfReplicas

Description: Each partition is replicated across a configurable number of servers for fault tolerance.

RetentionPeriodInSeconds

Description: The maximum time Kafka will retain messages exported over topic. Once reten¬tion period over Kafka clears all eligible exported messages.

SslKeyPasswordDataSource

Description: If KafkaKeyFile is password protected, then please create a separated data source which will include that password. User name is not used so can be anything. Mention that data source name as value of this field.

SaslKerberosServiceName

Description: When using GSSAPI i.e., Kerberos authentication, configure a service name that matches the primary name of the Brokers configured in the Broker JAAS file.; Example is: kafka

SaslKerberosKeytabPath

Description: When using GSSAPI i.e., Kerberos authentication, set path of the keytab file created for kafka client.

SaslKerberosPrincipal

Description: When using GSSAPI i.e., Kerberos authentication, set Kerberos principal created for kafka client.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.