JP4621709B2 - Version management system and program version management method - Google Patents

Description

  The present invention relates to a technique for managing versions of programs and the like, and more particularly, to a technique for maintaining consistency between a program operating on an active machine and the latest version grasped for version management.

  Patent Literature: A method that uses a program history table that stores program status and so on so that it can be smoothly operated in a large-scale system even when a program administrator is absent or in an emergency, when registering and paying out a program 1.

  Patent Document 2 describes a method for effectively managing computing resources in a large distributed enterprise environment.

JP 2000-47854 A Japanese Patent Laid-Open No. 10-124468

  Here, when upgrading a program or the like, there is an operation of correcting and updating the source file of the program. In a large-scale system in which the same program operates on a plurality of computers, the corrected and updated source files must be distributed and updated on the plurality of computers.

  In addition, immediately after the version upgrade work, the mistake is not noticed, and the mistake may be noticed after a while. For such a case, it is important to manage the history of past version upgrades.

  However, the program that is actually running for some reason may not match the latest version that is grasped by the system. In such a case, it is necessary to properly perform version management with consistency.

  An object of the present invention is to provide a system or the like for matching the history of program upgrades with the actual operating environment.

The version management system according to claim 1 , comprising a development management server, an active machine management server, and an active machine, wherein the version management system performs version management of a program operated on the active machine. The server and the active machine management server are each provided with a freezing area that is a storage area for copying the upgrade source file whose access authority is set and the correction contents are confirmed from the development management server side to the active machine management server side , The active server further includes a resource management area that performs version management of a program source file, identification information acquisition means that periodically acquires identification information of a program operating on the active device, and a resource management area. the identification information acquired identification information of the stored source files and by the identification information acquiring hand stage Based on the difference extracting means for extracting the difference between the latest version of the program with the program running on the working machine is recorded in the resource management area, when the difference is extracted by the difference extraction means, of the difference a difference file acquiring means for acquiring a source file of the corresponding program from the current machine, the latest version of the source file recording means store in the resource management area source file corresponding to the acquired difference as the source file of the latest version of the program When,
It is characterized by providing .

A version management system according to claim 2 is the version management system according to claim 1 , wherein the development management server is a storage area for storing a source file to be upgraded, and a version upgrade system And a work area that is a storage area for storing a modified source file, and when there is a version upgrade instruction specifying differential information to the development management server, the modified source file is stored in the work area. When stored, the development management server compares the modified source file of the work area with the source file of the delivery area to generate a difference file between the two, and compares the difference file with the difference information. If the comparison results in a match, the modified source file is There characterized by storing in the freezing area of development management server as an established source file.

The version management system according to claim 3 is the version management according to claim 1 or 2. The development management server includes a latest version recording unit, and the resource management The difference or the entire source file of the latest version of the program recorded in the area The latest version recording unit is updated at a predetermined timing.

