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
News

Publish Many, Commit Once: Atomic Kafka Batches from SAP Integration Suite

Publish Many, Commit Once: Atomic Kafka Batches from SAP Integration Suite

Product Update

Publish Many, Commit Once: Atomic Kafka Batches from SAP Integration Suite

The KaTe Kafka Adapter can publish multiple records from one SAP Integration Suite exchange in a Kafka transaction — creating an atomic visibility boundary for consumers that use read_committed.

Publishing events one by one is simple, but it becomes expensive when an upstream application already owns a complete set of records. Every individual call repeats network, authentication, integration-flow, serialisation and acknowledgement overhead. More importantly, a partial failure can leave only part of a logical group visible in Kafka.

Atomic Receiver Batching in the KaTe Kafka Adapter for SAP Integration Suite addresses both concerns. One SAP Integration Suite exchange can publish multiple Kafka records in one Kafka transaction. A consumer configured with read_committed sees either the complete committed batch or none of an aborted batch.

The feature makes the publication contract explicit: one upstream request carries a meaningful business group, one Kafka transaction handles the complete batch, and the right consumer isolation level exposes all committed records or none of an aborted transaction.

One request, one transaction, many records

The receiver channel first parses and validates the complete batch envelope. It then borrows one producer exclusively, starts one Kafka transaction, serialises and sends every record, waits for all acknowledgements and commits the transaction. If processing fails before a confirmed commit, the transaction is aborted. Producers affected by fencing, transaction timeouts, ambiguous commit results or failed aborts are closed and recreated before reuse.

The feature supports three request styles:

Simple XML
For a sequence of value-only business elements.
Simple JSON array
For a value-only JSON batch.
Detailed XML
For per-record IDs, keys, headers, tombstones and controlled topic or partition overrides.

Every published record receives the correlation headers kate.batch.id, kate.batch.index and kate.batch.size. A detailed input can additionally provide a recordId, which becomes kate.event.id. The same batch contract can use the receiver channel’s configured Avro, JSON, JSON Schema or Protobuf value serialisation.

The performance effect of fewer integration calls

The first gain occurs before Kafka: one upstream request and one Cloud Integration exchange carry many records. To illustrate the possible scale, assume a four-partition topic with four concurrent upstream publishing lanes, an average single-record interaction of 50 ms and a 25-ms network share within that time.

Single record: 4 / 0.050 seconds = 80 records per second

If a batch of 100 can be accepted, transformed and committed in approximately the same 50 ms, the corresponding planning ceiling is 8,000 records/s, or 100× the single-record rate. That is the ideal bulk-processing case.

If the network cost is shared but 25 ms of transformation or application work remains for every item, a 100-record batch takes approximately 25 ms + 100 × 25 ms = 2,525 ms. Four lanes then deliver about 158 records/s, or 1.98×. A batch of 10 reaches about 145 records/s, or 1.82×.

ModelBatch sizeApproximate throughputGain
Single-record baseline180 records/s1×
Efficient bulk processing10800 records/s10×
Efficient bulk processing1008,000 records/s100×
Linear per-record work, shared network10145 records/s1.82×
Linear per-record work, shared network100158 records/s1.98×

This is an illustrative latency model rather than a product benchmark. On the receiver side, four Kafka partitions are distribution lanes, not a strict concurrency ceiling for a producer. Actual results depend on the configured parallel producer count, record and batch size, serialisation, broker acknowledgements, transaction latency, compression, worker-node resources and upstream concurrency.

Interpreting the 50-ms assumption

The 50 ms includes acknowledgement and commit. As with a JDBC batch, sharing fixed call and transaction overhead can make additional records relatively inexpensive, although Kafka timings must be measured separately. Even if 100 records take 100–200 ms, four active publishing lanes would deliver 2,000–4,000 records/s, or 25–50× the single-record baseline. These are illustrative scenarios; compare equivalent durability settings and include batch-collection time when measuring end-to-end latency.

One exchange can also reduce message consumption

Atomic Receiver Batching can reduce SAP Integration Suite message consumption as well as technical overhead. SAP’s current public pricing definition meters Cloud Integration messages in 250 KB blocks — not 256 KB: an outbound message up to 250 KB counts as one message, and each further 250 KB or fraction counts as another. For synchronous receiver calls, request and response sizes are considered together. Contract terms, included volume, SAP-to-SAP exclusions, retries and the structure of the deployed flow determine whether a reduction changes the actual bill. Refer to the current SAP Integration Suite pricing definition and verify the result in the tenant’s Message Usage dashboard.

