onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
ServiceServicetypeA 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 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 →

SAP Integration Suite, Event Mesh

The event broker activated inside SAP Integration Suite: 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 Suite and is a different offering from the standalone Event Mesh: 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.

Docs

Where it sits

Lives in
BTP/BAIP
Provides
Event MeshBTPEvent 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).
Part of
SAP Integration SuiteSAP Integration SuiteartifactSAP'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.
Designs
Designing Event-Driven ApplicationsDesigning Event-Driven Applicationsreference architectureevent broker for small-volume scenarios

Who is behind it

SAPSAPOrganisationMaintains this
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

Connections2

Download
SAP Integration Suite, Event Mesh connectionsSAP Integration Suite,Event MeshPROVIDES→ provides1provides stated Brokers events between applications: a queue holds them and subscribes to the topics it should receive, consumers read the queue over AMQP, MQTT or HTTP, and a webhook subscription pushes a queue's messages to a REST endpoint. A message is capped at 1 MB and the broker at 250 queues and 3000 topic subscriptions. Event Mesh — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/event-mesh-3129673.md Queues — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/queues-99b7501.md Webhook Subscriptions — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/webhook-subscriptions-58e3729.md Event Mesh Scope — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/event-mesh-scope-4a89370.md Event Mesh Scope — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/event-mesh-scope-4a89370.mdEvent MeshLINEAGE→ part of1part of stated Event Mesh — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/event-mesh-3129673.md Configure A Message Client — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Event_Mesh/configure-a-message-client-867c517.mdSAP Integration Suite

Learn more3

Readings
  1. Receive Events from Event Mesh of Integration Suite to CAP Node.js ApplicationsKevinWang_ST_Consultancy, SAP Community
  2. Getting Started with SAP Event Mesh: Concepts, Setup, and Best Practicesvvinay_kumar, SAP Community
  3. Modern integration at TÜV Rheinland: APIs, events and cloud transformationManisha Debnath, Udo Paltzer, SAP TechEd — session catalogue

Others providing3

Compare all 4 on the Event Mesh page →
Event Mesh
  1. SAP Integration Suite, advanced event meshEvent streaming and management platform in Integration Suite
  2. SAP Cloud Application Event HubDistributes business events between SAP cloud applications
  3. Event MeshManaged queues and topics over AMQP, MQTT and REST

Details

Sources1
Added by handdiscovered herechecked

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 domainbtp, integration-and-messaging
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:btp-integration-suite-event-mesh
JSON
/artifacts/btp-integration-suite-event-mesh.json
MCP
Connecting an agent