A program version management method according to claim 4 , comprising a development management server, an active machine management server, and an active machine, wherein the version management system performs version management of a program operated on the active machine. The management server and active machine management server each have a freezing area, which is a storage area for copying the version- up source file for which the access authority has been set and the correction details are confirmed from the development management server side to the active machine management server side the active machine server further program source file version control system comprising a resource management area a which manages versions of the source files Te utilization for the program version management method odor was modified using develop management server But it was fixed for version upgrade and the contents were confirmed Storing the source file in a freezing area of the development management server, copying the version-up source file from the freezing area of the development management server to the freezing area of the active machine management server, and the active machine A step of transmitting the upgrade source file from the freezing area of the active machine management server, a step of periodically acquiring identification information of a program operating on the active machine, and the identification information from the active machine Is acquired based on the identification information of the source file stored in the resource management area and the identification information acquired from the active machine, and the latest version stored in the resource management area and the program running on the active machine extracting a difference between the programs, it flops corresponding to the difference Acquiring a source file of grams from the working machine, characterized in that it comprises the steps of: storing in the resource management area source file corresponding to the acquired difference as the source file of the latest version of the program.

  Another first invention according to the present invention is a management device for managing an active machine, comprising means for storing a source file of a latest generation program, and identification information of a program operating on the active machine, The difference between the program operating on the current machine and the latest generation program based on the means for periodically acquiring, the identification information of the source file stored in the storage means and the identification information acquired from the current machine And when the difference is extracted by the extracting means, a means for acquiring a source file of a program corresponding to the difference from the working machine, and the acquired source file in the storage means And a source file of the latest generation program stored in the storage means is connected to the management device. , Characterized in that it comprises a means for transferring to the other management device for managing the source files of the latest generation program.

  Another second invention according to the present invention is the management device according to the first invention, wherein the storage means includes a latest generation area for storing a source file of the latest generation program, and a generation before the latest generation. An old generation storage area for storing the file, and the storage means overwrites the source file of the latest generation storage area corresponding to the acquired source file on the corresponding file of the old generation storage area, Thereafter, the acquired source file is overwritten on the corresponding source file in the latest generation storage area.

  Another third invention according to the present invention is the management apparatus according to the first invention, wherein the identification information of the program includes at least a program name, a size, and an update date.

  According to another fourth aspect of the present invention, there is provided a method for a management apparatus for managing an active machine, the step of periodically obtaining identification information of a program operating on the active machine, and the active machine When the identification information is acquired from the machine, the current machine operates based on the identification information of the source file stored in the storage means for storing the source file of the latest generation program and the identification information acquired from the active machine. Extracting the difference between the current program and the latest generation program, obtaining the source file of the program corresponding to the difference from the active machine, and connecting the obtained source file to the management device, Transferring the source file of the latest generation program to another management apparatus that manages the source file.

  According to one embodiment of the present invention, a management apparatus for managing an active machine periodically acquires means for storing a source file of a latest generation program and identification information of a program operating on the active machine. Means for extracting a difference between the program running on the current machine and the latest generation program based on the identification information of the source file stored in the storage means and the identification information acquired from the current machine; When the difference is extracted by the extraction means, means for acquiring a source file of a program corresponding to the difference from the current machine, and storing the acquired source file as a source file of the latest generation program in the storage means And a source file of the latest generation program stored in the storage means, connected to the management device, And means for transferring to the other management device for managing the source file generation program.

  In a preferred embodiment, the storage means has a latest generation area for storing a source file of the latest generation program, and an old generation storage area for storing a file of a generation before the latest generation, and the storage means , Overwriting the source file of the latest generation storage area corresponding to the acquired source file with the corresponding file of the old generation storage area, and then replacing the acquired source file with the corresponding source file of the latest generation storage area It may be overwritten.

  In a preferred embodiment, the program identification information may include at least a program name, a size, and an update date / time.

  Hereinafter, an embodiment of a version upgrade management system to which the present invention is applied will be described with reference to the drawings.

  FIG. 1 is a diagram showing the overall configuration of the present system. This system has two management servers, a development management server 1 and an active machine management server 2. The active machine management server 2 is connected to a plurality of active machines 3 via a network 9 such as the Internet or a dedicated line, and manages them. In the current machine 3, for example, a plurality of computer programs are operating to provide various services to customers. Each active machine 3 can operate independently.

  The development management server 1 is connected to a version upgrade instruction terminal 4 that receives an input of a version upgrade instruction and an administrator terminal 5.

  An administrator terminal 6 is connected to the active machine management server 2. The network 9 is connected to an emergency terminal 7 for further emergency upgrade.

  The development management server 1, the active machine management server 2, the upgrade instruction terminal 4, the administrator terminals 5 and 6, and the emergency terminal 7 are all configured by a general-purpose computer system, for example. Individual components or functions are realized by, for example, executing a computer program.

  As its internal functions, the development management server 1 performs a numbering database 11 for automatically assigning unique management numbers, a delivery area for temporarily storing a version upgrade target file, and editing a version upgrade target file. The work area 13 for editing, the editor 14 for editing the source program, and the latest generation area 15 for storing the source file of the latest generation program operating on the current machine have been upgraded (modified) And a freezing area 16 for storing files.

  When the active machine management server 2 receives the transfer of the file frozen by the development management server 1, the active machine management server 2 stores a freezing area 21 for storing the file, a resource management area 22 for generation management of the source file of the program, A third generation area 23 for storing third generation resources, an emergency change area 24 for temporarily storing an emergency changed file sent from the active machine 3 when there is an emergency change, and Is provided.

  The freezing areas 16 and 21 are storage areas in which access authority is set so that only a specific administrator can access. The manager who can access the freezing area 16 and the manager who can access the freezing area 21 may be the same person or different persons. As will be described later, the frozen areas 16 and 21 are areas for storing source files that have been modified for version upgrade and whose contents have been determined, and have a security function for preventing unauthorized rewriting.

  The resource management area 22 is a storage area for managing the generation of source files of programs whose upgrades are repeated. In the resource management area 22, a plurality of types of files, the latest generation area 221 for storing the latest files, the first generation area 222 as an old generation storage area for storing files of generations before the latest generation, There is a second generation area 223. That is, the active machine management server 2 performs generation management of the above three generations of source files including the latest generation.

  The third generation area 23 is an area for storing a third generation source file that is one generation before the second generation that is not to be managed as the active machine management server 2. The third generation area 23 may be a hidden database.

  In the system having the above-described configuration, processing when upgrading the program operating on the active machine 3 will be described.

