Application non-intrusive management method based on autonomous unified deployment unit

Abstract

The invention discloses an application non-intrusive management method based on an autonomous unified deployment unit, and relates to the technical field of enterprise application management systems. Aiming at the problems of high invasiveness, poor compatibility, limited technical model selection, insufficient heterogeneous environment adaptation and the like caused by strong coupling of management capability and business application in the existing scheme, the method comprises the following steps of: building an autonomous unified deployment unit with self-description and self-maintenance capabilities by externally hanging archive files and operation and maintenance scripts for application programs; according to the invention, the application can obtain a standardized and plug-and-play management capability without modifying a code or binding a specific framework, a management plane and an application program are effectively decoupled, and'zero-intrusive and non-perceptual 'application unified management is realized.

Description

Technical Field

[0001] This invention relates to the technical field of application management systems, and in particular to a method for non-intrusive unified management of applications based on an autonomous unified deployment unit. Background Technology

[0002] Currently, application management systems primarily rely on two technical approaches to achieve unified application management: The first is application code modification, which requires applications to embed specific management SDKs or agents, supporting standardized management functions through code-level adaptation. This approach has significant invasiveness issues—not only does it require modifying application source code, increasing development and maintenance costs, but it also leads to deep coupling between management logic and business logic, resulting in complex adaptation work when upgrading the management platform. More importantly, this approach is incompatible with legacy systems and third-party closed-source applications, severely restricting the expansion of management scope. The second approach relies on framework-specific management solutions, such as those based on containerization technology (Docker) or PaaS platforms. While these solutions provide a certain degree of standardized management capabilities, they force applications to adapt to specific technology stacks (such as Kubernetes YAML description files), causing enterprises to lose autonomy in technology selection. Furthermore, these solutions cannot effectively manage traditional non-containerized applications, and their performance is particularly poor in heterogeneous environments such as hybrid clouds.

[0003] The core problem with traditional technology approaches lies in the "strong coupling between management capabilities and business applications"—whether it's code modification or framework dependency, both severely restrict the flexibility and universality of application management systems. Especially in the context of digital transformation, enterprise IT environments often contain both cloud-native applications and traditional applications, making it difficult for existing solutions to achieve true "plug-and-play" management, which seriously affects IT governance efficiency.

[0004] To address the problems of traditional technical approaches, this solution proposes a non-intrusive application management method based on an autonomous unified deployment unit. This method constructs an autonomous unified deployment unit with self-describing and self-maintaining capabilities by attaching external archive files and operation and maintenance scripts to applications. This allows applications to quickly obtain standardized, plug-and-play management capabilities without modifying any code or binding to specific frameworks, effectively decoupling the management plane from applications and achieving "zero-intrusion, seamless" unified application management.

[0005] The core inventive point of this invention is: (1) External management architecture: Management capabilities are built through archive files and operation and maintenance scripts independent of the application, achieving physical separation from the application logic.

[0006] (2) Autonomous unified deployment unit: Package the application and its plug-in management files into an autonomous unified deployment unit with self-description and self-maintenance.

[0007] (3) Non-intrusive application management method: Applications can quickly obtain standardized management capabilities without modifying application code or binding to a specific framework, which is suitable for traditional software such as flight simulators to cloud scenarios. Summary of the Invention

[0008] Purpose of the Invention: Traditional flight simulator software technology is highly mature, but application modification is complex, and most applications are non-containerized. In the scenario of migrating flight simulator software to the cloud, existing application management solutions struggle to achieve true "plug-and-play" management, severely impacting the governance efficiency of cloud applications. Therefore, there is an urgent need for a technical solution that allows simulator applications to quickly acquire standardized management capabilities without modifying application code or being bound to a specific framework, thereby overcoming the current technical bottlenecks in the field of cloud simulator application management.

[0009] To meet the management needs of cloud simulator applications, this invention constructs an autonomous unified deployment unit with self-description and self-maintenance capabilities by adding external archive files and operation and maintenance scripts to flight simulator applications. This allows traditional flight simulator software to quickly obtain standardized, plug-and-play management capabilities without modifying any code or binding to a specific framework, achieving "zero-intrusion and seamless" unified management of cloud simulator applications.

