SAP Integration Suite, Advanced Event Mesh Releases

This page contains the release history for advanced event mesh for SAP Integration Suite. You can jump to release notes for 2024, 2023, and 2022.

SAP Integration Suite, Advanced Event Mesh Releases (2025)

Ability to Trigger Messaging Node Switchovers for High-Availability Event Broker Services

High-availability switchover is now available for high-availability event broker services in advanced event mesh.

High-availability event broker services have two messaging nodes: an active and a backup. A high-availability switchover allows you to switch the node that is in the active state. You can use a high-availability switchover to test event broker service functionality, including how your applications respond to an interruption to the messaging connectivity of the active node.

For more information, see High-Availability Switchover for Event Broker Services.

Streamlined Manage Tab for Event Broker Services in Cluster Manager

We are introducing a streamlined Manage tab for event broker services in Cluster Manager. The updated Manage tab reduces time spent navigating options by providing quicker access to configurations using a new Management Settings menu.

The updated Manage tab features a new SAP Broker Manager Quick Links pane on the left of the screen, below the Management Settings menu, giving instant access to commonly configured event broker service features in Broker Manager.

Connection information for managing your event broker services has moved to the Connect tab.

These enhancements provide quicker access to configurable event broker service features in Cluster Manager and Broker Manager.

In-Service Upscaling for High-Availability Event Broker Services

SAP now offers in-service upscaling of high-availability event broker services for the following versions in advanced event mesh:

• 10.11.1.167-5 and later.

• 10.12.0.144-1 and later.

In-service upscaling upscales each messaging node of a high-availability event broker service individually, transferring Messaging Connectivity to the upscaled messaging node when the upscaling of that node is complete. In-service upscaling allows Messaging Connectivity to your client applications to continue during the upscale process, with less than a minute of downtime when Messaging Connectivity is transferred to the upscaled messaging node.

For more information, see Release and Versioning Scheme of Event Broker Services, and Upscaling Event Broker Services.

Certificate-Based Authentication for Applications in Event Portal

Event Portal has added support for certificate-based client authentication for messaging access. With this update, you can specify that applications configured in Event Portal use certificates to authenticate with event brokers to send and receive messages.

You do not upload certificates to the event broker from Event Portal and you must coordinate with your Middleware Integration team to configure certificate-based access on the event broker itself. For more information, see Configuring Authentication to Event Broker Services. SAP recommends following best security practices for event broker access and authentication and disabling basic authentication for messaging access if you have a different method configured.

To use this feature from Event Portal, you need only to enter a client username that matches the certificate Common Name on the application's certificate. For more information, see Updating Credentials for an Event Broker.

Event Broker Service Version 10.12.0 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version 10.12.0.

Event broker service 10.12.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in advanced event mesh , see Version Adoption .

This release introduces event broker 10.12.0 and includes a variety of security and bug fixes.

To create a 10.12.0 event broker service, you can use the version selection feature and select version 10.12 (Preview). Upgrades of existing services to 10.12.0 are not supported.

OAuth PKCE Support Available

Advanced event mesh now supports OAuth 2.0 Proof Key for Code Exchange (PKCE), which enhances the security of our OAuth implementation.

Event Portal Runtime Tab Improvements

To improve the user experience of promoting applications to Runtime Event Manager and automated provisioning of operational event brokers when the runtime configuration option is enabled, we have redesigned the application Runtime tab in Designer.

You will now find it easier to:

• understand where you can promote your applications
• manage your application promotions
• view where your applications are already configured

For more information, see Adding Applications to Environments.

End of Access to Event Portal 1.0

As previously announced in our deprecation notice on October 31, 2024, access to Event Portal 1.0 has been removed from advanced event mesh, effective April 3, 2025. This change aligns with our commitment to providing customers with the most advanced and innovative solutions through Event Portal 2.0, which offers significantly enhanced capabilities.

All customers should now be using Event Portal 2.0, which provides superior functionality and an improved user experience. For assistance with Event Portal 2.0 or questions about previously stored data, please contact SAP.

Automatic Connections Between Event Portal and Event Broker Services in Public Regions

We are excited to announce significant enhancements to how event broker services in cloud Public Regions connect to Event Portal.

You no longer need to deploy, upgrade, configure, and host your own self-managed Event Management Agents (EMA). If you have event broker services in Public Regions, we now manage their connections to Event Portal for you.

As soon as you add an event broker service in a Public Region to a modeled event mesh in Runtime Event Manager, Event Portal automatically creates and manages connections between those event broker services and Event Portal. You can then benefit from features such as discovery and audit or configuration push to event broker services without having to manage EMAs.

When you remove an event broker service from a modeled event mesh, the connection is deleted in Event Portal.

If you have connected self-managed Solace software event brokers, Solace appliances, Kafka clusters, or Confluent Schema Registries to Event Portal, you still need to use self-managed EMAs.

If you have event broker services in Dedicated or Customer-Controlled Regions, you still need to manage event broker service connections to Event Portal using the cloud-managed Event Portal connections feature.

For more information, see Connecting Event Brokers to Event Portal.

Please contact SAP with any enquiries.

Event Broker Service Version 10.11.1 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version 10.11.1.

This release introduces event broker 10.11.1 and includes a variety of security and bug fixes.

Any event broker service using version 10.11.1 automatically updates the cloud client username when launching the Try-Me feature in Broker Manager.

New event broker services created using version 10.11.1 in Customer-Controlled Regions have new persistent disk space requirements. The persistent disk space requirements are slightly reduced for most service classes due to a reduction in the required amount disk space required for the default message spool.

The following table lists the new minimum disk size requirement by service class and includes sizing for both the default message spool and the required 20 GiB of space for the event broker service.

Service Class	Minimum Persistent Disk Size for Version 10.11.1 and Later
Broker 100	55 GiB
Broker 250	84 GiB x 2
Broker 1K	276 GiB x 2
Broker 5K	532 GiB x 2
Broker 10K	800 GiB x 2
Broker 50K	1044 GiB x 2
Broker 100K	1320 GiB x 2

For more information, see Configuring Message Spool Sizes and Event Broker Service Message Spool Size Requirements.

To create event broker services in 10.11.1, you can use the version selection feature and select version 10.11.

You can book upgrades of existing Event broker services as times become available in Calendly. See the Software Event Broker Versions and Support in SAP Integration Suite, Advanced Event Mesh page for the planned upgrade availability date.

Version 1.7.11 of Insights Advanced Monitoring Available

This release introduces a variety of new features, enhancements, and bug-fixes. These new features and updates allow Insights Advanced Monitoring to provide improved visualization and management of your estate.

New features

This release of Insights Advanced Monitoring includes several new features, including:

• New replay and partition queue metrics and monitors. For more information, see New Replay and Partitioned Queue Metrics and Monitors for Insights.

• New system event logs to monitor partitioned queues and message replay, including:

  • Two new logs for monitoring the rebalance state of partitioned queues:

    • VPN_AD_PARTITIONED_QUEUE_REBALANCE_STARTED

    • VPN_AD_PARTITIONED_QUEUE_REBALANCE_COMPLETED

  • A new VPN_AD_REPLAY_STATE_TRANSITION log for measuring the transition state of message replay.

Enhancements

Insights 1.7.11 includes several enhancements to our existing Insights Advanced Monitoring dashboards, including improved queue monitoring capabilities by excluding internal system queues and optimizing monitoring for queue spool utilization.

Other Updates

Other minor updates featured in this release of Insights include:

• Corrections to the default time range displayed on the Topic Endpoint Overview dashboard.

• Updates to the average message payload size calculation.

• Removal of redundant widgets to streamline message size metrics.

New Replay and Partitioned Queue Metrics and Monitors for Insights

We have added new replay and partitioned queue metrics to the list of Insights metrics for Datadog, and updated the Queues Overview and Topic Endpoints Overview dashboards with this newly available information.

Partition Metrics

Four new metrics have been introduced to monitor partitioned queues. These metrics provide insights into the state of a queue’s partitions, including the configured versus operational amount of partitions. For more information, see Partitioned Queues.

As part of introducing the partitioned queue metrics, we have updated the Queue Overview dashboard to display information about queues and their partitions. For more information, see the Queues Overview.

Replay Metrics

Nine new replay metrics have been introduced. These metrics only publish data when replay is enabled for an event broker service. The metrics provide insights about replay activity on your event broker service, including whether replay is active, and the state of replay messages during a replay operation. For more information, see Queue Statistics.

We have also updated both the Queues Overview dashboard and the Topic Endpoint dashboard with new widgets showcasing the information from the new replay metrics . For more information, see the Queues Overview and Topic Endpoints Overview.

Together, these new metrics and associated dashboard updates provide you with new tools to monitor the operational state of the partitioned queues and replay features in your estate.

Event Portal Security Enhancement

To improve Event Portal security, we have removed the ability for users to retrieve application client username passwords in plaintext after they have provided them.

After users provide client username passwords, they can no longer:

• retrieve passwords in plaintext using the Manage Credentials option in the Runtime tab
• retrieve passwords in plaintext from the deployment Preview dialog.

All other application client username credential functionality continues to behave as previously implemented.

Please contact SAP if you need assistance.

Mesh Manager is Now Generally Available in Advanced Event Mesh

SAP is excited to announce that Mesh Manager is now generally available in advanced event mesh.

An event mesh allows you to network multiple event broker services together in a dynamic infrastructure layer for distributing events among decoupled applications, cloud services, and devices. An event mesh allows you to route data in real time between applications no matter where they are deployed.

Mesh Manager provides the tools you need in the Cloud Console to create and manage an event mesh composed of your event broker service.

For more information, see Mesh Manager.

Event Broker Service Version 10.11.0 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version 10.11.0.

Event broker service 10.11.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in advanced event mesh , see Version Adoption .

This release introduces event broker 10.11.0 and includes a variety of security and bug fixes.

To create a 10.11.0 event broker service, you can use the version selection feature and select version 10.11 (Preview). Upgrades of existing services to 10.11.0 are not supported.

New Instance Specifications for Elastic Kubernetes Service and Azure Kubernetes Service

We have updated the instance type specifications for the worker nodes in Kubernetes clusters hosting event broker services in Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS).

The new instance sizes have been selected to optimize resource requirements and performance of your event broker services.

SAP will upgrade instance types for Public Region and Dedicated Region customers. Both customer types should notice increases in their event broker service performance when scaling up to a new service class.

Customer-Controlled Region customers are encouraged to ensure their worker nodes meet the new instance specifications for their event broker service class. For more information on the instance specifications for Customer-Controlled Regions, see:

• Instance Type Specifications in Installing in Amazon Elastic Kubernetes Service (EKS)

• Node Pool Specifications in Installing in Azure Kubernetes Service (AKS)

XSD Schema Support in AsyncAPI Exports from Event Portal

Event Portal now supports XSD schemas in AsyncAPI specification exports, enabling customers working with XML-formatted event payloads to fully utilize the AsyncAPI capabilities offered by Event Portal. This feature is valuable for integration scenarios involving XML-based message formats. This enhancement allows you to:

• Export AsyncAPI specifications for applications, event APIs, and Event API Products that use XSD schema-based events.
• Generate valid AsyncAPI documents that properly represent XML payload schemas.
• Access exports through both Designer and a new Event Portal API.

Technical Notes

• In accordance with AsyncAPI specification requirements, XSD schemas are inlined as strings in the exported document
• The current implementation handles direct XSD schemas. Support for nested XSD schema references will be addressed in a future release.
• This functionality is available only through Designer and the new Beta AsyncAPI REST API endpoint, which provides enhanced support for schema references.

For more information about exporting schemas in AsyncAPI documents from Designer, see Schemas

Enhancement to Protect Production Environments

We have updated the ability to change the environment type between Production and Non-Production after creating an environment. This change helps better protect your production assets and ensure production and non-production environments stay separate. If you need to move assets in or out of production, you must now move or copy the assets between environments rather than changing the environment type.

For more information, see Creating and Managing Environments.

Easier User Management With User Groups in Advanced Event Mesh

You can now set up your advanced event mesh account with user groups. All customers can configure their organizations with user groups, assign roles to those groups, and assign users through their identity provider (IdP).

User groups allow you to dynamically add users to a group that has an assigned role when users log in through SSO. Mapping IdP claim values to groups provides an easier way to manage feature and resource access for large numbers of users.

For more information about user groups, see Configuring Group Management.

Nested Referenced JSON Schema Support in AsyncAPI Documents Exported from Event Portal

We are introducing support for nested referenced schemas within Event Portal for exported AsyncAPI specifications. This enhancement ensures that exported AsyncAPI documents accurately reflect the complete application or event API interface definitions, including all associated nested referenced schemas. This update includes the following improvements:

Comprehensive Support

• Supports nested referenced JSON type schemas.
• Compatible with AsyncAPI exports and integrations for applications, event APIs, and Event API Products.
• Supports AsyncAPI exports via both the UI and the REST API.
• A new Beta REST API endpoint is being introduced for these enhancements as part of this feature. The old REST API endpoint will be deprecated when the new one is declared GA.

Enhanced Data Integrity

• Implements collision detection for event and schema names within the AsyncAPI.
• Provides clear error messages to guide users in resolving naming conflicts.
• Introduces two new naming strategies to address collisions. Users can select one or both strategies to resolve naming conflicts effectively:
  • Prepend application domain names: (e.g., Shipping.Order)
  • Append major version number: (e.g., Order.V3)

This update offers the following benefits:

• Improved Data Accuracy: Exported AsyncAPI documents now provide a more complete and accurate representation of event payload schemas when schemas include references to other schemas, facilitating better integration and understanding by consumers.
• Enhanced Developer Experience: The new naming strategies and collision detection mechanisms minimize potential integration issues.
• Increased Reliability: By ensuring data integrity within the exported specifications, this feature enhances the overall reliability and stability of event-driven architectures.

This update may require adjustments to existing workflows involving AsyncAPI exports.

For more information, about downloading Async API documents from Designer, see Downloading an AsyncAPI Document for an Application, Downloading an AsyncAPI Document for an Event API, or Downloading an AsyncAPI Document with Event API Product Information.

SAP Integration Suite, Advanced Event Mesh Releases (2024)

 

Event Broker Service Version 10.10.1 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version, 10.10.1.

The release of 10.10.0 introduced a new Mission Control Manager user to Broker Manager. Users require the Mission Control Manager user in Broker Manager as of event broker service version 10.10.0 and later to configure certain event broker service features, including DMR links, message replay, client certificate authentication, disaster recovery (replication), and SEMP over message bus. Cloud Console users will also find that many of these listed features have been moved from the Cloud Console to Broker Manager.

Cloud Console users require either the Mission Control Manager role or the Mission Control User with the Manager permission to access the Mission Control Manager user in Broker Manager. If you have configured management access to Broker Manager using LDAP or OAuth profiles, you must update these configurations after you upgrade to 10.10.1. Failure to update the management access configurations may prevent users from accessing Broker Manager and configuring certain features in Broker Manager.

For more information on updating management access to Broker Manager, see:

• Configuring Authentication to Event Broker Services

• Configuring OAuth Profiles for Management Access to Event Broker Services

For more information about Mission Control roles in advanced event mesh, see Managing Users, Groups, Roles, and Permissions.

To create a 10.10.1 event broker service, you can use the version selection feature and select version 10.10.

You can book upgrades of existing Event broker services as times become available in Calendly. See the Software Event Broker Versions and Support in SAP Integration Suite, Advanced Event Mesh page for the planned upgrade availability date.

Enhanced Event Portal Event Broker Configuration and Auditing Capabilities

We are pleased to announce significant updates to Event Portal, designed to streamline configuration processes and improve configuring and auditing capabilities for event broker services. These enhancements focus on simplifying workflows to improve the usability and efficiency of Event Portal.

Cloud-Managed Event Broker Connections

Event Portal now offers a streamlined connection process for cloud-managed event broker services in Dedicated Regions and Customer-Controlled Regions:

• Simplified Connection Process: Users can now connect event broker services to Event Portal with minimal manual intervention.
• Elimination of Self-Managed Agents: The requirement for self-managed Event Management Agents has been removed for event broker services in Dedicated Regions and Customer-Controlled Regions in the same account.
• Accelerated Workflow: The connection process between event broker services and Event Portal has been significantly expedited. Note: Support for Public Regions is forthcoming, which will further reduce the need to install Event Management Agents.

Important Considerations

• Users with existing Event Management Agent configurations must enable Event Portal connections and remove outdated agents. For assistance, please contact support.
• In the event of data center migrations, it is crucial to update Event Portal mappings to ensure the continued functionality of features such as discovery and audit.

Environment Integration Enhancement

The multi-environment support previously available in Cluster Manager has been extended to Event Portal. New features include:

• Environment-Specific Navigation: Users can select and maintain environment context while navigating Runtime Event Manager.
• Visual Organization: Implementation of environment icons and color coding for improved organization and clarity.

Unchanged Features

• Configuration templates and Event Management Agent remain environment-agnostic.
• Designer and Catalog functionalities continue to operate across all environments without specific context.

For comprehensive information on these updates, please consult the following documentation:

• Discovering Runtime Data
• Creating and Managing Environments

