JP5061001B2 - Configuration check system - Google Patents

Description

  The present invention relates to a configuration check system for checking a configuration of a server.

  Currently, many companies, schools, local governments, etc. operate load balancing systems that distribute the load on servers. The servers in the load balancing system have basically the same configuration. Here, the configuration refers to the description contents of various configuration files held by the server. The configuration file includes all setting files necessary for various protocols used by the server, setting files prepared independently by a vendor that is a manufacturer and supplier of the server, and setting files necessary for an application provided by the server. Furthermore, the configuration file has a concept including settings that are not described in the setting file, such as a folder configuration.

  In such a load distribution system, for example, a configuration file may be modified by upgrading an application provided by the system, dealing with a problem, or the like. At this time, if the configuration file is not corrected for some of the servers included in the system, a failure occurs. When a failure occurs due to such a cause, it is very difficult to find out the cause of the failure (there is a difference in the configuration file between servers).

Therefore, a mechanism for detecting that there is a difference in the configuration file between the two servers has been devised (see Patent Document 1).
In the mechanism described in Patent Document 1, when there are two servers with the same configuration, when some failure occurs in one server (a part of the configuration file has been rewritten unintentionally) A difference between the configuration files of these two servers is detected.
JP 2005-266916 A

  However, the mechanism described in Patent Document 1 can only detect that there is a difference in configuration files between two servers. Therefore, for example, (1) all servers are infected with viruses, and all server configuration files are rewritten in the same way. (2) all servers fail to release due to human error. If the server configuration file is an old version, it cannot be detected as abnormal.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to detect an unintended change in a configuration file even in the case where there is no configuration file difference between servers in a load balancing system. It is to provide a configuration check system and the like. A secondary purpose is to provide a configuration check system or the like that can efficiently perform release management.

First invention to achieve the above object, an application server providing an application configured by the file, and release management server that manages the release of the application, the operation monitoring server for monitoring the operation of the entire system there are connected to each other, a configuration check system for checking the configuration of the application server, the release management server maintains a release object list is a list of changes that take place in a release object in a particular release work means, comprising a time the application server is a comparison file and the previous partial holding means for holding a previous comparison file is a comparison file was last checked, and this time the check target from the files that are currently installed Comparison A comparison file generation means for generating a file, a first difference confirmation means for confirming a difference between the current comparison file generated by the comparison file generation means, and the previous comparison file held by the previous time holding means; If there is a difference confirmation result according to one of the difference confirming means, check whether the acquired from the release management server the release target list, the changes place the current group of files that are installed is present in the release target list and release target confirmation means for, when the check result by the release target confirmation means absent, structure, characterized by comprising, a first abnormality notification means for notifying that there is an abnormality in the operation monitoring server Check system.

  The previous time holding means may hold the current comparison file generated by the first difference checking means as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking means. desirable. The application server preferably further includes history storage means for storing the previous comparison file held by the previous holding means as history data. The release management server further includes change history holding means for holding history data of file changes for each release, and the application server holds history data held by the release management server by the change history holding means, It is desirable to further include history comparison means for comparing history data held by the application server with the history storage means. The release management server further includes comparison source file generation means for generating a comparison source file from a file group of a specific version, and the application server acquires the comparison source file from the release management server, and acquires the acquired comparison source. The second abnormality for notifying that there is an abnormality in the operation monitoring server when there is a difference between the second difference confirmation means for confirming the difference between the file and the current comparison file and the confirmation result by the second difference confirmation means. And a notification means.

  Further, the current comparison file generated by the comparison file generation unit and the comparison source file generated by the comparison source file generation unit may be a summary of each target file group. The comparison file generation means may generate the current comparison file by dividing the target file group for each software layer to which each file belongs. In addition, the comparison file generation unit generates a comparison file this time by dividing the target file group for each software layer to which each file belongs, and the comparison source file generation unit generates each comparison file from the target file group. The comparison source file may be generated by dividing each software layer to which the file belongs.

A second invention is an application server providing an application configured by the file, and release management server that manages the release of the application, and the operation monitoring server for monitoring the operation of the entire system are connected to each other, wherein a configuration check system for checking the configuration of the application server, the application server generates a time comparison file is a comparison file for the files that are currently installed and the current check target, said generated time compared files It comprises comparing the file transmission means for transmitting the release management server, wherein the release management server includes means for retaining the release target list is a list of changes that take place in a release object in a particular release operation, the last check And last minute holding means for holding a previous comparison file is a comparison file and elephants, and the current comparison file received from the application server, the first to the last minute holding means to check the difference between the previous comparison file that holds and the difference confirming means, the first case where there is a difference confirmation result by the difference confirming means, said obtained from the release management server the release target list, the changed portion of the current group of files that are installed the release target list comprising: a release object confirmation means for confirming whether there, if confirmation result by the release target confirmation means is absent, a first abnormality notification means for notifying that there is an abnormality in the operation monitoring server, to This is a configuration check system.

  In addition, it is preferable that the previous holding unit holds the current comparison file received from the application server as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking unit. Further, the release management server includes a comparison source file generation unit that generates a comparison source file from a file group of a specific version, a comparison source file generated by the comparison source file generation unit, a current comparison file received from the application server, and A second difference confirmation unit for confirming the difference between the second monitoring unit and a second abnormality notification unit for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the second difference confirmation unit is different. It is desirable to have it.