As a simplified example, publishing 20 small records through 20 separate receiver exchanges normally produces at least 20 metered outbound messages. If one receiver exchange carries the complete atomic batch and its metered outbound size remains at or below 250 KB, it can count as one. A 600-KB batch counts as three 250-KB units rather than 20. Envelope data, replies, retries, splitters and other receiver calls must be included when estimating a real flow.

Atomic visibility, not exactly-once business processing

The delivery contract is atomic and at least once. Transactional visibility prevents a read_committed consumer from seeing a partial batch. It does not prevent an upstream retry from publishing the complete batch again as a new transaction after an uncertain client-side result. Downstream consumers should therefore use the batch ID, batch index, optional event ID or a stable business key for idempotent processing where duplicates matter.

Consumers that must honour the atomic boundary should select Read committed. A read_uncommitted consumer can observe records from open or aborted transactions and is unsuitable when the all-or-nothing contract is required.

Decision matrix: should the receiver publish atomically in batches?

Scenario or requirementFitGuidance
Upstream system already sends a coherent business groupStrongPreserve the group as one exchange and one Kafka transaction.
Bulk API, BI load, JDBC batch, OData $batch or multi-record file feeds KafkaStrongAvoid splitting a collection into many CPI exchanges before publishing.
Downstream consumers use read_committed and understand batch correlationStrongThey receive all committed records or none of an aborted transaction.
Per-record publication receipt is requiredStrongSelect the detailed reply to return topic, partition, offset and timestamp for every item.
Independent records with strict low-latency acknowledgementsWeakWaiting to assemble a batch adds latency and couples otherwise unrelated records.
A standard BAPI or SOAP operation produces only one object per callConditionalBatch publication helps only after the upstream side has intentionally assembled a meaningful collection.
Downstream consumers use read_uncommittedDo not use for atomic visibilitySuch consumers may observe records from open or aborted transactions.
End-to-end exactly-once business processing is requiredInsufficient on its ownKafka atomic visibility does not prevent a complete upstream retry from producing the batch again; keep processing idempotent.
One invalid record should not affect neighbouring recordsWeakAtomic publication deliberately aborts the whole batch; use smaller batches or single-record publication for error isolation.
Very large or highly variable recordsConditionalTest transaction timeouts and CPI, producer, broker and request-size limits with production-like data.

A receipt for every publication

The receiver can return no body, a summary or detailed record metadata. A summary confirms the generated batch ID, COMMITTED status and record count. A detailed reply additionally reports the topic, partition, offset and timestamp for every record, providing a precise publication receipt. Replies can be XML, JSON or match the request family.

KaTe Launchpad 1.0.6 or later can generate matching sender, receiver or interoperability batch contracts from the value schema. This avoids hand-maintained envelope definitions and keeps XML WSDL/XSD or JSON OpenAPI contracts aligned with the configured request and reply modes.

When to use atomic receiver batches

The feature is a strong fit for order groups, master-data packages, synchronised state changes or any upstream bulk interface where partial Kafka visibility would be misleading. Begin with batches that comfortably fit the broker and CPI payload limits, configure a transaction timeout that covers transformation, acknowledgement and commit, and increase Number of producers per worker node only when independent batches need to publish concurrently.

The result is more than fewer calls. It is a clear integration contract: the upstream system submits one logical group, Kafka exposes that group atomically, and the caller can receive a record-level publication receipt.

What this update means for SAP integration teams

These concise answers retain the technical boundaries of the update and improve retrieval in conventional and AI-assisted search.

What is Atomic Receiver Batching?

It publishes multiple records from one SAP Integration Suite exchange within one Kafka transaction, with simple and detailed input formats plus optional record-level publication evidence.

How do consumers preserve the atomic boundary?

Consumers that require all-or-none visibility must use read_committed and should use the batch correlation headers or stable business keys when idempotent processing is needed.

Is the measured throughput guaranteed?

No. The figures are illustrative planning scenarios. Validate performance against the specific producer settings, payloads, durability requirements, transaction timeouts, broker environment and upstream concurrency.

Atomic Kafka Batches from SAP Integration Suite

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

Categories
News

Kafka via SAP Cloud Connector

Kafka via SAP Cloud Connector (SCC)

Product Update

Kafka via SAP Cloud Connector: Secure Hybrid Access Without Compromises

The KaTe Kafka Adapter now connects private Kafka infrastructure through SAP Cloud Connector while preserving full TLS, SNI and hostname verification.

KaTe GmbH has expanded the KaTe Kafka Adapter for SAP Integration Suite with secure private-network connectivity through SAP Cloud Connector. The update enables SAP Cloud Integration and SAP Edge Integration Cell to access private Kafka environments without changing broker advertisements or weakening TLS security.

Kafka brokers, Schema Registry services and OAuth 2.0 identity providers can each use SAP Cloud Connector or the public network independently. Therefore, hybrid Kafka architectures can follow the network and security design that fits each individual service.

Secure hybrid Kafka connectivity for SAP Integration Suite

For organisations that run Apache Kafka in hybrid environments, private Kafka brokers, Schema Registry services and OAuth 2.0 identity providers can now be reached through SAP Cloud Connector where required. At the same time, each endpoint can continue to use the public network independently when that is the right architectural choice.

This matters because Kafka landscapes rarely follow a one-size-fits-all network model. An organisation may operate private Kafka brokers while using a public identity provider, or it may keep its Schema Registry in a separate network zone. The KaTe Kafka Adapter for SAP Integration Suite supports these combinations without forcing every Kafka-related service through the same connection path.

Apache Kafka brokers
SAP Cloud Connector or public network, with full TLS, SNI and hostname verification.
Schema Registry
SAP Cloud Connector or public network, independently configurable from broker access.
OAuth 2.0 identity provider
SAP Cloud Connector or public network, independently configurable from Kafka and Schema Registry access.

No custom broker advertisement rewriting and no TLS compromises

A frequent challenge in hybrid Kafka deployments is handling the broker addresses advertised to clients. The updated adapter avoids custom broker advertisement rewriting for SAP Cloud Connector connectivity. Consequently, teams do not need to introduce an additional address-translation layer simply to establish secure access from SAP Integration Suite to private Kafka services.

Equally important, the connection preserves TLS, Server Name Indication (SNI) and hostname verification. Established certificate validation therefore remains in place instead of being bypassed to make a hybrid connection work.

What this update clarifies for SAP integration teams

The following points are part of this product announcement. They explain the practical impact of the update rather than presenting a separate FAQ.

Can SAP Integration Suite reach a private Kafka broker through SAP Cloud Connector?

Yes. The KaTe Kafka Adapter can connect SAP Cloud Integration to private Kafka brokers through SAP Cloud Connector. The same capability is available for SAP Edge Integration Cell, enabling hybrid integration architectures that combine cloud-based integration with private Kafka services.

Do Kafka, Schema Registry and OAuth 2.0 identity providers have to use the same network route?

No. Each endpoint can be configured independently. Kafka brokers, Schema Registry services and OAuth 2.0 identity providers can use SAP Cloud Connector or the public network according to the organisation’s network architecture and security requirements.

Does private connectivity require weaker TLS validation or custom address rewriting?

No. The integration preserves full TLS, SNI and hostname verification. It also does not require custom broker advertisement rewriting for the SAP Cloud Connector connection path.

A practical option for SAP Cloud Integration and Edge Integration Cell

The enhancement is designed for SAP integration teams that need to connect SAP systems with event-driven Kafka platforms across cloud and private network boundaries. Whether an architecture uses SAP Cloud Integration, SAP Edge Integration Cell or a combination of both, the adapter enables a clear separation between integration logic and network-routing decisions.

The result is true hybrid Kafka connectivity: private where necessary, public where appropriate and consistently secured throughout.

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

Categories
Restful Adapter SAP Products

RESTful Adapter for SAP Integration Suite

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

RESTful Adapter for
SAP Integration Suite

Efficient integration and development of REST APIs with SAP Integration Suite and the Open API standard. OpenAPI 3.x, Swagger 2.0, OAuth2, JWT – development times drastically reduced.

Verified SAP Partner 30-Day Free Trial OpenAPI 3.x & Swagger 2.0 OAuth2 & JWT
Architecture Overview
SAP Cloud
Integration
Iflow
REST/HTTP
KaTe RESTful
Adapter
SAP CPI
OpenAPI
REST APIs
Cloud · On-Premise
EIC
OpenAPI 3.x Swagger 2.0 OAuth2 / JWT ABAP Proxy XCSRF-Token NTLM

REST APIs according to Open API Standard –
Development Times Drastically Reduced

The KaTe RESTful Adapter for SAP Integration Suite contains all necessary functions so that REST APIs according to the Open API standard can be implemented quickly, securely, and with low maintenance.

