Positioning Edge Integration Cell

Objective

After completing this lesson, you will be able to explain the positioning of Edge Integration Cell and identify its supported integration artifacts and runtime-specific adapters.

Introduction

Lesson 2.1 established the requirements that drive organizations toward hybrid integration - data sovereignty, ground-to-ground scenarios, PI/PO migration, and network constraints. This lesson answers the next practitioner question: what exactly is Edge Integration Cell, where does it sit within SAP Integration Suite, and what can it do?

Understanding the positioning of Edge Integration Cell - what it is, what it is not, and how it relates to the other runtime options in SAP Integration Suite - is essential groundwork before exploring the architecture in depth. This lesson also introduces the adapters that are exclusive to EIC, which are a key differentiator for private-network integration scenarios.

What Is Edge Integration Cell?

In Unit, 1 Lesson 4, you encountered Edge Integration Cell as one of three deployment options in SAP Integration Suite - alongside the Cloud Integration Runtime and Integration Cell. You learned the key principle: design always happens in the cloud; execution can happen anywhere. This lesson now unpacks exactly what EIC is, how it is positioned, and what it can do.

The official SAP definition:

"Edge Integration Cell is an optional hybrid integration runtime offered as part of SAP Integration Suite, which enables you to manage APIs and run integration scenarios within your private landscape."

Every word in this definition carries meaning:

"Optional" - EIC is not mandatory. For the majority of integration scenarios, the Cloud Integration Runtime is the appropriate choice. EIC is introduced when specific requirements demand local execution.

"Hybrid integration runtime" - EIC combines cloud-based design and management with private-network execution. It is not a purely on-premise product; it is a runtime within a cloud-managed platform.

"Part of SAP Integration Suite" - EIC is not a separate product or add-on. It is a runtime option within SAP Integration Suite, available to customers on Standard Edition, Enhanced Edition, CPEA, and PAYG licensing. (It is not available with the Starter Edition.)

"Manage APIs and run integration scenarios" - EIC supports both Integration Flows (iFlows) and API proxies. Both artifact types can run locally within the private landscape.

"Private landscape" - EIC can be deployed on-premise in a customer data center or on a customer-managed cloud environment. The defining characteristic is that the infrastructure is within the customer's organizational network boundary.

What Edge Integration Cell Is NOT

Clarifying what EIC is not prevents common misconceptions:

Common MisconceptionReality
EIC is a standalone product you purchase separatelyEIC is a runtime option within SAP Integration Suite
EIC has its own design environmentDesign always happens in the SAP Integration Suite Cockpit (cloud-based)
EIC has separate user managementUser management remains in SAP BTP - no separate identity store
EIC can operate permanently without connectionEIC is a hybrid runtime - requires connection for deployments, credential rotation, access to message processing logs; tolerates temporary connectivity loss (offline mode supports business continuity for up to 4 hours) but is not designed for permanent offline operation
EIC replaces SAP Integration SuiteEIC is part of SAP Integration Suite, not a replacement

Note

As introduced in Unit 1, Lesson 4, SAP Integration Suite offers three runtime options: Cloud Integration Runtime, Integration Cell, and Edge Integration Cell. Integration Cell and Edge Integration Cell share a name prefix but are fundamentally different. Integration Cell is a fully SAP-managed, cloud-native runtime designed for API-centric scenarios. Edge Integration Cell is a customer-managed runtime in private infrastructure supporting both Integration Flows and API proxies. This lesson focuses on EIC's unique capabilities and when it is the right choice.

Same Integration Concepts - Different Execution Location

One of the most practically important aspects of Edge Integration Cell is this: developers work with the same tools, the same objects, and the same design experience as for any other SAP Integration Suite runtime.

The integration vocabulary introduced in Unit 1, Lesson 3, such as Integration Packages, Integration Flows, Adapters, Messages, Mappings, Routing, and Content Modifiers - applies fully in EIC. The SAP Integration Suite Cockpit is the single design environment for all runtime targets.

This means:

  • An iFlow designed for the Cloud Integration Runtime can, in most cases, be deployed to an EIC instance without redesign (for current compatibility details, refer to SAP Note 3391207)
  • Integration developers do not need to learn a new tool or a new design language
  • The only change from the developer's perspective is the deployment target selection - which runtime location receives the artifact

