Segment Central | partitions | partition[n] | Content Integration | dataSources | Segment Central
Provide values for the optional/mandatory fields:
systemIdentifier
- Value
- SegmentCentralNote: If it is multi partition Unica environment, then the system identifier should be:
- For partition 1 - SegmentCentral SCP1
- For partition 2 - SegmentCentral SCP2
- For partition 3 - SegmentCentral SCP3 and so on.
userCredentials
- Value
- Logged-in user
defaultUserCredentials
- Value
- Blank
dataSourceNameForCredentials
- Value
- Blank
anonymousContentAccess
- Value
- Yes
additionalParameters
- Value
-
audience-event-interpreter.kafka.max-consumers: <max-consumers_num> audience-event-interpreter.kafka.max-poll-records: <max-poll-records_num> audience-event-interpreter.kafka.fetch.max.wait.ms: <max.wait.ms.value> audience-event-interpreter.kafka.topics: SC_CIF_INTEGRATION audience-event-interpreter.kafka.topics.SC_CIF_INTEGRATION.format: Json audience-event-interpreter.kafka.fetch.min.bytes: 8388608 audience-event-interpreter.kafka.fetch.max.bytes: 8388608 audience-event-interpreter.kafka.max.partition.fetch.bytes: 8388608
For more information, see Unica Content Integration Installation and Configuration
Guide
Note:
- If your setup has Docker provided configurations, in the Configurations panel access, for the additionalParameters field, the multiple parameters are separated by a space. To use the configurations provided by Docker, edit the configuration and for the additionalParameters field ensure that all parameters are separated by a new line.
- Use separate Kafka topic for each partition.Example: For partition 1
audience-event-interpreter.kafka.topics: SC_CIF_INTEGRATION_P1 audience-event-interpreter.kafka.topics.SC_CIF_INTEGRATION_P1.format: Json
Example: For partition 2audience-event-interpreter.kafka.topics: SC_CIF_INTEGRATION_P2 audience-event-interpreter.kafka.topics.SC_CIF_INTEGRATION_P2.format: Json
and so on.
- For SASL connectivity with Kafka, provide READ authorization to consumer
groups. A separate consumer group is created for each Segment Central
node configured in each partition. The Kafka consumer group name follows
the format shown below and is then converted into a lowercase
string:
ci-consumer-segmentcentral-{partition-name}-{system-id}-audience-event-interpreter
where
- {partition-name} is replaced with respective partition name.
- {system-id} is replaced with the System Identifier property value mentioned earlier.
Any space in system identifier is replaced with a hyphen (-) for composing the consumer group.
The following is an example of a consumer group name for the SegmentCentral SCP1 system identifier configured in partition1:
consumer-ci-consumer-segmentcentral-partition1-segmentcentral-scp1-audience-event-interpreter