[0010] Technical solution of the present invention: This invention proposes 1. a non-intrusive application management method based on an autonomous unified deployment unit, comprising the following steps: Step 1: Obtain the application to be managed; Step 2: Generate the application file: Obtain application information and generate the application file based on the application information; Step 3: Generate application maintenance scripts: Obtain script commands for installing, uninstalling, starting, and shutting down the application, and generate application maintenance scripts based on the script commands; Step 4: Build a unified deployment unit: Package the application, application archive files, and application operation and maintenance scripts into an autonomous unified deployment unit; Step 5: Deploy the application: Deploy the unified deployment unit to the target computer; Step 6: Dynamically locate the application deployment path: Determine the application's deployment path by finding the storage path of the archive file on the target computer; Step 7: Parse application information: Obtain application information by reading and parsing the archive file; Step 8: Monitor application running status: Determine the application running status by detecting whether there are running processes under the application deployment path; Step 9: Perform application maintenance operations: Install, uninstall, start, and shut down the application by calling the maintenance script.

[0011] 2. Step 1, obtaining the application to be managed, specifically involves: obtaining the original application to be managed without modifying the code or adjusting the function of the application during the process. The acquisition methods include receiving the application file uploaded by the user, importing the application from a specified storage location, or obtaining the application through network protocol transmission.

[0012] 3. Step 2 generates an external application archive file, specifically: obtaining application information and generating a structured application archive file based on the application information; the application archive file adopts a fixed naming rule, supports XML, JSON or custom markup language structured formats, and its content is encrypted to prevent tampering, serving as an independent description carrier for the application and attached outside the application program.

[0013] 4. Step 3 generates an external application maintenance script, specifically: obtaining script commands for application installation, uninstallation, startup, and shutdown operations, and generating an executable application maintenance script based on the commands; the application maintenance script adopts a fixed naming rule, supports explicit execution, silent execution, synchronous execution, and asynchronous execution modes, and its content is encrypted to ensure security, serving as an independent maintenance carrier for the application, attached to the application program.

[0014] 5. Step 4, which involves constructing a unified deployment unit, specifically involves placing the original application, the plug-in application archive files, and the plug-in application operation and maintenance scripts in the same root directory, and encapsulating them into a single file package using a unified encryption and compression algorithm, thereby forming an autonomous unified deployment unit with self-description and self-maintenance capabilities.

[0015] 6. Step 5, deploying the application, specifically involves: transmitting the autonomous unified deployment unit to the target computer, and after decompression, maintaining the same root directory hierarchy for the application, archive files, and operation and maintenance scripts.

[0016] 7. Step 6, which involves dynamically locating the application deployment path, specifically involves: on the target computer, locating the storage path of the application archive file by searching for the file with a fixed naming rule, and using the directory association between the archive file and the application to deduce and determine the deployment path of the application.

[0017] 8. Step 7, parsing application information, specifically involves: decrypting the encrypted application file, reading the file content using a structured parsing method, and extracting the application name, version number, and self-description information.

[0018] 9. Step 8, monitoring the application running status, specifically involves: traversing the currently running processes of the operating system, and determining whether the application is running by matching the executable file path of the process with the application deployment path or its sub-paths.

[0019] 10. Step 9 involves performing maintenance operations, specifically: after decrypting the encrypted application maintenance script, calling the corresponding script according to management needs, and performing installation, uninstallation, startup, and shutdown operations in an explicit, silent, synchronous, or asynchronous manner.

[0020] The innovative aspects and advantages / effects of this invention This invention constructs an autonomous, unified deployment unit with self-describing and self-maintaining capabilities by adding external archive files and operation and maintenance scripts to applications, achieving truly "zero-intrusion, seamless" unified application management. This invention eliminates the need to modify application source code and the forced binding to specific technology frameworks, improving upon the intrusiveness, high cost, technology stack lock-in, and poor compatibility with legacy / heterogeneous systems inherent in traditional solutions. This invention is particularly suitable for cloud migration scenarios of traditional non-containerized applications, closed-source applications, and other traditional IT applications, solving their core pain point of difficulty in modifying or adapting to containerized frameworks. It enables these applications to quickly integrate into the cloud environment without any internal changes, improving cloud application governance efficiency and accelerating the smooth migration of overall IT applications to the cloud. Attached Figure Description

[0021] Figure 1 This is an application management system for the simulation field.

[0022] Figure 2 This is a unified deployment unit for applications.

[0023] Figure 3 For data interaction between management terminals, management servers, and target computers. Detailed Implementation

[0024] The following example, an application management system for the simulation field, illustrates the specific implementation of this solution.

[0025] This system (see) Figure 1 It consists of two parts: central management control software and node agent software. The central management control software adopts a B / S architecture for unified storage and application management; its server is deployed on the management server, and the client browser is deployed on the management terminal. The node agent software is deployed on each target computer and is responsible for the specific execution of path location, information parsing, status monitoring, and operation and maintenance of the applications deployed on that local machine.

[0026] Step 1: Obtain the application to be managed Administrators upload the original application to be managed (e.g., SimulationApp.exe) to the central control software server via a client browser on the management terminal. The central control software server is responsible for storing the original applications to be managed.

