Categories
News

KaTe is now in Americas

KaTe now in Americas

Company News

KaTe Group Inc. Opens in Atlanta: SAP Integration Expertise for the Americas

With KaTe Group Inc. in Atlanta, KaTe is expanding its local presence for customers and partners across North and South America — bringing established SAP integration expertise closer to the region.

KaTe Group Inc. has officially been incorporated in Atlanta, Georgia. The new company presence marks an important step for KaTe: a stronger local connection for organisations, partners and SAP integration teams throughout North and South America.

KaTe has focused on SAP integrations since 2008. From its roots in Germany, the company has developed software solutions first for SAP integration landscapes — including dedicated SAP adapters and IntegraOps for integration operations. Core expertise spans SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO and SAP ERP/ABAP integration. Consulting and project services complement these products where organisations need architectural, implementation or operational support.

Software solutions for modern SAP integration. KaTe Group Inc. brings dedicated adapter products, IntegraOps for integration operations and practical SAP expertise closer to customers and partners across the Americas. Services are available where they add value — alongside a clear product focus.

A base in Atlanta for North and South America

The KaTe office is located in Atlanta Buckhead at Three Alliance Center. Atlanta is the base for the company’s activities in the Americas and supports closer collaboration across time zones, regional business contexts and individual integration roadmaps.

The goal is not simply a new address. It is to make KaTe’s software solutions, product knowledge and SAP integration experience more accessible to teams working with complex landscapes across North and South America.

Company presence
KaTe Group Inc., incorporated in Atlanta, Georgia, USA.
Regional focus
Customers, partners and the SAP community across North and South America.
Core expertise
SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO, SAP ERP/ABAP integration and dedicated SAP integration adapters.
KaTe’s solution for SAP integration operations: Monitoring, Transport Management and Disaster Recovery. Learn more about the monitoring capabilities with IntegraMon.

Software solutions for SAP integration and operations

KaTe is primarily a software solutions company. SAP integration landscapes are rarely static: teams run cloud integrations alongside on-premise systems, modernise SAP PI/PO, extend ERP processes through ABAP, connect business-critical systems and build new services on SAP BTP. KaTe develops software that helps organisations address these integration and operations requirements, with expert services available where a project needs additional support.

Solution areaWhat KaTe brings
Dedicated SAP adaptersSoftware products for connecting SAP and non-SAP systems in SAP Integration Suite, SAP PI/PO and hybrid integration scenarios.
SAP Integration SuiteIntegration solutions and adapter capabilities for cloud-based SAP integration architecture.
Edge Integration CellSupport for hybrid integration scenarios that combine cloud capabilities with local requirements.
SAP PI/POProducts and expertise for established middleware landscapes as organisations operate, modernise or evolve their integration architecture.
SAP ERP / ABAP integrationIntegration expertise for connecting SAP ERP processes, ABAP-based extensions and surrounding business systems.
IntegraOpsKaTe’s software solution for SAP integration operations: Monitoring, Transport Management and Disaster Recovery. The monitoring capabilities are available through IntegraMon.

For teams operating SAP Integration Suite and Edge Integration Cell, IntegraOps provides a product-led operations approach across integration environments. It combines Monitoring, Transport Management and Disaster Recovery; IntegraMon provides the central monitoring capabilities. Together with KaTe’s adapter portfolio, this creates a practical software foundation for connecting, operating and evolving SAP integration landscapes.

Building the next chapter together

Bernd Baier, Head of Americas, will represent KaTe from Atlanta and work with organisations across the region. Together with Sebastian Simon and Lars Albrecht, the team is looking forward to building new connections, supporting customers and contributing to the growing SAP integration community in the Americas.

The coming months will bring more conversations around SAP Integration Suite, SAP ERP/ABAP integration, Kafka, MQTT, Edge Integration Cell and the operational challenges that emerge as integration landscapes scale. KaTe looks forward to sharing product knowledge, discussing architectures and helping teams solve the integration problems that matter most to their business.

What the Atlanta presence means for SAP integration teams

For customers and partners in North and South America, KaTe Group Inc. creates a local starting point for conversations about software solutions, integration architecture, dedicated adapters, SAP ERP/ABAP integration, hybrid scenarios and IntegraOps. The experienced KaTe team remains connected across regions, while the Atlanta presence strengthens the company’s ability to engage locally.

Whether an organisation is modernising SAP PI/PO integrations, designing an Integration Suite architecture, evaluating Edge Integration Cell, connecting SAP ERP/ABAP processes or looking for more control in integration operations, the focus remains the same: fit-for-purpose software solutions, reliable operation and practical implementation support.

Frequently asked questions

Find answers to common questions about KaTe Group Inc., its SAP software solutions and its presence in the Americas.

Where is KaTe Group Inc. located in the United States?

KaTe Group Inc. is located in Atlanta Buckhead, Georgia, at Three Alliance Center.

Which regions does KaTe Group Inc. support?

The Atlanta presence supports KaTe’s work with customers, partners and the SAP community across North and South America.

What is KaTe’s primary focus?

KaTe primarily develops software solutions for SAP integration and operations. These include dedicated SAP adapters and IntegraOps. Consulting and project services complement the software portfolio where required.

Which SAP technologies are part of KaTe’s core expertise?

KaTe’s core expertise includes SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO, SAP ERP/ABAP integration and dedicated SAP integration adapters.

What is IntegraOps?

IntegraOps is KaTe’s solution for SAP integration operations. It combines Monitoring, Transport Management and Disaster Recovery. The monitoring capabilities are available through IntegraMon.

Who represents KaTe in the Americas?

Bernd Baier is Head of Americas. He works together with Sebastian Simon and Lars Albrecht as KaTe develops its presence across the region.

You can find even more news on our social media channels:

Categories
News

Scaling Kafka Consumption in SAP Integration Suite

Scaling Kafka Consumption in SAP Integration Suite

Product Update

From One Record per Message to One Batch per Run: Scaling Kafka Consumption in SAP Integration Suite

The KaTe Kafka Adapter can combine records returned by a Kafka poll into one batch payload — enabling SAP Integration Suite and Edge Integration Cell to process Kafka workloads with fewer repeated integration and network calls.

Kafka can deliver far more events than a conventional backend can process one request at a time. The bottleneck is often not Kafka itself. It is the repeated integration and network overhead created when every record starts its own SAP Integration Suite message and its own backend call.

The Sender Batch feature of the KaTe Kafka Adapter for SAP Integration Suite changes that equation. Instead of translating every polled Kafka record into a separate Cloud Integration message, the adapter can combine the records returned by a poll into one batch payload. One integration run can then validate, map and deliver many business records together.

Batching and partition parallelism complement one another: partitions provide concurrent work lanes, while batching makes each lane more efficient. The result can be substantially fewer integration and network round trips for Kafka workloads processed through SAP Integration Suite.

What changes in batch mode?

In single-record mode, 100 Kafka records create up to 100 Cloud Integration messages. In batch mode, the adapter can create one message containing up to the configured Max poll records. The backend receives fewer, larger calls, while Kafka offsets are committed only after the complete batch has been transferred successfully into Cloud Integration.

Two payload styles are available:

Simple batch format
Contains only the transformed record values under one configurable root element.
Detailed batch format
Also carries Kafka metadata such as topic, partition, key, offset, timestamp, headers and tombstone information for each record.

For continuous processing, the adapter collects available records up to the configured poll limit. If the batch is not full, it can wait for the configurable batch window before submitting the records already available. Interval processing creates one batch from the records returned by that interval’s poll.

An illustrative throughput model

Consider a topic with four partitions and enough parallel consumers to keep all four busy. Assume one single-record backend interaction takes 50 ms end to end: 25 ms of network and protocol latency plus 25 ms of backend work.

These are elapsed times including acknowledgement and commit where applicable. The model assumes four active processing lanes and excludes additional iFlow processing and batch-collection delays.

4 parallel partitions / 0.050 seconds = 80 records per second

Batching amortizes the integration and network cost. The exact gain depends on whether the backend has a true bulk operation or still performs most of its work record by record.

ModeIllustrative throughputGain vs. single record
Single record80 records/s1×
Batch of 10; whole batch handled in 50 ms800 records/s10×
Batch of 100; whole batch handled in 50 ms8,000 records/s100×
Batch of 10; 25 ms network per batch + 25 ms work per recordabout 145 records/sabout 1.82×
Batch of 100; 25 ms network per batch + 25 ms work per recordabout 158 records/sabout 1.98×

The optimistic case assumes that a backend can process the complete batch in roughly the same 50 ms as one record. The conservative case assumes that only the 25-ms network portion is shared while 25 ms of work remains for every record. Its speed-up is:

speed-up(B) = 50 × B / (25 + 25 × B) = 2B / (B + 1)

With these assumptions, eliminating repeated network round trips can approach 2× even when backend work remains linear. A real bulk API, bulk database operation or vectorised transformation can move the result much closer to the batch-size multiplier. These figures are a capacity-planning model, not a measured product benchmark; payload size, mapping cost, worker count, broker latency, retries and backend limits all affect production throughput.

Why a JDBC batch can finish close to a single insert

A 50-ms JDBC insert including network travel and commit is a plausible assumption for a remote database. A modest batch can finish close to that when fixed overhead dominates: JDBC batching reduces round trips, and one transaction shares commit overhead across rows.

For example, 49 ms fixed overhead + 1 ms per row gives 50 ms for one insert and 149 ms for 100 rows. Four concurrent lanes would then deliver approximately 2,685 records/s — 33.6× the single-record baseline. These are illustrative inputs; indexes, triggers and lock contention affect actual results. The earlier near-2× case assumes all backend work repeats per row, so it is not a general JDBC limit.

Fewer metered Integration Suite messages

Batching can also reduce SAP Integration Suite message consumption. At the time of writing, SAP’s public pricing definition counts a Cloud Integration message in 250 KB blocks — not 256 KB. An outbound message of up to 250 KB counts as one message; every additional 250 KB or fraction thereof counts as another. For synchronous receiver calls, SAP considers the request and response together, and special patterns such as splitters have separate counting rules. The exact commercial effect depends on the customer’s edition, included volume, contract and whether a message is chargeable. See the current SAP Integration Suite pricing definition and verify the deployed flow in the tenant’s Message Usage dashboard before using an estimate for budgeting.

For example, 20 individually processed records below 250 KB normally create 20 outbound backend messages and therefore at least 20 metered messages. If the same records form one outbound batch that remains at or below 250 KB — including its envelope and, for a synchronous call, its response — the batch can count as one metered message. If that batch grows to 600 KB, it counts as three rather than 20. Batching does not make payload volume free, but it removes the minimum one-message charge that otherwise applies to every small outbound call.

single-record units ≈ number of records × ceil(single outbound size / 250 KB) batch units ≈ ceil(total batched outbound size / 250 KB)

Treat this as a planning approximation. Headers, envelopes, receiver calls, synchronous responses, retries, splitters and the final deployed flow can change the metered total.

Where batching helps most

Sender Batching is particularly effective when the downstream system already supports bulk requests, database array operations, mass updates or file-oriented interfaces. It can also reduce the number of Cloud Integration message processing logs and repeated connection setups produced for the same business volume.

There is a deliberate trade-off: a batch is one processing unit. Larger batches improve amortisation but can increase per-record latency, memory use and the amount of work retried after a failure. Channel-level single-record deduplication is not available for variable batches, so downstream processing should be idempotent or deduplicate records using stable business identifiers. Batching is also not available for selective support-mode reads.

Decision matrix: should the sender use batching?

The decisive question is whether the connected backend can consume a collection efficiently. Merely wrapping single-record calls in one XML document does not create a bulk operation.

Backend or requirementFitGuidance
BI, data warehouse or data-lake ingestionStrongThese systems commonly prefer larger blocks, staged files or bulk-load APIs.
JDBC batch insert/upsert or set-based database procedureStrongUse a real bulk statement, array binding, staging table or mass-enabled procedure; looping over single inserts gives a smaller benefit.
OData $batchStrong when supportedConfirm that the service supports $batch, define whether operations belong in a transactional change set and map the Kafka batch to the required multipart request.
File, SFTP or object-storage deliveryStrongA batch maps naturally to a multi-record file when the receiver expects one; it is a poor fit if every event must remain a separate file.
Mass-enabled BAPI or SOAP operationConditionalUse batching only when the operation or a controlled wrapper accepts a table/list and defines partial-error behaviour.
Standard single-object BAPI or SOAP serviceUsually weakMany standard operations still execute one business transaction per call; batching may require a purpose-built wrapper and careful commit handling.
Per-record response, independent retry or very low latencyWeakSingle-record processing preserves granular acknowledgements and avoids waiting for a batch window.
Highly variable or very large payloadsConditionalSet conservative limits and test the combined request against CPI, adapter, backend and network size limits.
Backend cannot process collectionsDo not batchThe iFlow would have to split and loop, losing much of the throughput and metering advantage while adding complexity.

A practical starting point

Start with a moderate Max poll records value such as 10 or 25, align the number of parallel consumers with the available topic partitions and verify that the backend genuinely handles the batch efficiently. Then increase the batch size while watching end-to-end latency, metered message usage, payload size, memory, retry behaviour and backend saturation. A batch window should be long enough to form useful batches but short enough to meet the scenario’s latency target.

Batching and partition parallelism complement each other: partitions provide concurrent work lanes, while batching makes each lane more efficient. Together they let SAP Integration Suite process Kafka workloads with substantially fewer integration and network round trips.

What this update means for SAP integration teams

These concise answers preserve the technical scope of the update and make the page easier to navigate in conventional and AI-assisted search.

What is Kafka Sender Batching?

It is a KaTe Kafka Adapter feature that groups records returned by a Kafka poll into one batch payload and delivers that group as one Cloud Integration message for further processing.

Does Sender Batching guarantee a specific throughput increase?

No. The numerical examples above are capacity-planning models, not measured product benchmarks. The result depends on the bulk capability and limits of the downstream system as well as the complete deployed architecture.

What comes next?

A follow-up article will examine how Confluent Parallel Consumer can extend the sender-side design with controlled record-level concurrency, including ordering choices, offset management and the situations in which it complements — or replaces — classic partition-bound processing.

Scaling Kafka Consumption in SAP Integration Suite

You can find even more news on our social media channels:

Categories
SAP Products

Kafka Adapter for SAP Integration Suite

Kafka Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

Kafka Adapter for
SAP Integration Suite

Bidirectional connection between SAP Cloud Integration Iflows and Apache Kafka – the logical successor to the proven KaTe Kafka Adapter for SAP PO.

Verified SAP Partner Free 30-Day Trial
Architecture Overview
SAP Cloud
Integration
Iflow
bidirektional
KaTe
Kafka Adapter
CPI
Publish / Subscribe
Apache Kafka
On-Premise / BTP
Avro Protocol Buffers OAuth2 SASL_SSL Schema-Registry Batch Processing CSFLE / CSPE
Verified SAP Partner
Free 30-Day Trial
SAP Roadmap Compatible

All Features of the Kafka Adapter at a Glance

The KaTe Kafka Adapter for SAP Integration Suite offers much more than the SAP standard adapter – from Avro support to Field-Level Encryption.

Core Functions: Publish & Subscribe
Publish SAP Cloud Integration Iflow messages as Kafka records and subscribe to Kafka records as Iflow messages. Kafka Key, Header, and Data are translated into Iflow messages and vice versa.
  • Topics and partitions flexibly configurable
  • Ack mode and consumer commits customizable
  • Fully integrated into SAP Cloud Integration
  • Observable at channel and message log level
Enterprise-Grade Security
All common Kafka security standards are supported – including advanced encryption at the field and payload level for regulated environments.
  • PLAIN, PLAIN_SASL, SASL_SSL
  • SASL-Plain / SASL-SCRAM
  • OAuth2 & Client Certificate Authentication
  • Field-Level Encryption (CSFLE) & Payload Encryption (CSPE)
  • SOC 2, GDPR, ISO 27001 compliant
High Performance & Flow Control
Full control over message throughput, filtering, and batch processing – for optimal performance with high data volumes.
  • Filtering by headers, keys, and data content
  • Batch processing: n Kafka records as one Iflow message
  • Polling and record count/time unit configurable
  • Processing from the beginning, end, or any stream position

Advanced Features: Error Handling, Formats & Migration

Automated & Manual Error Handling
In "in order" streaming systems, errors can stop the entire processing. To prevent this, our adapter offers both manual and fully automated error handling.
  • Error routing to an error destination
  • Documentation and ignoring of specific cases
  • Error handling even for deserialization errors
  • Deduplication via offset or record header
Avro, Protocol Buffers & Schema Registries
Binary data formats like Avro and Protocol Buffers are standard in Kafka environments. Therefore, our adapter fully supports them – including automatic schema generation via schema registries.
  • Avro and Protocol Buffers ↔ XML conversion
  • JSON ↔ XML transformation
  • Schema Registry integration
  • Integrated schema generation tool
