JPH1021061A - Automatic version-up system for client software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately perform version-up of files on a client computer, and automatically add deficient files and delete unnecessary files. SOLUTION: A version-up file determining means 21 acquires information lists from a client-side version information table 31 and a master version information table 32 and compares them with each other, and determines files to be subjected to version-up by referring to information of files themselves stored in a file device CF, and a deficient file determining means 22 and a file determining means 23 also perform inspection similarly to determine deficient/ unnecessary files. A version-up execution means 24 makes alterations in the file device CF on the basis of the information determined by the said respective means and also makes alterations in the information tables so as to maintain their consistency.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an automatic version upgrade method for client / server type client software, and more particularly to a WAN (Wide Area).
Network), a large number of client computers and database server computers are connected, and the program execution environment stored in each client computer is managed in the same manner based on the contents of the program execution environment of the client computers stored in the database server computer. Related to an automatic client software version upgrade system.

[0002]

2. Description of the Related Art Conventionally, in this type of client software automatic version upgrade system, a client computer uses a LAN (Local Area Network).
k) and in an environment where many are connected on a WAN, it is used to maintain and manage the same program files, data files, etc., existing on each client computer.

As an example of a conventional client software automatic version upgrade system, see, for example,
Japanese Patent Publication No. 280342 proposes a configuration of a program management method in which each workstation can download only necessary files from a master file stored in a file server connected via a LAN.

That is, in the client software automatic version upgrade system described in the above publication, each client computer notifies a file server computer of a file name of a program file read and designated from a master file, and the file server computer For a program file having the same file name as the file name notified from the computer, a catalog file including list information of information on the version of the file stored in the master file is formed and notified to the client computer.

[0005] The client computer judges the contents of the catalog file notified from the file server computer and information on the version of the stored program file, judges the updated program file, and based on the judgment result, The file server computer notifies the file server computer of download file information including a list of file names of program files read from the master file.

[0006] The file server computer reads a program file specified by the download file information notified from the client computer from the master file, and transmits the read program file to the client computer. The stored program file is updated by the program file received from the server computer.

[0007]

However, in the conventional client software automatic version upgrade system, since addition / deletion of a file is not considered at all, a necessary file cannot be automatically added. There is a problem that unnecessary files cannot be automatically reduced. For this reason, management for maintaining consistency between the file on the client computer and the master file of the file server computer becomes complicated, and this problem becomes more serious with the increase in the number of client computers connected to the file server computer for communication. It becomes something.

Accordingly, the present invention has been made in view of the above circumstances, and an object of the present invention is to provide an automatic client software version-up system capable of automatically adding necessary files. Another object of the present invention is to provide an automatic client software version-up system capable of automatically deleting unnecessary files.

[0009]

In order to achieve the above object, an automatic client software version upgrade system according to the present invention checks version information of a client and version information of a master file, and executes a process on a client computer. Means for comparing files of the actual files stored in the file device with each other, determining a file to be upgraded, determining a missing file, and determining an unnecessary file based on the result of the comparison. In response to the determination of the above means, selectively performing a file version-up process, a fetching process for a missing file, and a process for deleting an unnecessary file, and updating the contents of the file device on the client computer. In response to this update, the database on the database server Characterized in that it comprises a means for updating the contents of the scan.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below. In a preferred embodiment of the present invention, the master file version information (FIG. 1) stored in a table configuration (3 in FIG. 1) on a database device (DF in FIG. 1) of a database server computer (1 in FIG. 1). 1-32), the version information on the client side (31 in FIG. 1), and the file information of the real file stored in the file device (CF in FIG. 1) of the client computer (2 in FIG. 1) are mutually checked. In this way, the operation of the version upgrade process is determined.

More specifically, in the embodiment of the present invention, a version upgrade file determination for determining a file to be upgraded based on a result of collation between each of the above-mentioned version information and information of an actual file. Means (21 in FIG. 1), missing file determining means (22 in FIG. 1) for determining missing files, and unnecessary file determining means (23 in FIG. 1) for determining unnecessary files. Version upgrade executing means (24 in FIG. 1) for performing version upgrade processing according to the processing determined by each means.

In the embodiment of the present invention, the version information of the file stored in the file device of the client computer is stored in the client side version information table (31 in FIG. 1). In the master version information table (32 in FIG. 1), version information of a file to be stored in the file device of the client computer is stored. In the master file storage table (33 in FIG. 1), the substance of the file to be stored in the file device of the client computer in association with the master version information is stored.

Version upgrade file determination means (FIG. 1)
21) obtains an information list from the client-side version information table (31 in FIG. 1) and the master version information table (32 in FIG. 1), and determines the file to be upgraded by comparing both. At this time, the file device of the client computer (C in FIG. 1)
The determination is also made with reference to the information of the real file stored in F).