[0027] Step 2: Generate the plug-in application archive file Administrators input self-descriptive elements of the application through a client browser on the management terminal, including the application name, application description, version number, version description, vendor information, and required environment dependencies (such as specific library versions). The central control software server saves the input information as an application archive file in XML format. The archive file is uniformly named "fwt_aat.xml" and encrypted using the AES algorithm. The encrypted fwt_aat.xml file is stored in the same root directory as the original application file, serving as an independent descriptive carrier for the application.

[0028] Step 3: Generate the operation and maintenance script for the plug-in application Administrators use a client browser on the management terminal to enter script commands for installing, uninstalling, starting, and shutting down applications. Administrators need to provide the appropriate commands based on the target computer's operating system type (supporting cross-platform command types such as Windows batch files and Linux Shell). An example of a Windows script command is as follows: (1) Installation command: msiexec / i setup.msi / qn (2) Uninstall command: msiexec / x {GUID} / qn (3) Startup command: start SimulationApp.exe -config config.ini (4) Command to close: taskkill / IM SimulationApp.exe / F The central control software server will save the above commands as separate executable script files based on the operating system type. The naming conventions for Windows scripts are as follows: (1) Installation script: fwt_install.bat (2) Uninstallation script: fwt_uninstall.bat (3) Startup script: fwt_run.bat (4) Close the script: fwt_quit.bat All generated script files are encrypted using the AES encryption algorithm. The encrypted operation and maintenance script files are stored in the same root directory as the original application files, serving as an independent maintenance carrier for the application.

[0029] Step 4: Build a unified deployment unit The central control software server encrypts and compresses the original application (SimulationApp.exe), application archive file (fwt_aat.xml), and application operation and maintenance scripts (fwt_install.bat, fwt_uninstall.bat, fwt_run.bat, fwt_quit.bat) located in the same root directory into a zip file package. This zip file package is the autonomous unified deployment unit (see...). Figure 2 It has self-describing capabilities (archive files) and self-maintenance capabilities (operation and maintenance scripts).

[0030] Step 5: Deploy the application Administrators can send deployment instructions by selecting the application to be deployed, one or more target computers, and using a client browser on the management terminal.

[0031] The central control software server sends a deployment message to the node agent software on the specified target computer via the network. The message contains the shared directory path of the deployment unit on the management server (e.g., "share\SimulationApp").

[0032] After receiving the deployment message, the node agent software copies the deployment unit from the shared directory specified by the management server to the local directory of the target computer. In the local directory, it decrypts and decompresses the encrypted zip file package.

[0033] Step 6: Dynamically locate the application deployment path The node agent software on the target computer periodically performs search tasks, searching the local machine for the application archive file fwt_aat.xml. Whenever an fwt_aat.xml file is found, the node agent software can use the association between this archive file and the application being located at the same directory level to deduce that the directory containing this archive file is the deployment path of the corresponding application. The node agent software then reports all discovered application deployment path information to the central control software server via the network.

[0034] For example: If a file named fwt_aat.xml is found on the local machine, and the full path of the file is "D: / soft / SimulationApp / fwt_aat.xml", then the directory where the archive file is located, "D: / soft / SimulationApp", is the deployment path of the corresponding application.

[0035] Step 7: Parse application information The node agent software on the target computer periodically performs parsing tasks. For each encrypted fwt_aat.xml file in the application deployment path, it decrypts the raw XML content, parses it, and extracts information such as application name, application description, version number, and version description. The node agent software then reports all discovered application information to the central control software server over the network.

[0036] Step 8: Monitor application running status The node agent software on the target computer periodically performs runtime status monitoring tasks.

[0037] Get process list: Call the operating system API to traverse and get a list of all currently running processes and their detailed information, including the executable file path of each process.

[0038] Matching Path: For each application deployed by the node agent software that is known (discovered via step 6), its deployment path is used as the baseline path.

[0039] Status determination: Check the executable file path of each currently running process. If the path begins with the application's deployment path (i.e., it is located under the deployment path or its subdirectories), then the application is considered to have a running instance and is in a running state. If, after traversing all running processes, no process's executable file path is found to match the application's deployment path, then the application is considered to be in a non-running state.

[0040] For example, the application deployment path is "D: / soft / SimulationApp". If the executable file path of a running process begins with the application's deployment path (i.e., it is located under the deployment path or its subdirectories), such as "D: / soft / SimulationApp" or "D: / soft / SimulationApp / bin", then it is determined that the application has a running instance and is in a running state.

[0041] The node agent software reports the running status (running / not running) information of each application to the central control software server via the network.