A third invention is a configuration check system in which an application server that provides an application constituted by files and an operation monitoring server that monitors the operation of the entire system are connected to each other, and the configuration of the application server is checked. The application server holds a release target list holding unit that holds a release target list that is a list of changes that have been released in a specific release operation, and a previous comparison file that is a comparison file to be checked last time. A previous-minute holding means, a comparison file generating means for generating a current comparison file that is a comparison file to be checked this time from a currently installed file group, a current comparison file generated by the comparison file generating means, And the first difference confirmation means whose serial last minute holding means to confirm the difference between the previous comparison file that holds, case where there is a difference confirmation result by the first difference confirmation means, the release from the release object list holding means When the target list is acquired, and the release target confirmation unit for confirming whether the changed part of the currently installed file group exists in the release target list, and the confirmation result by the release target confirmation unit is absent, A configuration check system comprising: first abnormality notification means for notifying that there is an abnormality in the operation monitoring server.

  According to the present invention, it is possible to provide a configuration check system that can detect an unintended change of a configuration file even when there is no configuration file difference between servers in a load distribution system. In addition, it is possible to provide a configuration check system that can efficiently perform release management.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<First Embodiment>
First, the first embodiment will be described with reference to FIGS. 1 to 4. An example according to the first embodiment will be described with reference to FIGS. 5 and 6.

  FIG. 1 is a diagram showing an overview of a configuration check system 1 according to the first embodiment. As shown in FIG. 1, the configuration check system 1 includes an AP (application) server 3-1, an AP server 3-2,..., An AP server 3-3, a release management server 5, and an operation monitoring server 7. It is connected via 9-1. The AP server 3-1, the AP server 3-2,..., The AP server 3-3 constitute a load distribution system, and the terminal 13 is connected via the load distribution device 11 and the external network 9-2. -1, terminal 13-2,..., Responds to a request from terminal 13-3.

  The AP server 3-1, the AP server 3-2,..., The AP server 3-3 are a group of servers having the same function, and the load is distributed by the load distribution node (= load distribution device 11) in the load distribution system. Server). The number of load distribution nodes is, for example, several to several hundreds, and the present invention is applicable from a small load distribution system to a large load distribution system. The AP server 3-1, the AP server 3-2,..., The AP server 3-3 are, for example, a web application system that provides a specific application via the external network 9-2, and a web that provides a specific service. It plays the role of responder such as service system.

  The release management server 5 is an application provided by the AP server 3-1, AP server 3-2,..., AP server 3-3 (including services provided by the web service system. The same shall apply hereinafter). Manage releases. Here, “release” refers to the production environment (provided that the application is actually provided to the user) when it is necessary to make changes to the files (configuration files, etc.) included in the application due to changes in the application specifications or bug fixes. Place the file with the changes in the environment). The release management server 5 also manages file changes.

  The operation monitoring server 7 monitors the operation of the load distribution system. Specifically, the operation status of the AP server 3-1, the AP server 3-2,..., The AP server 3-3, the release management server 5, the load balancer 11 and the like is monitored centrally, and an abnormality occurs. Notify interested parties when Usually, software called an agent is installed on a server to be monitored. Then, the operation monitoring server 7 collects data on the process status of each server, the usage status of the memory, the hard disk, and the operating status of the application to be provided by the function of the agent.

The internal network 9-1 is a network that is protected from intrusion from the outside by a so-called firewall (not shown). The internal network 9-1 is, for example, a LAN (Local) laid at the location where the configuration check system 1 is arranged.
Area Network).

  The load balancer 11 sends requests from the terminal 13-1, the terminal 13-2,..., The terminal 13-3 to the AP server 3-1, the AP server 3-2,. Send to. Further, the load balancer 11 sends responses from the AP server 3-1, AP server 3-2,..., AP server 3-3 to the terminal 13-1, terminal 13-2,. -3. The load balancer 11 distributes the request to each server and maintains a constant response speed. Further, the load distribution apparatus 11 maintains the operation of the application to be provided even when an abnormality has occurred in some servers.

  Terminal 13-1, terminal 13-2,..., And terminal 13-3 are used by application users. The terminal 13-1, the terminal 13-2,..., And the terminal 13-3 follow the user's instruction, and load balancer 11 (finally, AP server 3-1, AP server 3-2,. , A request is transmitted to the AP server 3-3).

  The external network 9-2 is a network outside a so-called firewall, for example, the Internet.

  FIG. 2 is a hardware configuration diagram of a computer that realizes the AP server 3-1, the AP server 3-2,..., The AP server 3-3, the release management server 5, the operation monitoring server 7, and the like. Note that the hardware configuration in FIG. 2 is an example, and various configurations can be adopted depending on the application and purpose.

  In the computer, a control unit 21, a storage unit 23, a media input / output unit 25, a communication control unit 27, an input unit 29, a display unit 31, a peripheral device I / F unit 33 and the like are connected via a bus 35.

  The control unit 21 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like.