OpenAPI & Swagger
Since OpenAPI 3.x and Swagger 2.0 are fully supported, REST APIs according to the Open API standard can be integrated into SAP Integration Suite without time-consuming custom development.
  • OpenAPI 3.x fully supported
  • Swagger 2.0 kompatibel
  • Automatische API-Beschreibung
  • Automatic JSON/XML translation
Sicherheit & Authentifizierung
Because enterprise environments have the highest security requirements, all common authentication methods are supported – for both cloud and on-premise scenarios.
  • OpenID / JWT Authentifizierung
  • OAuth2 (Cloud & On-Premise via Cloud Connector)
  • NTLM-Authentifizierung
  • Blocking of non-compliant API calls
ABAP Proxy Generation
Existing ESR objects can be used as Open APIs with just a few clicks, so ABAP Proxies are generated directly from Open API definitions – without time-consuming new development.
  • ABAP Proxies from Open API definitions
  • Reuse ESR objects as Open APIs
  • API-First development supported
  • Etablierte ABAP-Frameworks nutzbar
Monitoring & Debugging
All API operations and statuses are searchable and visible without overhead through automatic indexing of key/values in the SAP Integration Suite Monitor.
  • Automatisches API-Operationen-Indexing
  • HTTP status codes in the monitor
  • OAuth2 calls fully traceable
  • Integrated testing and generation
OData & SAP-Spezifika
Automatic XCSRF token management and link rewriting to frontend URLs – OData clients can use SAP APIs without SAP specifics.
  • Automatisches XCSRF-Token-Handling
  • Link rewriting to frontend URLs
  • OData in API management solutions
  • SAP specifics transparent for clients
Simple Migration from SAP PO
Open APIs from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow, so existing investments are fully preserved.
  • 1:1 migration from SAP PO
  • Reuse ESR content as Open APIs
  • No time-consuming new development
  • Custom migration plan possible

Typical Use Scenarios

The KaTe RESTful Adapter for SAP Integration Suite solves the most common challenges in REST API integration with SAP – whether in the cloud, on-premise, or in hybrid environments.

API-First Development
Bridge between old and new world

Software development is increasingly shifting to mobile platforms, hyperscalers, or container environments. These rely on the Open API standard for API management, security (JWT, OAuth2), and automation.

Our adapter facilitates the integration of SAP into API-first strategies of the non-SAP world – whether in SAP BTP, with hyperscalers like AWS, Azure, or GCP, or in containerized development environments.

Regulated Industries
Open APIs in Telecommunications, Banking & Energy

Regulated industries such as telecommunications (TMF), banking (Open Banking), or utilities (market data exchange) rely on standardized Open APIs. Our approach significantly reduces the development and operating costs of such APIs – while utilizing existing developer skills and requiring minimal investments.

With the KaTe RESTful Adapter, you maximize the efficiency and security of your API integrations, protect existing investments, and build seamless bridges between SAP and modern API standards – to meet the increasing demands for integrating modern technologies and drive your digital transformation forward.

OData Integration
OData in Hybrid Enterprise Architectures

SAP has strongly committed to OData over the years, which can be described via Open API definitions. However, the following challenges often arise in hybrid environments or API management solutions:

  • › SAP Specifics: Clients have to deal with XCSRF token management or SAP-specific attributes.
  • › Internal Links: API management solutions deliver responses with internal links, which poses security risks and makes use by OData clients difficult.

The KaTe RESTful Adapter solves these problems efficiently: Links are automatically rewritten to frontend URLs, and XCSRF tokens are processed automatically.

Why the KaTe RESTful Adapter
is the right choice

REST APIs according to the Open API standard with SAP Integration Suite – without time-consuming custom development, without maintenance costs, with complete security and visibility.

1
Drastically Reduced Development Times
JSON/XML translation, HTTP status routing, and API description in minutes instead of hours. Existing ESR objects become Open APIs with just a few clicks, so teams can work productively right away.
2
Complete Security & Transparency
OAuth2 calls are fully traceable – no black box. Because non-compliant API calls are automatically blocked, OpenID/JWT, custom OAuth2, and NTLM are seamlessly secured.
3
Simple Migration from SAP PO
Existing Open APIs from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow. This fully preserves investments.
4
Economic Advantages
Reduction of development costs through shortened development times and use of existing skills. Since ESR content is reused as Open APIs, costly new development is eliminated.

KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
OpenAPI 3.x & Swagger 2.0
✓ Yes
Limited
ABAP Proxy Generation
✓ Yes
✗ No
OAuth2 via Cloud Connector
✓ Yes
Limited
Automatic XCSRF Token Handling
✓ Yes
✗ No
API Operations Indexing
✓ Yes
✗ No
Migration from SAP PO (1:1)
✓ Yes
✗ No
OAuth2 fully traceable
✓ Yes
✗ No

