JPH07334436A - Automatic distribution system for software - Google Patents

Abstract

PURPOSE:To simply and surely distribute software to plural computers connected to a network. CONSTITUTION:A host computer 10 to be a transmitting source of software and an intermediate host computer 20 are respectively provided with load detecting parts 11, 21, which detect the communication load of respective networks 42, 44 and transmit software when the communication load of the each network is comparatively small. Each of dividing parts 13, 23 divides the software into transmitting units less than a prescribed size and then distributes the divided software. Thereby, the probability of a distribution failure due to a fault generated in the network or the like can be reduced. In addition the unitary management of software can be executed by collectively managing software to be distributed and its set information as one package.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software automatic distribution system for distributing software used in a terminal computer from a host computer in a network system.

[0002]

2. Description of the Related Art Conventionally, in a relatively large-scale network system, when distributing software to each terminal computer, a medium such as a magnetic disk or a magnetic tape is used, and an operator uses each terminal computer for each terminal computer. It was common to do an installation.

However, in such a method, it is necessary to register or replace the software for each terminal computer, which requires a large number of engineers having specialized knowledge. Further, in a computer system in which a large number of computers are distributed, it is very difficult to replace the software for each of the computers at the same time, and the installation work time consumed by the workers is enormous as the number of terminal computers increases. There was a problem such as a thing.

As a means for solving these problems, an automatic software distribution system has been devised in which software is automatically distributed between interconnected computers using a communication medium.

An example of such a system is shown in FIG.
There is a software automatic distribution method as shown in FIG. The flow of operation of the software automatic distribution method of FIG. 13 will be described below.

(1) A computer administrator uses a server (host)
An application program 66 for distribution is put in the storage device 64 of the computer 60.

(2) The installation program 68 is transferred from the transmission program 62 on the server computer 60 to the reception program 72 of each client (terminal) computer 70 by the command input of the administrator.

(3) The server computer 60 transfers the application program 66 from the transmission program 62 in response to a command input by the administrator.

(4) The client computer 70 starts the distributed installation program 68 and installs the transferred application program 66.

(5) The installation result is displayed on the server computer 6
Report to 0.

With such a configuration and processing operation, it is possible to transfer and install the application program to the specific client computer 60.

Similarly, as a technique relating to a system for automatically distributing software, for example, Japanese Patent Laid-Open No.
286345 "Software upgrade method" and Japanese Patent Laid-Open No. 4-96159 "Network system". According to these methods, (a) means for storing software on a computer connected to a network (b) means for storing distribution destinations (c) means for distributing to distribution destinations stored in (b) at the time of version upgrade By providing the, automatic software distribution is realized.

[0013]

In the conventional automatic software distribution method, when the size of the software to be distributed is large or the number of terminal computers to be distributed is extremely large, the load on the network increases. There was a case where it interfered with the actual operation.

Further, according to the conventional automatic software distribution method, when the software is not normally distributed due to the stop of the power supply of the terminal computer or the overload or failure of the network when distributing the software, the software is distributed on the same network. Different versions of software will be mixed. In this case, inconvenience in operation may occur such as loss of integrity of data generated when the software is used.

Further, in the conventional automatic software distribution method, when the software to be distributed is a new version of the existing software, the old version is lost due to the installation of the new version, so that the old version cannot be used. However, if a defect is found in the new version installed in this way, it may be necessary to temporarily restore the old version in order not to interrupt work. In this case, there is a problem that the new version once installed must be completely removed so as not to affect others, and the old version must be installed again. Further, during the revision work, there is a problem that both the new edition and the old edition cannot be used.

Further, in order to use the distributed software, other software may be required depending on the dependency between the software. For example, when software compatible with the window system is distributed, a window system program is required to use the software. In such a case, it is necessary to distribute the software so that all the software required to operate the distributed software are available.
However, in the case of a system in which there are multiple types of software that can be distributed and each terminal computer selects the software that it wants to be distributed and receives the distribution (selective distribution method), the individual terminal computers on the receiving side The status of the software that the company already has is not always constant. In such a case, in the conventional automatic software distribution method, the computer administrator on the receiving side may have other software necessary for executing the software to be distributed depending on the situation of each computer. I was checking whether or not to do it. And if such other software exists, you must check whether you have such other software, and be careful to have all the necessary software. There was a problem that the work became very complicated.

The present invention has been made to solve the above problems, and an object of the present invention is to obtain an automatic software distribution system which can reduce the load on the network and can surely distribute software.

It is another object of the present invention to provide an automatic software distribution method capable of maintaining the consistency of data among terminal computers even when software is not normally distributed.

Another object of the present invention is to provide an automatic software distribution system which enables a prompt restoration of the old version when a defect is found in the new version during revision. A further object of the present invention is to obtain a software automatic distribution method capable of distributing the minimum necessary software in response to a usage request from a terminal computer.

[0020]

In order to achieve the above object, an automatic software distribution method according to the present invention is a distribution source computer and a plurality of distribution destination computers connected to the distribution source computer via a network. And a size of software to be distributed to the distribution source computer, the communication load detecting unit detecting the communication load amount of the network, and the communication load amount detected by the communication load detecting unit. And a transmission propriety determination means for determining whether it is possible to transmit the distribution target software through the network,
It is characterized in that the distribution source computer transmits the distribution target software to the distribution destination computer only when the transmission availability determination unit determines that the transmission is possible.

