Lesson 1 established why systems need to be connected. This lesson answers the how - how should systems be structurally connected? The answer - the integration topology, has architectural consequences that matter directly for the design and placement of Edge Integration Cell.
Understanding Integration Topologies
Objective
Introduction
Integration Topologies at a Glance
Once systems need to communicate, a fundamental design question arises: should they connect directly with each other, or through an intermediary layer? The answer determines the integration topology. There are three fundamental topologies for system integration.
- Point-to-Point:
Systems are connected directly with each other. This is simple when only a few systems are involved. However, the number of interfaces grows rapidly: for 5 systems, you need 10 connections; for 10 systems, already 45; for 20 systems, you need 190. Each interface must be developed, tested, monitored, and maintained independently. This is the fundamental scalability problem of point-to-point integration.

- Bus Topology:
A shared communication channel (the "bus") enables systems to publish and receive messages. The focus is on asynchronous, event-driven, decoupled communication - systems do not need to know about each other directly; they interact through the shared channel. This reduces direct dependencies between systems but requires a common message format and event infrastructure

- Hub-and-Spoke:
A central integration layer (the Hub) mediates all communication. All connected systems (the Spokes) send and receive through the Hub. Instead of connecting each application directly with others, communication flows through the central Hub. This enables centralized routing, transformation, protocol mediation, monitoring, and governance - at the cost of the Hub becoming a critical component that must be reliable and scalable. If the Hub fails or becomes a bottleneck, all connected integrations are affected. This is the classic tradeoff of the hub-and-spoke model: simplified management vs. central dependency.

Edge Integration Cell and the Hub- and- Spoke Topology
The operational model of Edge Integration Cell realizes a hybrid hub-and-spoke architecture. In this hybrid model, the architectural roles are split:
- Centralized management: SAP Integration Suite running on SAP Business AI Platform - integration content is designed, versioned, deployed, and monitored here.
- Decentralized execution: Edge Integration Cell - the local execution environment installed in the customer's private infrastructure. It receives deployed integration content and processes messages within the private landscape. Business messages never pass through the cloud.
This means the governance and management benefits of the hub-and-spoke model are preserved, while data processing happens locally. This is the architectural principle that makes EIC possible.
The SAP Integration Solution Advisory Methodology
Topologies describe how systems are structurally connected. The SAP Integration Solution Advisory Methodology (ISA-M) adds the next level: it classifies integration scenarios by their business purpose and thereby helps select the appropriate integration technology.
ISA-M is SAP's structured, technology-agnostic approach for defining an enterprise integration strategy. Its basic structure has three layers:
- Integration Domains - outline typical integration areas in a hybrid landscape (e.g., cloud-to-cloud, cloud-to-on-premise, on-premise-to-on-premise)
- Integration Styles - classify integration scenarios by business purpose (see table below)
- Use Case Patterns- refine each style into specific, reusable patterns that map to concrete integration technologies
ISA-M Integration Styles
ISA-M defines integration styles as the fundamental categories of integration, each with its own business purpose and characteristics. ISA-M defines five integration styles. This course focuses on the four styles most relevant to Edge Integration Cell:
| Integration Style | Business Purpose | Example Scenario | Typical SAP Technology (simplified) |
| Process Integration | Connects business processes across applications, synchronously or asynchronously. | A production batch completion in S/4HANA triggers a quality inspection request in the QMS. | Cloud Integration / Edge Integration Cell |
| Data Integration | Replicates or synchronizes data sets across systems and data stores. | Customer master data is synchronized between SAP S/4HANA and a third- party CRM. | SAP Datasphere, Cloud Integration, |
| Analytics Integration | Derives and exposes operational data from source systems to support business intelligence and enterprise planning. | Transactional data is extracted from S/4HANA and loaded into an analytics platform for reporting. | SAP Datasphere, Analytics Cloud |
| User Integration | Integrates user- centric applications (mobile apps, browser- based UIs, portals) with business applications. | An SAP Fiori application is embedded within a third-party enterprise portal. | SAP Build Work Zone, Cloud Integration |
Note
ISA-M is technology-agnostic: The technology column shows a simplified mapping for orientation. Actual technology selection depends on the specific use case pattern and customer context.
Note
Thing Integration: ISA-M defines a fifth integration style - Thing Integration - for connecting IoT devices, sensors, and machines to business applications. It is part of the official ISA-M framework (including Template v4.0 and the current SAP Help Portal documentation). This course focuses on the four styles most relevant to Edge Integration Cell. Thing Integration and its use-case patterns are covered in detail in the ISA-M template.
Why ISA-M Matters for This Course
Of the four active ISA-M integration styles, Process Integration is the most relevant to Edge Integration Cell - specifically, Process Integration in a private network, where both systems are on-premise and data must not leave the corporate infrastructure.
EIC is not a general-purpose solution for all integration styles. It is purpose-built for scenarios that require local execution in a customer-managed environment. Ground-to-ground Process Integration - where both sender and receiver reside on-premise - is its primary home territory.
Every other scenario type (cloud-to-cloud, cloud-to-on-prem, event broadcasting, data replication to a cloud analytics platform) may be handled by the standard Cloud Integration runtime or other SAP Integration Suite capabilities. But for Process Integration in a private network, Edge Integration Cell is the primary solution for this use case.
Returning to our example: GlobalManufacturing AG's S/4HANA-to-QMS integration is a classic Process Integration scenario. A business process (production batch completion) triggers data exchange between two on-premise systems. Both systems reside in the private network - this ground-to-ground scenario cannot be routed through external cloud infrastructure. It is the defining use case for Edge Integration Cell in this course.
Key Takeaways
In this lesson, you distinguished the three fundamental integration topologies: Point-to-Point (direct connections, scales poorly as landscapes grow), Bus Topology (shared asynchronous channel), and Hub-and-Spoke (central mediation layer). You learned that EIC realizes a hybrid hub-and-spoke model: cloud-based design and management with private-network execution. You also learned that ISA-M classifies integration scenarios by business purpose into four actively mapped styles - Process, Data, Analytics, and User Integration - and that Process Integration in a private network is the primary ISA-M use case for Edge Integration Cell.
Lesson 3 introduces the technical vocabulary of SAP Integration Suite: the specific objects - Integration Flows, Adapters, Messages, Routing, and more - that you will encounter in every later lesson of this course.