Interfaces (Visualization)
The Interfaces visualization provides a dynamic system flow diagram showing how systems are connected through integration interfaces. Use this view to understand integration relationships from both sender and receiver perspectives across your landscape.
Workflow Integration: The Interfaces visualization connects system dependency analysis with interface flow understanding, enabling visual exploration of integration patterns and system connectivity across your enterprise architecture.
Accessing the Visualization
Navigate to Landscape → Visualization → Interfaces to access the interactive system flow visualization.
System Selection: Choose from available systems in your landscape for visualization analysis
Clicking a system name loads the integration flows associated with that system
Available systems include all harmonized systems from your integration landscape
Real-time filtering shows systems based on your integration data
System selection showing available systems for visualization analysis
The system list shows examples like Account Management, Adams Testsystem and Airlines Check-In, representing the diverse system types in your environment.
Understanding the Flow Diagram / System Flow Visualization
The Interfaces visualization displays systems assigned to interfaces in an interactive flow diagram format. Systems are shown as connected nodes/lines showing integration relationships discovered through transformation rules processing.
As Receiver
Shows systems from the receiving perspective:
Systems that receive data from other systems in integration flows
Visual representation of inbound data flows and dependencies
Helps identify systems that consume data from multiple sources
As Sender
Shows systems from the sending perspective:
Systems that send data to other systems in integration flows
Visual representation of outbound data flows and dependencies
Helps identify systems that distribute data to multiple targets
Integration Architecture Analysis:
Use both As Receiver and As Sender views to understand different aspects of your integration architecture. The receiver perspective helps identify data consumption patterns, while the sender perspective shows data distribution patterns across your enterprise systems.
Navigation Controls
Manage your view of the integration landscape:
Plus button (+): Zoom in for detailed view of system connections and relationships
Minus button (-): Zoom out for broader landscape overview
Fit view button (□): Single click to automatically adjust view to show all systems perfectly
Lock button: Lock the view to prevent accidental zooming or moving while analyzing flows
Example: Airport Integration Architecture Analysis
The airport/airline integration visualization demonstrates how you can analyze enterprise integration patterns to understand system dependencies and architectural relationships.
EAM appearing as central hub in both As Receiver and As Sender flows, indicating its critical role in airport operations
Identifying Hub Systems: The visualization shows EAM (Enterprise Asset Management) appearing in multiple flows across both As Receiver and As Sender perspectives, identifying it as the central coordination hub for airport operations. This pattern indicates EAM serves as a critical dependency point that coordinates airport operations across multiple operational systems.
Integration Chain Analysis:
The As Sender perspective reveals the passenger check-in workflow sequence where Airlines Check-In generates data that flows through Boarding Pass processing before reaching EAM for enterprise coordination. This flow pattern shows the complete passenger processing integration chain.
Finding Isolated Systems: Notice Report Generation and Airport Mobile v1.0 (in sender mode) appear as standalone systems without extensive integration connections. This suggests these might be:
Legacy systems not fully integrated or needing modernization
New systems that need better connection to the main architecture
Systems requiring integration architecture review
Architecture Pattern Recognition: The visualization reveals a hub-and-spoke integration pattern where operational systems (Billing, Order processing, Airlines Check-In) connect through the central enterprise system rather than maintaining direct system-to-system connections. This centralized architecture pattern supports:
Dependency planning: Understanding that EAM availability affects multiple operational systems
Performance optimization: Recognizing that EAM capacity impacts overall airport operations
Integration strategy: Identifying opportunities to better integrate isolated systems through the central hub
Using Integration Insights
The visualization enables comprehensive integration pattern analysis to identify hub systems with many connections, isolated systems with few integration connections and critical dependencies that are central to multiple integration flows.
Dynamic Layout: Systems are positioned to show clear integration flow patterns and dependencies, with visual representation of direct connections, flow direction understanding and integration complexity assessment.
Architecture Review: Visual analysis enables dependency mapping to understand system interdependencies, integration complexity assessment to identify complex integration patterns and architecture optimization opportunities to spot potential simplification areas.
Data Source: The system flow visualization is based on systems assigned to interfaces through transformation rules processing. Systems and connections shown reflect the harmonized system mappings configured in your transformation rules, providing standardized system identifiers, interface relationships established through transformation rule mappings and visual representation of enterprise integration architecture.
Last Updated: August 21, 2025