Further, the distribution source computer is provided with software dividing means for dividing the distribution target software into transmission units of a predetermined size or smaller, and when the distribution target software is larger than the predetermined size. Is a software combining unit that divides by the software dividing unit and transmits for each transmission unit, and combines the received transmission unit with the distribution destination computer to restore the original distribution target software form. Is provided.

Further, the distribution source computer is provided with setting information registration means for registering setting information including a distribution destination of the distribution target software and a distribution retry interval, and registering the setting information for each distribution target software. Is characterized by.

Further, the distribution source computer is provided with a package creating means for collecting the distribution target software and the setting information of the distribution target software into one package, and a package storing means for storing the package. The software to be distributed is managed in package units.

Further, each distribution destination computer is provided with a reception completion notifying means for transmitting a reception completion signal to the distribution source computer when the reception of the distribution target software is normally completed, and the distribution source computer is provided with: Based on the presence or absence of a reception completion signal from each distribution destination computer, a distribution status table creating means for creating a distribution status table showing the distribution status of the distribution target software in each distribution destination computer is provided, and the distribution source computer It is characterized in that a distribution status table is created for each distribution target software, and distribution processing is retried to a distribution destination computer that has not been distributed based on this distribution status table.

The distribution destination computer communicates with the distribution source computer when receiving a software execution command,
From the distribution status search means for searching the distribution status of the software from the distribution status table, and the distribution status of the software searched by the distribution status search means,
When it is found that the software is an old version of the software currently being distributed, it has a warning means for outputting a warning message indicating that the software is an old version.

Further, when the distribution source computer distributes the distribution target software, the distribution target already stored in the storage device of the distribution destination computer as an installation position in the storage device of the distribution destination computer. The distribution destination computer has an installation position setting means for setting a position different from the installation position of the old version of the software, and the distribution destination computer sets the distribution target software to the existing software based on the installation position instruction from the distribution source computer. It is characterized in that it is stored in a different location from the old version.

Further, the distribution source computer creates, for each distributable software, a dependency relationship list creating means for creating a dependency relationship list describing other software required to execute the software, Dependency relationship list storage means for storing the dependency relationship list created by the dependency relationship list creating means for each of the distributable software, and the dependence on the software indicated by the selection signal received from the distribution destination computer. Dependency list transmitting means for reading out the relation list from the dependency list storage means and transmitting it to the distribution destination computer, and distributing the software indicated in the request list received from the distribution destination computer to the distribution destination computer. And a software distributed by the distribution-destination computer. The desired software is selected from the possession list describing the distribution list, the distribution list describing the software that can be distributed by the distribution source computer, and the software described in the distribution list. Software selection means for transmitting a selection signal indicating software to the distribution source computer, and comparing the dependency list and the possession list received from the distribution source computer,
Distribution request means for searching for software that needs to be distributed from the software listed in the dependency list, collecting them in a distribution request list, and transmitting the distribution request list to the distribution source computer. It is characterized by having.

The distribution source computer is a host computer of a network system composed of a host computer and a plurality of terminal computers, and the distribution destination computer is a terminal computer of the network system.

The distribution source computer is a host computer of a network system composed of a host computer, a plurality of intermediary host computers, and a plurality of terminals, and the distribution destination computer is an intermediary host computer of the network system. It is characterized by

The distribution source computer is a mediation host computer of a network system composed of a host computer, a plurality of intermediary host computers, and a plurality of terminals, and the distribution destination computer is a terminal computer of the network system. It is characterized by

[0031]

In the automatic software distribution method according to the present invention, when the distribution source computer distributes the distribution target software to a plurality of distribution destination computers, the communication load detection means detects the communication load amount of the network, and the transmission availability determination means. But,
Based on the detected communication load, it is determined whether the distribution target software can be transmitted on the network.
By distributing the software based on this determination, the software can be distributed when the network is relatively free, so that the distribution target software can be surely distributed.

If the size of the software exceeds a certain threshold, the distribution source computer divides the distribution target software by the software dividing means and distributes the divided transmission units. Then, the distribution-destination computer combines the received transmission units by software combining means to restore the original software form.

Further, in the automatic software distribution method according to the present invention, when the system administrator instructs the distribution source computer to distribute the distribution target software, the distribution destination and distribution processing retry intervals are set by the setting information registration means. Register the information in the distribution source computer as setting information. When distributing the software, the distribution source computer reads the setting information of the software and distributes it to the distribution destination indicated by the setting information. If the distribution is not normally performed to a certain distribution destination, the distribution source computer attempts distribution again after the retry interval indicated by the setting information has elapsed. In this method, it is possible to further provide a package means, and the package creating means collects the distribution target software and the setting information of the software into one package, and distributes each distribution target software to the above-mentioned package unit. By managing with, it becomes easy to manage information about the software to be distributed.

