Enabling Communication Between Cloud and Private Runtime

Objective

After completing this lesson, you will be able to explain how SAP Integration Suite securely communicates and synchronizes data with the Edge Integration Cell runtime.

Introduction

Lesson 2.3 described the EIC architecture at the component level - the control plane, the data plane, and the key components in each. This lesson zooms in on the mechanics: how do the cloud and the private runtime actually communicate?

Understanding the communication model between SAP Business AI Platform and the EIC runtime answers questions that matter for security reviews, network planning, and operational resilience:

  • How does a deployment command from the cloud reach the private Kubernetes cluster?
  • What happens when a developer clicks "Deploy" in the SAP Integration Suite Cockpit?
  • Does the communication require opening inbound firewall ports in the customer's network?
  • What happens if the internet connection is temporarily interrupted?

From Design to Execution: The Deployment Lifecycle

The following six-step walkthrough is this course's analytical framework for the artifact deployment lifecycle - it is not a numbered SAP framework. Each step reflects documented EIC behavior. When a developer deploys an integration artifact to an EIC instance, the following sequence occurs:

Step 1 - Design (Control Plane)

An integration developer opens the SAP Integration Suite Cockpit in their browser. They create or modify an Integration Flow, configure adapters, define message mappings, and set processing logic - exactly as they would for any integration scenario. All work at this stage is within the cloud control plane. No EIC communication occurs yet.

Step 2 - Select Runtime Location

When the iFlow is ready for deployment, the developer selects the target runtime. In addition to the Cloud Integration Runtime, the deploy dialog presents the available EIC instances registered to the tenant. The developer selects the appropriate EIC instance - for example, "FRA-EIC-PROD."

Step 3 - Deployment Command Transmitted

The SAP Integration Suite Cockpit transmits a deployment instruction to the target EIC instance via the secure outbound communication channel. The compiled integration artifact and its configuration are included in or referenced by this instruction.

Step 4 - Local Instantiation on the Kubernetes Cluster

The EIC runtime receives the deployment instruction via its Cloud Connector-based communication channel. The EIC runtime orchestrates the local Kubernetes deployment - creating or updating the containerized workloads that implement the Integration Flow. Kubernetes schedules these workloads on available cluster nodes. The Integration Flow adapters initialize, connect to their configured endpoints on the private network, and begin listening for messages.

Step 5 - Execution in the Private Network

The Integration Flow is running locally. Source systems send messages to the flow's integration endpoint - an address on the customer's private network. The flow processes messages entirely within the Kubernetes cluster: receiving, transforming, routing, and delivering. Business message content does not leave the data plane.

Step 6 - Monitoring Feedback to the Cloud

As messages are processed, the EIC runtime generates Message Processing Logs. These are stored locally in the EIC database (PostgreSQL or SAP HANA). The Message Monitor in the SAP Integration Suite Cockpit queries the MPLs via an API request through the Cloud Connector and displays them on demand. No data is transmitted to or updated in SAP Business AI Platform.

Once deployed, the Integration Flow continues to operate. Subsequent lifecycle management actions - configuration updates, version upgrades, error handling - follow the same pattern: instruction from the control plane, local execution, telemetry transmitted back.

The Cloud Connector: The Secure Communication Bridge

The communication between the EIC runtime and SAP Business AI Platform is established through the Cloud Connector - a well-established SAP component that creates a secure, outbound-initiated tunnel between a private infrastructure and SAP Business AI Platform.

The Cloud Connector: The Secure Communication Bridge

Important terminology: The communication component is the Cloud Connector.

By default: Edge Integration Cell includes an embedded Cloud Connector that is deployed and managed through Edge Lifecycle Management as part of the EIC setup process. Most organizations deploying EIC for the first time will use this embedded instance.

Existing Cloud Connector: Customers who already have a Cloud Connector installation in their network (for example, for SAP S/4HANA connectivity to SAP Business AI Platform) can configure EIC to use that existing instance instead of the embedded one.

Key characteristics of the Cloud Connector in EIC context:

  • Outbound-only connection: The connection is always initiated from the private infrastructure, going outward to SAP Business AI Platform. SAP's cloud infrastructure does not initiate connections into the customer's private network.
  • No inbound firewall ports required: Because all communication is initiated from the private side, there is no need to open inbound firewall rules to permit external access to the Kubernetes cluster for EIC's operational communication.
  • Encrypted in transit: All communication between the Cloud Connector and SAP Business AI Platform uses TLS encryption.
  • Corporate proxy support: The outbound connection can be routed through a corporate HTTP forward proxy - the standard security architecture in many enterprises.
  • Note

    Corporate proxy support requires that the proxy passes the TLS connection through without terminating it. TLS-terminating proxies - such as those performing deep packet inspection or SSL/TLS inspection - are not supported by the Cloud Connector and will cause the tunnel to SAP Business AI Platform to fail. If your organization operates a TLS-terminating proxy, consult your network team to configure a bypass rule for the Cloud Connector traffic. See also: SAP Cloud Connector FAQ and SAP Note 3669974.

Synchronization and Resilience

Runtime Synchronization After Deployment

Beyond the initial deployment, the EIC runtime and the cloud control plane maintain ongoing synchronization:

  • Artifact synchronization: When integration artifacts are updated or new versions are deployed, the updated artifact is transmitted to the EIC runtime via the secure channel. The EIC runtime applies the update locally.
  • Security material synchronization: Security artifacts (certificate references, credential references) managed in SAP Integration Suite are distributed to the EIC runtime. The EIC runtime caches these locally for authentication and encryption operations. This local caching enables continued operation during temporary cloud connection interruptions.
  • MPL synchronization: Message Processing Logs generated locally are transmitted to the cloud for display in the Message Monitor. MPLs contain operational metadata only - not business message content.

Connection Resilience

EIC is designed to handle temporary connection interruptions without interrupting message processing. Authentication and authorization are handled locally, without a real-time dependency on SAP Business AI Platform. If the connection to the cloud is temporarily lost, already deployed integration scenarios can continue to process messages for a limited duration - currently up to approximately 4 hours. SAP has published a roadmap item to extend offline operation to 48 hours; check the SAP EIC FAQ for the latest supported duration. During this period, local security material is used for authentication.

This resilience means that a transient internet connectivity issue does not immediately stop integration processing.

However, EIC cannot be operated permanently without a cloud connection. It is a hybrid runtime, not an offline platform. The following actions require an active connection to SAP Business AI Platform:

  • Deploying new integration artifacts or updating existing ones
  • Accessing Message Processing Logs via the SAP Integration Suite Cockpit
  • Rotating credentials and refreshing security material
  • Applying software updates via Edge Lifecycle Management
  • Registering new EIC instances

Key distinction: EIC provides resilience against temporary interruptions - it is not designed for air-gapped or permanently disconnected environments. Organizations with environments that have no outbound internet connectivity should evaluate whether EIC's connection requirements can be met in their network architecture.

Software Updates

EIC software updates are delivered through SAP Repository-Based Shipment Channel (RBSC) - SAP's standard channel for delivering software packages to customer environments. Updates are applied by the customer's administrator using Edge Lifecycle Management (ELM).

This means:

  • SAP controls when new EIC versions are made available
  • The customer controls when and how updates are applied to their EIC instance
  • ELM provides the tooling and guided process for executing updates
  • Customers are responsible for keeping their EIC instance within the supported version range. EIC updates ship every 4 weeks at cloud speed, consistent with SAP Integration Suite's release cadence. SAP supports only the current version (n) and the immediately preceding version (n-1). Falling more than one version behind means the instance is outside the supported range

Scenario Check-In: Global Manufacturing AG

The Cloud Connector (embedded in ELM) maintains an outbound HTTPS connection from the Frankfurt Kubernetes cluster to SAP Business AI Platform. When the integration team deploys an updated version of the S/4HANA-to-QMS iFlow, the deployment instruction travels from SAP Business AI Platform over this established channel to Frankfurt, where the updated flow is instantiated locally. Production order messages that flow between S/4HANA and the QMS travel exclusively over Global Manufacturing AG's private Frankfurt data center network - never reaching the outbound channel to SAP Business AI Platform. Operations engineers can monitor message processing in near real time in the SAP Integration Suite Cockpit while the underlying production and quality data remains entirely within Germany.

Key Takeaways

The deployment lifecycle transfers integration artifacts from the cloud control plane to the private EIC runtime in six steps - from design through local execution to monitoring feedback. The Cloud Connector establishes the secure tunnel from the private side, requiring no inbound firewall ports. Synchronization between cloud and runtime covers management and operational data only - business messages never leave the customer's infrastructure. In the event of a temporary connection loss, already deployed scenarios can continue processing for up to approximately 4 hours. Deployment, monitoring, and credential management require an active cloud connection. Software updates are delivered via RBSC and applied through Edge Lifecycle Management. EIC is updated every 4 weeks, and customers must stay within one version of the latest release.