PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cesar-sap/abap_kafka_rest_proxy
An ABAP connector that produces and consumes data to and from Kafka through the Confluent Kafka REST Proxy, since SAP NetWeaver ABAP has no native Kafka client; tested on ABAP 7.5x.
SAP NetWeaver ABAP has no native Kafka client, so this connector reaches a broker through the Confluent Kafka REST Proxy instead, producing and consuming ABAP data over a subset of the proxy's v2 HTTP API. It targets SAP NetWeaver ABAP systems and has been tested on ABAP 7.5x, with most of it expected to run from 7.3x onwards. It installs into a system as an abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap repository.
Facts
Last pushLicenceApache-2.0
Where it sits
Lives in
Provides
Event MeshABAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).
Who is behind it
Cesar MartinCesar MartinMaintains this
In the atlas: maintains 2, contributes to 2@cesar-sapmaintainer
In the atlas: maintains 2, contributes to 2@cesar-sapmaintainer
Before choosing this
Signals
ActivityQuietNo published releases; repository quiet for 57 months
It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
Conditions
PolicySAP API Policy 4.2026a§ 2.2.2, 3, FAQ 12, FAQ 27, FAQ 38The connector is used to expose an SAP API to an external consumer, or as a pathway for systematic or large-scale extraction of SAP business data. Ordinary outbound event notifications or callbacks are out of scope as such.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
- § 3 Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
- § FAQ 12 Outbound interfaces. The accompanying FAQ distinguishes external consumption of SAP-provided services from outbound notifications or callbacks sent by an SAP system, which it places outside this policy's scope.
- § FAQ 27 Custom-developed APIs. Customer-namespace ABAP interfaces are not prohibited merely because they are custom, but their underlying SAP dependencies and usage pattern still determine whether the use aligns with the policy.
- § FAQ 38 Large-scale data access. Large-scale extraction and replication must use access mechanisms and patterns documented for that purpose rather than treating a transactional or custom API as a general bulk-data surface.
The connector runs as customer ABAP code and normally calls outward to Kafka, which does not by itself put that traffic in scope. Reassess the concrete use when it fronts SAP APIs or moves data systematically at scale: custom code does not turn a transactional interface into an unrestricted extraction path.
SAP API Policy 4.2026a →Also, from Event Mesh§ 2.2.2, 3, FAQ 12, FAQ 27, FAQ 38: Direction and usage pattern decide the policy relevance. Customer ABAP code may publish events outward, but it must not be used to bypass SAP API controls or substitute a custom event stream for a documented bulk-data pathway.
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- Inside its host
- Distributed through
- abapGit
Connections
Group by
NodeRelationBasis
Functional
Event MeshEvent MeshEmitting and consuming business events across systems through brokersSAP and community, narrow by design
provides
stated
provides Event Mesh
Produces and consumes ABAP data to and from Kafka through the Confluent Kafka REST Proxy's v2 HTTP API.
“This connector produces and consumes ABAP data to and from Kafka via the [Confluent Rest Proxy](https://docs.confluent.io/current/kafka-rest/docs/index.html).”
Emitting and consuming business events across systems through brokers
Download
README
quoted from cesar-sap/abap_kafka_rest_proxy under Apache-2.0, readcesar-sap/abap_kafka_rest_proxy/README.mdthe maintainer’s wordsOn GitHub
ABAP to Confluent Kafka REST Proxy Connector
Welcome to the ABAP to Kafka REST Proxy Connector.
This connector produces and consumes ABAP data to and from Kafka via the Confluent Rest Proxy. It implements a subset of the v2 API.
This connector is intended to be run on SAP NetWeaver ABAP Systems. It has so far only been tested in SAP ABAP 7.5x, but most of it should be fine from ABAP 7.3x onwards.
How to install
You need to have abapGit installed in your system. Once you have abapGit correctly set-up, just clone it into the system following abapGit instructions.
Set Kafka destinations
Examples
Comments
Others providing
Compare all 20 on the Event Mesh page →Event MeshEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to async processing.SAP and community, narrow by design
- SAP Integration Suite, advanced event meshSAP Integration Suite, advanced event meshAn event streaming, event management and monitoring platform for event-driven architecture, offered within SAP Integration Suite.sap official, btpEvent streaming and management platform in Integration Suitefrom BTP/BAIP
- SAP Cloud Application Event HubSAP Cloud Application Event HubDistributes the business events SAP cloud applications publish to the other SAP cloud applications in a landscape, with subscriptions managed in its own UI and no topics or queues to configure.sap official, btpDistributes business events between SAP cloud applicationsfrom BTP/BAIP
- Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btpManaged queues and topics over AMQP, MQTT and RESTfrom BTP/BAIP
- SAP Integration Suite, Event MeshSAP Integration Suite, Event MeshThe event broker activated inside SAP Integration Suite: queues, topic subscriptions and webhook subscriptions, reached over AMQP, MQTT and HTTP.sap official, btpEvent broker inside SAP Integration Suitefrom BTP/BAIP
- com.sap.cds:cds-feature-advanced-event-meshcom.sap.cds:cds-feature-advanced-event-meshA beta CAP Java plugin that adds SAP Integration Suite, advanced event mesh as a messaging broker, activated by setting a messaging service's kind to aem.sap official, capCAP Java plugin for SAP Integration Suite, advanced event meshfrom CAP
- com.sap.cds:cds-feature-enterprise-messagingcom.sap.cds:cds-feature-enterprise-messagingA CAP Java feature that connects a CAP messaging service to SAP Event Mesh, activated by setting the service's kind to enterprise-messaging, and looks up the bound instance.sap official, capConnects CAP Java messaging to SAP Event Meshfrom CAP
- com.sap.cds:cds-feature-event-hubcom.sap.cds:cds-feature-event-hubA CAP Java plugin that connects CAP's messaging service to SAP Cloud Application Event Hub, so an application sends and consumes business events without coding against its API.sap official, capConnects CAP Java messaging to SAP Cloud Application Event Hubfrom CAP
- com.sap.cds:cds-feature-kafkacom.sap.cds:cds-feature-kafkaA CAP Java feature that connects a CAP messaging service to Apache Kafka for intra-application messaging, through the Apache Kafka client library rather than a managed SAP messaging service.sap official, capConnects CAP Java messaging to Apache Kafkafrom CAP
- com.sap.cds:cds-feature-rediscom.sap.cds:cds-feature-redisA beta CAP Java feature that connects a CAP messaging service to Redis Pub/Sub, which broadcasts each event to every subscribed instance and does not guarantee delivery.sap official, capBeta connector from CAP Java messaging to Redis Pub/Subfrom CAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @cap-js/advanced-event-mesh@cap-js/advanced-event-meshIntegrates CAP with SAP Integration Suite advanced event mesh.sap official, capCAP integration with SAP Integration Suite advanced event meshfrom CAP
- @cap-js/asyncapi@cap-js/asyncapiExports AsyncAPI documents describing the events a CAP service emits and consumes.sap official, capExports AsyncAPI documents for a CAP service's eventsfrom CAP
- @cap-js/event-broker@cap-js/event-brokerConsumes events from SAP Cloud Application Event Hub.sap official, capConsumes events from SAP Cloud Application Event Hub in CAPfrom CAP
- cds-kafkacds-kafkaA Kafka adapter for CAP that registers Kafka topics as a CDS messaging service over KafkaJS, so emit and on work unchanged, with per-message keys, partitions and topics set through headers.independent, capKafka adapter exposing topics as a CDS messaging servicefrom CAP
- cds-event-monitoringcds-event-monitoringA CAP plugin that stores every event received on its configured messaging topics in a table, with a Fiori-annotated service to browse them, resend events and drain a dead-message queue.independent, capStores, browses and resends messages a CAP service receivesfrom CAP
- gregorwolf/AWS_SNS4ABAPgregorwolf/AWS_SNS4ABAPAn ICF handler that receives Amazon SNS notifications in an ABAP system as an HTTPS subscriber endpoint, leaving what happens to a notification once it arrives to the caller.independent, abapICF handler receiving Amazon SNS notifications in an ABAP systemfrom ABAP
- INVIXO/abapMQINVIXO/abapMQAn MQTT client implemented in ABAP, supporting protocol version 3.1.1, so an ABAP program can publish and subscribe to a broker; it requires ABAP 750sp01 and installs through abapGit.independent, abapMQTT 3.1.1 client implemented in ABAPfrom ABAP
- MQBAMQBAAn implementation of MQTT publish/subscribe in ABAP, with a broker inside the system built on ABAP Push Channels and ABAP Messaging Channels, and a bridge to external non-SAP brokers.independent, abapMQTT publish/subscribe in ABAP with an external broker bridgefrom ABAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, integration-and-messaging
abaplint
issues under its own abaplint configuration1,570
lines3,043
statements2,198
objects28
files16
analysed, master
abaplint version2.120.84
read fromabaplint.app,
History in the atlas
- First seen.
For your agent
- Ref
artifact:cesar-sap-abap-kafka-rest-proxy- JSON
- /artifacts/cesar-sap-abap-kafka-rest-proxy.json
- MCP
- Connecting an agent