Get started easily – scale flexibly

1
Request Free Trial

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

2
Install Adapter

Since the installation in your SAP Integration Suite only requires a few steps, our team will support you during onboarding – so you can be productive quickly.

3
Go Live

Initial productive scenarios run quickly. Scale as needed – without upfront investments.

Supported Platforms & Standards

Whether SAP BTP, Edge Integration Cell, or hyperscalers – the KaTe RESTful Adapter is compatible with all common API standards and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP BTP
SAP Business Technology Platform – cloud-native
Supported
SAP Edge Integration Cell
Hybride On-Premise/Cloud-Szenarien
Supported
OpenAPI 3.x
Current Open API standard for REST APIs
Supported
Swagger 2.0
Weit verbreiteter API-Beschreibungsstandard
Supported
AWS / Azure / GCP
Hyperscaler REST APIs and API management
Supported
OData
SAP OData services with automatic XCSRF handling
Supported
ABAP / SAP ERP
ABAP Proxy generation from Open API definitions
Supported

KaTe Launchpad – more control during setup and operation

The KaTe Launchpad extends the RESTful Adapter with an integrated toolbox for developers and operations teams – directly usable from within the SAP Integration Suite.

Generator

Automatic generation of OpenAPI definitions, ABAP Proxy structures, and SAP Integration Suite Iflow channel configurations from existing ESR objects – significantly reducing configuration effort.

Service List Display & Tester

Overview of all configured REST API endpoints, HTTP methods, and authentication configurations. While the tester sends REST requests directly from the SAP Integration Suite, all results are immediately visible.

SAP Technology and Migration Consulting –
Future-Proof Integration

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.

  • 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 RESTful interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite – ensuring continuous operation.

Learn more
SAP PO Adapter – 30-Day Free Trial
All SAP PO Adapters Without Upfront Payment

Test our SAP PO adapters for Kafka, MQTT, AMQP, AWS, RESTful and more – 30 days free of charge.

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 – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

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

What is the KaTe RESTful Adapter for SAP CPI?

As a powerful middleware component, the KaTe RESTful Adapter for SAP Integration Suite connects SAP systems with REST APIs according to the Open API standard. It supports OpenAPI 3.x and Swagger 2.0 and enables 1:1 migration of existing interfaces from SAP Process Orchestration – drastically reducing development times.

What advantages does the adapter offer in API development?

The adapter offers the following development advantages:

  • Drastically reduced time required for JSON/XML translation and HTTP status routing
  • Existing ESR objects become Open APIs with just a few clicks
  • ABAP Proxies can be generated from Open API definitions (API First)
  • Established frameworks like ABAP Proxy generation and monitoring can continue to be used
Is the adapter compatible with SAP BTP and hybrid landscapes?

Yes. The adapter supports OAuth2 endpoints on the public internet as well as on-premise via SAP Cloud Connector. It is fully compatible with SAP BTP, SAP Cloud Integration, and the SAP Edge Integration Cell. Hyperscalers like AWS, Azure, and GCP are directly supported.

How does security work in the RESTful Adapter?

Because security is a top priority in enterprise environments, the adapter blocks non-compliant API calls and supports:

  • OpenID / JWT Authentifizierung
  • Custom OAuth2 (cloud and on-premise via Cloud Connector)
  • NTLM-Authentifizierung

This makes OAuth2 calls fully traceable – no black box. All authentication flows are visible in the SAP Integration Suite Monitor.

How are monitoring and debugging implemented?

All API operations and statuses are searchable and visible without overhead through automatic indexing of key/values of API operations in the SAP Integration Suite Monitor. HTTP status codes, OAuth2 flows, and API endpoints can be viewed directly in the monitor – without additional configuration.

Which SAP platforms are supported?

The KaTe RESTful Adapter runs on all current SAP platforms:

  • SAP Integration Suite (Cloud Integration / CPI)
  • SAP Business Technology Platform (BTP)
  • SAP Edge Integration Cell (EIC) – for hybrid on-premise/cloud scenarios
  • SAP Process Orchestration (PO) – via the separate SAP PO version of the adapter
How does ABAP Proxy generation work?

With the KaTe Launchpad Generator, ABAP Proxy structures can be generated directly from Open API definitions. Existing ESR objects from SAP PO can be used as a basis, so no new development is required. The generated proxies are fully compatible with SAP ABAP development environments.

