Discovering Provisioning and Operations (Cloud Console)

SAP Integration Suite, Advanced Event Mesh provides deployment flexibility by supporting major public cloud hyperscalers, including Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP), as well as private enterprise cloud environments.

The choice of cloud provider and region is guided by geographic proximity to core business applications, data residency regulations, and existing enterprise cloud strategies. Placing Event Broker Services in the same cloud region as primary event producers or consumers reduces latency, minimizes cross-region data transfer costs, and optimizes overall network throughput.

Service Classes define the messaging capacity, hardware allocation, and performance capabilities of an Event Broker Service. When creating a service, administrators select a Service Class based on expected message volume, connected client counts, and queue storage requirements. Service Classes range from entry-level developer tiers suitable for non-production testing to high-performance enterprise tiers capable of processing high message volumes with high-availability redundancy.

Key considerations when selecting a Service Class include:

Client Connections

Maximum number of concurrent client connections required by applications.

Message Throughput

Total message processing capacity measured in messages per second.

Spool Storage

Dedicated queue storage capacity for persistent messaging workloads.

Availability Requirements

High availability multi-zone redundancy for mission-critical production environments.

During the service creation workflow, administrators define key operational settings to tailor the Event Broker Service to specific workload requirements. This includes assigning a unique service name and binding it to a specific Environment tenant to ensure proper resource isolation and governance.

Administrators also configure high-availability options across multiple cloud availability zones to guarantee continuous uptime and zero data loss for critical production workloads. Furthermore, required messaging protocols, such as AMQP, MQTT, REST, JMS, and SMF/Solace Web Messaging, are enabled with dedicated, secure connection endpoints, while spool storage capacity and client connection thresholds are defined to handle persistent messaging traffic.

After deployment, administrators use the Cloud Console to maintain and optimize running Event Broker Services throughout their operational lifecycle. Capacity can be scaled dynamically by upgrading Service Classes or expanding message spool storage to accommodate growth in application traffic without service disruption.

Platform updates, security patches, and software upgrades are managed and applied seamlessly by the underlying infrastructure. Administrators continuously monitor platform health using real-time performance indicators such as CPU utilization, memory usage, active client connections, queue depth, and network traffic rates. Finally, inactive broker instances can be safely decommissioned to release allocated cloud infrastructure resources and update environmental resource quotas.

An event mesh is a configurable network of interconnected Event Broker Services that dynamically routes messages between applications regardless of where those applications are deployed. Within the Cloud Console, administrators use dedicated management interfaces to configure and maintain these inter-broker networks.

Administrators access mesh management features through the Mesh Manager in the Cloud Console's navigation bar, where all configured Event Meshes and their connected broker services are displayed. Users choose the primary Event Broker Service that will serve as the origin node for the mesh connection and navigate to the Links tab to inspect existing connections or initiate new broker linkages.

To create an event mesh, administrators navigate to Mesh Manager and click Create Mesh. They then use Add Service to select and connect the desired Event Broker Services. The Mesh Manager automatically configures the underlying DMR links between the selected brokers. Optionally, administrators can use Switch Initiator to define which broker service initiates the link creation. For existing meshes, links are modified via Mesh Actions → Ed.

After creating Mesh Links, administrators perform ongoing operational tasks directly within the Cloud Console:

• Monitoring Link Health: The console provides real-time visual indicators for link state, throughput, and error rates across connected nodes.

• Managing Subscription Topologies: Administrators inspect active subscriptions across the mesh to ensure messages are routed efficiently without redundant traffic.

• Updating Security Settings: Interface controls allow users to adjust TLS encryption profiles and rotate authentication credentials for existing Mesh Links without tearing down the entire mesh topology.

This interface-driven approach ensures that administrators can build and maintain multi-cloud event distribution networks through structured workflows within the Cloud Console.