Virtualized Application Launcher Dependency Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Deploying virtualized applications in large enterprise environments is cumbersome and resource-intensive due to the need for complex dependency management and compatibility with varying client machine configurations.
Innovation Solution
A method and system for deploying virtualized applications that involves a launcher and an apploader, which check for and install dependencies such as the .NET framework, determine client device configurations, and download appropriate virtualized application components, allowing virtualized applications to run on both 32-bit and 64-bit machines with specific runtime requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If virtualized applications are deployed across diverse client devices with varying configurations, then adaptability is improved, but device complexity increases due to dependency management
Solution Approach 1:
The launcher checks for and installs required dependencies (such as the .NET framework) before the virtualized application is deployed. This preliminary action ensures that all necessary components are in place beforehand, eliminating the need for complex runtime dependency management and simplifying the deployment process across diverse client devices.
Solution Approach 2:
The launcher acts as an intermediary between the deployment system and the client device. It mediates the dependency management process by automatically checking for, downloading, and installing required components before the virtualized application is deployed, thereby reducing the complexity of direct dependency management between the application and diverse client configurations.
2Reliability
If comprehensive dependency checking and installation is performed, then reliability is improved, but use of energy increases due to additional downloads and processing
Solution Approach 1:
The launcher performs dependency checking and installation only when necessary - specifically checking for the presence of required dependencies like the .NET framework and installing them only if they are missing. This partial action approach ensures deployment reliability by addressing only the actual gaps in the client environment, rather than performing exhaustive checks and installations in all cases, thereby reducing unnecessary resource consumption.
3Manufacturing precision
If configuration-specific components are downloaded, then manufacturing precision is improved, but loss of time increases due to configuration determination and selective downloading
Solution Approach 1:
The launcher determines the client device configuration (32-bit or 64-bit) and downloads the appropriate virtualized application components in advance. This preliminary action ensures that the correct configuration-specific components are prepared before the main deployment process, improving component compatibility accuracy while minimizing deployment time by avoiding post-installation adjustments.
Data Source
AI summary
Methods and systems for deploying virtualized applications are disclosed. In an embodiment, a method involves, at a client device, downloading a launcher from a virtualized application portal to the client device, running the launcher at the client device, wherein running the launcher comprises checking for a first dependency and downloading a file of the first dependency if the first dependency is not installed on the client device, after checking for the first dependency, downloading an apploader from the virtualized application portal, and running the apploader at the client device. Running the apploader involves determining a configuration of the client device and downloading virtualized application components dependent on the configuration, determining specific needs of the virtualized application and downloading components dependent on the specific needs, and starting the virtualized application on the client device.