Adapter Flow Modeling for Integration System Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current integration system vendors and modeling approaches fail to systematically classify adapter types and tasks within integration systems, hiding default adapter processing and lacking modification capabilities, which limits understanding and control over system behavior.

Innovation Solution

The method involves receiving adapter-related information, determining communication and quality-of-service patterns, configuring an adapter flow, providing visualization, and storing characterization information to systematically describe and modify adapter processing, enabling better control and configurability of integration systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If default adapter processing is hidden in runtime implementations, then system complexity is reduced, but understanding and control over system behavior deteriorates

Engineering Contradiction:
Improvesystem complexityVSAvoidunderstanding of system behavior
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent introduces an adapter flow model as an intermediary layer between the hidden runtime implementation and the user. This model explicitly represents adapter processing behavior through standardized flow elements (sequence flows, decision gates, parallel branches) that make the hidden logic visible and understandable without requiring users to examine source code directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If adapter processing is hidden behind property sheets, then ease of operation is improved, but adaptability and modification capability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidmodification capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments adapter processing into distinct, modifiable flow elements including sequence flows, decision gates, parallel branches, and error handling blocks. Each segment can be independently configured and modified through property sheets while maintaining the overall adapter flow structure, enabling both ease of operation and adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent makes the adapter flow model dynamic by allowing users to modify the flow structure and processing logic after initial configuration. The model supports adding, removing, and reconfiguring flow elements through property sheets, enabling the system to adapt to different scenarios while maintaining ease of operation.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If systematic classification of adapter types is not implemented, then device complexity is reduced, but adaptability and understanding of adapter behavior deteriorate

Engineering Contradiction:
Improveclassification complexityVSAvoidadapter configurability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal adapter flow model that can represent multiple adapter types and processing patterns through a common set of flow elements. This standardized model provides systematic classification capabilities while maintaining adaptability to different adapter scenarios through configurable properties and flow variations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9483329B2Categorizing and modeling integration adapters
Publication Date: 2016.11.01 SAP SE
  • US9483329B2 patent drawing
  • US9483329B2 patent drawing
  • US9483329B2 patent drawing

AI summary

The disclosure generally describes computer-implemented methods, software, and systems, including a method for generating and storing adapter characterization information. Adapter-related information associated with an adapter is received. Communication patterns associated with the adapter are determined. Quality-of-service patterns are applied to the communication patterns. An adapter flow is configured for the adapter. A visualization of the adapter flow for the adapter is provided. Characterization information determined for the adapter is stored.