Service Integration Framework Using Adaptation Patterns

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enterprise systems require manual and labor-intensive processes for integrating services into core business applications, limiting scalability and participation from non-experts due to proprietary, low-level adaptation techniques and lack of abstraction, which complicates the integration of unforeseen services across multiple application layers.

Innovation Solution

A service integration framework that uses a pattern-driven approach with an integration modeling environment to model and parameterize adaptation patterns, allowing seamless integration of services into enterprise systems by linking application extensibility points with service elements, thereby increasing abstraction and reducing manual coding and expertise requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual integration techniques are used to extend enterprise systems with services, then integration flexibility is achieved, but integration complexity and manual effort increase significantly

Engineering Contradiction:
Improveintegration flexibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an integration framework as an intermediary layer between services and enterprise systems. This framework provides standardized adapters and integration patterns that mediate the connection between external services and core business applications, reducing the complexity of direct manual integration while maintaining flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration framework segments the integration process into distinct components: service adapters, integration patterns, and configuration mechanisms. By dividing the complex integration task into manageable segments with predefined interfaces and patterns, the system reduces overall integration complexity while preserving adaptability.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If proprietary low-level adaptation techniques are used, then integration capability is achieved, but ease of operation and expertise requirements worsen

Engineering Contradiction:
Improveintegration capabilityVSAvoidexpertise requirements
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent employs integration patterns that copy and reuse proven integration approaches across different service-to-enterprise-system scenarios. By storing and reusing successful integration templates, the system enables operators to leverage past solutions rather than creating integration logic from scratch, significantly reducing expertise requirements.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The framework provides high-level configuration parameters and abstractions that allow integration to be defined through parameter specification rather than low-level coding. By changing the interface from code-level manipulation to parameter configuration, the system maintains integration capability while dramatically improving ease of operation.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple application layers are adapted for service integration, then comprehensive service integration is achieved, but device complexity and integration time increase

Engineering Contradiction:
Improveservice integration completenessVSAvoidintegration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent defines integration patterns and adapter templates in advance that cover common multi-layer integration scenarios. By preparing these integration blueprints beforehand, the system can rapidly configure and execute integrations across presentation, business logic, and data layers without time-consuming on-site analysis and development.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The integration framework provides universal adapters and patterns that can be applied across multiple application layers simultaneously. A single integration pattern can coordinate changes across presentation layer, business logic layer, and data layer, achieving comprehensive service integration through a unified approach rather than handling each layer separately.

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

4Adaptability or versatility

If manual coding and programming are required for integration, then customization flexibility is achieved, but productivity and scalability worsen

Engineering Contradiction:
Improvecustomization flexibilityVSAvoidintegration productivity
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The integration framework enables self-service configuration where integration is achieved through automated adapter instantiation and pattern application rather than manual coding. The system provides self-describing interfaces and automated wiring mechanisms that allow integration to be configured without extensive programming expertise, significantly improving productivity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The framework replaces manual coding with high-level parameter configuration and automated code generation. By specifying integration requirements through configuration parameters rather than writing integration code, the system maintains customization flexibility while dramatically improving integration speed and scalability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2378415B1Service integration modeling and execution framework
Publication Date: 2015.07.08 SAP SE
  • EP2378415B1 patent drawingFigure 1~2
  • EP2378415B1 patent drawingFigure 3
  • EP2378415B1 patent drawingFigure 4

AI summary

In one embodiment, a method for integrating a service into an application is provided. The method determines an application extensibility description for an application. The application extensibility description includes a set of application extension points. The method determines a service description for a service, the service description including a set of service elements. An adaptation pattern is determined and includes a first port connected to an application extension point in the set of application extension points and a second port connected to a service element in the set of service elements. A computing device generates an integration description based on the adaptation pattern having the first port connected to the application extension point and the second port connected to the service element. The integration description allows the application to be adapted or extended with the service.