Further, in the automatic software distribution method according to the present invention, when the distribution source computer transmits the distribution target software, the distribution destination computer normally completes the reception of the software. To the reception completion signal. Then, the distribution source computer collects the distribution status of the software at each distribution destination in the distribution status table based on the presence or absence of the reception completion signal from each distribution destination of the software. That is, the distribution source computer, when receiving the reception completion signal from the distribution destination computer, sets the status of the distribution destination computer in the distribution status table to distribution completed. On the contrary, the status in the distribution status table is set to undistributed for the distribution-destination computers that did not receive the reception completion signal within the predetermined time after transmitting the software. If the distribution is not completed for all the distribution destinations in one distribution process, after a predetermined time has elapsed, the distribution process is retried to the distribution destinations that have not been distributed in the distribution status table. I do.

Further, in the software automatic distribution system provided with this distribution status table, it is possible to further provide distribution status retrieval means and warning means in the distribution destination computer. In this case, when executing a piece of software in the distribution destination computer, the distribution status search means inquires of the distribution source computer about the current distribution status of the software, and based on the obtained distribution status, the When it is determined that the new version of the software is being distributed to the distribution destination computer, the warning means outputs a warning message indicating that the software is the old version. As a result, if distribution to all distribution destination computers is not completed and there is a situation where new version software and old version software are mixed on the network, it is possible to suppress the use of the old version with a warning.
Data inconsistency due to different versions can be prevented.

Further, in the automatic software distribution method according to the present invention, when the software to be distributed is distributed,
When the old version of the software is already stored in the storage device of the distribution destination computer, the installation position setting means of the distribution source computer causes the installation position of the new version to be different from the installation position of the old version of the software. Set the position. With this, when the new version of the software is distributed, it is possible to prevent the existing old version from being overwritten. Therefore, even if a problem occurs in the distributed new version, it is possible to quickly switch to the old version.

Further, in the automatic software distribution system according to the present invention, for each distributable software possessed by the distribution source computer, a list of other software (dependency relation list) necessary for executing the software. ) Is created in advance by the dependency relationship list creating means and stored in the dependency relationship list storage means. The distribution-destination computer has a list of software that can be distributed (distribution list), and the user selects the desired software from the software listed in this distribution list by means of software selection means. Select clothing. Then, a selection signal indicating the selected software is transmitted to the distribution source computer. Upon receiving the selection signal, the distribution source computer reads out the dependency list of the software indicated by the selection signal from the dependency list storage means and transmits it to the distribution destination computer which transmitted the selection signal. In response to this, the distribution destination computer compares the dependency list and the possession list by the distribution requesting means, and lists up the software not currently possessed among the software listed in the dependency list, The distribution request list is notified to the distribution source computer. Then, the distribution source computer distributes the software indicated in the distribution request list to the distribution destination computer.

[0038]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First Embodiment FIG. 1 is a schematic diagram showing an embodiment of an automatic software distribution system according to the present invention.

In the network system shown in FIG. 1, each terminal computer 30 is connected via the network 44 to the intermediary host computer 20 which manages the section to which it belongs. Then, the intermediary host computer 20 connects the central host computer 10 to the network 42.
Connected through.

On the host computer 10, the network 4
2, a load detection unit 11 that detects the communication load amount, a transmission availability determination unit 12 that determines whether or not the software can be transmitted based on the detected communication load amount and the size of the distribution target software, A division unit 13 that divides the distribution target software into transmission units of a predetermined size or less, and a transmission unit 14 that transmits this transmission unit to the intermediary host computer 20 are operating.

Further, on the intermediary host computer 20, a receiving unit 25 that receives the transmission units transmitted from the host computer 10, a combining unit 26 that combines these transmission units and restores the original software form, a network A load detecting unit 21 for detecting the communication load of 44, a transmission propriety judging unit 22 for judging whether or not the software can be transmitted based on the detected communication load amount and the size of the software to be distributed, software A division unit 23 that divides the wear into transmission units of a predetermined size or less, and a transmission unit 24 that transmits these transmission units to the terminal computer 30 are operating.

Further, on the terminal computer 30, a receiving unit 35 which receives the transmission units transmitted from the intermediary host computer 10, and a combining unit 36 which combines these transmission units and restores the original software form. Is working.

Here, for example, the host computer 10
The network 42 connecting the intermediary host computer 20 and the intermediary host computer 20 is a wide area network, and the network 44 connecting the intermediary host computer 20 and the terminal computer 30 is an Ethernet (registered trademark) cable. Of course, the networks used are not limited to these.

FIG. 2 is a flowchart showing the processing procedure on the transmission (distribution) side in this embodiment. Further, FIG. 3 is a flow chart showing a processing procedure on the receiving side in the present embodiment. Hereinafter, the processing procedure of the present embodiment will be described with reference to FIGS.

When the administrator of the host computer 10 gives an instruction to distribute certain software (S101), the host computer 10 activates the load detection unit 11 to check the amount of information exchanged on the network 42, and communicates on the network 42. The load amount is detected (S102). This communication load amount can be obtained, for example, by counting the number of packets passing over the network in a unit time.

Next, based on the detected communication load and the size of the software to be distributed, the network 42
The transmission availability determination unit 12 determines whether or not the software can be transmitted through (S103). When the network 42 is busy, it is determined that transmission is impossible. In this case, the communication load amount is continuously detected and the transmission is waited. When it is determined that the software can be transmitted, the size of the software is compared with a certain threshold value (S104). The data is transmitted to the computer 20 (S106). On the other hand, when the size of the software is larger than the threshold value, the dividing unit 13 divides the software into transmission units having a size smaller than the threshold value (S105), and transmits for each transmission unit (S106). ).