SAP Roadmap Compatible
Because the adapter is available for both SAP Process Orchestration and the SAP Integration Suite, existing SAP PO integrations can be transferred with minimal effort.
  • Available for SAP PO and SAP Integration Suite
  • Import existing interfaces without refactoring
  • Determine your own migration plan and schedule
  • Investments in SAP PO integrations are preserved

Why the KaTe Adapter
Can Do More

The KaTe Kafka Adapter offers crucial features that the SAP standard Kafka adapter in SAP Cloud Integration does not provide.

1
Arbitrary Stream Positions & Group Names
While the SAP standard connector does not support arbitrary positions or group names in the stream, our Kafka connector fully provides this feature, which is crucial in daily operations.
2
All Data Formats incl. Schema Registry
Avro, Protocol Buffers, JSON, and schema registries with automatic schema generation are fully supported – although the SAP standard connector has significant gaps here.
3
Batch Processing in One Iflow Execution
Multiple Kafka records can be bundled as a single Iflow message, significantly increasing throughput. Since the SAP standard connector does not offer this function, this is a decisive advantage.
4
Advanced Error Handling & Encryption
Both manual and automated error handling – including deserialization errors – as well as Field-Level and Payload Encryption (CSFLE/CSPE) are integrated, whereas the SAP standard connector does not provide these features.
5
Private and Public Network Access
The adapter runs equally on SAP Cloud Integration and SAP Edge Integration Cell (EIC). It also supports hybrid scenarios, including access to on-premises Kafka brokers, schema registries, and OAuth 2.0 identity providers through SAP Cloud Connector.

Kafka Adapter Comparison:
KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
Arbitrary Stream Positions
✓ Yes
✗ No
Avro / Protocol Buffers
✓ Yes
✗ No
Schema-Registry
✓ Yes
✗ No
Batch Processing
✓ Yes
✗ No
Field-Level Encryption
✓ Yes
✗ No
Advanced Error Handling
✓ Yes
Limited
Filtering & Deduplication
✓ Yes
✗ No
OAuth2 & CSFLE/CSPE
✓ Yes
✗ No
SAP Cloud Connector Support
✓ Yes
✗ No

Set Up Kafka Adapter – Start in 3 Steps

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Installation in your SAP Integration Suite is completed in just a few steps, as our team guides you through the onboarding process.

3
Go Live

Initial productive scenarios start quickly, allowing you to scale as needed – without upfront investments.

Compatibility: Supported Kafka Platforms & Protocols

Whether on-premise, cloud, or hybrid – the KaTe Kafka Adapter for SAP Integration Suite is compatible with all common Kafka deployments and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated. SAP Docs ↗
Supported
SAP BTP
SAP Business Technology Platform – Cloud-native
Supported
Apache Kafka
On-premise Kafka clusters of all common versions. Apache Kafka ↗
Supported
Confluent Platform
Confluent Cloud and Confluent Platform on-premise. Confluent ↗
Supported
Azure Event Hubs
Kafka-compatible Azure Event Hubs endpoint
Supported
AWS MSK
Amazon Managed Streaming for Apache Kafka
Supported
SAP Edge Integration Cell
Hybrid on-premise scenarios with EIC
Supported
SAP Cloud Connector
Access on-premises Kafka brokers and schema registries through SAP Cloud Connector (SCC).
Supported

KaTe Launchpad – More Control During Setup and Operations

The KaTe Launchpad extends the Kafka Adapter with an integrated toolbox for developers and operations teams, so that all key functions are accessible directly from the SAP Integration Suite.

Generator

Kafka configurations, topic structures, and SAP Integration Suite Iflow channel definitions are automatically generated, significantly reducing configuration effort and error sources.

Service List Display & Tester

The Service List Display provides an overview of all configured Kafka topics, consumer groups, and broker connections, while the integrated tester enables sending and receiving Kafka messages directly from the SAP Integration Suite.

SAP Technology & Migration Consulting –
Future-Proof Integration

KaTe GmbH is your expert partner for SAP technology and migration projects. Our focus is on the secure and seamless transformation of existing SAP PO landscapes to the modern SAP Integration Suite – including the SAP Edge Integration Cell for hybrid integration scenarios.

  • Migration from SAP PO to SAP Integration Suiteincluding analysis, architecture design, and technical implementation
  • Implementation and Optimization of the SAP Edge Integration Cellfor flexible and secure hybrid integration
  • SAP BTP (Business Technology Platform) ConsultingLeveraging modern services and tools for innovation and process automation
  • Technology-Based Strategy Consultingfrom cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Downtime

We analyze your existing interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite, so the transition succeeds without operational disruption.

Learn More
SAP PO Adapter – Free 30-Day Trial
All SAP PO Adapters – No Upfront Payment

Try our SAP PO Adapters for Kafka, MQTT, AMQP, AWS, Azure, GCP, GraphQL, gRPC, and RESTful – free for 30 days.

View All SAP PO Adapters
IntegraMon – SAP Monitoring
Central Dashboard for All SAP CPI Tenants & EIC Instances

IntegraMon unifies all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe Kafka Adapter for SAP Integration Suite.

What is the Kafka Adapter for SAP Integration Suite?

As a powerful middleware component, the Kafka Adapter for SAP Integration Suite connects SAP systems bidirectionally with Apache Kafka – both cloud-native and in hybrid scenarios. Since it reliably processes event-driven data streams and enables message exchange between SAP Cloud Integration Iflows and Kafka topics, it is the ideal integration layer for modern SAP landscapes. As the successor to the KaTe Adapter for SAP Process Orchestration (SAP PO), it also offers state-of-the-art features for seamless SAP integration.

What core features does the Kafka Adapter for SAP Integration Suite offer?