The CPU calls a program stored in the storage unit 23, ROM, recording medium, or the like to a work memory area on the RAM, executes it, drives and controls each device connected via the bus 35, and AP server 3-1. , AP server 3-2,..., AP server 3-3, release management server 5, operation monitoring server 7, and the like.
The ROM is a non-volatile memory and permanently holds a computer boot program, a program such as BIOS, data, and the like.
The RAM is a volatile memory, and temporarily stores programs, data, and the like loaded from the storage unit 23, ROM, recording medium, and the like, and includes a work area used by the control unit 21 for performing various processes.

The storage unit 23 is an HDD (hard disk drive), and stores a program executed by the control unit 21, data necessary for program execution, and the like. With respect to the program, a control program corresponding to an OS (operating system) and an application program for causing a computer to execute processing described later are stored.
Each of these program codes is read by the control unit 21 as necessary, transferred to the RAM, read by the CPU, and executed as various means.

  The media input / output unit 25 (drive device) inputs / outputs data, for example, a CD drive (-ROM, -R, -RW, etc.), DVD drive (-ROM, -R, -RW, etc.), MO drive, etc. And other media input / output devices.

  The communication control unit 27 includes a communication control device, a communication port, and the like, and is a communication interface that mediates communication between the computer and the network 9 (internal network 9-1, external network 9-2). Control communication with other computers.

The input unit 29 inputs data and includes, for example, a keyboard, a pointing device such as a mouse, and an input device such as a numeric keypad.
An operation instruction, an operation instruction, data input, and the like can be performed on the computer via the input unit 29.

  The display unit 31 includes a display device such as a CRT monitor and a liquid crystal panel, and a logic circuit (such as a video adapter) for realizing a video function of the computer in cooperation with the display device.

  The peripheral device I / F (interface) unit 15 is a port for connecting a peripheral device to the computer, and the computer transmits and receives data to and from the peripheral device via the peripheral device I / F unit 33. The peripheral device I / F unit 33 is configured by USB, IEEE 1394, RS-232C, or the like, and usually has a plurality of peripheral devices I / F. The connection form with the peripheral device may be wired or wireless.

  The bus 35 is a path that mediates transmission / reception of control signals, data signals, and the like between the devices.

Next, the scheduled difference confirmation process and the release difference confirmation process according to the present invention will be described with reference to FIGS.
FIG. 3 is an activity diagram of the AP server 3-1 in the scheduled difference confirmation process. The AP server 3-2,..., The AP server 3-3 also performs the process shown in FIG.

  The processing shown in FIG. 3 is periodically performed in operation. The process shown in FIG. 3 may be performed by, for example, a daily batch. Further, the operation monitoring server 7 may transmit an execution start command to the AP server 3-1. Further, the administrator may input an execution start command via the input unit 29 of any of the devices (AP server 3-1, release management server 5, monitoring server 7, etc.).

  When the AP server 3-1 starts the time difference confirmation process (51), the AP server 3-1 acquires the release target list from the release management server 5 (52). The release target list is a list of changes that have been released in a specific release operation. The release target list may be, for example, a list in units of files that are targeted for release in a specific release operation. Further, the release target list may be, for example, a list of locations (for example, data item units) where changes have been made in a specific release operation.

  Next, the AP server 3-1 confirms the difference between the file it has and the previous check (53). Specifically, the AP server 3-1 holds the previous comparison file, which is a comparison file to be checked last time, in the storage unit 23 (previous-number holding unit). Then, the AP server 3-1 generates a current comparison file, which is a comparison file to be checked this time, from the currently installed file group (comparison file generation means). Next, the difference between the current comparison file generated by the comparison file generation unit and the previous comparison file held by the previous holding unit is checked (first difference checking unit).

When the confirmation result by the first difference confirmation unit is “no difference” (54 [no difference]), the AP server 3-1 ends the scheduled difference confirmation process (59).
On the other hand, when the confirmation result by the first difference confirmation unit is “difference” (AP [difference] in 54), the AP server 3-1 has a change point of the currently installed file group in the release target list. (Release target confirmation means) (55).

