RMS Client-Library Extraction for Readable UI Data Streaming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face challenges in efficiently accessing and analyzing data from an in-memory, column-oriented relational database management system within a data intelligence system, as manual SQL querying is slow, incomplete, and data is often returned in an unreadable format, hindering error troubleshooting and data exploration.

Innovation Solution

A replication management system (RMS) test tool combines a container orchestration system's client library and configuration file to automate data querying and present data in a usable format, enabling efficient extraction and streaming to a user interface (UI) using a client library and configuration file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual SQL querying is used to access data in the repository, then developers can query data, but the querying process is slow and inefficient

Engineering Contradiction:
Improvedata querying speedVSAvoidtime to access and analyze data
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary component that sits between the developer's query request and the repository database. This intermediary automatically formats and executes SQL queries, transforming high-level data requests into optimized database queries without requiring manual SQL writing, thereby significantly improving querying speed while reducing developer time investment

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-compiling and optimizing query templates, and by establishing connection pools and caching mechanisms before actual data retrieval operations. This preliminary preparation eliminates the need for slow, ad-hoc query compilation during actual data access operations

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If developers access data through manual SQL commands, then they can retrieve some data, but they cannot access all data in the repository

Engineering Contradiction:
Improvecompleteness of data accessVSAvoidcomplexity of data access process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a universal data access interface that can handle multiple types of data retrieval operations (full table exports, filtered queries, incremental extracts) through a single unified mechanism. This multi-functional approach allows developers to access any data in the repository regardless of volume or complexity, eliminating the limitations of manual SQL while maintaining operational simplicity

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

Solution Approach 2:

The system provides self-service capabilities by automatically handling query optimization, result formatting, and data export without requiring developers to manually construct complex SQL statements. The interface autonomously manages the complexity of data access operations while providing simple, intuitive access to complete repository data

Inventive Principle:
Principle #25Self-service

3Ease of operation

If data is queried from the repository, then results are obtained, but the returned data is not easy to read and not in a usable form

Engineering Contradiction:
Improvereadability of returned dataVSAvoidefficiency of data analysis
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent applies parameter changes by automatically transforming raw database results into multiple usable formats (CSV, JSON, XML, formatted tables) based on user preferences or application requirements. This format transformation occurs automatically during the data retrieval process, converting unreadable database output into human-readable and machine-processable formats that enhance both readability and analysis efficiency

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

An intermediary formatting layer is introduced between the database engine and the user interface. This intermediary automatically formats query results with proper delimiters, headers, and structure, ensuring that all returned data is immediately usable for analysis without requiring additional processing or manual formatting by developers

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12353433B2Extraction from an internal repository for replication management system in a data intelligence
Publication Date: 2025.07.08 SAP SE
  • US12353433B2 patent drawing
  • US12353433B2 patent drawing
  • US12353433B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for extracting data to stream to a user interface using a client library and configuration file. An embodiment operates by receiving the configuration file from a replication management system (RMS). The embodiment accesses a RMS pod using the client library. The embodiment retrieves a list of tables in a repository using the client library. The embodiment chooses at least one table from the list of tables. The embodiment downloads data from the at least one table. The embodiment exports the data in a readable file format. The embodiment then streams the exported data to the UI.