Not every integration scenario requires a full-fledged integration platform. For some scenarios, all you need is a lightweight way to connect an application or service directly to your event broker.

This is where the Micro-Integrations capability of SAP Integration Suite, advanced Event Mesh comes in.
They provide lightweight integration functionality to easily connect SaaS and legacy applications, LLMs and AI Agents, messaging services, data stores, file servers, etc. directly to your event brokers. It also supports basic transformations, comparable to message mappings.

The keyword here is lightweight. Micro-Integrations are not a replacement for Cloud Integration, it complements it. Cloud Integration is designed to handle integration complexity way beyond the level that the Micro-Integrations capability can handle. Micro-Integrations focus on simplicity, speed, and high volume use cases.

In practice, using Cloud Integration for simple pass-through scenarios from or to Advanced Event Mesh with no transformation (apart from perhaps a message mapping) can be inefficient. In high-volume scenarios (e.g. Event Streaming) it means you’re consuming a lot of messages without leveraging the true strength of Cloud Integration.
This is exactly where the Micro-Integrations capability adds value: handling lightweight, high-throughput integrations, closer to the event broker, while leaving the more complex transformations to Cloud Integration.

The following blog: Small but Great: Introducing Micro-Integrations for Advanced Event Mesh was published when Micro-Integrations were released and provides more background on the capability. I recommend reading it before continuing this blog, as it explains the capability and benefits in more detail, this blog focuses specifically on how to obtain access.

Initially, included with certain broker service classes (as from Broker 1K), now they are also available an an additional chargeable capability. This new metric you can be charged for each hour an additional Micro-Integration is in state “deployed”, the pricing can be found on SAP Discovery Center.

The following table shows how many Micro-Integrations (MI) are included with each broker service class, note that each MI can contain up to 5 flows:

This new (Micro-Integration by the hour) metric enables organizations to:

1. Leverage Micro-Integrations when they only have small brokers:
   We recommend having the same broker size for PROD and QA. This means that for a 3 tier environment the smallest setup is Broker 250 for PROD and QA and Broker 100 for DEV. In this case, Micro-Integrations are not included in your broker and if you want to use Micro-Integrations, you need to purchase it as a seperate line item.
2. Use additional flows:
   Every Micro-Integration comes with 5 flows, a single flow contains the details of a target/source system/queue/topic, error handling config (e.g. Dead Message Queues) and a message mapping.
   So let’s say, you have an SFTP source micro-integration, these flows can listen to their own SFTP server or directory/folder and map different objects, for example:
   • 5 flows that listen to the same SFTP server but each to a different directory.
     One listens to the directory /salesorders and maps sales order objects, another one that listens to /businesspartners and maps business partner objects, etc:
     in this case you require 1 Micro-Integration.
   • 5 flows that each listen to a different SFTP server but they both map and publish sales order objects:
     in this case you require 1 Micro-Integration
   • 10 flows that listen to the same SFTP server, but map different objects:
     in this case you require 2 Micro-Integrations
    
3. Leverage more Micro-Integrations than included in your Broker or Subaccount:
   Micro-Integrations cannot be shared across Subaccounts, so let’s say you have a 3 tier environment with a 1K Broker in PROD & QA and a 250 Broker (no MIs included) in DEV, each environment is hosted in a different SAP BTP Subaccount. In this case, you can leverage 2 Micro-Integrations in PROD, 2 in QA (as this is included in your Broker), but if you were to use Micro-Integrations on your DEV Subaccount, you would need to activate the entitlement for additional Micro-Integrations on your DEV Subaccount.
   Following the same example, if you want to use more than 2 Micro-Integrations in your PROD and/or QA environment, you also need to activate the entitlement for additional MIs on your PROD and/or QA Subaccount.

In this blog, we will walk you through the process of enabling the Micro-Integrations add-on within your SAP AEM environment, as well as the activation process of a 1K Broker or larger.

Assigning the entitlements to your SAP BTP Subaccount

In this first part of the blog, we will assign the required entitlements to the SAP BTP Subaccount. Depending on how you want to obtain Micro-Integrations, this can either be the entitlement for the Micro-Integration add-on or an entitlement for a broker service class that includes Micro-Integrations (Broker 1K or larger).
This part of the process needs to be done by the Subaccount or Global Account Administrator on SAP Business Technology Platform.

1. Go to your SAP BTP Cockpit
2. Navigate to the SAP BTP Subaccount, where you have deployed an Advanced Event Mesh environment and where you want to enable Micro-Integrations.
   

    