The AP server 3-1 stores the current comparison file (current comparison file) in the storage unit 23 (holds the previous time) when the confirmation result by the release target confirmation unit is “exist” (56 [exists]). (Means) (58), the scheduled difference confirmation process is terminated (59).
On the other hand, when the confirmation result by the release target confirmation unit is “does not exist” (56 [does not exist]), the AP server 3-1 notifies the operation monitoring server 7 that there is an abnormality (first abnormality notification) Means) (57). Then, the AP server 3-1 saves the current comparison file (current comparison file) in the storage unit 23 (previous-part holding means) (58), and ends the scheduled difference confirmation process (59).

  In FIG. 3, the AP server 3-1 acquires the release target list from the release management server 5, but the AP server 3-1 may hold the release target list. For example, at the time of the release work, the AP server 3-1 acquires the difference between the configuration before the release and the configuration after the release, and a location where this difference exists (may be a file unit or a data item unit). May be held as a release target list. In this case, even if the release management server 5 does not exist, the AP server 3-1 can execute the scheduled difference confirmation process shown in FIG.

  In FIG. 3, the confirmation by the release target confirmation unit is performed, but this confirmation may not be performed. That is, when the confirmation result by the first difference confirmation unit is “difference”, the AP server 3-1 notifies the operation monitoring server 7 that there is an abnormality without performing the confirmation by the release target confirmation unit. May be.

  As described above, the previous time holding means holds the current comparison file generated by the first difference checking means as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking means. .

  Further, the AP server 3-1 may store the previous comparison file held by the previous holding unit as history data (history storage unit). Furthermore, the AP server 3-1 compares the history data of file changes for each release held by the release management server 5 (usually having version information) and the history data accumulated by the history accumulation means. A function (history comparison means) may be provided.

  For example, regarding the change of the data item of a certain file, the release management server 5 records history data of 100 (Ver1.0)-> 101 (Ver1.1)-> 102 (Ver1.2)-> 103 (Ver1.3). Is held. On the other hand, in the AP server 3-1, 100 (Ver1.0 release date) → 111 (Ver1.1 release date) → 112 (Ver1.2 release date) → 113 (Ver1.3 release date) ) Is stored.

  In the above-described situation, the follow-up survey by the history comparison unit included in the AP server 3-1 will be described. The AP server 3-1 compares the value “100” of Ver 1.0 held by the release management server 5 with the value “100” of the release date of Ver 1.0 held by the AP server 3-1. Make sure they match. Next, the AP server 3-1 compares the value “101” of Ver 1.1 held by the release management server 5 with the value “111” of the release date of Ver 1.1 held by the AP server 3-1. Confirm that they do not match. Then, the AP server 3-1 outputs that the files do not match on the release date of Ver1.1. In this case, it can be seen that an illegal file was installed when Ver 1.1 was released. In other words, the history comparison means can trace back to the past when the file included in the application has been illegally changed.

  In this way, by performing the scheduled difference confirmation process shown in FIG. 3, for example, (1) a case where all servers are infected with a virus, and the configuration files of all servers are rewritten in the same way, (2) artificial Even if the release fails for all servers due to a mistake, the configuration files of all servers are out of date, etc., it is possible to detect an abnormality and conduct a detailed follow-up survey. it can.

  FIG. 4 is an activity diagram of the AP server 3-1 in the release time difference confirmation process. The AP server 3-2,..., The AP server 3-3 also performs the process shown in FIG.

  The processing shown in FIG. 4 is performed at the time of release in operation. In the execution of the process shown in FIG. 4, for example, the administrator inputs an execution start command via the input unit 29 of any of the devices (AP server 3-1, release management server 5, monitoring server 7, etc.). May be. As a pre-process of the process shown in FIG. 4, the release management server 5 generates a comparison source file from a file group of a specific version (version that the administrator wants to compare) (comparison source file generation means). The execution of the comparison source file generation means is performed, for example, by an administrator inputting an execution start command via the input unit 29 of any of the devices (AP server 3-1, release management server 5, monitoring server 7, etc.). May be.

  When the AP server 3-1 starts the release time difference confirmation process (71), the AP server 3-1 acquires the comparison source file from the release management server 5 (72). Next, the AP server 3-1 generates a comparison file to be checked from the currently installed file group (73), compares the comparison file with the comparison source file, and confirms the difference (second). Difference confirmation means) (74).

If the confirmation result by the second difference confirmation unit is “no difference” (75 [no difference]), the AP server 3-1 ends the release difference confirmation process (77).
On the other hand, when the confirmation result by the second difference confirmation unit is “difference” (75 [difference]), the AP server 3-1 notifies the operation monitoring server 7 of the abnormality (second abnormality notification unit). ) (76), the release time difference confirmation process is terminated (77).

  In this way, by performing the release time difference confirmation process shown in FIG. 4, it is possible to confirm whether the configuration of the production environment matches the configuration of the file group of a specific version.

Next, examples according to the first embodiment will be described with reference to FIGS. 5 and 6.
FIG. 5 is a diagram illustrating an overall configuration of an example according to the first embodiment. In this embodiment, the configuration check system 1 is incorporated into a load distribution system.

  As shown in FIG. 5, in this embodiment, the configuration check system 1 includes an AP server 3, a release management server 5, an operation monitoring server 7, and the like. Further, the operator 15 monitors an application provided by the AP server 3. However, the operator 15 does not need knowledge regarding the application provided by the AP server 3. Further, the operator 15 is means for contacting the person in charge 17-1 and the person Y in 17-2 when a failure occurs (telephone, FAX, e-mail, etc .; Means are not particularly limited.) The person in charge X and the person in charge Y have knowledge about the application provided by the AP server 3.

  First, the flow of the scheduled difference confirmation process indicated by step 101, step 102, and step 301 will be described.