For inquiries or feedback, please contact our support team.

Snap to Grid Support in Event Portal Graphs

Users can now enable the Snap to Grid feature in Event Portal graphs so that the icons snap to the closest grid position when users move and place icons on the graph. This update makes it much easier to align icons to make more visually appealing graphs.

Announcing Support for Rancher RKE2 in Advanced Event Mesh

SAP now supports deployments of event broker services to Rancher Kubernetes Engine 2 (RKE2) for customers with deployments in Customer-Controlled Regions.

We have extended support to RKE2 to provide customers with:

• support for Rancher’s next-generation Kubernetes distribution and its enhanced features

• a migration path for customers currently deployed to Rancher Kubernetes Engine 1 (RKE1), which is end-of-life (EOL), effective July 2025

We have added RKE2 to our Other category of supported Kubernetes distributions. For more information, see Kubernetes Upgrades in SAP Integration Suite, Advanced Event Mesh .

For more information about the RKE1 EOL, see the RKE End of Life document on the SUSE Support website.

Multiple Value Custom Attributes and Custom Attribute Renaming in Event Portal

Event Portal has added support for a new type of custom attribute (multi-value) as well as the ability for users to rename existing custom attributes.

With this feature, the names of the other two other custom attribute types have changed as follows.

• Simple is now Text.
• Complex is now Long Text.

Key benefits include:

• Improved asset classification and categorization
• Enhanced filtering capabilities in Catalog
• Greater flexibility in describing Event Portal objects
• Support for migrating object tags and owners from Event Portal 1.0 to 2.0

These features enhance the flexibility and usability of the custom attribute feature set and enables users to better organize and manage their event-driven architecture assets by tagging them with multiple values for attributes such as project IDs, phases, use cases, contacts, owners, URLs, and departments. The new multi-value attribute type complements the existing text and long text types, to provide a more comprehensive tagging system.

For more information, see Using Custom Attributes.

New Kafka Bridge Monitoring Dashboard for Insights

We have added a new Kafka Bridge Monitoring dashboard to the list of Insights dashboards for Datadog. The dashboard is available to Insights Advanced Monitoring subscribers using event broker services 10.8.1 and later.

The Kafka Bridge Monitoring dashboard focuses on monitoring the flow of messages over the Kafka Bridges in your estate, integrating Kafka Bridge metrics and health data into Insights. Monitoring the critical connection between your Kafka and SAPevent broker services helps provide a unified view into the overall health of your event streaming infrastructure.

New Kafka bridge monitors and metrics are available, including data for Kafka bridge sender, receiver, and overview statistics, providing a wealth of information about your Kafka bridges. You can use the metrics to create your monitors and dashboards.

For more information about:

• the Kafka Bridge Monitoring dashboard, see Kafka Bridges Overview

• the monitors, see Kafka Metric Monitors

• the metrics, see Kafka Bridge Statistics

• configuring Kafka bridging, see Configuring Kafka Bridging

Environment Integration Completed for Cluster Manager

The completed integration of environments into Cluster Manager now allows you to configure, select, and use environments while managing event broker services in the Cloud Console.

This update provides the following features:

• New labels throughout Cluster Manager inform users about their currently selected environment.

• Users can change their selected environment and toggle the list of viewable services (all or current environment only) in Cluster Manager.

• Administrators can configure environments, including their environment type (production, or non-production), and environment appearance using colors and icons in the Environments tab when creating or updating environments.

Along with the above changes, we have removed the ability to designate an environment during event broker service creation. The Environment field is now read-only. Users now create event broker services in their currently selected environment.

For more information, see Creating and Managing Environments.

Event Broker Service Version 10.10.0 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version, 10.10.0.

Event broker service 10.10.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in advanced event mesh, see Version Adoption .

This release introduces elevated Broker Manager permissions to the Mission Control Manager role and the Manager permissions for the Mission Control User role. These two roles can now configure certain features that were not configurable without requesting support from SAP in previous versions. Some of the configurable features include: DMR links, message replay, disaster recovery (replication), client certificate authentication, SEMP over message bus settings, and increasing the Broker Manager user interface timeout.

As of 10.10.0, users must have the Mission Control Manager role, or Manager permission to configure DMR links.

For more information about Mission Control roles, see Managing Users, Groups, Roles, and Permissions.

To create a 10.10.0 event broker service, you can use the version selection feature and select version 10.10 (Preview). Upgrades of existing services to 10.10.0 are not supported.

Deprecation of Event Portal 1.0 in SAP Integration Suite, Advanced Event Mesh

SAP has deprecated Event Portal 1.0 as of October 31, 2024. This decision aligns with our ongoing commitment to providing our customers with the most advanced and innovative solutions, and at this point Event Portal 2.0 has far surpassed Event Portal 1.0 in value and capabilities.

Key Dates and Actions:

• October 31, 2024: Event Portal 1.0 has been deprecated as of October 31, 2024.

• March 31, 2025: Event Portal 1.0 reaches end of support and end of user access on March 31, 2025. In order to not lose your data in Event Portal 1.0, you must migrate to Event Portal 2.0 before the end of support date.

Self-Service Access to Runtime Configuration from Event Portal

You can now provision runtime configurations to your advanced event mesh event brokers from Event Portal. This new feature can speed up the application development in your enterprise, without sacrificing governance. This update includes the following updates improvements:

Self-Service Configuration: Development teams can now configure event brokers for their applications themselves.

Governed Access: Middleware Integration teams stay in control, deciding who can push runtime configurations to event brokers in each environment.

Queue Configuration Templates: Templates let Middleware Integration teams define required and allowed settings, helping developers build applications faster while controlling what configurations can be pushed to which environments.

For more information, see Configuring Event Brokers in Event Portal.

New Ability to Select Environment During Event Broker Service Creation in Advanced Event Mesh

SAP continues the introduction of environments to the Advanced Event Mesh platform, allowing you to designate an environment for your event broker services during creation and cloning.

Organizations with environments beyond the default will notice a new mandatory Environment field during service creation or cloning. You can designate an environment for the event broker service during creation using this field.

This update also introduces environments as a column in the list view in Cluster Manager when viewing event broker service information.

For more information, see:

• Creating Event Broker Services

• Cloning an Event Broker Service

• Creating and Managing Environments

Event Broker Service Version 10.9.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.9.1.

This release introduces event broker 10.9.1 and includes a variety of security and bug fixes.

To create event broker services in 10.9.1, you can use the version selection feature and select version 10.9.

New Replication and Disaster Recovery Dashboard for Insights

We have added a new Replication and Disaster Recovery (DR) dashboard to the list of Insights dashboards for Datadog available to Insights Advanced Monitoring subscribers.

The dashboard provides information about the health and status of the connection between the event broker services configured as a replication pair for disaster recovery. The dashboard also provides information about the flow of the replicated messages between the primary and backup event broker services in a replication pair.

Six new metrics are also available as part of the dashboard release, providing a method for tracking various replication information. You can use these metrics to create your monitors and dashboards.

For more information about:

• the Replication and DR dashboard, see the Replication and DR Overview

• the metrics, see Replication Statistics

• using replication for disaster recovery, see Using Replication for Disaster Recovery of Event Broker Services

New Event Portal AsyncAPI Export Options

Event Portal now offers greater flexibility for exporting AsyncAPI documents for application developers. Users can customize their exports by:

• Selecting an event broker: This limits the exported data to attracted events, bindings, and server information.

• Not selecting an event broker: This focuses the data on declared events and bindings.

• Checking or unchecking individual options: Users can dynamically adjust their export preferences

Event broker context related features include:

• Pre-selected event broker in the runtime tab: The event broker is automatically chosen for AsyncAPI document exports from the “Runtime” tab.

• Event broker info access: Only users with EP Runtime Viewer access to a specific event broker can view its information.

• Modeled event mesh context option: For backwards compatibility, users can choose a modeled event mesh context when exporting from the API.

For more information, see Downloading an AsyncAPI Document for an Application.

Datacenters in Advanced Event Mesh Associated with Environments

As part of the continued introduction of environments across the Advanced Event Mesh platform, existing datacenters are being associated with an environment. During this phase of the environments roll-out, you can’t delete an environment containing a datacenter.

Future environments updates will introduce the ability to move datacenters and their associated event broker services to different environments.

For more information, see Creating and Managing Environments.

SAP Extends Environments to the Advanced Event Mesh Platform

SAP is extending environments from Event Portal to the advanced event mesh platform. The first phase of extending environments introduces a default environment to Mission Control. Default environments introduce:

• a new default attribute for environments.

• the ability to rename default environments.

• the ability to designate any environment as default.

• a restriction on deleting default environments.