Important nuance: While design-time concepts and artifact types are the same, not all features and adapters available in the Cloud Integration Runtime are supported in EIC. The EIC runtime scope evolves continuously. SAP Note 3391207 is the authoritative and continuously updated reference for the EIC runtime scope and restrictions. Consult this note when planning EIC scenarios.

Supported Artifacts in Edge Integration Cell

SAP Integration Suite supports a broader range of artifact types and capabilities (as introduced in Unit 1). The following two are the artifact types that can be deployed to and executed on an EIC runtime:

1. Integration Flows (iFlows)

Integration Flows - the central artifact type you defined in Unit 1, Lesson 3 - are the primary artifact for message-based integration scenarios in EIC. The key difference is where they execute: in EIC, iFlows run locally within the customer's private infrastructure. This enables sender and receiver systems to exchange data without passing through the internet. Only operational metadata - such as deployment status and Message Processing Log entries - is synchronized with the cloud control plane; the message payload itself is processed and stored locally.

Note

If trace-level logging is enabled, message content may be included in log records accessible from the cloud. Organizations with strict data residency requirements should review their logging configuration accordingly.

2. API Proxies

API proxies are artifacts managed by the API Management capability of SAP Integration Suite. They act as a controlled gateway layer in front of a backend API - applying security policies, rate limiting, transformation, and governance rules to API traffic. With EIC, API proxies can run locally within the private infrastructure. This means API governance capabilities - such as security policies, traffic management, and access control - can be applied to APIs that reside within a private network, without routing API traffic through the cloud. Note that not all policies available in the Cloud Integration Runtime are supported identically in EIC; refer to SAP Note 3391207 for current policy availability.

Scenario relevance for Global Manufacturing AG: The primary artifacts for the S/4HANA-to-QMS integration are Integration Flows. The company may also consider deploying an API proxy in EIC to govern access to the QMS REST API from within the private network - applying authentication and access control policies locally.

Commonly Supported Adapters

EIC supports a broad set of the standard adapters available in SAP Integration Suite. The following adapters are among those commonly used in EIC deployment scenarios:

AdapterProtocol / Purpose
HTTPStandard HTTP/HTTPS-based communication
SOAPSOAP-based web service communication
ODataOData V2 / V4 API-based communication
SFTPSecure file transfer
AS2 / AS4B2B document exchange
MailEmail-based integration
JDBCDatabase connectivity
JMSMessage queue-based integration

Always refer to SAP Note 3391207 for the current and complete adapter compatibility list. The EIC runtime scope is updated continuously, and the list of supported adapters expands with each release.

EIC-Exclusive Adapters

Some adapters are exclusively available in the Edge Integration Cell runtime. They are not available in the Cloud Integration Runtime because they are designed for communication within a private network environment. Additional EIC-exclusive adapters are on SAP's published roadmap - always verify the current scope in SAP Note 3391207

RFC Sender Adapter

The RFC (Remote Function Call) Sender Adapter enables direct RFC communication with ABAP-based SAP systems (such as SAP S/4HANA on-premise or SAP ECC) from the private network.

RFC is SAP's proprietary protocol for calling ABAP function modules and BAPIs directly on a remote SAP system. The RFC Sender Adapter - which receives RFC calls from an on-premise SAP system - is only meaningful within a private network, where the SAP system and the EIC runtime share the same network segment.

When to use it: Scenarios where an on-premise SAP system initiates integration by calling an RFC-based endpoint directly - without requiring a separate Cloud Connector on the inbound path.

Note

The RFC Receiver Adapter - which sends outbound RFC calls to an on-premise SAP system - is available on both Cloud Integration Runtime (via Cloud Connector) and EIC. Only the RFC Sender Adapter (inbound direction) is exclusive to EIC.

NFS File Adapter

The NFS (Network File System) Adapter enables integration flows to access files and directories on network file systems within the private infrastructure.

NFS is a distributed file system protocol used in enterprise on-premise environments to share storage across servers. Because NFS shares are typically accessible only within a private network, this adapter is only available in EIC, where the runtime is inside the same network.

When to use it: Scenarios involving file-based integration with NFS-mounted shared storage - for example, picking up batch files from a shared network drive on a production system.

OFTP2 Adapter

