JPH10269065A - Library management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to add, change and delete the rules concerning a library constitution, by checking whether the software constitution of each terminal is adapted to a prescribed constitution rule and displaying this check result. SOLUTION: At a certain time, every set of correspondence among a built-in destination 800, a constitution name 801 and a version 802 is acquired from the built-in information showing a current built-in software constitution. Then, it's checked whether the name 801 and the version 802 are coincident with each prescribed constitution rule. If a built-in destination is not coincident with the constitution rule, a list of built-in destinations is displayed. If it's desired to distribute the software as prescribed by the constitution rule, a list of libraries is displayed together with the list of built-in destinations. Then it's checked whether the library selected by a user can be distributed to a selected built-in destination. Thus, the selected library is distributed based on the check result.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing a library in a software development environment and a software execution environment, and more particularly to a library capable of checking a library configuration and distributing software in accordance with a predetermined configuration rule. Regarding management methods.

[0002]

2. Description of the Related Art With the spread of distributed development and distributed processing in recent years, there is a tendency to install a large number of machines at a plurality of bases. It is necessary to manage the name and version of the installed software for each such distributed machine.

Conventionally, the software configuration of each machine has been managed by a handwritten document or a word processing document. It is necessary to incorporate software into each machine and keep the documents up to date. When distributing software to the distributed machines, a method of distributing the latest software has been adopted. As a method related to this method, there is a "distributed processor software maintenance management method" described in JP-A-3-158961.

[0004]

The above-described library management method has the following problems.

[0005] In the above-described method of managing the software configuration on a desk, the terminal administrator at each site arbitrarily incorporates the software, so that the software configuration of all machines cannot be managed. . Therefore, there is a problem that there is no software configuration rule that can be freely changed, added, or deleted.

Further, when distributing the latest software as described above, if a person who does not know the software configuration of the destination machine performs the operation, the application on the machine after distribution may not work. For this reason, there is a problem that the latest software cannot be distributed.

Accordingly, it is an object of the present invention to provide a library management method capable of adding, changing, and deleting rules relating to a library configuration.

Another object of the present invention is to provide a library management method which enables a user who does not know the configuration rules to distribute software according to the rules when distributing software.

[0009]

SUMMARY OF THE INVENTION The present invention provides, at one point,
The correspondence between the installation destination, the configuration name, and the version is acquired one by one from the installation information indicating the currently installed software configuration, and it is checked whether the configuration name and the version match a predetermined configuration rule. Things.

If there is an installation destination that violates the configuration rule as a result of the inspection, a list of the installation destinations is displayed.

Further, when it is desired to distribute software according to the configuration rules, a list of libraries and a list of installation destinations are displayed, and whether a library selected by a user may be distributed to the selected installation destination is determined. Inspection and distribution. When files constituting the library are version-controlled, only the changed / added files are extracted and distributed.

The file to be distributed is stored in an external storage medium such as a floppy disk.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a flowchart showing an embodiment of a processing procedure when the present invention is applied to a library management system, FIG. 2 is a flowchart showing a configuration inspection process in FIG. 1, and FIG. 3 is a flowchart in FIG. FIG. 4 is a flowchart showing the configuration information display processing of FIG. FIG. 5 is a block diagram showing the system configuration of the first embodiment. FIG. 6 is a table configuration example of configuration information 407 in which a configuration name is associated with a library included in the configuration and its version.
FIG. 8 is a table configuration example of a configuration rule 408 representing a predetermined rule regarding a correspondence between an installation destination and a library, and FIG. 8 is a table configuration example of installation information 409 representing an installation destination and a library incorporated in the installation destination. is there. FIG.
Is a display example of a terminal that does not match the configuration rule 408, and FIG. 10 is a display example of configuration information 407 specified by the user.

In FIG. 5, reference numeral 501 denotes an interactive terminal having a keyboard, a mouse, and a monitor screen, which is used by a user to input an instruction or to display an operation instruction to the user. 502 is a C which has a sequential processing function of the program.
A PU 503 is a main storage device accessed by the CPU 502, and 504 is an auxiliary storage device used to hold data and programs. Reference numeral 505 denotes a program for executing the processing procedure shown in FIG. 1, reference numeral 506 denotes a file group constituting a library in the present system, reference numeral 507 denotes a file holding configuration information,
Reference numeral 508 denotes a file holding configuration rules.
Reference numeral 9 denotes a file holding embedded information.

Next, a first embodiment will be described with reference to FIGS. 5 to 10 based on the flowcharts of FIGS.

