Using Kafka Event Logger with History Node

You can use Apache Kafka as a transport for Interaction Server reporting events. It is especially useful if you plan to use Interaction Server Kafka Capture Point, allowing you not to install a separate JMS broker. The same Kafka installation can be used as a transport both for Capture Point and Event Logger needs.

Prerequisites

Configure Interaction Server Kafka Event Logger as described in the Using the Groovy Event Logger with Apache Kafka topic in the eServices Administration Guide.

Configure Kafka Event Logger Application Object

For the Kafka Event Logger application object created on the previous step set the following mandatory options on the Application Options tab:

1. [consumer-options]\auto.offset.reset = earliest
2. [consumer-options]\max.poll.records = 1000
3. [consumer-options]\poll-delay = 100

Important

max.poll.records and poll-delay values can be tuned for better performance depending on your environment and the size of interaction user data. Please change these values only if you understand what and why you are doing.

Consumer Options Description

consumer-options \ poll-delay - the maximum time in milliseconds to block consumer when it polls for records.

All other options are standard Kafka consumer options and can be found in the official Kafka documentation

Important Option iWD \ batch-size is not taken into account when Kafka Event Logger is used. Use option consumer-options \ max.poll.records instead.

Configure iWD History Node Application Object Set Application Options > iWD \ event-logger-mode = kafka Add Kafka Event Logger application object to the iWD History Node connections on the Connections tab.