SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Starting point

SAP-samples/event-hub-cap-samples

A CAP consumer wired to SAP Cloud Application Event Hub, which has to be deployed to SAP BTP before events arrive, exposing the received events through an OData V4 service.

Connecting a CAP application to SAP Cloud Application Event Hub only works once it is deployed, since the Event Hub cannot reach a project running locally, and this sample is configured for exactly that path: build, deploy to SAP BTP with cf login --sso and npm run deploy, and the events arrive. Once deployed, received events are exposed through an OData V4 service at /odata/v4/cloud-event/Events. It stops at consumption: there is no publishing side, and the README points to a companion SAP PRESS book for the wider event-driven-integration picture rather than restating it.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Event MeshCAPEvent MeshcapabilityEmitting 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

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerAntonio MaradiagaPersonContributes to this
Developer Advocate
In the atlas: contributes to 10
@ajmaradiaga
1 contributor

What it declares

Every artifact

Type
Sample
Origin
By SAP

As a sample

Form
A reference application

Connections1

SAP-samples/event-hub-cap-samples connectionsSAP-samples/event-hub-cap-samplesPROVIDES→ demonstrates1demonstrates authoredEvent Mesh

ArchitectureBetaRead from the sample's deployment descriptor. Some of the connections it states are not drawn yet.

as mta.yaml states it at b7e2456, read
SAP BTP, Cloud Foundry Runtimecap.ssffceconsmta.yaml, module ssffcecons-srv, requires ssffcecons-iasbindingOpenID Connect, HTTP, outboundmta.yaml, module ssffcecons-srv, requires ssffcecons-xsuaabinding, HTTP, outboundmta.yaml, module ssffcecons-destination-content, requires ssffcecons-srv-apissffcecons-srv-apidocumentedOpenID ConnectCloud Identity Services, identity, applicationCloud IdentityServicesSAP Authorization and Trust Management service, xsuaa, applicationSAP Authorizationand TrustManagement servicessffcecons-srv, nodejsssffcecons-srvssffcecons-destination-content, com.sap.application.contentssffcecons-destinati…teched2025sfevents, html5teched2025sfeventsssffcecons-app-content, com.sap.application.contentssffcecons-app-conte…SAP Application Logging service for SAP BTP, application-logs, liteSAP ApplicationLogging servicefor SAP BTPSAP Destination service, destination, liteSAP DestinationserviceSAP Cloud Application Event Hub, event-broker, event-connectivitySAP CloudApplication EventHubSAP HTML5 Application Repository service for SAP BTP, html5-apps-repo, app-hostSAP HTML5ApplicationRepository servicefor SAP BTP
SAPnot SAP's, or the project's ownauthenticationtruststated in the documentdocumented only

Bound, and not drawn

Documented, with no instance in the document

README

quoted from SAP-samples/event-hub-cap-samples under Apache-2.0, read
SAP-samples/event-hub-cap-samples/README.mdOn GitHub

Cloud Event Consumer

REUSE status


This is a sample CAP application configure to easily connect to SAP Cloud Application Event Hub for SAP cloud applications.

Unfortunately, it is not possible to connect SAP Cloud Application Event Hub to a project running locally. The project will need to be deployed to SAP BTP in order to connect to SAP Cloud Application Event Hub.

Next Steps

Open a new terminal and run the following commands

# Login to CloudFoundry
$ cf login --sso

# Build and deploy to BTP
$ npm run build
$ npm run deploy

# To clean up resources
$ npm run undeploy

To access the OData services, navigate to https://.cfapps..hana.ondemand.com/odata/v4/cloud-event/Events

Learn More

Learn more at https://www.sap-press.com/developing-event-driven-integrations-with-sap-btp_6021/.

How to obtain support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/event-hub-cap-samplestree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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 domaincap, integration-and-messaging
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-event-hub-cap-samples
JSON
/artifacts/sap-samples-event-hub-cap-samples.json
MCP
Connecting an agent