Current Scope, Limitations, and Roadmap

Objective

After completing this lesson, you will be able to describe EIC monitoring through Message Processing Logs and the Operations Cockpit, and explain its integration with enterprise monitoring platforms.

Introduction

Lesson 4.1 established how to monitor integration flows and diagnose failures using the SAP Integration Suite Cockpit. That operational knowledge is only useful if you know what EIC can actually do - and what it currently cannot.

In this lesson, you will describe EIC's functional scope today, identify key known limitations, explain why SAP Note 3391207 is the essential planning reference, and evaluate when EIC is the right runtime choice. You will also understand the product direction so you can plan EIC adoptions with a realistic view of where gaps currently exist and where they are closing.

This lesson contributes to the overall goal: giving you the factual knowledge to plan and justify EIC deployments with confidence - and to set realistic expectations with business stakeholders.

EIC's Current Scope - and How to Stay Current

EIC Is Not a Full Replacement for Cloud Integration

A common misconception: Edge Integration Cell is a feature-complete, on-premise replacement for the SAP Integration Suite Cloud Integration Runtime. This is not accurate - and planning under this assumption leads to failed migrations and unexpected capability gaps.

The correct framing: EIC is an additional runtime option within SAP Integration Suite. It shares the same design-time environment and core integration concepts, but does not have complete feature parity with the cloud runtime. The functional scope continues to expand, but gaps exist at any given point in time.

If local execution is not required, the standard Cloud Integration Runtime is almost always the better choice: fully managed by SAP, no customer-managed infrastructure, no feature gaps.

Supported Artifacts and Core Functions

1. Integration Flows (iFlows)

Integration Flows execute locally within the EIC Worker. The following core iFlow capabilities are supported in EIC:

  • All basic iFlow processing steps: routing, mapping, transformation, content modifier, filter, scripting (Groovy, JavaScript)
  • Local data storage: Data Store, Variables
  • Message Processing Logs (MPLs) - persisted locally, viewable in the cloud Cockpit
  • Local messaging service (JMS-based) for asynchronous, decoupled iFlow processing
  • Key management: keystores, credential store (with documented resource limits - see below)
  • Most common SAP adapters (see adapter table below)

2. API Proxies (from API Management)

API proxies designed in the API Management capability can be deployed to EIC, enabling managed, policy-enforced exposure of backend APIs from within the private landscape, API policies (rate limiting, authentication, transformation), and API Analytics.

Supported Adapters and EIC-Exclusive Adapters

Adapter support is the most operationally relevant part of the EIC runtime scope. Commonly used adapters supported in EIC:

AdapterDirectionNotes
HTTP/HTTPSSender and ReceiverCore adapter for REST-based communication
SOAPSender and ReceiverWeb services / WSDL-based integration
OData (V2 and V4)Sender and ReceiverREST/JSON access to OData APIs
SFTPSender and ReceiverSecure file transfer
FTPSender and ReceiverFile-based integration (use SFTP where possible)
Mail (IMAP, SMTP, POP3)Sender and ReceiverEmail-based integration
IDocSender and ReceiverSAP IDoc communication
JDBCReceiverDatabase connectivity (PostgreSQL, Microsoft SQL Server, MySQL, MariaDB, and others)
ProcessDirectSender and ReceiverInternal iFlow-to-iFlow communication within EIC

EIC - Exclusive Adapters (Not Available in the Cloud Runtime)

A small but significant set of adapters are only available in EIC. They require direct network-level access to private infrastructure - something not achievable from a cloud runtime:

AdapterPurposeWhy EIC-exclusive
RFC Sender AdapterEnables ABAP systems in the private network to send RFC calls directly to EIC.RFC requires direct network-level access from the ABAP system to the EIC cluster - not possible via public internet. Note: the RFC Receiver adapter (EIC calling ABAP via RFC) is available in both runtimes.
NFS AdapterEnables access to Network File System (NFS) shares within the private infrastructure.NFS shares are private network resources not reachable from the cloud.
OFTP2 AdapterOFTP2-based file transfer, commonly used in automotive and logistics B2B scenarios.OFTP2 requires direct network connectivity in private EDI environments.