With the adapter, SAP Cloud Integration Iflow messages can be published as Kafka records, and Kafka records can be subscribed to as Iflow messages. Kafka keys, headers, and payloads are automatically translated into Iflow messages – and vice versa. In addition, the following core features are available:

  • Full support for Avro, Protocol Buffers, and JSON, including schema registry and automatic schema generation
  • Topics, partitions, and reliability settings (ack mode, consumer commits) are flexibly configurable
  • Batch processing: n Kafka records as one Iflow message
  • Filtering by headers, keys, and data content
  • Fully integrated into SAP Cloud Integration, observable and debuggable
What security standards are supported?

Because regulated environments have special requirements, the Kafka Adapter for SAP Integration Suite meets the highest security standards. Specifically, the following protocols and methods are supported:

  • Kafka Security Standards: PLAIN, PLAIN_SASL, SASL_SSL, SASL-Plain/SASL-SCRAM
  • OAuth2 and client certificate authentication for broker and service registry connections
  • Field-Level Encryption (CSFLE) and Payload Encryption (CSPE) for sensitive data
  • Compliance-ready for SOC 2, GDPR, and ISO 27001

Technical Details & Comparison

How does the adapter support high performance and error handling?

Thanks to integrated batch processing, filtering, and flow control, the adapter delivers high-performance streaming even at high data volumes, so that even large amounts of data are reliably processed. Messages can be filtered by headers, keys, or data content and bundled into optimized batches.

For stable data processing, both automated and manual error handling are available. Serialization errors, data transformation errors, or Iflow errors can be forwarded to an error destination or deduplicated, so that continuous operation is always guaranteed.

How does the KaTe Adapter differ from the SAP standard Kafka adapter?

While the SAP standard Kafka adapter covers only basic functions, the KaTe Kafka Adapter offers significantly more flexibility and depth. Specifically, these include:

  • Support for arbitrary stream positions and freely definable group names
  • Compatibility with Avro, Protocol Buffers, JSON, and schema registries with automatic schema generation
  • Batch processing in a single Iflow execution
  • Advanced error handling – both manual and automated – including for deserialization errors
  • Filtering and deduplication for higher data quality and optimized data throughput
  • Field-Level and Payload Encryption (CSFLE/CSPE)
  • Flexible private network access to Kafka brokers, schema registries, and OAuth 2.0 identity providers through SAP Cloud Connector.
How does SAP Cloud Connector support hybrid Kafka integration?

The KaTe Kafka Adapter supports SAP Cloud Connector for hybrid integration scenarios. It enables SAP Cloud Integration and SAP Edge Integration Cell to reach on-premises Kafka brokers, schema registries, and OAuth 2.0 identity providers without exposing them directly to the public internet.

Is the KaTe Kafka Adapter SAP Roadmap Compatible?

Yes, the KaTe Kafka Adapter is available for both SAP Process Orchestration and the SAP Integration Suite. Existing SAP PO integrations can therefore be transferred to the Integration Suite without significant migration effort, adjustments, or refactoring.

You determine your own timeline and roadmap. Because your investments in SAP PO integrations are fully preserved, neither unforeseen risks nor commercial follow-up questions arise.

Get Started Now

Ready for Kafka in the SAP Integration Suite?

Contact us for a free 30-day trial or an individual consultation. We set up your trial within 48 hours.

Categories
SAP Products

Confluent Parallel Consumer Adapter for SAP Integration Suite

Confluent Parallel Consumer Adapter for SAP Integration Suite – KaTe GmbH
SAP Integration Suite (CPI)

Confluent Parallel Consumer Adapter for
SAP Integration Suite

Achieve 10–500x higher throughput than the SAP standard adapter. By leveraging parallelization at the record-key level, Avro, Protocol Buffers, Schema Registry, and automated error handling, you ensure maximum performance in SAP Integration Suite and Edge Integration Cell.

Verified SAP Partner Request a Demo 10–500x Higher Throughput Avro & Protocol Buffers
Architecture Overview
SAP Cloud
Integration
Iflow / EIC
parallel
KaTe Confluent
Parallel Consumer
SAP CPI
Kafka Protocol
Confluent /
Apache Kafka
Cloud · On-Premise · EIC
10–500x Throughput Avro / Protobuf Schema Registry Batch Processing SASL_SSL OAuth2 Error Handling

High-Throughput Kafka Integration –
10–500x More Throughput Than SAP Standard

The KaTe Confluent Parallel Consumer Adapter includes all functions of the Kafka Adapter. Additionally, it supplements these with parallelizable processing capabilities for maximum throughput.

Publish & Subscribe
SAP Cloud Integration Iflow messages are published as Kafka records, while Kafka records are subscribed to as Iflow messages. During this process, Kafka Key, Header, and Data are fully translated into Iflow Messages.
  • Configurable topics, partitions, and ack mode
  • Customizable consumer commits
  • Wildcards and durable subscriptions
  • Processing from beginning, end, or any position
Parallelization & Throughput
Because parallelization occurs at the record-key level instead of the partition level, a 10–500x higher throughput is achieved for single and batched records. Consequently, this happens without losing the functional order of related records.
  • 10–500x Higher Throughput
  • Parallelization at record-key level
  • Configurable thread pool
  • Batch processing (n records per Iflow)
Security
Since enterprise environments demand the highest security standards, all common Kafka security protocols for broker and ServiceRegistry connections are supported. This includes both OAuth2 and Client Certificate Authentication.
  • PLAIN, PLAIN_SASL, SASL_SSL
  • SASL-Plain / SASL-SCRAM
  • OAuth2 Authentication
  • Client Certificate Authentication
Filtering & Flow Control
Gain full control over throughput and processing order. Kafka records can be filtered before triggering an integration, ensuring that only relevant messages are processed.
  • Filtering by headers, keys, and data contents
  • Deduplication via offset or record header
  • Freely definable group names
  • Unordered and ordered scenarios