First, the installation destination 800, the configuration name 801 and the version 802 are read one by one from the table of the installation information 509 (100), and the configuration inspection process (102).
I do. In the case of this example, the installation destination “host001” 8
03, configuration name “A” 804 and version “1.0” 8
05 is acquired. Next, the configuration inspection processing will be described. First, in order to acquire the installation destination 700 of the configuration rule 508 corresponding to the installation destination “host001” 803, the installation destination 700, the configuration name 701, and the version 702 are read as a set from the table of the configuration rule 508 (2
00), it is determined whether or not the installation destination 800 acquired in step 100 matches the integration destination 700 acquired in step 200 (202).
3 is performed, and if they do not match, step 200 is repeated. In the case of this example, the installation destination “host001”
702 match. This time, the configuration name 801 obtained in step 100 and the configuration name 7 obtained in step 200
01 is determined (203). If they match, step 204 is processed. If they do not match, the contents acquired in step 100 and the configuration name 701 and version 702 acquired in step 200 are compared. The flag is stored, and a flag that violates the configuration rule 508 is set (206). In this example, the configuration name “A” 804 and the configuration name “A” 70
Since step 4 matches, step 204 is processed. Next, it is determined whether the version 702 obtained in step 100 matches the version 702 obtained in step 200 (204).
Is terminated, and if they do not match, the content acquired in step 100, the configuration name 701 and the version 702 acquired in step 200 are stored, and a flag that is contrary to the configuration rule 508 is set (206). In this example, since the version “1.0” 805 does not match the version “1.1” 705, the integration destination “h” acquired in step 100
ost001 ”803, the configuration name“ A ”804, the version“ 1.0 ”805, the configuration name“ A ”704 and the version“ 1.1 ”705 acquired in step 200 are stored. If the installation destination 800 acquired in step 100 does not exist in the configuration rule 508, the content acquired in step 100 is stored, and a flag indicating that the corresponding configuration rule 508 does not exist is set. 102. Next, it is determined whether or not all the sets of the embedded information 509 have been read (101). If all the sets have been read, it is determined whether or not there is an installation destination 800 that does not match the configuration rule 508. Judgment is made based on the flag set in 205 or 206 (103), and a flag or When the flag configuration rules 508 equivalent to the absence has been set, the list display process 10
Perform 4. In the list display process 104, first, in step
5 or 206 is read one set at a time (30
0), and display the contents (302). In this example, since the flag contrary to the configuration rule 508 is set in step 206, the configuration name “A” 903 and the version “1.0” 904 of the integration destination “host001” 900 and the integration information 509 stored in step 206 are stored. , And the configuration name “A” 907 and version “1.1” 908 of the configuration rule 508 are displayed. FIG. 9 shows a display example in this example.
Shown in This time, the embedded information 5 displayed in step 302
For the configuration name 901 and version 902 of 09 or the configuration name 905 and version 906 of the incorporation rule 508, it is determined whether or not to display the corresponding configuration information 507 according to the user's instruction (303). Is
The configuration name and version designated by the user are read (304), and the configuration information display processing 306 is performed. In the case of this example, at the installation destination “host001” 900,
The configuration name “A” 903 and the version “1.0” 904 of the embedded information 509 are specified. In the configuration information display processing 305, first, the correspondence between the configuration name 600 and the version 601 and the correspondence between the library name 602 and the library version 603 are read one by one from the configuration information 507 (40).
0), the configuration name acquired in step 304 and step 4
It is determined whether or not the configuration name 600 acquired in 00 matches (402), and if they match, the version acquired in step 304 and the version 6 acquired in step 400
It is determined whether or not 01 matches (403). If both the configuration name and the version match, the content acquired in step 400 is displayed (404). If the corresponding configuration information 507 does not exist, a message to that effect is displayed. In this example, the configuration name “A” 604 of the configuration information 507, the version “1.0” 605 of the configuration, the first library name “PGM1” 606, the library version “1.0” 607, and the second library The name "PGM
2 "608 and library version" 1.0 "60
9, the third library name “PGM3” 610 and the library version “1.0” 611 are displayed. FIG. 10 shows a display example in this example.

According to this embodiment, it is possible to check and display whether or not the software configuration of each terminal is inconsistent with the predetermined configuration rule 9, so that terminals which do not conform to the configuration rule can be grasped. The unjust condition can be corrected.

In the above, an embodiment has been described in which it is checked whether or not a software configuration at a certain point violates a configuration rule. However, software can be distributed using the configuration rule. One embodiment will be described in detail below.

