SAP Integration Suite, Event Mesh
The event broker activated inside SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp: queues, topic subscriptions and webhook subscriptions, reached over AMQP, MQTT and HTTP.
SAP Integration Suite, Event Mesh publishes and consumes business events across applications through a message broker: events are stored in queues, a queue subscribes to one or more topics, and a webhook subscription delivers a queue's messages to a REST consumer without polling. An application reaches the broker through a message client, a service instance of the message-client plan, over AMQP, MQTT or HTTP. It is activated as a capability of SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp and is a different offering from the standalone 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, btp: SAP's scope page says one-to-one parity between the two is not in scope. Its documented limits are a 1 MB message, 2 GB of spool across all queues, 250 queues and 200 connections.
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 1
- Regions
- 38
Connections
Emitting and consuming business events across systems through brokers
Integration service on BTP with Cloud Integration and API Management
Download
Learn more
- Receive Events from Event Mesh of Integration Suite to CAP Node.js ApplicationsReceive Events from Event Mesh of Integration Suite to CAP Node.js ApplicationsWalks a CAP Node.js application through consuming events from SAP Integration Suite, Event Mesh: adding the messaging and xsuaa services with cds add, writing messaging.on handlers for named topics, and building and deploying the service as an MTA to Cloud Foundry. Documents a mismatch between Cloud Foundry's automatic queue provisioning and Event Mesh's management API, worked around by pointing the service key's management URI at a mock endpoint that always returns 201.KevinWang_ST_Consultancy, published 2026-02-13KevinWang_ST_Consultancy, SAP Community
- Getting Started with SAP Event Mesh: Concepts, Setup, and Best PracticesGetting Started with SAP Event Mesh: Concepts, Setup, and Best PracticesExplains SAP Event Mesh as SAP's managed messaging service and works through its core concepts: queues versus topics, publish-subscribe versus point-to-point delivery, and direct versus guaranteed messaging. A hands-on half wires a Solace event broker to SAP Cloud Platform Integration, with two iFlows publishing to and consuming from a queue and a topic over AMQP and HTTP REST.vvinay_kumar, published 2025-10-15vvinay_kumar, SAP Community
- Modern integration at TÜV Rheinland: APIs, events and cloud transformationModern integration at TÜV Rheinland: APIs, events and cloud transformationTÜV Rheinland's migration from SAP Process Orchestration to SAP Integration Suite with API-led connectivity and event-driven architecture, told through business cases. The abstract names what was used: the SAP Integration Suite, Event Mesh capability, API Management, generative AI for faster development and SAP Cloud ALM for monitoring. It states nothing about how any of them was used, so the edges rest on the names and on the Platform migration the story starts from. A TechEd 2026 session (Wednesday 28 October, Berlin), written here from SAP's abstract; the recording is not yet published.Manisha Debnath, Udo Paltzer, SAP TechEd — session catalogue
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
- 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
- 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
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-integration-suite-event-mesh- JSON
- /artifacts/btp-integration-suite-event-mesh.json
- MCP
- Connecting an agent