Working With EIC in SAP Integration Suite Cockpit

Objective

After completing this lesson, you will be able to identify the SAP Integration Suite Cockpit areas used for EIC and explain the role of Edge Lifecycle Management.

Introduction

Lesson 2.4 explained the mechanics of communication between the cloud and the private runtime. This lesson brings the focus to the practical user experience: where in the SAP Integration Suite Cockpit does EIC appear, and what do different roles - integration developer, administrator, edge node administrator - actually do?

One of the most reassuring aspects of Edge Integration Cell for integration developers is this: for the integration developer, EIC changes primarily the deploy step. Integration Flows are designed in the same web-based editor. Adapters are configured using the same palette. The familiar rhythm of design, configure, deploy, and monitor remains intact. Instead of a single cloud runtime target, the developer selects from a list of available runtime locations - one of which may be an EIC instance.

Working With EIC in SAP Integration Suite Cockpit

Settings → Runtime:

EIC activation begins in the Settings area of the SAP Integration Suite Cockpit, under the Runtime section. This is a one-time setup step performed by the tenant administrator.

Settings → Runtime — EIC Activation

During activation, the administrator configures the connection to the Edge Integration Cell service in the SAP Business AI Platform subaccount. Once activation is complete, the SAP Integration Suite Cockpit displays the URL for the Edge Lifecycle Management (ELM) interface - the dedicated administration environment for EIC infrastructure.

Note

For Administrators: The activation step in Settings → Runtime establishes the trust relationship between the SAP Business AI Platform cloud control plane and the EIC runtime infrastructure. It does not deploy anything to the Kubernetes cluster - that step is handled through ELM. For integration developers, this step occurs before they begin working with EIC. By the time a developer selects an EIC instance as a deployment target, the activation has already been completed by an administrator.

Design → Integrations & APIs: Identical to Cloud Runtime:

iFlows are designed in the same editor as for the Cloud Integration Runtime. The development approach remains the same - however, EIC does not support all adapters and functions of the cloud runtime (see Runtime Scope, SAP Note 3391207).

Design → Integrations & APIs → Integration Packages → Artifacts → Integration Flows

The same graphical iFlow editor, the same adapter palette, the same mapping editor, the same routing configuration - all unchanged. EIC does not require a separate design environment or a different design approach. An iFlow designed for the Cloud Integration Runtime can, in most cases, be deployed to an EIC instance without modification.

Note

Not all adapters available in the Cloud Integration Runtime are supported in EIC. When designing an iFlow intended for EIC deployment, verify that all adapters used are supported by the EIC runtime. Refer to SAP Note 3391207 for the current adapter compatibility matrix.

API proxies for EIC are designed in the same way as for any other API Management scenario - within the API Management capability of SAP Integration Suite.

Deploy → Select Runtime Location:

The most visible change for a developer working with EIC occurs at deployment time. When deploying an integration artifact, the Cockpit presents a Select Runtime Location step.

From this selection, the developer chooses the target runtime:

  • Cloud Integration Runtime - the standard SAP-managed cloud runtime
  • EIC instances - one or more EIC instances registered to the tenant, identified by the name assigned during ELM registration (for example, "FRA-EIC-PROD" or "PLANT-SINGAPORE-EIC")

This selection determines where the integration artifact will execute. The selection is made per artifact - different artifacts within the same tenant can run on different runtimes. For example:

  • The S/4HANA-to-QMS iFlow deploys to "FRA-EIC-PROD" (EIC, Frankfurt) - because of data residency requirements
  • The supplier catalog synchronization iFlow deploys to the Cloud Integration Runtime - because there are no data residency constraints

Practical consideration: The available runtime locations in the deploy dropdown reflect only those EIC instances that have been successfully registered and are in a healthy state. If an expected EIC instance does not appear, the administrator should verify its registration status in ELM.

Monitor → Monitor Message Processing:

Message Processing Logs are stored locally in the EIC database and can be viewed via the Message Monitor in SAP Integration Suite. The corresponding runtime must be selected in the Monitor - the display is filtered per runtime, not aggregated across all runtimes. This is an important operational difference to communicate to monitoring teams before go-live.

Monitoring View with Runtime Selection

For centralized monitoring of multiple EIC instances, Message Processing Logs can be transferred in a push-based manner to SAP Cloud ALM or SAP Focused Run.

Edge Lifecycle Management (ELM) Interface

Edge Lifecycle Management (ELM) is a separate administration interface from the standard SAP Integration Suite Cockpit. Its URL is displayed in Settings → Runtime after EIC activation.

ELM is the tool through which the EIC software is installed on the Kubernetes cluster and managed over time. It is used primarily by the Edge Node Administrator role - the person responsible for the Kubernetes cluster and EIC infrastructure administration.

ELM manages three main areas:

1. Edge Nodes

An Edge Node represents the Kubernetes cluster where an EIC instance is deployed. ELM is used to register new Edge Nodes, view their health status, and manage their configuration.

2. Solutions

A Solution is the EIC software package deployed on an Edge Node. ELM shows which version of the EIC solution is running on each Edge Node and whether updates are available.

3. Software Updates

When SAP delivers a new EIC software version via the Repository-Based Shipment Channel (RBSC), ELM is the tool through which the update is applied to registered Edge Nodes. The Edge Node Administrator reviews the release notes, plans the update, and executes it through ELM.

Edge Lifecycle Management (ELM) - Nodes Overview

For integration developers: ELM is the Edge Node Administrator's domain. Integration developers do not need to access ELM to design, deploy, or monitor integration flows. The developer's interaction with EIC is entirely within the standard SAP Integration Suite Cockpit.

Role Separation in EIC

EIC introduces a clear separation of responsibilities across three functional roles. Note: These are functional role designations used in SAP's architecture guidance, not the formal SAP BTP Role Collection names. The corresponding BTP role collections are Integration_Provisioner (for IS Administrator functions) and EdgeLMAccess (for Edge Node Administrator).

RolePrimary ToolKey Responsibilities
Integration DeveloperSAP Integration Suite Cockpit (Design & Deploy)Designs iFlows, configures adapters, selects runtime location at deploy time, monitors message processing
Integration Suite AdministratorSAP Integration Suite Cockpit (Settings → Runtime)Activates EIC in SAP Integration Suite, manages runtime locations, assigns roles to users
Edge Node AdministratorEdge Lifecycle Management (ELM) interfaceManages Kubernetes cluster, registers Edge Nodes, installs and updates EIC solution, monitors EIC infrastructure health

This separation means that an integration project team can include developers who work entirely within the SAP Integration Suite Cockpit, while a separate infrastructure team manages the Kubernetes environment and ELM.

Overview of EIC Roles and Key Responsibilities.

Scenario Check-In: Global Manufacturing AG

At Global Manufacturing AG, three roles are in play. The integration developer works in the SAP Integration Suite Cockpit, designing the S/4HANA-to-QMS iFlow and selecting "FRA-EIC-PROD" as the deployment target. The Integration Suite administrator has already completed the EIC activation in Settings → Runtime and confirmed that the ELM URL is accessible. The Edge Node Administrator, a member of the Frankfurt infrastructure team, uses ELM to manage the Kubernetes cluster, monitor the EIC solution health, and apply software updates. The developer never needs to access ELM or touch the Kubernetes cluster directly.

Key Takeaways

For the integration developer, EIC primarily changes the deploy step: a runtime location is selected at deployment time. Design and monitoring remain in the familiar cloud-based SAP Integration Suite Cockpit - in the Monitor, the corresponding runtime must be selected to view logs. Edge Lifecycle Management (ELM) is the separate administration interface for managing Edge Nodes, EIC software, and updates - used by the Edge Node Administrator, not by integration developers. Three roles share the responsibilities: Integration Developer (design/deploy), Integration Suite Administrator (activation/settings), and Edge Node Administrator (ELM/K8s infrastructure).