FIG. 11 is a flowchart showing an embodiment in which the present invention is applied to software distribution. FIG. 12 is a flowchart showing a configuration inspection process of FIG. 11, and FIG. 13 is a difference extraction process of FIG. It is a flowchart which shows. FIG. 14 is a block diagram showing the system configuration of the second embodiment. FIG. 15 shows library information 1407 in which a library name and its version are associated with files constituting the library and file versions.
FIG. 16 is a table configuration example of configuration information 1408 in which a configuration name and its version are associated with a library included in the configuration and its version, and FIG. 17 is a table configuration example of an integration destination and a library. FIG. 18 is a table configuration example of a configuration rule 1409 representing a rule predetermined for correspondence, and FIG. 18 is a table configuration example of installation information 1410 indicating an installation destination and a library installed in the installation destination. FIG. 19 shows a list display example of the library, and FIG. 20 shows a list display example of the installation destination.

Referring to FIG. 14, reference numeral 1401 denotes an interactive terminal having a keyboard, a mouse, and a monitor screen, which is used by a user to input an instruction or display an operation instruction to the user. Here, it is the terminal of the distribution source. 1402
Is a CPU having a sequential processing function of a program.
Reference numeral 403 denotes a main storage device accessed by the CPU 1402, and reference numeral 1404 denotes an auxiliary storage device used to hold data and programs. Reference numeral 1405 denotes a program for executing the processing procedure of FIG. 11, and reference numeral 1406 denotes a change history file to be subjected to configuration management in this system, which is managed by UNIX RCS. It may be a file managed by SCCS or another version control tool. Reference numeral 1407 denotes a file holding library information, 1408 denotes a file holding configuration information, 1409 denotes a file holding configuration rules, and 1410 denotes a file holding embedded information. There is a file 1411 included in the installation destination. An interactive terminal 1412 is a distribution destination.

Next, the second embodiment will be described in detail with reference to FIGS. 14 to 20 based on the flowcharts of FIGS.

First, a list of libraries is displayed on the interactive terminal 1401 with reference to the library information 1407 (110).
0). FIG. 19 shows a display example of the library list. Further, a list of installation destinations is displayed with reference to the installation information (1101). FIG. 20 shows an example of the display. The library name and version selected by the user from the library list and the installation destination, configuration name, and version selected from the installation destination list are stored (1102). In the case of this example, the library name “PGM2” 19 in the library list
00, version “1.1” 1901, installation destination “host001” 2000, configuration name “A” 2001, and version “1.0” 2002 in the installation destination list. Next, when the library is incorporated, the configuration check processing 11 is performed to determine whether or not the configuration rule 1409 is met.
Perform 03. In the configuration check processing, the configuration destination 1700, the configuration name 1701, the version 17
02 is read one by one (1200), step 11
Step 1200 is repeated until the installation destination stored in step 02 and the installation destination 1700 acquired in step 1200 match. Next, the configuration name 160 is obtained from the configuration information 1408.
0 and the version 1601, and the correspondence between the array of the library name 1602 and the array of the library version 1603 are read one by one (1202), and the configuration name 1701 and the version 1702 obtained in the step 1200 and the step 1
Configuration name 1600 and version 160 acquired in 202
Step 1202 is repeated until each of the two matches.
Then, in the set obtained and matched in step 1202,
It is determined whether the library name and its version stored in step 1102 are included (1204),
If it is not included, the fact that it violates the composition rule is stored (1205). In this example, the configuration name and version corresponding to the installation destination “host001” 1703 are “A” 1704 and “1.1” 1705 in the configuration rule, and the configuration name “A” 1604 and the version “ 1.1 ”1605, library name“ PGM2 ”1606 of the target library, version“ 1.1 ”16
07 is included. The above is the configuration inspection processing 1103. If composition rule 1409 is met,
A difference extraction process 1105 is performed. Library information 1407
From the library name 1500 and the version 1501, the storage location 1502 of the change history file 1406 and the file name 1503 and the version 1504 are read as a set (1300), and the library name and version to be incorporated stored in the step 1102 are read. It is determined whether or not each matches (1301). Next, from the configuration information 1408, the configuration name 1600 and the version 1601,
Library name 1602 and library version 16
03 and the array is read one by one (130
2) It is determined whether the configuration name and the version stored in step 1102 match each other (1303). Then, the library name 15 is obtained from the library information 1407.
00 and version 1501, history accumulation file 1406
Of the storage destination 1502, its file name 1503, and version 1504 are read as a set (130).
4) It is determined whether the currently installed library name and version acquired in step 1302 match each other (1305). In this example, the library name “A” 1507 to be incorporated and the version “1.
Library information 1407 corresponding to “1” 1508, library information corresponding to the currently incorporated “A” 1505, version “1.0” 1506, and a change history file changed by both libraries “Sub1. c, v "1509 to version" 1.
The file of “1” 1510 is extracted. Then, the file extracted in step 1105 is distributed to the installation destination 1412 (1106).

