Virtual Application Configuration Runtime Modification Merge

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing virtual applications have read-only executable files that cannot be modified during runtime, making it difficult to incorporate changes made during execution back into the application configuration without manual editing or repeating snapshot processes.

Innovation Solution

A sandbox merge tool is introduced to read and write modifications from a sandbox location into the application configuration, allowing changes made by the virtual application during runtime to be seamlessly integrated into the virtualized application file, eliminating the need for manual editing and reducing the complexity of snapshot processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the executable files storing the virtual application are made read-only to protect integrity, then reliability is improved, but ease of operation deteriorates because modifications cannot be made during runtime

Engineering Contradiction:

Improveintegrity of executable filesVSAvoidability to modify configuration

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system separates the virtual application configuration into two distinct components: read-only executable files that maintain integrity, and a writable sandbox directory that accepts runtime modifications. This segmentation allows the executable files to remain protected while enabling configuration changes through the sandbox mechanism.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The sandbox acts as an intermediary between the read-only executable files and the desired modifications. Users can make configuration changes in the sandbox environment, and these changes are later merged back into the executable files through automated tools, eliminating the need for direct editing of protected files.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If modifications are stored in a sandbox location during runtime, then ease of operation is improved, but loss of information occurs because changes cannot be written back to the executable files

Engineering Contradiction:

Improveability to modify configurationVSAvoidruntime modifications

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The system implements a feedback mechanism where modifications made in the sandbox during runtime are detected, captured, and merged back into the executable files. This feedback loop ensures that temporary sandbox changes are permanently integrated, preventing loss of information while maintaining the read-only nature of the original files.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by creating a sandbox environment where modifications can be safely made before finalizing them. This preliminary modification phase allows users to test and adjust configurations without risking the integrity of the original executable files, and subsequent merging consolidates these changes.

Inventive Principle:

Principle #10Preliminary action

3Manufacturing precision

If manual editing or snapshot processes are used to incorporate changes, then manufacturing precision is maintained, but productivity deteriorates due to time-consuming processes

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidspeed of updating applications

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The system implements self-service automation where a merge tool automatically detects, captures, and integrates sandbox modifications into the executable files without requiring manual intervention. This automated process maintains configuration accuracy while dramatically improving productivity by eliminating time-consuming manual editing and snapshot procedures.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system replaces manual mechanical processes (hand-editing configuration files, manually creating snapshots) with an automated software-based merge tool. This substitution maintains the precision of configuration updates while eliminating the time and effort required for manual operations, thereby improving productivity.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9773017B2Method of configuring a virtual application

Publication Date: 2017.09.26 CODE SYSTEMS CORP

AI summary

A method of modifying a virtual application configuration to include modifications made at runtime by a virtual application that is implemented by a first virtualized application file that was created previously using the virtual application configuration. At runtime, the virtual application implemented by the first virtualized application file stores modifications to its configuration in a sandbox memory location. The method includes reading the modifications from the sandbox memory location. Then, the modifications are written to the virtual application configuration. The modified virtual application configuration is then used to create a second virtualized application file that includes the modifications stored in the sandbox memory location.