On the other hand, the intermediary host computer 20 on the receiving side
Then, when the receiving unit 25 receives the software transmitted from the host computer 10 (S107), it is determined whether or not the software has been divided and transmitted for each transmission unit (S108). If the software is divided, the combining unit 26
Combined with the original software form by (S10
9) Save.

The above is the processing procedure when software is distributed from the host computer 10 to the intermediary host computer 20. The intermediary host computer 20 distributes the software thus distributed to the terminal computer 30 in the lower hierarchy. The processing procedure at this time is also the host computer 1
The procedure is the same as when distributing from 0 to the intermediary host computer 20.

As described above, according to this embodiment, when the communication load on the network is detected and the transmission of the distribution target software is adjusted based on this load, when the network load is relatively small. Since the software can be transmitted to, the software to be distributed can be surely distributed.

In this embodiment, the load detectors 11 and 21 are used.
Is configured to detect the communication load of the network and transmit the distribution target software when the communication load is relatively small. However, the CPU load of the distribution side computer is further detected and based on the CPU load. It is also possible to adopt a configuration in which the distribution process is controlled. That is, the host computer 10
And a distribution for determining to the intermediary host computer 20, a CPU load detection unit that detects each CPU load amount and whether or not it is possible to perform the series of software processes described above based on the detected CPU load amount. A processing availability determination unit is provided. Then, the host computer 10 and the intermediary host computer 20 perform distribution processing based on the determination result of the distribution processing availability determination unit. As a result, the distribution process can be performed when the load on the CPU is relatively small, so that the distribution process can be performed without hindering other tasks of the host computer and the intermediary host computer. In other words, this reduces the possibility that a trouble will occur during the distribution process, and the distribution process will be executed more reliably.

In this embodiment, the host computer 10,
Although the network having three layers of the intermediary host computer 20 and the terminal computer 30 has been described as an example, the present invention is not limited to such a three-layer network, but is also applicable to a host and terminal two-layer network. It is also applicable to a hierarchical network system.

Second Embodiment FIG. 4 shows a second embodiment of the automatic software distribution system according to the present invention.

In the second embodiment, the basic configuration of the network is the same as that shown in FIG. 1, and is composed of three layers of the host computer 10, the intermediary host computer 20, and the terminal computer 30. .

That is, the host computer 10 as the software distribution source distributes the software to the terminal computer 30 via the intermediary host computer 20. At this time, in this embodiment, the mediation host computer 20 mediates the distribution by adding additional information to the software to be distributed.

FIG. 5 shows the operation of this second embodiment. The processing procedure of this embodiment will be described below with reference to FIGS. 4 and 5.

First, the host computer 10 sets the storage device 17
The application program (software) to be distributed, which is stored in, is transmitted to each intermediary host computer 20 by the transmission unit 14. In the intermediary host computer 20, when the receiving unit 25 receives the software, the administrator of the intermediary host computer creates the setting information for distributing the software to each terminal computer 30. This setting information is set as a distribution condition table 51 and a schedule table 52.

The distribution condition table 51 shows information about distribution destinations of software, and is created in the description format shown in FIG. That is, the distribution condition table describes the name and version (version) name of the distribution target software, the name and address (ID number) of each terminal computer to which the software is distributed. The distribution condition table “appli.tab” in FIG. 6 is the version “B” of the application software “appli”.
00 "is distributed to the terminal computers A, B, C ...

On the other hand, the schedule table 52 is a table in which setting conditions for managing the schedule of software distribution are described. In particular, the software is normally transmitted due to a failure on the network side or the terminal computer side. If there is not, the time interval (retry interval) until the transmission process is retried (retry) is described. The schedule table of FIG. 6 indicates that the distribution process is performed at a retry interval of 12 hours using the distribution condition table “appli.tab”.

After the creation of such setting information, in the intermediary host computer 20, the packager 28 collects the software to be distributed and the corresponding distribution condition table and schedule table into one file,
This is stored in the storage device 27 as a package (S2
01).

When the package registration process is completed, the scheduler 29 is activated (S202).

The started scheduler 29 reads the distribution condition table and the schedule table from the package, and instructs the transmission unit 24 to perform the distribution process based on the setting information shown in these tables (S203).

The transmitting unit 24 transmits the package to the terminal computer 30 according to the instruction from the scheduler 29 (S204).

In the terminal computer 30, the receiving unit 35 receives the transmitted package, and the unpackager cuts out the application software portion from the package and stores it in the storage unit 37.

When the software distributed from the intermediary host computer 20 is normally acquired in this way, the terminal computer 30 sends a signal to the intermediary host computer 20 indicating that the reception has been completed normally (reception completion signal). To send.

The intermediary host computer 20 determines the distribution status table 53 based on the presence / absence of a reception completion signal from the terminal computer.
Is created (S205). That is, the intermediary host computer 20 waits for a reception completion signal from the terminal computer for a predetermined time after transmitting the package, and for the terminal computers for which the reception completion signal has returned during that time, the status indicating the distribution status of the software is “distributed”. Done. " At the same time, describe the version name of the distributed software. Further, with respect to the terminal computer for which the reception completion signal does not return within the predetermined time, it is determined that the terminal computer could not be distributed due to a network or other failure, and the status is set to "distributed".

This distribution status table is created for each software in the format shown in FIG. The distribution status table in FIG. 7 is the version “B0” of the software “appli”.
When the distribution process of "0" is performed, the distribution is normally completed for the terminal computers B and C, but it cannot be distributed for the terminal computer A for some reason.
In this example, the old version "A00" of the software "appli" has been previously distributed to the terminal computers, and this distribution is a version upgrade. Therefore, in the terminal computer A, the software version (version name) remains "A00".

The distribution status table 53 thus created is used for retrying the distribution process. That is, the distribution status table 5 created in this way
3 is read by the scheduler 29 (S206), and if the statuses of all the distribution destination terminals are "distributed" in the distribution status table 53 at this time (S20).
7), the process ends.

On the other hand, in the distribution status table 53,
If there is a terminal computer having a status of "distributed" (S207), the distribution process is continued. In this case, the scheduler transmits the package to the terminal computers whose status is "Distribution" after the lapse of the retry interval described in the schedule table (S204). Then, the reception completion signal from the destination is awaited, and the distribution status table is updated based on the presence or absence of the signal (S205). In this way, the above cycle is repeated until the status of all distribution destination computers in the distribution status table becomes "distributed".

As described above, according to this embodiment, the distribution condition table and the schedule table are created as the setting information for the distribution target software, and the distribution is carried out based on these setting information, so that the reliable distribution is achieved. be able to. And this table with software 1
Managing the software to be distributed becomes easy by managing it in one file as a package.
That is, for example, in the case of distributing a large number of software at a time, in this embodiment, in the intermediary host computer, setting information is added to the software to create a package, which is once stored in the auxiliary storage device 27. The distribution process will be sequentially performed for each of these packages.
At this time, the scheduler 29 can obtain the setting information necessary for the distribution process only by extracting the package.

In the present embodiment, the setting information (distribution condition table, schedule table, etc.) of the distribution target software is set in the intermediary host computer 20,
This is because the network system of this embodiment is a large-scale system. That is, since the number of terminal computers is huge, the host computer does not manage individual terminal computers, but the intermediary host computer that controls each section manages the terminal computers. Therefore, conversely, in a small-scale system, the host computer may be configured to register and package the setting information. Further, not only the distribution from the intermediary host computer to the terminal computer, but also the distribution of the software from the host computer to the intermediary host computer, by registering the same setting conditions and packaging the software, the reliability of the software distribution is further improved. Therefore, efficiency can be improved.

Further, not only software and setting information, but also a distribution status table may be collectively managed in one package. With such a configuration, the distribution destination when the distribution is retried can be known only by reading the package. Furthermore, according to the configuration of the present embodiment, it is possible to prevent data inconsistency between the revised terminal and the unrevised terminal during the revision work of the software. That is, the intermediary host computer 2 is connected to the terminal computer 30.
0, the distribution computer 30 communicates with the intermediary host computer 20 to search the distribution status table of the software when a command to execute the software is input. The terminal computer 30
Read the status of. If the read status is "Distributing", the software that received the execution command is currently undergoing revision work, and using that software may cause data inconsistency with other computers. The fact that there is is displayed as a warning message on the display 39, for example. As a result, even if the distribution to all distribution destination terminals is not completed and the new version software and the old version software are mixed on the network, it is possible to suppress the use of the old version with a warning, and the data due to the version difference Inconsistencies can be prevented. If not only the warning message is displayed but also the intermediary host computer (distributor) is requested to distribute the new version, detailed software distribution according to the usage status can be realized.

[0072] The basic configuration of the third embodiment The third embodiment is similar to that of the second embodiment shown in FIG. 4, the host computer 10, intermediary host computer 20, and the three terminal computer 30 It is assumed to consist of layers.

8 and 9 show the processing procedure in the third embodiment of the software automatic distribution system according to the present invention. The processing procedure of this embodiment will be described below with reference to FIGS. 8 and 9.

Normally, when installing distributed software in a terminal computer, individual software is installed by relative designation from a specific position. That is, in the distributed software, the installation location (for example, the installation directory) is fixed to some extent depending on the type. This is designated, for example, when the software is created or when the software is distributed from the host computer.
Therefore, when the terminal computer has an old version of the distribution target software, the distribution target software is normally overwritten on the old version in the storage device of the terminal computer.

Therefore, in this embodiment, when setting the setting information for the distribution target software in the intermediary host computer 20, at the same time, the registration position of the distribution target software (a directory to be stored, etc.) is set. To solve this problem.

That is, the intermediary host computer 20 on the distribution side inquires of the administrator whether or not to specify the registration position (storage position) in the terminal computer when packaging the distribution target software (S301), When the registration position is designated, the packager 28 adds the registration position information to the distribution target software (S30).
2). Then, the scheduler 29 transmits the package to which the registration position information is added to the terminal computer (S
303) to the transmission unit 24. . If the registration position information is not specified, it is distributed as it is.

