The Two-Plane Model
Edge Integration Cell is built on a clear architectural split between two planes:
| Plane | Location | Managed By | Purpose |
| Control Plane | SAP Business AI Platform (Cloud) | SAP | Design, deployment orchestration, monitoring, security material management |
| Data Plane | Customer's Kubernetes cluster (Private) | Customer (infrastructure); SAP (EIC software layer) | Message processing - where integration flows actually run |
This separation is the architectural cornerstone of EIC. It allows organizations to leverage the governance capabilities of a cloud platform while keeping actual data processing entirely within their own security perimeter.
Analogy: Think of a large international bank. The bank's headquarters sets the rules, defines procedures, monitors performance, and manages compliance across all branches. Each regional branch serves customers locally, transactions happen on-site, with the money and client data never leaving the branch building. Headquarters has full visibility into what is happening at every branch, but the actual transactions stay local. This is precisely the EIC model: centralized control, local execution. (Note: As with any analogy, this is a simplification. When Trace-level logging is enabled for troubleshooting, message payload data can be transmitted to cloud monitoring, see the Data Separation section below for details.)
Control Plane: Centralized Management
The control plane is the cloud-based side of the EIC architecture. It runs within SAP Business AI Platform and is accessed through the SAP Integration Suite Cockpit. Regardless of whether integration flows will eventually execute in the cloud or locally on an EIC instance, all design and management work happens here.
Key functions of the control plane:
- Integration Flow Design: The SAP Integration Suite Cockpit provides a browser-based environment for creating, configuring, and versioning Integration Flows and API proxies.
- Integration Flow Design: The SAP Integration Suite Cockpit provides a browser-based environment for creating, configuring, and versioning Integration Flows and API proxies.
- Deployment Orchestration: When an integration artifact is ready, deployment instructions are sent from the control plane to the target runtime. The control plane tracks deployed versions and enables controlled updates.
- Monitoring and Observability: Dashboards in the SAP Integration Suite Cockpit display Message Processing Logs, error reports, and performance metrics - for all runtimes, including remote EIC instances. Operations teams do not need separate monitoring tools for cloud and EIC scenarios.
- Security Material Management: Credentials, certificates, and security artifacts are managed centrally in the cloud and distributed securely to the runtimes that need them.
Critical constraint: Under normal operating conditions (log level Info or Error), no business message content passes through the cloud control plane. Only metadata, configuration data, and monitoring information are exchanged between SAP Business AI Platform and the EIC runtime. The actual content of integration messages - production orders, quality inspection records, customer data - stays within the private network. Note: When the Trace log level is enabled for a specific integration flow, payload data may be included in log records accessible from cloud monitoring. This is a documented exception relevant for compliance planning.
Data Plane: Decentralized Processing
The data plane is the customer-managed side of the EIC architecture - the local environment where integration scenarios actually execute. It consists of the EIC runtime components deployed on a Kubernetes cluster within the customer's private infrastructure.
Key characteristics of the data plane:
Local Message Processing: Integration flows and API proxies execute within the private network. Sensitive business data remains within the customer's defined security boundaries.
No Internet Traversal for Business Data: Messages between connected systems flow through the EIC runtime without leaving the corporate network.
Kubernetes Foundation: The EIC runtime is packaged as containerized workloads deployed on Kubernetes. Kubernetes provides container orchestration: scheduling workloads, managing container lifecycles, handling restarts. Unit 3 covers Kubernetes in depth.
Customer-Managed Infrastructure: The customer provisions, maintains, and operates the underlying Kubernetes cluster. SAP manages the EIC application layer.
Architecture Components Reference
The following table describes the key components in the EIC architecture:
| Component | Location | Role |
| SAP Integration Suite | SAP Business AI Platform (Cloud) | Design environment, deployment control, monitoring dashboards, security material management. The single management interface for all runtimes. |
| Kubernetes Cluster | Customer private infrastructure | The container orchestration platform on which EIC runs. Provisioned and operated by the customer. Supported platforms listed in Lesson 2.6. |
| Edge Lifecycle Management (ELM) | Customer private (ELM Bridge on cluster) + SAP Business AI Platform | Installs, updates, and monitors the EIC runtime. Manages the connection between the Kubernetes cluster and SAP Integration Suite. Primary tool for EIC infrastructure administration. |
| Cloud Connector | Customer private (embedded in ELM by default) | Establishes the secure outbound tunnel from the private infrastructure to SAP Business AI Platform. By default, an embedded Cloud Connector is deployed and managed through Edge Lifecycle Management as part of the EIC setup process. Customers who prefer to use an existing, external Cloud Connector installation can configure EIC to use that instance instead. |
| PostgreSQL or SAP HANA | Customer private | Relational database used by the EIC runtime for Integration Flow state persistence, message store, and Message Processing Logs (MPLs). |
| Redis or Valkey | Customer private | In-memory data store used for messaging and caching within the EIC runtime. |
Note
Cloud Connector: The communication between the EIC runtime and SAP Business AI Platform is established through the Cloud Connector. The connection is always initiated from the private side (outbound from the customer's network). No inbound firewall ports to the customer's infrastructure are required for EIC's operational communication. Lesson 2.4 covers the communication model in detail.