You can use the Apache Kafka Producer adapter to write a message to a Kafka topic.
| Multiexcerpt include |
|---|
| SpaceWithExcerpt | INTERNAL |
|---|
| MultiExcerptName | kafka_message |
|---|
| PageWithExcerpt | INTERNAL:_designer_excerpts |
|---|
| shouldDisplayInlineCommentsInIncludes | false |
|---|
|
Write a Message
Using the produce operation of the Apache Kafka adapter, you can write a message to a Kafka topic.
| Multiexcerpt include |
|---|
| MultiExcerptName | produce |
|---|
| PageWithExcerpt | Apache Kafka Producer |
|---|
| shouldDisplayInlineCommentsInIncludes | false |
|---|
|
producerRecord is a complex structure that defines the message and target.The topic you want to write the message to is the only mandatory parameter.
| Multiexcerpt include |
|---|
| MultiExcerptName | ProducerRecord |
|---|
| PageWithExcerpt | Apache Kafka Producer |
|---|
| shouldDisplayInlineCommentsInIncludes | false |
|---|
|
The Kafka Producer returns some meta data about the processing of the message.
| Multiexcerpt include |
|---|
| MultiExcerptName | RecordMetaData |
|---|
| PageWithExcerpt | Apache Kafka Producer |
|---|
| shouldDisplayInlineCommentsInIncludes | false |
|---|
|
Transaction Handling
The xUML Runtime handles Apache Kafka Producer calls like is specified in the Runtime transaction concept. All producer calls within a session are wrapped into a dedicated transaction with a random unique transaction ID. These transactions can be rolled back until they have been committed.
You cannot set a custom transaction ID (transactional.id), therefore there will be no fencing.