The missing file determining means (22 in FIG. 1) of the client computer (2 in FIG. 1) performs the same processing as described above to determine a file to be taken. The unnecessary file determining means (23 in FIG. 1) performs the same processing as described above, and determines a file to be deleted.

Version upgrade execution means (24 in FIG. 1)
Performs file update / addition / deletion processing on a file in the file device (CF in FIG. 1) based on the information determined by each of the above means.

At this time, if necessary, the client computer is sent from the master file storage table (33 in FIG. 1) via the DBMS (11 in FIG. 1) of the database server computer (1 in FIG. 1). Retrieve files to send.

In accordance with processing such as updating, adding, or deleting a file on the client computer, the client-side version information table (31 in FIG. 1) and the master version information table (32 in FIG. 1) on the database device (DF). The operation is performed on the client side version information table (31 in FIG. 1) so that the contents of ()) are equal to each other.

In order to explain the above-described embodiment of the present invention in more detail, embodiments of the present invention will be described below in detail with reference to the drawings.

Referring to FIG. 1, in a first embodiment of the present invention, a database server computer 1 and a client computer 2 are connected to a LAN / WAN, and a database device DF and a file device CF, respectively.
It has.

In the database server computer 1, D
BMS (Data Base Management System) 11
Comprises a general database management system, and has a mechanism for managing a database configured in the database device DF.

The table configuration 3 shown in FIG. 1 corresponds to a database device DF connected to the database server computer 1.
This shows an example of the configuration of the database table constructed above, and the client-side version information table 3
1, a master version information table 32, and a master file storage table 33.

Client side version information table 3
1 stores information on files introduced into the file device CF of the client computer 2, and the management information includes, for example, information such as the actual file name, file size, update date and time, and version.

The master version information table 3
2 stores information on files to be introduced into the client computer 2 in a client-side version information table 3
The information is stored in advance together with the same management information as that of the information No. 1.

Then, the master file storage table 3
3 stores the substance of the file in association with the master version information.

Referring to FIG. 1, the client computer 2 according to the embodiment of the present invention includes an upgrade file determining unit 21, a missing file determining unit 22, an unnecessary file determining unit 23, and a version executing unit 24. ,
It is provided with.

Version upgrade file determining means 21
Obtains required data from the client-side version information table 31 in the database device DF via the DBMS 11 on the database server computer 1. Similarly, required data is obtained from the master version information table 32.

Version upgrade file determining means 21
Compares and compares these two sets of data, and as a result, if the management information does not match each other, determines that a version upgrade is necessary. Even if the two sets of data match each other, the data is compared with the information of the real file stored and stored in the file device CF, and if it does not match the information of the real file, a version upgrade is required. Judge.

The missing file determination means 22 acquires predetermined data from the database device DF via the DBMS 11 of the database server computer 1 in the same manner as the upgrade file determination means 21, and stores the data in the master version information table 32. If there is (file information) and no data exists in the client side version information table 31, it is determined that the data is insufficient. Further, even if data exists in the client-side version information table 31, it is confirmed whether or not an actual file exists in the file device CF.

The unnecessary file deciding means 23 acquires data in the same manner as the above-mentioned upgrade file deciding means 21. The client side version information table 31 has data (file information), and the master version information table 32 has data. If the file does not exist, it is determined that the file is unnecessary.

The upgrade execution means 24 is based on the upgrade information determined by each of the above means.
If a version upgrade is required, the master file is acquired from the master file storage table 33 on the database device DF via the DBMS 11, and the version upgrade target file existing in the file device CF is updated. At this time, the content of the client side version information table 31 in the database device DF is updated via the DBMS 11 so as to match the master version information table 32 and the information of the file device CF.

If the client computer 2 determines that the file is insufficient, the database device D is transmitted via the DBMS 11 in the same manner as described above.
The master file is acquired from the master file storage table 33 of F and stored in the file device CF. Also,
At the same time, the contents of the client side version information table 31 are configured and registered so as to match the master version information table 32 and the information of the file device CF.

If the file stored in the file device CF of the client computer 2 is unnecessary, the corresponding file existing in the file device CF is deleted. At this time, the corresponding information in the client side version information table 31 on the database device DF of the database server computer 1 is deleted.

Next, the operation of the embodiment of the present invention will be described with reference to the flowcharts of FIGS.

Version upgrade file determining means 21
Acquires a list of version information for itself from the client side version information table 31 via the DBMS 11. Similarly, a list of version information of the master file is acquired from the master version information table 32.

The difference between the two sets of information is obtained, and if the information does not match in the same key item, it is determined that the version needs to be upgraded. Further, even if the information matches, the actual file existing in the file device CF may have been updated for some reason. The difference between the file and the corresponding information in the list of version information is calculated, and if the information does not match, it is determined that the version needs to be upgraded (steps S1 and S2).