Automated Error Handling
Errors during deserialization, data transformation, or downstream processing can be handled automatically. Therefore, non-blocking and asynchronous processing is guaranteed even with faulty records.
  • Error forwarding to Error Topic / Dead Letter Topic
  • Deserialization errors automatically handleable
  • Non-blocking and asynchronous processing
  • Fine-grained error strategies configurable
Avro, Protocol Buffers & Schema Registry
Typical binary data formats are supported with Kafka-specific optimizations. As a result, Avro and Protocol Buffers are directly translated into XML – and vice versa.
  • Avro and Protocol Buffers support
  • Schema Registry integration
  • Integrated schema generation tool
  • JSON to XML transformation

Processing Models Compared –
Standard vs. Parallel Consumer

The KaTe Confluent Parallel Consumer Adapter offers three processing models: Partition-Based Processing (SAP Standard), Key-Ordered Processing, and Unordered Processing. Thus, it provides maximum flexibility for different requirements.

Verarbeitungsmodelle: Partition-Based Processing (1 Partition = 1 Thread), Key-Ordered Processing (Ordered per Message Key), Unordered Processing (Concurrent & Unordered)

Why the Confluent Parallel Consumer Adapter
is the Right Choice

High-throughput Kafka integration with SAP Integration Suite – without increasing the partition count, with complete error handling and Avro/Protobuf support.

1
10–500x Higher Throughput
Because parallelization occurs at the record-key level instead of the partition level, a drastically higher throughput is achieved – without increasing the partition count and with only a single consumer.
2
Automated Error Handling
Errors during deserialization, data transformation, or downstream processing are automatically forwarded to an error topic or dead letter topic – non-blocking and without any operational disruption.
3
Avro, Protocol Buffers & Schema Registry
Typical binary data formats are fully supported, so integrated schema generation tools can be used directly without third-party tools.
4
Easy Migration from SAP PO
Existing interfaces can be easily imported because the adapter is fully compatible with the SAP Integration Suite – investments in SAP PO integrations can be easily transferred.

KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
Parallelism Model
Record-Key-Level
Partition-Level
Throughput Scaling
10–500x higher
Partition increase required
Automated Error Handling
✓ Yes
✗ No
Avro / Protocol Buffers
✓ Yes
✗ No
Batch Processing
✓ Yes
✗ No
Filtering & Deduplication
✓ Yes
✗ No
Freely Definable Group Names
✓ Yes
✗ No
Advanced Monitoring
Consumer Lag, 1:1 Record-Tracking
✗ Not supported

Summary

FeatureSAP Standard Kafka AdapterConfluent Parallel Consumer Adapter
Parallelism modelLimited by number of Kafka partitionsConfigurable thread pool enables high parallelism with a single consumer
Ordering guaranteesOrdering guaranteed only per partitionOrdering guaranteed at message key level (optional), with parallel execution across different keys
Throughput scalingRequires increasing partition count for scalingScales without increasing partitions; up to 10–500x higher throughput possible.
Iflow executionBlocked calls partially or completely stop message processingNon-blocking and asynchronous processing without message processing being blocked by errors or individual "slow" records.
Automated Error handlingNot supported, some errors are not directly visible (deserialization)Error handling for deserialization / data transformation or iflow execution errors can be set automatically. Errors are then logged (as error messages) and ignored or forwarded to an error topic/dead letter topic.
Offset /Group Name controlNot supportedAny type of start possible (start, end) of the offset or reprocessing of arbitrary offsets. Group names freely definable.
Message acknowledgmentOffset commits at partition levelFine-grained, message-level acknowledgment and processing control
Advanced MonitoringNot supportedRich monitoring user experience (consumer lag, 1:1 recognition of which Kafka record generated which Iflow execution at a glance and out of the box)
FilteringNot supported, nur manuel in jedem einzelnen iflow implementierbarFiltering with headers or data contents to avoid unnecessary message load
Avro/Protobuf and JSON with schema registryNot supportedSupported, including data transformation and schema generation to XML

Getting Started – flexibel skalieren

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Installation in your SAP Integration Suite is completed in just a few steps. Furthermore, our team will support you during onboarding.

3
Go Live

Initial productive scenarios start quickly. Consequently, you can scale as needed – without upfront investments.

Supported Platforms & Kafka Distributions

Whether Confluent Cloud, Apache Kafka, or Azure Event Hubs – the KaTe Confluent Parallel Consumer Adapter is compatible with all common Kafka distributions and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP Edge Integration Cell
Hybrid on-premise/cloud scenarios (EIC)
Supported
Confluent Platform
Confluent Cloud and on-premise with Schema Registry
Supported
Apache Kafka
Open Source Apache Kafka – all versions
Supported
Azure Event Hubs
Azure Event Hubs with Kafka protocol
Supported
AWS MSK
Amazon Managed Streaming for Apache Kafka
Supported
SAP BTP
SAP Business Technology Platform – Cloud-native
Supported
Avro / Protocol Buffers
Binary data formats with Schema Registry
Supported

KaTe Launchpad – more control during setup and operations

The KaTe Launchpad extends the Confluent Parallel Consumer Adapter with an integrated toolbox for developers and operations teams. As a result, all key functions are accessible directly from the SAP Integration Suite.

Generator

Kafka configurations, topic structures, schema definitions, and SAP Integration Suite Iflow channel definitions are generated automatically. Therefore, the configuration effort for new Kafka integration scenarios is significantly reduced, accelerating deployment.

Service List Display & Tester

The Service List Display provides an overview of all configured Kafka topics, consumer groups, broker connections, and Schema Registry entries. Meanwhile, the integrated tester enables sending and receiving Kafka records directly from the SAP Integration Suite.

SAP Technology and Migration Consulting –
Future-Proof Integration

KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus lies on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP Consulting – use of modern services and tools for innovation and process automation
  • Technology-based Strategy Consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Operational Disruption

We analyze your existing Kafka interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite. Consequently, your Kafka integrations are migrated without operational disruption.

Learn more
Kafka Adapter for SAP PO – Request a Demo
All SAP PO Adapters Without Upfront Payment

Test our SAP PO Adapters for Kafka, MQTT, AMQP, AWS and more – 30 days for free.

View all SAP PO Adapters
IntegraMon – SAP Monitoring
Central Dashboard for all SAP CPI Tenants & EIC Instances

IntegraMon unites all SAP CPI tenants and Edge Integration Cells in a single dashboard. It features proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe Confluent Parallel Consumer Adapter for SAP Integration Suite.

What is the Confluent Parallel Consumer Adapter for SAP Integration Suite?

As a specialized high-throughput extension of the KaTe Kafka Adapter, the KaTe Confluent Parallel Consumer Adapter optimizes processing on SAP Integration Suite or Edge Integration Cell (EIC). It contains all functionalities of the KaTe Kafka Adapter and supplements them with parallelizable processing functions for high throughput – up to 10–500x more than the SAP standard adapter.

What core features does the Confluent Parallel Consumer Adapter offer?

The adapter provides the following core features:

  • Parallelization at record-key level (instead of partition level)
  • Batch processing (n records as a single Iflow message)
  • Filtering by headers, keys, and data contents
  • Deduplication via offset or record header
  • Automated Error Handling (Error Topic / Dead Letter Topic)
  • Avro/Protocol Buffers with Schema Registry and automatic schema generation
Which security standards are supported?

Because enterprise environments demand the highest security standards, the adapter supports all common Kafka security protocols: PLAIN, PLAIN_SASL, SASL_SSL, SASL-Plain/SASL-SCRAM, OAuth2, as well as Client Certificate Authentication for broker and ServiceRegistry connections.

How does the adapter support high performance and error handling?

Since parallelization occurs at the record-key level, the adapter enables 10–500x higher throughput for single and batched records without losing the functional order of related records. Furthermore, errors during deserialization, data transformation, or downstream processing can be automatically forwarded to an error destination or documented and ignored – non-blocking and asynchronous.

How does the adapter differ from standard SAP Cloud Integration adapters?

While the SAP standard adapter parallelizes at the partition level, the KaTe Confluent Parallel Consumer Adapter offers compared to the SAP standard:

  • 10–500x higher throughput without increasing the partition count
  • Parallelization without blocking by individual "slow" records
  • Automated error handling even for deserialization errors
  • Avro/Protobuf support with Schema Registry
  • Batch processing in a single Iflow execution
  • Filtering and deduplication at high data throughput
  • Freely definable group names and arbitrary stream positions
On which SAP platforms does the Confluent Parallel Consumer Adapter run?

The adapter is compatible with SAP Cloud Integration (CPI) and SAP Edge Integration Cell (EIC). Thus, both pure cloud scenarios and hybrid on-premise/cloud environments are covered. Furthermore, it is listed in the SAP App Center and therefore officially available as an SAP partner solution.

Which Kafka distributions are supported?

Whether Confluent Cloud, Apache Kafka (all versions), Azure Event Hubs with Kafka protocol, or AWS MSK – the adapter is compatible with all common Kafka distributions, as it uses the standardized Kafka protocol. Additionally, Confluent Platform on-premise with Schema Registry is fully supported.

How does Avro and Protocol Buffers support work?

The adapter supports Avro and Protocol Buffers natively, so binary data formats are directly translated into XML – and vice versa. Thanks to the integrated Schema Registry integration and the included schema generation tool, manual schema maintenance is eliminated. Meanwhile, JSON-to-XML transformation is also available out of the box.

How does installation and deployment work?

After starting the 30-day trial, you will receive access to the adapter within 48 hours. Installation in your SAP Integration Suite is completed in just a few steps, as the KaTe team supports you during onboarding. Initial productive scenarios typically start within a few days – without upfront investments or lengthy project phases.

What licensing models are available for the Confluent Parallel Consumer Adapter?

The KaTe Confluent Parallel Consumer Adapter is available as a flexible license based on your actual usage volume. After the free 30-day trial, you can choose between different licensing options. Contact us for an individual offer so we can find the right model for your requirements together.

Get Started Now

Ready for High-Throughput Kafka Integration?

Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.

Categories
SAP Products

Kafka Adapter for SAP PO

Kafka Adapter for SAP PO – SAP Integration | KaTe GmbH
SAP Adapter

Kafka Adapter
for SAP PO

Bidirectional SAP-Kafka integration – on-premise and in the SAP Integration Suite

Seamlessly connect SAP Process Orchestration with Apache Kafka. Publish and subscribe to PO messages as Kafka records, full security standards, in-order processing at key level and Avro/Protobuf support – without third-party tools.

Verified SAP Partner
30 days free trial
Worldwide Available
Verified SAP Partner
SASL/SSL Security
High-Performance & Resilience
Avro · Protobuf · JSON

All features of the KaTe Kafka Adapter for SAP PO

The KaTe Kafka Adapter for SAP PO provides a complete solution for bidirectional integration of your SAP system landscape with Apache Kafka – without dependency on third-party tools.

Core Functions: Publish & Subscribe

The adapter enables bidirectional publishing of PO messages as Kafka records and subscribing to Kafka records as PO messages. Kafka key, header, and data are translated into PO messages and vice versa.

  • Customizable topics, partitions, and ack mode/consumer commits
  • Fully integrated into SAP PO/NetWeaver functionality
  • Message processing observable without third-party tools

Enterprise-Standard Security