<Upgrade instruction>
The development management server 1 receives a version upgrade instruction for a program running on the active machine 3 in the procedure as shown in FIG.

  The upgrade instruction is input to the upgrade instruction terminal 4 (S11). For example, the worker inputs upgrade request information from an upgrade request input screen (hereinafter referred to as an input screen) using an input / output device (not shown) of the upgrade instruction terminal 4.

  For example, as shown in FIG. 3, the input screen 100 includes input areas for the following items. That is, on the input screen 100, the target system name 101, the scheduled release date 102, the upgrade work start and end date and time 103, the priority order 104, the influence degree 105, the upgrade target file name 106, the target active machine 107, and the upgrade instruction There are input areas for the person in charge 108, the person in charge of upgrading 109, the work instruction sheet 110, and the difference evidence 111.

  Here, with respect to the priority order 104, when a plurality of files are upgraded, the order of the work is input when the work of the upgrade has an order.

  The upgrade target program can be identified by the upgrade target file name 106.

  In the work instruction sheet 110, a file name of a document describing a detailed procedure of a version upgrade work created in advance is input.

  In the difference evidence 111, the file name of the file indicating the difference before and after the correction of the source file to be upgraded is input. For example, it is generated when an upgrade instructor or the like confirms the upgrade in advance in a test environment or the like. As will be described later, this is used when confirming the validity of the upgrade work.

  When necessary information is input on the input screen 100, the upgrade instruction terminal 4 assigns a management number for this upgrade work from the numbering database 11 (S12).

  The upgrade instruction terminal 4 instructs to extract the source file specified by the upgrade target file name 106 from the latest generation area 15 (S13).

  Then, the upgrade instruction terminal 4 transfers the work request information input on the input screen 100 to the development management server 1, and associates the work request information with the source file extracted by the instruction in step S13 in the delivery area 12. Store (S14). At this time, the work instruction sheet 110 and the difference evidence 111 may be associated with each other.

  Since the preparation for the upgrade work is completed, the upgrade instruction start instruction is sent from the upgrade instruction terminal 4 to the development management server 1 (S15).

<Create upgrade resources>
Next, a procedure for creating a frozen file for version upgrade will be described with reference to FIG. Here, the frozen file means a file in which the source file has been corrected and changed and is not desired to be changed any more.

  First, the development management server 1 copies the source file to be upgraded stored in the delivery area 12 to the work area 13 (S21). Then, the version upgrade operator activates the editor 14 using the manager terminal 5, and corrects and updates the source file in the work area 13 (S22). This correction is performed according to the work instruction. The corrected source file is stored in the work area 13.

  When the correction work is completed, the development management server 1 compares the source file before the correction with the source file after the correction, and generates a difference file indicating the difference between the two (S23).

  Then, the development management server 1 compares the difference file generated here with the difference evidence 111 specified on the input screen (S24). As a result of the comparison, if the two do not match (S24: NG), the operator is notified of this by outputting a message window or the like, and step S22 and subsequent steps are repeated. On the other hand, if the results of this comparison match (S24: OK), the modified source file is copied to the frozen area 16 based on the instructions of a specific administrator who is authorized to access the frozen area 16. .

  As a result, the source file (frozen file) to be upgraded is determined and stored in the frozen area 16 with high confidentiality. By storing the confirmed file in the freezing area 16, the possibility that the file is accidentally rewritten or intentionally rewritten is reduced, and the file is stored with higher security.

