Getting to Know Additional Specific Terms

The centralized management layer operated by the cloud provider. It is used by administrators to provision, scale, configure, and monitor event broker services without directly touching the underlying infrastructure.

The data layer (runtime environment) where event brokers operate and where actual messaging traffic flows between applications and systems in real time.

Predefined broker instance configurations that determine capacity, throughput, and reliability. Developer classes are single-node instances meant for non-production environments, whereas Enterprise classes offer dedicated resources and high-availability setups for production workloads.

A design, modeling, and governance tool within SAP Integration Suite, advanced event mesh. It allows architects and developers to design topic taxonomies, define event schemas, catalog event assets, and visualize application interactions across the enterprise.

An open-source specification standard (similar to OpenAPI for REST APIs) used by the Event Portal to document and define asynchronous, event-driven interfaces in a machine-readable format.

A structured, slash-separated naming system for events (e.g., sap/s4/orders/created). It enables fine-grained message classification and precise filtering via subscriptions.

A high-availability deployment pattern consisting of three software instances working together:

Primary Messaging Node

The active broker node handling client connections and message traffic.

Backup / Standby Messaging Node

The passive node that synchronously mirrors the primary node's state and message store for immediate failover.

Monitoring Node (Arbiter)

A lightweight node that assists in quorum detection to prevent split-brain scenarios during automated failovers.

A virtual partition inside an event broker that provides complete multi-tenancy. It isolates topics, queues, client access, and configuration settings from other Message VPNs on the same physical or virtual broker.

The mechanism that enables interconnected brokers within an event mesh to automatically share active subscriptions and dynamically route events across cloud or regional boundaries only to destinations that requested them.

A broker configuration that allows the event broker to initiate HTTP/REST requests to push events directly to external REST endpoints or webhooks, eliminating the need for the receiver to run a native messaging client.

The native binary protocol used internally by the underlying event broker technology for maximum performance, low latency, and efficient header handling.

Built-in tracing capabilities that attach standardized trace context headers to messages, allowing end-to-end tracking of an event's path across distributed systems and brokers.

An integrated operational monitoring service within SAP Integration Suite, advanced event mesh that provides dashboards, alerts, and metrics on broker health, queue usage, and system resources.

Client Profiles define technical connection properties, session limits, and queue resource quotas for connected clients. ACL Profiles control authorization by specifying which topics a client is permitted to publish to or subscribe from. Client Usernames represent the identity used for authentication; each username is associated with a specific Client Profile and ACL Profile.