The adapter supports all common Kafka security standards and is therefore compatible with the security requirements of any enterprise.

  • PLAIN, PLAIN_SASL, SASL_SSL
  • SASL-Plain/SASL-SCRAM, Oauthbearer, Kerberos
  • Client Certificate Authentication

High Performance & Flow Control

Maintain full control over your message throughput and protect your backend systems from overload.

  • Filtering by headers, keys, and data content
  • Batch processing: n records as a single PO message
  • Polling interval and record count/time unit customizable

Full control during execution

Process records from the beginning or end of the stream or from any position – with full transparency over the consumer lag.

  • Processing and reprocessing of records
  • Deduplication via offset or record header
  • Group names freely definable (no vendor lock-in)
  • Consumer lag per sender channel without third-party tools

In-order processing at key/header level

High performance while maintaining message order down to the backend system. Faulty records do not block the entire stream.

  • EOIO support at partition and key level
  • Finer sorting within the partition at key/header level
  • Faulty ID isolated – all other records continue processing

Avro, Protobuf, JSON & Schema registries

Support for typical binary data formats with Kafka-specific optimizations. The adapter translates Avro and Protocol Buffers into XML and vice versa.

  • Avro and Protobuf ↔ XML transformation
  • Integrated schema generation tool
  • Schema registry support
  • JSON ↔ XML transformation

KaTe Launchpad – more control in building and operating Kafka scenarios

The KaTe Launchpad extends the Kafka adapter with an integrated toolbox that simplifies daily tasks for developers and operators – directly within the SAP environment, without external tools.

Generator

Automatic generation of Kafka configurations, schemas, and integration objects – saves development time and reduces errors.

Service list display & tester

Clear overview of all Kafka services with integrated test function – validate and debug scenarios directly from the interface.

Easy to start – flexible to scale

All KaTe adapters are designed to be quickly operational – from inquiry to productive operation.

1
Request free trial
Contact us by email or phone. We will set up your personal free trial within 48 hours.
Free · 30 days
2
Install adapter
Simple installation in your SAP PO or Integration Suite environment. No third-party tool required.
Plug & Play
3
Go live
Bidirectional SAP-Kafka integration running. Full control over topics, security, and message order.
Go Live
Why KaTe

Easy to start –
flexible to scale

All KaTe adapters are designed to be quickly operational and adapt to your requirements – on-premise and in the cloud.

No vendor lock-in – group names freely definable
No third-party tools required
SAP PO and SAP Integration Suite compatible
Worldwide available – global deployment
KaTe Launchpad – integrated tools for setup & operation

SAP roadmap compatible

The KaTe Kafka adapter is available for current and future SAP platforms. Protect your investments and migrate at your own pace.

SAP Process Orchestration (PO)

Full support for SAP PO. Existing interfaces can continue to be used without adjustment.

SAP Integration Suite (CPI)

Seamless migration from SAP PO to SAP Integration Suite. Developed interfaces continue to work without refactoring.

Migration flexibility

Set your own schedule. Investments in SAP PO integrations can be seamlessly transferred to the Integration Suite.

Frequently Asked Questions about the KaTe Kafka Adapter

Answers to the most important questions about the Kafka Adapter for SAP PO and the SAP Integration Suite.

The Kafka Adapter for SAP PO enables seamless bidirectional connection of your SAP system landscape to Apache Kafka, both on-premise and in the SAP Integration Suite. It facilitates the exchange of PO messages with Kafka records, including translation of Kafka Key, Header, and Data into SAP PO messages. This allows companies to efficiently integrate event-driven data streams into their SAP processes.
Yes, the Kafka Adapter supports all common Kafka security standards: PLAIN, PLAIN_SASL, SASL_SSL, SASL-Plain/SASL-SCRAM, Oauthbearer, Kerberos, as well as Client Certificate Authentication. This ensures the integration is compatible with the security requirements of any company and guarantees secure data exchange.
The Kafka Adapter offers powerful features such as batch processing, filtering by header, key, and data content, as well as adjustment of polling intervals and message count per time unit. This allows individual control of message throughput and performance optimization without overloading backend systems.
Yes, the adapter supports binary data formats such as Avro and Protocol Buffers as well as JSON. It enables translation of these formats into XML and vice versa. Thanks to an integrated schema registry and a schema generation tool, Avro and Protobuf schemas can be easily transformed – ideal for complex integration scenarios.
The Kafka Adapter is fully SAP roadmap compliant and available for both SAP PO and the SAP Integration Suite. Existing interfaces can be adopted without major adjustments. Companies can plan their migration strategy flexibly without high risks or unexpected costs.
The adapter ensures that message order (EOIO) is maintained down to the backend system. While Kafka topics guarantee order within a partition, the adapter enables even finer sorting at key and header level. Faulty messages do not block the entire stream but only the affected record.
With batch processing, filtering, throughput control, and polling interval settings, you maintain full control over your data flow. This helps to process messages selectively while optimally utilizing backend systems.
The adapter translates Avro and Protobuf data into XML and vice versa. With an integrated schema registry, schemas are automatically generated and managed, allowing binary formats to be seamlessly integrated into SAP PO processes.
Yes, the adapter is designed for high performance and resilience. Through batch processing, filtering, and flow control, scalable and stable processing of large data streams is ensured.
Yes, the adapter is SAP roadmap compliant and supports both current SAP PO environments and future developments of the SAP Integration Suite. This prepares companies well for upcoming technologies and integration strategies.

SAP Technology and Migration Consulting

The KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite – including the SAP Edge Integration Cell for hybrid integration scenarios.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell for hybrid integration scenarios
  • Technology-based strategy consulting – from cloud integration to API management
Request a consultation
SAP PO → Integration Suite

We support you in the migration – from analysis through architecture design to technical implementation.

Request now

Now test free for 30 days

Contact us by email or phone – we will set up your free trial and support you in the first steps.