How does automatic XCSRF token handling work?

SAP OData services require XCSRF tokens for write operations. The KaTe RESTful Adapter handles token management fully automatically, so OData clients can use SAP APIs without SAP-specific knowledge. Internal links are rewritten to frontend URLs in the process.

How does the installation and commissioning work?

Installation takes place in just a few steps directly in your SAP Integration Suite. After requesting the 30-day trial, you will receive access to the adapter within 48 hours. Our team will support you during onboarding, so initial productive scenarios run quickly.

What licensing models are available for the RESTful Adapter?

The KaTe RESTful Adapter is available with a 30-day free trial – after that, flexible licensing models are available. Because every corporate environment has different requirements, we would be happy to advise you individually on licensing options and prices. Contact us at info@kate-group.com.

Get Started Now

Ready for REST APIs in the SAP Integration Suite?

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

Categories
SAP Products

AWS Adapter for SAP PO

AWS Adapter for SAP PO – Amazon SQS, SNS, S3, Lambda Integration | KaTe GmbH
Cloud / AWS Adapter

AWS Adapter for SAP PO

Amazon Web Services Integration for SAP Process Orchestration

The KaTe AWS Adapter connects SAP PO with the key AWS services: SQS, SNS, S3, Lambda, Kinesis, EventBridge, DynamoDB and more. Handles AWS authentication, security, and API calls within the SAP PO context.

Verified SAP Partner 30 Days Free Trial Available Worldwide
SQS, SNS, S3, Lambda
AWS IAM Authentication
Kinesis & EventBridge
XML / JSON Transformation

AWS Adapter – All Features

Powerful features for professional SAP integration in enterprise environments – deployable worldwide.

AWS Service Coverage

Access the key AWS services directly from SAP PO.

  • AWS SQS (Simple Queue Service)
  • AWS SNS (Simple Notification Service)
  • AWS S3 Storage
  • AWS Lambda, Kinesis, EventBridge

AWS IAM Authentication

Secure authentication via AWS IAM without manual credential management.

  • AWS Signature V4
  • IAM Roles & Policies
  • Temporary Security Tokens (STS)
  • Cross-Account Access

Event-Driven Integration

Processing AWS events in real-time directly within SAP PO processes.

  • AWS EventBridge Events
  • AWS Cloudwatch Events
  • AWS Kinesis Data Streams
  • AWS Kinesis Data Firehose

XML / JSON Transformation

Automatic transformation between SAP PO XML and AWS JSON formats.

  • JSON to XML Transformation
  • XML to JSON Transformation
  • AWS-specific Data Formats
  • Custom Mapping

DynamoDB & AppSync

Direct access to AWS database services and GraphQL APIs.

  • AWS DynamoDB CRUD
  • AWS AppSync (GraphQL)
  • AWS API Gateway
  • Batch Operations

SAP PO Integration

Complete integration into the SAP Adapter Framework.

  • SAP PI/PO Design Tools
  • Configuration & Monitoring
  • SAP Integration Suite ready
  • Migration path from SAP PO

KaTe Launchpad – More than just an adapter

The KaTe Launchpad extends the adapter with additional tools that significantly simplify the development and operation of AWS scenarios.

Generator

Automatic generation of AWS API configurations, IAM policy templates, and SAP PO channel definitions for all supported AWS services.

Service List Display & Tester

Overview of all configured AWS service connections. Integrated tester for sending and receiving AWS messages directly from SAP PO.

Start easily – scale flexibly

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 PO environment in a few steps. Our team supports you during onboarding.

3

Go Live

First productive scenarios run quickly. Scale as needed – without upfront investments.

All KaTe adapters are designed to be ready for use quickly – from inquiry to productive operation.

Request Free Trial now

AWS Adapter – Compatibility

The AWS adapter is available for all current SAP PO versions and compatible target systems.

SAP Process Orchestration (PO/PI)

  • SAP PI 7.x and SAP PO 7.5x
  • All current Support Packages
  • AWS IAM Authentication
  • XML/JSON Transformation

AWS Services

  • SQS, SNS, S3, Lambda
  • Kinesis, EventBridge, Cloudwatch
  • DynamoDB, AppSync, API Gateway
  • AWS Signature V4 Auth

Frequently Asked Questions about the AWS Adapter

What is the KaTe AWS Adapter for SAP PO?

The KaTe AWS Adapter enables seamless integration of SAP PO with key Amazon Web Services. It handles authentication, security, and API calls within the SAP PO context and supports SQS, SNS, S3, Lambda, Kinesis, EventBridge, and more.