<Step 101>
When an instruction to start execution of the scheduled difference confirmation process is given by the daily batch scheduling function of the AP server 3, the AP server 3 generates the current comparison file from the comparison target file 91, and the generated current comparison file, The difference from the previous comparison file 92 stored in the storage directory 19 on the storage unit 23 is confirmed.

  Here, the generation standard of the comparison file will be described. This comparison file is, for example, a digest comparison file that summarizes the comparison target file 91. The digest comparison file is, for example, a hash value calculated for each comparison target file 91 using a hash function, and the calculated hash values are collected for each software layer, for example.

<Step 102>
If the confirmation result in step 101 is “difference”, the AP server 3 generates, for example, the type of the current comparison file that has been generated (for example, indicating which software layer has been generated based on the comparison target file 91) A message in which an identifier for identifying is embedded is transmitted to the operation monitoring server 7. On the other hand, the operation monitoring server 7 has person-in-charge information 95. The person-in-charge information 95 includes the name of the person in charge, the contact information of the person in charge, etc., using the identifier as a key.

<Step 301>
The operation monitoring server 7 displays the message content and the person-in-charge information 95 on the display unit 31 in order to notify the operator 15 of the failure according to the message received from the AP server 3. In addition, the operation monitoring server 7 may transmit a control signal indicating a lighting instruction to a patrol lamp (not shown) as a warning lamp. On the other hand, the operator 15 confirms the content of the message displayed on the display unit 31 and the person-in-charge information 95, and specifies the person in charge. Then, the operator 15 notifies the specified person in charge that a failure has occurred. Thereby, even if the operator 15 does not have knowledge about the application provided by the AP server 3, it is possible to quickly deal with the failure. The operation monitoring server 7 may transmit an e-mail addressed to the e-mail address related to the identified person in charge.

  Next, the flow of the scheduled difference confirmation process indicated by step 201, step 202, step 203, step 204, and step 301 will be described. In the following description, it is assumed that the Ver2.0 file group held by the release management server 5 is installed in the AP server 3.

<Step 201>
The release management server 5 generates a digest file 94b that is a comparison source file from a Ver2.0 file group 93-3 that is a file group of a specific version. The digest file 94b is a summary of the Ver2.0 file group 93-3. Here, the file group 93-3 may include different data items for each server, for example, computer names (names that can be identified on the internal network 9-2), IP addresses, and the like. In this case, the release management server 5 generates a work file from which these data items are deleted, and calculates a hash value for the generated work file. Then, the release management server 5 collects the calculated hash values for each software layer and forms a digest file 94b.

<Step 202>
The AP server 3 generates a digest file 94a to be checked from the comparison target file 91. The generation standard of the digest file 94a is the same as the generation standard of the digest file 94b in step 201. That is, for data items that are different for each server, a work file from which these data items are deleted is generated, and a hash value is calculated for the generated work file. Then, the AP server 3 collects the calculated hash values for each software layer and forms a digest file 94a.

<Step 203>
The AP server 3 checks the difference between the digest file 94a and the digest file 94b. Since the digest file 94a and the digest file 94b are collected for each software layer, the AP server 3 can determine which software layer has a difference when there is a difference.

<Step 204>
If the confirmation result in step 203 is “difference”, the AP server 3 generates, for example, the type of the current comparison file that has been generated (for example, indicates which software layer has been generated based on the comparison target file 91) A message in which an identifier for identifying is embedded is transmitted to the operation monitoring server 7. On the other hand, the operation monitoring server 7 has person-in-charge information 95. The person-in-charge information 95 includes the name of the person in charge, the contact information of the person in charge, etc., using the identifier as a key. The identifier embedding process will be described later with reference to FIG.

<Step 301>
The operation monitoring server 7 displays the message content and the person-in-charge information 95 on the display unit 31 in order to notify the operator 15 of the failure according to the message received from the AP server 3. In addition, the operation monitoring server 7 may transmit a control signal indicating a lighting instruction to a patrol lamp (not shown) as a warning lamp.

  FIG. 6 is a diagram illustrating an example of failure notification to a person in charge. In the example shown in FIG. 6, the software layers of the AP server 3 to be checked by the configuration check system 1 are the OS, middleware, and application. The comparison target file, which is a configuration file, is divided into a common file and an individual file for each software layer. The common file is a file describing a configuration common to all AP servers 3. The individual file is a file describing a configuration unique to each AP server.