These EIC - exclusive adapters represent an important category: scenarios involving private-network communication protocols inherently inaccessible from a cloud-based runtime. They are among the strongest technical justifications for an EIC deployment.

Diagram comparing adapter availability across Cloud Integration Runtime, both runtimes, and Edge Integration Cell (EIC) only.

Resource Limits and Operational Boundaries

SAP documents explicit resource limits for EIC. Must be verified when sizing your deployment:

ResourceLimit
Integration content (deployed artifacts)500 MB maximum
X.509 keystoresMaximum 20
Runtimes per credential or keystoreMaximum 20
JDBC data sourcesMaximum 500 per edge runtime
Credentials per runtimeMaximum 500 (combined across credential types)

Known Limitations and SAP Note 3391207

Several Cloud Integration capabilities are currently not available or constrained in EIC:

Limitation areaDetail
B2B scenariosNot all B2B scenario types supported; Integration Advisor-based content may have restrictions
MPL archivingArchiving of Message Processing Logs to external storage is not currently supported
Partner DirectoryThe Partner Directory (for B2B partner configuration) is not available in EIC
Inspect featureThe Inspect simulation and debug environment is not available in EIC
Certain OAuth flowsSome OAuth 2.0 flows are not supported as they require cloud-based callback mechanisms
Number rangesNumber range artifacts are not supported in EIC
Some adapter featuresIndividual adapter options may be unavailable even if the adapter itself is supported

Note

This list is not exhaustive and is updated with every EIC release. The single authoritative reference for the current, complete scope and limitations is: SAP Note 3391207 - Edge Integration Cell: Runtime Scope and Restrictions. -This note documents the full EIC runtime scope in tabular form, organized by category: adapter scope, iFlow steps, API Management policies, and known restrictions. It is updated with every EIC release. Always check the current version of SAP Note 3391207 before planning any EIC deployment or migration. Never rely on a copied or cached summary - the scope changes.

When to Use EIC - and Where It's Headed

EIC vs. Cloud Integration Runtime: A Decision Guide

Knowing EIC's current scope and limitations leads directly to the planning question every architect faces: when is EIC the right choice - and when is the standard Cloud Integration Runtime the better fit?

Use EIC when:

  • The data being processed must not leave your private network (data residency or compliance requirement).
  • Both source and target systems are within the same private network (ground-to-ground scenario).
  • You are migrating a ground-to-ground scenario from SAP Process Orchestration and local execution must be preserved.
  • The integration requires an EIC-exclusive adapter (RFC Sender, NFS, OFTP2).
  • Network constraints prevent cloud-based message routing.

Use the standard Cloud Integration Runtime when:

  • The scenario involves cloud-to-cloud or cloud-to-on-premise integration where routing through SAP's cloud is acceptable.
  • You want to minimize infrastructure management responsibility - SAP manages the cloud runtime.
  • The scenario requires a capability not yet available in EIC.
  • You do not have organizational capacity to operate and maintain a Kubernetes cluster.

Key principle: EIC is a specialized runtime for scenarios with genuine local-execution requirements. For everything else, the cloud runtime is simpler to operate, fully managed by SAP, and feature-complete.

Flowchart illustrating how local-execution requirements determine whether to use Edge Integration Cell or Cloud Integration Runtime.

Migration from SAP Process Orchestration (SAP PI/PO)

One of the key use cases for EIC is as the target runtime for organizations migrating from SAP Process Orchestration (SAP PI/PO). For ground-to-ground scenarios that cannot move to the cloud, EIC provides a modern, cloud-native migration path that preserves local execution: integration design moves to the cloud-based SAP Integration Suite Cockpit, but message processing remains local on EIC.

Note

The integration flow model in EIC is not fully compatible with the Cloud Integration model in all migration scenarios. Always consult the SAP Integration Suite migration tooling (PI/PO to Cloud Integration) and the migration restrictions documentation for EIC before planning.