SAP will introduce a default environment to all organizations. You can set a different environment as the default and delete the provided one. For more information, see Creating and Managing Environments.

We encourage organizations to use this opportunity to designate an environment of their choice as their default environment, as SAP will move any event broker service without an environment to your organization’s default at a future date.

For more information, contact SAP.

Increased Memory Resource Requirements for Event Broker Service 10.6 and Later

The memory limit and total memory limit requirements for event broker services versions 10.6 and later are increasing. The memory limit is increasing by 256 MiB per broker to provide more memory to the monitoring agents. This means the following total memory increase per service type:

• Standard class event broker services require 256 MiB additional memory limit per service.

• High availability event broker service require 768 MiB additional memory limit per service.

This memory increase provides the monitoring agents with additional resources they require during upgrades. The memory request limit remains unchanged at 256 MiB per monitoring agent.

See the General Resource Requirements for Kubernetes and Default Port Configuration for a table listing the memory limit requirements for all supported event broker versions.

Event Portal Event Access Request/Approval Workflows

SAPEvent Portal now supports new event data access governance capabilities. This feature set introduces an event data request and approval workflow to streamline the process of granting access to sensitive or restricted event data. Developers and architects can now request access to specific event data for their applications, and these requests are automatically routed to designated approvers. Approvers review and approve or deny access requests, ensuring secure and efficient data management while empowering event data owners to maintain control over their data.

This feature addresses the challenge of governing event data access in complex organizational structures by providing a centralized mechanism for managing and controlling data flows. For more information, see Managing Event Data Access.

Enhanced Service Details Tabs in Cluster Manager

We have updated the service detail tabs for event broker services in Cluster Manager. Most of the changes to these tabs are technical, modernizing the underlying code of the user interface to allow for future upgrades and enhancements.

From a user perspective, you may notice minor changes in colors used, fonts, icons, and content layout. The overall experience should be almost identical to the previous iteration of the tabs. Tabs with noticeable changes include:

• Monitoring—We have streamlined access to the tabs information, requiring less interaction to get the information you need from the tab, and removed several less relevant monitors.

• Try Me!—We have replaced the Try Me! feature with a landing page providing access to the more complete Try Me! in Broker Manager. For more information, see Try Me! Tab in Cloud Console now Links to Broker Manager Try Me!.

Try Me! Tab in Cloud Console now Links to Broker Manager Try Me!

We have replaced the Code Pen-based Try Me! in the Cloud Console with a landing page providing direct access to the Try Me! in Broker Manager.

Broker Manager’s Try Me! is frequently updated, providing new functionality with more comprehensive features for event broker service users of all experience levels. To make this change seamless, we have added the ability to copy and paste your event broker service credentials from the landing page to use in the Try Me! in Broker Manager.

For more information, see Trying Out Your Event Broker Service.

Manage Custom TLS Server Certificates on Event Broker Services Using v2 REST APIs for Advanced Event Mesh

Customers can now use the advanced event mesh v2 REST APIs for Mission Control to install and manage SSL/TLS server certificates on their existing event broker services in advanced event mesh.

Using the Server Certificate v2 REST API you can:

• upload and install SSL server certificates

• request server certificate information for one, or many event broker services

• delete server certificates from an event broker service

For more information, see Managing Custom TLS Server Certificates for an Event Broker Service

.

Helpful Warnings When Adding Application Versions to Event Brokers in Event Portal

Now, when adding an application version to an event broker in an environment, Event Portal displays helpful warning messages to indicate if there are discrepancies between the event versions that are declared to be subscribed to by the application version and event versions that will actually be attracted by that application version’s subscriptions after it is deployed to the runtime. Each discrepancy displays in a table row that explains the discrepancy, such as no matching subscription for the application or if the application’s subscription attracts an older or newer version of the event in the target environment. The new messages provide a preview of what will happen in the runtime before the actual deployment and allows users to continue with adding the application version to the environment or fix the discrepancies first. For more information, see Fixing Event Flow Discrepancies.

Single Sign-On Support for Insights Datadog Account as Controlled Availability

Insights customers can now configure single sign-on (SSO) for the Datadog account included with their Insights subscription as a Controlled Availability feature.

With this feature, SAP gives a user you choose the SAML Manager role. They use this role to configure SSO for the Datadog account using your own SAML Identity Provider. Configuring SSO for the Datadog account included with your Insights subscription allows you to provide your users with access to the Datadog account and map permissions within the account to existing Insights user roles.

For more information, see Single Sign-On for Insights Datadog Accounts.

New Insights Advanced Manager now Available as Controlled Availability

Insights customers can now assign the Insights Advanced Manager role to a user as a Controlled Availability feature.

The Insights Advanced Manager role provides the user with the same permissions as the Insights Advanced Editor, as well as the ability to manage Datadog API and APP keys, and some Datadog Integrations. The Insights Advanced Manager role allows you to share the data in your Insights Datadog account with SAP approved applications, providing more value to the data collected from your event broker service.

For more information, see Insights Advanced Manager Role.

Hyphens in Topic Variables Names in Event Portal

Event Portal Users with Application Domain Editor access can now use hyphens (-) in topic variable names in Event Portal, which allows more complex names in topics to better match your topic taxonomy.

Event Broker Service Version 10.8.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version 10.8.1.

This release includes a variety of security and bug fixes; no new major features are included.

To create event broker services in 10.8.1, you can use the version selection feature and select version 10.8.

Advanced Event Mesh Now Offers Message Spool Expansion for Public Regions and Dedicated Regions

Message spool expansion is now available to advanced event mesh customers with Public Regions and Dedicated Regions with event broker service 10.7.1 and later. Message spool expansion provides a self-serve method for configuring and expanding message spool size for your event broker services.

With message spool expansion, you can configure message spool size beyond service class defaults when you create a service. You can also expand the message spool size of in-service event broker services beyond service class defaults, while the event broker service remains in service. Spool sizes of up to 6 TB are possible for an event broker service. For more information, see Configuring Message Spool Sizes.

Message spool expansion provides 500 gigabytes (GB) per limit to configure and scale up message spool size beyond service class defaults. Message spool expansion is an organization-wide setting that you can apply to one or many event broker services.

For more information or to get message spool expansion for your event broker services, contact SAP.

Advanced Event Mesh Announces Supported Networking Options for Dedicated Regions

SAP has introduced a defined list of supported networking options for advanced event mesh customers who require private Messaging Connectivity between the event broker services in their Dedicated Region, and the virtual private cloud (VPC) where their applications reside.

Customers should choose the options that meet both their Messaging Connectivity requirements and cloud provider availability. Options for Messaging Connectivity include:

• VPC/VNet peering

• Managed hub-and-spoke networking

• Unidirectional endpoints

For more information about the supported networking options for Dedicated Regions, see Networking Options for Dedicated Region Deployments.

New Access Levels for Event Portal Users to Use Runtime Event Manager

Previously, only Administrators and Event Portal Managers could access the Runtime Event Manager and its environment-focused features. Now, Event Portal Users can be assigned the new EP Runtime Viewer and EP Runtime Editor access levels for environments.

Event Portal Users with EP Runtime Viewer access can:

• Open Runtime Event Manager
• View the list of modeled event meshes and their related environments
• View the modeled event mesh and environment details they have access to
• View shared applications and events in environments they have access to

Event Portal Users with EP Runtime Editor access can:

• Access and view the same information as EP Runtime Viewers
• Deploy applications to environments in Runtime Event Manager when they also have the Application Domain Editor role

The following features are still limited to Event Portal Managers and Administrators:

• Runtime discovery and audit
• Deployment of Kafka events to modeled event meshes

In addition, a new runtime tab was added to the application details page in Designer to help you manage applications in environments.

With these updates, you can define environment access with the granularity required by your organization.

See Managing User Access to Event Portal for more information.

Event Broker Service Version 10.8.0 Available in Advanced Event Mesh

Customers can now create event broker services using event broker version, 10.8.0.

Event broker service 10.8.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in Advanced Event Mesh, see Version Adoption .

This release includes a variety of security and bug fixes; no new major features are included.

To create a 10.8.0 event broker service, you can use the version selection feature and select version 10.8 (Preview). Upgrades of existing services to 10.8.0 are not supported.

Filtered Event Flow Views in the Event Portal Runtime Event Manager Graph

The event flows in the graph view in the Runtime Event Manager can now be filtered for designed event flows or events consumed via subscriptions. By default, users can view both types of flows at the same time. For more information, see Viewing a Modeled Event Mesh.

Setting End of Life Date for Deprecated Object Versions in Event Portal

Users can now set the planned End of Life date for deprecated objects in Event Portal. If set, the date displays with the object details in Event Portal. For more information, see Event Portal Overview.

