Database Independent Web Application Archiving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for copying or archiving web-based applications are cumbersome and inefficient, as they are typically performed in a database and operating system-dependent manner, requiring separate utilities for file system and non-file system structures.
Innovation Solution
A method that initializes a file with a root directory, creates data directories, and stores non-file system structures as storage data objects, with files from the file system stored as additional data objects, allowing for a database and operating system-independent copying and archiving process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate utilities are used to copy file system structures and non-file system structures, then the copying process can handle different data types, but the copying process becomes cumbersome and inefficient
Solution Approach 1:
The patent combines separate utilities for copying file system structures and non-file system structures into a single integrated utility. This unified utility can handle both types of data through a common interface and processing mechanism, eliminating the need to switch between different tools and simplifying the overall copying process while maintaining the ability to handle diverse data types.
Solution Approach 2:
The copying utility is designed with multi-functionality to handle both file system structures (directories, files) and non-file system structures (database tables, schemas, users) through a single interface. This universal utility performs multiple copying functions that previously required separate specialized tools, improving ease of operation without sacrificing adaptability.
2Ease of manufacture
If database and operating system dependent utilities are used, then the copying process can leverage existing tools, but the copying process becomes database and operating system dependent
Solution Approach 1:
The patent creates a universal copying utility that can operate across different database systems and operating systems without being dependent on any specific platform. The utility implements platform-independent interfaces and processing logic, allowing it to leverage existing tools on various platforms while maintaining portability and independence from specific database or operating system implementations.
Solution Approach 2:
The patent introduces an intermediary layer between the copying utility and the underlying database/operating system structures. This intermediary layer provides standardized interfaces that abstract away platform-specific details, allowing the utility to interact with different database systems and operating systems through a common protocol, thereby achieving platform independence while still utilizing existing system capabilities.
3Manufacturing precision
If files and non-file system structures are copied separately, then each data type can be processed appropriately, but the overall copying efficiency decreases
Solution Approach 1:
The patent merges the separate copying operations for files and non-file system structures into a single coordinated process. The unified utility processes both data types simultaneously through integrated processing logic, maintaining appropriate handling for each data type while eliminating the overhead of sequential processing and improving overall copying efficiency.
Solution Approach 2:
The patent implements continuous processing where the copying utility operates on both file system structures and non-file system structures in an uninterrupted sequence without requiring intermediate storage or manual intervention between stages. This continuous action eliminates idle time and improves productivity while maintaining the precision needed for different data types.
Data Source
AI summary
A web based application having non-file system structures is copied or archived by first initializing a file to store the web based application, including creation of a root directory within the file. Then, data directories are created under the root directory, and a number of storage data objects under the data directories are initialized for all non-file system structures of the web based application. Thereafter, the non-file system structures are copied and stored into the storage data objects. In embodiments where the web based application further includes files that are part of a file system, the files are stored as additional storage data objects under the root directory. Accordingly, database and operating system independence is achieved.


