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.