In this embodiment, since only the changed difference is distributed, the transfer time can be reduced without imposing a load on the communication line, and the software can be distributed according to the configuration rules.

In the above embodiment, an example of distribution to one machine has been described. However, it is needless to say that the present invention can be applied to incorporation into a large number of distribution destinations.

The present invention can be applied to a case where the extracted differences are stored and distributed in an external storage medium such as a floppy disk or digital audio tape even if they are not connected by a communication line.

[0027]

As described above, according to the present invention, it is necessary to check whether or not the software configuration of each terminal conforms to a predetermined configuration rule and display the same. It is possible to recognize the incompatible terminal and correct the unjust state.

When distributing software,
Since only the changed files are extracted, the transfer time can be reduced, and the software can be distributed according to the configuration rules.

[Brief description of the drawings]

FIG. 1 is a flowchart illustrating a processing procedure according to a first embodiment.

FIG. 2 is a flowchart showing a configuration inspection process of FIG. 1;

FIG. 3 is a flowchart showing a list display process of FIG. 1;

FIG. 4 is a flowchart showing a configuration information display process of FIG. 3;

FIG. 5 is a block diagram showing a system configuration of the first embodiment.

FIG. 6 is a table configuration example of configuration information handled in the first embodiment.

FIG. 7 is a table configuration example of a configuration rule handled in the first embodiment.

FIG. 8 is a table configuration example of embedded information handled in the first embodiment.

FIG. 9 is a display example of a list of installation destinations that do not match the configuration rules handled in the first embodiment.

FIG. 10 is a display example of configuration information handled in the first embodiment.

FIG. 11 is a flowchart illustrating a processing procedure according to the second embodiment.

FIG. 12 is a flowchart illustrating a configuration inspection process of FIG. 11;

FIG. 13 is a flowchart illustrating a difference extraction process of FIG. 11;

FIG. 14 is a block diagram illustrating a system configuration according to a second embodiment.

FIG. 15 is a table configuration example of library information handled in the second embodiment.

FIG. 16 is a table configuration example of configuration information handled in the second embodiment.

FIG. 17 is a table configuration example of a configuration rule handled in the second embodiment.

FIG. 18 is a table configuration example of embedded information handled in the second embodiment.

FIG. 19 is a display example of a library list.

FIG. 20 is a display example of an installation destination list.

[Explanation of symbols]

