Content Transfer Between Files and Databases Using Field Type Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Enterprise Application Integration (EAI) methods face challenges in automatically transferring information between disparate applications without human intervention, particularly in handling different data formats, which requires complex translation and skilled resources, leading to high development and maintenance costs.
Innovation Solution
A method and processing system that determines the type of each field in a file and database, stores content instances accordingly, and transfers them using queries, enabling efficient mapping and translation between file and database formats, thereby simplifying the integration process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If custom translation solutions are developed for each application installation, then translation accuracy between message format and target structure is improved, but development cost and complexity increase significantly
Solution Approach 1:
The patent introduces a message format translator as an intermediary component that sits between the message receiving interface and the target application structure. This translator automatically converts messages from the standardized message format into the target application's data structure, eliminating the need for custom point-to-point translation code for each application installation while maintaining accurate data transformation.
Solution Approach 2:
The message format translator is designed as a universal component that can serve multiple application installations with different target structures. By implementing a standardized interface and using configurable translation rules, the same translator can adapt to different applications without requiring separate custom solutions for each installation, thereby reducing overall development complexity.
2Reliability
If skilled resources are used to develop custom translation solutions, then data format translation reliability is improved, but resource cost and maintenance burden increase
Solution Approach 1:
The message format translator is designed to be self-configuring through the use of description files that automatically define the translation rules. Instead of requiring skilled developers to manually create and maintain complex translation logic, the system uses automated parsing of description files to generate the necessary translation code, reducing both initial development cost and ongoing maintenance requirements while maintaining reliable data transformation.
Solution Approach 2:
The translation rules and data format descriptions are prepared in advance in separate description files before the actual translation needs to occur. This preliminary configuration allows the system to automatically generate and apply the correct translation logic without requiring skilled resources during runtime, reducing both development cost and operational complexity while ensuring reliable translation.
3Reliability
If application-specific programs are used for data transfer, then data integrity between applications is improved, but system complexity and maintenance requirements increase
Solution Approach 1:
The patent segments the data transfer functionality into separate, independent components: a standardized message format layer and application-specific target structures. The message format translator handles the universal communication protocol, while each application maintains its own simplified interface to the translator. This segmentation allows data integrity to be maintained through standardized protocols without requiring complex point-to-point integration programs for each application pair.
Data Source
AI summary
The present invention provides a method of transferring content from a file and a database. In this case, the file includes content instances, each content instance being associated with a respective field, and each field having a respective type. The transfer is achieved by determining the type of each field, and then storing each content instance in a store in accordance with the determined field type of the associated field. Each content instance can then be transferred to the database in accordance with the determined field type. A similar procedure is provided for creating XML files based on content within the database.