SAP Event Mesh for Real-Time, Scalable Integrations

What is SAP Event Mesh?

SAP Event Mesh is a cloud service that enables the creation of an asynchronous, event-driven architecture between applications. By establishing a publish–subscribe communication model between event producers and consumers, it allows for modern Event-Driven Architecture (EDA). This enables applications to operate independently, ensuring high scalability and loose coupling between systems.
Within SAP Integration Suite, the “Advanced Event Mesh” (AEM) service elevates Event Mesh functionality to an enterprise engineering level, offering advanced management, distribution, and monitoring capabilities.

Key Concepts & Components

• Event Broker Service

 Acts as a bridge between systems publishing and consuming events via topics. Supports multi-broker usage for geographically distributed systems.

• Event Producer & Consumer

SAP applications like S/4HANA, SuccessFactors, or third-party systems can act as event producers or consumers.

• Event Portal

Used to manage Event Mesh configurations. In AEM, the transition to Event Portal 2.0 is complete; version 1.0 is no longer supported.

• Filtering & Routing

When subscribing to events, content-based filtering and routing rules can be defined to ensure only the relevant consumers receive the necessary events.

Use Case: SAP S/4HANA → Cloud Integration

A “Stock Update” event from SAP S/4HANA can be routed via Event Mesh to Cloud Integration, for example, to update stock levels in Salesforce in real time. This setup enables automated triggering of business processes.

Basic steps:

1. Activate the Event Mesh service on SAP BTP.
2. Create an event topic such as “inventory-updates.”
3. Define S/4HANA as the Event Producer.
4. Subscribe Cloud Integration to the topic.
5. Define filtering, routing, and transformation iFlows, then perform testing.

Advanced Event Mesh (AEM): Features & Advantages

• Dynamic Message Routing (DMR)

 Automatically selects the most optimal route between event brokers, ensuring events are delivered to the correct destination.

• High Availability (HA) & Message Broker Redundancy

 Brokers operate in active standby mode; automatic failover ensures uninterrupted service in case of failure.

• Distributed Tracing

With OpenTelemetry support, the complete path from event source to consumer can be traced. Bottlenecks can be detected, ensuring end-to-end visibility.

• Message Replay

Persistent messages can be resent to consumers; useful for replaying messages to systems that encountered errors.

• Kafka Bridging

Kafka clusters can be bridged to the AEM event broker system, enabling hybrid environment support.

• Message VPN Bridges

Messages published in one VPN can be delivered to consumers in another VPN through configured bridging.

• Protocol Support (AMQP, MQTT, REST)

Supports broad application integration via AMQP 1.0, MQTT 3.1.1, and HTTP/REST.

• Event Streaming & Mission Control

Centralized console for broker distribution, event mesh creation, scaling, and monitoring.

• Insights: Monitoring & Analytics Dashboards

Real-time and historical performance data is visualized in dashboards; anomalies and traffic trends can be monitored.

• Proxy Support

Corporate proxy configurations are supported for Event Portal–broker connections; works with Distributed Tracing.

• TLS Certificate Management UI

TLS certificates for brokers can now be uploaded, managed, and deleted via GUI instead of REST API.

• Static IP Addresses

Supports static IP for API access, maintaining secure connections during maintenance or migration.

• In-Service Upscaling

HA brokers can be scaled node-by-node with only ~1 minute downtime.

• HA Switchover Test

Supports switching the active node to standby to test failover scenarios safely.

• OAuth 2.0 PKCE Support

Enables secure authentication from Event Portal using OAuth PKCE; offers more secure access flows.

• Certificate-Based Authentication (Event Portal)

Clients can use certificates to access the broker. CN name can be mapped to a username; basic authentication can be disabled.

Licensing & Plans:

• The new Standard Plan should be preferred over the Default Plan, which no longer receives updates.
• Offers consumption-based and subscription-based licensing options for flexibility.
• Deployment regions no longer incur additional costs; multiple infrastructure options are included in the license.

Architecture & Application Flow

1. Configure Event Mesh / Advanced Event Mesh service in SAP BTP.
2. Create one or more event brokers.
3. Define event topics and add filtering rules.
4. Configure producer & consumer systems (e.g., S/4HANA & Cloud Integration).
5. Apply authentication (TLS, OAuth PKCE, or certificate-based).
6. Enable distributed tracing to monitor the event flow in detail.
7. Use monitoring dashboards to analyze message throughput and failure rates → apply improvements such as dead-letter queues and retries.

Why SAP Event Mesh?

Key Recommendations & Migration Strategy

• Migrate from Event Portal 1.0 to 2.0: Support for 1.0 ended on April 3, 2025; use 2.0 for ongoing configurations and historical data.
• Upgrade from Default to Standard Plan: New features are available only in the Standard Plan.
• Follow the Road Map Explorer: Plan ahead for new features arriving in Q3 2025 and beyond.

Conclusion: Transform Your Business Processes with Event-Driven Architectures

SAP Event Mesh —especially with Advanced Event Mesh— enables organizations to make application integrations more flexible, secure, and observable. From S/4HANA to cloud-based systems and third-party applications, you can build event-driven, real-time workflows that significantly enhance the agility and efficiency of your business processes.