Adapter Framework for Heterogeneous System Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current business systems face challenges in integrating and collaborating information and enterprise software due to direct one-to-one connections, making upgrades and extensions resource-intensive, and legacy systems present technical connectivity issues that new protocols and standards like HTTP and XML cannot fully address.

Innovation Solution

An adapter framework with messaging adapters that connect applications using SOAP over HTTP, providing Java Messaging Service (JMS), JDBC, and file I/O, and a pure Java adapter engine for platform neutrality, enabling communication between heterogeneous external data sources and a central message exchange server through XML messaging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If direct one-to-one connections are used between application components, then integration capabilities are hardwired into components, but collaborative sharing becomes difficult and upgrades are resource-intensive

Engineering Contradiction:

Improveintegration capabilityVSAvoidcollaborative sharing

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an adapter framework as an intermediary layer between application components and the integration server. Adapters translate messages from various protocols (JMS, JDBC, file I/O) to SOAP over HTTP, enabling collaborative sharing without direct component connections and allowing independent upgrades of individual adapters.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If new protocols like HTTP and XML are used for connectivity, then universal connectivity is provided, but technical connectivity gaps with legacy systems remain

Engineering Contradiction:

ImproveconnectivityVSAvoidtechnical connectivity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The adapter framework changes protocol parameters by implementing multiple protocol handlers that convert legacy system protocols (JMS, JDBC, file I/O) into HTTP/XML/SOAP parameters. This allows legacy systems to communicate through the standard HTTP/XML interface without modifying their internal protocols.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If multiple protocol adapters are implemented, then connectivity to diverse systems is improved, but system complexity increases

Engineering Contradiction:

Improveprotocol compatibilityVSAvoidadapter framework

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The integration server provides a universal SOAP-based interface that all adapters communicate with using the same HTTP protocol. Each adapter handles a specific protocol but all converge on the same universal interface, reducing overall system complexity while maintaining protocol compatibility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The adapter framework segments protocol-specific functionality into separate, independent adapter modules. Each adapter is a discrete unit that can be developed, deployed, and upgraded independently, managing complexity through modular segmentation rather than monolithic design.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS7865606B1Adapter framework

Publication Date: 2011.01.04 SAP SE

AI summary

A framework for communicating between central message exchange server and one or more heterogeneous external data sources includes an adapter engine. The adapter engine includes an instantiation of one or more adapters. Each adapter is configured to connect, via messaging, an external data source operating using a native message format and the central message exchange server using an extensible markup language (XML) messaging format.