In the terminal computer 30 on the receiving side, the receiving section 35 receives the software (S401). Then, it is detected whether the registration position information is set in the package (S402). If it is set, the storage location of the software is changed to the registered location (S40
3) Then, the software is installed in the registered position (S406).

The above is the flow of processing when software is uniformly and simultaneously distributed from the host computer or the intermediary host computer to the terminal computers. It can also be applied to a configuration in which a computer requests a host computer to distribute desired software, and the host side distributes the requested software. That is, the terminal computer side sets the registration position of the software at the same time when the distribution request is made to the host side. Then, when the software is distributed from the host side, it is checked whether or not a registration position is set for it (S404), and if it is set, the storage position of the software is changed to the registration position (S404). S40
5). Then, the software is installed in the registered position (S406).

As described above, according to this embodiment, when the new version of the software is distributed, the registration position of the software can be specified from the host side or the terminal side, and as a result, the existing old version can be specified. Since it is possible to prevent the new version from being overwritten, it is possible to quickly switch to the old version even if a problem occurs in the new version distributed. Fourth Embodiment This fourth embodiment relates to a distribution system in which the terminal computer side requests the host computer side for software distribution, and the host computer side distributes the requested software.

Also in the fourth embodiment, the basic configuration of the network is the same as that shown in FIG. 1, and is composed of three layers of the host computer 10, the intermediary host computer 20, and the terminal computer 30. There is.

FIG. 10, FIG. 11 and FIG. 12 show a processing procedure of the fourth embodiment of the present invention.
The processing procedure of this embodiment will be described with reference to FIGS.

In this embodiment, the terminal computer 30 has a list in which file names of software that can be distributed from the host computer 10 are described, that is, a distribution list. This distribution list is, for example, the host computer 1
It will be updated from 0 on a regular basis or by distribution at any time.

First, in the terminal computer 30, the user or the administrator selects desired software from the software listed in the distribution list (S50).
1). The selection result is transmitted to the intermediary host computer as a selection signal (S502). The intermediary host computer 20 receives a signal from the terminal computer 30 (S601),
It is determined whether the signal is a selection signal or a distribution request list described later (S602).

The intermediary host computer 20 has information on the dependency relationship of each software listed in the distribution list. That is, in the present embodiment, in the intermediary host computer 20, for each software in the distribution list, a list of other software required for executing that software is created and stored in advance. Here, the list is called a dependency list. This dependency list may be created at the same time when the software is registered in the distribution list, for example.

Therefore, when the signal received from the terminal computer 30 is the selection signal, the intermediary host computer 20
The dependency list of the software indicated by the selection signal is read (S603), and the dependency list is transmitted to the terminal computer that issued the selection signal (S604).

The dependency list is created and stored in the following format, for example.

Software name: version number {expression expressing required software} Alternatively, although it is not a software name itself, when it is desired to handle a generic name of a certain kind of software, an abstract software name may be described as follows. .

Abstract Software Name {Expression Representing Required Software} In the expression expressing required software, the name of the software required for the software and the version name are AND (&), O
It is expressed by connecting logical operators such as R (|) and NOT (!).

The following is a specific example of the dependency list.

Soft-A: 18.55 {OS & terminal & window-system} OS {OS-A: 5.3 .. 5.4 ｜ OS-B: 4.1 .. 4.3} terminal {console ｜ tty ｜ Soft-D} window-system {OS & display & (WindowSoft-A: 11.5 ｜
WindowSoft-A: 11.4)} Soft-D {OS & window-system} This example shows the dependency list for version 18.55 of the software named Soft-A. In this dependency list, in order to use Soft-A, software collectively referred to as OS (operating system) is required, and both software collectively referred to as terminal and window-system are also required. Is shown. Then, it is shown that it is sufficient for the OS to have any one of the version names (versions) 5.3 to 5.4 of the software called OS-A or any of the version names 4.1 to 4.3 of the software called OS-B. Has been done. Also, term
As the inal, software called console or tty or Soft-D may be used, and it is shown that OS and window-system are required to use Soft-D. Also, as the window-system, OS and di
It has been shown that splay and WindowSoft-A version 11.5 or version 11.4 are all that is required.

Of the software listed in such a dependency list, the software not owned by the terminal computer cannot be used unless it is newly distributed. Therefore, when the terminal computer 30 receives such a dependency list (S503), based on it, the software that needs to be distributed is listed and a distribution request list is created (S504).

That is, the terminal computer 30 has a list of software (owned list) owned by itself. To give a specific example, for example, it is created and stored in the following format.

OS-A: 5.3 console display This holding list is created and updated by the administrator or the user, or automatically each time the software is newly installed on the terminal computer, for example.

The process of creating the distribution request list will be described in detail below using the specific examples of the dependency list and the holding list.

As shown in FIG. 11, when the terminal computer receives the dependency relationship list, it first selects one software item from the dependency relationship list (S511). Then, it is checked whether or not the selected software is listed in the possession list (S512). If so, it means that the software is already installed on the terminal computer, so there is no need for new distribution. However, if the software is not listed in the holding list, it is necessary to receive the distribution, so the software is added to the items in the distribution request list (S513).

If such work is completed for all software in the dependency list (S514),
The distribution request list is completed. If not done again,
Select another software from the dependency list and repeat the same operation.