New Event Portal Drag and Drop Capabilities to Create and Update your Event-Driven Architecture in Designer

Event Portal has been enhanced to allow users to quickly and easily design and extend their event-driven architecture graphically. Users now have the ability to create and modify their applications, events, and their relationships in the graphical Designer itself, without having to drill into the form based method, until they are ready to add more configuration details to their design.

For more information, see Using the Graph View.

Editing Object Descriptions in Event Portal

Application domain managers (and higher-level users) can now allow users to edit object version Description fields for applications, events, and schemas in any lifecycle state. Before this enhancement, descriptions could be edited only for objects in Draft state, even though updating an Event Portal object version's description does not materially change the event interface of an application version. Now, managers have the option not to enforce this restriction. If the restriction is not enforced, users can edit the Description of an object version without moving the version back to Draft state or creating a new version. For more information, see Creating an Application Domain.

Event Portal Enhancements to Help Users Manage their Event-Driven Architecture

Event Portal has introduced several improvements to help users:

• When selecting an event version to be published or subscribed to by a new application version, users can now narrow down the event versions displayed to only those already being published to specific event meshes or environments. For more information, see Creating Applications.

• Administrators and Event Portal Managers can now enable delete protection on a specific application domain. For more information, see Deleting an Application Domain.

Choosing Specific Versions/Revisions of Broker Releases Now Available in Cluster Manager

Previously in Cluster Manager, when you selected the broker version, you could only select the release number and you could not select the version or revision that you wanted. The ability to select version and revision information was only available to users that created event broker services use the SAP Integration Suite, advanced event mesh Cloud REST API.

Now, when you create an event broker service using the new Create Service page user-interface in Cluster Manager, you can choose the broker release in the new Broker Release field and then optionally select a specific version and revision of that broker release in the Broker Version field. See Release and Versioning Scheme of Event Broker Services for more information about broker releases, versions, and revisions.

You can choose from versions that are currently in support and the default is still to create the event broker service using the most recent version and revision of a broker release.

You may find this capability useful in situations where you require event broker services to be created with an exact match that includes not only the broker release but also the version and revision. For example, you may have tested using 10.6.1.50-2, but then 10.6.1.100-1 gets released shortly after you complete testing, becoming the default for all new event broker service creation. To avoid invalidating your testing, you can choose the exact version and revision you tested with when creating new event broker services.

Besides the new ability to choose a specific version and revision of a broker release, there are other user-interface flow improvements, including:

• You now select a region using a drop-down list rather than a cumbersome pop-up window

• You select message spool size and connections after choosing the broker release, version and revision.

For more information about creating event broker services with the improved updates in Cluster Manager, see Creating Event Broker Services.

SAP Increases Default Spool Size for Event Broker Services in Advanced Event Mesh

SAP has increased the default message spool size for all newly created 10.7.1 and later event broker services in advanced event mesh.

The default message spool size for an event broker service continues to be defined by its service class. The following table lists both the existing and new default message spool sizes by event broker service class.

Service Class	Message Spool Size for Versions 10.6.1 and Earlier	Message Spool Size for Version 10.7.1 and Later
Standard	10 GiB	25 GiB
Broker 250	25 GiB	50 GiB
Broker 1K	50 GiB	200 GiB
Broker 5K	200 GiB	400 GiB
Broker 10K	300 GiB	600 GiB
Broker 50K	500 GiB	800 GiB
Broker 100K	500 GiB	1000 GiB

For more information about default message spool size, see Default Message Spool Sizing.

For Customer-Controlled Regions, the new default spool sizes introduce changes to the minimum persistent disk space requirement. Event broker services created with version 10.7.1 and later require persistent disk space that is 30% greater than the default message spool size for its service class. This change in persistent disk size is a reduction from the previous requirement of double the message spool size. For example, the new 50 GB default message spool size for the Broker 250 class service now requires 65 GiB-sized disks per broker (two disks total). See the 10.7.1 Event Broker Service release note, and Volume Size for High-Availability Event Broker Services for a table listing the persistent disk size requirements.

SAP will provide notice soon on how customers can upscale the message spool size for existing upgraded event broker services to the new default sizes and overhead requirements.

Event Broker Service Version 10.7.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version 10.7.1.

For Customer-Controlled Regions, new event broker services created using version 10.7.1 have new minimum persistent disk space requirements. The new minimum persistent disk space requirement is reduced, from double the message spool size to 30% greater than the default message spool size, for the event broker service's class type. Customers should note that the default spool size for each class has also increased. The following table lists the new minimum disk size requirement by service class.

Service Class	Minimum Persistent Disk Size for Version 10.7.1 and Later
Standard	35 GiB
Broker 250	65 GiB x2
Broker 1K	260 GiB x2
Broker 5K	520 GiB x2
Broker 10K	780 GiB x2
Broker 50K	1040 GiB x2
Broker 100K	1300 GiB x2

See Message Spool Size Requirements in General Resource Requirements for Kubernetes and Default Port Configuration for the updated persistent disk space requirements.

For more information about the increased default spool size change, see the SAP Increases Default Spool Size for Event Broker Services in Advanced Event Mesh release note.

To create event broker services in 10.7.1, you can use the version selection feature and select version 10.7.

TLS Support Added to Provide Enhanced Security for Syslog Forwarding

SAP has introduced TLS protocol support when forwarding syslogs to an external system. TLS support enhances security by providing encryption when forwarding syslogs.

You can enable syslog forwarding using the new TLS radio button on the Add Syslog Forwarding Destination dialog when adding or editing syslog forwarding for an event broker service.

Users should also be aware at this time that syslog forwarding does not support HTTP proxies.

To add, or edit syslog forwarding, see Forwarding Logs to an External System.

Event Portal Enhancements to Help Users Locate Assets

Event Portal has several improvements to help users locate their event-driven assets in various screens in Event Portal. These include:

• In Designer, text searches for objects use "contains" criteria instead of "starts with".

• Custom attributes of type “Simple” can now support the entry of values with special characters. This enables various new use cases. For example, users can filter on all applications or events (or other objects) in the Catalog that have custom attributes with values containing a specific email address or set of email addresses. Thereby helping users better categorize and locate their event-driven assets.

  The following special characters are supported: period [.], hyphen [-], en dash [–], underscore [_], at [@], slash [/], and parentheses [( )].

• Users can now toggle the graph view setting, “Show Object Full Names”, in both Runtime Event Manager and Designer. This helps find objects with longer names where the unique part is towards the middle or end of the name.

Event Management Agent User Experience Improvements in Event Portal

The Event Management Agent installation and use for Upload Scan File mode have been simplified. We've reduced the number of steps and you now must perform only a single operation to scan event brokers and schema registries, and another single operation to manually upload the scan files to Event Portal. When using Upload Scan File mode, the Event Management Agent is stopped and cleaned up after the scan and upload operations complete to reduce resource consumption and meet business security requirements.

For more information, see Setting Up Event Broker Connections.

Graphical Designer Now Available in Event Portal

Event Portal introduces new graphical design capabilities in Designer. This first phase of the graphical designer provides a graphical view of the event-driven architecture for each of your application domains, along with the ability to customize the arrangement of the application and event icons in the graph. For more information, see Using the Graph View.

The graph displays the latest, non-retired version of each application and event in the application domain, and shows the intended pub/sub relationships between them, as well as the relationships with events and applications in other application domains.

If you have Editor level access or higher to the application domain, as you drag objects around in the graph to customize the view, the changes are automatically saved and can be viewed by other users who have access to the application domain. You can also double-click on an application or event icon in the graph to view or edit the details of the object.

Adding Application Versions to Runtime Event Manager in Event Portal

In December 2022, we deprecated the ability to directly associate application versions with modeled event meshes in Designer and replaced it with associating application versions to model event brokers within modeled event meshes. For more information about associating application versions with modeled event meshes, see Adding Applications to Environments.

We have now removed all remaining direct associations of applications to modeled event meshes in Event Portal.

This change means that if you had application versions associated with modeled event meshes that had not been updated since December 2022, you may have modeled event meshes in Runtime Event Manager that no longer contain any objects. All of your objects are still in Designer and you can reassociate them.

If you need assistance, please contact SAP.

Event Broker Service Version 10.7.0 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.7.0.

Event broker service 10.7.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in Advanced Event Mesh, see Version Adoption .

This release includes a variety of security and bug fixes; no new major features are included.

To create a 10.7.0 event broker service, you can use the version selection feature and select version 10.7 (Preview). Upgrades of existing services to 10.7.0 are not supported.

Kafka Bridge Now Available for Existing Event Broker Services in Advanced Event Mesh

SAP now supports Kafka bridges for existing event broker services in advanced event mesh that are upgraded to 10.6.1 and greater.

