Central Service for Automatic Middleware Data Querying

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems require users to manually specify the location of middleware components to search for data, lacking the ability to intelligently identify the correct component and retrieve data automatically based on user-provided search parameters.

Innovation Solution

A method and system for central data querying that retrieves user parameters, determines the appropriate device, generates a query, and executes it to extract data, utilizing a central service that refers to a landscape directory to identify devices storing similar data and forwards the query to those devices for parallel or sequential execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually specify the location of middleware components to search for data, then data retrieval can be performed, but the ease of operation deteriorates because users must have knowledge of the middleware component structure

Engineering Contradiction:
Improveease of data searchVSAvoiduser knowledge requirement
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent introduces a central service as an intermediary between the user and middleware components. This central service receives user search parameters, determines the appropriate middleware component addresses, generates queries, and executes them automatically. The intermediary eliminates the need for users to directly interact with or know the internal structure of middleware components, thereby improving ease of operation while preventing information loss about component locations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the system automatically determines device addresses based on search parameters, then ease of operation improves, but device complexity increases due to the need for intelligent identification and query generation

Engineering Contradiction:
Improveease of data searchVSAvoidcentral service complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the data retrieval functionality into distinct components: a user interface for parameter input, a central service for address determination and query generation, and multiple middleware components for data storage. This segmentation allows the central service to handle complexity systematically by breaking down the automated determination process into manageable steps (receiving parameters, determining addresses, generating queries, executing queries), thereby improving ease of operation while managing device complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

3Productivity

If users provide exact addresses of middleware components, then data retrieval is direct and efficient, but adaptability deteriorates because the system cannot handle unknown or dynamic component locations

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidsystem adaptability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by enabling the central service to adaptively determine middleware component addresses based on search parameters rather than relying on static, pre-provided addresses. The system can dynamically resolve component locations, generate appropriate queries, and execute them successfully. This dynamic approach maintains high productivity through efficient automated retrieval while significantly improving adaptability to handle unknown or changing component locations in the heterogeneous system landscape.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8924403B2Method and system for central data querying
Publication Date: 2014.12.30 SAP SE
  • US8924403B2 patent drawing
  • US8924403B2 patent drawing
  • US8924403B2 patent drawing

AI summary

A method and system for central data querying are provided. A user parameter requesting data is retrieved. A device is determined based upon the user parameter. A query is generated based upon the user parameter. The query is executed in the device to extract the data.