Product Direction: Where EIC Is Headed

SAP is actively investing in EIC. The public product direction is clear: expand feature parity with the Cloud Integration Runtime, expand adapter coverage, and expand supported Kubernetes platforms.

Adapter Expansion

SAP has announced significant adapter expansion for EIC, including connectors for Amazon services, Box, Google Workspace, Microsoft Azure Service Bus and Microsoft 365 services, MongoDB, Salesforce Service Cloud, Twilio, and Zendesk.

Kubernetes Platform Expansion

Support for Red Hat OpenShift (OCP versions 4.19–4.22, including ROSA and ARO) extends EIC deployment options for organizations that standardize on OpenShift. Supported version ranges evolve with each release - always check SAP Note 3247839 for the current matrix.

Resilience Improvements

In Q4 2025, SAP added support for basic HTTP authentication using a client ID and a client secret during temporary connectivity loss, improving EIC's ability to handle brief disconnections gracefully.

Note

Roadmap information is not a guarantee of delivery date or scope. Always verify current capabilities against SAP Note 3391207 rather than relying on roadmap announcements.

Scenario Check-in: Global Manufacturing AG

With EIC's current scope and limitations understood, Global Manufacturing AG's assessment is clear. The S/4HANA ↔ QMS scenario meets the core criteria for EIC: quality inspection data must remain within the German data center (data residency), both systems are on-premise in the same Frankfurt location (ground-to-ground), and the required HTTP and OData adapters are fully supported. The RFC Sender Adapter - exclusive to EIC - is a candidate for direct RFC-based S/4HANA communication that has no equivalent in the Cloud Integration Runtime. A check against SAP Note 3391207 confirms that no planned scenario feature relies on a currently unsupported EIC capability. The decision: proceed with EIC deployment for the S/4HANA ↔ QMS integration.

Key Takeaways

In this lesson, you learned that EIC has a defined but expanding functional scope - it supports Integration Flows, API proxies, and a broad adapter set, but is not a full replacement for the Cloud Integration Runtime, and gaps must always be validated against SAP Note 3391207, the single authoritative reference that travels with every EIC release. Three adapters - RFC Sender, NFS, and OFTP2 - are exclusive to EIC and cover private-network communication protocols that are architecturally impossible in the cloud runtime. EIC is the right choice when local execution is genuinely required: data residency, ground-to-ground scenarios, EIC-exclusive adapter needs, and SAP PI/PO migration of on-premise scenarios are the strongest justifications; for everything else, the Cloud Integration Runtime is simpler, fully managed, and feature-complete. SAP is actively investing in EIC - adapter coverage and platform support are expanding - but the roadmap is not a planning substitute: always check the current version of SAP Note 3391207 before committing to a deployment.

The Unit 4 Closing ties together all four units and returns to Global Manufacturing AG one final time - showing how everything covered in this course applies to a real deployment decision.

What you learnedWhy it matters
EIC is an additional runtime option within SAP Integration Suite - not a standalone product.All design, monitoring, and lifecycle management always go through the SAP Integration Suite Cockpit, regardless of runtime.
EIC does not have complete feature parity with the Cloud Integration Runtime.Deployment decisions must be based on verified scope. Gaps can block migrations or cause rework.
SAP Note 3391207 is the authoritative, continuously updated scope reference.It is the only reliable source - always check the current version before planning, not a summary from a previous project.
RFC Sender, NFS, and OFTP2 are EIC-exclusive adapters.These adapters identify scenarios where EIC is technically required - they are the strongest technical justification for an EIC deployment.
Use EIC only when local execution is genuinely required.For cloud-to-cloud or cloud-to-on-premise without data residency constraints, the Cloud Integration Runtime is simpler, fully managed, and feature-complete.
Migration from SAP PI/PO to EIC requires compatibility assessment first.Not all PI/PO scenarios migrate without modification. Consult migration tooling before planning.
The EIC product roadmap shows continued SAP investment.The gaps are narrowing - but roadmap information is not a delivery guarantee. Verify against SAP Note 3391207.