Understanding Direct and Guaranteed Messaging

Objectives

After completing this lesson, you will be able to:
  • Explain the key components and patterns of Event-Driven Architecture.
  • Differentiate between direct messaging and guaranteed message delivery.

Direct and Guaranteed Messaging

Modern event brokers support direct and guaranteed messaging.

Chart comparing direct messaging and guaranteed messaging: direct messaging is for high message rates with low latency, no storage, messages can be discarded, no delivery confirmation; guaranteed messaging ensures permanent storage, no message loss, retention until consumption, delivery confirmation.

Persistence and Durability

Two sections: Persistence (messages stored in non-volatile memory, acknowledged, requires persistent delivery mode). Durability (endpoints function independently, queue retained despite broker failure, temporary queues delete messages).

Read More

  • Event Driven Architecture Pattern: Overview of different event-driven architecture (EDA) patterns, their use cases, and best practices for implementing event-driven systems.
  • Direct Messages: Explanation of direct messaging in SAP Advanced Event Mesh, including how messages are sent, routed, and received without persistence.
  • Guaranteed Messages: Detailed documentation on guaranteed messaging, ensuring message persistence, reliability, and delivery confirmation in SAP Advanced Event Mesh.

Create an Integration Suite, Event Mesh Instance

Using the SAP Integration Suite, Event Mesh capability requires the creation of a Message Client. It is done by creating an SAP Integration Suite, Event Mesh instance with the message-client plan in the SAP BTP Cockpit under Services→Instances and Subscriptions.

In this exercise, we will create an SAP Integration Suite, Event Mesh instance using the message-client plan.

Flowchart demonstrating steps in EDA-Demo process. Five steps marked: Log in, Activate EMIS, Activate Cloud Integration, Add Role Collections, Create EMIS Instance. Service Key and Event Topic icons on the right.

Prerequisites

  • The SAP Integration Suite, Event Mesh service with the message-client plan must be available as an entitlement in the global SAP BTP account. The service must be assigned to the development subaccount.Dashboard showing SAP service assignments for CLD900-DEV-CO21. Service: SAP Integration Suite, Event Mesh. Quota assigned: 1 unit; remaining quota: 29 units. Options to edit and manage assignments present.
  • A Cloud Foundry environment must be available. The user creating the service instance must be listed as an Org Manager under Cloud Foundry→Org Member.Screenshot of Cloud Foundry org members list showing their e-mails, origins, org roles, and actions. Key members are highlighted in yellow.
  • At least one space must exist in the Cloud Foundry. Service instances are deployed within a Cloud Foundry space. In this case, it is a space named dev.Cloud Foundry space configuration screen displaying development space details, including memory usage and available services.
DemoStart Demo

Note

For participants attending an on-site training only: This exercise will be discussed theoretically by your trainer and will not be carried out on the training system.

Create a Service Key for the Integration Suite, Event Mesh Instance

After creating the Message Client as an SAP Integration Suite, Event Mesh instance, a Service Key is generated. This key provides an endpoint via WebSockets and enables access through an OAuth 2.0 client.

In this exercise, we will generate a service key for the previously created Integration Suite, Event Mesh instance.

Flowchart showing steps to activate SAP Integration Suite. Steps: Log in, Activate Event Mesh, Activate Cloud Integration, Add Role Collections, Create EM Instance, Create EM Instance Service Key, and Create Queue.

Prerequisites

A successfully created SAP Integration Suite, Event Mesh instance.

DemoStart Demo

Note

For participants attending an on-site training only: This exercise will be discussed theoretically by your trainer and will not be carried out on the training system.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn