JPH11119980A - Software distributing instruction supporting method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for automatically determining the software to be distributed to respective computers for the exclusion of an input designation error and the reduction of input labor. SOLUTION: When a distribution source computer 110 is provided with a distributing means 116 for transferring various kinds of softwares to a distribution destination computer 130 in accordance with the instruction of a use, while having a resource managing DB 111 for preserving various kinds of softwares 112, a distribution list preparing means 115 is provided and the distribution list preparing means 115 reads a list 114 of softwares instructed to be distributed in the past (the previous time), searches software registered with version-up in the resource managing DB 111 and defines the discovered software with version-up as the candidate for an object to be distributed this time. Further, the inside of the resource managing DB 111 is searched, and the novel software discovered there is also defined as the candidate of the object to be distributed this time.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to remote maintenance of software for a plurality of computers arranged in a distributed manner, and more particularly, to remote distribution of a new version of various software to each computer. The present invention relates to a software distribution instruction automatic determination method suitable for automatically determining software to be distributed and its version.

[0002]

2. Description of the Related Art In a distributed system in which a plurality of computers are connected via a network, if software (programs, data files, etc.) is upgraded due to a specification change or a countermeasure against a problem, a computer on a center side transmits a request from a computer on a remote side. It is required to update software of a remote computer by transferring a file to a plurality of computers. To this end, several patents relating to software remote distribution have been filed. Of these patents, a representative example of the prior art is disclosed in
37768 “Remote distribution management network”.

In the prior art, the installation source computer is provided with software installation means and a database storing the software, and after the installation source computer prepares an installation list indicating which software is to be installed on which computer on the installation source computer side, When an instruction to start installation is given, the software installation means transfers files in the database to the installation destination computer according to the installation list.

[0004]

In the prior art, every time an installation instruction is issued after some software has been upgraded, an installation list indicating which software is to be installed on which computer must be created each time. That is, there is a problem that an input error occurs, and a problem that the input is troublesome. This problem is because the convenience for the user is not considered when the software version is frequently updated.

For example, in a system that requires high reliability, such as a financial institution, software that does not generate an abnormal state (error) as much as possible and that does not require human labor to transfer the software to be maintained. Construction of a remote maintenance system is desired.

SUMMARY OF THE INVENTION An object of the present invention is to provide a method for automatically designating software to be distributed to each computer in order to eliminate an error in input designation by a user and to eliminate troublesome input work.

[0007]

SUMMARY OF THE INVENTION In a distributed system in which a distribution source computer and one or more distribution destination computers are connected by a network, the distribution source computer has a resource management database for storing various software. If there is a distribution means for transferring various software in the resource management database to the distribution destination computer in accordance with the instructions of Wear extraction means is provided. The distribution target software extracting means reads a software (for example, a list of software names and their version numbers) instructed to be distributed in the past (previous time), and stores the software names and version numbers in the resource management database for each software name and version number. Then, the software registered in the version upgrade is searched for, and the found upgraded version of the software is set as a candidate for the current distribution. Furthermore, the software that has not been listed in the past (previous) distribution instruction is searched in the resource management database, and the new software found is also a candidate for distribution this time. The final determination of the distribution target uses one of (1) a method according to the user's selection, and (2) a method of automatically limiting to the latest version among a plurality of versions.

[0008] Since the software to be distributed is automatically determined as the software to be distributed by the above-mentioned distribution target software extracting means, the upgraded software and the newly registered software, the user is required to be one by one as in the prior art. The trouble of inputting the software name and version number can be saved, and the input error can be reduced as much as possible.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments for realizing the present invention will be described below with reference to the drawings.

[1] First Embodiment (A) Example of Hardware / Software Configuration FIG. 1 shows an example of a hardware / software configuration for realizing the present invention. FIG. 1 shows a configuration in which a distribution source computer 110 and a distribution destination computer 130 are connected to a network 120 as a hardware configuration. Distribution destination computer 1
30 is not limited to one, and a plurality of 30s may be connected to the network 120. The distribution source computer 110 includes a software resource management DB 111, a software distribution management DB 113, and a distribution list creation unit 11.
5 and software distribution means 116. On the other hand, the distribution destination computer 130 has a software reception area 131 and a replacement execution unit 133. When software maintenance is performed, the distribution list creating unit 115 creates a distribution list 114 instructing the destination computer 130 of a software name and a version number to be replaced. Then, the software distribution unit 116 updates the software version 112 indicated in the distribution list 114 in the software resource management database 111 by the software reception area 131 of the distribution destination computer 130 to be maintained.
To download. All versions of software 112 and 132 each have source files or objects, libraries, and installation scripts. Then, the replacement execution means 133 executes the software replacement from the old (current) version to the new version by activating the installation script of the new version of the software 132 downloaded to the software reception area 131. here,
The installation script describes a compile, link, and load command for generating an execution module from each version of software.

A feature of the present invention is that the distribution list creation means 11 eliminates input errors and minimizes the trouble of inputting.
5, a distribution list 114 instructing the distribution destination computer 130 with the software name and the version number to be replaced is automatically created.

(B) Example of DB Configuration and Process Flow of Distribution Source Computer The software resource management DB 111 is a database for centrally managing all versions of text files, sources, objects, load modules, and the like. FIG. 2 shows a configuration example of the software resource management DB. The software resource management DB 111 is hierarchically composed of a first directory having a software name 201, a second directory having a version number 202, and a second directory under a file group 203 to be transferred to one of the distribution destination computers. . The software name 201 corresponds to a software name registered in any of the distribution destination computers. The version number 202 is a software version number. The file group to be transferred to the distribution destination computer is placed in the directory 203 under the version number. Specifically, an installation script for registering in the execution environment
This is a group of files required in ap_load and ap_load.

For example, the software resource management DB 111
The software of Program A, Program B and Data A is V1.1, V1.1 and V1.
2. When registered with V1.1 and V1.2, the software names are ProgramA211, ProgramB221, DataA231.
And the version number for ProgramA211 is V
The software resource management DB 101 is configured such that the version numbers for the program 221 are V1.1 and V1.2 222 as 1.1 212, and the version numbers for the DataA 231 are V1.1 and V1.2232. Further, object files ProgramA.o and Pro are stored under the directory of each version number as files to be transferred.
one of gramB.o, text file DataA.txt,
And the installation script ap_load is stored. Specifically, V in directory ProgramA211
1.1 Below 212 is the object file ProgramA.o2
13 and an installation script ap_load 214, an object file ProgramB.o and an installation script under V1.1 of the directory ProgramB221.
ap_load, under V1.2 of directory ProgramB221, 22
2 includes an object file ProgramB.o223 and an installation script ap_load 224, and a text file DataA.
txt and the installation script ap_load, the text file DataA.txt233 and the installation script ap_lo
ad234 is stored.

The software distribution management DB 113 is a database for defining a list of software to be registered in each distribution computer. FIG. 3 shows a configuration example of the software distribution management DB 113. Software distribution management D
B113 is that the first directory is the distribution destination computer name 301
And the second directory is the system version number 302
The file under the second directory is the distribution list 303
Is composed hierarchically. The distribution destination computer name 301 corresponds to a host name existing as a distribution destination computer. The system version number 302 is a system version number for identifying each distribution, and indicates the number of distributions. In the directory 303 under the system version number, a file Define.DB defining the software constituting the distribution destination computer and its version number is created. The distribution list Define.DB 303 is a file in which the software name is described in the first column and the version number is described in the second column.

For example, when the distribution to the distribution destination computer SiteA is performed for the second time, the distribution list Define.DB313 under the directory of the system version number V1.2312 of SiteA311 includes ProgramA V1.1, Program
B V1.2 and DataA V1.2. Thus, when the first distribution list Define.DB and the second distribution list Define.DB 313 are compared, Program B V
1.2, DataA V1.2 has been updated, so ProgramB
V1.2, DataA V1.2 will be distributed to the distribution destination computer SiteA. On the other hand, when the distribution to the distribution destination computer SiteB is performed for the second time, the distribution list Define.DB323 under the directory of the system version number V1.2322 of SiteB321 contains ProgramA V1.1,
amB V1.1, DataA V1.2. Thus, comparing the first distribution list Define.DB with the second distribution list Define.DB323, DataA V1.
Since 2 has been updated, DataA V1.2 will be distributed to the distribution destination computer SiteB. Here, the program is executed between the second distribution list 313 to the distribution destination computer SiteA and the second distribution list 323 to the distribution destination computer SiteB.
B has a different version number because the distribution destination computer Site
After completing the second distribution to B, the program Progr
This is because it is assumed that the version of amB has been upgraded and subsequently the second distribution to the distribution destination computer SiteA has been performed.

Now, the distribution destination computers SiteA and SiteB
It is assumed that after the second distribution is completed, the software is newly upgraded and registered in the software resource management DB. For example, the program ProgramA
From V1.1 to V1.2, data DataA from V1.2 to V1.3
Upgraded to a new program
When C is registered in V1.1, the software resource management DB is configured as shown in FIG. In FIG. 4, in the example of the program ProgramA, the directory ProgramA2
11, a directory V1.2 412 is newly created, and an object file P is stored under the directory V1.2 412.
rogramA.o413 and installation script ap_loa
d414 is stored. Here, the object files Program A.o 213 and Program A.o 413 are partially different because corrections have been made between new and old. On the other hand, the installation scripts ap_load 214 and ap_load 414 are often the same because changes in software names and command names are rare. In the example of the data DataA, the directory V1.3 is stored under the directory DataA231.
432 is newly created, and a text file DataA.txt 433 and an installation script ap_load 434 are stored under the directory V1.3 432. As in the example of the program ProgramA, the text file DataA.
txt 233 and DataA.txt 433 are partially different, and the contents of the installation scripts ap_load 234 and ap_load 434 are the same. Further, in the example of the program ProgramC, a directory ProgramC441 and a directory V1.1 442 are newly created and the directory V1.
The object file ProgramCo.443 under 1442
In addition, an installation script ap_load 444 is stored.

FIG. 5 shows the flow of processing of the distribution list creating means 115 according to the present invention. In step 501, the software distribution management DB 11 is used to notify the user.
A list of destination computer names (referred to as site names) is displayed based on No.3. For example, the software distribution management DB 11 shown in FIG.
If you search for the first directory name in Site3, SiteA31
1 and SiteB 321 can be taken out. And
A list is displayed on a screen or the like to notify the user of the extracted site name. Step 502 receives a selection of a site name from an operator in the display list of site names. For example, if the operator selects SiteA from SiteA and SiteB in the site name list, Site
Recognize as A. Step 503 retrieves the latest distribution list for the specified site name. For example, of V1.1 and V1.2 of the system version number list of the designated site name SiteA311, V1.2 31
2 is the newest, the distribution list 313 of V1.2 is taken out as a base distribution list. Step 504
Extracts one set of the software name and its version number from the extracted distribution list 313 one by one, and repeats the following processing for the number of software. For example, since the first line of the distribution list 313 is ProgramA, V1.1, the software name is ProgramA and the version number is V.
Recognize as 1.1. A step 511 searches the software resource management DB to determine whether a newer version number than the corresponding version number of the software is registered. For example, the software resource management DB 11 shown in FIG.
By searching the directory under the software name ProgramA211 with V.1, V1.1 and V1.2 can be found. Of those, V1.2 412 is newer than the version number V1.1 described in the distribution list. Since it is a version number, it can be determined that a new version number V1.2 412 is registered. Step 512 is a step 51 if a new version number is registered.
Then, if the new version number is not registered, the process skips to step 511. In the example of program ProgramA, the new version number V1.2 4
Since 12 has been registered, the process proceeds to step 513. Step 513 replaces the version number described in the distribution list with the newly discovered version number.
In the example of the program ProgramA, the version number V1.1 on the first line of the distribution list 313 is replaced with the newly discovered version number V1.2 412. With the above steps, the processing for the first line of the distribution list 313 is completed,
Next, steps 511 to 513 are similarly repeated for the second and subsequent lines of the distribution list 313. Distribution list 313
In the second line, it is recognized that the software name is ProgramB and the version number is V1.2. However, even if a search is made under the directory having the software name ProgramB221 in FIG. 4, no processing is performed since a version number newer than the corresponding version number V1.2 is not registered. Also, the third line of the distribution list 313 recognizes DataA as the software name and V1.2 as the version number. A search under the directory with the software name DataA231 in FIG. 4 reveals a new version number V1.34.
Since 32 is registered, the version number V1.2 on the third line of the distribution list 313 is replaced with the newly discovered version number V1.3432. The processing for each line of the distribution list has been completed in the above steps.
Return to 05. In step 505, among the software existing in the software resource management DB, software not described in the distribution list, that is, newly registered software is added to the distribution list. For example, when the first directory of the software resource management DB 111 in FIG. 4 is searched, Program A 211, Program B 221 and D
Although ataA 231 is described in the first to third lines of the distribution list 313, Program C441 is not described in the distribution list 313, so the program name Program
Add C441 and version number V1.1 442 to the distribution list. Here, the user may be inquired whether or not to add. In step 506, the distribution list updated by the replacement processing in step 513 and the addition processing in step 505 is stored as a new file.
For example, as shown in FIG. 6, a directory V1.3 612 with a revised system version number is newly created under a directory having a site name SiteA311 and a distribution list 613 is created under the directory V1.3 612.
Save as a new file. The distribution list 613 is the updated content, and is an instruction content for distributing the latest version of each software. Although three pieces of software are taken as an example of the distribution list, when the number of software is several tens to several hundreds, the user's labor of input is considerably reduced.

On the other hand, in step 502, S is set as the site name.
When iteB is selected, as a result of processing each step, as shown in FIG. 6, V1.3 622 is newly created under directory SiteB321, and distribution list 623 is further created under directory V1.3622. Newly saved. Here, the reason why the distribution lists 613 and 623 have the same content is that it is assumed that there is no new registration or upgrade registration of software in the software resource management DB while instructing the sites SiteA and SiteB. is there.

The software name and version number newly registered in the software resource management DB are searched by the distribution list creating means as described above, and the newly registered one is automatically designated as the current distribution target. This eliminates the need for the user to input the software name and version number one by one, and further reduces input errors as much as possible. Further, since there is no need to input the distribution target and no backward operation due to erroneous operation of software distribution, software maintenance can be easily and reliably performed.

[2] Second Embodiment In the first embodiment, it is effective to distribute all the software registered in the software resource management DB evenly to each site. However, partial software is distributed to each site. Or distributing certain software only to certain sites, there is a risk of discovering software that is not newly registered. Therefore, as a modification of the first embodiment, a file for managing the distribution relationship between each distribution destination computer (site) and each software is provided,
An embodiment will be described in which the distribution list creation means uses this file to efficiently determine software newly registered in the software resource management DB. The hardware / software configuration is the same as in FIG. 1, and the software resource management DB 111 is the same as in FIGS.

FIG. 7 shows that the site resource distribution relation files Link.DB 715 and 725 are provided in the software resource management DB 113 of FIG. 3 in order to manage the distribution relation between each distribution destination computer (site) and each software. This is an example of a configuration. Here, program ProgramA is site SiteA
Distributed to only Site B
Distributed to only Site A and Site A and Site A
B to show an example of distribution to both
And 723 are different from those in FIG. When distributing software to the destination computer SiteA,
After distributing ProgramA V1.1 and DataA V1.1 for the first time, and then distributing DataA V1.2 for the second time,
The distribution list Define.DB 713 includes ProgramA V1.
1, DataA V1.2. Thus, the first distribution list Define.DB and the second distribution list Def
Comparing ine.DB 713, DataA V1.2 has been updated, so that DataA V1.2 is distributed to the distribution destination computer SiteA. On the other hand, when distributing software to the distribution destination computer SiteB, the first time
When distributing DataA V1.2 for the second time after completing the distribution of amB V1.1 and DataA V1.1, the distribution list Defi
ne.DB723 contains ProgramB V1.1, DataAV1.2
It is described. Thus, the first distribution list D
When efine.DB is compared with the second distribution list Define.DB723, since DataA V1.2 has been updated, Da
taA V1.2 will be distributed to the distribution destination computer SiteB. By the way, the site resource distribution relation file Link.DB
Reference numerals 715 and 725 manage whether or not each software is distributed for each site, and are automatically created by the distribution list creating unit. For example, the site resource distribution relation file Link.DB 715 of site SiteA means that program ProgramA and data DataA are distributed but program ProgramB is not distributed. Here, a software name without any prefix means distribution, and a software name with a exclamation mark "!" Means not distribution. On the other hand, the site resource distribution file Link.DB 725 of the site SiteB distributes the program ProgramB and the data DataA, but the program ProgramA.
Means not to distribute.

FIG. 8 is an improvement of the processing flow of the distribution list creating means of FIG. 5 in order to recognize newly registered software reliably and at high speed. The difference between FIG. 5 and FIG. 8 is that steps 801 and 802 are provided in FIG. 8 instead of step 505 in FIG. Similarly to the example of the first embodiment, after the second distribution to the distribution destination computers SiteA and SiteB is completed, the program ProgramA is upgraded from V1.1 to V1.2, and the data DataA is upgraded from V1.2 to V1.3. And a new program Progr
Consider a case where amC is registered in the software resource management DB at V1.1. The configuration of the software resource management DB at this time is as shown in FIG. Step 801 extracts a site resource distribution relation file for the designated site name. For example, since there is a designated site name SiteA, the site resource distribution relation file Link.DB 715 under the directory SiteA311 is extracted. In step 802, among the software existing in the software resource management DB, software not described in the inter-site-resource distribution relation file, that is, newly registered software is added to the distribution list. For example, when the first directory of the software resource management DB 111 in FIG. 4 is searched, Program A 211, Program B 221 and Dat
The aA 231 is described from the first line to the third line of the inter-site resource distribution relation file 715.
Since 41 is not described in the inter-site resource distribution relation file 715, the user is asked whether to add the program name ProgramC441 and the version number V1.1442 to the distribution list. If the user responds, the program name ProgramC441 and the version number V1.1442 are added to the distribution list, and the program name ProgramC441 is added to the inter-site resource distribution relation file. On the other hand, if the user refuses to add, the program name Program
C441 is added to the site resource distribution relation file. Here, assuming that the answer is “add”, the inter-site-resource distribution relation file 715 is updated as indicated by reference numeral 915. Further, the distribution list 713 is updated as indicated by 913. As described above, the distribution list 913 is an instruction content for distributing the latest version of each software including the newly registered software.

On the other hand, in step 502, the site name is set to S
When iteB is selected, as a result of processing each step, as shown in FIG. 9, the distribution relation file between site resources 725 is updated as shown by 9215, and the distribution list 7
23 is updated as shown at 923. Here, a case is described as an example in which a reply is not added in step 802.

With the above-described distribution list creating means, newly registered ones are automatically designated as the current distribution targets faster and more reliably than in the first embodiment. And the trouble of inputting the version number and the version number can be saved, and the input error can be reduced as much as possible. Furthermore, since the responsiveness and ease of use are good, software maintenance can be performed comfortably.

[3] Third Embodiment In the first embodiment, centralized development and maintenance is taken as an example. This is effective when centrally managing software in a software resource management DB as in centralized development and maintenance. is there. From now on,
It is expected to shift from centralized development and maintenance to distributed development and maintenance. Thus, as a modification of the first embodiment, distributed development and maintenance will be described as an example, and an embodiment will be described in which software is distributedly managed by a software resource management DB distributed to each computer.

FIG. 10 shows an example of a hardware / software configuration for performing distributed management of software resource management. Another distribution source computer 1010 is connected to the network 120 in addition to the distribution source computer 110. The distribution source computer 1010 is another software resource management DB 1
011. Software resource management DB 111
2 and FIG. 4, and the configuration method of the software resource management DB 1011 is the same as that of FIG. 2 and FIG. 4, but the contents (name of software, etc.) are different.
The distribution list creation means 115 is a software resource management DB
Reference is made to 1011 in addition to 111. The processing flow of the distribution list creation unit 115 is the same as that in FIG. 5 or FIG.
Steps 511, 505 and 802 in FIG. 5 or FIG.
In the software resource management DBs 111 and 10
11 may be referred to.

As described above, it is possible to search for a software name and a version number newly registered in the software resource management DB configured in a distributed manner, and to automatically designate the newly registered one as a distribution object of this time. Thus, effects similar to those of the first and second embodiments can be obtained.

[0028]

According to the present invention, a software name and a version number newly registered in the software resource management DB are searched, and the newly registered one is automatically designated as the current distribution target. This eliminates the need for the user to input the software name and version number one by one, and further reduces input errors as much as possible. Further, since there is no need to input the distribution target and no backward operation due to erroneous operation of software distribution, software maintenance can be easily and reliably performed. In addition, since the responsiveness and ease of use are good, software maintenance can be performed comfortably.

[Brief description of the drawings]

FIG. 1 is an example of a software maintenance system configuration.

FIG. 2 is an example of the configuration of a software resource management database.

FIG. 3 is an example of a software distribution management database configuration and a distribution list.

FIG. 4 is an example of the configuration of a resource management database after registering various software.

FIG. 5 is an example of a processing flow of a distribution list creation unit.

FIG. 6 is an example of a distribution list generated by a distribution list creating unit.

FIG. 7 is an alternative example of a software distribution management database configuration and a distribution list.

FIG. 8 is an alternative example of the processing flow of the distribution list creation unit.

FIG. 9 is an alternative example of the distribution list generated by the distribution list creation unit.

FIG. 10 shows an example of a distributed configuration of a software maintenance system.

[Explanation of symbols]

110: distribution source computer, 120: network, 130
... distribution destination computer, 111 ... software resource management database, 112 ... various software, 113 ... software distribution management database, 114 ... distribution list for each distribution destination computer, 115 ... distribution list creation means, 116 ...
Software distribution means, 131: software reception area, 132: new version of software, 133: replacement execution means.

 ──────────────────────────────────────────────────の Continued on the front page (72) Inventor Hiroshi Watani 5-2-1, Omika-cho, Hitachi City, Ibaraki Prefecture Inside the Omika Plant, Hitachi, Ltd.

Claims (8)

[Claims] In a distributed system in which a distribution source computer and one or more distribution destination computers are connected via a network, the distribution source computer has a resource management database for storing various software, and the resource management database is stored in accordance with a user's instruction. When there is provided a distribution means for transferring various software in the resource management database to the distribution destination computer, a distribution target software extraction means is provided, and the distribution target software extraction means has provided a software program for which distribution has been instructed in the past. A software distribution instruction support method, wherein software updated in the resource management database among the software is set as a candidate for the current distribution target. 2. The distribution target software extracting means according to claim 1, stores a list of software for which distribution has been instructed in a distribution management file, and refers to the distribution management file to designate distribution in the past. 2. The software distribution instruction support method according to claim 1, wherein the software is grasped. 3. The distribution target software extracting means according to claim 1 stores the distribution target file in a distribution permission / prohibition file for managing whether or not to distribute each software, and refers to the distribution permission / prohibition file. 2. The software distribution instruction support method according to claim 1, wherein newly registered software is determined in the resource management database. 4. The distribution target software extracting means according to claim 1, wherein said updated software includes a newly registered one and a corrected one in said resource management database. 2. The software distribution instruction support method according to claim 1, wherein the software distribution instruction is a candidate for distribution. 5. The distribution software extracting means according to claim 1, wherein said distribution target software extracting means determines the distribution target software according to a user's selection among a plurality of distribution target software. Software distribution instruction support method. 6. The software extracting means according to claim 1, wherein said software to be distributed automatically determines the latest software from among those updated in said resource management database. Software distribution instruction support method. 7. In a case where the resource management database according to claim 1 is configured in a plurality of distributed manners, the distribution target software extracting means according to claim 1 searches all the resource management databases. A software distribution instruction support method characterized by being a candidate for distribution this time. 8. A software maintenance method characterized in that the distribution means transfers the software determined by the software distribution instruction support method according to any one of claims 1 to 7 to a distribution destination computer. Method.