CN102609281A - Distributed software patch updating method and distributed software patch updating system - Google Patents
Distributed software patch updating method and distributed software patch updating system Download PDFInfo
- Publication number
- CN102609281A CN102609281A CN2012100152185A CN201210015218A CN102609281A CN 102609281 A CN102609281 A CN 102609281A CN 2012100152185 A CN2012100152185 A CN 2012100152185A CN 201210015218 A CN201210015218 A CN 201210015218A CN 102609281 A CN102609281 A CN 102609281A
- Authority
- CN
- China
- Prior art keywords
- patch
- program
- file
- server
- destination application
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a distributed software patch updating method and a distributed software patch updating system. The distributed software patch updating method includes that a patch management server transmits a first program patch file to a first target application server, remotely controls the first target application server to execute the first program patch file to update patches of a first program module and further transmits a data patch file to a database server, a database system of the distributed software is installed on the database server, and the database server updates patches of the database system according to the data patch file. Since the patch management server initiatively propels the program patch file and the data patch file of the distributed software to the target application server and the database server during patch updating of the distributed software, updating of the program module on the target application server and updating of the database system on the database server can be realized simultaneously, and upgrading and fixing of the distributed software can be realized.
Description
Technical field
The present invention relates to computer communication technology, relate in particular to and a kind of distributed software is carried out patch method for updating and system.
Background technology
How comprehensively software is in order to realize some function, by the set of people institute written program code, no matter considers, deficiency, carelessness or wrong (Bug) are always arranged.In order to remedy the deficiency of original program, correct mistakes enhancement function; Perhaps improve many reasons such as security, can issue the small routine of this leak of special solution or safety problem usually to certain leak of software or safety problem, this small routine is called as the Hotfix of this software; Be also referred to as the patch of this software, and most of software all can there be patch, need carries out patch and upgrade; Also claim patch installing, the process of patch installing is software upgrade process.
At present, the automatic renewal technology of patch mainly is to carry out patch to client software (for example operating system or tool software etc.) to upgrade: the software by being deployed on the client computer upgrades to long-range patch server request patch; After long-range patch server receives request, send patch update package file to the software that sends the client computer of asking; The software of client computer is carried out patch and is upgraded operation after receiving the patch update package file that long-range patch server sends, thus accomplish long-range, upgrade patch automatically.
Along with the infotech fast development, E-Government is used deep day by day, and the infosystem of each entity is huge day by day, and based on multi-layer framework, the software of To enterprises, distributed deployment has obtained using widely.Distributed software system (Distributed Software Systems) is software systems of supporting distributed treatment, is the system that on the multiprocessor architecture interconnected by communication network, executes the task.It comprises distributed operating system, distributed program design language and compiling thereof (explanation) system, distributed file system and distributed data base system etc.A distributed software is made up of several program modules that can independently carry out, and they are distributed on many computing machines of a distributed processing system(DPS) and are carried out simultaneously.For example; As shown in Figure 1; A program module (program module A) of a distributed software is installed in the application server 1, and another program module (program module B) of this distributed software is installed in the application server 2, and the Database Systems of distributed software then are installed in the database server.
If still adopt the patch renewal technology of prior art to upgrade for distributed software; Easy error then; And the patch upgrading process is difficult to management: for example; When being installed in distributed software in the system shown in Figure 1 and needing patch installing to carry out software upgrading, application server 1 upgrades to patch server request patch, the renewal of execution of program modules A after obtaining patch.But; Software for distributed deployment; Program module A in needing application server 1 carries out the patch renewal, also needs the program module B in the application server 2 to carry out the patch renewal, and need the Database Systems of database server be carried out modify.For example, need increase or delete some field to certain tables of data in the database.And prior art can't guarantee that the program module A of application server 1 has carried out after patch upgrades, and the program module B in the application server 2 can in time carry out patch to be upgraded, and more can't carry out automatic modify to database data in server storehouse system.
Inventor of the present invention finds; Adopt the patch update method of prior art, to carry out that patch upgrades be effectively for being installed in a client software on the processor, and for the distributed software that is installed on a plurality of processors; Because neither one upgrades management system to the unified patch of program module on the multiprocessor and Database Systems; Then easy error, and patch upgrading process is difficult to management, also just can't reach the purpose of distributed software being carried out auto-update, Hotfix.
Summary of the invention
The embodiment of the invention provides a kind of distributed software patch update method and system, in order to realize upgrading, the repairing of distributed software.
According to an aspect of the present invention, a kind of distributed software patch update method is provided, has comprised:
The patch management server sends the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch management server sends patch data file, the Database Systems that said distributed software has been installed on the said database server to database server;
Said database server carries out patch to said Database Systems and upgrades according to the database operating instruction information of carrying in the said patch data file.
Wherein, before said Long-distance Control first destination application server is carried out the first program patch file, also comprise:
Said patch management server Long-distance Control first destination application server backs up first program module; And; If in the process of first program module that is installed in the said distributed software on first destination application server being carried out the patch renewal; Mistake appears; Then first destination application server returns the renewal failure information to said patch management server, and after said patch management server received said renewal failure information, Long-distance Control first destination application server recovered according to first program module of backup.
Preferable, said patch management server sends the first program patch file to first destination application server and is specially:
Said patch management server sends the first program patch file according to the patch update strategy of said distributed software to first destination application server; And,
Said patch management server sends the patch data file to database server and is specially:
Said patch management server sends the patch data file according to the patch update strategy of said distributed software to database server;
Wherein, Said patch update strategy is predetermined, comprising: the first program patch file and pairing first destination application server of the first program patch file and said patch data file and the pairing database server of said patch data file; Wherein, the said patch data file and the first program patch file are the required file of the said distributed software of upgrading.
If said distributed software also comprises second program module that is installed on second destination application server, and the required file of said distributed software of upgrading also comprises the second program patch file, and then said method also comprises:
Said patch management server sends the second program patch file to second destination application server, and Long-distance Control second destination application server carries out the second program patch file, second program module is carried out patch upgrade.
Preferable, before said Long-distance Control second destination application server is carried out the second program patch file, also comprise: said patch management server Long-distance Control second destination application server backs up second program module.
Preferable, said patch management server sends the first program patch file to first destination application server and is specially:
Said patch management server sends the first program patch file according to the patch update strategy of said distributed software to first destination application server; And,
Said patch management server sends the patch data file to database server and is specially:
Said patch management server sends the patch data file according to the patch update strategy of said distributed software to database server; And,
Said patch management server sends the second program patch file to second destination application server and is specially:
Said patch management server sends the second program patch file according to the patch update strategy of said distributed software to second destination application server;
Wherein, Said patch update strategy is predetermined, comprising: the first program patch file and pairing first destination application server of the first program patch file, the second program patch file and pairing second destination application server of the second program patch file and said patch data file and the pairing database server of said patch data file; Wherein, said patch data file, the first program patch file and the second program patch file are the required file of the said distributed software of upgrading.
Particularly, said database operating instruction information comprises: database patch operation instruction information, database rollback operation command information; And,
Said according to the database operating instruction information of carrying in the said patch data file, said Database Systems are carried out the patch renewal specifically refer to:, said Database Systems are carried out patch upgrade according to said database patch operation instruction information; And,
If the patch of said Database Systems is upgraded failure, then said database server is according to said database rollback operation command information, said Database Systems returned to carry out the state of patch before upgrading.
According to another aspect of the present invention, a kind of distributed software patch update system is provided, has comprised: patch management server, first destination application server and database server;
The patch management server is used for sending the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch management server also is used for sending patch data file, the Database Systems that said distributed software has been installed on the said database server to said database server;
Said database server carries out patch to said Database Systems and upgrades according to the database operating instruction information of carrying in the said patch data file.
If said distributed software also comprises second program module that is installed on second destination application server, then said system also comprises: second destination application server;
Said patch management server also is used for sending the second program patch file to second destination application server, and Long-distance Control second destination application server carries out the second program patch file, second program module is carried out patch upgrade.
According to another aspect of the present invention, a kind of patch management server is provided also, has comprised:
Program patch management module; Be used for sending the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
The patch data administration module; Be used for sending the patch data file to database server; The Database Systems of said distributed software have been installed on the said database server; Carry database operating instruction information in the said patch data file, be used to indicate said database server that said Database Systems are carried out patch and upgrade.
Said server further can also comprise:
Patch update strategy module; Be used to generate the patch update strategy of said distributed software, said patch update strategy comprises: said distributed software carries out the required first program patch file and pairing first destination application server of the first program patch file, required patch data file and the pairing database server of this patch data file of said distributed software of upgrading of time, the said distributed software of upgrading that patch upgrades;
Dispatching management module; Be used for patch update strategy according to said patch update strategy module generation; Confirming that said distributed software carries out time that patch upgrades when arriving, and makes an announcement to said program patch management module and patch data administration module transmission patch; And,
Said program patch management module specifically is used for receiving after said patch makes an announcement; Patch update strategy according to said distributed software; First destination application server in said patch update strategy sends the first program patch file; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch data administration module specifically is used for receiving after said patch makes an announcement, and according to the patch update strategy of said distributed software, the database server in said patch update strategy sends said patch data file.
Preferable, said program patch management module also was used for before Long-distance Control first destination application server is carried out the first program patch file, controlled first destination application server and backed up said first program module; And said program patch management module also is used for if receive the renewal failure information that first destination application server returns, and then Long-distance Control first destination application server recovers according to first program module of backup.
If said distributed software also comprises second program module that is installed on second destination application server, and the required program patch file of the said distributed software of upgrading also comprises the second program patch file, then:
The patch update strategy of said distributed software also comprises: the second program patch file and pairing second destination application server of the second program patch file; And,
Said program patch management module also is used for receiving after said patch makes an announcement; Patch update strategy according to said distributed software; Also send the second program patch file to second destination application server; And Long-distance Control second destination application server carries out the second program patch file, second program module carried out patch upgrade.
Preferable; Said program patch management module also is used for the patch update strategy according to said distributed software, every backs up at a distance from setting-up time section Long-distance Control first destination application server that first program module, second destination application server back up second program module, said database server backs up said Database Systems.
According to another aspect of the present invention, a kind of database server is provided also, has comprised:
The file receiver module is used to receive the patch data file that the patch management server sends, and carries database operating instruction information in the said patch data file;
Parsing module is used for parsing database operating instruction information from said patch data file;
Execution module is used for according to the database operating instruction information and executing corresponding database operational order that parses, and the Database Systems that are installed in the said database server are carried out the patch renewal.
The embodiment of the invention is because in the patch renewal process of distributed software; Through the patch management server to destination application server and database server active push program patch file and patch data file; Can unify to realize program module on the destination application server is upgraded and database server on Database Systems upgrade, thereby realizing distributing is installed in the upgrading and the repairing of the distributed software on destination application server and the database server.Technical scheme through the embodiment of the invention can make things convenient for, realize effectively the automatic patch of distributed software is upgraded; Save the manpower and materials that expend in the patch renewal process of upgrading distributed software, improve the reliability that distributed software carries out the patch renewal process.
Description of drawings
Fig. 1 is that the software patch of prior art upgrades synoptic diagram;
Fig. 2 is the distributed software patch update system synoptic diagram of the embodiment of the invention;
Fig. 3 is the patch update method process flow diagram of the distributed software of the embodiment of the invention;
Fig. 4 is the patch update method process flow diagram of another distributed software of the embodiment of the invention;
Fig. 5 is the structured flowchart of the patch management server of the embodiment of the invention;
Fig. 6 is the structured flowchart of the database server of the embodiment of the invention.
Embodiment
Inventor of the present invention notices; For repairing, upgrading, the patch of realizing the distributed software program upgrades; Except need be to the program module patch installing of the software in a plurality of application servers; Also need solve the problem that the Database Systems in the database server are upgraded, revised, promptly also need be to the Database Systems patch installing.When carrying out the patch renewal for the program module that realizes application server; Also database is upgraded, revised; Main thought of the present invention is: the mode that the patch management server is taken the initiative and pushed; According to the demand that the distributed software patch upgrades, active is to the update routine (being called for short the program patch file among this paper) of application server router module; And, also send the update routine (being called for short the patch data file among this paper) of database to database server.After application server receives the program patch file, software application is carried out patch upgrade, realize modification, the upgrading of software application; After database server receives the patch data file, database is carried out corresponding modification or upgrading, thereby the complete patch of realizing distributed software upgrades, and reaches the purpose of distributed software upgrading, Hotfix.
Specify the technical scheme of the embodiment of the invention below in conjunction with accompanying drawing.In distributed software patch update system as shown in Figure 2, comprise patch management server 201 and a plurality of deployment node, each has disposed node deploy distributed software.Dispose node for one and can comprise database server 203 and a plurality of destination application servers 202; The program module of distributed software is installed in respectively on each destination application server of disposing node, and the Database Systems of distributed software are installed on the database server of disposing node.
Carry out patch and be updated to example and tell about specific embodiments to be deployed in the distributed software 1 of disposing node 1 below.In disposing node 1, the program module of distributed software 1 is installed in the destination application server 1, and the Database Systems of distributed software 1 are installed in the database server.201 pairs of patch management servers are deployed in the distributed software 1 of disposing node 1 and carry out the flow process that patch upgrades, and are as shown in Figure 3, comprise the steps:
S301: patch management server 201 sends the program patch file of distributed software 1 to the destination application server of disposing node 11.
A lot of equipment, server etc. all provide the interface of a kind of remote access and management.For example, the Windows server can utilize the Telnet agreement to carry out telemanagement, perhaps utilizes SSH (Secure Shell, Secure Shell) agreement to carry out long-range visit and management in the linux system.Patch management server 201 can carry out patch through Telnet agreement or SSH agreement controlled target application server 202 to be upgraded.Because the SSH agreement has higher security, therefore, preferable scheme is that patch management server 201 carries out patch through SSH agreement Long-distance Control destination application server 202 to be upgraded.
Patch management server 201 is following to the detailed process of the destination application server 1 router patch file of disposing node 1 according to the SSH agreement: patch management server 201 is disposed the destination application server 1 of node 1 according to user name, password, the address of the destination application server 1 of disposing node 1 through SSH agreement remote access login.After the login, patch management server 201 sends the program patch file of distributed software 1 to according to the SSH agreement destination application server 1 of deployment node 1.
S302: the program patch file that patch management server 201 Long-distance Control are disposed the destination application server 1 execution distributed software 1 of node 1, carry out patch to the program module that is installed in the destination application server 1 of disposing node 1 and upgrade.
After the destination application server 1 of deployment node 1 receives the program patch file of distributed software 1; Patch management server 201 sends order according to the SSH agreement to the destination application server of disposing node 11; Controlled target application server 1 executive routine patch file, thus completion is to the patch renewal of the program module of the destination application server 1 of deployment node 1.The destination application server 1 of disposing node 1 can also return to patch management server 201 after the patch of accomplishing program module upgrades and upgrade successful result.
S303: patch management server 201 is upgraded demand according to patch, sends the patch data file of distributed software 1 to the database server of disposing node 1.
Patch management server 201 is disposed the database server of node 1 according to user name, password, the address of the database server of disposing node 1 through SSH agreement remote access login.After the login, patch management server 201 sends the patch data file to the database server of disposing node 1 according to the SSH agreement.
S304: after the database server of deployment node 1 receives distributed software 1 patch data file, database is carried out the corresponding modification operation, the patch of fulfillment database system upgrades.
In the patch data file, carry database operating instruction information.Database operating instruction information can comprise: patch release number, SQL (Structured Query Language; SQL) action type, positive SQL operation (SQL script), contrary SQL operation (cancelling the SQL operation) etc.; Be used to indicate operation to the data storehouse; Such as newly-increased tables of data, to the tables of data new field, perhaps delete, change field in the tables of data etc.
After the database server of deployment node 1 receives the patch data file of patch management server transmission, from the patch data file, parse database operating instruction information.The database server of disposing node 1 can such as newly-increased tables of data, thereby carry out the patch renewal to the Database Systems that are installed in the database server of disposing node 1 according to database operating instruction information and executing corresponding database operational order.
Preferable, can comprise in the database operating instruction information of carrying in the patch data file: database patch operation instruction information, database rollback operation command information.The database patch operation instruction information comprises positive SQL operation (SQL script); In order to the referred database server Database Systems are carried out the operation of patch data updated storehouse; The database server of disposing node 1 carries out patch to Database Systems and upgrades according to the database patch operation instruction information.
Make mistakes in the patch renewal process if dispose the database server of node 1, the database server of then disposing node 1 can also be according to database rollback operation command information, Database Systems is returned to carry out the state of patch before upgrading.Comprise in the database rollback operation command information against SQL and operate (cancelling the SQL operation) that the database server of disposing node 1 through the inverse operation indication returns to Database Systems and carries out patch renewal state before.
The database server of disposing node 1 can also return to patch management server 201 after the patch of accomplishing Database Systems upgrades and upgrade successful result.
If distributed software has a plurality of program modules, be installed in respectively in a plurality of destination application servers, then in the patch renewal process, patch management server 201 need be to a plurality of destination application server active push program patch files.For example; Be deployed in the distributed software 2 of disposing node 2; Comprise two program modules and Database Systems: program module 1 is installed in the destination application server of disposing in the node 21; Program module 2 is installed in the destination application server of disposing in the node 22, and two program module data shared storehouse systems are installed in the database server of disposing in the node 2.201 pairs of patch management servers are deployed in the distributed software 2 of disposing node 2 and carry out the flow process that patch upgrades, and are as shown in Figure 4, comprise the steps:
S401: patch management server 201 sends the first program patch file of distributed software 2 to the destination application server of disposing node 21.
S402: patch management server 201 Long-distance Control are disposed the destination application server 1 of node 2 and are carried out the first program patch file, and first program module that is installed on the destination application server 1 of disposing node 2 is carried out the patch renewal.
S403: patch management server 201 sends the second program patch file of distributed software 2 to the destination application server of disposing node 22.
S404: patch management server 201 Long-distance Control are disposed the destination application server 2 of node 2 and are carried out the second program patch file, and second program module that is installed on the destination application server 2 of disposing node 2 is carried out the patch renewal.
S405: patch management server 201 sends the patch data file of distributed software 2 to the database server of disposing node 2.
S406: after the database server of deployment node 2 receives the patch data file, Database Systems are carried out the corresponding modification operation, the patch of fulfillment database system upgrades.
If distributed software comprises the program module more than 2; Be installed in respectively in a plurality of destination application servers; So; Patch management server 201 is to these destination application server active push program patch files, and it is identical with the method for above-mentioned introduction that the controlled target application server carries out the patch method for updating to program module.Those skilled in the art can upgrade according to the patch of the multiprogram module on the easy realization multiple goal of the technique scheme application server, repeat no more here.
In fact; In order to guarantee the patch reliability of updating of distributed software system; Patch management server 201 can also be at Long-distance Control destination application server 202 executive routine patch files; Program module is carried out before patch upgrades, and 202 pairs of program modules of controlled target application server back up.If destination application server 202 mistake occurs in the process of carrying out the patch renewal; Cause patch to upgrade failure; Then destination application server 202 returns the renewal failure information to patch management server 201; After patch management server 201 received and upgrades failure information, Long-distance Control destination application server 202 recovered according to the program module of backup.
For example; Distributed software 1 for above-mentioned deployment node 1; Patch management server 201 is disposed before the destination application server 1 executive routine patch file of node 1 in execution in step S302 Long-distance Control; Can control the destination application server 1 of disposing node 1 earlier, the program module that is installed in the destination application server 1 of disposing node 1 is backed up.So; In execution in step S302 process; If mistake causes patch to upgrade failure, the destination application server 1 of then disposing node 1 returns the renewal failure information to patch management server 201; After patch management server 201 received and upgrades failure information, the destination application server 1 that Long-distance Control is disposed node 1 recovered according to the program module of backup.
In like manner; Distributed software 2 for above-mentioned deployment node 2; Patch management server 201 is disposed before the destination application server 1 execution first program patch file of node 2 in execution in step S402 Long-distance Control; Can control the destination application server 1 of disposing node 2 earlier, first program module that is installed in the destination application server 1 of disposing node 2 is backed up; Patch management server 201 is disposed before the destination application server 2 execution second program patch file of node 2 in execution in step S404 Long-distance Control; Can control the destination application server 2 of disposing node 2 earlier, second program module that is installed in the destination application server 2 of disposing node 2 is backed up.
So, if in execution in step S402 process, mistake occurs; Cause patch to upgrade failure; The destination application server 1 of then disposing node 2 returns the renewal failure information to patch management server 201, and after patch management server 201 received and upgrades failure information, the destination application server 1 that Long-distance Control is disposed node 2 recovered according to first program module of backup; Can carry out patch afterwards again and upgrade, perhaps carry out other operation.
If in execution in step S404 process; Mistake occurs, cause patch to upgrade failure, the destination application server 2 of then disposing node 2 returns the renewal failure information to patch management server 201; After patch management server 201 receives and upgrades failure information; The destination application server 2 that Long-distance Control is disposed node 2 recovers according to second program module of backup, can carry out patch afterwards again and upgrade, and perhaps carries out other operation.
In practical application, the patch that patch management server 201 can be managed a plurality of deployment node distribution formula softwares upgrades.For convenient management; Patch management server 201 is upgraded demand according to the patch of this distributed software to each distributed software; Generate a patch update strategy, comprising: distributed software carries out the required program patch file of time, this distributed software of upgrading that patch upgrades and the pairing destination application server of program patch file, required patch data file and the pairing database server of this patch data file of this distributed software of upgrading.
For example; Patch management server 201 is to the distributed software 1 of above-mentioned deployment node 1; Upgrading distributed software 1 required file comprises program patch file and patch data file; Comprise according to the patch of the distributed software 1 patch update strategy that generates of upgrading demand: distributed software 1 carries out the required program patch file of time that patch upgrades, upgrading distributed software 1 and the destination application server 1 of the pairing deployment node 1 of this program patch file, the patch data file that upgrading distributed software 1 is required and the database server of the pairing deployment node 1 of this patch data file.
And for example; Patch management server 201 is to the distributed software 2 of above-mentioned deployment node 2; Upgrading distributed software 1 required file comprises the first program patch file, the second program patch file and patch data file, comprises according to the patch of the distributed software 2 patch update strategy that generates of upgrading demand: distributed software 2 carries out the required patch data file of the destination application server 2, upgrading distributed software 2 of second required program patch file of the destination application server 1, upgrading distributed software 2 of required first program patch file of time that patch upgrades, upgrading distributed software 2 and the pairing deployment node 2 of the first program patch file and the pairing deployment node 2 of the second program patch file and the database server of the pairing deployment node 2 of this patch data file.
Patch management server 201 specifically according to the patch update strategy of each distributed software, initiatively sends corresponding program patch file and controls the patch renewal to corresponding destination application server; Perhaps, initiatively send corresponding patch data file to the corresponding database server.
For example; Can to be patch management server 201 send the program patch file of distributed software 1 according to the patch update strategy of distributed software 1 to the destination application server of disposing node 11 to above-mentioned steps S301-S302, and controlled target application server 1 carries out patch and upgrades.
Above-mentioned steps S303 can be patch management server 201 sends distributed software 1 to the database server of disposing node 1 according to the patch update strategy of distributed software 1 a patch data file.
For another example; Can to be patch management server 201 send the first program patch file and the second program patch files to the destination application server of disposing node 21 and destination application server 2 respectively according to the patch update strategy of distributed software 2 to above-mentioned steps S401-S404, and controlled target application server 1 carries out patch with destination application server 2 and upgrades respectively.
Above-mentioned steps S405 can be patch management server 201 sends distributed software 2 to the database server of disposing node 2 according to the patch update strategy of distributed software 2 a patch data file.
In addition, in order to ensure the system reliability of each distributed software, patch management server 201 can also whenever carry out the backup of program module at a distance from each destination application server 202 of setting-up time section Long-distance Control.For example, the backup of program module is carried out in the linux of patch management server 201 far call destination application servers 202 order.When some was necessary, patch management server 201 can return back to certain version of backup before with program module by controlled target application server 202.
Patch management server 201 can also whenever carry out the backup of Database Systems at a distance from each database server 203 of setting-up time section Long-distance Control: the backup command of data base management system (DBMS) self band on the patch management server 201 far call database servers 203 carries out the backup of Database Systems.When some is necessary, patch management server 201 can control database server 203 with Database Systems return back to before the backup certain version.
A kind of patch management server that the embodiment of the invention provides, its inner modular structure synoptic diagram is as shown in Figure 5, comprising: program patch management module 501, patch data administration module 502.Suppose that first program module of distributed software 3 is deployed on first destination application server, the Database Systems of distributed software 3 are deployed on the database server.The patch renewal process of then patch management server controls distributed software 3 is:
Program patch management module 501 is used for sending the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the distributed software 3 on first destination application server carried out patch upgrade;
Patch data administration module 502 is used for sending the patch data file to database server; The Database Systems of distributed software 3 have been installed on the said database server; Carry database operating instruction information in the said patch data file, be used to indicate said database server that said Database Systems are carried out patch and upgrade.
Further, the patch management server can also comprise: patch update strategy module 503, dispatching management module 504.
The patch that the patch management server can be managed a plurality of deployment node distribution formula softwares upgrades.For convenient management, patch management server 201 generates a patch update strategy to each distributed software.
Particularly, patch update strategy module 503 is used for upgrading demand according to the patch of distributed software and generates the patch update strategy of distributed software.The patch update strategy comprises: distributed software carries out required program patch file and the pairing destination application server of program patch file, required patch data file and the pairing database server of this patch data file of said distributed software of upgrading of time, the said distributed software of upgrading that patch upgrades.
For example, comprise according to the patch of the distributed software 3 patch update strategy that generates of upgrading demand: distributed software 3 carries out the required first program patch file of time that patch upgrades, upgrading distributed software 3 and pairing first destination application server of the first program patch file, required patch data file and the pairing database server of this patch data file of upgrading distributed software.
Correspondingly; Program patch management module 501 specifically is used for after the patch that receives dispatching management module 504 transmissions makes an announcement; Patch update strategy according to said distributed software; Destination application server in said patch update strategy sends corresponding program patch file, and this program patch file of Long-distance Control destination application server execution, and the program module that is installed on the destination application server is carried out the patch renewal.For example; Program patch management module 501 is after the patch that receives distributed software 3 makes an announcement; Patch update strategy according to distributed software 3; First destination application server in the patch update strategy of distributed software 3 sends the first corresponding program patch file, and Long-distance Control first destination application server carries out the first program patch file, carries out patch and upgrades being installed in first program module on first destination application server.Preferable, program patch management module 501 can also be controlled first destination application server and back up said first program module before Long-distance Control first destination application server carried out the first program patch file.Like this, if program patch management module 501 receives the renewal failure information that first destination application server returns, then can recover according to first program module of backup by Long-distance Control first destination application server.
Patch data administration module 502 specifically is used for receiving after said patch makes an announcement, and according to the patch update strategy of distributed software, the database server in said patch update strategy sends said patch data file.For example, patch data administration module 502 is after the patch that receives distributed software 3 makes an announcement, and according to the patch update strategy of distributed software 3, the database server in the patch update strategy of distributed software 3 sends said patch data file.Preferable, patch data administration module 502 can also carry out the backup of Database Systems at remote control data storehouse server: the backup command of data base management system (DBMS) self band on the patch data administration module 502 far call database servers carries out the backup of Database Systems.
If distributed software 3 also comprises second program module, second program module is installed on second destination application server.Then also comprise in the patch update strategy of distributed software 3: the second program patch file and pairing second destination application server of the second program patch file that upgrading distributed software 3 is required.Correspondingly; Program patch management module 501 is after the patch that receives distributed software 3 makes an announcement; Patch update strategy according to distributed software 3; Send the second program patch file to second destination application server, and Long-distance Control second destination application server carries out the second program patch file, second program module is carried out patch upgrade.
Program patch management module 501 can also be controlled second destination application server and back up said second program module before Long-distance Control second destination application server is carried out the second program patch file.
Program patch management module 501 can also be according to the patch update strategy of distributed software, and each destination application server of timing controlled backs up, and promptly every separated each destination application server of setting-up time section control backs up.For example, program patch management module 501 is according to the patch update strategy of distributed software 3, and every separated setting-up time section is controlled first destination application server and backed up first program module, controls second destination application server and backs up second program module.
Patch data administration module 502 can also be according to the patch update strategy of distributed software, and each database server of timing controlled backs up, and promptly whenever backs up at a distance from the setting-up time section server of controlling database.For example, program patch management module 501 is according to the patch update strategy of distributed software 3, whenever carries out the backup of the Database Systems of distributed software 3 at a distance from the setting-up time section server of controlling database.
Program patch management module 501 can also be when some be necessary, certain version of backup before the Long-distance Control destination application server return back to program module.For example; To distributed software 3; Program patch management module 501 can return back to the version that timestamp is 2010-3-5 with first program module by Long-distance Control first destination application server, controls second destination application server second program module is return back to the version that timestamp is 2010-3-5.
Patch data administration module 502 can also be when some be necessary, certain version of backup before remote control data storehouse server return back to Database Systems.For example, to distributed software 3, patch data administration module 502 can remote control data storehouse server return back to the version that timestamp is 2010-3-5 with the Database Systems of distributed software 3.
In addition, the patch management server can also comprise: server info administration module to be updated 505, patch state administration module 506.
The keeper of patch management server can import the relevant connection information of the destination application server that distributed software has been installed through server info administration module 505 to be updated, disposes address etc. like user name, password, address, program module.Program patch management module 501 can be carried out remote access, control to destination application server according to the relevant connection information of the corresponding destination application server in the server info administration module 505 to be updated.
The keeper can also import the relevant connection information of the database server of the Database Systems that distributed software has been installed through server info administration module 505 to be updated, disposes address etc. like user name, password, address, Database Systems.Patch data administration module 502 can carry out remote access, control to database server according to the relevant connection information of the correspondence database server in the server info administration module 505 to be updated.
The keeper through patch state administration module 506 can program patch file or patch data file be uploaded, download, bookkeeping such as deletion, record version this shop.
Program patch management module 501 is according to the patch update strategy of distributed software; Obtain corresponding program patch file from patch state administration module 506 and send to corresponding intended application service; And after the Long-distance Control destination application server carries out the patch renewal; The renewal result that the receiving target application server returns, as upgrade success or upgrade failure.Program patch management module 501 will be upgraded the result and send to patch state administration module 506.
Patch data administration module 502 is according to the patch update strategy of distributed software; Obtain corresponding patch data file from patch state administration module 506 and send to corresponding database service; And after remote control data storehouse server carries out the patch renewal; Receive the renewal result that database server returns, as upgrade success or upgrade failure.Patch data administration module 502 will upgrade the result and send to patch state administration module 506.
The keeper can check the renewal result of each program patch file on the destination application server of correspondence through patch state administration module 506, perhaps the renewal result of each patch data file on the database server of correspondence.
A kind of database server that the embodiment of the invention provides, its inner modular structure synoptic diagram is as shown in Figure 6, comprising: file receiver module 601, parsing module 602, execution module 603.
Parsing module 602 is used for parsing database operating instruction information from the patch data file that file receiver module 601 receives;
The embodiment of the invention is because in the patch renewal process of distributed software; Through the patch management server to destination application server and database server active push program patch file and patch data file; Can unify to realize program module on the destination application server is upgraded and database server on Database Systems upgrade, thereby realizing distributing is installed in the upgrading and the repairing of the distributed software on destination application server and the database server.Technical scheme through the embodiment of the invention can make things convenient for, realize effectively that the automatic patch of distributed software upgrades; Save the manpower and materials that expend in the patch renewal process of upgrading distributed software, improve the reliability that distributed software carries out the patch renewal process.
One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to accomplish through program; This program can be stored in the computer read/write memory medium, as: ROM/RAM, magnetic disc, CD etc.
The above only is a preferred implementation of the present invention; Should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; Can also make some improvement and retouching, these improvement and retouching also should be regarded as protection scope of the present invention.
Claims (15)
1. distributed software patch update method comprises:
The patch management server sends the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch management server sends patch data file, the Database Systems that said distributed software has been installed on the said database server to database server;
Said database server carries out patch to said Database Systems and upgrades according to the database operating instruction information of carrying in the said patch data file.
2. the method for claim 1 before said Long-distance Control first destination application server is carried out the first program patch file, also comprises:
Said patch management server Long-distance Control first destination application server backs up first program module; And,
If in the process of first program module that is installed in the said distributed software on first destination application server being carried out the patch renewal, mistake occurs, then:
First destination application server returns the renewal failure information to said patch management server, and after said patch management server received said renewal failure information, Long-distance Control first destination application server recovered according to first program module of backup.
3. method as claimed in claim 2, said patch management server sends the first program patch file to first destination application server and is specially:
Said patch management server sends the first program patch file according to the patch update strategy of said distributed software to first destination application server; And,
Said patch management server sends the patch data file to database server and is specially:
Said patch management server sends the patch data file according to the patch update strategy of said distributed software to database server;
Wherein, Said patch update strategy is predetermined, comprising: the first program patch file and pairing first destination application server of the first program patch file and said patch data file and the pairing database server of said patch data file; Wherein, the said patch data file and the first program patch file are the required file of the said distributed software of upgrading.
4. the method for claim 1; It is characterized in that; If said distributed software also comprises second program module that is installed on second destination application server, and the required file of said distributed software of upgrading also comprises the second program patch file, and then said method also comprises:
Said patch management server sends the second program patch file to second destination application server, and Long-distance Control second destination application server carries out the second program patch file, second program module is carried out patch upgrade.
5. method as claimed in claim 4 before said Long-distance Control second destination application server is carried out the second program patch file, also comprises:
Said patch management server Long-distance Control second destination application server backs up second program module.
6. like claim 4,5 described methods, said patch management server sends the first program patch file to first destination application server and is specially:
Said patch management server sends the first program patch file according to the patch update strategy of said distributed software to first destination application server; And,
Said patch management server sends the patch data file to database server and is specially:
Said patch management server sends the patch data file according to the patch update strategy of said distributed software to database server; And,
Said patch management server sends the second program patch file to second destination application server and is specially:
Said patch management server sends the second program patch file according to the patch update strategy of said distributed software to second destination application server;
Wherein, Said patch update strategy is predetermined, comprising: the first program patch file and pairing first destination application server of the first program patch file, the second program patch file and pairing second destination application server of the second program patch file and said patch data file and the pairing database server of said patch data file; Wherein, said patch data file, the first program patch file and the second program patch file are the required file of the said distributed software of upgrading.
7. like the described method of claim 1-6, said database operating instruction information comprises: database patch operation instruction information, database rollback operation command information; And,
Said according to the database operating instruction information of carrying in the said patch data file, said Database Systems are carried out the patch renewal specifically refer to:, said Database Systems are carried out patch upgrade according to said database patch operation instruction information; And,
If the patch of said Database Systems is upgraded failure, then said database server is according to said database rollback operation command information, said Database Systems returned to carry out the state of patch before upgrading.
8. a distributed software patch update system comprises: patch management server, first destination application server and database server;
The patch management server is used for sending the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch management server also is used for sending patch data file, the Database Systems that said distributed software has been installed on the said database server to said database server;
Said database server carries out patch to said Database Systems and upgrades according to the database operating instruction information of carrying in the said patch data file.
9. system as claimed in claim 8 is characterized in that, if said distributed software also comprises second program module that is installed on second destination application server, then said system also comprises: second destination application server;
Said patch management server also is used for sending the second program patch file to second destination application server, and Long-distance Control second destination application server carries out the second program patch file, second program module is carried out patch upgrade.
10. patch management server comprises:
Program patch management module; Be used for sending the first program patch file to first destination application server; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
The patch data administration module; Be used for sending the patch data file to database server; The Database Systems of said distributed software have been installed on the said database server; Carry database operating instruction information in the said patch data file, be used to indicate said database server that said Database Systems are carried out patch and upgrade.
11. server as claimed in claim 10 is characterized in that, also comprises:
Patch update strategy module; Be used to generate the patch update strategy of said distributed software, said patch update strategy comprises: said distributed software carries out the required first program patch file and pairing first destination application server of the first program patch file, required patch data file and the pairing database server of this patch data file of said distributed software of upgrading of time, the said distributed software of upgrading that patch upgrades;
Dispatching management module; Be used for patch update strategy according to said patch update strategy module generation; Confirming that said distributed software carries out time that patch upgrades when arriving, and makes an announcement to said program patch management module and patch data administration module transmission patch; And,
Said program patch management module specifically is used for receiving after said patch makes an announcement; Patch update strategy according to said distributed software; First destination application server in said patch update strategy sends the first program patch file; And Long-distance Control first destination application server carries out the first program patch file, first program module that is installed in the said distributed software on first destination application server carried out patch upgrade;
Said patch data administration module specifically is used for receiving after said patch makes an announcement, and according to the patch update strategy of said distributed software, the database server in said patch update strategy sends said patch data file.
12. server as claimed in claim 11 is characterized in that,
Said program patch management module also was used for before Long-distance Control first destination application server is carried out the first program patch file, controlled first destination application server and backed up said first program module; And said program patch management module also is used for if receive the renewal failure information that first destination application server returns, and then Long-distance Control first destination application server recovers according to first program module of backup.
13. server as claimed in claim 11; It is characterized in that; If said distributed software also comprises second program module that is installed on second destination application server, and the required program patch file of the said distributed software of upgrading also comprises the second program patch file, then:
The patch update strategy of said distributed software also comprises: the second program patch file and pairing second destination application server of the second program patch file; And,
Said program patch management module also is used for receiving after said patch makes an announcement; Patch update strategy according to said distributed software; Also send the second program patch file to second destination application server; And Long-distance Control second destination application server carries out the second program patch file, second program module carried out patch upgrade.
14. server as claimed in claim 13 is characterized in that,
Said program patch management module also is used for the patch update strategy according to said distributed software, every backs up at a distance from setting-up time section Long-distance Control first destination application server that first program module, second destination application server back up second program module, said database server backs up said Database Systems.
15. a database server is characterized in that, comprising:
The file receiver module is used to receive the patch data file that the patch management server sends, and carries database operating instruction information in the said patch data file;
Parsing module is used for parsing database operating instruction information from said patch data file;
Execution module is used for according to the database operating instruction information and executing corresponding database operational order that parses, and the Database Systems that are installed in the said database server are carried out the patch renewal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210015218.5A CN102609281B (en) | 2012-02-24 | 2012-02-24 | Distributed software patch update method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210015218.5A CN102609281B (en) | 2012-02-24 | 2012-02-24 | Distributed software patch update method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102609281A true CN102609281A (en) | 2012-07-25 |
| CN102609281B CN102609281B (en) | 2016-01-27 |
Family
ID=46526679
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210015218.5A Active CN102609281B (en) | 2012-02-24 | 2012-02-24 | Distributed software patch update method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102609281B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239113A (en) * | 2014-10-09 | 2014-12-24 | 浪潮通用软件有限公司 | Method for updating program patches for multiple servers on basis of messages |
| CN104375834A (en) * | 2014-11-18 | 2015-02-25 | 无锡悟莘科技有限公司 | Distributed software hot plug method based on MAPE-K ring structure model |
| CN104881336A (en) * | 2015-05-22 | 2015-09-02 | 北京奇虎科技有限公司 | Data backup method and device |
| WO2015127850A1 (en) * | 2014-02-26 | 2015-09-03 | 可牛网络技术（北京）有限公司 | Data upgrading method and central server |
| CN104980956A (en) * | 2015-06-29 | 2015-10-14 | 迈锐数据（北京）有限公司 | Method for remotely updating node firmware in batched manner |
| CN105306237A (en) * | 2014-06-26 | 2016-02-03 | 中兴通讯股份有限公司 | Distributed management method and device for network management |
| CN106126568A (en) * | 2016-06-17 | 2016-11-16 | 杭州财人汇网络股份有限公司 | One promotes mainly formula serializing buffer memory management method and system |
| CN106406921A (en) * | 2015-07-29 | 2017-02-15 | 深圳市腾讯计算机系统有限公司 | Patch installation method and device |
| CN106775852A (en) * | 2016-12-05 | 2017-05-31 | 云鸟（上海）能源科技有限公司 | A kind of method that embedded Linux Charge Management terminal is upgraded by wireless communication module |
| CN106909429A (en) * | 2017-04-05 | 2017-06-30 | 微鲸科技有限公司 | A kind of synchronous upgrade method and device |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107179924A (en) * | 2017-04-01 | 2017-09-19 | 北京五八信息技术有限公司 | Application program update method and more new system |
| CN109863475A (en) * | 2017-10-09 | 2019-06-07 | 华为技术有限公司 | The upgrade method and relevant device of a kind of application in safety element |
| CN109976788A (en) * | 2019-03-26 | 2019-07-05 | 深圳Tcl数字技术有限公司 | The miniature loophole restorative procedure of intelligent terminal, intelligent terminal, equipment and server |
| CN112416386A (en) * | 2020-10-26 | 2021-02-26 | 北京一亩田新农网络科技有限公司 | Method, device, system and medium for software upgrading |
| CN116048577B (en) * | 2022-12-29 | 2024-05-17 | 哈尔滨工大卫星技术有限公司 | Distributed digital satellite system upgrading method, device and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5920725A (en) * | 1997-07-02 | 1999-07-06 | Adaptivity Inc. | Run-time object-synthesis and transparent client/server updating of distributed objects using a meta server of all object descriptors |
| CN1758607A (en) * | 2005-11-10 | 2006-04-12 | 中国工商银行 | Software edition updating system in distributed service system and its method |
| CN101699399A (en) * | 2009-11-03 | 2010-04-28 | 中兴通讯股份有限公司 | Software update system and method |
-
2012
- 2012-02-24 CN CN201210015218.5A patent/CN102609281B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5920725A (en) * | 1997-07-02 | 1999-07-06 | Adaptivity Inc. | Run-time object-synthesis and transparent client/server updating of distributed objects using a meta server of all object descriptors |
| CN1758607A (en) * | 2005-11-10 | 2006-04-12 | 中国工商银行 | Software edition updating system in distributed service system and its method |
| CN101699399A (en) * | 2009-11-03 | 2010-04-28 | 中兴通讯股份有限公司 | Software update system and method |
Non-Patent Citations (1)
| Title |
|---|
| 电脑报: "《真能上手——我的第一本网络安全手册》", 30 April 2010, 电脑报电子出版社 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015127850A1 (en) * | 2014-02-26 | 2015-09-03 | 可牛网络技术（北京）有限公司 | Data upgrading method and central server |
| CN105306237A (en) * | 2014-06-26 | 2016-02-03 | 中兴通讯股份有限公司 | Distributed management method and device for network management |
| CN104239113A (en) * | 2014-10-09 | 2014-12-24 | 浪潮通用软件有限公司 | Method for updating program patches for multiple servers on basis of messages |
| CN104375834B (en) * | 2014-11-18 | 2017-06-16 | 无锡悟莘科技有限公司 | A kind of distributed software hot-plug method based on MAPE K loop configuration models |
| CN104375834A (en) * | 2014-11-18 | 2015-02-25 | 无锡悟莘科技有限公司 | Distributed software hot plug method based on MAPE-K ring structure model |
| CN104881336A (en) * | 2015-05-22 | 2015-09-02 | 北京奇虎科技有限公司 | Data backup method and device |
| CN104980956A (en) * | 2015-06-29 | 2015-10-14 | 迈锐数据（北京）有限公司 | Method for remotely updating node firmware in batched manner |
| CN106406921B (en) * | 2015-07-29 | 2020-02-28 | 深圳市腾讯计算机系统有限公司 | Method and device for installing patch |
| CN106406921A (en) * | 2015-07-29 | 2017-02-15 | 深圳市腾讯计算机系统有限公司 | Patch installation method and device |
| CN106126568A (en) * | 2016-06-17 | 2016-11-16 | 杭州财人汇网络股份有限公司 | One promotes mainly formula serializing buffer memory management method and system |
| CN106775852A (en) * | 2016-12-05 | 2017-05-31 | 云鸟（上海）能源科技有限公司 | A kind of method that embedded Linux Charge Management terminal is upgraded by wireless communication module |
| CN107179924A (en) * | 2017-04-01 | 2017-09-19 | 北京五八信息技术有限公司 | Application program update method and more new system |
| CN106909429A (en) * | 2017-04-05 | 2017-06-30 | 微鲸科技有限公司 | A kind of synchronous upgrade method and device |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107147711B (en) * | 2017-05-04 | 2020-03-13 | 浙江数链科技有限公司 | Application service updating method and device |
| CN109863475A (en) * | 2017-10-09 | 2019-06-07 | 华为技术有限公司 | The upgrade method and relevant device of a kind of application in safety element |
| CN109976788A (en) * | 2019-03-26 | 2019-07-05 | 深圳Tcl数字技术有限公司 | The miniature loophole restorative procedure of intelligent terminal, intelligent terminal, equipment and server |
| CN109976788B (en) * | 2019-03-26 | 2024-03-15 | 深圳Tcl数字技术有限公司 | Intelligent terminal miniature vulnerability restoration method, intelligent terminal, equipment and server |
| CN112416386A (en) * | 2020-10-26 | 2021-02-26 | 北京一亩田新农网络科技有限公司 | Method, device, system and medium for software upgrading |
| CN116048577B (en) * | 2022-12-29 | 2024-05-17 | 哈尔滨工大卫星技术有限公司 | Distributed digital satellite system upgrading method, device and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102609281B (en) | 2016-01-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102609281B (en) | Distributed software patch update method and system | |
| CN107515776B (en) | Method for upgrading service continuously, node to be upgraded and readable storage medium | |
| KR101970839B1 (en) | Replaying jobs at a secondary location of a service | |
| CN102622298B (en) | Software testing system and method | |
| CN101217411B (en) | A method, device and system realizing the upgrading of stacking device software | |
| US8892712B2 (en) | Upgrading enterprise managers | |
| US10797952B1 (en) | Intelligent rollback analysis of configuration changes | |
| US20060259594A1 (en) | Progressive deployment and maintenance of applications on a set of peer nodes | |
| CN111045854B (en) | Method, apparatus and computer readable medium for managing service containers | |
| US10331428B1 (en) | Automated firmware update management on huge big-data clusters | |
| CN103530150A (en) | Remote updating method for Linux operating system | |
| CN102455915A (en) | Method for automatically configuring distributed system, and server | |
| CN102025778A (en) | Software version upgrading work method based on Shell | |
| CN106657167B (en) | Management server, server cluster, and management method | |
| CN109240716B (en) | Big data platform version management and rapid iterative deployment method and system | |
| CN110912728B (en) | Operating system patch batch automatic update management method and system | |
| CN106569863B (en) | Resource and code modularization-based android app resource updating and repairing method | |
| CN109558147A (en) | A kind of continuous integrating platform construction method based on Jenkins and Gitlab | |
| CN103455346A (en) | Application program deployment method, deployment main control computer, deployment client side and cluster | |
| CN114138754A (en) | Software deployment method and device based on Kubernetes platform | |
| CN105430096A (en) | Automatic installation method and device for parallel file system | |
| CN104899116A (en) | Data backup method, source server, target server and system | |
| CN110795105A (en) | Automatic compiling and deploying method and system for power distribution automation master station system | |
| CN116149713B (en) | Program upgrading method and device for all-level equipment under tree-type heterogeneous network | |
| CN104158906A (en) | Server agent manipulation system and manipulation method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |