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.
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).
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.
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.