100 embedded information acquisition processing 101 step 10
0: end determination, 102: configuration inspection process, 103: determination of existence of configuration rule violation, 104: list display process, 200
··· Configuration rule acquisition processing, 201: End determination of step 200, 202: Integration destination comparison processing, 203: Configuration name comparison processing, 204: Version comparison processing, 205: Configuration rule absent Storage processing, 206: Configuration rule violation storage processing, 300: Acquisition of contents stored in steps 205 and 206, 301: End determination of step 300, 30
2 ... Display the contents stored in steps 205 and 206; 303 ... configuration information display determination processing; 304 ... configuration name and version acquisition processing; 305 ... step 30
4 end determination, 306... Configuration information display processing, 400.
Configuration information acquisition processing, 401: end determination of step 400, 402: configuration name comparison processing, 403: version comparison processing, 404: display of contents acquired in step 400, 405: applicable Display that no configuration information exists, 500 ... interactive terminal, 502 ... CPU, 503 ...
A main storage device, 504 an auxiliary storage device, 505 a program, 506 a file, 507 configuration information, 50
8: Configuration rule, 509: Embedded information, 600: Configuration name, 601: Version, 602: Library name, 603: Version, 604: Configuration name "A",
605: version "1.0", 606: library name "PGM1", 607: version "1.0",
608: Library name “PGM2”, 609: Version “1.0”, 610: Library name “PGM”
3 ", 611: version" 1.0 ", 700: installation destination, 701: configuration name, 702: version, 70
3 ... Installation destination "host001", 704 ... Configuration name "A", 705 ... Version "1.1", 800 ... Installation destination, 801 ... Configuration name, 802 ... Version , 8
03 ... Installation destination "host001", 804 ... Configuration name "A", 805 ... Version "1.0", 900 ...
Configuration name “host001”, 901... Embedded information configuration name, 902... Embedded information version, 903.
··· Configuration name of embedded information “A”, 904: Version of embedded information “1.0”, 905: Configuration name of configuration rule, 906: Version of configuration rule, 907: Configuration rule Configuration name “A”, 908... Configuration rule version “1.1”, 1100... Library list display, 11
01: display of a list of installation destinations; 1102: storage of items specified by the user; 1103: configuration inspection processing;
104: Configuration rule conformity comparison process, 1105: Difference extraction process, 1106: Distribution process, 1200: Configuration rule acquisition process, 1201: Integration destination comparison process, 1202: Configuration information acquisition Processing, 1203: Configuration name and version comparison processing, 1204: Judgment as to whether or not the target library is included, 1205: Storage that violates the configuration rule, 1
300: library information acquisition processing, 1301: library name and version comparison processing to be incorporated, 13
02 ... Configuration information acquisition processing, 1303 ... Step 110
Comparing the configuration name and version stored in step 2, 13
04: comparison processing of library name and version already incorporated, 1306: determination of existence of changed file, 1307: file extraction processing, 1401: interactive terminal serving as a distribution source, 1402 ... CPU, 1403: Main storage device, 1404: Auxiliary storage device, 1405: Program, 1406: Change history file, 1407: Library information, 1408: Configuration information, 1409 ... Configuration rule, 1410 embedded information, 1411 file,
1412: distribution destination interactive terminal 1500: library name, 1501: version, 1502: storage destination, 1
503: file name, 1504: version, 15
05: Library name “PGM2”, 1506: Version “1.0”, 1507: Library name “PG
M2 ", 1508 ... version" 1.1 ", 1509
..File name "sub1.c, v", 1510 ... version "1.1", 1600 ... configuration name, 1601
..Version, 1602... Library name, 1603.
..Version, 1604... Configuration name "A", 1605.
..Version "1.1", 1606... Library name "PGM2", 1607... Version "1.1", 1
700 ... installation destination, 1701 ... configuration name, 1702 ...
-Version, 1703: Installation destination "host00"
1 ", 1704 ... Configuration name" A ", 1705 ... Version" 1.1 ", 1900 ... Library name" PGM "
2 ", 1901 ... version" 1.1 ", 2000 ...
Installation destination “host001”, 2001... Configuration name “A”, 2002... Version “1.0”

Claims (4)

[Claims] In a library management method in an information processing apparatus having a computer and an interactive terminal, a file,
A predetermined configuration rule indicating a correspondence between a certain installation destination and a combination of a configuration name and a version, and an integration indicating a correspondence between the integration destination and a combination of a configuration name and a version actually incorporated. Acquiring information and a set of the installation destination, the configuration name, and the version from the integration information; and obtaining the combination of the integration destination, the configuration name, and the version from the configuration rule. The configuration name of the configuration information, the configuration name of the configuration rule, and the version of the configuration information and the configuration if the configuration destination of the configuration information and the configuration destination of the configuration rule match. Checking whether the version of the rule matches with the version of the rule. 2. The library management method according to claim 1, further comprising configuration information indicating a combination of the configuration name and the version and a correspondence between the library name and an array in which the library version is a set, The installation destination, the configuration name, and the version of the configuration information that violates the configuration rule;
Storing the configuration name and the version of the configuration rule; storing that the configuration rule does not exist; displaying the stored content; and specifying the content specified by the user. Displaying the configuration information. 3. A library management method in an information processing apparatus having a computer and an interactive terminal, wherein a correspondence between a change history file storing a change history of a file, a certain installation destination, and a combination of a configuration name and a version is represented. Embedded information indicating correspondence between a predetermined configuration rule, the installation destination, a combination of the configuration name and the version actually installed, a combination of the configuration name and the version, a library Configuration information indicating a correspondence between a name and an array in which a version of the library is set as one set, the library name and the version of the library,
A step of displaying a list by referring to the library information, the library information having library information in which a storage location of the change history file is associated with an array of names and versions, and Displaying a list of destinations, storing the library name and version specified by the user, and storing the installation destination, the configuration name and the version, and determining the integration destination, the configuration name and the version from the configuration rules. Obtaining a set, determining whether the installation destination specified by the user matches the obtained installation destination, a combination of the configuration name and the version from the configuration information, and a library name And obtaining a version of the library as a set. The configuration name and the version specified by the user are Determining whether the library name and the version match each other; and checking whether the library specified by the user is included in the set read together with the obtained configuration name and the version. Comparing the configuration currently installed at the specified installation destination with the specified configuration to determine whether or not the changed or added change history file exists; and A library management method, comprising: extracting a file to be incorporated from a change history file; and distributing the extracted difference to an installation destination. 4. The library management method according to claim 3, further comprising the step of storing the extracted difference in an external storage medium such as a floppy disk.