About the Map
See every package, iFlow, API proxy and queue in your landscape, and the systems they talk to, in one picture.
The Map draws everything the last sync found in SAP Integration Suite, together with the systems around it. Lines are the connections that SAP’s design files declare: who sends to whom, and over which adapter. Nothing is placed on the map unless SAP returned it.
What the columns mean
Section titled “What the columns mean”Each column is a platform that Integration Mapper syncs: SAP Cloud Integration, SAP API Management and SAP Event Mesh. Anything else that appears in a design, but is not synced, is an external system:
- ERP and HCM get their own group when they are recognised with certainty, for example SAP S/4HANA or SuccessFactors.
- Everything else goes to External systems.
A product that Integration Mapper does not sync never gets its own column, even when it is mentioned in an iFlow. A column would suggest an inventory, versions and metrics that do not exist.
Three views, one landscape
Section titled “Three views, one landscape”The same data can be drawn three ways:
- Groups is the overview. Each package is a card with its iFlows inside, and the groups can wrap into several rows. This is the default view.
- Tunnel puts the groups in a single row and runs the lines in corridors above and below them, so connections never cross the cards.
- Production is compact, for operations. Its tiles can be placed freely.
Positions you change are saved per view, so arranging one does not disturb the others.
When to use which
Section titled “When to use which”Use Groups when you need to answer questions like:
- What does our integration landscape look like?
- Which packages are the largest?
- Where does a given iFlow live?
Use Tunnel when you need to answer questions like:
- Which systems does this package talk to?
- What is connected to SAP S/4HANA, and over which adapters?
- How many paths lead from one system to another?
Use Production when you need a compact board of what is running, arranged the way your team works.
What it needs
Section titled “What it needs”The Map is built from the Discovery sync. Credentials for SAP Cloud Integration must be active; SAP API Management and SAP Event Mesh are added to the map when their credentials are present. An iFlow appears with its senders and receivers once its design has been read.
Next steps
Section titled “Next steps”- Use the Map: search, select, filter and move things around
- Arrange with templates: decide where each group sits, or let Auto-arrange do it
- Explore in 3D: go down into a block and into an iFlow’s design