BTP Integration Suite Edge Integration Cell On Azure
BTP Integration Suite Edge Integration Cell On Azure
Edge Integration Cell, part of the SAP Integration Suite, brings a powerful hybrid integration runtime that
bridges the gap between the cloud and your private landscape. It provides the flexibility to seamlessly
manage APIs and run integration scenarios within a controlled environment, combining the best of both
worlds.
With its hybrid deployment model, Edge Integration Cell makes it easy to design and monitor integration
content in the cloud, while still allowing it to be securely deployed and run in a customer-managed private
environment.
Security or compliance use cases: Sensitive data stays safely within an enterprise's firewall,
following strict rules to keep it within a private environment.
Migration path for SAP Process Integration customers: Edge Integration Cell helps customers
design and monitor integration content in the cloud while keeping deployment and execution fully
within their private environments.
This blog offers a step-by-step guide to deploying SAP Edge Integration Cell on Azure, with two setup
options: a quick start for trying out the simplest setup, and a high-availability configuration for production.
Whether you're looking for a quick test or a scalable, production-ready deployment, the guide makes it
easy to configure SAP BTP and Azure resources. Once the setup is complete, the SAP Integration Suite can
deploy integration flows securely to the on-premise setup using the Edge Integration Cell.
Architecture
Both the quick start setup and the high availability (HA) architecture for deploying SAP Edge Integration
Cell (EIC) on Azure utilize Azure Kubernetes Service (AKS). The quick start setup uses the default VNet in
the region, with all storage handled by AKS and smaller compute and storage resources for simple and
efficient deployment. In contrast, the HA architecture is spread across at least three availability zones for
redundancy, with dynamic storage managed by a combination of (AKS), along with additional services like
Azure Relational Database Service (RDS) for persistence and Redis for caching.
On the SAP BTP side, the Edge Integration Cell must be activated within the SAP Integration Suite. Once
the EIC is configured and successfully deployed on the Azure AKS cluster, integration flows can be
designed and seamlessly deployed to the new EIC runtime, combining the powerful integration capabilities
of SAP Integration Suite with the customer-managed resources on Azure Cloud.
Non-HA Setup
HA Setup
The detailed setup instructions are in the following repository – Deploy Edge Integration Cell on Azure.
Disclaimer: The suggested steps and instructions will be treated as a starter guide. For a production-level
final setup please use caution and consider security and scalability standards.
After completing the setup, start designing integration flows on the SAP Integration Suite and choose the
created Edge Node as the runtime environment. This allows the deployment of integration flows to the on-
premise environment, harnessing the full capabilities of the SAP Integration Suite within a secure on-
premise setting.
Additional resources
Here are some helpful resources related to the SAP Edge Integration cell:
Deploy Edge Integration Cell on Microsoft Azure using Azure Kubernetes Service
Conclusion
I hope this blog has guided you in setting up SAP Edge Integration Cell on Azure, simplifying the
connection between SAP on-premise solutions, and enabling seamless integration design and monitoring in
the cloud. By following these steps, you can create secure, high-performing business applications that
combine innovation with robust control in a secure environment.
I want to express my gratitude to our SAP team members Adarsh Hegde, Alex Bishka, and Sivakumar N for
their valuable contributions, guidance, and support. If you have any questions, feel free to
contact [email protected].
Labels:
Technology Updates
1 Comment
RamMohanLanka
Newcomer
Friday
0 Kudos
The blog is certainly much appreciated and the use cases are well described. But I have a query related to
logs and traces and not sure where they will be stored in case of any error messages. Does it store these
logs at On premises or at parent cloud location. Appreciate your response here.