Using the list of files that need to be upgraded determined in the above steps, the upgrade executing means 24 acquires the file from the master file storage table 33 via the DBMS 11, and stores the file in the file device CF. Update files. At the same time, the information in the client side version information table 31 is set so as to match the master version information table 32 and updated (step S3).

Next, the missing file determining means 22 uses the list of two sets of information obtained in the above step, and uses the list of master file information, but the list of version information on the client side. If it does not exist, it is determined that it is insufficient. If the corresponding real file exists in the file device CF for some reason but does not exist in the list of version information on the client side, it is insufficient, but the file acquisition is unnecessary. (Steps S4 and S4)
5).

Using the list of missing files determined in the above steps, the version upgrade execution means 24
Master file storage table 3 via BMS11
3 to obtain a file and store it in the file device CF. At this time, files that are determined to be unnecessary are not obtained. In addition, the information in the client side version information table 31 is configured to match the master version information table 32 and registered (step S6).

The unnecessary file determining means 23 uses the two sets of information lists (a list of master file version information and a list of client computer version information) acquired in the above-described steps to obtain version information on the client side. , But not in the master file version information list,
It is determined that the file is unnecessary. In addition, when the corresponding real file exists in the file device CF for some reason but does not exist in the master file information list, it is determined that the file is unnecessary (steps S7 and S8). .

Using the unnecessary file list determined as described above, the version upgrade executing means 24 deletes unnecessary files existing in the file device CF (step S9). In addition, the information of the client side version information table 31 is deleted via the DBMS 11 so as to match the master version information table 32.

Next, the function and effect of the embodiment of the present invention will be described.

In the above-described embodiment of the present invention, the necessity of version upgrade is determined based on a comparison between the master version, the client-side version, and the actual file, so that version control can be performed accurately.

In addition, the presence or absence of a missing file is determined in the same manner, and the necessity of acquiring the file is determined. Therefore, when the file is not necessary, the file is not acquired. It can be used.

Further, the presence / absence of unnecessary files is determined in the same manner, and unnecessary files are deleted from the file device of the client computer, so that the free storage capacity can be increased.

[0045]

As described above, according to the present invention,
The following effects are obtained.

The first effect is that only storing the master file version information and the corresponding master file in the database on the database server computer allows the file version in the file device on each client computer to be stored. It means that management can be done accurately.

The reason is that, in the present invention, the version management information of the client computer and the version management information of the master file are stored and held in the database on the database server computer, and the file management information and the file of the client computer are stored. This is because the file information of the actual file existing in the device is compared with each other, and the file to be upgraded is determined.

As a second effect of the present invention, the necessity of file acquisition is determined and the file to be acquired is determined. Therefore, when file acquisition is not required, the processing speed is reduced and the communication line is reduced. This means that it is possible to effectively utilize the information.

Further, a third effect of the present invention is that, since the file to be deleted is determined from the file device of the client computer, unnecessary files existing on the file device of the client computer are automatically deleted. As a result, the file device can be prevented from being occupied by useless files, the free space can be increased, and the file space can be effectively used.

[Brief description of the drawings]

FIG. 1 is a diagram for explaining a configuration of an embodiment of the present invention.

FIG. 2 is a flowchart for explaining the operation of one embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Database server computer 11 Database management system 2 Client computer 21 Upgrade file determination means 22 Insufficient file determination means 23 Unnecessary file determination means 24 Upgrade execution means 3 Table configuration 31 Client side version information table 32 Master version information table 33 Master file storage Table CF file device DF database device

Claims (3)

[Claims] 1. A method for comparing version information of a client with version information of a master file, and matching information of a real file stored in a file device on a client computer with each other. Means for deciding a file to be upgraded, means for deciding a missing file, and means for deciding an unnecessary file. Means for selectively executing an import process and an unnecessary file deleting process to update the contents of the file device on the client computer, and updating the contents of the database on the database server computer in response to the update. Automatic client software version upgrade system 2. The list of version information of the master file includes a list of version information on the client side and a version of the master file. If the file exists and does not exist in the list of version information on the client side, it is determined that the file is insufficient, and the actual file exists on the client computer. 2. The automatic client software version upgrade system according to claim 1, wherein it is determined that acquisition of the file is unnecessary if the file does not exist in the version information list on the side. 3. The means for deciding a file to be upgraded includes: version information on the client side;
The master file and the version information of the master file are compared and collated with each other. If these pieces of information do not match each other, it is determined that a version upgrade is necessary, and the two sets of information match each other. The information of the real file stored in the file device of the client computer, and if the information does not match the information of the real file, it is determined that a version upgrade is necessary. Item 2. An automatic client software version upgrade system according to Item 1.