Dear Community,
this blog provides practical insights into setting up a proper landscape for SAP Integration Suite.
Intention:
With the move to Integration Suite as middleware, customers will reach an early point at which they need to consider their future landscape setup. SAP provides many resources (such as the Reference Architecture, Discovery Center, Naming Conventions, Learning Journey, Considerations on the System Landscape for Integration when On-boarding into SAP Cloud Integration, [SAP BTP Onboarding Series] Account Structure and Decision Making ) to help them get started and become familiar with the new environment. Based on multiple customer ramp-ups, a clear picture is emerging of what a solid setup can look like.
Approach:
We collect the basic information required to run and operate Integration Suite properly. This includes a simple consideration of the account setup and the services we recommend for your integration landscape (such as Transport Management, SAP Cloud ALM, etc.).
Solution:
How many tenants (SAP BTP subaccounts) are needed for SAP Integration Suite to support such a landscape?
"A general rule of thumb is to align the landscape of the SAP Integration Suite with the primary business system in your architecture."
However, the decision between a 2-tier or 3-tier landscape for SAP Integration Suite also depends on various organizational and functional factors:
- A 2-tier landscape is suitable for simpler scenarios where mostly preconfigured content is used.
- A 3-tier landscape is suitable for more complex environments with existing multi-tier on-premise systems and extended quality assurance requirements.
What about the sizing of Integration Suite in comparison to PI/PO?
As of now, the number of messages is the primary factor influencing cost. Other aspects — such as sizing — do not affect the price. Scaling is handled entirely by SAP, and there are predefined internal value sets. SAP Cloud Integration generally scales well (scale up/out), provided that the integration flows are designed according to the design guidelines.
For Edge Integration Cell, the concept is different, as the infrastructure is managed within the customer's private landscape. Therefore, planned sizing should be taken into consideration.
Are there differences between DEV, Test, and Prod regarding message calculation? What should we take into consideration?
SAP Integration Suite - Message Metric Definition serves as our source of truth for message calculation in SAP Integration Suite. It also includes the following important information: “There is no concept of development, test, and production landscapes in SAP Integration Suite. Messages on all tenants are metered based on the description in this note.”
What do we need to start with our Integration Suite setup?
As a very basic setup, we would take the Integration Suite subscription into consideration. This means, according to question 1, we are going to deploy and roll out our landscape according to our needs. The naming of directories is flexible and can be changed afterwards. Due to this fact, in our consideration we will name the base directory Development, Test, and Production, everything else is flexibel to your customer needs.
Architectural Overview BTP
General Naming - Stage Development
| Directory | Development |
| Subaccount | Dev – SAP Integration Suite |
| Subdomain | company-dev-sap-integration-suite-uniqueid or dev-sap-integration-suite-uniqueid |
| Cloud Foundry Org | dev-sap-integration-suite |
| Space | dev-sap-integration-suite |
General Naming - Stage Test
| Directory | Test |
| Subaccount | Test - SAP Integration Suite |
| Subdomain | company-test-sap-integration-suite or test-sap-integration-suite |
| Cloud Foundry Org | test-sap-integration-suite |
| Space | test-sap-integration-suite |
General Naming - Stage Prod
| Directory | Production |
| Subaccount | Prod - SAP Integration Suite |
| Subdomain | company-prod-sap-integration-suite-uniqueid or prod-sap-integration-suite-uniqueid |
| Cloud Foundry Org | prod-sap-integration-suite |
| Space | prod-sap-integration-suite |
Is there anything else we need to take into consideration?
Beyond the Integration Suite we recommend to take the following further Services also in consideation:
By default, you can leverage SAP's default Identity Provider (IDP) for user access and role management. Users who should work in the Integration Suite environment can be assigned predefined roles. This falls under Identity and User Management.
SAP Cloud Transport Management can be used for your basic landscape and transport scenarios in Integration Suite. Besides a file-based manual approach, you can transport your content across the landscape in a more structured way using Cloud Transport Management.
Important: If you want to leverage Cloud Transport Management in combination with Cloud ALM, the Cloud Transport Management service should not be set up within the same account as Cloud ALM. Follow the Guideline: Setup and Administration for SAP Cloud ALM.
SAP Cloud ALM helps you to implement and operate intelligent cloud and hybrid business solutions. With the Integration and Exception Monitoring for the Cloud Integration part of Integration Suite, you can already cover a comprehensive monitoring concept for your hybrid integration landscape with minimal effort. Since Cloud ALM is basically free for customers, it should be one of your key considerations.
CI/CD concept for Integration Suite.
To set up a proper CI/CD pipeline for automated transports, Integration Suite provides Management APIs, which can be leveraged in third-party solutions.
Additionally, our SAP partners offer dedicated automation tools specifically designed for Integration Suite. Check out the SAP Store to get the latest information and products, including those provided by our partners.
Besides partner solutions, there are also some open-source approaches. The most recent one is the CICD Actions for SAP Integration Suite. – an open‑source solution built on GitHub Actions that automates deployment processes for the SAP Integration Suite.
Parallel development of integration flows as part of a CI/CD concept - How do we handle this?
From a general approach, a single integration flow should be handled by one developer. A valid development approach, e.g. for multi-country roll-out and parallel development, is covered under: Integration Flow Extension – Concepts.
The Extension concept enables flexible enhancement of standard integration flows by embedding defined extension points (Customer Exits) via the ProcessDirect adapter, with activation and control managed through external parameters – all without modifying the main flow. This concept is actively used by multiple large enterprise customers and has consistently proven its practical value in productive, including highly regulated, environments.
Additionally, there are many other solution approaches available, such as partner solutions (see SAP Store ) and design approaches. An individual cross-check with your implementation partner is recommended to identify the best concept for your environment.
We want to use AI features?
Check out SAP Discover Center for Integration Suite and 2903776 - SAP Integration Suite – Service Plans and Upgrade Paths which outlines the different AI features included in each plan. As well as the Blog Post dedicated to Enhanced Edition: Introducing SAP Integration Suite, enhanced edition
- the Premium Service Plan is subscription‑based and includes 4 tenants.
- The Enhanced Edition has been generally released and is available via BTPEA/CPEA for customers using that model — and it is calculated per single tenant (an interesting approach to leverage AI for development or use Advanced Event Mesh in Production).
---
We’d love to hear your thoughts and experiences with SAP Integration Suite. What challenges are you facing? How can we help you unlock the full potential of your IT ecosystem? Feel free to reach out to us via SAP Integration Services.
#Modernize #Integrate #Innovate – SAP Integration Modernization TEAM
Bluesky