For example, in the above-described specific example of the dependency list, three pieces of software are required to execute Soft-A, but the OS is first selected from these. Then, the expression represented by the line of the OS of the dependency list and each line of the holding list are matched. Then, since OS-A: 5.3 exists in the possession list, the conditional expression of the line OS of the dependency list is satisfied. Therefore, regarding the OS,
Nothing is added to the distribution request list.

Next, terminal is selected from the dependency list and the same work as in the case of the OS is performed. Also in this case, since the holding list has console, the conditional expression is satisfied and nothing is added to the distribution request list.

Finally, from the dependency list window-syste
Select m. Comparing the conditional expression in the row of this window-system with the holding list, the conditional expression is satisfied for OS and display, but is not satisfied with WindowSoft-A: 11.5 or Wi
The condition ndowSoft-A: 11.4 is not satisfied. Therefore,
This WindowSoft-A: 11.5 or WindowSoft-A: 11.4 is added to the distribution request list.

In this way, when there are a plurality of possible methods (software), for example, the following criteria are set to determine the type of software to be distributed.

(1) Priority is given to software appearing at the beginning of the conditional expression.

(2) Prioritize the combination of software that minimizes the distribution amount (size).

(3) Prioritize software combinations that minimize distribution costs. (When the software is charged for distribution) By repeating the above operation, all the software required to operate a certain software can be obtained as a distribution request list.

When the distribution request list is completed in this way, the terminal computer 30 sends the distribution request list to the intermediary host computer 20 (S505).

The intermediary host computer 20 is the terminal computer 30.
When a signal sent from the distribution request list is received (S601) and it is found that it is a distribution request list (S602), the software indicated in the distribution request list is read from its own storage device 27, and the terminal computer is read. It transmits to 30 (S605). If some software in the distribution request list is not possessed by the intermediary host computer, it makes a request to the host computer and sends the one sent from the host computer to the terminal computer. .

Then, the terminal computer 30 sequentially receives the requested software (S506) and installs them in its own storage device 37 (S507).

The above is the software distribution procedure in this embodiment.

As described above, according to this embodiment, the software required by the terminal computer can be distributed / acquired to the required minimum without omission and waste.

In each of the above embodiments, the host computer 1
0, the intermediary host computer 20 and the terminal computer 30 have been described as an example of a three-layer network, but the present invention is not limited to such a three-layer network, but may be applied to a two-layer network of a host and a terminal. It can also be applied to a multi-layer network system.

[0110]

As described above, according to the present invention, the load amount of the network is automatically investigated by the load detecting unit every time the software is transmitted, and the time for transmitting the software is increased when the load of the network is high. By changing, it is possible to avoid network load concentration.

When the software is very large, the software can be divided and transmitted, so that the load on the network is not increased for a long time. Furthermore, since distribution can be realized at midnight when the number of users of the network is small, it is possible to prevent the network from being overloaded during the daytime when the users are concentrated.

Further, according to the present invention, a distribution condition table and a schedule table are created as setting information for distribution target software, and distribution is performed based on these setting information, so that reliable distribution can be performed. . Then, by managing the table and the software in one file and managing them as a package, the software to be distributed can be easily managed.

Further, according to the present invention, a worker who uses an application program on a terminal computer is guaranteed to use the same version as a worker who uses another terminal computer. It is possible to maintain consistency.

Further, according to the present invention, since the new version of the software can be installed in a place different from the old version, it is possible to construct an environment in which both the new version and the old version can be used at the same time. This enables trial use of the new version, and gradual transition from the old version to the new version.

Further, according to the present invention, it becomes possible to receive required software without excess or deficiency.
This makes it possible to avoid problems caused by the lack of required software. Also, the type of software to be distributed
Since the judgment is made according to the state of each computer, it is possible to distribute only the minimum necessary software, and therefore the load at the time of software distribution can be reduced.

[Brief description of drawings]

FIG. 1 is a schematic diagram showing a software automatic distribution system according to a first embodiment of the present invention.

FIG. 2 Transmission (distribution) in the first embodiment of the present invention
It is a flow chart which shows the processing procedure of the side.

FIG. 3 Reception (reception) in the first embodiment of the present invention
It is a flow chart which shows the processing procedure of the side.

FIG. 4 is a schematic diagram showing a software automatic distribution system according to a second embodiment of the present invention.

FIG. 5 is a flowchart showing a processing procedure of the second embodiment of the present invention.

FIG. 6 is a diagram for explaining a distribution condition table and a schedule table in the second embodiment.

FIG. 7 is a diagram for explaining a distribution status table in the second embodiment.

FIG. 8 is a flowchart showing a processing flow of a terminal computer in the third embodiment of the present invention.

FIG. 9 is a flowchart showing the flow of processing of the intermediary host computer 3 in the third embodiment.

FIG. 10 is a flow chart showing a processing flow of a terminal computer in the fourth embodiment of the present invention.

FIG. 11 is a flowchart showing a distribution request list creation process of the terminal computer in the fourth embodiment.

FIG. 12 is a flow chart showing a processing flow of an intermediary host computer in the fourth embodiment.

FIG. 13 is a schematic diagram showing a system configuration of a software distribution system in a conventional example.