[0042] Step 9: Perform application maintenance operations Administrators can view the information aggregated by the central control software server in real time through a client browser on the management terminal. This includes a list of target computers, a list of applications deployed on each target computer, detailed information about each application, and the real-time running status of each application.

[0043] Administrators can specify target computers and applications, select the maintenance operations to be performed: install, uninstall, start or shut down, and send operation instructions.

[0044] The central control software server sends maintenance messages to the node agent software on the specified target computer via the network. The messages contain the deployment path, operation type, and execution mode of the specified application (for example, the application deployment path is "D: / soft / SimulationApp", the operation type is "startup", and the execution mode is "silent").

[0045] After receiving the maintenance message, the node agent software selects the corresponding maintenance script under the specified application deployment path, decrypts the original script commands, and executes the script commands according to the specified mode. After the commands are executed, the node agent software collects the execution results and reports them to the central control software server via the network.

[0046] Administrators can view the results of operation and maintenance operations in real time through a client browser on the management terminal.

[0047] Data interaction between the management terminal, management server, and target computer is described in [link to documentation]. Figure 3 .

Claims

1. A non-intrusive application management method based on an autonomous unified deployment unit, characterized in that, Includes the following steps: Step 1: Obtain the applications to be managed; Step 2: Generate the application file: Obtain application information and generate the application file based on the application information; Step 3: Generate application maintenance scripts: Obtain script commands for installing, uninstalling, starting, and shutting down the application, and generate application maintenance scripts based on the script commands; Step 4: Build a unified deployment unit: Package the application, application archive files, and application operation and maintenance scripts into an autonomous unified deployment unit; Step 5: Deploy the application: Deploy the unified deployment unit to the target computer; Step 6: Dynamically locate the application deployment path: Determine the application's deployment path by finding the storage path of the archive file on the target computer; Step 7: Parse application information: Obtain application information by reading and parsing the archive file; Step 8: Monitor application running status: Determine the application running status by detecting whether there are running processes under the application deployment path; Step 9: Perform application maintenance operations: Install, uninstall, start, and shut down the application by calling the maintenance script.

2. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 1, obtaining the application to be managed, specifically involves: obtaining the original application to be managed without modifying the code or adjusting the function of the application during the process. The acquisition methods include receiving the application file uploaded by the user, importing the application from a specified storage location, or obtaining the application through network protocol transmission.

3. The application non-intrusive management method based on autonomous unified deployment units according to claim 1, characterized in that, Step 2, generating the external application archive file, specifically involves: obtaining application information and generating a structured application archive file based on the application information; the application archive file is named according to a fixed naming rule, supports XML, JSON, or custom markup language structured formats, and its content is encrypted to prevent tampering, serving as an independent description carrier for the application and attached outside the application program.

4. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 3 generates an external application maintenance script, which specifically involves: obtaining script commands for application installation, uninstallation, startup, and shutdown operations, and generating an executable application maintenance script based on the commands; the application maintenance script is named according to a fixed naming rule, supports explicit execution, silent execution, synchronous execution, and asynchronous execution modes, and its content is encrypted to ensure security, serving as an independent maintenance carrier for the application outside of the application program.

5. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 4, constructing a unified deployment unit, specifically involves placing the original application, plug-in application archive files, and plug-in application operation and maintenance scripts in the same root directory, and encapsulating them into a single file package using a unified encryption and compression algorithm, thus forming an autonomous unified deployment unit with self-description and self-maintenance capabilities.

6. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 5, deploying the application, specifically involves: transmitting the autonomous unified deployment unit to the target computer, and after decompression, maintaining the same root directory hierarchy for the application, archive files, and operation and maintenance scripts.

7. The application non-intrusive management method based on autonomous unified deployment units according to claim 1, characterized in that, Step 6, dynamically locating the application deployment path, specifically involves: on the target computer, locating the storage path of the application archive file by searching for the file with a fixed naming rule, and using the directory association between the archive file and the application to deduce and determine the deployment path of the application.

8. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 7, parsing the application information, specifically involves: decrypting the encrypted application file, reading the file content using a structured parsing method, and extracting the application name, version number, and self-descriptive information.

9. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 8, monitoring the application's running status, specifically involves: traversing the currently running processes of the operating system, and determining whether the application is running by matching the executable file path of the process with the application deployment path or its sub-paths.

10. The application non-intrusive management method based on an autonomous unified deployment unit according to claim 1, characterized in that, Step 9 involves performing maintenance operations, specifically: after decrypting the encrypted application maintenance script, calling the corresponding script according to management needs, and performing installation, uninstallation, startup, and shutdown operations in explicit, silent, synchronous, or asynchronous manner.

Images