Important note: Our Kafka support is in beta version.

Introduction: Phase 1.

images/download/attachments/44941510/input_agent_kafka_EN-version-1-modificationdate-1580779710461-api-v2.png

(1) Only relevant for the add-on module Load Balancing to start the profile on a specific node.

(2) The Kafka alias. See section Kafka Connections.

(3) The topic from which messages are to be received.

(4) The data type of the key of the message. Important note: The data type must always be specified. Make sure that you always use matching types when sending and receiving. If, for example, a message is defined and sent as Byte/String and then read as Integer/Byte, this leads to an error and the message cannot be read. Lobster_data as a consumer is blocked until someone removes this erroneous message from the broker and it does not process any messages from this topic!

(5) The data type of the data to be sent. Important note: The data type must always be specified. Make sure that you always use matching types when sending and receiving. If, for example, a message is defined and sent as Byte/String and then read as Integer/Byte, this leads to an error and the message cannot be read. Lobster_data as a consumer is blocked until someone removes this erroneous message from the broker and it does not process any messages from this topic!

System Variables and Header Properties

When receiving a message, the key of a message is stored in the system variable MSG_CALL_KAFKA_KEY (if defined) and is therefore available in the mapping. Header properties of a message can be read out using system variables of the form MSG_CALL_<KEYNAME> (everything in uppercase).