After upgrading your existing event broker service to 10.6.1, you can enable Kafka bridge with a scale up. During the scale up, SAP performs the required configuration changes to enable Kafka bridges on the existing event broker service. The scale up requires a small maintenance window of approximately 10 to 15 minutes.

To schedule a Kafka bridge scale up for your existing event broker service, contact SAP.

To upgrade your event broker service to 10.6.1, see Upgrading Event Broker Services or contact SAP.

The number of Kafka bridges and connections available to your event broker service depends on its service class. See Service-Level Limits for Each Service Class for more information. To configure Kafka bridges for your event broker service after a scale up, see Configuring Kafka Bridging

Enhanced Cluster Manager User Interface with New List View

SAP is introducing an updated and enhanced user interface (UI) for Cluster Manager in Mission Control. Customers should notice that the enhanced UI is very similar to the previous UI, with some changes and additional features.

The most significant change is the availability of a list view. You can access the list view by clicking the List View icon in the top-right corner of the screen. When in list view, Cluster Manager shows a list of event broker services in a table-like format. Each entry in the list features the same information as appears on the tiles representing the event broker services when Cluster Manageris in tile view. The list view allows you to select multiple event broker services. Currently, you can use this to delete multiple event broker services at the same time or to create an event mesh.

Other new features of the enhanced UI include:

• The filter field now provides the ability to use an asterisk as a wild card. You can place an asterisk at the beginning or end of a string to return results including all event broker services matching the string plus wild card. For example, entering ‘My-*’ returns all services with names starting with My-, including My-First-Service, My-Second-Service, and My-New-Service.

• The tiles in the tile view now show the complete event broker service name, up to the maximum of 50 characters.

• You can rename an event broker service by opening a rename dialog directly from the tile or list entry for a service. See Changing the Name of an Event Broker Service for more information.

• Deleting an event broker service now produces a confirmation dialog. You must confirm the deletion by entering the event broker service name into the dialog. See Deleting Event Broker Services for more information.

See Viewing Event Broker Services for information on using Cluster Manager, including the new list view and features.

SAP Integration Suite, Advanced Event Mesh Releases (2023)

 

Event Broker Service Version 10.6.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.6.1.

This event broker service version features support for Integrated Kafka Bridges for new event broker services created with this release. Support for Integrated Kafka Bridges for existing event broker services will come with upcoming updates.

• Event broker services under 5k class support up to 10 Kafka bridges and 300 connections.

• Event broker services over 5k class support up to 50 Kafka bridges and 2000 connections.

This release introduces increased memory requirements for event broker services. These additional memory requirements are to support the new Kafka bridge feature. Clusters hosting event broker services now require additional memory, as outlined below:

• 100 to 1K class - 700 MiB

• 5k class and above - 4000 MiB

You can view a complete list of memory requirements in Memory Resource Requirements.

If you are upgrading your existing event broker service to 10.6.1 and have any Kafka bridges in place from the Kafka beta, you must delete these bridges before upgrading your service.

To create event broker services in 10.6.1, you can use the version selection feature and select version 10.6.

Advanced Event Mesh Now Supports EKS On AWS Outposts as a Controlled Availability Feature

SAP now supports deploying event broker services on-premises to Amazon Elastic Kubernetes Service (EKS) on AWS Outposts Racks.

Support for AWS Outposts is currently in Controlled Availability. Controlled Availability indicates full support but with the potential requirement of additional time, tuning, and configuration.

Validation of releases for EKS on AWS Outposts occurs as part of our Other category of supported Kubernetes providers. For information on how we validate releases, see Kubernetes Upgrades in SAP Integration Suite, Advanced Event Mesh . For a summary of supported Kubernetes versions, see Supported Kubernetes Versions.

Deploying advanced event mesh to EKS on AWS Outposts has certain prerequisites, including:

• Support is limited to EKS on the AWS Outposts Rack.

• The AWS Outposts must be configured to use direct VPC routing (DVR) for AWS Outposts.

• The storage class must be configured to use GP2 storage.

• If you require a network load balancer style option for connecting to the event broker services on the AWS Outposts, then you must use a custom MetalLB-based load balancer provided by SAP.

To learn more, or to start the process of deploying to EKS on AWS Outposts, see Installing in AWS Outposts or contact SAP.

Ability to Enhance Messaging Performance with WAN Optimization for Advanced Event Mesh

SAP now provides the ability to perform wide area network (WAN) optimization, otherwise known as WAN Tuning, for customers who want to increase messaging performance between event broker service in their WAN. WAN Optimization can increase the messaging performance between event broker service that are dispersed over different geographic locations.

SAP performs WAN optimization using a DaemonSet that configures the TCP network settings with increased memory size on the worker nodes hosting the event broker service. Customers wanting to take advantage of SAP’s WAN optimization should consider the following:

• The DemonSet must run in privileged mode.

• The hostNetwork settings must be set to true so the DeamonSet can see TCP settings that are not namespaced.

• The worker nodes need to be configured before establishing connections.

For more information, see Using Wide Area Network Optimization for Event Broker Services in Kubernetes Clusters or contact SAP.

Event Portal SAP Queue Configuration Management in Designer

We are pleased to announce the general availability of Event Portal SAP queue configuration management in Designer. This new feature enables you to provide granular definition for your SAP event queue consumers in Designer so that Event Portal can reflect and provide an accurate view of your runtime assets.

With SAP queue configuration management in Designer, you can:

• Add configurations to SAP event queue consumers
• Start defining queue configurations from a default example
• Edit queue configurations
• Remove queue configurations from SAP event queue consumers

These capabilities will be extended with upcoming Event Portal features to help automate the configuration of your SAP event broker services in the runtime.

For more information, see: Configuring Event Brokers in Event Portal.

Event Portal KPI Dashboard

We are pleased to announce the availability of the Event Portal 2.0 KPI Dashboard. This new feature enables you to view the reuse indexes of your Designer events and therefore measure a key aspect of your Event-Driven Architecture (EDA) efficiency.

With the KPI Dashboard, you can:

• view reuse indexes for all your shared and non-shared Solace and Kafka events in Designer whether you created those events as part of you design-first strategy or whether you imported those events from your runtime environments with the Discovery & Audit feature

• view the 20 most and the 20 least reused events in your EDA

• filter the KPI Dashboard by application domains so you can compare the reuse indexes of events across different development teams or parts of your organization

The KPI Dashboard helps you understand how your events are used in your EDAs and make the right decisions to update your events so you can have the maximum return on investments in your EDAs.

For more information, see KPI Dashboard.

Use the v2 REST API to Configure OAuth Profiles for Event Broker Service Authentication

You can now use the new SEMP Proxy v2 REST API to configure OAuth profiles for your event broker services. OAuth profiles provide enhanced flexibility for managing access to your event broker services.

You can configure up to three OAuth profiles per event broker service using the SEMP Proxy v2 REST API. You link the OAuth profiles using your identity provider to existing roles in advanced event mesh. With OAuth Profiles configured on your event broker service, you can provide varying levels of access on a per-event broker service basis for both users and machines. Examples of how you can control access include:

• restricting user or machine access to event broker services entirely

• granting permission to edit certain event broker services, while restricting access to only viewing others

• allowing access to event broker services without granting access to the SAPCloud Console

See Configuring OAuth Profiles for Management Access to Event Broker Services for more information.

Event Broker Service Version 10.6.0 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.6.0.

Event broker service 10.6.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. Preview releases have six months of technical support. For information about software event broker service types in advanced event mesh,see Version Adoption .

This release includes a variety of security and bug fixes; no new major features are included.

To create a 10.6.0 event broker service, you can use the version selection feature and select version 10.6 (Preview). Upgrades of existing services to 10.6.0 are not supported.

High Availability Event Broker Services in Advanced Event Mesh now Support Client Certificate Authentication within Bridges and REST Consumers

Advanced event mesh customers can now install client certificates directly to the individual nodes of enterprise high-availability event broker services (version 10.5.1 and later) when configuring a Message VPN (static) or DMR bridge on the event broker service.

Installing client certificates directly to the nodes of the event broker services in a bridge increases security. It requires the event broker services to authenticate with each other when communicating. When the client certificate is on both nodes of the event broker service, it maintains authentication if one node takes over.

Using this feature, you can also copy and synchronize client certificates on your event broker service nodes. This is useful when one node doesn't have a certificate or has a different one than its partner node.

For more information, see Installing and Synchronizing Client Certificates for High-Availability Event Broker Service in Bridges.

Advanced Event Mesh Now Supports Connectivity Using AWS Transit Gateway in Dedicated Regions

Customers in Dedicated Regions can now use their own AWS Transit Gateway for event broker service connectivity as a controlled availability feature.

