Answers to common questions about the Kafka Adapter for ABAP.
What is the Kafka Adapter for ABAP?
The adapter connects SAP applications directly to Kafka using native ABAP producer and consumer APIs. It brings IDocs and custom ABAP data into Kafka integration, with configurable serialization and a web console for administration. RAP Events integration is TBA.
How are Kafka connections secured?
Broker communication uses TCP/TLS with SASL/PLAIN authentication. Broker and Schema Registry credentials are stored under separate encrypted aliases, keeping connection configuration separate from secrets.
How does the adapter preserve processing order?
Records are processed in order within each assigned partition. A failed record is retried before later records in that partition proceed, while other partitions can continue. Ordering across different partitions is determined by your application design.
Can consumers process records in parallel?
Managed consumer groups distribute partitions across configured consumers. This allows parallel processing across partitions while retaining ordered processing within each partition. Capacity depends on partition count, SAP resources and receiver workload.
Can I choose where consumption starts?
You can configure consumption from the beginning or latest position of the stream. Explicit-offset read APIs also support selected stream positions. Existing consumer-group offsets affect where an established group resumes.
How can I monitor and troubleshoot my integration?
The web console brings channel controls, processing progress, consumer offsets and producer outbox inspection together. Application logs show error and retry details; temporary Kafka protocol traces support targeted troubleshooting. Retry limits and delays are configurable.
When should I use the ABAP adapter instead of a Kafka adapter on middleware?
Use the ABAP adapter when integration logic belongs in SAP — for example, application data integration or custom ABAP extraction of table data to Kafka. Publish and consume Kafka records directly within your ABAP applications, with control over data binding and processing, without routing each exchange through a middleware layer. Use the KaTe Kafka Adapter for SAP Integration Suite when you need central orchestration, transformations or routing across multiple systems. The two adapters complement each other within your integration landscape.
Do I need a Kafka REST proxy?
Unlike other solutions, no separate Kafka REST proxy is needed for broker communication. The adapter speaks Kafka’s binary protocol directly over TCP/TLS from ABAP. Schema Registry integration uses HTTPS separately.
Can I replicate tables to Kafka?
Yes. Publish table data to Kafka using generic or explicitly typed ABAP serialization and a simple custom ABAP program that reads and sends data through a Kafka channel. This enables straightforward data integration tailored to your requirements.
Can I exchange IDocs through Kafka?
Yes. Send and receive complete IDocs as Kafka records using standard SAP IDoc integration. Outbound IDocs are confirmed after Kafka acknowledges the record.
Which Confluent serializers are supported?
The adapter provides serializers and deserializers compatible with Confluent Avro and Confluent JSON Schema, including Schema Registry integration. Avro supports schema evolution; JSON Schema supports validation within a documented Draft 7 subset.
How does the adapter support reliable delivery?
The adapter commits Kafka consumer offsets only after successful receiver processing. Failed records are retried before processing continues within their partition, helping ensure records are not skipped when processing fails.