Which AWS services are supported?

The adapter supports: AWS SQS, SNS, S3 Storage, Lambda, EventBridge, Cloudwatch Events, Kinesis Data Streams, Kinesis Data Firehose, DynamoDB, AppSync, and API Gateway.

How does AWS authentication work?

The adapter uses AWS Signature V4 and IAM roles for secure authentication. Temporary Security Tokens (STS) and cross-account access are also supported.

Are XML and JSON messages supported?

Yes, the adapter provides automatic transformation between SAP PO XML and AWS JSON formats. AWS-specific data formats and custom mapping are also possible.

Can the adapter process Kinesis Data Streams?

Yes, the adapter supports AWS Kinesis Data Streams and Kinesis Data Firehose for processing real-time data streams directly in SAP PO.

Is the adapter compatible with SAP Integration Suite?

Yes, the AWS adapter is available for SAP PO and the SAP Integration Suite. Existing interfaces can be migrated with minimal effort.

How can I test the adapter?

KaTe offers a free 30-day trial. Contact us via kate-group.de/kontakt/ to test the adapter in your environment.

Does the adapter support AWS DynamoDB?

Yes, the adapter enables CRUD operations on AWS DynamoDB as well as access to AWS AppSync (GraphQL) and API Gateway.

Which security standards are followed?

The adapter uses AWS IAM for authentication and supports SSL/TLS encryption for all connections. AWS security best practices are fully adhered to.

Does KaTe GmbH also offer AWS consulting?

Yes, KaTe GmbH offers SAP-AWS integration consulting – from architecture planning to implementation and optimization of your AWS integration landscape.

AWS Integration and SAP Migration

KaTe GmbH supports you in planning and implementing your AWS integration strategy – from initial analysis to productive operation.

Consulting Services

KaTe GmbH supports you in planning, implementing, and operating your SAP integration landscape – from initial analysis to go-live.

Request Consultation

30 Days Free
Test AWS Adapter

Test the KaTe AWS Adapter free for 30 days in your own SAP PO environment. No risk, no prepayment.

Categories
SAP Products

AMQP Adapter for SAP PO

AMQP Adapter for SAP PO – RabbitMQ, Azure Service Bus Integration | KaTe GmbH
Messaging / AMQP Adapter

AMQP Adapter for SAP PO

Bidirectional AMQP Integration for SAP Process Orchestration

The KaTe AMQP Adapter connects SAP PO with AMQP-based message brokers (RabbitMQ, Azure Service Bus, Apache Qpid). Supports AMQP 0-8-0, 0-9-0, 0-9-1 and 1.0, SSL/TLS, virtual hosts as well as publish/subscribe and request/reply patterns.

Verified SAP Partner 30 Days Free Trial Available Worldwide
AMQP 0-8 / 0-9 / 1.0
SSL / TLS Encryption
Virtual Hosts Support
Pub/Sub & Request/Reply

AMQP Adapter – All Features

Powerful features for professional SAP integration in enterprise environments – deployable worldwide.

AMQP 1.0 Compatibility

Full support of the AMQP 1.0 standard as well as older versions for maximum compatibility.

  • AMQP 0-8-0, 0-9-0, 0-9-1 and 1.0
  • Compatible with RabbitMQ, OpenAMQ, Apache Qpid
  • Seamless integration with Azure Service Bus
  • Automatic protocol negotiation

Security & SSL

Robust security mechanisms for use in enterprise environments.

  • SSL/TLS Encryption
  • Virtual Hosts for isolation
  • Username/Password Authentication
  • Client Certificates

Flexible Messaging Patterns

Publish/Subscribe and Request/Reply without complex module configurations.

  • Pub/Sub and Request/Reply
  • Async/Sync bridge integrated
  • Dead Letter Queue handling
  • Message TTL configuration

XML & JSON Payloads

Automatic transformation between XML and JSON for maximum interoperability.

  • JSON to XML transformation
  • XML to JSON transformation
  • Binary payload support
  • Custom serializer

SAP PI/PO Framework

Full integration into the SAP Adapter Framework for design, configuration, and monitoring.

  • SAP PI/PO Design Tools
  • Configuration & Monitoring
  • SAP Integration Suite ready
  • Migration path from SAP PO

Scalability & Decoupling

Message-oriented middleware for cloud, IoT, and mobile scenarios.

  • Horizontal scaling
  • Application decoupling
  • Cloud & IoT support
  • High throughput

