In today’s digital economy, event-driven architectures (EDA) enable real-time insights and seamless integration across diverse system landscapes—whether connecting SAP applications or extending integration to third-party solutions. Organizations can now more efficiently discover, publish, and consume events and APIs, empowering both developers and integration architects.
In this blog, we’ll explore what these capabilities mean in practice, how to connect Advanced Event Mesh with Developer Hub, and how to publish events from business systems into a centralized discovery catalog—bringing event-driven integration patterns into the mainstream of enterprise integration design.
Create a Destination to Connect Advanced Event Mesh with SAP Developer Hub
To enable the discovery and publication of events from Advanced Event Mesh in Developer Hub, the first step is to establish a secure connection between the two services. This connection is configured using a destination in SAP Business Technology Platform (BTP).
In the following sections, we’ll explain the purpose of this destination and walk through the key configuration details required to set it up successfully.
Why is a Destination Required?
A destination serves as the secure connectivity bridge between Developer Hub and your Advanced Event Mesh (AEM) instance. This connection is essential for Developer Hub to discover EventAPIs within AEM and display them as Events in the central catalog.
Note: In the current release, the destination is used exclusively for the discovery phase of the event lifecycle.
Create the Destination in SAP BTP
1. To create the destination, log in to SAP BTP Cockpit and navigate to the source subaccount where Developer Hub is enabled.
2. From the left navigation pane, go to Connectivity → Destinations and choose Create. Select From Scratch to manually define a new destination.
3. In the Destination Details section, enter all required information:
- Name: Provide a unique and meaningful name for the destination.
- Type: Choose HTTP as the destination type.
- Description: Provide a brief description of the Advanced Event Mesh (AEM) system. This description appears for the AEM business system in Developer Hub.
- URL: Enter the base URL of your Advanced Event Mesh portal.
- For authentication, choose BasicAuthentication.
Username: Enter the username of the technical user. This can be an email address.
Password: Use an API token generated from the Advanced Event Mesh portal as the password. - When creating the API token, ensure that the following permissions are assigned: a. Read any Application Domain (application_domain:get:*) b. Do anything to any Event API (event_api:*:*) c. Access to Event Portal Designer (event_designer:access). These permissions allow Developer Hub to read event definitions and interact with the Event portal.
- Enter the Additional Settings: Choose Internet as the Proxy Type.
- Add the following custom property to enable Advanced Event Mesh support in Developer Hub: Key: sap.isuite.dh.aem.enabled Value: true
4. Validate the destination.
After entering all details, choose Create.
You can optionally use Check Connection to verify that the destination has been configured correctly, and that Developer Hub can successfully connect to Advanced Event Mesh.
What’s Next?
Once the destination is set up, Developer Hub can start discovering events from Advanced Event Mesh. These events can then be reviewed, published, and made available to developers through the central catalog.
This simple setup step lays the foundation for enabling event-driven integration using SAP Integration Suite.
Discover and Publish Events from Advanced Event Mesh on Developer Hub
Once the destination between Advanced Event Mesh and SAP Developer Hub is in place, you can start making events available to developers by discovering and publishing them in Developer Hub.
This step is typically performed by a content administrator, who curates events and organizes them into products for easy discovery and reuse.
Before You Begin
To discover and publish events, make sure the following prerequisites are met:
- You are assigned the AuthGroup.Content.Admin role collection.
- EventAPIs are marked as shared in the Advanced Event Mesh portal.
Only shared events can be added to products and published in Developer Hub. If an event is not shared, update its settings in the Advanced Event Mesh portal before proceeding.
Discover Events in Developer Hub
- Log on to Developer Hub and navigate to Admin Center → Manage → Content. Here, you’ll see a list of available business systems. Select the Advanced Event Mesh business system to discover events exposed from it.
- Events in Advanced Event Mesh are organized under application domains. When you select an application domain, all events associated with that domain are displayed.
- If required, you can enable the option to Show shared events from other domains. This allows you to view and reuse events that have been shared across application domains.
Understand Event Visibility
Each application domain contains its own set of events:
- Shared events are visible across all application domains.
- Non-shared events are visible only within their own domain.
Only shared events can be added to a product in Developer Hub. This ensures that events intended for broader consumption are clearly identified and reusable.
- After selecting the relevant events, you can group them into a product. Products help organize events logically and make them easier for developers to discover.
- When creating a product, you can include:
- Shared events from the current application domain
- Shared events from other application domains
This flexibility allows you to design products that align with business capabilities rather than technical boundaries.
3. Publish the product
Once the product details are reviewed, you can choose how to proceed:
- Save as Draft
Keeps the product in a draft state. Draft products are not visible in the catalog and can be published later. - Publish
Makes the product visible in the Developer Hub catalog so developers can discover it.
Published products are discoverable but not yet available for subscription.
What Happens Next?
After publishing, your events are visible in Developer Hub and ready to be explored by developers. This enables teams to quickly understand available event streams and build event-driven applications or integrations using Advanced Event Mesh.
Together with the destination setup, this completes the core flow for exposing Advanced Event Mesh events through Developer Hub.
This approach helps organizations promote event reuse, improve discoverability, and simplify adoption of event-driven integration patterns across the landscape.
Final Thoughts
SAP Integration Suite’s Advanced Event Mesh paired with Developer Hub empowers organizations to treat events as first-class citizens in integration landscapes.
By connecting Advanced Event Mesh to Developer Hub and publishing your event sources and APIs, you:
- Promote transparency of event streams
- Enable faster development cycles
- Support modern application patterns that rely on real-time business context
Whether you’re driving integrations for ERP, CRM, third-party SaaS systems, or custom applications, this capability helps you move from point-to-point communication to a flexible, scalable event-driven architecture.
In today’s digital economy, event-driven architectures (EDA) enable real-time insights and seamless integration across diverse system landscapes—whether connecting SAP applications or extending integration to third-party solutions. Organizations can now more efficiently discover, publish, and consume events and APIs, empowering both developers and integration architects.In this blog, we’ll explore what these capabilities mean in practice, how to connect Advanced Event Mesh with Developer Hub, and how to publish events from business systems into a centralized discovery catalog—bringing event-driven integration patterns into the mainstream of enterprise integration design.Create a Destination to Connect Advanced Event Mesh with SAP Developer HubTo enable the discovery and publication of events from Advanced Event Mesh in Developer Hub, the first step is to establish a secure connection between the two services. This connection is configured using a destination in SAP Business Technology Platform (BTP).In the following sections, we’ll explain the purpose of this destination and walk through the key configuration details required to set it up successfully.Why is a Destination Required? A destination serves as the secure connectivity bridge between Developer Hub and your Advanced Event Mesh (AEM) instance. This connection is essential for Developer Hub to discover EventAPIs within AEM and display them as Events in the central catalog.Note: In the current release, the destination is used exclusively for the discovery phase of the event lifecycle.Create the Destination in SAP BTP1. To create the destination, log in to SAP BTP Cockpit and navigate to the source subaccount where Developer Hub is enabled.2. From the left navigation pane, go to Connectivity → Destinations and choose Create. Select From Scratch to manually define a new destination.3. In the Destination Details section, enter all required information:Name: Provide a unique and meaningful name for the destination.Type: Choose HTTP as the destination type.Description: Provide a brief description of the Advanced Event Mesh (AEM) system. This description appears for the AEM business system in Developer Hub.URL: Enter the base URL of your Advanced Event Mesh portal. For authentication, choose BasicAuthentication. Username: Enter the username of the technical user. This can be an email address. Password: Use an API token generated from the Advanced Event Mesh portal as the password.When creating the API token, ensure that the following permissions are assigned: a. Read any Application Domain (application_domain:get:*) b. Do anything to any Event API (event_api:*:*) c. Access to Event Portal Designer (event_designer:access). These permissions allow Developer Hub to read event definitions and interact with the Event portal.Enter the Additional Settings: Choose Internet as the Proxy Type.Add the following custom property to enable Advanced Event Mesh support in Developer Hub: Key: sap.isuite.dh.aem.enabled Value: true 4. Validate the destination.After entering all details, choose Create.You can optionally use Check Connection to verify that the destination has been configured correctly, and that Developer Hub can successfully connect to Advanced Event Mesh.What’s Next?Once the destination is set up, Developer Hub can start discovering events from Advanced Event Mesh. These events can then be reviewed, published, and made available to developers through the central catalog.This simple setup step lays the foundation for enabling event-driven integration using SAP Integration Suite.Discover and Publish Events from Advanced Event Mesh on Developer HubOnce the destination between Advanced Event Mesh and SAP Developer Hub is in place, you can start making events available to developers by discovering and publishing them in Developer Hub.This step is typically performed by a content administrator, who curates events and organizes them into products for easy discovery and reuse.Before You BeginTo discover and publish events, make sure the following prerequisites are met:You are assigned the AuthGroup.Content.Admin role collection.EventAPIs are marked as shared in the Advanced Event Mesh portal.Only shared events can be added to products and published in Developer Hub. If an event is not shared, update its settings in the Advanced Event Mesh portal before proceeding.Discover Events in Developer HubLog on to Developer Hub and navigate to Admin Center → Manage → Content. Here, you’ll see a list of available business systems. Select the Advanced Event Mesh business system to discover events exposed from it.Events in Advanced Event Mesh are organized under application domains. When you select an application domain, all events associated with that domain are displayed.If required, you can enable the option to Show shared events from other domains. This allows you to view and reuse events that have been shared across application domains.Understand Event VisibilityEach application domain contains its own set of events:Shared events are visible across all application domains.Non-shared events are visible only within their own domain.Only shared events can be added to a product in Developer Hub. This ensures that events intended for broader consumption are clearly identified and reusable.After selecting the relevant events, you can group them into a product. Products help organize events logically and make them easier for developers to discover.When creating a product, you can include:Shared events from the current application domainShared events from other application domains This flexibility allows you to design products that align with business capabilities rather than technical boundaries.3. Publish the product Once the product details are reviewed, you can choose how to proceed:Save as DraftKeeps the product in a draft state. Draft products are not visible in the catalog and can be published later.PublishMakes the product visible in the Developer Hub catalog so developers can discover it.Published products are discoverable but not yet available for subscription. What Happens Next?After publishing, your events are visible in Developer Hub and ready to be explored by developers. This enables teams to quickly understand available event streams and build event-driven applications or integrations using Advanced Event Mesh.Together with the destination setup, this completes the core flow for exposing Advanced Event Mesh events through Developer Hub.This approach helps organizations promote event reuse, improve discoverability, and simplify adoption of event-driven integration patterns across the landscape. Final ThoughtsSAP Integration Suite’s Advanced Event Mesh paired with Developer Hub empowers organizations to treat events as first-class citizens in integration landscapes.By connecting Advanced Event Mesh to Developer Hub and publishing your event sources and APIs, you:Promote transparency of event streamsEnable faster development cyclesSupport modern application patterns that rely on real-time business contextWhether you’re driving integrations for ERP, CRM, third-party SaaS systems, or custom applications, this capability helps you move from point-to-point communication to a flexible, scalable event-driven architecture. Read More Technology Blog Posts by SAP articles
#SAPCHANNEL