<Upgrade resource change>
Next, a procedure for updating a program that is actually running on the active machine after the file is frozen will be described with reference to FIGS. The following processing can also be performed by, for example, an operator inputting a predetermined command from the administrator terminal 6.

  First, the frozen source file is copied from the freezing area 16 of the development management server 1 to the freezing area 21 of the active machine management server 2 (S31). At this time, the work request information and the work instruction sheet may be copied together. Then, a list of source files stored in the freezing area 21, that is, a list of programs to be upgraded is output (S32).

  This file list includes, for example, file identification information such as a file name (including a folder name), a file size, and a file update date / time. The file list generated in the following description includes the same items.

  The active machine management server 2 transmits the source file stored in the freezing area 21 to the current machine 3 to be updated (S33). The active machine 3 receives the transmitted file.

  Then, the active machine management server 2 instructs the active machine 3 to generate and transmit a file list of the received program, and obtains a file list from each active machine 3 (S34). By confirming this list, it is confirmed that the file transfer to the working machine 3 has been performed without any problem.

  Thereafter, the current machine 3 is instructed to back up the source file of the program currently running on the current machine 3 (S35). In response to this instruction, each active machine 3 backs up the current environment.

  Then, the active machine management server 2 instructs to update (upgrade) to the program newly sent to each active machine 3 in step S33 (S36). Upon receiving this instruction, the current machine 3 updates (upgrades) the program according to the instruction. At this time, conversion to an executable program is performed as necessary.

  The active machine management server 2 instructs the active machine 3 to generate and transmit a file list of the upgraded program, and acquires a file list from each active machine 3 (S37).

  Here, the file list generated in step S32 is compared with the file list acquired in step S37 (S38). As a result of the comparison, if the two do not match (S38: NG), step S33 and subsequent steps are repeated. As a result of the comparison, if the two match (S38: OK), the file list acquired in step S37 is stored, and the active machine 3 is instructed to restart (S39, S40). When the working machine 3 operates normally, the process ends as it is (S41: OK). When the active machine 3 does not operate normally, the environment before the upgrade is restored based on the data backed up in step S33, and an instruction is given to restart (S42).

  By executing the procedure described above, the version upgrade can be executed reliably.

<Generation management>
Next, a plurality of generations of each resource are stored in the resource management area 22 of the active machine management server 2. When the upgrade described above is completed, these generations are changed in order to maintain consistency with the current machine. Hereinafter, the processing procedure will be described with reference to FIG.

  When the upgrade is completed, the second generation source file of the upgrade target program stored in the second generation area 223 is copied to the third generation area 23 (S51). In this process, the database is not renamed, but only the source file of the program whose version has been upgraded is copied. The same applies hereinafter.

  Next, the first generation source file of the upgrade target program stored in the first generation area 222 is overwritten on the corresponding file in the second generation area 223 (S52).

  Next, the latest generation source file of the upgrade target program stored in the latest generation area 221 is overwritten on the corresponding file in the first generation area 222 (S53).

  Finally, the source file of the upgrade target program stored in the freezing area 21 is overwritten on the corresponding file in the latest generation area 221 (S54).

  It is confirmed whether or not an error has occurred in the above processing and the processing has been completed normally (S55). If not normal (S55: NG), step S51 and subsequent steps are repeated. If it is normal (S55: OK), the development management server 1 is notified of the file name and the like, and an instruction is given to update the source file in the latest generation area 15 of the development management server 1 (S56). In accordance with this instruction, the development management server 1 overwrites the corresponding file in the latest generation area 15 with the source file stored in the frozen area 16 specified by the notified file name or the like.

  Thereby, the development management server 1 also ensures consistency with the latest version.

<Emergency change>
The normal processing procedure for upgrading the program operating on the current machine 3 has been described above. However, in actual system operation, there are times when it is necessary to upgrade the version as soon as possible. In such a case, even the time required by following the above procedure is too long. In such a case, an emergency change is performed in which the version of the working machine 3 is upgraded directly from the emergency change terminal 7. Hereinafter, the emergency change procedure will be described with reference to FIG.

  Based on the operator's instruction, the emergency change terminal 7 directly transmits the modified source file to the active machine 3 to upgrade the version (S61). Then, it is confirmed whether or not the emergency change version upgrade succeeds and operates normally (S62).

  When it is not normal (S62: No), it returns to before version upgrade (S63). When it is normal (S62: Yes), the active machine management server 2 acquires the file list of the latest generation area 221 (S65). A file list of programs running on the active machine 3 is acquired from the active machine 3 (S64). These file lists are compared, the difference between the program running on the current machine 3 and the program managed in the latest generation area 221 is extracted, and the program upgraded by emergency change is specified (S66). ).

  The active machine management server 2 acquires the source file after the upgrade specified here from the active machine 3 that has been upgraded, and stores it in the emergency change database 24 (S67). Then, the generation change of the active machine management server 2 is performed according to the procedure described in FIG. 7 (S68). In step 54 in FIG. 7, the source file stored in the freezing area 21 is copied to the latest generation area, but here the source file stored in the emergency change database 24 is copied.

  With the above procedure, even when an emergency change is made, the consistency of the generation of source files managed by the active machine management server 2 is ensured.

