Application Launch Sequence Automation via Dependency Parsing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual setting of application launch sequences in application deployment is inefficient and difficult to adapt to variable deployment and update requirements, especially due to the complexity of managing dependencies between various application software developed by different teams.
Innovation Solution
A method that automatically determines the launch sequence of application software by reading dependency relationships from a dependency description file, generating an application launch sequence chain, and sequentially launching applications based on this chain, utilizing an interface definition language to describe and parse dependencies, and updating the sequence in response to changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual setting of application launch sequence is used, then the launch sequence can be determined, but the efficiency is low and it is difficult to adapt to variable deployment and update requirements
Solution Approach 1:
The system automatically determines the launch sequence by reading dependency relationships from description files carried by each application and performing topological sorting, eliminating the need for manual configuration. The application package itself provides the dependency information needed for sequence determination, achieving self-service automation.
Solution Approach 2:
The patent changes the parameter from manually configured sequence to automatically generated sequence based on dependency relationships. By reading dependency description files and performing topological sorting algorithms, the system dynamically determines the optimal launch sequence according to actual dependency parameters rather than fixed manual settings.
2Ease of operation
If manual configuration of launch sequence is used, then the process is simple, but it requires significant human effort and time
Solution Approach 1:
The application package automatically carries its own dependency description file, which contains information about dependencies on other applications and system services. The system reads this information and automatically generates the launch sequence without requiring human operators to manually analyze and configure dependencies.
Solution Approach 2:
The dependency relationships are pre-recorded in description files during application packaging. When deployment occurs, the system directly reads these pre-prepared dependency information and performs automatic topological sorting to generate the launch sequence, eliminating the need for manual configuration at deployment time.
3Productivity
If automatic determination of launch sequence is implemented, then efficiency is improved, but the system complexity increases
Solution Approach 1:
The patent introduces an intermediary component that reads dependency description files from application packages and performs topological sorting to generate launch sequences. This intermediary automation layer handles the complexity of dependency analysis, while the overall system maintains simplicity through standardized file formats and automatic processing.
Data Source
AI summary
A method, an apparatus, an electronic device, and a storage medium for application launch. The method includes: reading a dependency relationship of each application in a plurality of applications from a dependency description file carried by each application; generating an application launch sequence chain according to the dependency relationship; and sequentially launching the plurality of applications according to the application launch sequence chain.


