Summary of the invention
The objective of the invention is to overcome the deficiencies in the prior art and defective, fast automatic method for updating on a kind of line is provided, its purpose is to utilize one to upgrade version number, the date that log file stores the program of unusual fluctuation or renewal .... etc. information, and the program that these are up-to-date is put into enterprises end for the use side down loading updating.Use side also has the program that log file record always upgraded, and can compare on the enterprises end when upgrading and these two log files of use side doing, and decides on earth to upgrade which program.Enterprises end can be divided into first server end and second server end again, and first server is as internal cartulary; The second server end then is as external cartulary, and deposit be once to upgrade and be the program of latest edition, wherein some perhaps use side upgraded, and some does not upgrade as yet, but how to determine to upgrade which program? this moment, these two log files of second server end and use side were exactly very important comparison foundation, which is obtained is up-to-date and be the program of this less important renewal by specific comparison mechanism, use side need not just to worry that so which will upgrade many programs on earth like this, last just by some procotols with program updates to the local terminal computing machine.
For reaching above-mentioned purpose, the invention provides fast automatic method for updating on a kind of enterprises end inner wire, refer to be undertaken transmitting after the unusual fluctuation be updated to a second server end by program in one first server end, this method includes the following step:
At least one program has the unusual fluctuation state in this first server end;
Produce a more new record file and depositing in the catalogue;
Detect this second server end nearest archives update date;
All programs of having upgraded after this second server end down loading updating date; And
This second server end record file that same version is older is deleted.
For reaching above-mentioned purpose, the present invention also provides fast automatic method for updating on a kind of enterprises end outer lines, refers to that transmitting up-to-date program to a use side by a server end upgrades, and this method includes the following step:
Whether the special parameter of a record in the file of comparing this this program of use side be less than the special parameter in the record file of this this program of server end;
This use side is downloaded the program of this server end and is upgraded; And
Upgrade a special parameter of noting down in the file of this this program of use side.
Thus, the user just can utilize the regular update program of more newly arriving on this line, because can get up-to-date program in the process of upgrading, it is the old edition program that the user just need not worried whether oneself execution, in addition also can not need be upgraded the relative setting of data in directly can refresh routine at start context.So will make the running of system more stable, and the user need not make a phone call to want new procedures with serving the people yet, so save client's time, and service department also can reduce cost of serving; The present invention also provides a kind of method to save the space that the second server end is deposited refresh routine in addition, and guarantees only to deposit up-to-date refresh routine.
Embodiment
The present invention is a fast automatic method for updating on a kind of line, please refer to Fig. 1, and the system architecture synoptic diagram for automatic update method on the line of the present invention is described as follows:
As shown in the figure, enterprises end 40 provides first server end 20 to handle different refresh routines with second server end 30, and first server end 20 can utilize extensible indicating language (eXtensible Markup Language in the program with modification or unusual fluctuation; XML) store the information of refresh routine,, just note down file by extensible indicating language (eXtensible Markup Language as the program updates log file; XML) form and any form of depositing store.And the record file of first server end 20 can comprise following parameters: a program name (Name), a program version (Version), are set up the date parameter that (Create), revises date (Modify), a program size (Size) and a program format (Type) and a download state (Update), and the parameter of download state (Update) can be upgraded after second server end 30 is downloaded successfully.
Second server end 30 also has a record file, and comprise following parameters: a program name (Name), a program version (Version), are set up the date parameter that (Create), revises date (Modify), a program size (Size) and a program format (Type) and a last Docket No. (Max), and the parameter of last Docket No. (Max) is upgraded after also finishing according to 30 downloads of second server end.First server end 20 provides by same enterprises end 40 with second server end 30, in addition the transmission mode of 30 at first server end 20 and second server end can in the enterprise by choosing one in internet (Internet) and Intranet (Intranet) transmission manner wantonly.
Use side 10 then is meant the user of down loading updating demand, and a record file also is provided, and this record file is also by extensible indicating language (eXtensible Markup Language; XML) form stores, and more comprises following special parameter: a last Docket No. (Max), a program name, a program version, are set up the date, one and are revised date, a program size and a program format; And second server end 30 can be transmitted by any network kenel with use side 10, as: File Transfer Protocol (File Transfer Protocol; FTP), super document host-host protocol (HyperText Transfer Protocol; HTTP) mode of world-wide web (Internet) remote connection.
Then see also Fig. 2, Fig. 2 is the process flow diagram of automatic update method on the enterprises end inner wire of the present invention.
At first the procedure service personnel of enterprises end 40 can carry out a unusual fluctuation behavior (step 100) at least one program in one first server end 20, this unusual fluctuation behavior can be newly-increased and revises two kinds of patterns, after unusual fluctuation is finished, just produce a more new record file and depositing in the particular category (step 110), this particular category refers in the date catalogue of same version, deposit finish after, begin to detect nearest archives update date (step 120) of a second server end 30, just have a nearest update date, all programs (step 130) of having upgraded after these 30 down loading updating dates of second server end then, this moment, the refresh routine of first server end 20 just can be sent to second server end 30, this second server end 30 record file that same version is older is deleted (step 140) at last, to save the storage area, also avoid the user to hold the program of 10 repeated downloads old editions, second server end 30 also can be revised some specific parameters in addition, allow afterwards to convenient comparison in use side 10 process of downloading, and this specific parameter, mention at the 1st figure, do not give unnecessary details at this.
Next, please see Figure 3, be the process flow diagram of automatic update method on the enterprises end outer lines of the present invention.
At first just, whether begin to compare a special parameter in a use side 10 record files less than the special parameter (step 200) in these second server end 30 record files, the special parameter of this comparison refers to last Docket No. (Max) parameter, this parameter can introduced thereafter in detail, when last Docket No. (Max) parameter in the use side 10 record files is not noted down last Docket No. (Max) parameter of files less than second server end 30, just represent the use side 10 need not down loading updating, second server end 30 does not have newer program to download, just come back to step 200, allow use side 10 continue to wait for; When if last Docket No. (Max) parameter in the use side 10 record files is determined less than last Docket No. (Max) parameter of second server end 30 record files, then use side 10 just needs to begin to upgrade, this use side 10 is downloaded the program of this second server end 30 and is upgraded (step 210), after program updates is finished, a last special parameter (step 220) that just upgrades in these use side 10 record files, last Docket No. (Max) parameter is revised, revised according to use side 10 down loading updatings several programs and decided.
In addition, first server end 20 can be two machines with second server end 30 and forms, also first server end 20 can be positioned over same machine with second server end 30, Each performs its own functions with second server end 30 but its spirit is for allowing first server end 20, and employed machine or equipment are not just added all restrictions.
Enumerate an embodiment in order to effect of the present invention to be described at this,, be the archives catalog synoptic diagram of the present invention's first server end earlier with reference to Fig. 4-a.
In first server end 20, archives catalog meeting elder generation is according to the version of program, to have then the program of unusual fluctuation put into different categories and regularly be placed under the date catalogue in, have in each date catalogue then the program of log file record unusual fluctuation version number, revise the date ... etc. relevant information.As Fig. 4-a, this enterprises end record has extensible indicating language (eXtensible MarkupLanguage; XML) with dynamic link routine library (Dynamic Link Library; DLL) two types archives provide refresh routine.
One log file is also arranged on the second server end 30, can write down be to get which date catalogue last time when first server end 20 is obtained recent program in this record file, as long as we write this date down, and search greater than all date catalogues of this date to first server end 20, by internal network up-to-date program is put on the second server end 30, when if the program that desire is upgraded has been present in first server end 20, second server end 30 old edition program replacings can be become latest edition and amendment record file, what in other words deposit in first server end 20 is the program (comprising the renewal with the Zhi Chengxu different editions) that unusual fluctuation is always arranged, and second server end 30 is put is up-to-date program, so far up-to-date program has been ready to wait for that use side 10 upgrades on online.
Follow 4-b with the aid of pictures then, for the present invention's first server end upgrades preceding record file structure figure, as figure Fig. 4-b, Here it is, and first server 20 has been revised the program of finishing, preparation is sent to second server end 30, and first server, 20 distinctive parameters, download state (Update) presents: the state of False, representative also are not updated to second server end 30; Existing statement before each parameter name among the figure.4-c with the aid of pictures then is for second server end of the present invention upgrades preceding record file structure figure.
After execution of step 100 arrives step 140, continue to consult Fig. 4-d, be record file structure figure and Fig. 4-e after the present invention's first server end upgrades, be the record file structure figure after second server end of the present invention upgrades.
The difference of examination comparison diagram 4-b and Fig. 4-d, Fig. 4-c and Fig. 4-e.On behalf of this program, the state that has only download state (Update) to become True by the state of False among Fig. 4-b and Fig. 4-d upgraded by second server end 30 and is finished; And Fig. 4-c and Fig. 4-e, second server end 30 log files are original<F00000001〉and the value of record also has the record of this Zhi Chengxu old edition because of this time renewal, therefore last one edition record can be deleted, can many<F000000002 and this time upgrade〉which refresh routine record this time have, the Max value is also more remarkable have been changed, therefore as can be known the log file of second server end 30 record be the program of latest edition, if the renewal of different editions is arranged with Zhi Chengxu, then the record of old edition can be deleted, thus can guarantee that use side 10 gets be up-to-date program and can not repeat to upgrade.
Continue now 5-a with the aid of pictures, be the archives catalog synoptic diagram of use side of the present invention, be to use identical framework as same Fig. 4-a, what just deposit is the program of upgrading.
Use side 10 is carried out when upgrading on the line, can compare with the Max value of use side 10 log files and the Max value of second server end 30 log files, when if the Max value of use side 10 is also littler than the Max value of second server end 30, the program of representing Shang You not upgrade, upgrade the operation meeting on the line and get that the Max value is downloaded to use side 10 by FTP or HTTP with the archives on the second server end 30 and does renewal than the archives in the also big node of the Max value of use side 10 in the log file of second server end 30.
The then record file structure figure that compares for second server end of the present invention and use side for record file structure figure, Fig. 5-c of use side of the present invention before upgrading of Fig. 5-b and Fig. 5-d record file structure figure after for use side renewal of the present invention.
Now comparison diagram 5-b and Fig. 5-d, upgrade finish after, the log file of use side 10 can be updated as follows, the meeting of comparing with old data is many<F00000002 data, also be program record of renewal this time, the Max value also is changed.The data that log file write down of use side 10 log files and second server end 30 almost is living in fact, different is, the log file of second server end 30 only writes down up-to-date part to same Zhi Gengxin program repeatedly, and the log file of use side 10 then can be with the record deletion that repeats to upgrade.
But set forth the effect of fast automatic renewal on the present invention's line again for an embodiment at this.Before explanation, suppose a situation earlier, be under the state of regular update, provide a download area for user's down loading updating program, and if be the state of the end of month (31 days) at present, 5 programs have been upgraded till now altogether from the beginning of the month, and yesterday till now without any refresh routine, the foundation that traditional way may number compare with date or version, and the result who causes is that to have done the renewal and the inspection speed that repeat slow.Log file (user A, user B judge usefulness) and three different situations of using on the Server are provided below, can reach best efficient with illustrated emphasized update mode provided by the present invention.
The renewal course of this month is as follows:
09/01?A01.dll
09/01?A02.dll
09/01?A03.dll
09/01?A04.dll
09/11?A02.dll
09/11?A03.dll
09/19?A02.dll
09/19?A03.dll
09/23?A02.dll
09/23?A03.dll
Though above record has been listed as renewal repeatedly, but in fact only done the renewal of 4 programs of A01.A02.A03.A04, and A02.A03 has upgraded three times at 9/11.9/19.9/23 more respectively, when upgrading A02.A03 with actual state, only need get upgrading of 9/23 this edition in fact and get final product, following example will show the tradition renewal and utilize renewal provided by the invention which great difference is arranged.
The program of the log file record this month renewal on the Server is judged with (traditional way) for user A, user B renewal
<unusual fluctuation date=2002-09-05〉<File=A01.dll Dir=DLL Date=2002-09-01〉<File=A02.dll Dir=DLL Date=2002-09-01〉<File=A03.dll Dir=DLL Date=2002-09-01〉<File=A04.dll Dir=DLL Date=2002-09-01 〉 |
<unusual fluctuation date=2002-09-11〉<File=A02.dll Dir=DLL Date=2002-09-10〉<File=A03.dll Dir=DLL Date=2002-09-10〉<unusual fluctuation date=2002-09-19〉<File=A02.dll Dir=DLL Date=2002-09-15〉<File=A03.dll Dir=DLL Date=2002-09-17〉<unusual fluctuation date=2002-09-22〉<File=A02.dll Dir=DLL Date=2002-09-20〉<File=A03.dll Dir=DLL Date=2002-09-21 〉 |
Updating form after the improvement: in producing more new record, because can judge forward and have or not identical program, the words that have can delete record before, only write down last update, therefore form following more new record.
<Fsp> <F00000000?Modify=″20011231″Max=″F00000004″/>
<F00000001>
<File?Name=″A01.dll″?Version=″1.0.0.0″?Create=″2002-09-01″
Modify=″2002-09-01″Size=″100K″Type=″DLL″/>
<File?Name=″A04.dll″?Version=″1.0.0.0″?Create=″2002-09-01″
Modify=″2002-09-01″Size=″100K″Type=″DLL″/>
</F00000001>
<F00000002/>
<F00000003/>
<F00000004>
<File?Name=″A02.dll″?Version=″1.0.0.0″?Create=″2002-09-01″
Modify=″2002-09-23″Size=″105K″Type=″DLL″/>
<File?Name=″A03.dll″?Version=″1.0.0.0″?Create=″2002-09-01″
Modify=″2002-09-23″Size=″108K″Type=″DLL″/>
</F00000004>
</Fsp>
1, user A-did not once upgrade till now from the beginning of the month yet
First, traditional method: get off from the version sequential update of grabbing program and comparing program one by one the beginning of the month according to log file, done 10 times renewal altogether, so that can do the renewal of repetition during with the Zhi Chengxu different editions.
Second, improvement way: owing to same program in the inventory after the improvement only keeps the data of last unusual fluctuation, so this user only need do 3 times renewal.
2, user B-hypothesis was 9/27 and did more new element yesterday
First, traditional method: system need compare the version number of program one by one so that understand and whether to have archives to need to upgrade, and when archives quantity was increasing, the time of inspection also increased relatively.
Second, improvement way: a unusual fluctuation code name is provided, whether only need removes to judge own last unusual fluctuation code name less than the unusual fluctuation code name on the main frame in the time of therefore each the inspection, system just knows whether that needing to download archives upgrades.
Relatively user A and user B when using traditional way to upgrade, are not to download duplicated files in a large number, otherwise can compare the version number of program exactly one by one and the situation that repeats to upgrade is arranged; Review and utilize update mechanism of the present invention, do not need to go one by one comparison version number, as long as judge that a unusual fluctuation code name is just passable,, and can not lose time and download a large amount of programs and do the action that repeats to upgrade on the speed of checking and come efficiently fast than traditional approach on the benefit.
Though the present invention discloses as above with aforesaid preferred embodiment; right its is not in order to limit the present invention; anyly be familiar with this operator; without departing from the spirit and scope of the present invention; when can doing a little change and retouching, thus protection scope of the present invention when with the scope of claims the person of being defined be as the criterion.