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.