In the configuration check process illustrated in FIG. 6, the AP server 3 classifies the comparison target file for each software layer, a common file or an individual file, and compares a specific version of the file group held by the release management server 5 with the comparison target file. And
Specifically, the AP server 3 compares the common file 91-1a of its own application with the common file 91-1b of the application of the release management server 5. Further, the AP server 3 compares the individual file 91-2a of its own application with the individual file 91-2b of the application of the release management server 5.
Further, the AP server 3 compares the middleware common file 91-3a of its own with the middleware common file 91-3b of the release management server 5. Also, the release management server 5 compares the middleware individual file 91-4a with the middleware individual file 91-4b of the release management server 5.
In addition, the AP server 3 compares the OS common file 91-5a with the OS common file 91-5b of the release management server 5. Further, the AP server 3 compares the individual file 91-6a of its own OS with the individual file 91-6b of the OS of the release management server 5.

  When comparing the common files, the AP server 3 determines that there is an abnormality if, for example, there is a portion that does not match, that is, if there is a difference between the two files. On the other hand, when comparing the individual files, the AP server 3 determines that there is an abnormality, for example, when there is no mismatched portion, that is, when there is no difference between the two files. Thereby, for example, it is possible to detect omissions in settings such as different IP addresses and server names for each server (for example, when the installation is performed without changing the contents of the file based on the server).

When there is an abnormality in the comparison result regarding the application, the AP server 3 sends a message in which an identifier indicating the application is embedded as the type of the generated comparison file to the operation monitoring server 7 in order to notify the person in charge X of the failure. To do.
On the other hand, the AP server 3 embeds an identifier indicating the middleware and / or the OS as the type of the generated comparison file in order to notify the person in charge Y of the failure when the comparison result regarding the middleware and / or the OS is abnormal. A message is transmitted to the operation monitoring server 7.

<Second Embodiment>
Next, a second embodiment will be described with reference to FIGS. Below, the same number is attached | subjected about the component similar to the component which concerns on 1st Embodiment, and suppose that the duplicate description is avoided.

  FIG. 7 is a diagram showing an outline of the configuration check system 1c according to the second embodiment. As shown in FIG. 7, the configuration check system 1c includes an AP server 3-1c, an AP server 3-2c,..., An AP server 3-3c, a release management server 5c, and an operation monitoring server 7 that are connected to the internal network 9-1. Connected through.

  In the configuration check system 1 according to the first embodiment, the configuration check program 2 is installed in the AP server 3-1, AP server 3-2,..., AP server 3-3. In the configuration check system 1c according to the embodiment, the configuration check program 2c is installed in the release management server 5c. Accordingly, the release management server 5c performs the scheduled difference confirmation process shown in FIG. 3 and the release difference confirmation process shown in FIG.

Next, the scheduled difference confirmation process and the release difference confirmation process according to the present invention will be described with reference to FIGS.
FIG. 8 is an activity diagram of the release management server 5c in the scheduled difference confirmation process.
In the following, the regular difference confirmation process for the AP server 3-1c will be described, but the same process is performed for the AP server 3-2c and the AP server 3-3c. As a premise of the processing shown in FIG. 8, the AP server 3-1c generates a current comparison file to be checked this time, and transmits the generated current comparison file to the release management server 5c (comparison file transmission means). . Therefore, for example, the process shown in FIG. 8 may be executed when the release management server 5c receives the current comparison file. Alternatively, the administrator may input an execution start command via the input unit 29 of the release management server 5c.

  When the release management server 5c starts the time difference confirmation process (61), the release management server 5c acquires the current comparison file, which is the current comparison file (62).

  Next, the release management server 5c confirms the difference from the previous check (63). Specifically, the release management server 5c holds the previous comparison file, which is the comparison file to be checked last time, in the storage unit 23 (previous amount holding means). Then, the difference between the current comparison file and the previous comparison file held by the previous holding unit is checked (first difference checking unit).

If the confirmation result by the first difference confirmation unit is “no difference” (64 [no difference]), the release management server 5c ends the scheduled difference confirmation process (69).
On the other hand, when the confirmation result by the first difference confirmation unit is “difference” (64 [difference]), the release management server 5c has a change point of the currently installed file group in the release target list. (Release target confirmation means) (65). The release target list is held in the storage unit 23 of the release management server 5c.

The release management server 5c saves the current comparison file (current comparison file) in the storage unit 23 when the confirmation result by the release target confirmation unit “exists” (66 [exists]) (previous amount holding unit). ) (68), the fixed time difference confirmation processing is terminated (69).
On the other hand, the release management server 5c notifies that there is an abnormality in the operation monitoring server 7 when the confirmation result by the release target confirmation unit is “does not exist” (66 [does not exist]) (first abnormality notification unit) ) (67). Then, the release management server 5c saves the current comparison file (current comparison file) in the storage unit 23 (previous holding unit) (68), and ends the scheduled difference confirmation process (69).

  As described above, the previous time holding means holds the current comparison file generated by the first difference checking means as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking means. . Furthermore, the release management server 5c may store the previous comparison file held by the previous holding unit as history data (history storage unit). Accordingly, even when a failure occurs, it is possible to trace back when the file included in the application has been changed.

  In this way, by performing the scheduled difference confirmation process shown in FIG. 8, for example, (1) a case where all servers are infected with a virus and the configuration files of all servers are rewritten in the same way, (2) artificial Even if the release of all servers fails due to a mistake, and the configuration file of all servers is an old version, an abnormality can be detected.

