Differentiating Design Time and Runtime Options

Objective

After completing this lesson, you will be able to differentiate between Design Time and Runtime and describe the runtime options available in SAP Integration Suite.

Introduction

Lesson 3 introduced the Integration Flow as the central deployable artifact. This raises the key question of this lesson: where does an Integration Flow actually execute?

In SAP Integration Suite, the answer depends on a fundamental architectural split between two phases: Design Time - where integration content is created - and Runtime - where it is executed. Understanding this separation is the principle that makes Edge Integration Cell possible, because it allows you to design once and deploy to different execution environments.

Design Time and Runtime

The lifecycle of an integration scenario in SAP Integration Suite has two clearly separated phases:

Design Time is the phase where integration logic is defined and prepared. It encompasses all activities involved in creating integration content before it is put into operation:

  • Modeling Integration Flows using the web-based design environment in the SAP Integration Suite Cockpit
  • Configuring connection endpoints - adapter types, connection parameters, authentication settings
  • Defining processing rules - data mappings, routing conditions, error handling
  • Managing artifacts - organizing Integration Flows into Integration Packages, managing versioning

The Design Time environment is always the SAP Integration Suite Cockpit - a cloud-based web interface running on SAP Business AI Platform. All integration content is created, versioned, and managed in the cloud, regardless of where it will eventually execute.

Runtime is the actual execution environment where a deployed integration scenario processes live messages. Once an Integration Flow is deployed, it becomes active in a runtime - receiving incoming messages, processing them according to its logic, and delivering results to the target system.

Why this separation matters - and why it makes EIC possible: In traditional integration middleware (like SAP PI/PO), the design tool and the runtime are tightly coupled - they run on the same server. If you wanted local execution, you needed a local design environment too.

SAP Integration Suite breaks this coupling: design always happens in the cloud; execution can happen anywhere. This strict separation is precisely what enables the hybrid model of EIC. You design your Integration Flow once, in the same Cockpit you always use - and then choose whether to execute it in the cloud or in your private data center.

The same Integration Flow can generally be deployed to different runtimes without modifications to its design - provided the target runtime supports the features and adapters used.

Design is always cloud-based - only the execution environment varies.

Deployment Options in SAP Integration Suite

SAP Integration Suite supports different deployment options to meet organizational, security, and latency requirements. In all cases, design, configuration, and monitoring remain cloud-based in the SAP Integration Suite Cockpit. What differs is the infrastructure where the runtime executes.

Cloud Integration (Standard Cloud Deployment)

The default deployment option. Integration content runs entirely in the cloud on SAP Business AI Platform, using the Cloud Integration Runtime - a fully SAP-managed execution environment. No customer-managed infrastructure is needed. This option is ideal for standard A2A and B2B scenarios where there are no constraints requiring local data processing.

Use when: data can be processed in the cloud; scenarios are cloud-to-cloud or cloud-to-on-premise; no data sovereignty or residency restrictions apply.

Integration Cell

Integration Cell is a fully SAP-managed runtime within SAP Integration Suite, designed for API-centric integration. It provides a cloud-based execution environment for API artifacts and MCP (Model Context Protocol) servers, with centralized governance, security, and monitoring. Customers do not manage any underlying infrastructure.

Important: Integration Cell is SAP-managed and runs in the cloud. It is not the same as Edge Integration Cell. Integration Cell is for API-centric scenarios in a managed cloud environment; Edge Integration Cell supports both integration flows and API artifacts in a customer-managed private environment.

Use when: deploying API artifacts or MCP servers in a fully managed cloud environment, with no need for local execution.

Edge Integration Cell

Edge Integration Cell is an optional hybrid integration runtime that operates within the customer's private infrastructure - either on-premise or in a customer-managed cloud environment. It is Kubernetes-based, but the Kubernetes cluster is managed by the customer. According to the official SAP definition:

"Edge Integration Cell is an optional hybrid integration runtime offered as part of SAP Integration Suite, which enables you to manage APIs and run integration scenarios within your private landscape."

EIC is the solution of choice when:

  • Data sovereignty or regulatory compliance prevents data from leaving the private network
  • Network constraints make cloud connectivity impractical (e.g., factory floor systems, isolated networks)
  • Ground-to-ground scenarios involve systems that both reside on-premise and do not require cloud routing
  • Migration from SAP PI/PO requires preserving local execution characteristics while gaining cloud-based design and governance

Supported Kubernetes platforms for EIC deployment include: Microsoft Azure AKS, Amazon EKS, Google GKE, SUSE Rancher, and Red Hat OpenShift.

Returning to our example: For Global Manufacturing AG, the S/4HANA-to-QMS scenario must remain within the private network - quality data cannot leave the internal infrastructure. Edge Integration Cell is therefore the appropriate runtime. The Integration Flow is designed in the SAP Integration Suite Cockpit (Design Time, always cloud-based) and deployed to an EIC instance running within the company's private data center (Runtime). Unit 2 examines the architecture of this deployment in full detail.

Key Takeaways

In this lesson, you differentiated between Design Time (where integration content is created - always cloud-based in the SAP Integration Suite Cockpit) and Runtime (the execution environment - chosen at deployment). You learned that SAP Integration Suite supports three deployment options:

  • Cloud Integration Runtime (standard cloud deployment) - SAP-managed, cloud-based execution
  • Integration Cell - for API-centric integration (API artifacts and MCP servers)
  • Edge Integration Cell - customer-managed Kubernetes in private infrastructure

Integration flows are designed once in the cloud and can be deployed to different runtimes - Cloud Integration or Edge Integration Cell - at deployment time.

The Design Time / Runtime separation is the architectural principle that makes EIC possible: cloud-based design and governance with private-network execution.

You have now completed Unit 1. Every concept introduced here - heterogeneous landscapes, topologies, ISA-M, core integration objects, and the Design Time / Runtime split - forms the foundation for Unit 2, where Edge Integration Cell itself takes center stage.