3. In your Subaccount, go to “Entitlements“, and click on “Edit“.
   

    

4. Now, click on “Add Service Plan” on the right top of the table.
   
5. Look for “integration-suite-advanced-event-mesh“. 
6. Now you should see “SAP Integration Suite, advanced event mesh“, under “Services available to this subaccount”, select this service.
   

    

7. Under “Available Plans”, select “micro-integration-add-on“. This entitlement allows you to create additional Micro-Integrations beyond those included with eligible broker service classes.
8. Optional: If you want to use the Micro-Integratoins included with your broker service, select the appropriate broker entitlement instead. For example, a Broker 1K includes two Micro-Integrations (this is smallest broker that includes MIs) , please have a look at the documentation if you want to know how many Micro-Integrations are included in your broker.
   You can also assign both entitlements if you want to use the Micro-Integrations included with your broker service and additional Micro-Integrations through the add-on.
   

    

9. Once you’ve selected the right service plans, click on “Add Service Plans” at the bottom of your screen.
   

    

10. Don’t forget to press the “Save” button.

    

     

     

Optional: Ensure a compatible broker is available

To deploy Micro-Integrations, you need at least one active broker in your Advanced Event Mesh environment. If you are using the Micro-Integrations included with a broker service, the minimum service class is Broker 1K. If you are using the micro-integration-add-on entitlement, any broker service class can be used. This section is written for organizations that want to deploy a broker that already includes Micro-Integration. The following steps are performed by the Mission Control Manager in SAP Integration Suite, advanced event mesh.

1. In your SAP BTP Subaccount, go to “Instances and Subscription” and open “SAP Integration Suite, advanced event mesh” (under “Subscriptions”).
   

    

2. Now, you are redirected to what we refer to as the “Cloud Console” in Advanced Event Mesh (you can always go back to the cloud console by clicking on the SAP logo on the top left).
3. In the Cloud Console, scroll down to “Mission control” and open “Cluster Manager“.
   

    

4. In the Cluster Manager you seee an overview of your existing brokers. If you don’t have a 1K Broker or a larger broker, click on “Create Service” on the right top.
   
5. Provide at least the following:
   • Service Name
   • Cloud provider & region
   • Service Type: Enterprise
   • Service Class: Broker 1K (or larger)
6. Click on “Create Service“. 
   

    

7. Once the service is ready, you should see a screen that looks like this (see screenshot below). This means that your broker was successfully created!
   

Granting access to Micro-Integrations

If you (or your admin) have successfully configured the appropriate Micro-Integration entitlement and/or broker service, we’re almost ready to create and deploy Micro-Integrations. The only thing you must verify is that you and/or the people who should create and deploy the MIs, have the “Micro-Integrations Manager” role assigned. This part of the process is done by the Account Administrator in SAP Integration Suite, advanced event mesh.

1. In the Cloud Console, click on the user icon (bottom left corner) and go to “Account Details“.
   
2. Now, go to “User Management” ➡️ “Users“, click on the 3 dots right next to the user you want to grant access to Micro-Integrations and hit “Edit“.
   

    

3. Go to the line “Micro-Integrations” and open the drop-down list, select “Micro-Integrations Manager“, and press “Save“. Now this user will be able to create and deploy Micro-Integrations in SAP Integration Suite, advanced event mesh. Repeat the previous 3 steps to give access to other users.
   

    

Discovering and creating Micro-Integrations

Once the appropriate entitlement has been assigned, a compatible broker is available, and the Micro-Integrations Manager role has been assigned to your user, you can create and deploy Micro-Integrations.

1. In the Cloud Console in Advanced Event Mesh, you should now see a tile with the title “Micro-Integrations“. Click on this tile.
   

    

2. Here, you will find an overview of all Micro-Integrations that are created. Click on “Create Micro-Integration” on the right top.
   

    

3. Now, you see an overview of all Micro-Integrations that you can create and configure with Advanced Event Mesh.
   

    

4. From this list, you can select a Micro-Integration that fits your use case and start configuring it. Configuring a Micro-Integration is very straight forward, you need the connection and credential details of the source or target system, as well as the queue/topic and broker credentials to create and configure the Micro-Integration.

If you want to try-out a Micro-Integration, I recommend to go through a blog I wrote earlier this year:
File to Mesh: Liberating SFTP Data with Micro-Integrations. 
In this blog, we create a Micro-Integration that listens to an SFTP server and publishes the lines of a CSV file one by one as (mapped) events to the broker. The File to Mesh use case is one where Micro-Integrations are commonly used.

 Not every integration scenario requires a full-fledged integration platform. For some scenarios, all you need is a lightweight way to connect an application or service directly to your event broker.This is where the Micro-Integrations capability of SAP Integration Suite, advanced Event Mesh comes in.They provide lightweight integration functionality to easily connect SaaS and legacy applications, LLMs and AI Agents, messaging services, data stores, file servers, etc. directly to your event brokers. It also supports basic transformations, comparable to message mappings.The keyword here is lightweight. Micro-Integrations are not a replacement for Cloud Integration, it complements it. Cloud Integration is designed to handle integration complexity way beyond the level that the Micro-Integrations capability can handle. Micro-Integrations focus on simplicity, speed, and high volume use cases.In practice, using Cloud Integration for simple pass-through scenarios from or to Advanced Event Mesh with no transformation (apart from perhaps a message mapping) can be inefficient. In high-volume scenarios (e.g. Event Streaming) it means you’re consuming a lot of messages without leveraging the true strength of Cloud Integration.This is exactly where the Micro-Integrations capability adds value: handling lightweight, high-throughput integrations, closer to the event broker, while leaving the more complex transformations to Cloud Integration.The following blog: Small but Great: Introducing Micro-Integrations for Advanced Event Mesh was published when Micro-Integrations were released and provides more background on the capability. I recommend reading it before continuing this blog, as it explains the capability and benefits in more detail, this blog focuses specifically on how to obtain access.Initially, included with certain broker service classes (as from Broker 1K), now they are also available an an additional chargeable capability. This new metric you can be charged for each hour an additional Micro-Integration is in state “deployed”, the pricing can be found on SAP Discovery Center.The following table shows how many Micro-Integrations (MI) are included with each broker service class, note that each MI can contain up to 5 flows:Service ClassNr. of Micro-Integrations IncludedBroker 100 (Developer)0Broker 250 (Smallest Production Broker)0Broker 1K2Broker 5K5Broker 10K8Broker 50K15Broker 100K25This new (Micro-Integration by the hour) metric enables organizations to:Leverage Micro-Integrations when they only have small brokers:We recommend having the same broker size for PROD and QA. This means that for a 3 tier environment the smallest setup is Broker 250 for PROD and QA and Broker 100 for DEV. In this case, Micro-Integrations are not included in your broker and if you want to use Micro-Integrations, you need to purchase it as a seperate line item.Use additional flows:Every Micro-Integration comes with 5 flows, a single flow contains the details of a target/source system/queue/topic, error handling config (e.g. Dead Message Queues) and a message mapping.So let’s say, you have an SFTP source micro-integration, these flows can listen to their own SFTP server or directory/folder and map different objects, for example:5 flows that listen to the same SFTP server but each to a different directory.One listens to the directory /salesorders and maps sales order objects, another one that listens to /businesspartners and maps business partner objects, etc:in this case you require 1 Micro-Integration.5 flows that each listen to a different SFTP server but they both map and publish sales order objects:in this case you require 1 Micro-Integration10 flows that listen to the same SFTP server, but map different objects:in this case you require 2 Micro-Integrations Leverage more Micro-Integrations than included in your Broker or Subaccount:Micro-Integrations cannot be shared across Subaccounts, so let’s say you have a 3 tier environment with a 1K Broker in PROD & QA and a 250 Broker (no MIs included) in DEV, each environment is hosted in a different SAP BTP Subaccount. In this case, you can leverage 2 Micro-Integrations in PROD, 2 in QA (as this is included in your Broker), but if you were to use Micro-Integrations on your DEV Subaccount, you would need to activate the entitlement for additional Micro-Integrations on your DEV Subaccount.Following the same example, if you want to use more than 2 Micro-Integrations in your PROD and/or QA environment, you also need to activate the entitlement for additional MIs on your PROD and/or QA Subaccount.In this blog, we will walk you through the process of enabling the Micro-Integrations add-on within your SAP AEM environment, as well as the activation process of a 1K Broker or larger.Assigning the entitlements to your SAP BTP SubaccountIn this first part of the blog, we will assign the required entitlements to the SAP BTP Subaccount. Depending on how you want to obtain Micro-Integrations, this can either be the entitlement for the Micro-Integration add-on or an entitlement for a broker service class that includes Micro-Integrations (Broker 1K or larger).This part of the process needs to be done by the Subaccount or Global Account Administrator on SAP Business Technology Platform.Go to your SAP BTP CockpitNavigate to the SAP BTP Subaccount, where you have deployed an Advanced Event Mesh environment and where you want to enable Micro-Integrations. In your Subaccount, go to “Entitlements”, and click on “Edit”. Now, click on “Add Service Plan” on the right top of the table.Look for “integration-suite-advanced-event-mesh”. Now you should see “SAP Integration Suite, advanced event mesh”, under “Services available to this subaccount”, select this service. Under “Available Plans”, select “micro-integration-add-on”. This entitlement allows you to create additional Micro-Integrations beyond those included with eligible broker service classes.Optional: If you want to use the Micro-Integratoins included with your broker service, select the appropriate broker entitlement instead. For example, a Broker 1K includes two Micro-Integrations (this is smallest broker that includes MIs) , please have a look at the documentation if you want to know how many Micro-Integrations are included in your broker.You can also assign both entitlements if you want to use the Micro-Integrations included with your broker service and additional Micro-Integrations through the add-on. Once you’ve selected the right service plans, click on “Add Service Plans” at the bottom of your screen. Don’t forget to press the “Save” button.  Optional: Ensure a compatible broker is availableTo deploy Micro-Integrations, you need at least one active broker in your Advanced Event Mesh environment. If you are using the Micro-Integrations included with a broker service, the minimum service class is Broker 1K. If you are using the micro-integration-add-on entitlement, any broker service class can be used. This section is written for organizations that want to deploy a broker that already includes Micro-Integration. The following steps are performed by the Mission Control Manager in SAP Integration Suite, advanced event mesh.In your SAP BTP Subaccount, go to “Instances and Subscription” and open “SAP Integration Suite, advanced event mesh” (under “Subscriptions”). Now, you are redirected to what we refer to as the “Cloud Console” in Advanced Event Mesh (you can always go back to the cloud console by clicking on the SAP logo on the top left).In the Cloud Console, scroll down to “Mission control” and open “Cluster Manager”. In the Cluster Manager you seee an overview of your existing brokers. If you don’t have a 1K Broker or a larger broker, click on “Create Service” on the right top.Provide at least the following:Service NameCloud provider & regionService Type: EnterpriseService Class: Broker 1K (or larger)Click on “Create Service”.  Once the service is ready, you should see a screen that looks like this (see screenshot below). This means that your broker was successfully created!Granting access to Micro-IntegrationsIf you (or your admin) have successfully configured the appropriate Micro-Integration entitlement and/or broker service, we’re almost ready to create and deploy Micro-Integrations. The only thing you must verify is that you and/or the people who should create and deploy the MIs, have the “Micro-Integrations Manager” role assigned. This part of the process is done by the Account Administrator in SAP Integration Suite, advanced event mesh.In the Cloud Console, click on the user icon (bottom left corner) and go to “Account Details”.Now, go to “User Management” ➡️ “Users”, click on the 3 dots right next to the user you want to grant access to Micro-Integrations and hit “Edit”. Go to the line “Micro-Integrations” and open the drop-down list, select “Micro-Integrations Manager”, and press “Save”. Now this user will be able to create and deploy Micro-Integrations in SAP Integration Suite, advanced event mesh. Repeat the previous 3 steps to give access to other users. Discovering and creating Micro-IntegrationsOnce the appropriate entitlement has been assigned, a compatible broker is available, and the Micro-Integrations Manager role has been assigned to your user, you can create and deploy Micro-Integrations.In the Cloud Console in Advanced Event Mesh, you should now see a tile with the title “Micro-Integrations”. Click on this tile. Here, you will find an overview of all Micro-Integrations that are created. Click on “Create Micro-Integration” on the right top. Now, you see an overview of all Micro-Integrations that you can create and configure with Advanced Event Mesh. From this list, you can select a Micro-Integration that fits your use case and start configuring it. Configuring a Micro-Integration is very straight forward, you need the connection and credential details of the source or target system, as well as the queue/topic and broker credentials to create and configure the Micro-Integration.If you want to try-out a Micro-Integration, I recommend to go through a blog I wrote earlier this year:File to Mesh: Liberating SFTP Data with Micro-Integrations. In this blog, we create a Micro-Integration that listens to an SFTP server and publishes the lines of a CSV file one by one as (mapped) events to the broker. The File to Mesh use case is one where Micro-Integrations are commonly used.  Read More Technology Blog Posts by SAP articles 

#SAPCHANNEL