FIG. 9 is an activity diagram of the release management server 5c in the release time difference confirmation process.
In the following, the regular difference confirmation process for the AP server 3-1c will be described, but the same process is performed for the AP server 3-2c and the AP server 3-3c. As pre-processing of the processing shown in FIG. 9, the AP server 3-1c generates a comparison file from the currently installed file group, and transmits the generated comparison file to the release management server 5c (comparison file generation means) ). Therefore, the process shown in FIG. 9 may be executed when the release management server 5c receives the comparison file, for example. Alternatively, the administrator may input an execution start command via the input unit 29 of the release management server 5c.

  When the release management server 5c starts the release time difference confirmation process (81), the release management server 5c generates a comparison source file from a file group of a specific version (version that the administrator wants to compare) (82). Next, the release management server 5c acquires a comparison file (83). Next, the release management server 5c compares the comparison file with the comparison source file and confirms the difference (second difference confirmation unit) (84).

If the confirmation result by the second difference confirmation unit is “no difference” (75 [no difference]), the release management server 5c ends the release difference confirmation process (87).
On the other hand, when the result of confirmation by the second difference confirmation unit is “difference” (85 [difference]), the release management server 5c notifies the operation monitoring server 7 of the abnormality (second abnormality notification unit). (86), the release time difference confirmation process is terminated (87).

  In this way, by performing the release time difference confirmation process shown in FIG. 9, it is possible to confirm whether the configuration of the production environment matches the configuration of the file group of a specific version.

  In the second embodiment, the release management server 5c performs the scheduled difference confirmation process shown in FIG. 8 and the release difference confirmation process shown in FIG. 9, thereby checking the configuration of the AP server 3-1c and the like. As in the second embodiment, the release management server 5c performs the configuration check process, so that no excessive load is applied to the AP server 3-1c and the like. Accordingly, even when a configuration check is performed during operation, such as a 24-hour operation system, the configuration of the AP server 3-1c and the like can be checked without greatly affecting the entire system.

  Although various embodiments have been described above, operation examples applicable to all the embodiments will be described. For example, according to the present invention, it is possible to execute a scheduled difference confirmation process in order to detect a case where all servers are infected with a virus and the configuration files of all servers are rewritten in the same way. In addition, for example, according to the present invention, release difference confirmation processing is performed to detect a case in which release fails for all servers due to human error and configuration files of all servers are out of date. Can be executed. For example, when the release management server according to the present invention is used, even if there is a problem with the latest version, the release management server holds the old version, so that the old version can be quickly installed. Further, for example, according to the present invention, even when a failure occurs, it is possible to trace back when the file included in the application has been changed.

  In addition, release management can be performed efficiently by using the history storage means (means for storing the previous comparison file held by the previous holding means as history data) provided in the AP server. For example, consider a case where a service for renting a server is provided. In this case, the rental target server confirms whether or not the file has been updated by the user (the person who rented the rental server) by performing the scheduled difference confirmation process according to the present invention, and accumulates the updated contents as history data. Can be kept. Furthermore, in the case of a system that charges for each file update, the rental target server can perform a charging process for the user using the history data.

  The preferred embodiments of the configuration check system and the like according to the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to such examples. It will be apparent to those skilled in the art that various changes or modifications can be conceived within the scope of the technical idea disclosed in the present application, and these naturally belong to the technical scope of the present invention. Understood.

The figure which shows the outline | summary of the structure check system 1 which concerns on 1st Embodiment. Computer hardware configuration diagram Activity diagram of the AP server 3-1 in the scheduled difference confirmation process Activity diagram of AP server 3-1 in the release time difference confirmation process The figure which shows the whole structure of the Example which concerns on 1st Embodiment. Diagram showing an example of failure notification to the person in charge The figure which shows the outline | summary of the structure check system 1c which concerns on 2nd Embodiment. Activity diagram of the release management server 5c in the scheduled difference confirmation process Activity diagram of release management server 5c in the release time difference confirmation process

Explanation of symbols

1, 1c... Configuration check system 3, 3-1, 3-2, 3-3, 3-1c, 3-2c, 3-3c ... AP server 5, 5c ... Release management server 7 ... Operation monitoring server 9 ......... Network 9-1 ......... Internal network 9-2 ......... External network 11 ......... Load balancer 13-1, 13-2, 13-3 ......... Terminal 15 ... ...... Operator 17-1 ... Person in charge X
17-2 ... Person in charge Y
19 ......... Storage Directory 21 ......... Control Unit 23 ......... Storage Unit 25 ......... Media Input / Output Unit 27 ......... Communication Control Unit 29 ......... Input Unit 31 ......... Display Unit 33 ......... Peripherals Device I / F section 35... Bus 91... Comparison target file 92... Previous comparison file 93-1, 93-2, 93-3 ... File group 94 a, 94 b ... Digest file 95. ...... Responsible person information

Claims (13)

An application server that provides an application configured by a file, a release management server that manages the release of the application, and an operation monitoring server that monitors the operation of the entire system are connected to each other, and the configuration of the application server is checked. A configuration check system that
The release management server
Means to maintain a release target list, which is a list of changes that have been released in a specific release operation;
Comprising
The application server is
Last time holding means for holding the previous comparison file which is the comparison file to be checked last time,
A comparison file generating means for generating a current comparison file, which is a comparison file to be checked this time, from a currently installed file group;
First difference confirmation means for confirming a difference between the current comparison file generated by the comparison file generation means and the previous comparison file held by the previous time holding means;
If there is a difference in the confirmation result by the first difference confirmation unit, the release target list is acquired from the release management server, and whether or not the changed part of the currently installed file group exists in the release target list Release target confirmation means to confirm
A first abnormality notification means for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the release target confirmation means is absent;
A configuration check system comprising:   The previous time holding means holds the current comparison file generated by the first difference checking means as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking means. The configuration check system according to claim 1, wherein: The application server is
History storage means for storing the previous comparison file held by the previous holding means as history data;
The configuration check system according to claim 2, further comprising: The release management server
Change history holding means to hold file change history data for each release,
Further comprising
The application server is
History comparison means for comparing the history data held by the release management server by the change history holding means and the history data held by the application server by the history storage means;
The configuration check system according to claim 3, further comprising: The release management server
Comparison source file generation means for generating a comparison source file from a specific version of the file group,
Further comprising
The application server is
A second difference confirmation means for obtaining a comparison source file from the release management server and confirming a difference between the obtained comparison source file and the current comparison file;
A second abnormality notification means for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the second difference confirmation means is different;
The configuration check system according to claim 1, further comprising:   The configuration check system according to claim 1, wherein the current comparison file generated by the comparison file generation unit summarizes a target file group.   6. The current comparison file generated by the comparison file generation unit and the comparison source file generated by the comparison source file generation unit summarize the target file groups, respectively. The configuration check system described.   2. The configuration check system according to claim 1, wherein the comparison file generation unit generates a comparison file this time by dividing the target file group for each software layer to which each file belongs.   The comparison file generation means divides the target file group for each software layer to which each file belongs to generate a comparison file this time, and the comparison source file generation means determines that each file from the target file group 6. The configuration check system according to claim 5, wherein the comparison source file is generated for each software layer to which the software belongs. An application server that provides an application configured by a file, a release management server that manages the release of the application, and an operation monitoring server that monitors the operation of the entire system are connected to each other, and the configuration of the application server is checked. A configuration check system that
The application server is
A comparison file transmitting means for generating a current comparison file, which is a comparison file to be checked this time, from a currently installed file group, and transmitting the generated current comparison file to the release management server;
Comprising
The release management server
A means of maintaining a release target list, which is a list of changes that have been released in a specific release task;
Last time holding means for holding the previous comparison file which is the comparison file to be checked last time,
First difference confirmation means for confirming a difference between the current comparison file received from the application server and the previous comparison file held by the previous time holding means;
If there is a difference in the confirmation result by the first difference confirmation unit, the release target list is acquired from the release management server, and whether or not the changed part of the currently installed file group exists in the release target list Release target confirmation means to confirm
A first abnormality notification means for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the release target confirmation means is absent;
A configuration check system comprising:   The previous time holding means holds the current comparison file received from the application server as the previous comparison file regardless of the confirmation result after checking the difference by the first difference checking means. Item 13. The configuration check system according to Item 10. The release management server
Comparison source file generation means for generating a comparison source file from a specific version of the file group,
Second difference confirmation means for confirming a difference between the comparison source file generated by the comparison source file generation means and the current comparison file received from the application server;
A second abnormality notification means for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the second difference confirmation means is different;
The configuration check system according to claim 10, further comprising: An application server that provides an application configured by a file and an operation monitoring server that monitors the operation of the entire system are connected to each other, and is a configuration check system that checks the configuration of the application server,
The application server is
A release target list holding means for holding a release target list, which is a list of changes to be released in a specific release operation;
Last time holding means for holding the previous comparison file which is the comparison file to be checked last time,
A comparison file generating means for generating a current comparison file, which is a comparison file to be checked this time, from a currently installed file group;
First difference confirmation means for confirming a difference between the current comparison file generated by the comparison file generation means and the previous comparison file held by the previous time holding means;
When the confirmation result by the first difference confirmation unit is different, the release target list is acquired from the release target list holding unit, and the changed part of the currently installed file group exists in the release target list. Release target confirmation means to confirm whether or not,
A first abnormality notification means for notifying that there is an abnormality in the operation monitoring server when the confirmation result by the release target confirmation means is absent;
A configuration check system comprising:

Images