Database Procedure Web Service Exposure via Metadata Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database procedures are not universally accessible over public networks due to the use of proprietary protocols in existing access APIs, limiting their exposure and invocation as web services.
Innovation Solution
Automatically constructing a Web service definition using metadata from database procedures, converting SQL data types to XML data types, and generating SOAP messages to invoke procedures stored in a database as web services, allowing universal accessibility and invocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If access APIs are used to invoke stored procedures, then database procedures can be accessed by database clients, but the stored procedures are not universally accessible over public networks due to proprietary protocols
Solution Approach 1:
The patent introduces a web service layer as an intermediary between database clients and stored procedures. This intermediary converts proprietary database protocols into standard web service protocols (HTTP, XML, SOAP), enabling universal accessibility while maintaining database procedure functionality. The web service acts as a mediator that translates between different communication standards.
Solution Approach 2:
The patent changes the communication parameters from proprietary binary protocols to standard web service parameters (HTTP methods, XML data formats, SOAP envelopes). This parameter transformation enables stored procedures to be accessed through universal web service interfaces rather than being locked to specific database client protocols.
2Ease of operation
If stored procedures are exposed as web services, then universal accessibility is achieved, but automatic construction of web service definitions requires metadata retrieval and conversion
Solution Approach 1:
The system performs self-service by automatically retrieving metadata about stored procedures from the database and generating web service definitions without requiring manual intervention. The database system itself provides the information needed to construct web service interfaces, eliminating the need for developers to manually create WSDL files or configuration documents.
Solution Approach 2:
The patent performs preliminary action by pre-retrieving and storing metadata about stored procedures (parameter types, data formats, return values) in a structured format that can be directly used to generate web service definitions. This preliminary preparation eliminates the need for real-time metadata extraction during web service construction.
3Adaptability or versatility
If SQL data types are converted to XML data types, then web service compatibility is improved, but data type conversion complexity increases
Solution Approach 1:
The patent systematically changes data type parameters from SQL-specific types (VARCHAR, NUMBER, DATE, BOOLEAN) to standard XML data types (xsd:string, xsd:integer, xsd:dateTime, xsd:boolean). This parameter transformation enables direct compatibility with XML-based web services while maintaining the semantic meaning of the data.
Solution Approach 2:
The patent creates universality by establishing a mapping between SQL data types and XML data types that works across different database systems and web service implementations. The conversion mechanism is designed to be multi-functional, handling various data types through a unified approach that maintains compatibility across different platforms.
Data Source
AI summary
A database server that manages a database retrieves metadata that is stored, within the database, in association with a procedure that is stored in the database. Based on the metadata, a Web service definition is automatically constructed to describe the procedure as a Web service. The WSDL definition can be referenced to construct SOAP messages with the appropriate arguments and in the appropriate format which, when received, are converted to a suitable format for invoking execution of the procedure by the database server.