Mapping Proxy Module for Web Service Interface Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Efficient mapping of messages between web services with differing interfaces is challenging, as existing solutions require modifying applications and do not effectively handle asynchronous and synchronous operations across different service formats.

Innovation Solution

A mapping proxy module identifies and employs mapping interfaces based on the first web service, mapping messages to associated second web services with logical port connections, supporting asynchronous and synchronous mappings to adapt operations to the second service format without modifying the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a mapping proxy module is introduced to map messages between web services with differing interfaces, then compatibility and adaptability between services are improved, but system complexity increases due to the additional mapping layer

Engineering Contradiction:
Improveinterface compatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A mapping proxy module is introduced as an intermediary component between the first web service and the second web service. This proxy module contains a mapping interface that stores mapping relationships between different service interfaces, enabling message format conversion without modifying the original web services. The intermediary handles the complexity of interface adaptation internally while presenting a simple interface to both services.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If message mapping is implemented to support both asynchronous and synchronous operations, then operational versatility is improved, but mapping complexity increases

Engineering Contradiction:
Improveoperational versatilityVSAvoidmapping complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The mapping interface is segmented into different mapping type indicators, including asynchronous mappings and synchronous mappings. Each mapping type is handled separately with specific processing logic, allowing the system to support multiple operational modes while maintaining clear, organized mapping relationships. This segmentation enables versatile operation support without creating monolithic complexity.

Inventive Principle:
Principle #1Segmentation

3Reliability

If application modification is avoided to maintain existing functionality, then system stability is improved, but integration capability deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidintegration capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Instead of modifying the original web services, the mapping proxy module creates virtual copies of the service interfaces through mapping relationships. These mappings replicate the interface behavior and data structures of the first web service in terms compatible with the second web service, allowing integration without altering the original services and thus maintaining system stability while achieving integration capability.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2669801B1Mapping messages between web services
Publication Date: 2019.04.17 SAP SE
  • EP2669801B1 patent drawingFigure 1
  • EP2669801B1 patent drawingFigure 2A~2B
  • EP2669801B1 patent drawingFigure 3

AI summary

Techniques for mapping of messages includes receiving, from a first web service, a message comprising one or more operations in a first format; identifying a mapping interface that is based on the first web service, the mapping interface comprising one or more mappings for each of the operations of the message; identifying a second web service that is associated with the identified mapping interface; mapping the message to the second web service such that the one or more operations are in a second format associated with the second web service; and assigning a logical port connection to the second web service.