Declarative vSolution Packaging Format for Software Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software installation processes for cloud-based applications are inefficient and error-prone due to the need for individualized installer executables, which require developers to handle various system configurations and increase the likelihood of errors.
Innovation Solution
A declarative multi-artefact software installation approach using a vSolution packaging format that organizes artefacts by content type and employs universal handlers on the application server, eliminating the need for dedicated installation executables and allowing developers to focus on metadata and content organization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If individualized installer executables are created for each software package, then the installation process can handle specific application requirements, but the system complexity and error probability increase
Solution Approach 1:
The patent implements a universal installer executable that can handle multiple software packages through a manifest file system. The manifest files contain application-specific installation instructions, allowing a single installer to adapt to different applications without requiring individualized installer code for each package.
Solution Approach 2:
The installation system is segmented into separate components: a universal installer executable and application-specific manifest files. This separation allows the installer logic to remain generic while application-specific details are isolated in manifest files, reducing overall system complexity.
2Ease of manufacture
If individualized installer executables are programmed for each application, then specific installation requirements are met, but development time and error introduction increase
Solution Approach 1:
A single universal installer executable serves all software packages, eliminating the need to program individualized installers for each application. The installer reads application-specific requirements from manifest files, maintaining customization capability while dramatically reducing development time.
Solution Approach 2:
Instead of creating unique installer code for each application, the system uses template-based manifest files that can be copied and modified for different applications. This approach reuses the same installer executable template across multiple packages.
3Adaptability or versatility
If new developers create installer executables for unfamiliar application servers, then application-specific installation is achieved, but system reliability decreases due to increased error likelihood
Solution Approach 1:
The universal installer executable is created by experienced developers and can be used across multiple applications and target systems. This reduces reliance on new developers creating installers for unfamiliar systems, as the universal installer handles most installation scenarios through its manifest-based approach.
Solution Approach 2:
The installer executable performs self-configuration by reading application-specific details from manifest files rather than requiring developers to hardcode installation logic. This allows the installer to adapt to different applications automatically, reducing human error in the installation process.
Data Source
AI summary
In an example embodiment, a solution is used to provide for a highly efficient application installer. A software packaging format, known as vSolution, is provided that allows software developers to ship multiple artefacts of different types in a single container. Unlike traditional mechanisms, this container does not contain a dedicated installer executable or any sort of installation routine. Rather, the container format encourages a declarative approach to describe what an installation routine should perform, via the organization of the artefacts based on content type and using a naming convention.