In Dedicated Region, AWS Transit Gateway provides a method for connecting the event broker service to a Virtual Private Cloud (VPC) through a central hub. This can simplify your networking requirements while retaining the benefits advanced event mesh offers. See Networking Options for Dedicated Region Deployments for more information.

To learn more, or start using your AWS Transit Gateway with advanced event mesh, contact SAP.

Event Broker Service Version 10.5.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.5.1.

This event broker service version features support for up to 3 billion queue messages, depending the on event broker service tier. See the Advanced Event Mesh Increases the Maximum Number of Queue Messages for more details. 10.5.1 has the same increased memory requirements outlined for 10.5.0 (see the 10.5.0 release note) to accommodate the new queue message. The increased queue message size allows event broker services to support applications that require large numbers of messages to be available for replay.

To create event broker services in 10.5.1, you can use the version selection feature and select version 10.5.

Advanced Event Mesh Increases the Maximum Number of Queue Messages

With the release of event broker service 10.5, advanced event mesh has increased the default maximum amount of queue messages supported by event broker services.

• Service tiers under 5K (including Developer, 250, and 1K) now support 240 million queue messages
• Service tiers 5K and greater now support 3 billion queue messages

Event broker service tiers that support up to 3 billion queue messages require an additional 8,294 MiB per messaging pod. Deployments in Customer-Controlled Regions must ensure their Kubernetes clusters meet this enhanced memory requirement. For information, see Memory Resources for Event Broker Services and General Resource Requirements for Kubernetes and Default Port Configuration.

You can see the current queue message size of your existing event broker services on the service detail page in Cluster Manager in the Cloud Console. The maximum queue messages for existing event broker services can be scaled up after upgrading to version 10.5. See Upgrading Event Broker Services or contact SAP.

Event Portal 2.0 Discovery and Audit Now Available

We are pleased to announce the General Availability of the Event Portal 2.0 Discovery and Audit features. These features enable you to populate Event Portal by collecting data from your event brokers in the runtime, compare your runtime broker configurations with your design time intent to identify any discrepancies, and synchronize your runtime data with your design.

With discovery and audit, you can:

• connect Event Portal to your Kafka and Solace event brokers and Confluent Schema Registries
• discover Kafka topics, consumer groups, and associated configuration details from your Kafka clusters
• discover schemas from your Confluent Schema Registries
• discover queues and queue configurations from your Solace event brokers and event broker services
• upload discovery scans to Event Portal even if your event brokers can't access Event Portal or if you need to redact data from the broker scans
• audit all your runtime objects and detect any differences compared to your design
• import discovered data into Event Portal and make it available for searches in Catalog
• run subsequent discovery scans and view new discrepancies as audit results
• update or synchronize Event Portal with runtime changes
• tag audit results for actions on your event brokers
• visualize your EDAs in runtime graphs

Discovery and audit help you govern your EDAs, synchronize your runtime and design data, and enables the reuse of your EDA assets to expand your EDA and contribute to the success of your businesses.

For more information, see Discovering Runtime Data.

Insights Advanced Viewer Now Available for Insights

Insights subscribers can now assign the Insights Advanced Viewer role to users in their organization.

Users assigned the Insights Advanced Viewer role can view the Datadog dashboards provided as part of your Insights subscription. This permission does not allow them to perform other actions like editing or cloning the dashboards.

This is useful for providing access to the dashboard information to members of your organization, such as developers or support teams, who can benefit from it.

See Managing Users, Groups, Roles, and Permissions and Configuring an Existing User to Access Datadog or contact SAP to learn more about the Insights Advanced Viewer role.

Event Broker Service Version 10.5.0 Available in SAP Integration Suite, Advanced Event Mesh for Kubernetes-Based Deployments

Customers can now create event broker services using broker version, 10.5.0.

Broker version 10.5.0 is a Preview release. You cannot upgrade your existing event broker services to a Preview release. SAP also only provides six months of technical support for preview releases. For information about software event broker release types in advanced event mesh, see Version Adoption .

This release introduces increased memory requirements for event broker services in the Enterprise 5K service class and higher. Clusters hosting Enterprise 5K event broker services and above require the following additional memory per messaging node:

• 5K and 10K: 7065.6 MiB

• 50K and 100K: 9113.6 MiB

This requirement does not extend to the monitoring node in a high-availability deployment. You can view a complete list of memory requirements in Memory Resource Requirements. The additional memory requirement is to support 3 billion queue messages.

To create a 10.5.0 event broker service, you can use the version selection feature and select version 10.5 (Preview). Upgrades of existing services to 10.5.0 are not supported.

Event Portal Now Visualizes a Specific Object’s Relationships

Event Portal now provides a visualization to view a specific object’s relationships. This object relationship visualization provides a refined view of your event-driven architecture (EDA), focused on a specific object of your choice.

To view the new visualization, right-click an object in the modeled event mesh Graph view and select Show Relationships. You can easily navigate between both visualizations to get either a refined or comprehensive view of your EDA. For more information, see Viewing Object Relationships.

Also, the warning indicators on the modeled event mesh Graph view are no longer displayed by default. You can enable them in the Graph view settings. This setting also applies to the new relationship visualization.

Event Broker Service Version 10.4.1 Available in Advanced Event Mesh

Customers can now create event broker services using broker version, 10.4.1.

This event broker service version features partitioned queues. Partitioned queues are non-exclusive queue sub-types that use partition keys and partitions to identify a message’s context and assign it to a specific consumer instance. Partitioned queues offer event filtering, in-order processing, and when combined with load-balancing and auto-scaling, intelligent fast rebalancing and dynamic consumer scaling. For more information, see Partitioned Queues.

10.4.1 event broker services also introduce send spans for distributed tracing. Send spans complete the end-to-end tracing of events through your estate. They include transmission and response information from the consumer, including the outcome (ACK/NACK).

To create event broker services in 10.4.1, you can use the version selection feature and select version 10.4.

Advanced Event Mesh Now Supports Canonical Charmed Kubernetes and Anthos as Deployment Options

SAP now supports the deployment of event broker services on-premises to Canonical Charmed Kubernetes. Support has also been added for the deployment of event broker services to Anthos in Google Cloud and AWS Cloud.

Support for both providers is currently in Controlled Availability. Controlled Availability indicates full support but with the potential requirement of additional time, tuning, and configuration.

Validation of releases for either of these new providers occurs as part of our Other category of supported Kubernetes providers. For information on how we validate releases, see the Kubernetes Upgrades in SAP Integration Suite, Advanced Event Mesh . For a summary of supported Kubernetes versions, see Supported Kubernetes Versions.

Deploying to Canonical Charmed Kubernetes is similar to other on-premises deployments. Deploying Anthos on Google Cloud or AWS is similar to other cloud deployments. To learn more, or to start the process of deploying to either of these new Kubernetes options, contact SAP.

Event Portal Now Allows Moving Objects Between Application Domains

Event Portal now allows you to move objects from one application domain to another via a streamlined process, saving you valuable time and effort. For more information, see our documentation for Moving Objects Between Application Domains.

Advanced Event Mesh Now Supports Kubernetes Version 1.25

Kubernetes version 1.25 is now supported for all primary category Kubernetes’ providers, which include:

• Amazon Elastic Kubernetes Service (EKS)
• Azure Kubernetes Service (AKS)
• Google Kubernetes Engine (GKE)

Support for other providers and distributions occurs according to the Kubernetes Provider Categories and Validation section of our Kubernetes’ adoption policy.

Advanced event mesh follows a defined Kubernetes adoption policy to stay up to date with the release cadences of our supported providers and distributions. For more information about the policy, see Kubernetes Upgrades in SAP Integration Suite, Advanced Event Mesh .

SAP recommends upgrading your event broker services before upgrading your Kubernetes cluster in a Customer-Controlled Region. This ensures compatibility and minimizes downtime. See upgrading your Upgrading Event Broker Services for more information.

SAP Now Offers Forwarding of Insights Data to Customer Datadog Accounts

SAP now allows sending data collected by Insights to your own Datadog account or sub-organization as a Controlled Availability (CA) feature.

When enabled, SAP forwards data collected as part of your Insights subscription to your Datadog account. SAP provides this data as is to your Datadog account. You are responsible for creating your own monitors and dashboards within your Datadog account to leverage the Insights data we provide.

Forwarding your Insights data to your own account offers many benefits, including:

• Centralizing the data alongside other infrastructure data you already collect.
• Eliminates the need to switch between Insights and your own Datadog account.
• Allows your application teams to make sense of the data using tools they know in an already familiar environment.
• Provides wider access to your Insights data while retaining the benefits and options of your Insights subscription that ensure your event mesh is healthy.

