CN102479092A - Method and device for updating patch of software system - Google Patents
Method and device for updating patch of software system Download PDFInfo
- Publication number
- CN102479092A CN102479092A CN2010105671663A CN201010567166A CN102479092A CN 102479092 A CN102479092 A CN 102479092A CN 2010105671663 A CN2010105671663 A CN 2010105671663A CN 201010567166 A CN201010567166 A CN 201010567166A CN 102479092 A CN102479092 A CN 102479092A
- Authority
- CN
- China
- Prior art keywords
- file
- patch
- upgrade
- user
- needs
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and device for updating a patch of a software system, wherein the method comprises the following steps of: monitoring whether a patch updating condition of the software system, set by a user, is met at the current moment, and if so, acquiring a patch document according to a server address of the patch document, set by the user; determining a document of the software system, which is required to be updated, according to the patch document and a patch document folder path set by the user; and comparing whether the patch document is matched with the document required to be updated, if not, updating the document required to be updated by using the patch document. According to the method and the device, the problems of untimeliness in updating and complexity in operation caused by manually updating a software patch are solved, and the satisfaction of the user to a product is enhanced.
Description
Technical field
The present invention relates to the software upgrading field, upgrade the method and apparatus of patch in particular to a kind of software systems.
Background technology
The test of long period has all been experienced in the formal issue of any software product.Particularly,, can often release the product demand service packs, at this moment, need the feasibility of tester's testing requirement along with the continuous variation of product demand in the product planning phase; Then, product demand is basicly stable, and at the product development initial stage, under the also unsettled situation of product function and performance, it is particularly important that test job also can seem---and be an important ring that guarantees product quality.
The tester is in test, and in order to verify the quality of version, maximum mode of usefulness is exactly to verify the Trouble ticket of version through the mode of upgrading patch file.And the mode of obtaining patch file at present commonly used, be manual obtaining: manually connect patch server, the catalogue of patch file is searched in manual work, checks newly-increased patch file explanation, and the user is according to own needs, determines whether patch installing.This mode is upgraded patch has following defective:
The first, the user upgrades the randomness of patch, and when the user upgrades patch, does not have the regular time point, relies on user's oneself wish fully, if in the test, and user's patch that do not upgrade in time, validation fault timely just, the efficient that influence is tested;
Second; The user upgrades the passivity of patch, the user when, beat which type of patch, rely on patch issue personnel or whereabouts developer fully and understand the patch situation; The each mail that all need pay close attention to patch issue personnel mass-sending; This also interrupts tester's thinking easily when test, influence testing efficiency.
In addition, after software product is externally issued, also need constantly through upgrading the mode upgrading products of patch.Such as webmastering software, take engineering site or user at webmastering software and go can often run into the problem of upgrading patch when on probation or commercial there, through patch, solve the Bug that some have more been corrected one's mistakes, the network management function of perhaps upgrading.Upgrading the way of patch in the market, also is by market interface personnel service packs to be provided mostly, removes the manual patch that upgrades by the customer service personnel, and there is the above-mentioned manual drawback of upgrading patch equally in this way.
Can know that by above content manually there is problems such as upgrading untimely and complex operation in the update software patch.
Summary of the invention
The method and apparatus that fundamental purpose of the present invention is to provide a kind of software systems to upgrade patch, the untimely problem with complex operation of the renewal that causes when solving above-mentioned manual update software patch at least.
According to an aspect of the present invention; Provide a kind of software systems to upgrade the method for patch; Comprise: whether the monitoring current time satisfies the renewal patch condition of the software systems that the user is provided with, if satisfy, the server address of the patch file that is provided with according to the user obtains patch file; The file that above-mentioned software systems needs upgrade is confirmed in patch file folder path according to this patch file and user's setting; Relatively whether this patch file matees with the file that needs to upgrade, if do not match, uses this patch file renewal to need the file that upgrades.
According to a further aspect in the invention, provide a kind of software systems to upgrade the device of patch, having comprised: monitoring modular is used to monitor the renewal patch condition whether current time satisfies the software systems of user's setting; File acquisition module, the monitoring result that is used for said monitoring modular are when satisfying said renewal patch condition, and the server address of the patch file that is provided with according to said user obtains patch file; The file determination module, the file that said software systems needs upgrade is confirmed in the patch file folder path that said patch file that is used for obtaining according to said file acquisition module and said user are provided with; Update module, whether the file that is used for the renewal of more said patch file and said needs matees, if do not match, uses said patch file to upgrade the said file that needs renewal.
Through the present invention; The renewal patch condition that adopts the monitoring current time whether to satisfy user's setting determines whether triggering patch and upgrades; This trigger process does not need the people to participate in; The untimely problem with complex operation of the renewal that has caused when having solved manual update software patch has promoted the satisfaction of user to product.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the method flow diagram that upgrades patch according to the software systems of the embodiment of the invention 1;
Fig. 2 is the structured flowchart according to the equipment of the embodiment of the invention 2;
Fig. 3 is the method flow diagram that upgrades patch according to the software systems of the embodiment of the invention 2;
Fig. 4 is the patch automatic rollback process flow diagram according to the embodiment of the invention 2; And
Fig. 5 is the structured flowchart that upgrades the device of patch according to the software systems of the embodiment of the invention 3.
Embodiment
Hereinafter will and combine embodiment to specify the present invention with reference to accompanying drawing.Need to prove that under the situation of not conflicting, embodiment and the characteristic among the embodiment among the application can make up each other.
The method and apparatus that the embodiment of the invention provides software systems to upgrade patch is in order to realize the automatic renewal of software systems.
Embodiment 1
Fig. 1 shows the method flow diagram that upgrades patch according to the software systems of the embodiment of the invention, and this method may further comprise the steps:
Whether step S102, monitoring current time satisfy the renewal patch condition of the software systems that the user is provided with, if satisfy, the server address of the patch file that is provided with according to the user obtains patch file;
Upgrade the patch condition and be one of following: the fixed time of appointed day starts back operation appointment duration with software systems.For example at 8 in the evening of every day or software systems operation 40 hours etc.; Do not upgrade the patch condition if current time does not satisfy, then do not carry out the renewal patch operation of these software systems;
Step S104 confirms the file that the software systems needs upgrade according to the patch file folder path of above-mentioned patch file and user's setting;
Step S106, whether more above-mentioned patch file matees with the file that needs to upgrade, if do not match, uses the patch file renewal to need the file that upgrades.
Above-mentioned patch file does not match with the file that needs to upgrade, and explaining has newly-increased patch on the server, then need the file of this locality be upgraded, otherwise, explain that the two is identical, do not need the file of this locality is upgraded.
The renewal patch condition that present embodiment adopts the monitoring current time whether to satisfy user's setting determines whether triggering patch and upgrades; This trigger process does not need the people to participate in; The untimely problem with complex operation of the renewal that has caused when having solved manual update software patch; Promoted the satisfaction of user, be particularly useful for software upgrading and the software upgrading of webmastering software in the software test procedure product.
Can there be abnormal conditions in the patch renewal of considering software, and present embodiment is before the file that uses the patch file renewal to need to upgrade, and this method also comprises: the file that the backup needs upgrade; Based on this; The file that uses the patch file renewal to need to upgrade comprises: in the process of the file that use patch file renewal needs upgrade; If take place to upgrade interrupt (for example unexpected disconnection of operating terminal and server is connected etc.), then the file according to the needs renewal of backing up carries out rollback.Promptly use the file of the needs renewal of backup to replace newly-increased file in the patch renewal.
The user uses the software systems behind the renewal patch, if find that uneasy congruent problem is arranged, in the time of need returning to the state that does not carry out the patch renewal, also need carry out rollback.Based on this, use after the file that patch file renewals need to upgrade, said method comprises: in the software systems operational process, receive user's rollback order after, carry out rollback according to the file of the needs renewal of backup.
Above-mentioned rollback action is unexistent in the prior art, for the manual mode of upgrading patch, if upgrade the patch failure; Patch is not easy rollback, because the tester is disposable all to be upgraded all patches in order to make things convenient for, most of patches all adopt the full dose compiling; And then issue, but, can not back up the configuration file that upgrades automatically owing to upgrade the mode of patch by hand; Cause upgrading under patch failure or the problematic situation of patch itself, patch is not easy rollback.In addition, in practical applications,, just in case upgrade patch failure or the insecure words of patch itself, can also can let the user that product is produced distrust to the consequence of the bringing on a disaster property of managerial ability of on-the-spot webmaster if patch can not automatic rollback.So present embodiment preferably backs up the file that needs upgrade, operate and overcome above-mentioned defective in order to carry out rollback.
Certainly, a large amount of backup files can take the storage space of equipment, and therefore, after present embodiment adopted the operating software system to reach the time of setting, the prompting user deleted the file of the needs renewal of backup; After receiving user's agreement deletion indication, delete the file of the needs renewal of above-mentioned backup.
In order to accomplish the renewal operation of patch file smoothly, present embodiment preferably uses the patch file renewal to need before the file of renewal, and this method comprises: judge whether software systems are used, if the prompting user closes software systems; After these software systems are closed, carry out the step of using the patch file renewal to need the file of renewal again.
The configuration information that the user is provided with can be preserved with the mode of template, also can upgrade often, for example points out the user to upgrade configuration information at set intervals.Based on this; Whether above-mentioned monitoring current time satisfies before the renewal patch condition of the software systems that the user is provided with; This method also comprises: receive and preserve the configuration information of the software systems of user's setting, this configuration information comprises: the path of upgrading server address, patch file folder and the patch file folder of patch condition, patch file.
In order to strengthen the security that soft system uses, the above-mentioned configuration information of present embodiment also comprises: user's username and password; Whether above-mentioned monitoring current time satisfies before the renewal patch condition of the software systems that the user is provided with, and method also comprises: after receiving the order that starts software systems, the prompting user imports username and password; Whether legal according to the checking of the username and password in configuration information user, if the user is legal, start and the operating software system.
In order to protect operator or software developer's interests, present embodiment can carry out authentication to software systems before carrying out patch renewal operation; Before promptly relatively whether patch file matees with the file that needs to upgrade; This method also comprises: judge whether legitimacy of software systems, for example, judge that whether correct the sequence number of input etc.; If legal, carry out the step whether relatively patch file and the file that needs to upgrade mate.
The patch update condition that present embodiment is set according to the user triggers patch and upgrades; Software systems will be automatically obtained and are upgraded patch from server, if patch upgrades failure, perhaps patch needs rollback; Software systems meeting automatic rollback patch recovers the environment before software systems are upgraded patch.The untimely problem with complex operation of the renewal that has caused when having solved manual update software patch has well guaranteed that the user upgrades the periodicity and the initiative of patch, simultaneously, changes artificial regeneration patch pattern, and system upgrades patch automatically; Even upgrade the patch failure, system also can fast automatic rollback patch, therefore has very strong practicality.
Embodiment 2
The equipment that present embodiment provides with Fig. 2 is that example describes, and this equipment comprises 4 modules: configuration module, authentication module, upgrade patch module and automatic rollback patch module automatically.Wherein, each functions of modules is following:
Configuration module is responsible for the needs according to the user; Various condition combinations are set, and preserve into a masterplate form to the condition that the user is provided with, for example: the configuration information that the user is set; Comprise address, user name, password and file that patch server is set; The file that needs to upgrade patch file is set, the time strategy of automatic renewal patch is set, preserve user's configuration data etc.;
Authentication module is responsible for judging the user identity that needs to upgrade patch file, mainly is used for judging the legitimacy of the system software that needs upgrading, such as judging through the license file whether these software systems possess the authority of obtaining patch file automatically.
Automatically upgrading the patch module is responsible for obtaining automatically patch file, upgrades patch automatically; For example: through certain judgment criterion; The comparison result of patch file and operating terminal same file on the judgement patch server, whether decision upgrades patch automatically, such as passing through catalogue file comparer instrument.
Automatic rollback patch module is responsible for upgrading result and patch quality according to user's patch, and whether the user determines the automatic rollback patch.
Based on above-mentioned device shown in Figure 2, present embodiment provides a kind of software systems to upgrade the method for patch, and referring to Fig. 3, this method may further comprise the steps:
Step S301, whether judges is provided with the condition masterplate of automatic renewal patch, if, execution in step S302; If not, execution in step S306.
If the user has disposed this module, all automatic operations of upgrading patch of back will be based on the operation that is provided with of this module; If the condition template of automatic renewal patch is not set, then read the masterplate of the last configuration of user.
Step S302 is provided with the server address, user name, password and the patch file folder that obtain patch file automatically.
Step S303, the file of patch file need be upgraded in the setting operation terminal.
Step S304, the time strategy of patch is upgraded at the setting operation terminal automatically, and patch is upgraded in some timing every day or how long system start-up upgrades patch etc. such as being provided with; After the various condition setting of treating the user finish, get into step S305.
Step S305 preserves user's configuration, and this operation meeting is used as the template preservation to user's various configurations, moves this system later on, promptly upgrades patch file automatically according to the condition of this setting of user; If the user has changed configuration condition, move this system so next time, the template of preservation is as the criterion with the condition of nearest user's change.
Above-mentioned steps S301-S305 can realize on above-mentioned configuration module.
Step S306 reads the masterplate of the last configuration of user.
If in step S301, the user selects not dispose the masterplate of automatic renewal patch file, and then system changes step S306 over to, promptly reads the masterplate of the last configuration of user.
Before system compares patch file automatically, at first need get into step S307.
Step S307, to subscriber identity authentication, the purpose of this step is the legitimacy that judgement needs to upgrade the patch file system, judges such as going through the license file on the decision operation terminal whether the system that need upgrade patch is legal; If illegal, execution in step S308; If legal, execution in step S309 then.
Step S308 does not allow operating terminal to upgrade patch automatically, so far, and system's end of run then;
Step S309 starts the catalogue file comparer, and the catalogue file comparer can be reference according to the patch file on the patch server of user's setting here.
Step S310, whether the patch file on the server is identical with local file, if, execution in step S311; If not, execution in step S312.
For example, use on the file comparer contrast operation terminal file size and time whether with server on the patch file coupling, if promptly mate; Then explaining does not have new patch on the patch server, need not upgrade patch, i.e. step S311; System's end of run so, then; If do not match, then explaining has new patch on the patch server, and at this moment, system can access patch automatically and upgrade instruction card, supplies the user to check newly-increased patch.
Step S311 does not need to upgrade automatically patch.
Above-mentioned steps S306-step S311 can realize through above-mentioned authentication module.
Step S312 judges whether these software systems are moved, if, execution in step S313; If not, execution in step S315.
Step S313 need to judge whether the shutdown system process to upgrade patch again, if, execution in step S314; If not, execution in step S315.
Step S314, prompting user are all processes that finish these software systems automatically or manually.
Step S315, the automatic patch installing of system, and the file backup that is replaced this locality.
Before system upgrades patch automatically; Can go to judge whether these software systems are moved,, then can go to judge whether that needs shutdown system process upgrades patch again according to the different situations of system if promptly system moves; Be step S313; Shutdown system process if desired, then can point out the user is automatically or manually all processes of ends with system, i.e. step S314; The benefit of doing like this is: let the user how select the ends with system process, prevent that automatic ends with system process from causing unnecessary influence to other business.
After upgrading patch, system's some files before deletion is upgraded automatically are such as the temp file etc.; If system not operation does not perhaps need the shutdown system process, then directly get into this step, when upgrading patch automatically here, can be the file automated back-up that is updated, in case the user needs the rollback patch.
Above-mentioned steps S312-S315 can realize on above-mentioned automatic renewal patch module.
Step S316, the system that treats upgrade patch file automatically and finish, and the ruuning situation of user's software according to the situation of upgrading patch with after upgrading patch gets into the rollback flow process.
Step S317 lets the user judge whether the automatic start up system process, if, execution in step S318, if not, execution in step S319;
Step S318, the automatic start up system process; System after then starting is the system that upgrades automatically behind the patch naturally;
Step S319, the prompting user selects whether to delete backup file, if, execution in step S320; If not, finish.
Step S320, if the user selects deletion, system is the deletion backup file automatically.
If the user selects not delete backup file, then backup file can keep always, initiatively deletes these backup files up to the user.The purpose of doing like this is: prevent that backup file is too much, take hard drive space.
Above-mentioned steps S316-S320 can realize on above-mentioned automatic rollback patch module.
What be worth explanation is that deletion backup file function is an independent function, can in system's operational process, carry out, and also can be independent of system's operation, the standalone feature of deletion backup file in the present embodiment.
Fig. 4 is a patch automatic rollback process flow diagram in this equipment, and patch needs the processing under the situation of rollback to comprise:
Step S401 judges whether rollback patch immediately, if, execution in step S405; If not, execution in step S402;
Step S402, automatic or manual start-up system process;
Step S403 judges whether patch is reliable, if finish current flow process; If not, execution in step S404;
Step S404, automatic or manual shutdown system process, execution in step S405 then;
Step S405 is with local backup file replacement original.
Above-mentioned patch automatic rollback process has two kinds of situation: the first, and patch is rollback immediately, and this situation generally is, and when upgrading patch, network interrupts, and this moment, system needed rollback patch immediately, and the local backup file is replaced original, i.e. step S405; The second, after system start-up, according to the patch quality, whether decision needs the rollback patch; Be step S403, before this step, at first need the user to select manually perhaps to start automatically this system process; Be step S402, if patch is unreliable, then manual or automatic closing system process can be pointed out the user by system; Be step S404, same then execution in step S405 is with local backup file replacement original; In this case, the user need generally can not judge whether the rollback patch, generally needs the user in the software process that uses after upgrading patch, finds that patch has problem, and just the rollback patch is removed in decision.If upgrade in the patch process, upgrade smoothly, and patch itself is reliably, then system need not to refill and moves back fourth.
Present embodiment and the contrast of existing manual renewal patch method, this method is a mode of upgrading patch automatically because of what adopt, has improved the efficient of software upgrading patch, and for the processing of upgrading after patch is failed, rollback function preferably is provided.
Embodiment 3
Fig. 5 shows the structured flowchart that upgrades the device of patch according to the software systems of the embodiment of the invention, and this device can be arranged on any equipment, and it comprises:
Monitoring modular 52 is used to monitor the renewal patch condition whether current time satisfies the software systems of user's setting;
Upgrade the patch condition and be one of following: the fixed time of appointed day starts back operation appointment duration with software systems.For example at 8 in the evening of every day or software systems operation 40 hours etc.; Do not upgrade the patch condition if current time does not satisfy, then do not carry out the renewal patch operation of these software systems;
Whether update module 58 links to each other with file determination module 56, be used for the comparison patch file and mate with the file that needs upgrade, if do not match, uses the patch file renewal to need the file that upgrades.
Above-mentioned patch file does not match with the file that needs to upgrade, and explaining has newly-increased patch on the server, then need the file of this locality be upgraded, otherwise, explain that the two is identical, do not need the file of this locality is upgraded.
The renewal patch condition that present embodiment adopts the monitoring current time whether to satisfy user's setting determines whether triggering patch and upgrades; This trigger process does not need the people to participate in; The untimely problem with complex operation of the renewal that has caused when having solved manual update software patch; Promoted the satisfaction of user, be particularly useful for software upgrading and the software upgrading of webmastering software in the software test procedure product.
Can there be abnormal conditions in the patch renewal of considering software, and present embodiment is before the file that uses the patch file renewal to need to upgrade, and this method also comprises: the file that the backup needs upgrade; Based on this, this device also comprises:
Backup module is used for the file that the definite needs of backup file determination module upgrade;
First rollback module is used for using patch file to upgrade the process of the file that needs upgrade, if (for example operating terminal be connected with the unexpected disconnection of server etc.) taken place to upgrade and interrupted, carries out rollback based on the file of the needs renewal of above-mentioned backup.Promptly use the file of the needs renewal of backup to replace newly-increased file in the patch renewal.
The user uses the software systems behind the renewal patch, if find that uneasy congruent problem is arranged, in the time of need returning to the state that does not carry out the patch renewal, also need carry out rollback.Based on this, this device also comprises: second rollback module, be used for the software systems operational process, receive rollback order after, the file that upgrades according to the needs of above-mentioned backup carries out rollback.
Certainly, a large amount of backup files can take the storage space of equipment, and therefore, the device of present embodiment can also comprise: removing module, be used for time that the operating software system reaches setting after, the prompting user deletes the file that the needs of backup upgrade; And after receiving user's agreement deletion indication, delete the file of the needs renewal of above-mentioned backup.
In order to accomplish the renewal operation of patch file smoothly, present embodiment is preferred, and this device also comprises: the software closing module is used to judge whether software systems are used, if the prompting user closes software systems; After these software systems are closed, trigger update module 58 again and use the patch file renewal to need the file that upgrades.
The configuration information that the user is provided with can be preserved with the mode of template, also can upgrade often, for example points out the user to upgrade configuration information at set intervals.Based on this, said apparatus also comprises: backup module, be used to receive and preserve the configuration information of the software systems that the user is provided with, and this configuration information comprises: the path of upgrading server address, patch file folder and the patch file folder of patch condition, patch file.
In order to strengthen the security that soft system uses, the above-mentioned configuration information of present embodiment also comprises: user's username and password; Said apparatus also comprises: authentication module, and after being used to receive the order that starts software systems, the prompting user imports username and password; Whether legal according to the checking of the username and password in configuration information user, if the user is legal, start and the operating software system.
In order to protect operator or software developer's interests; The authentication module of present embodiment also is used to judge whether legitimacy of software systems, for example, judges that whether correct the sequence number of input etc.; If legal, trigger update module 58 and compare patch file and need the file of renewal whether to mate.
The patch update condition that present embodiment is set according to the user triggers patch and upgrades; Software systems will be automatically obtained and are upgraded patch from server, if patch upgrades failure, perhaps patch needs rollback; Software systems meeting automatic rollback patch recovers the environment before software systems are upgraded patch.The untimely problem with complex operation of the renewal that has caused when having solved manual update software patch has well guaranteed that the user upgrades the periodicity and the initiative of patch, simultaneously, changes artificial regeneration patch pattern, and system upgrades patch automatically; Even upgrade the patch failure, system also can fast automatic rollback patch, therefore has very strong practicality.
From above description, can find out that the present invention has realized the demand according to the user; System upgrades patch, automatic rollback patch automatically, and the first, guaranteed that the user upgrades the periodicity and the initiative of patch; The second, change artificial regeneration patch pattern, system upgrades patch automatically; The 3rd, even upgrade the patch failure, system also can fast automatic rollback patch.
Obviously, it is apparent to those skilled in the art that above-mentioned each module of the present invention or each step can realize with the general calculation device; They can concentrate on the single calculation element; Perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element; Thereby; Can they be stored in the memory storage and carry out, and in some cases, can carry out step shown or that describe with the order that is different from here by calculation element; Perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (12)
1. the method for a software systems renewal patch is characterized in that, comprising:
Whether the monitoring current time satisfies the renewal patch condition of the software systems that the user is provided with, if satisfy, the server address of the patch file that is provided with according to said user obtains patch file;
The file that said software systems needs upgrade is confirmed in patch file folder path according to said patch file and said user setting;
Whether more said patch file and the said file that needs to upgrade mate, if do not match, use said patch file to upgrade the said file that needs renewal.
2. method according to claim 1 is characterized in that,
The said patch file of said use upgrades before the said file that needs to upgrade, and said method also comprises: back up the file that said needs upgrade;
Using said patch file to upgrade the said file that needs to upgrade comprises: use said patch file to upgrade in the process of the file that said needs upgrade, interrupt if take place to upgrade, carry out rollback based on the said file of renewal that needs of backup.
3. method according to claim 2 is characterized in that, the said patch file of said use upgrades after the said file that needs to upgrade, and said method comprises:
In the said software systems operational process, receive said user's rollback order after, the file that upgrades according to the said needs of backup carries out rollback.
4. method according to claim 2 is characterized in that, the said patch file of said use upgrades after the said file that needs to upgrade, and said method comprises:
After moving the time that said software systems reach setting, the said file that upgrades of needing of pointing out that said user deletes backup;
After receiving said user's agreement deletion indication, the said file that need upgrade of deletion backup.
5. method according to claim 1 is characterized in that, the said patch file of said use upgrades before the said file that needs to upgrade, and said method comprises:
Judge whether said software systems are used, if point out said user to close said software systems;
After said software systems are closed, carry out the said patch file of said use and upgrade the said step that needs the file of renewal.
6. according to each described method of claim 1-5, it is characterized in that,
Whether said monitoring current time satisfies before the renewal patch condition of the software systems that the user is provided with; Said method also comprises: receive and preserve the configuration information of the said software systems of user's setting, said configuration information comprises: the path of upgrading server address, patch file folder and the said patch file folder of patch condition, patch file.
7. method according to claim 6 is characterized in that,
Said configuration information also comprises: said user's username and password;
Whether said monitoring current time satisfies before the renewal patch condition of the software systems that the user is provided with, and said method also comprises:
After receiving the order that starts said software systems, point out said user to import username and password;
Verify according to the said username and password in the said configuration information whether said user is legal,, start and move said software systems if said user is legal.
8. according to each described method of claim 1-5, it is characterized in that,
Before whether said patch file and the said file that need upgrade mated, said method also comprised:
Judge whether legitimacy of said software systems, if legal, the step whether file that carrying out more said patch file and said needs to upgrade matees.
9. according to each described method of claim 1-5, it is characterized in that said renewal patch condition is one of following:
The fixed time of appointed day and said software systems start the back operation and specify duration.
10. the device of a software systems renewal patch is characterized in that, comprising:
Monitoring modular is used to monitor the renewal patch condition whether current time satisfies the software systems of user's setting;
File acquisition module, the monitoring result that is used for said monitoring modular are when satisfying said renewal patch condition, and the server address of the patch file that is provided with according to said user obtains patch file;
The file determination module, the file that said software systems needs upgrade is confirmed in the patch file folder path that said patch file that is used for obtaining according to said file acquisition module and said user are provided with;
Update module, whether the file that is used for the renewal of more said patch file and said needs matees, if do not match, uses said patch file to upgrade the said file that needs renewal.
11. device according to claim 10 is characterized in that, said device also comprises:
Backup module is used to back up the file that the definite said needs of said file determination module upgrade;
First rollback module is used for using said patch file to upgrade the process of the file that said needs upgrade, and interrupts if take place to upgrade, and carries out rollback according to the file of the said needs renewal of backup.
12. device according to claim 11 is characterized in that, said device also comprises:
Second rollback module is used for said software systems operational process, receive rollback order after, the file that upgrades according to the said needs of backup carries out rollback.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105671663A CN102479092A (en) | 2010-11-30 | 2010-11-30 | Method and device for updating patch of software system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105671663A CN102479092A (en) | 2010-11-30 | 2010-11-30 | Method and device for updating patch of software system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102479092A true CN102479092A (en) | 2012-05-30 |
Family
ID=46091746
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010105671663A Pending CN102479092A (en) | 2010-11-30 | 2010-11-30 | Method and device for updating patch of software system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102479092A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064714A (en) * | 2013-01-08 | 2013-04-24 | 北京赛科世纪数码科技有限公司 | Software system updating method and software system updating device |
| CN103984574A (en) * | 2014-05-28 | 2014-08-13 | 能力天空科技（北京）有限公司 | Method and system for updating website |
| CN105094863A (en) * | 2014-05-07 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Application software upgrade processing method and device and mobile terminal |
| CN105224371A (en) * | 2015-10-21 | 2016-01-06 | 浪潮(北京)电子信息产业有限公司 | A kind of update method of storage management software and system |
| CN105247524A (en) * | 2013-05-31 | 2016-01-13 | 皇家飞利浦有限公司 | System and method for automatically uploading, downloading, and updating data such as sleep study data |
| CN105765908A (en) * | 2014-06-30 | 2016-07-13 | 北京新媒传信科技有限公司 | Method, client and system for multi-site automatic update |
| CN105426215B (en) * | 2015-12-11 | 2018-11-02 | 福建新大陆支付技术有限公司 | Payment terminal remote auto based on Ftp matches firmware updating service packs method |
| CN111930413A (en) * | 2020-05-22 | 2020-11-13 | 无锡中感微电子股份有限公司 | Automatic patch generation method, device and system |
| CN112698846A (en) * | 2020-12-30 | 2021-04-23 | 麒麟软件有限公司 | Method and system for automatically installing patch in Linux system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946032A (en) * | 2006-09-30 | 2007-04-11 | 华为技术有限公司 | Method for realizing patch management |
| CN101267336A (en) * | 2007-03-15 | 2008-09-17 | 中兴通讯股份有限公司 | Software version management method and system |
| CN101593118A (en) * | 2009-02-24 | 2009-12-02 | 浪潮集团山东通用软件有限公司 | A kind of software upgrade method flexibly |
| CN101661400A (en) * | 2009-09-16 | 2010-03-03 | 中兴通讯股份有限公司 | Method and device for managing software patches |
-
2010
- 2010-11-30 CN CN2010105671663A patent/CN102479092A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946032A (en) * | 2006-09-30 | 2007-04-11 | 华为技术有限公司 | Method for realizing patch management |
| CN101267336A (en) * | 2007-03-15 | 2008-09-17 | 中兴通讯股份有限公司 | Software version management method and system |
| CN101593118A (en) * | 2009-02-24 | 2009-12-02 | 浪潮集团山东通用软件有限公司 | A kind of software upgrade method flexibly |
| CN101661400A (en) * | 2009-09-16 | 2010-03-03 | 中兴通讯股份有限公司 | Method and device for managing software patches |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064714A (en) * | 2013-01-08 | 2013-04-24 | 北京赛科世纪数码科技有限公司 | Software system updating method and software system updating device |
| CN105247524A (en) * | 2013-05-31 | 2016-01-13 | 皇家飞利浦有限公司 | System and method for automatically uploading, downloading, and updating data such as sleep study data |
| CN105094863A (en) * | 2014-05-07 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Application software upgrade processing method and device and mobile terminal |
| CN103984574A (en) * | 2014-05-28 | 2014-08-13 | 能力天空科技（北京）有限公司 | Method and system for updating website |
| CN105765908A (en) * | 2014-06-30 | 2016-07-13 | 北京新媒传信科技有限公司 | Method, client and system for multi-site automatic update |
| CN105765908B (en) * | 2014-06-30 | 2019-07-19 | 北京新媒传信科技有限公司 | A kind of multi-site automatic update method, client and system |
| CN105224371A (en) * | 2015-10-21 | 2016-01-06 | 浪潮(北京)电子信息产业有限公司 | A kind of update method of storage management software and system |
| CN105426215B (en) * | 2015-12-11 | 2018-11-02 | 福建新大陆支付技术有限公司 | Payment terminal remote auto based on Ftp matches firmware updating service packs method |
| CN111930413A (en) * | 2020-05-22 | 2020-11-13 | 无锡中感微电子股份有限公司 | Automatic patch generation method, device and system |
| CN111930413B (en) * | 2020-05-22 | 2023-07-21 | 无锡中感微电子股份有限公司 | Automatic patch generation method, device and system |
| CN112698846A (en) * | 2020-12-30 | 2021-04-23 | 麒麟软件有限公司 | Method and system for automatically installing patch in Linux system |
| CN112698846B (en) * | 2020-12-30 | 2024-04-09 | 麒麟软件有限公司 | Method and system for automatically installing patches in Linux system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102479092A (en) | Method and device for updating patch of software system | |
| US20240086273A1 (en) | Systems and methods to reprogram mobile devices including a cross-matrix controller to port connection | |
| US7624394B1 (en) | Software installation verification | |
| CN101268620B (en) | Device management system and method for managing device management object | |
| CN103365683B (en) | For end-to-end patch automation and integrated method and system | |
| CN103635885B (en) | By providing the instant availability of prebuild environment to dispose the environment for testing | |
| US6971095B2 (en) | Automatic firmware version upgrade system | |
| CN104679534B (en) | System application installation package loading processing method, apparatus and terminal | |
| JP5444178B2 (en) | Backup / restore processing device, backup / restore processing method and program | |
| TWI570324B (en) | Method for configuring a wind energy installation, and wind energy installation | |
| CN105117263A (en) | UNIX environment software system upgrading method | |
| CN107147711A (en) | Application service update method and device | |
| CN102880478B (en) | Oftware updating method | |
| CN109710596B (en) | Data cleaning method, device, equipment and computer readable storage medium | |
| US20190372952A1 (en) | loT DATA COLLECTION SYSTEM, loT DATA COLLECTION METHOD, MANAGEMENT DEVICE, MANAGEMENT PROGRAM, AGENT DEVICE, AND AGENT PROGRAM | |
| JP2011175494A (en) | Maintenance work support system | |
| CN106708494A (en) | JAR upgrading method and apparatus | |
| CN109933351A (en) | A kind of method and apparatus of reparation and upgrading linux system | |
| Cisco | Administering the CiscoWorks2000 Server | |
| Cisco | Administering the CiscoWorks2000 Server | |
| Cisco | Administering the CiscoWorks2000 Server | |
| Cisco | Maintaining the Cisco 7204 | |
| CN112947951A (en) | Software installation method and related equipment | |
| CN102479093A (en) | Software installing system for providing verification and updating original file and register table and method thereof | |
| KR102221593B1 (en) | System for maintaining the installation envoronment of computer terminals |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120530 |