Message Delivery Modes (Direct vs Persistent)
The concept name was not provided, so a precise definition cannot be produced. Based on the available sources — which cover topics such as SAP Event Mesh, SAP Integration Suite advanced event mesh, event-driven architectures, queues, subscriptions, and publish/subscribe patterns — no specific concept can be accurately defined without risking unsupported claims. Please supply a valid concept name so a grounded, accurate definition can be written.
Tutorials that teach this
- Tutorial Learn about SAP Event Mesh
- Tutorial 3 - Explore SAP Integration Suite, advanced event mesh
- Tutorial 4 - Publish and Subscribe to Events
- Tutorial Create an Application for Receiving Messages
- Tutorial Queues and subscriptions in SAP Integration Suite, advanced event mesh
- Tutorial 2 - Why Event-Driven Architectures?
- Tutorial Publish and Subscribe to Events in SAP Integration Suite, advanced event mesh
- Tutorial Send and Receive Test SAP Event Mesh
Prerequisites
- Concept Event Mesh Queue Management The concept name was not provided (marked as "undefined"), and the supplied source snippets do not contain enough substantive content to derive and define a specific SAP developer concept. The sources reference SAP Event Mesh, SAP Integration Suite advanced event mesh, RAP Business Events, and ABAP Environment event consumption, but without a named concept and detailed source text, a grounded 2–4 sentence definition cannot be accurately produced.
- Concept Publish-Subscribe Messaging Pattern The **Eventing Module** is a component on SAP Business Technology Platform that developers use to set up [event-driven communication between applications](https://help.sap.com/docs/btp/sap-business-technology-platform/07b2d1db518b441780d1ea981eb77bb9?locale=en-US&state=PRODUCTION&version=Cloud). By adopting an event-driven architecture, applications can react to changes and triggers asynchronously rather than relying on direct, synchronous calls. Developers configure the module to enable reliable message exchange across distributed services within the SAP BTP landscape.
- Concept Event Broker Service Creation and Configuration The concept name was not provided, and the available source snippets contain only tutorial titles without substantive descriptive content to ground a definition. A valid definition cannot be written without either a defined concept name or source snippets containing explanatory text about the concept.
- Concept Message Queue Creation and Subscription Management A Java-based messaging client is an application built using Java that a developer uses to send and receive messages within an event-driven integration landscape. It can be used alongside [SAP Integration Suite, advanced event mesh](https://help.sap.com/docs/SAP_INTEGRATION_SUITE) to both consume and publish events, enabling asynchronous communication between systems. Developers use it in combination with Cloud Integration to connect Java applications to message brokers and exchange data across distributed environments.
- Concept Event Mesh Queue and Topic Subscription The concept name was not provided, and the available source snippets do not contain enough detail to produce a grounded, accurate definition. A meaningful definition cannot be written without a clearly identified concept and sufficient supporting source content.