<Consistency check>
Next, a description will be given of a program version check periodically performed during normal operation.

  In principle, the source file of the program stored in the latest generation area 221 of the active machine management server 2 and the program actually running on the active machine 3 are in correspondence. However, for some reason, this correspondence may be shifted. It is not preferable to leave such a correspondence shift. Therefore, a consistency check is performed in the procedure as shown in FIG. 9 to restore the correspondence. This process is preferably started periodically.

  First, Steps S64 to S68 shown in FIG. 8 are performed to acquire a difference file between the program running on the current machine and the latest generation, and match the latest generation area 221 with the current machine 3 (S71).

  The updated file name acquired in step S71 is transferred to the development management server 1 (S72). The development management server 1 copies the transferred file to its latest generation area 15. As a result, the version of the development management server 1 is also restored to a consistent state.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

1 is a diagram illustrating an overall configuration of a version upgrade management system according to an embodiment to which the present invention is applied. It is a flowchart which shows the reception procedure of the program upgrade instruction. It is a figure which shows an example of a version-up work request input screen. It is a flowchart which shows the preparation procedure of the frozen file for performing version upgrade. It is a flowchart which shows the procedure which updates a program. It is a flowchart which shows the procedure which updates a program. It is a flowchart which shows the procedure which performs the generation change of a resource. It is a flowchart which shows the process sequence of an emergency change. It is a flowchart which shows the process sequence for ensuring consistency.

DESCRIPTION OF SYMBOLS 1 ... Development management server, 2 ... Active machine management server, 3 ... Active machine, 4 ... Version upgrade instruction terminal, 5, 6 ... Administrator terminal, 7 ... Emergency terminal, 9 ... Network.

Claims (4)

And development management server, and the working machine management server, and the working machine, comprising a, a version control system for the version management of the program Ru is operated by the working machine,
Development management server as the working machine management server, access rights are set, the frozen area is a storage area of the order to copy the version-up source file modification contents is finalized to develop the management server or al working machine management server Prepare for each
The active machine server further comprises a resource management area for version control of the source files for the program,
Identification information acquisition means for periodically acquiring identification information of a program running on the current machine ;
Wherein based on the identification information acquired by the identification information and the identification information acquiring means for source files stored in the resource management area, the latest version recorded with programs running on the working machine to the resource management area a difference extracting means for extracting the difference between the programs, the difference is extracted by the difference extraction means, a difference file acquiring means for acquiring a source file of a program corresponding to the difference from the current machine,
Latest version source file recording means for storing in the resource management area a source file corresponding to the obtained difference as a source file of the latest version of the program ;
A version management system comprising: The development management server comprises a delivery area that is a storage area for storing a source file to be upgraded, and a work area that is a storage area for storing a modified source file for version upgrade. If there is a version upgrade instruction designating difference information for the work area, and the modified source file is stored in the work area, the development management server causes the modified source file of the work area and the delivery to be delivered. Compare the source file of the area to generate a difference file between the two, compare the difference file with the difference information, and if the comparison results in a match, the contents of the modified source file are confirmed. Stored as a source file in the frozen area of the development management server Version management system according to Motomeko 1. The development management server includes a latest version recording means and is recorded in the resource management area. The difference or whole of the source file of the latest version of the program is 3. The latest version recording means is updated at the above. Version control system. And development management server, and the working machine management server, and the working machine, comprising a, a version control system for the version management of the program Ru is operated by the working machine,
Development management server as the working machine management server, access rights are set, the frozen area is a storage area of the order to copy the version-up source file modification contents is finalized to develop the management server or al working machine management server provided in each of the active machine server further in program version management method take advantage of the version control system comprising a resource management area for version control of the source files for the program,
Storing a source file that has been modified using a development management server and that has been modified for version upgrade and whose contents have been confirmed in a freezing area provided in the development management server; Copying the upgrade source file from the freezing area to the freezing area of the active machine management server; transmitting the upgrade source file from the freezing area of the active machine management server to the active machine;
A step of periodically obtaining identification information of a program running on the current machine, and obtaining the identification information from the current machine, the source file identification information stored in a resource management area and the current machine based on the obtained identification information; you extracts the difference between the latest version of the program the stored in the resource management area and program operating on the working machine, the source file for the program corresponding to the difference wherein the step you get from the current machine, program version management method for storing the source file corresponding to the acquired difference in the resource management area as the source file of the latest version of the program, comprising: a a.

Images