Settings

(1) Max. file number per submission: The maximum number of files that can be sent per message can be specified here. This can lead to several messages being created within a triggered transmission. You will find corresponding messages in the ASM log ("... message 1", "... message 2", ...). However, all files collected up to that point are always processed for each triggered transmission.

(2) Alias: The Kafka alias. See section Kafka connections.

(3) Topic: The topic to which the message is sent.

(4) Persist too large messages: This is a special setting that you can (and should) ignore under normal circumstances. If a sent message is too large (broker limit 1 MB by default, 10 MB protocol limit), an exception is normally thrown. If this checkbox is set, this exception is caught, the file is stored in a local folder instead and a dummy message with a reference to the local file is sent, with which the recipient automatically obtains this local file. However, this currently only works if the consumers listening to topic (3) are in the same Load Balancing system. Otherwise, do not set this checkbox, as this will give the impression that the message has been sent successfully, but the recipient cannot receive it.

(5) Data Type: The data type of the message 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 Integration as a consumer is blocked until someone removes this erroneous message from the broker and it does not process any messages from this topic! Important note: If the data type AVRO is used, the path to a schema file (6) and in (12) the address to the schema registry must also be specified. Name: schema.registry.url , Value: http://address:port.

(6) Path to schema file: See (5).

(7) Key Type: 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 Integration as a consumer is blocked until someone removes this erroneous message from the broker and it does not process any messages from this topic!

(8) Waiting time in ms: The waiting time (linger.ms) is the time that is waited until sending. If messages are added until then, they are all sent together. At 0 ms, messages are always sent immediately one by one.

(9) Message size in KB: The message size (batch.size) determines the maximum size of the collected messages. If this size is reached before the waiting time expires, sending occurs.

(10) Abort on Error: If this checkbox is not set, sending is not interrupted even if there is a erroneous message.

(11) Client ID: An optional identifier of a Kafka consumer (in a consumer group) that is passed to a Kafka broker with every request.

(12) KafkaProducer Properties: Additional producer properties can be defined via the context menu.