KaTe Launchpad – More than just an adapter

The KaTe Launchpad extends the adapter with additional tools that significantly simplify the setup and operation of AMQP scenarios.

Generator

Automatic generation of AMQP configurations, queue definitions, and SAP PO channel definitions. Significantly reduces configuration effort.

Service list display & tester

Overview of all configured AMQP queues and broker connections. Integrated tester for sending and receiving AMQP messages directly from SAP PO.

Start easily – scale flexibly

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 PO environment in a few steps. Our team supports you during onboarding.

3

Go productive

First productive scenarios run quickly. Scale as needed – without upfront investments.

All KaTe adapters are designed to be ready for use quickly – from inquiry to productive operation.

Request free trial now

AMQP adapter – compatibility

The AMQP adapter is available for all current SAP PO versions and compatible target systems.

SAP Process Orchestration (PO/PI)

  • SAP PI 7.x and SAP PO 7.5x
  • All current support packages
  • AMQP 0-8-0, 0-9-0, 0-9-1 and 1.0
  • SSL/TLS and virtual hosts

SAP Integration Suite (CPI / EIC)

  • SAP Cloud Platform Integration (CPI)
  • SAP Edge Integration Cell (EIC)
  • Migration path from SAP PO
  • Azure Service Bus compatible

Frequently asked questions about the AMQP adapter

What is the KaTe AMQP adapter for SAP PO?

The KaTe AMQP adapter enables seamless integration of SAP PO with AMQP-based message brokers such as RabbitMQ, Azure Service Bus, and Apache Qpid. It supports AMQP 0-8-0, 0-9-0, 0-9-1, and 1.0 as well as bidirectional message exchange.

Which AMQP versions are supported?

The adapter supports AMQP 0-8-0, 0-9-0, 0-9-1, and the latest AMQP 1.0 standard. This ensures maximum compatibility with all common AMQP brokers.

Can the adapter be used with Azure Service Bus?

Yes, the AMQP adapter is fully compatible with Azure Service Bus and enables smooth integration of your SAP systems with the Azure cloud infrastructure.

What security features does the adapter offer?

The adapter supports SSL/TLS encryption as well as virtual hosts for access control. Username/password authentication and client certificates are also supported.

Are XML and JSON messages supported?

Yes, the adapter processes XML and JSON payloads and offers automatic, forward- and backward-compatible transformations between these formats.

Is the adapter compatible with SAP Integration Suite?

Yes, the AMQP adapter supports SAP Integration Suite and enables easy migration from SAP PO without complex adjustments.

How does the request/reply pattern work?

The adapter supports synchronous and asynchronous request/reply communication without complicated module configuration. Correlation ID handling and timeout configuration are integrated.

Which message brokers are supported?

The adapter is compatible with RabbitMQ, Azure Service Bus, Apache Qpid, and all other AMQP-compliant brokers.

How can I test the adapter?

KaTe offers a free 30-day trial. Contact us via kate-group.de/kontakt/ to test the adapter in your environment.

Does KaTe GmbH also offer consulting?

Yes, KaTe GmbH offers comprehensive SAP consulting services – from architecture planning to implementation of your AMQP integration landscape.

AMQP integration and SAP migration

KaTe GmbH supports you in planning and implementing your AMQP integration strategy – from initial analysis to productive operation.

Consulting services

KaTe GmbH supports you in planning, implementing, and operating your SAP integration landscape – from initial analysis to go-live.

Request Consultation

30 Days Free
Test AMQP Adapter

Test the KaTe AMQP Adapter free for 30 days in your own SAP PO environment. No risk, no prepayment.

Categories
News

KaTe Confluent Parallel Consumer Adapter for SAP IS

KaTe Confluent Parallel Consumer Adapter for SAP Integration Suite

Die KaTe GmbH hat einen Adaper für Apache Kafka by Confluent entwickelt für maximale Messages Übertragung auf der SAP Integration Suite

SAP integrations are great — until throughput becomes the bottleneck!

The Confluent Parallel Consumer Adapter for SAP Integration Suite (incl. Edge Integration Cell) enables massively parallel Kafka consumption for high-throughput scenarios.

Key highlights:
– Parallel processing (down to record-key level, optional without ordering)
– Avro / Protobuf / JSON + Schema Registry support, incl. transformations and XML schema generation
– Fully traceable & debuggable in the iFlow context
– Modern Kafka security options (e.g., SASL, OAuth2, client certificates)

For mor Details: Confluent Parallel Consumer Adapter for SAP Integration Suite

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