See the Forward Insights Data to Your Own Datadog Account documentation to learn more about this feature.

Event Broker Service Version 10.4.0 Available in Advanced Event Mesh for Kubernetes Based Deployments

Customers can now create event broker service using broker version, 10.4.0.

Event broker service 10.4.0 is a Preview release, the first release of this type for a advanced event mesh-based event broker service. SAP plans to make all future Preview releases available to advanced event mesh customers. Releases of this type are intended for feature introduction and integration and include a subset of upcoming features that offer insights into the next Production release. You cannot upgrade your existing event broker services to a Preview release, and should be aware that releases of this type are limited to six months of technical support. For information about software event broker release types in advanced event mesh, see Version Adoption .

This release brings support for Partitioned Queues / MQ-Style Message Groups / Consumer Groups (Respect JMSXGroupID) advanced event mesh.

To create a 10.4.0 event broker service, you can use the version selection feature and select version 10.4 (Preview). Upgrades of existing services to 10.4.0 are not supported.

Event Portal Schema Content Type Deprecation

The Event Portal 2.0 schema content type attribute has been deprecated. Schema content types are a runtime concept and they did not provide useful value in the way they were implemented.

Schema content types have been removed from Event Portal in the Cloud Console and are deprecated in the APIs.

Event Broker Version 10.3.1 Available in Advanced Event Mesh for Kubernetes-Based Deployments

Customers can now create event broker services using broker version, 10.3.1. These event broker services support 240 million queue messages.

To create event broker services in 10.3.1, you can use the version selection feature and select version 10.3. Upgrades of existing services to 10.3.1 are not supported.

Referenced Schema Support in Event Portal 2.0

We’re pleased to announce the availability of referenced schemas in Event Portal 2.0.

Users can now reference other schemas within complex schemas and manage their associations.

Schemas also now support the Protobuf schema type.

For more information about the change, see Schemas.

Removing Proxy Mode for Monitoring Traffic

The Proxy Mode option for setting up connections from Customer-Controlled Regions to the centralized monitoring service has been deprecated. For more information, see: Monitoring Traffic for Customer-Controlled Regions.

Event Portal Custom Attribute Enhancements

When defining custom attributes in Event Portal, you can now define whether a custom attribute is available across all application domains or scoped to a specific application domain. This update enables application teams to better govern custom attributes across their organization.

Custom attributes can now also be defined with either a simple or complex value.

For more information on these enhancements, see Using Custom Attributes.

Renaming Event Portal Messaging Services

To better describe and abstract SAP event brokers, Kafka clusters, and other core components of event-driven architecture technologies in Event Portal 2.0, messaging services were renamed to event brokers.

This change was implemented only in the Cloud Console and the documentation at this time.

Using Replication for Disaster Recovery for Event Broker Services

You can now use replication as the solution for disaster recovery of deployments of event broker services in advanced event mesh. You can configure replication with any deployment ownership model (Public Region, Dedicated Region , and Customer-Controlled Region). The solution is available as Controlled Availability. Contact SAP to get more information about using and configuring replication for your event broker services.

Advanced Event Mesh now Supports Kubernetes Version 1.24

Kubernetes version 1.24 is now supported on all primary category Kubernetes providers, including Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), and Google Kubernetes Engine (GKE). Support for other providers and distributions occurs according to the Kubernetes Provider Categories and Validation section of the Kubernetes adoption policy.

Advanced event mesh follows a defined Kubernetes adoption policy to stay up to date with the release cadences of our supported providers and distributions. This policy is available at Kubernetes Upgrades in SAP Integration Suite, Advanced Event Mesh .

SAP recommends upgrading your event broker services before upgrading your Kubernetes cluster in a Customer-Controlled Region or scheduling SAP to perform the upgrade in a Public Region or Dedicated Region. This ensures compatibility and minimizes downtime. See upgrading your Upgrading Event Broker Services for more information.

Event Broker Version 10.2.1 Available in Advanced Event Mesh for Kubernetes-Based Deployments

Customers can now create event broker services using software event broker version 10.2.1. As part of this new version, the following key features are now available in advanced event mesh:

• Add Stalled State to Show Bridge Output (Customer Configured)
• Broker Support For Message NACK

In addition to the above two features, as of software event broker version 10.1.1 39 and greater, new advanced event meshevent broker services are created with a default REST SSL Server Certificate Validation maximum certificate chain depth value of 8.

To create event broker services in 10.2.1, you can use the version selection feature and select version 10.2.

SAP Integration Suite, Advanced Event Mesh Releases (2022)

 

Event Portal 2.0 Introduces Application Domain Export and Import

The following updates make Event Portal 2.0 easier and more powerful to use to design, document, and share your event-driven architecture:

• Export/Import Application Domains: You can now export and import application domains. You can select one or more application domains for export to a file, which can then be imported into other SAP accounts. This feature allows you to easily share your EDA. You can also import sample application domains for different industry use cases, so that you don’t have to start from scratch. See Exporting and Importing Application Domains for more information about using this capability.
• Event API Products: You can now apply topic address variable filters to define more granular event streams in your Event API Products.
  • See Creating an Event API Product for more information on filters.
  • AsyncAPI download now supports the AsyncAPI Servers object.

To learn more about all of the available features, see the Event Portal 2.0 documentation.

Event Portal 2.0 Lifecycle Management is now GA

The following Event Portal 2.0 features are now Generally Available:

• Version control and lifecycle states: Create and track every version of each object type through their lifecycle. Available for applications, Event API Products, event APIs, events, schemas, and enumerations.
• Custom attributes: Customize Event Portal objects with additional attribute and value data so you can better integrate Event Portal data with your organization's operational processes. You can also search for objects with custom attributes using configurable search filters in Catalog.
• Event API Products and event APIs:
  • Both are searchable in Catalog.
  • Both can now be integrated with third party API management platforms via the Event Portal published REST APIs. Application teams can use Event Portal to create and lifecycle manage Event API Products, while consumers across their organization, partner ecosystem, and customer base can find and request access to them via the same developer portals they use to access REST APIs.
    • Integration support for specific API Management systems will be added over time.
  • Event API AsyncAPI specification download now includes support for the following operation bindings:
    • REST/RESTs, MQTT, MQTTs, MQTTWS, MQTTWSs, SMF, SMFs, SMFC, AMQP, AMQPs

Event Portal 2.0 is available to all users with Event Portal access. You can switch between Event Portal versions by following these instructions.

For more information, see our Event Portal 2.0 documentation.

Version 1.6.13 of Insights Advanced Monitoring Available

This release introduces several enhancements, a new metric, and updates to some widgets on dashboards. These features help Insights Advanced Monitoring with visualizing and managing your estate.

A new subscriptions.total_unique_subscriptions metric has been added to Insights. This metric tracks the number of unique system-level subscriptions within a DMR cluster. See Subscription Statistics in Insights Metrics and Checks for details.

Labels on Insights Advanced Monitoring dashboard widgets have been updated. The standard and services are now grouped and reported under the Single Node Service widget. High Availability Enterprise services now display under the HA Services widget. Some dashboards affected by this change include:

• Estate Overview
• Event broker service SLO

The auto-recovery time for the Message VPN Client Username - Connections - Total monitor has been updated. In situations where this monitor has no data, it now recovers within 24 hours.

This release also includes other minor fixes to aid with the monitoring of event broker services.

Event Broker Version 10.1.1 Available in Advanced Event Mesh for Kubernetes-Based Deployments

Customers can now create event broker services with 10.1.1. As with version 9.13.1, only new event broker services for Kubernetes-based deployments can access 10.1.1. Upgrades of existing event broker services to 10.1.1 are not available.

To create event broker services in 10.1.1, you can use the version selection feature and select version 10.1. When selecting the broker version, you should note that 10.1.1 is not the default version because it isn't available in all deployment scenarios.

Event Broker Version 10.0.1 Available in Advanced Event Mesh for All Regions and Deployment Types

Customers can now create event broker services using software event broker version 10.0.1. This version is available in all regions and deployment types. Like previous releases, features in each release are implemented in the context of software-as-a-service in advanced event mesh and as such, these key features are available:

• Replay Service—Configurable Topics
• Replay Messages to a Temporary Endpoint
• Copy One Message to an Endpoint
• RDP Wizard for Google Run

Customers can select 10.0 using the version selection feature when creating an event broker service

For customers that have deployed event broker services to customer-controlled regions, upgrades may need to occur to their deployment infrastructure to enable this version. To do this, contact SAP to coordinate this update.

Advanced Event Mesh

Advanced event mesh for SAP Integration Suite is now available. For more information abotu what you can do with advanced event mesh, see SAP Integration Suite, Advanced Event Mesh.