JP2008165388A - Program update management system, program update management method and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program update management system, a program update management method and a computer program, eliminating room for an act of a person in charge of maintenance to interpose, and allowing an update history to be managed without omission while associating a source program file with an execution form program file. <P>SOLUTION: When inputting instruction information showing a production instruction of EAR file that is a source of a source file from a person-in-charge terminal 1 via a network, an EAR creation server 2 reads the updated source file from a repository server 4 according to the input instruction information to produce the EAR file, incorporates the EAR file into an actual machine 3 via the network, stores (registers) the updated source file and the EAR file produced base thereon into the repository server 4 via the network, and stores (registers) update management data for managing the update history into a database server 5 via the network. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technical field such as a program update management system that manages an update history of a program or the like.

  For example, in a large-scale system of a company where the same execution format program is running on a plurality of computers (hereinafter referred to as “actual machines”), the above execution format is used for function expansion or defect correction in the system. When editing and updating a program, the maintenance person updates (upgrades) the source program file by correcting or adding a part of the source program that is the basis of the executable program. Then, the source program file updated in this way (written in a program language that can be understood by the maintenance staff) is converted into an executable program file (written in a machine language that can be executed by a computer) ( After being compiled, it is incorporated (installed) into the plurality of actual machines.

  Thus, when a program applied to a large-scale system as described above is updated, the update history needs to be strictly managed. In particular, the association between the source program file and the executable program file (association for version matching) is an important management element. In addition, the Japanese version of the SOX (Survein Oxley) Act, which is a law that requires the enhancement of the accounting audit system and the strengthening of internal control of corporations, demands stricter management of the above update history.

  Patent Document 1 discloses a technique that can eliminate version inconsistency after compilation. Here, from a source (corresponding to a source program file) to a binary file (corresponding to an executable program file). Conversion (compilation) and their association (creation of new version software configuration information) are performed in the developer client 1.

On the other hand, Patent Document 2 adds source file attribute information (including source file location information and data changed according to source file reorganization) to an executable file translated into a machine language. Discloses a technique that makes it possible to check the consistency between an executable file and a source file that is the source of the executable file.
JP 2006-302066 A JP 2003-256202 A

  However, in the technique of Patent Document 1, since the correspondence between the source and the binary file is performed by the developer client 1, it cannot be denied that the developer (maintenance staff) is involved.

  On the other hand, in the technique of Patent Document 2, the consistency between the execution file and the source file is not sufficient because it can only be determined by the attribute information of the source file. It is not.

  The present invention has been made in view of the above points and the like, eliminates the space for maintenance personnel's work, and can manage the update history without omission while associating the source program file with the executable program file. An object of the present invention is to provide a program update management system, a program update management method, and a computer program.

  In order to solve the above problem, the invention according to claim 1 is created by a source program file updated by a first computer and a second computer different from the first computer based on the source program file. A program update management system for managing an update history of the executable program file executed by the third computer, wherein the second computer stores the source program file updated by the first computer The first storage means and instruction information indicating an instruction to create the executable program file are input, and the updated source program file is read from the first storage means in accordance with the input instruction information. Execution format program creation means for creating the execution format program file, and the updated source program And program files, to said executable program which is prepared based on this, a second storage means for storing, and update management data for managing the update history, comprising: a.

  According to a second aspect of the present invention, in the program update management system according to the first aspect, the first storage means includes a source program file updated by the first computer and the non-updated source program. And the executable program creation means stores the updated source program file and the non-updated source program file in accordance with the inputted instruction information. And the second storage means reads the updated source program file, the non-updated source program file, the one executable program, and the second storage means. The update management including information for specifying an updated source program file And to store and over motor, the.

  According to a third aspect of the present invention, in the program update management system according to the first or second aspect, the second computer inputs the instruction information from the first computer.

  According to a fourth aspect of the present invention, a computer program causes a computer to function as the second computer according to any one of the first to third aspects.

  According to the fifth aspect of the present invention, a source program file updated by the first computer and a second computer different from the first computer based on the source program file are created and executed by the third computer. A program update management method for managing an update history of the executable program file, a first storage step for storing the source program file updated by the first computer, and creation of the executable program file An input step of inputting instruction information indicating an instruction; an executable program creating step of reading the updated source program file according to the inputted instruction information and creating the executable program file; and the updated Source program file and the above-mentioned created based on this And row format program, characterized by comprising a second storing step of storing, the update management data for managing the update history, the.

  According to the present invention, the update history of the file is stored by storing the updated source program file, the executable program created based on the source program file, and update management data for managing the update history. Therefore, the update history can be managed without omission while associating the source program file with the executable program file.

  Further, since the executable program file is configured to be created by a second computer different from the first computer based on the updated source program file, there is no room for intervention by the maintenance staff. Can do.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, the best embodiment of the invention will be described with reference to the drawings. The embodiment described below is an embodiment when the present invention is applied to a program change management system.

  First, the configuration and function of a program change management system according to an embodiment of the present invention will be described with reference to FIG.

  FIG. 1 is a diagram showing a schematic configuration example of a program change management system according to an embodiment of the present invention.

  As shown in FIG. 1, the program change management system S according to the present embodiment includes a person-in-charge terminal 1 as an example of a first computer, an EAR creation server 2, an actual machine (an actual number machine) as an example of a third computer. ) 3, a repository server 4, a database server 5, and the like. An actual machine 3, a repository server 4, and a database server 5 are connected to the EAR creation server 2 through a network such as a LAN (Local Area Network) and can communicate with each other. In addition, the person-in-charge terminal 1 is connected to the EAR creation server 2 or the repository server 4 via a network and can communicate therewith.

  Here, the EAR creation server 2, the repository server 4, and the database server 5 constitute a second computer in the present invention, the EAR creation server 2 is an executable program creation means, and the repository server 4 is a first storage means. The repository server 4 and the database server 5 constitute second storage means, respectively. The EAR creation server 2, the repository server 4, and the database server 5 may be configured by a single server. A plurality of person-in-charge terminals 1 and actual machines 3 are provided, but in the example of FIG. 1, only one is shown for convenience of explanation.

  The person-in-charge terminal 1 is composed of, for example, a general-purpose personal computer. Although not shown, the person-in-charge terminal 1 inputs a control unit mainly composed of a CPU, a storage unit composed of an HD (hard disk) drive, etc. For example, an operation unit including a keyboard and a mouse, a display unit including a CRT display or a liquid crystal display (LCD), and a communication unit including a communication device for connecting to a network.

  In the person-in-charge terminal 1, a maintenance person operates the operation unit to edit and update a source program (hereinafter referred to as "source") file, and the updated source file is received from the maintenance person. Is stored in the repository server 4 via the network.

  In the present embodiment, a Java program created by Java (registered trademark), which is an object-oriented programming language, will be described as an example.

  The EAR creation server 2, the actual machine 3, the repository server 4, the database server 5, and the like are, for example, server computers. Although not shown, a control unit mainly composed of a CPU, an HD (hard disk) drive, etc. A storage unit, a communication unit including a communication device for connecting to a network, and the like.

  The EAR creation server 2 is input when instruction information indicating an instruction to create an executable program (hereinafter referred to as “EAR”) file that is the source of the source file is input from the person-in-charge terminal 1 via the network, for example. The updated source file is read from the repository server 4 according to the specified instruction information, and an EAR file (module) is created (that is, the source file is converted (compiled) into the EAR file). 3 is built in. At this time, the EAR creation server 2 stores (registers) the updated source file and the EAR file created based on the source file on the repository server 4 via the network, and manages the update history. Update management data is stored (registered) in the database server 5 via a network.

  Next, the operation of the program change management system S according to the present embodiment will be described with reference to FIG.

  FIG. 2 is a diagram showing an example of a file flow in the program change management system S, and FIG. 3 is a flowchart showing a program update process in the EAR creation server 2.

  First, a source file being edited and updated by a maintenance person in the person-in-charge terminal 1 is stored in the development repository 41 in the repository server 4 ((a) of FIG. 2). Note that such editing / updating work is performed by a maintenance person who inputs a user ID and password from the person in charge terminal 1, and a login request including the user ID and password is sent to the repository server 4. Can be performed when login is permitted.

  Then, when the editing / update is completed and the maintenance person inputs a source file registration instruction from the operation unit, a plurality of source files including the updated source file are transferred from the person in charge terminal 1 to the repository server 4. Is sent via the network and stored in the EAR creation repository 42 ((b) of FIG. 2), and the EAR creation instruction information indicating the EAR creation instruction is sent from the person in charge terminal 1 to the EAR creation server 2 via the network. Sent.

  The EAR creation instruction information includes a change management No. The change management No. Is added to the change request sheet data in which information for specifying a program change request (for example, function addition in the actual machine 3) and an updated (changed) source among a plurality of sources (Java programs) is described. It is what is done.

  When the EAR creation server 2 inputs the EAR creation instruction information from the person-in-charge terminal 1, the program update process shown in FIG. 3 is started, and the EAR creation instruction tool 21 (module) executed in the EAR creation server 2 However, the EAR creation tool 22 executed in the server 2 gives an EAR creation instruction, and in response to this, the EAR creation tool 22 sends a plurality of source files including the updated source files (including unupdated source files). 2) from the EAR creation repository 42 (step (c) in FIG. 2), step S1) creates an EAR file (step S2), that is, converts the plurality of source files into one EAR file.

  FIG. 4 is a conceptual diagram showing an example of how an EAR file is created from a plurality of source files. In the example of FIG. 4, the source 3 has been updated. Can be specified.

  Next, the synchronization tool 23 executed in the EAR creation server 2 stores a plurality of source files including the updated source file in association with the created EAR file in the production repository 43 and the update history. Is stored in the program update management DB (database) in the database server 5 ((d) of FIG. 2), step S3).

  The update management data includes the date and time registered in the production repository 43, the file name (or module ID) of the created EAR file, the change management No. (Or change request sheet data) and the reason for deployment are included. Such change management No. This makes it possible to specify an updated source among a plurality of sources.

  Next, the EAR creation server 2 stores the created EAR file in the deployment repository 44.

  When deployment instruction information indicating a deployment instruction is sent from the person-in-charge terminal 1 to the EAR creation server 2 via the network, the deployment tool 24 executed in the EAR creation server 2 reads the EAR file from the deployment repository 44. ((E) of FIG. 2), step S4), this is deployed, output (input) to the real machine 3 through the network, and incorporated (step S5). At this time, the deployment result data is stored in the deployment result DB 52 in the database server 5.

  The deployment result data is associated with the update management data, and the deployment result data includes the date and time when it was input to the actual device 3, and the file name (or module ID) of the created EAR file. ), Change management No. above. (Or change request sheet data) is included.

  As described above, according to the embodiment, the EAR creation server 2 stores the updated source file and the EAR file created based on the updated source file in the repository server 4 and manages the update history. Since the update management data is stored in the database server 5, the update history can be managed without omission while associating the source program file and the executable program file.

  Also, since the EAR file is configured to be created by the EAR creation server 2 that is different from the person-in-charge terminal 1 based on the updated source file, there is no room for intervention by the person in charge of maintenance.

  Furthermore, the stored update management data includes a change management number. Including the change management No. Since it is configured so that an updated (changed) source among a plurality of sources can be identified, for example, even when configured from a plurality of Java programs, only the updated Java program is identified, It is possible to trace back to the Java program itself.

  The embodiment has been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiment, and there are design changes and the like without departing from the scope of the invention. Are also included in the present invention.

