Platform Independent JSON Configuration Reporting Services

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional reporting services are tightly coupled with databases, making it difficult to generate reports that are platform and database agnostic, and fail to provide programming features that enable users to extend and customize reporting functionality independently of the database or platform.

Innovation Solution

A platform and database agnostic report generating module that uses JSON-based configuration to generate platform-independent libraries, database-agnostic report templates, and supports rich customized features for reporting, allowing for heterogeneous data sources and various report formats without relying on Structured Query Language Server Reporting Services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional reporting services are tightly coupled with databases, then database-specific reporting functionality is achieved, but platform and database agnosticism is lost

Engineering Contradiction:

Improveplatform and database agnosticismVSAvoidreporting service architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the reporting functionality into distinct components: a reporting service layer, a data access layer, and a presentation layer. The reporting service is decoupled from database-specific implementations through the use of configuration files and abstract data access interfaces, allowing the same reporting service to work with different database platforms without modification.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Configuration files serve as intermediaries between the reporting service and database-specific data access layers. These configuration files contain database connection details, query parameters, and data source information, allowing the reporting service to interact with different databases through a standardized interface without direct coupling to database-specific code.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If reporting services depend on database-specific queries and stored procedures, then database integration is achieved, but customization and extension capabilities are limited

Engineering Contradiction:

Improvecustomization capabilityVSAvoidprogramming feature accessibility

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The reporting service is designed with universal functionality that can work with any database platform through standardized configuration files. Users can customize reporting behavior by modifying configuration parameters without needing to change the underlying service code, enabling easy extension and adaptation to different reporting needs across multiple platforms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system enables customization through parameter changes in configuration files rather than code modification. Users can change data source parameters, query parameters, formatting options, and other reporting parameters to adapt the service to different needs, making customization accessible without requiring programming expertise.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If reporting services are tightly integrated with specific databases, then database-specific optimization is achieved, but portability across platforms is reduced

Engineering Contradiction:

Improvereport generation efficiencyVSAvoidplatform independence

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The system uses configuration files as portable representations of database connection and query settings. These configuration files can be copied and reused across different platforms and database systems, maintaining reporting efficiency while enabling portability. The same configuration file can be used with different database backends without requiring code changes.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12287769B2System, method, and computer program for platform independent JSON configuration based reporting services

Publication Date: 2025.04.29 JPMORGAN CHASE BANK NA

AI summary

Various methods, apparatuses/systems, and media for generating platform and database agnostic reports without depending on reporting services are disclosed. A processor receives a configuration file via a user interface, the configuration file including reporting configurations for components associated with reporting service; interprets the configuration file by utilizing corresponding interpreter libraries; invokes, in response to interpreting the configuration file, a predefined application programming interface (API); processes, in response to invoking the API, the reporting configurations using the interpreter libraries to process data object references and pre-configured report layout formats; receives a request from a user to generate a custom report; and automatically renders, in response to receiving the request, a platform and a database agnostic report by implementing a desired visualization techniques.