JP2004310230A - System and method for version-up of program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To restrain mistakes generated in version-up work of a program to the utmost. <P>SOLUTION: This system/method is provided with a current equipment control server 2 for controlling a current equipment, and a development control server 1 connected to the current equipment control server 2, and executes version-up for the program operated in the current equipment 3. The development control server 1 is provided with the newest generation area 15 for storing a source file of the program operated in the current equipment 3, and a means for extracting the source file of a version-up object from the area 15, an editor 14 for correcting the extracted source file, and a storage area 12 for storing the source file after corrected. The current equipment control server 2 is provided with a freezing area 21 for storing the corrected source file transmitted from the development control server 1, and a means for transmitting the corrected source file to the current equipment 3 to indicate the version-up. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technique for updating a version-upgraded file, and more particularly to a technique for transferring a version-upgraded file from a management server to an active device in which a program to be upgraded is running and operating the program.
[0002]
[Prior art]
In a large-scale system, a method of registering and paying out a program using a program history table storing the state of the program and the like so that the program can be smoothly operated even in the event of an emergency even when a program manager is not present in Patent Document 1.
[0003]
Patent Document 2 describes a method for effectively managing computing resources in a large distributed enterprise environment.
[0004]
[Patent Document 1]
Japanese Patent Application Laid-Open No. 2000-47854 [Patent Document 2]
JP 10-124468 A
[Problems to be solved by the invention]
Here, when a version of a program or the like is upgraded, there is a task of modifying and updating a source file of the program. In a large-scale system in which the same program runs on a plurality of computers, the modified and updated source files must be distributed to the plurality of computers and updated. At this time, if the work procedure is not clear, the program to be distributed may be mistaken.
[0006]
An object of the present invention is to provide a system or the like for minimizing mistakes caused by a program version-up operation.
[0007]
[Means for Solving the Problems]
A system according to one embodiment of the present invention includes a first management device that manages an active device, and a second management device that is connected to the first management device, and a program running on the active device. A second management device for storing a source file of a program running on the active device; and a source file to be upgraded from the storage unit. , An editor for correcting the extracted source file, and a second storage means for storing the corrected source file. The first management device includes: A third storage unit for storing the modified source file transferred from the management device; and a third storage unit for transmitting the modified source file to the active device to issue a version upgrade instruction. And a stage.
[0008]
In a preferred embodiment, an access right of the second storage unit is limited so that only a specific administrator who manages the second management device can access the second storage unit. The access authority may be restricted so that only a specific administrator who manages one management device can access.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of a version upgrade management system to which the present invention is applied will be described with reference to the drawings.
[0010]
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 device management server 2. The active device management server 2 is connected to and manages a plurality of active devices 3 via a network 9 such as the Internet or a dedicated line. In the active device 3, for example, a plurality of computer programs are operating and provide various services to customers. Each working machine 3 can operate independently.
[0011]
The development management server 1 is connected to a version upgrade instruction terminal 4 that receives an input of a version upgrade instruction, and a manager terminal 5.
[0012]
An administrator terminal 6 is connected to the active device management server 2. An emergency terminal 7 for further performing an emergency version upgrade is connected to the network 9.
[0013]
The development management server 1, the active device management server 2, the upgrade instruction terminal 4, the administrator terminals 5, 6 and the emergency terminal 7 are all configured by, for example, a general-purpose computer system. The individual components or functions within are realized, for example, by executing a computer program.
[0014]
As its internal functions, the development management server 1 edits a numbering database 11 for automatically numbering unique management numbers, a delivery area for temporarily storing files to be upgraded, and files to be upgraded. Area 13, an editor 14 for editing a source program, a latest generation area 15 for storing a source file of the latest generation program running on the active device, and And a frozen area 16 for storing files.
[0015]
When receiving the transfer of the file frozen by the development management server 1, the active device management server 2 stores a frozen area 21 for storing the file, a resource management area 22 for generationally managing the source file of the program, and A third generation area 23 for storing third generation resources, and an emergency change area 25 for temporarily storing an emergency changed file sent from the active device 3 when an emergency change occurs. Is provided.
[0016]
Each of the frozen areas 16 and 21 is a storage area to which an access right is set so that only a specific administrator can access. The administrator who can access the frozen area 16 and the administrator who can access the frozen 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 protection function to prevent unauthorized rewriting.
[0017]
The resource management area 22 is a storage area for managing the generation of a source file of a program that is repeatedly upgraded. The resource management area 22 includes, for a plurality of types of files, a latest generation area 221 for storing respective latest files, a first generation area 222 as an old generation storage area for storing files of a generation earlier than the latest generation, There is a second generation area 223. That is, the active device management server 1 performs generation management of the source files for the above three generations including the latest generation.
[0018]
The third generation area 23 is an area for storing a third generation source file that is one generation earlier than the second generation that is not to be managed as the active device management server 1. The third generation area 23 may be a hidden database.
[0019]
In the system having the above configuration, a process for upgrading the version of a program operating on the active device 3 will be described.
[0020]
<Version upgrade instruction>
The development management server 1 accepts a version upgrade instruction of a program running on the active device 3 in a procedure as shown in FIG.
[0021]
The instruction to upgrade is input to the upgrade instruction terminal 4 (S11). For example, an operator uses a not-shown input / output device of the upgrade instruction terminal 4 to input upgrade request information from a upgrade request input screen (hereinafter referred to as an input screen).
[0022]
The input screen 100 includes input areas for the following items, for example, as shown in FIG. That is, on the input screen 100, the target system name 101, the scheduled release date 102, the start and end date and time of the upgrade work 103, the priority order 104, the impact level 105, the upgrade target file name 106, the target active device 107, There are input areas for a manager 108, a version upgrade manager 109, a work order 110, and difference evidence 111.
[0023]
Here, in the case of performing the version upgrade of a plurality of files, when the work of the version upgrade has a sequence, the order of the work is input.
[0024]
The upgrade target program name can be identified by the upgrade target file name 106.
[0025]
In the work instruction sheet 110, a file name or the like of a document that describes a detailed procedure of a version upgrade work created in advance is input.
[0026]
In the difference evidence 111, a file name of a file indicating a difference between a source file to be upgraded and a source file before and after correction is input. For example, it is generated when a version upgrade instructor or the like confirms version upgrade in a test environment or the like in advance. As will be described later, this is used when confirming the validity of the version upgrade work.
[0027]
When necessary information is input on the input screen 100, the upgrade instruction terminal 4 assigns a management number for the upgrade work from the assignment database 11 (S12).
[0028]
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).
[0029]
Then, the version 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. It is stored (S14). At this time, the work instruction 110 and the differential evidence 111 may be further associated.
[0030]
Since the preparation for the upgrade is completed, the upgrade instruction terminal 4 notifies the development management server 1 of an instruction to start the upgrade (S15).
[0031]
<Upgrade resource creation>
Next, a procedure for creating a frozen file for upgrading will be described with reference to FIG. Here, the frozen file is a file in which the source file has been corrected and changed, and is not desired to be changed any more.
[0032]
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 upgrade operator activates the editor 14 using the administrator terminal 5, and corrects and updates the source file in the work area 13 (S22). This correction is made according to the work order. The corrected source file is stored in the work area 13.
[0033]
When the modification work is completed, the development management server 1 compares the source file before modification with the source file after modification, and generates a difference file indicating the difference between the two (S23).
[0034]
Then, the development management server 1 compares the generated difference file 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), a message window is output to notify the worker of the fact, and the process from step S22 is repeated. On the other hand, if the result of this comparison is a match (S24: OK), the modified source file is copied to the frozen area 16 based on the instruction of the specific administrator who has been given access authority to the frozen area 16. .
[0035]
Thereby, the source file (frozen file) to be upgraded is determined and stored in the frozen area 16 with high confidentiality. By storing the determined file in the frozen area 16, the possibility that the file is erroneously rewritten or intentionally rewritten is reduced, and the file is stored with higher security.
[0036]
<Upgrade resource change>
Next, a procedure for updating a program actually running on the active device after the file is frozen will be described with reference to FIGS. The following processing can be performed, for example, by an operator inputting a predetermined command from the administrator terminal 6.
[0037]
First, the frozen source file is copied from the frozen area 16 of the development management server 1 to the frozen area 21 of the active device management server 2 (S31). At this time, the work request information and the work instruction may be copied together. Then, a list of source files stored in the frozen area 21, that is, a list of programs to be upgraded is output (S32).
[0038]
The 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 and time. The file list generated in the following description includes the same items.
[0039]
The active device management server 2 transmits the source file stored in the frozen area 21 to the active device 3 to be updated (S33). The active device 3 receives the transmitted file.
[0040]
Then, the active device management server 1 instructs the active device 3 to generate and transmit a file list of the received program, and obtains a file list from each active device 3 (S34). By confirming this list, it is confirmed that the file transfer to the active device 3 has been performed without any problem.
[0041]
After that, the active device 3 is instructed to back up the source files and the like of the program currently running on the active device 3 (S35). Each of the active devices 3 receiving this instruction backs up the current environment.
[0042]
Then, the active device management server 1 instructs to update (upgrade) the program newly sent to each active device 3 in step S33 (S36). The active device 3 receiving this instruction updates (upgrades) the program according to the instruction. At this time, conversion to an executable program is performed as necessary.
[0043]
The active device management server 1 instructs the active device 3 to generate and transmit a file list of the upgraded program, and acquires a file list from each active device 3 (S37).
[0044]
Here, the file list generated in step S32 is compared with the file list obtained in step S37 (S38). As a result of the comparison, when the two do not match (S38: NG), the process from step S33 is repeated. As a result of the comparison, if they match (S38: OK), the file list acquired in step S37 is saved, and a restart is instructed to the active device 3 (S39, S40). When the working machine 3 operates normally, the process is terminated (S41: OK). If the active unit 3 does not operate normally, an instruction is given to restore the environment before the version upgrade and restart based on the data backed up in step S33 (S42).
[0045]
By performing the above-described procedure, it is possible to surely execute the version upgrade.
[0046]
<Generation management>
Next, in the resource management area 22 of the active device management server 2, each resource is stored for a plurality of generations. When the above-described version upgrade is completed, these generations are changed in order to ensure consistency with the active device. Hereinafter, the processing procedure will be described with reference to FIG.
[0047]
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). This process does not rename the database, but copies only the source file of the upgraded program. Hereinafter, the same applies.
[0048]
Next, the first generation source file of the version-upgraded program stored in the first generation area 222 is overwritten on the corresponding file in the second generation area 223 (S52).
[0049]
Next, the source file of the latest generation 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).
[0050]
Finally, the source file of the upgrade target program stored in the frozen area 21 is overwritten on the corresponding file in the latest generation area 221 (S54).
[0051]
It is checked whether no 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), it notifies the development management server 1 of the file name and the like, and instructs the development management server 1 to update the source file in the latest generation area 15 (S56). According to this instruction, the development management server 1 overwrites the source file stored in the frozen area 16 specified by the notified file name or the like with the corresponding file in the latest generation area 15.
[0052]
Thus, the development management server 1 also ensures consistency with the latest version.
[0053]
<Urgent change>
The normal processing procedure for upgrading the version of the program operating on the active device 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, the time required by following the above procedure is regrettable. In such a case, an emergency change for upgrading the working machine 3 is performed directly from the emergency change terminal 7. Hereinafter, the emergency change procedure will be described with reference to FIG.
[0054]
Based on the operator's instruction, the emergency change terminal 7 directly sends the corrected source file to the active device 3 to upgrade the version (S61). Then, it is confirmed whether or not the urgent change has been successfully upgraded and operates normally (S62).
[0055]
If the status is not normal (S62: No), the process returns to before the version upgrade (S63). If it is normal (S62: Yes), the active device management server 1 acquires a file list of the latest generation area 221 (S64). From the active device 3, a file list of the programs running on the active device 3 is obtained (S65). By comparing these file lists, the difference between the program running on the active unit 3 and the program managed in the latest generation area 221 is extracted, and the program upgraded by the emergency change is specified (S66). ).
[0056]
The active device management server 1 acquires the source file after the version upgrade specified here from the upgraded active device 3 and stores it in the emergency change database 25 (S67). Then, the generation of the active device management server 1 is changed according to the procedure described with reference to FIG. 7 (S68). In step 54 of FIG. 7, the source file stored in the frozen area 21 is copied to the latest generation area. Here, the source file stored in the emergency change database 25 is copied.
[0057]
Through the above procedure, even when an emergency change is performed, the consistency of the generation of the source file managed by the active device management server 1 is ensured.
[0058]
<Consistency check>
Next, a description will be given of a version check of a program that is periodically performed during normal operation.
[0059]
In principle, there is a correspondence between the source file of the program stored in the latest generation area 221 of the active device management server 2 and the program actually running on the active device 3. However, the correspondence may be shifted for some reason. It is not preferable to leave such a shift in the correspondence. Therefore, a consistency check is performed according to the procedure shown in FIG. 9 to restore the correspondence. This process is preferably started periodically.
[0060]
First, steps S64 to S68 shown in FIG. 8 are performed to obtain a difference file between the program running on the active device and the latest generation, and align the latest generation area 221 with the active device 3 (S71).
[0061]
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.
[0062]
The embodiments of the present invention described above are exemplifications for describing 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.
[Brief description of the drawings]
FIG. 1 is a diagram showing an entire configuration of a version upgrade management system according to an embodiment to which the present invention is applied.
FIG. 2 is a flowchart showing a procedure for receiving a program version upgrade instruction;
FIG. 3 is a diagram showing an example of a version upgrade work request input screen.
FIG. 4 is a flowchart showing a procedure for creating a frozen file for performing version upgrade.
FIG. 5 is a flowchart showing a procedure for updating a program.
FIG. 6 is a flowchart showing a procedure for updating a program.
FIG. 7 is a flowchart illustrating a procedure for changing the generation of a resource.
FIG. 8 is a flowchart illustrating a procedure of an emergency change process.
FIG. 9 is a flowchart illustrating a processing procedure for ensuring consistency.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Development management server, 2 ... Active equipment management server, 3 ... Active equipment, 4 ... Upgrade instruction terminal, 5, 6 ... Administrator terminal, 7 ... Emergency terminal, 9 ... Network.

Claims (3)

A system for upgrading a program running on an active device, comprising: a first management device for managing an active device; and a second management device connected to the first administrative device. ,
The second management device is
First means for storing a source file of a program running on the active device;
Means for extracting a source file to be upgraded from the storage means;
An editor to modify the extracted source files,
Second storage means for storing the corrected source file,
The first management device is
Third storage means for storing the corrected source file transferred from the second management device;
Means for transmitting the corrected source file to the active device and instructing a version upgrade. The second storage means has an access right restricted so that only a specific administrator who manages the second management device can access the second storage device.
2. The system according to claim 1, wherein an access right of the third storage unit is restricted so that only a specific administrator who manages the first management device can access the third storage unit. A method for upgrading a version of a program running on an active device using a first management device that manages the active device and a second management device connected to the first management device,
The second management device is
Extracting a source file to be upgraded from first storage means for storing a source file of a program running on the active device;
Storing the corrected source file obtained by correcting the extracted source file using an editor in a second storage unit;
Transmitting the corrected source file from the second storage means to the first management device.
The first management device is
Storing the corrected source file transferred from the second management device in a third storage unit;
Transmitting the corrected source file from the third storage means to the active device, and instructing a version upgrade.

Images