CN117289951B - Software system multi-application automatic deployment method based on recursion principle - Google Patents
Software system multi-application automatic deployment method based on recursion principle Download PDFInfo
- Publication number
- CN117289951B CN117289951B CN202311563276.6A CN202311563276A CN117289951B CN 117289951 B CN117289951 B CN 117289951B CN 202311563276 A CN202311563276 A CN 202311563276A CN 117289951 B CN117289951 B CN 117289951B
- Authority
- CN
- China
- Prior art keywords
- application
- list
- deployed
- applications
- judging whether
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 230000007717 exclusion Effects 0.000 claims abstract description 24
- 238000012216 screening Methods 0.000 claims abstract description 15
- 230000001419 dependent effect Effects 0.000 claims description 38
- 238000004458 analytical method Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 abstract description 9
- 230000008878 coupling Effects 0.000 abstract description 5
- 238000010168 coupling process Methods 0.000 abstract description 5
- 238000005859 coupling reaction Methods 0.000 abstract description 5
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 9
- 238000013461 design Methods 0.000 description 6
- 238000009434 installation Methods 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a software system multi-application automatic deployment method based on a recursion principle, which comprises the following steps: establishing a system preset application list, a user-defined application list, attribute files corresponding to each application and a list to be deployed; traversing and analyzing all application attribute files corresponding to all applications in an application list in advance, traversing and analyzing all applications in a user-defined application list, performing mutual exclusion and dependency screening on the application attribute files, and adding the application which passes the mutual exclusion and dependency screening to a list to be deployed; and sequentially deploying the applications according to the list of the list to be deployed. The invention reduces the complexity of automatic deployment implementation, can adapt to and arrange the software system with complex arrangement and strong coupling between applications, and improves the application deployment expansibility by managing the processing mode of depending on resources through configuration files.
Description
Technical Field
The invention relates to the technical field of application deployment, in particular to a software system multi-application automatic deployment method based on a recursion principle.
Background
Along with the development and popularization of IT technology, the derived software system has more and more abundant business capability, dependence and mutual exclusion among applications and other relations provide customized requirements for system deployment, greatly increase the difficulty of automatic deployment and bring a plurality of challenges to the automatic deployment: there may be a need for multiple application consolidated deployment, where an application may depend on other applications, requiring co-usage for better ease of use, requiring simultaneous deployment of multiple applications. Certain applications may have mutually exclusive relationships and cannot be deployed at the same time. Multiple application deployment schemes exist in the same service, and an optimal deployment scheme needs to be automatically or manually selected according to requirements.
At present, some technical means for automatically deploying applications exist, and a method and a system for implementing automatic application deployment refer to a method and a system for implementing automatic application deployment in Chinese patent publication No. CN113778461A, wherein the method comprises the following steps: after receiving an application access request sent by an access person, the application automatic release platform receives an item management instruction sent by the access person if the access person has item management authority, adds an item and an application to be deployed, and sets the deployment environment of the application on a corresponding application deployment host; after receiving a deployment request sent by project management personnel, creating a work order, and submitting the work order to a work order auditing module for auditing; after receiving the command that the worksheet passes the audit, sending the application to an automatic deployment module; the automatic deployment module selects a deployment sub-module according to a deployment scheme, and deploys the application on a corresponding application deployment host based on a deployment command. The patent still needs manual participation in the application deployment process, and can not realize complete automatic deployment.
The invention relates to an integrated method and system for automatic installation and deployment of a java multi-service application, which refer to Chinese patent publication No. CN112732277B, and comprises the steps of dividing a java multi-service application system into a static file area, an operation area and a bat script file, configuring the built-in operation environment of a tomcat package corresponding to the version of each JDK package, configuring parameters of the app application package in the service configuration file, binding the app application package and the tomcat package and preparing the operation environment of the content in the static file area by writing and adding a sub-bat script file in the bat script file, and finally packaging the static file area and the files in the bat script file to obtain an installation file required by automatic installation and deployment of the java multi-service application system. This patent also requires restrictions on the application type in application deployment, with certain limitations. The prior art has the problems that customized software development cannot meet the complex multi-application deployment scene of coupling, and the complexity is high, the upgrading is difficult, the compatibility is poor and the like. The customized code development is implemented aiming at the differentiated requirements, and the automatic deployment of the specific application set is realized, but the method has high coding complexity and no generality, needs to customize a deployment scheme for each set of system, even needs to redesign the method when the application requirements of extreme scenes change, and has obvious problems: when the software system is deployed, code processing is required to be carried out on abnormal scenes such as dependent components, conflicts and the like possibly existing in each application, the complexity is high, the applications are directly and tightly coupled, maintenance is not facilitated, and the iteration rate of the product is also affected. With the increase of service types and the upgrading of software, the application types are more and more, and each time an application is newly added, the automatic deployment code needs to be modified, and the introduction of new codes may affect the existing flow, so that the product stability is not facilitated.
Disclosure of Invention
The invention solves the problems that the customized software development in the prior art cannot meet the complex multi-application deployment scenario, has high complexity, difficult upgrading and poor compatibility, and provides the software system multi-application automatic deployment method based on the recursion principle, which reduces the complexity of automatic deployment implementation, can adapt and arrange the software system with complex combination and strong inter-application coupling, and improves the application deployment expansibility by configuring the file management dependent resource processing mode.
In order to achieve the above purpose, the following technical scheme is provided:
a software system multi-application automatic deployment method based on a recursion principle comprises the following steps:
s1, a system preset application list, a user-defined application list, attribute files corresponding to each application and a list to be deployed are established;
s2, traversing all the attribute files corresponding to all the applications in the preset application list of the analysis system, performing mutual exclusion and dependency screening on the attribute files, and adding the applications passing through the mutual exclusion and dependency screening to the list to be deployed;
s3, after traversing the preset application list of the system, traversing and analyzing all applications in the user-defined application list, judging whether the applications are added into the list to be deployed, traversing the next application if yes, analyzing the attribute files corresponding to the applications if no, performing mutual exclusion and dependency screening on the attribute files, and adding the applications which pass the mutual exclusion and the dependency screening into the list to be deployed;
s4, after traversing the user-defined application list, outputting a list to be deployed, and sequentially deploying the applications according to the list to be deployed.
Aiming at the problems that when a software system is deployed, code processing is required to be carried out on abnormal scenes such as dependent components, conflicts and the like possibly existing in each application, the complexity is high, each application is directly and tightly coupled, maintenance is not facilitated, and the iteration rate of a product is affected, the invention provides an automatic deployment scheme, a resource structure design which depends on mutual exclusion is introduced into an application configuration file, and universal code logic is realized through the structure design of the file configuration so as to solve the problem of automatic deployment of multiple applications in a complex service environment. Meanwhile, the relational automation processing of multi-application deployment improves the user experience, greatly reduces the coding complexity of automation realization, and improves the stability of software products and the iteration rate of the products. The invention can adapt to the scene with a large number of applications and complex coupling to realize automatic deployment through the recursion checking logic, and does not increase the complexity of the system due to the change of the number of applications or the relation.
Preferably, the system preset application list is an application list which must be installed when the system is deployed, and is decided by an administrator and a system developer; the user-defined application list is an application list to be deployed, which is configured according to user requirements during deployment or upgrading, and is ordered according to descending priority, and the attribute file records an application name, a dependent application list and a mutually exclusive application list.
The invention configures the attribute file for the application, introduces the dependent and mutually exclusive resource structure design in the attribute file, and can cover the current automatic deployment requirement. When the application is newly added, only the attribute files of the application configuration are needed to be newly added, the deployment relation of the application is independently managed, the code flow is not needed to be modified, and the influence on the supported functions is small. According to the three types of configuration files, the file structure is analyzed during automatic deployment, and finally an installable application list, namely an application list to be deployed, can be generated, so that the installation can be sequentially executed according to the sequence. The output result ensures the priority of application deployment, eliminates mutual exclusivity, and does not cause deployment failure caused by lack of dependence and mutual exclusion.
Preferably, depending on the application means that the application should be pre-installed before the current application is deployed, the deployment sequence is superior to that of the current application, and the mutually exclusive application is an application which cannot be deployed simultaneously with the current application.
Preferably, the step S2 specifically includes the following steps:
s201, sequentially traversing all applications in a preset application list of the system, judging whether the traversal is finished, if so, carrying out S3, and if not, carrying out S202;
s202, analyzing an application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s203, judging whether a mutually exclusive application exists, if not, carrying out S204, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S201, and if not, carrying out S204;
s204, judging whether a dependent application exists, if not, performing S206; if yes, S205 is performed;
s205, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, performing S206, if not, finding out the attribute file of the dependent application, and then performing S202;
s206, adding the current application to the list of the list to be deployed, and returning to S201.
Preferably, the step S3 specifically includes the following steps:
s301, traversing all applications in the user-defined application list in sequence, judging whether traversing is finished, if yes, carrying out S4, and if not, carrying out S302;
s302, judging whether the current application is added to the list of the list to be deployed, if so, traversing the next application, returning to S301, and if not, carrying out S303;
s303, analyzing the application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s304, judging whether a mutually exclusive application exists, if not, carrying out S305, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S301, and if not, carrying out S305;
s305, judging whether a dependent application exists, if not, executing S307; if yes, S306 is performed;
s306, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, executing S307, if not, finding out the attribute file of the dependent application, and executing S303;
s307, adding the current application to the list of the list to be deployed, and returning to S301.
Preferably, the system presets that the application list stores applications without mutual exclusion relation.
The beneficial effects of the invention are as follows:
1. the method has the advantages that a general automatic deployment implementation scheme for multi-application installation of the system is provided, and complexity of automatic deployment implementation is reduced;
2. the automatic processing of the relation among the applications deployed by various applications can improve the customer experience;
3. the processing mode of depending application is managed through configuration attribute files, so that the application deployment expansibility is improved;
4. the influence of newly introduced deployment application on the existing flow is reduced, the reliability and stability of the product are enhanced, and the method is beneficial to accelerating the software iteration rate.
Drawings
FIG. 1 is a method flow diagram of an embodiment;
FIG. 2 is a schematic diagram of an embodiment property file.
Detailed Description
Examples:
the embodiment provides a software system multi-application automatic deployment method based on a recursion principle, and referring to fig. 1, the method comprises the following steps:
s1, a system preset application list, a user-defined application list, attribute files corresponding to each application and a list to be deployed are established; the system preset application list is an application list which must be installed when the system is deployed, and is determined by an administrator and a system developer; the user-defined application list is an application list to be deployed, which is configured according to user requirements when the user-defined application list is deployed or updated, and is ordered according to descending priority, and the attribute file is recorded with an application name, a dependent application list and a mutually exclusive application list.
Referring to fig. 2, in the present embodiment:
the system preset application list is in list format, is an application list which must be installed when the system is deployed, is decided by an administrator and a system developer, and does not need users to participate in decision:
sys_default_apps:[app1,app2];
the user-defined application list is in list format, and the list of the application list to be deployed is configured according to the user requirements during deployment or upgrading, and is ordered according to descending priority.
user_define_apps:[app3,app4,app5];
The attribute files of each application configuration are json format, k-v is stored, the name of the corresponding application is recorded and globally unique, and the dependency of the application list and the exclusive application list are recorded. The dependent application represents an application which is pre-installed before the application is deployed, the deployment sequence is superior to that of the application, and the mutually exclusive application cannot be deployed simultaneously with the application. In general, there is no mutual exclusion relationship between the system preset application lists, and the system preset application is deployed prior to the user-defined application. Referring to fig. 2, a property file of one of the applications includes the following:
name: app3
dependency:app1、app4
exclusion:app5。
this application name is indicated as app3, the dependent applications are app1, app4, and the mutually exclusive application is app5.
Before S2, the to-be-deployed application list confim_list needs to be initialized, so that the to-be-deployed application list confim_list is ensured to be empty.
S2, traversing all the attribute files corresponding to all the applications in the preset application list of the analysis system, performing mutual exclusion and dependency screening on the attribute files, and adding the applications passing through the mutual exclusion and dependency screening to the list to be deployed; s2 specifically comprises the following steps:
s201, sequentially traversing all applications in a preset application list of the system, judging whether the traversal is finished, if so, carrying out S3, and if not, carrying out S202;
s202, analyzing an application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s203, judging whether a mutually exclusive application exists, if not, carrying out S204, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S201, and if not, carrying out S204;
s204, judging whether a dependent application exists, if not, performing S206; if yes, S205 is performed;
s205, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, performing S206, if not, finding out the attribute file of the dependent application, and then performing S202;
s206, adding the current application to the list of the list to be deployed, and returning to S201.
Referring to fig. 2, what is traversed is app1 and app2, where app1 and app2 can be sequentially input to a list to be deployed according to a traversing sequence through mutual exclusion and dependency screening, and at this time, the list to be deployed stores app1 and app2.
S3, after traversing the preset application list of the system, traversing and analyzing all applications in the user-defined application list, judging whether the applications are added into the list to be deployed, traversing the next application if yes, analyzing the attribute files corresponding to the applications if no, performing mutual exclusion and dependency screening on the attribute files, and adding the applications which pass the mutual exclusion and the dependency screening into the list to be deployed; s3 specifically comprises the following steps:
s301, traversing all applications in the user-defined application list in sequence, judging whether traversing is finished, if yes, carrying out S4, and if not, carrying out S302;
s302, judging whether the current application is added to the list of the list to be deployed, if so, traversing the next application, returning to S301, and if not, carrying out S303;
s303, analyzing the application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s304, judging whether a mutually exclusive application exists, if not, carrying out S305, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S301, and if not, carrying out S305;
s305, judging whether a dependent application exists, if not, executing S307; if yes, S306 is performed;
s306, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, executing S307, if not, finding out the attribute file of the dependent application, and executing S303;
s307, adding the current application to the list of the list to be deployed, and returning to S301.
Referring to fig. 2, app3 is traversed first, the dependent applications of app3 are found as app1 and app4, at this time app1 is already in the list of to-be-deployed lists, so that it is also necessary to find out the attribute file of app4 preferentially for interpretation, app4 is app2 and has no exclusive application, app2 is already in the list of to-be-deployed lists, so app4 is preferentially deployed with app3 in the list of to-be-deployed lists, app3 also satisfies the deployment condition after app4 is deployed, app3 is deployed in the list of to-be-deployed lists again, app5 is traversed again, and app2 is present as exclusive application app5, so that an alarm log is issued when app5 is traversed, and cannot be deployed, and finally the finally output list of to-be-deployed lists are app1, app2, app4, app3.
S4, after traversing the user-defined application list, outputting a list to be deployed, and sequentially deploying the applications according to the list to be deployed.
Aiming at the problems that when a software system is deployed, code processing is required to be carried out on abnormal scenes such as dependent components, conflicts and the like possibly existing in each application, the complexity is high, each application is directly and tightly coupled, maintenance is not facilitated, and the iteration rate of a product is affected, the invention provides an automatic deployment scheme, a resource structure design which depends on mutual exclusion is introduced into an application configuration file, and universal code logic is realized through the structure design of the file configuration so as to solve the problem of automatic deployment of multiple applications in a complex service environment. Meanwhile, the relational automation processing of multi-application deployment improves the user experience, greatly reduces the coding complexity of automation realization, and improves the stability of software products and the iteration rate of the products. The invention can adapt to the scene with a large number of applications and complex coupling to realize automatic deployment through the recursion checking logic, and does not increase the complexity of the system due to the change of the number of applications or the relation.
The invention configures the attribute file for the application, introduces the dependent and mutually exclusive resource structure design in the attribute file, and can cover the current automatic deployment requirement. When the application is newly added, only the attribute files of the application configuration are needed to be newly added, the deployment relation of the application is independently managed, the code flow is not needed to be modified, and the influence on the supported functions is small. According to the three types of configuration files, the file structure is analyzed during automatic deployment, and finally an installable application list, namely an application list to be deployed, can be generated, so that the installation can be sequentially executed according to the sequence. The output result ensures the priority of application deployment, eliminates mutual exclusivity, and does not cause deployment failure caused by lack of dependence and mutual exclusion.
Claims (6)
1. A software system multi-application automatic deployment method based on a recursion principle is characterized by comprising the following steps:
s1, a system preset application list, a user-defined application list, attribute files corresponding to each application and a list to be deployed are established; the system preset application list is an application list which is required to be installed when the system is deployed, and the user-defined application list is an application list to be deployed which is configured according to user requirements;
s2, traversing all the attribute files corresponding to all the applications in the preset application list of the analysis system, performing mutual exclusion and dependency screening on the attribute files, and adding the applications passing through the mutual exclusion and dependency screening to the list to be deployed; the dependent application represents an application which is pre-installed before the current application is deployed, and the mutually exclusive application is an application which cannot be deployed simultaneously with the current application;
s3, after traversing the preset application list of the system, traversing and analyzing all applications in the user-defined application list, judging whether the applications are added into the list to be deployed, traversing the next application if yes, analyzing the attribute files corresponding to the applications if no, performing mutual exclusion and dependency screening on the attribute files, and adding the applications which pass the mutual exclusion and the dependency screening into the list to be deployed;
s4, after traversing the user-defined application list, outputting a list to be deployed, and sequentially deploying the applications according to the list to be deployed.
2. The method for automatically deploying multiple applications of a software system based on a recursion principle as set forth in claim 1, wherein the system preset application list is an application list which must be installed when the system is deployed, and is determined by an administrator and a system developer; the user-defined application list is an application list to be deployed, which is configured according to user requirements during deployment or upgrading, and is ordered according to descending priority, and the attribute file records an application name, a dependent application list and a mutually exclusive application list.
3. The method for automatically deploying multiple applications in a software system based on a recursion principle according to claim 2, wherein the dependent applications represent applications which should be pre-installed before deploying the current application, the deployment order is superior to the current application, and the mutually exclusive applications are applications which cannot be deployed simultaneously with the current application.
4. The method for automatically deploying multiple applications of a software system based on a recursion principle according to claim 2, wherein the step S2 specifically comprises the following steps:
s201, sequentially traversing all applications in a preset application list of the system, judging whether the traversal is finished, if so, carrying out S3, and if not, carrying out S202;
s202, analyzing an application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s203, judging whether a mutually exclusive application exists, if not, carrying out S204, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S201, and if not, carrying out S204;
s204, judging whether a dependent application exists, if not, performing S206; if yes, S205 is performed;
s205, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, performing S206, if not, finding out the attribute file of the dependent application, and then performing S202;
s206, adding the current application to the list of the list to be deployed, and returning to S201.
5. The method for automatically deploying multiple applications of a software system based on a recursive principle according to claim 2, wherein the step S3 specifically comprises the following steps:
s301, traversing all applications in the user-defined application list in sequence, judging whether traversing is finished, if yes, carrying out S4, and if not, carrying out S302;
s302, judging whether the current application is added to the list of the list to be deployed, if so, traversing the next application, returning to S301, and if not, carrying out S303;
s303, analyzing the application attribute file to obtain an application name, a dependent application list and a mutually exclusive application list;
s304, judging whether a mutually exclusive application exists, if not, carrying out S305, if so, judging whether a list of to-be-deployed lists contains the mutually exclusive application of the current application, if so, sending out alarm information, returning to S301, and if not, carrying out S305;
s305, judging whether a dependent application exists, if not, executing S307; if yes, S306 is performed;
s306, judging whether the dependent application of the current application has a list of to-be-deployed lists, if so, executing S307, if not, finding out the attribute file of the dependent application, and executing S303;
s307, adding the current application to the list of the list to be deployed, and returning to S301.
6. The method for automatically deploying multiple applications of a software system based on a recursion principle according to claim 1 or 2, wherein the applications stored in the preset application list of the system have no mutual exclusion relation.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311563276.6A CN117289951B (en) | 2023-11-22 | 2023-11-22 | Software system multi-application automatic deployment method based on recursion principle |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311563276.6A CN117289951B (en) | 2023-11-22 | 2023-11-22 | Software system multi-application automatic deployment method based on recursion principle |
Publications (2)
Publication Number | Publication Date |
---|---|
CN117289951A CN117289951A (en) | 2023-12-26 |
CN117289951B true CN117289951B (en) | 2024-04-02 |
Family
ID=89257487
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202311563276.6A Active CN117289951B (en) | 2023-11-22 | 2023-11-22 | Software system multi-application automatic deployment method based on recursion principle |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117289951B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN118672637A (en) * | 2024-08-20 | 2024-09-20 | 紫光摩度教育科技有限公司 | Software application upgrading method and system |
Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1838068A (en) * | 2004-09-29 | 2006-09-27 | 微软公司 | Workflow association in a collaborative application |
CN1945530A (en) * | 2006-11-07 | 2007-04-11 | 中兴通讯股份有限公司 | Arranging system and method for module having dependence |
CN102404381A (en) * | 2011-09-02 | 2012-04-04 | 西安交通大学 | Software deployment system and deployment method based on workflow in cloud computing environment |
CN106469068A (en) * | 2015-08-14 | 2017-03-01 | 中国移动通信集团安徽有限公司 | The dispositions method of application program and system |
CN112637335A (en) * | 2020-12-22 | 2021-04-09 | 新华三大数据技术有限公司 | Main/standby mode service deployment method, device, equipment and storage medium |
CN113179329A (en) * | 2021-05-24 | 2021-07-27 | 深圳平安智汇企业信息管理有限公司 | Service distribution method and device, server and storage medium |
CN113867736A (en) * | 2021-09-03 | 2021-12-31 | 中国人民解放军军事科学院战争研究院 | Deployment scheme generation method and device |
CN114185557A (en) * | 2021-12-15 | 2022-03-15 | 中国电信股份有限公司 | Software product deployment method, device, medium and electronic equipment |
CN114237651A (en) * | 2021-12-24 | 2022-03-25 | 建信金融科技有限责任公司 | Installation method and device of cloud native application, electronic equipment and medium |
CN114237902A (en) * | 2021-12-21 | 2022-03-25 | 中国建设银行股份有限公司 | Service deployment method and device, electronic equipment and computer readable medium |
CN114356538A (en) * | 2020-10-12 | 2022-04-15 | 华为技术有限公司 | Model deployment method, device, equipment and computer readable storage medium |
WO2022127420A1 (en) * | 2020-12-18 | 2022-06-23 | 中兴通讯股份有限公司 | Service choreography and deployment method and system, network device, and storage medium |
CN115190010A (en) * | 2022-07-01 | 2022-10-14 | 北京友友天宇系统技术有限公司 | Distributed recommendation method and device based on software service dependency relationship |
CN115857958A (en) * | 2022-11-30 | 2023-03-28 | 西安大医集团股份有限公司 | Software deployment method based on cloud platform, computer equipment and readable storage medium |
CN116107596A (en) * | 2023-01-30 | 2023-05-12 | 深圳微众信用科技股份有限公司 | Automatic system deployment method and related device |
WO2023155819A1 (en) * | 2022-02-15 | 2023-08-24 | 浙江大华技术股份有限公司 | Application deployment method and system |
CN116662132A (en) * | 2023-05-05 | 2023-08-29 | 浙江大华技术股份有限公司 | Evaluation method, virtual deployment method, computer device, and storage medium |
CN116886696A (en) * | 2023-07-20 | 2023-10-13 | 杭州谐云科技有限公司 | Cloud edge collaboration-based application deployment method and system |
-
2023
- 2023-11-22 CN CN202311563276.6A patent/CN117289951B/en active Active
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1838068A (en) * | 2004-09-29 | 2006-09-27 | 微软公司 | Workflow association in a collaborative application |
CN1945530A (en) * | 2006-11-07 | 2007-04-11 | 中兴通讯股份有限公司 | Arranging system and method for module having dependence |
CN102404381A (en) * | 2011-09-02 | 2012-04-04 | 西安交通大学 | Software deployment system and deployment method based on workflow in cloud computing environment |
CN106469068A (en) * | 2015-08-14 | 2017-03-01 | 中国移动通信集团安徽有限公司 | The dispositions method of application program and system |
CN114356538A (en) * | 2020-10-12 | 2022-04-15 | 华为技术有限公司 | Model deployment method, device, equipment and computer readable storage medium |
WO2022127420A1 (en) * | 2020-12-18 | 2022-06-23 | 中兴通讯股份有限公司 | Service choreography and deployment method and system, network device, and storage medium |
CN112637335A (en) * | 2020-12-22 | 2021-04-09 | 新华三大数据技术有限公司 | Main/standby mode service deployment method, device, equipment and storage medium |
CN113179329A (en) * | 2021-05-24 | 2021-07-27 | 深圳平安智汇企业信息管理有限公司 | Service distribution method and device, server and storage medium |
CN113867736A (en) * | 2021-09-03 | 2021-12-31 | 中国人民解放军军事科学院战争研究院 | Deployment scheme generation method and device |
CN114185557A (en) * | 2021-12-15 | 2022-03-15 | 中国电信股份有限公司 | Software product deployment method, device, medium and electronic equipment |
CN114237902A (en) * | 2021-12-21 | 2022-03-25 | 中国建设银行股份有限公司 | Service deployment method and device, electronic equipment and computer readable medium |
CN114237651A (en) * | 2021-12-24 | 2022-03-25 | 建信金融科技有限责任公司 | Installation method and device of cloud native application, electronic equipment and medium |
WO2023155819A1 (en) * | 2022-02-15 | 2023-08-24 | 浙江大华技术股份有限公司 | Application deployment method and system |
CN115190010A (en) * | 2022-07-01 | 2022-10-14 | 北京友友天宇系统技术有限公司 | Distributed recommendation method and device based on software service dependency relationship |
CN115857958A (en) * | 2022-11-30 | 2023-03-28 | 西安大医集团股份有限公司 | Software deployment method based on cloud platform, computer equipment and readable storage medium |
CN116107596A (en) * | 2023-01-30 | 2023-05-12 | 深圳微众信用科技股份有限公司 | Automatic system deployment method and related device |
CN116662132A (en) * | 2023-05-05 | 2023-08-29 | 浙江大华技术股份有限公司 | Evaluation method, virtual deployment method, computer device, and storage medium |
CN116886696A (en) * | 2023-07-20 | 2023-10-13 | 杭州谐云科技有限公司 | Cloud edge collaboration-based application deployment method and system |
Non-Patent Citations (3)
Title |
---|
Pavel Shapkin.Automation of Configuration, Initialization and Deployment of Applications Based on an Algebraic Approach.Procedia Computer Science.2022,第213卷全文. * |
戴文博 ; 徐珞 ; 卫津逸 ; .面向军事信息系统的自动化软件部署算法.计算机与现代化.2020,(第01期),全文. * |
武少波 ; 苏浩 ; .分布式系统自动部署中的组件依赖配置.信息技术.2016,(第07期),全文. * |
Also Published As
Publication number | Publication date |
---|---|
CN117289951A (en) | 2023-12-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2777443C (en) | Automated enterprise software development | |
CN117289951B (en) | Software system multi-application automatic deployment method based on recursion principle | |
US8250458B2 (en) | Method, system, and software tool for emulating a portal application | |
US20060190579A1 (en) | Assisted command script template creation | |
CN111104106A (en) | Visual development method, system and medium for integrating business process and communication message | |
CN101645013A (en) | Plug-in type service management system and method of integrated service management platform | |
US20110161924A1 (en) | Call wizard for information management system (ims) applications | |
US20110258620A1 (en) | Method and Apparatus for Making a BPM Application Available to Multiple Tenants | |
CN115543546B (en) | Spring-based module hot deployment method and system | |
CN114115838A (en) | Data interaction method and system based on distributed components and cloud platform | |
CN114064213A (en) | Kubernets container environment-based rapid arranging service method and system | |
CN114995807A (en) | Configuration method and system of front-end multi-project framework | |
CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
CN113961570A (en) | Real-time acquisition method applied to MYSQL BINLog change data | |
CN116684243B (en) | Method and terminal for managing SCA component | |
CN105701406A (en) | Method of Android platform for running traditional payment application | |
CN113031964B (en) | Big data application management method, device, equipment and storage medium | |
CN114625384A (en) | Installation package generation method, installation device, equipment and storage medium | |
Blech | Towards a framework for behavioral specifications of osgi components | |
CN108694048A (en) | A kind of implementation method of batch issuing service | |
CN113721940A (en) | Software deployment method and device, electronic equipment and storage medium | |
CN108664235B (en) | Coal mine information system fusion construction method based on component warehouse | |
CN106897074B (en) | Data processing method and system for VR development platform | |
CN108491193A (en) | Eclipse RCP products construction method, device, terminal and medium | |
CN112615745B (en) | Method and system for accessing Internet of things card platform to upstream through parameter configuration |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |