Generic API for Database Asset Web Service Exposure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies fail to provide generic implementations for exposing database assets, including user-defined functions (UDFs) and stored procedures, as web services, which hinders the ability to efficiently manage and utilize business critical data across multiple systems.

Innovation Solution

A generic application programming interface (API) is created on the application layer of a Master Data Management system to interact with database objects and convert them into web services, allowing database assets to be exposed as web services, utilizing a design time component to define and a run time component to process and format the data for web service operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If database assets are exposed as web services using custom implementations, then functionality can be achieved, but development time and complexity increase

Engineering Contradiction:
Improveimplementation speedVSAvoiddevelopment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal framework that can expose any database asset (tables, views, stored procedures, UDFs) as web services through a standardized process. The Meta Data Repository stores reusable metadata about database assets, and the Framework enables generic web service generation without custom implementation for each asset type, thus improving productivity while maintaining manageability of complexity.

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

Solution Approach 2:

The Framework performs preliminary actions by automatically generating web service code and metadata before deployment. The Meta Data Repository pre-stores information about database assets, and the Framework uses this pre-prepared information to quickly generate web services, eliminating the need for manual development and reducing both time and complexity.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If generic web service exposure is implemented, then implementation cycle shortens, but system architecture complexity increases

Engineering Contradiction:
Improveimplementation cycleVSAvoidsystem architecture
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent segments the web service exposure process into distinct modular components: the Meta Data Repository for storing asset information, the Framework for coordination, the Web Service Generator for code creation, and the Execution Environment for runtime operations. This segmentation allows each component to be developed and maintained independently, reducing the perceived complexity despite the comprehensive functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Framework acts as an intermediary layer between the database assets and the web service layer. It manages the complexity by providing a standardized interface and automation processes, allowing users to expose database assets without directly dealing with the underlying architectural complexity of web service generation and deployment.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If manual web service creation is used, then control over implementation is maintained, but additional skill sets are required

Engineering Contradiction:
Improveease of implementationVSAvoidskill set requirements
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The Framework enables self-service by automatically generating web service code from database asset metadata. Users simply need to specify which database assets to expose, and the Framework handles the complex tasks of code generation, metadata management, and deployment configuration, making the process accessible to users without specialized web service development skills.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9489437B2Master data management database asset as a web service
Publication Date: 2016.11.08 TERADATA CORP
  • US9489437B2 patent drawing
  • US9489437B2 patent drawing
  • US9489437B2 patent drawing

AI summary

A method, system, apparatus, and article of manufacture is configured to expose a database asset as a web service. A relational database management system (RDBMS) that stores information is executed in a computer system. As part of a process and framework, a series of business rules and process workflows are maintained that manage data that resides in RDBMS tables. A rule is created that contains an application programming interface definition with predefined input and output for exposing the database asset as the web service. The rule is exposed as the web service. The web service is used to invoke a database operation based on the database asset, and to output a result.