It is a figure showing an example of outline composition of a program change management system concerning one embodiment of the present invention. It is a figure which shows an example of the flow of the file in the program change management system S. It is a flowchart which shows the program update process in EAR production server 2. FIG. It is a conceptual diagram which shows an example of a mode that an EAR file is produced from a some source file.

Explanation of symbols

1 Person in charge terminal 2 EAR creation server 3 Real machine 4 Repository server 5 Database server S Program change management system

Claims (5)

Updating a source program file updated by a first computer and an executable program file created by a second computer different from the first computer based on the source program file and executed by a third computer A program update management system for managing history,
The second calculator is
First storage means for storing a source program file updated by the first computer;
Instruction information indicating an instruction to create the executable program file is input, and the updated source program file is read from the first storage unit according to the input instruction information, and the executable program file is generated. An executable program creation means;
Second storage means for storing the updated source program file, the executable program created based on the source program file, and update management data for managing the update history;
A program update management system comprising: In the program update management system according to claim 1,
The first storage means stores a source program file updated by the first computer and a source program file not updated,
The execution format program creating means reads the updated source program file and the non-updated source program file from the first storage means according to the inputted instruction information, and executes the one execution program Create a format program file,
The second storage means includes the updated source program file, the non-updated source program file, the one executable program, and information for specifying the updated source program file. And storing the update management data. In the program update management system according to claim 1 or 2,
The program update management system, wherein the second computer inputs the instruction information from the first computer.   A computer program for causing a computer to function as the second computer according to any one of claims 1 to 3. Updating a source program file updated by a first computer and an executable program file created by a second computer different from the first computer based on the source program file and executed by a third computer A program update management method for managing history,
A first storage step of storing a source program file updated by the first computer;
An input step of inputting instruction information indicating an instruction to create the executable program file;
An executable program creating step of creating the executable program file by reading the updated source program file according to the input instruction information;
A second storage step for storing the updated source program file, the executable program created based on the source program file, and update management data for managing the update history;
A program update management method comprising:

Images