com.sap.cds:cds-feature-event-hub
A CAP Java plugin that connects CAP's messaging service to 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, btp, so an application sends and consumes business events without coding against its API.
Connects CAP Java's messaging service to 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, btp, the default messaging offering on SAP BTP, so an application consumes and sends business events without coding against the Event Hub's own API. The Maven dependency cds-feature-event-hub goes into srv/pom.xml, and a messaging service is switched to it by setting its kind to event-hub in application.yaml. Deploying to Cloud Foundry needs an SAP Cloud Application Event Hub configuration that states the system namespace and a webhook URL, plus a trust relationship set up through SAP Cloud Identity Services. When cds-feature-ordcom.sap.cds:cds-feature-ordGenerates Open Resource Discovery (ORD) documents from a CAP Java application's model, a single entry point that a static metadata catalog or a runtime landscape inspection can read.sap official, cap is present too, the plugin's own Maven metadata notes that it optionally contributes content to it.
Facts
Where it sits
Who is behind it
In the atlas: maintains 10@cap-javamaintainerMarc BeckerContributes to this
In the atlas: contributes to 7@beckermarckevin-b-sapContributes to this
In the atlas: contributes to 1@kevin-b-sapLisa Julia NebelContributes to this
In the atlas: contributes to 15@lisajuliaMarkus BucherContributes to this
In the atlas: contributes to 1@markusbucherniemdaContributes to this
In the atlas: contributes to 4@niemdasjvansContributes to this
In the atlas: contributes to 45@sjvansThomas BonkContributes to this
In the atlas: contributes to 4@t-bonk7 contributors
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Java
As a package
- Where it runs
- Inside its host
- Distributed through
- Maven
Connections
Emitting and consuming business events across systems through brokers
Distributes business events between SAP cloud applications
Download
Where it sits in your app
Download
README
quoted from cap-java/cds-feature-event-hub under Apache-2.0, read
CDS plugin for SAP Cloud Application Event Hub
About this project
The com.sap.cds:cds-feature-event-hub dependency is
a CAP Java plugin that provides out-of-the box integration with SAP Cloud Application Event Hub.
Requirements and Setup
See Getting Started on how to jumpstart your development and grow as you go with SAP Cloud Application Programming Model.
SAP Cloud Application Event Hub
For details on how to use SAP Cloud Application Event Hub, please see the SAP Cloud Application Event Hub Service Guide.
CDS Plugin
The usage of CAP Java plugins is described in the CAP Java Documentation. Following this documentation this plugin needs to be referenced in the srv/pom.xml of a CAP Java project:
<dependency>
<groupId>com.sap.cds</groupId>
<artifactId>cds-feature-event-hub</artifactId>
<version>${latest-version}</version>
</dependency>The latest version can be found in the changelog or in the Maven Central Repository.
Overriding the CloudEvent source suffix
In multitenant scenarios the CloudEvent source is composed of the configured ceSource and, by default, the current tenant ID. If the tenant ID differs from the subaccount ID registered as the UCL system ID, an application can override the suffix per message by setting the eventhub.btp.subaccountId header when emitting the event:
Map<String, Object> headers = new HashMap<>();
headers.put("eventhub.btp.subaccountId", subaccountId);
// emit the event with these headersThe header is consumed by the plugin and is not included in the outgoing message. If it is absent or blank, the tenant ID is used as before.
Support, Feedback, Contributing
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
Security / Disclosure
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
Code of Conduct
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Licensing
Copyright 2025 SAP SE or an SAP affiliate company and cds-feature-event-hub contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
History
Features 2
Notes
Added
- Support overriding the CloudEvent
sourcesuffix per message via theeventhub.btp.subaccountIdheader, for multitenant scenarios where the tenant ID differs from the subaccount ID registered as the UCL system ID - Fix startup logs
Removed, Features 2, Changed 1, Fixes
Notes
Added
- Support emitting events for Event Hub Connectivity Plan
- Support for CAP Transactional Event Queues
Changed
- Improve logging during Event Hub Messaging Service initialization
Fixed
Removed
Others providing
Compare all 20 on the Event Mesh page →- 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-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
- cesar-sap/abap_kafka_rest_proxycesar-sap/abap_kafka_rest_proxyAn 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.independent, abapABAP connector to Kafka through the Confluent Kafka REST Proxyfrom ABAP
- 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
Flavors
“This artifact is a CAP Java plugin that provides out-of-the box integration with SAP Cloud Application Event Hub.” — com.sap.cds:cds-feature-event-hub-root — POM
History in the atlas
- Sets a CAP Java messaging service's `kind` to `event-hub`, so it sends and receives through SAP Cloud Application Event Hub instead of another broker, with no topics or queues for the application to declare.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-feature-event-hub- JSON
- /artifacts/cap-java-cds-feature-event-hub.json
- MCP
- Connecting an agent