Addon Configuration Retention in Web Application Server Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software platform upgrades often result in the overwrite of configuration information for addon software packages, leading to service disruptions and requiring manual, time-consuming restoration processes.
Innovation Solution
The implementation of an addon presence file to store configuration information separately from the common configuration file, allowing automated processes to detect and restore addon configuration information during software platform upgrades, thereby preventing data loss and service disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If configuration information is stored in a common configuration file during software platform upgrades, then the upgrade process can proceed smoothly with new platform features, but the configuration information for addon software packages is overwritten and lost
Solution Approach 1:
The patent segments configuration information into two distinct parts: common platform configuration and addon-specific configuration. The addon presence file serves as a separate storage mechanism that identifies and preserves addon configuration information independent of the common configuration file, allowing the platform to upgrade without losing addon settings.
Solution Approach 2:
The patent implements preliminary action by creating and maintaining an addon presence file before the upgrade occurs. This file预先 identifies which addons are installed and where their configuration information is located, enabling automated restoration of addon configurations after the platform upgrade completes.
2Loss of information
If manual restoration of configuration information is performed after software platform upgrades, then configuration information can be restored, but the process is time-consuming and requires administrator intervention
Solution Approach 1:
The patent implements self-service by enabling the system to automatically restore addon configuration information without requiring administrator intervention. The automated process reads the addon presence file, locates the preserved configuration information, and restores it to the appropriate locations, eliminating manual restoration efforts.
Solution Approach 2:
The addon presence file acts as a feedback mechanism that provides the system with information about which addons are installed and where their configurations are stored. This feedback enables the automated restoration process to correctly identify and restore the appropriate configuration information after an upgrade.
3Adaptability or versatility
If configuration information is overwritten during software platform upgrades, then new platform features can be implemented, but service disruptions occur until configuration is restored
Solution Approach 1:
The patent performs preliminary action by preserving addon configuration information in the addon presence file before the upgrade overwrites the common configuration file. This ensures that configuration data is not lost and can be quickly restored, minimizing service disruption time and maintaining reliability during platform updates.
4Loss of information
If manual editing of configuration files is required for each software platform instance, then configuration can be restored, but the complexity of the restoration process increases with the number of instances
Solution Approach 1:
The patent implements self-service by automating the entire restoration process across multiple software platform instances. The system automatically reads the addon presence file, identifies the required configuration information, and restores it to each instance without requiring administrator intervention, thereby reducing process complexity regardless of the number of instances.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Technologies are described for retaining configuration information for software applications during upgrades. For example, when an addon software package is deployed to a web application server running a main software platform, the configuration information for the addon software package can be preserved separately (e.g., independent of the common configuration file) and used later to restore the addon configuration information if needed. In some implementations, an addon presence file is used to store an entry for the addon software package. The entry identifies another file containing the configuration information for the addon software package. If the main software platform is upgraded resulting in the common configuration file being overwritten or replaced, then the addon configuration information can be added back to the common configuration file using the preserved configuration information.