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 2023, 2022.

SAP Integration Suite, Advanced Event Mesh Releases (2024)

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 an Application.

• 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
Enterprise 250	25 GiB	50 GiB
Enterprise 1K	50 GiB	200 GiB
Enterprise 5K	200 GiB	400 GiB
Enterprise 10K	300 GiB	600 GiB
Enterprise 50K	500 GiB	800 GiB
Enterprise 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 Enterprise 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
Enterprise 250	65 GiB x2
Enterprise 1K	260 GiB x2
Enterprise 5K	520 GiB x2
Enterprise 10K	780 GiB x2
Enterprise 50K	1040 GiB x2
Enterprise 100K	1300 GiB x2

See Message Spool Size Requirements in 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 Management Agents.

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 an Application to an Environment.

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: Specifying Queue Configuration for a Solace Event Broker.

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 Management OAuth Profiles for Event Broker Service Authentication 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 Using AWS Transit Gateway for EKS Connectivity 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 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, 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 an additional 8,294 MiB per messaging node. 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.

For information about:

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 the Sample Application Domains page for a list of samples that you can download and import into Event Portal 2.0.
  • 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.

With the introduction of Standalone services, labels on Insights Advanced Monitoring dashboard widgets have been updated. The developer and standalone 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.