ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished 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 →
Event Mesh
Managed queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.
Where it sits
Lives in
Provides
Event MeshCAPBTPEvent 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).Async processingCAPBTPAsync processingDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.
Serves
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from Async processingA covered CAP application sends SAP product data through an external broker where it is copied, saved or processed in a non-SAP product.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
Messaging is not automatically mass extraction, but an external broker can cross the boundary named in section 1. The data flow, volume and interoperability purpose therefore need to be checked for the concrete design.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 1
- Regions
- 39
- Support component
- BC-CP-EM-MESOPU-GW-OD-MES
Connections
Group by
NodeRelationBasis
Functional
Async processingAsync processingDoing work outside the request that triggered it, with retriesSAP and community, narrow by design
provides
authored
provides Async processing
Doing work outside the request that triggered it, with retries
Event MeshEvent MeshEmitting and consuming business events across systems through brokersSAP and community, narrow by design
provides
authored
provides Event Mesh
Emitting and consuming business events across systems through brokers
Technical
com.sap.cds:cds-feature-enterprise-messagingcom.sap.cds:cds-feature-enterprise-messagingConnects CAP Java messaging to SAP Event Meshsap official, cap
optionally used by
derived
optionally used by com.sap.cds:cds-feature-enterprise-messaging
A messaging service is configured with kind enterprise-messaging.
“SAP Event Mesh is declared as the message broker to use.”
Connects CAP Java messaging to SAP Event Mesh
btp-abap-cnabtp-abap-cnaRAP bonus-calculation extension across Cloud Foundry, ABAP and Kymasap official, abap
used by
derived
used by btp-abap-cna
The bonus calculation scenario reaches [Event Mesh](artifact:btp-event-mesh) among the additional BTP services it consumes, and the sample's own requirements list an Event Mesh entitlement on the subaccount before it runs.
“Event Mesh service entitlement”
RAP bonus-calculation extension across Cloud Foundry, ABAP and Kyma
Download
Learn more
Readings
- SAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhooksSAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhooksA step-by-step walkthrough of wiring Event Mesh to publish and consume events between an on-premise S/4HANA system and Cloud Integration, contrasting persistent queues (one subscriber, kept until consumed) against unpersisted topics, and WebSocket's AMQP transport against webhook delivery for the same queue. Two tested findings support it: a queue consumer running in continuous consumption mode receives a message ahead of a webhook on the same topic, and a message stays queued and is retried (almost 8770 times in under a minute, in the author's test) until the consumer processes it successfully.FarooqAhmed, published 2023-10-03FarooqAhmed, SAP Community
What’s New
from SAP Help Portal, readhelp.sap.com/whats-new, Event MeshSAP’s wordsOn SAP Help Portal
18 entries from to , counted per month.
Health Monitoring on CALM Dashboard
Monitoring Connections
Health Monitoring on CALM Dashboard
Export Configuration button on the Overview screen.
Migration to SAP Integration Suite, advanced event mesh
New Fields for Messages
New Role Collection
Message Monitoring
Monitoring for Queues
Support for MQTT Protocol
Event Mesh Bridge
Test Messaging
Specify parameters in JSON file when configuring a message client.
Support for HTTP Protocol
Creating Webhook Subscriptions
View Message Clients in Integration Suite UI
Event Mesh Capability is Now Generally Available
No New Content
Others providing
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 Suite
- 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 mesh
- 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 Mesh
- 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 Hub
- 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 Kafka
- 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/Sub
- 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 versions
- @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 mesh
- @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 events
- @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 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 service
- 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 receives
- @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 runtime
Async processingAsync processingDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.SAP and community, narrow by design
- 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 versions
- @cap-js-community/event-queue@cap-js-community/event-queueTransactional processing of asynchronous and periodic events, with instant dispatch over Redis Pub/Sub and load spread across every application instance.community org, capTransactional processing of asynchronous and periodic CAP events
- @cap-js-community/sap-afc-sdk@cap-js-community/sap-afc-sdkSDK for building SAP Advanced Financial Closing scheduling providers on CDS.community org, capSDK for SAP Advanced Financial Closing scheduling providers on CDS
- 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 receives
- @odatano/watch@odatano/watchWatches Cardano addresses, payment credentials and minting policies from inside CAP, emitting events with full UTxO payloads and persisting them so a missed window can be replayed.independent, capCAP plugin watching Cardano addresses and emitting events
- @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 runtime
- cds-natscds-natsNATS as a messaging service for the CAP Node.js runtime, the broker behind cds.connect for emit and subscribe, for teams already running NATS rather than Event Mesh or Redis.independent, capNATS messaging service for the CAP Node.js runtime
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 viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-event-mesh- JSON
- /artifacts/btp-event-mesh.json
- MCP
- Connecting an agent