[Explanation of symbols]

10 host computer, 20 intermediary host computer, 30
Terminal computer, 11, 21 load detection unit, 12, 22 transmission availability determination unit, 13, 23 division unit, 14, 24 transmission unit, 25, 35 reception unit, 26, 36 combination unit, 42,
44 network, 17, 27, 37 storage device, 2
8 packager, 29 scheduler, 38 unpackager, 39 display, 51 distribution condition table, 52, schedule table, 53 distribution status table.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Masato Shimoda 325 Kamimachiya, Kamakura City, Kanagawa Mitsubishi Electric Corporation Computer Works

Claims (11)

[Claims] 1. A network system comprising a distribution source computer and a plurality of distribution destination computers connected to the distribution source computer via a network, wherein the distribution source computer detects the communication load of the network. Based on the communication load amount detected by the communication load detecting means and the size of the distribution target software, it is determined whether or not the distribution target software can be transmitted through the network. And a transmission permission / inhibition determination unit for transmitting the distribution target software from the distribution source computer to the distribution destination computer only when the transmission permission / inhibition determination unit determines that transmission is possible. Automatic software distribution method. 2. The automatic software distribution method according to claim 1, wherein the distribution source computer is provided with software dividing means for dividing the distribution target software into transmission units of a predetermined size or less, When the distribution target software is larger than the predetermined size, the software is divided by the software dividing unit and then transmitted for each transmission unit, and the received transmission unit is combined with the original computer by the distribution destination computer. An automatic software distribution method characterized by providing a software combining means for restoring the distribution target software. 3. The automatic software distribution method according to claim 1, wherein the distribution source computer registers setting information including a distribution destination of distribution target software and a distribution retry interval in the distribution source computer. An automatic software distribution method characterized in that a registration means is provided and the setting information is registered for each distribution target software. 4. The automatic software distribution method according to claim 3, wherein the distribution source computer collects the distribution target software and the setting information of the distribution target software into one package. An automatic software distribution system, characterized by comprising: means and a package storage means for storing the package, and managing the software to be distributed in package units. 5. The automatic software distribution method according to claim 1, wherein the distribution is performed to each of the distribution destination computers when reception of the distribution target software is normally completed. Distributing the distribution target software to each distribution destination computer based on the presence or absence of the reception completion signal from each distribution destination computer in the distribution source computer A distribution status table creating means for creating a distribution status table showing the status is provided, and the distribution source computer creates a distribution status table for each software to be distributed, and distribution is completed based on this distribution status table. An automatic software distribution method characterized by retrying the distribution process to a destination computer. 6. The automatic software distribution method according to claim 5, wherein the distribution-destination computer communicates with the distribution-source computer when a software execution command is received, If it is found from the distribution status search means for searching the distribution status of the software and the distribution status of the software searched by the distribution status search means that the software is an old version of the software currently being distributed. An automatic software distribution method characterized by having a warning means for outputting a warning message indicating that the software is an old version. 7. The automatic software distribution method according to claim 1, wherein the distribution source computer is configured to distribute the distribution target software to the distribution destination computer. As the installation location in the storage device,
The distribution destination computer has an installation position setting means for setting a position different from the installation position of the old version of the distribution target software already stored in the storage device of the distribution destination computer, and the distribution destination computer is installed from the distribution source computer. An automatic software distribution method characterized in that the software to be distributed is stored in a position different from the existing old version based on a position instruction. 8. The automatic software distribution method according to claim 1, wherein the distribution source computer is required to execute each distributable software. Dependency list creating means for creating a dependency list describing other software, and a dependency list storing the dependency list created by the dependency list creating means for each of the distributable software. Storage means, and a dependency list transmission means for reading out the dependency list for the software indicated by the selection signal received from the distribution destination computer from the dependency list storage means and transmitting it to the distribution destination computer, A software distributor that distributes the software indicated in the distribution request list received from the distribution destination computer to the distribution destination computer. And a distribution list in which the distribution-destination computer describes a software holding list of the software owned by the distribution-destination computer, and a distribution list describing software that the distribution-source computer can distribute. From the software listed in the distribution list, the desired software is selected, and the software selection means for transmitting a selection signal indicating the selected software to the distribution source computer, and the selection signal received from the distribution source computer. The dependency list is compared with the possession list, and the software required to be distributed among the software listed in the dependency list is searched for and compiled into a distribution request list. And a distribution requesting means for transmitting to the distribution source computer, and an automatic software distribution method. 9. The software automatic distribution method according to claim 1, wherein the distribution source computer is a host computer of a network system including a host computer and a plurality of terminal computers. A software automatic distribution method, wherein the distribution destination computer is a terminal computer of the network system. 10. The automatic software distribution system according to claim 1, wherein the distribution source computer comprises a host computer, a plurality of intermediary host computers, and a plurality of terminals. An automatic software distribution system, which is a host computer of a network system, wherein the distribution destination computer is an intermediary host computer of the network system. 11. The software automatic distribution method according to claim 1, wherein the distribution source computer comprises a host computer, a plurality of intermediary host computers, and a plurality of terminals. An automatic software distribution system, which is an intermediary host computer of a network system, wherein the distribution destination computer is a terminal computer of the network system.