The OFTP2 (ODETTE File Transfer Protocol 2) Adapter enables OFTP2-based file transfer - the standard B2B file exchange protocol in the automotive industry and related logistics sectors.

OFTP2 is used for exchanging EDI messages (order confirmations, delivery notifications, invoices) between automotive manufacturers, tier-1 suppliers, and logistics partners. Because OFTP2 communication can involve dedicated, secured private connections between partner organizations, this adapter is available in EIC for scenarios where the OFTP2 connection endpoint is within the private network.

When to use it: Automotive and logistics B2B scenarios requiring OFTP2-based file transfer with business partners or within a private partner network.

The following table summarizes the three presented adapters and facilitates a direct comparison of their key features:

AdapterUse Case
RFC Sender AdapterDirect RFC calls from on-premise ABAP systems - no separate inbound Cloud Connector required
NFS File AdapterAccess to network file systems within the private infrastructure
OFTP2 AdapterAutomotive and logistics B2B file transfer via OFTP2 protocol

Decision Guide: Is EIC the Right Runtime?

SAP identifies specific use cases for Edge Integration Cell - primarily security and compliance scenarios, and ground-to-ground integration including PI/PO migration. The following questions, based on these use cases, can help structure the runtime selection for a given integration scenario:

Question 1: Data sovereignty - Does this integration flow process data subject to regulatory requirements, contractual obligations, or internal governance policies that mandate processing within a specific geographic or network boundary? → If yes: EIC is designed for this requirement.

Question 2: Ground-to-ground scenario - Are both the source system and the target system within the same private network, and is low latency or data containment a requirement? → If yes: EIC enables local processing without cloud round-trips.

Question 3: Network constraints - Does the network architecture of this environment restrict or prohibit routing integration message traffic through external cloud infrastructure? → If yes: EIC keeps business message traffic within the private network.

Question 4: PI/PO migration - Is this scenario being migrated from SAP PI/PO and must it preserve local execution? → If yes: EIC provides a modern migration target for scenarios requiring local runtime.

If none of the above apply: The Cloud Integration Runtime is the standard choice - it requires no customer-managed infrastructure and no Kubernetes operations overhead.

EIC artifacts are described as "largely compatible" with Cloud Integration Runtime artifacts - but not identical. Adapter support, feature availability, and behavior may differ. Always check SAP Note 3391207 for current compatibility details when planning a deployment.

Determine the appropriate runtime for integration scenarios.

Scenario Check-In: Global Manufacturing AG

With the positioning of EIC established, the picture for Global Manufacturing AG is clear. Its S/4HANA-to-QMS scenario meets three of the four decision criteria: data sovereignty (GDPR and internal policy), ground-to-ground routing (both systems in the Frankfurt data center), and PI/PO migration (retiring its SAP Process Orchestration system). The RFC Sender Adapter - exclusive to EIC - is a candidate for direct RFC-based communication from S/4HANA, eliminating the need for a separate inbound Cloud Connector configuration.

Key Takeaways

  • Edge Integration Cell (EIC) is an optional hybrid runtime of SAP Integration Suite for running integration scenarios and APIs within a private landscape.
  • EIC is not a standalone environment: design, user management, and lifecycle management remain cloud-based, and connectivity to SAP Business AI Platform is required.
  • The development experience remains consistent: the same integration concepts, such as adapters, integration flows, mappings, and routing, apply across EIC and Cloud Integration.
  • EIC supports Integration Flows and API proxies with most common adapters available across both runtimes.
  • Some adapters are EIC-specific: e.g. RFC Sender, NFS File, OFTP2, supporting private-network integration scenarios.
  • SAP Note 3391207 defines the current EIC runtime scope and adapter compatibility and should be consulted when planning an EIC deployment.

Further Resources

SAP Help Portal – Supported Features and Limitations of EIC

https://help.sap.com/docs/integration-suite/sap-integration-suite/supported-features-for-edge-integration-cell

SAP Note 3391207 – SAP Integration Suite - Restrictions for EIC

https://me.sap.com/notes/3391207

SAP Help Portal – Available Adapters in SAP Integration Suite

https://help.sap.com/docs/integration-suite/sap-integration-suite/available-adapters

SAP Community – FAQ on Edge Integration Cell

https://community.sap.com/t5/integration-blog-posts/frequently-asked-questions-faq-on-edge-integration-cell/ba-p/13571636