JP6290810B2 - Management apparatus and management method - Google Patents

Description

  The present invention relates to a management apparatus and a management method for managing a network system configured by connecting various servers, various terminals, and various devices to each other.

  Conventionally, a large-scale network infrastructure has been constructed. For example, the IDC (Internet Data Center) provides a network device, a server, a storage group for storing various data, and the like, and also provides an access infrastructure network for various communication networks such as Internet connection. In addition, the IDC usually accepts operations and monitoring work at the same time, and supports system operations such as notification and handling when an error occurs. A network infrastructure in a financial institution includes a Web-type financial system (Web-ATM), which is a center-intensive server system.

  Processing determined by banking operations is executed in units of jobs using operation management middleware. Furthermore, a mechanism for starting a job at a predetermined time is called a job scheduler. The business is realized by a business application called from the job scheduler. An interface is provided between the job scheduler and the business application so that the execution result such as normal or abnormal can be understood. For example, when a business application detects an abnormality and returns information to the calling job scheduler, the status of the business (job) becomes clear.

  Since such a system is not composed of a single device, a job error cause is affected by a plurality of servers and components (business application, OS, middleware, etc.). Therefore, the management device that manages the server monitors the error message of each server. The management device determines the execution result of the banking business based on the error message.

  Then, the person in charge of operation or maintenance checks the error message of each server and decides what the error is and what to do next (acquisition of investigation log, retry execution, etc.) It is addressed.

  In addition, as a technology to support error investigation, information that correlates the relationship between the expected operation and the error phenomenon that occurs by that operation is accumulated, and the error message extracted from the log file when the error occurs Based on the above, there is disclosed a technique for searching stored information and outputting the searched series of operations as a procedure for reproducing a phenomenon that caused an error (see, for example, Patent Document 1).

JP 2012-212283 A

  However, a business application as described above usually implements a simple shell script. Such a business application has a problem in that detailed data cannot be transferred due to a limitation of a shell script, and only “normal” or “abnormal” information can be transferred.

  Also, if the cause of an error is not only due to a business application, but there are multiple servers, various devices, middleware, etc., there is a mechanism to consolidate messages to the management server that manages the server. The cause needs to be identified against the application error list. Therefore, there is also a problem that it takes time to identify the work load and cause of the operation manager.

  Also, it is good if the business application itself is operating normally, but if the business application itself is incomplete, for example if it becomes unresponsive, the cause of the error or message cannot be output, and the business application There is also the problem of not knowing what is happening.

  In addition, when an error occurs, necessary investigation information (system log, etc.) may not be acquired immediately. There is information that disappears depending on the time and the amount of data, and there is a problem that error information cannot be collected depending on the error analysis time.

  The Web-type financial system (Web-ATM) is a system that has been operating for many years, and it is impossible to drastically change business applications and the system itself in terms of cost and quality. Therefore, there is a problem that it is necessary to cope with the existing server configuration and business application (logic) without changing them as much as possible.

  The present invention has been made in view of the above situation, and when the business application called from the job scheduler cannot return the detailed information at the time of the error occurrence, the cause is identified from the error message of the related server generated during that time. An object of the present invention is to provide a management device and a management method capable of immediately obtaining necessary survey information.

The present invention employs the following configuration in order to solve the above problems.
That is, according to one aspect of the present invention, the management apparatus of the present invention is a data center having a plurality of servers, and a data center that relays transaction processing executed between a host computer of a financial institution and an automatic transaction apparatus. A job information acquisition unit that acquires job information related to a job executed on the server, and retrieves target job information including a predetermined character string from the job information acquired by the job information acquisition unit Error verification for verifying an error by executing a verification command associated with the target job information on a target job information search unit to be executed and a server that has output the target job information searched by the target job information search unit And an investigation for investigating the error status of the server based on the verification result verified by the error verification unit. Characterized in that it comprises a survey information acquisition unit that executes the information acquisition command.

  In the management apparatus of the present invention, the job information acquisition unit may store the acquired job information in a memory in a table format, and the target job information search unit may search for job information stored in the memory. desirable.

  In the management apparatus of the present invention, it is preferable that the job information acquisition unit acquires job information related to a job that satisfies a predetermined condition based on a job start time, a job end time, and an average execution time of the job.

  According to another aspect of the present invention, the management method of the present invention is a data center having a plurality of servers, which relays transaction processing executed between a host computer of a financial institution and an automatic transaction apparatus. A management method executed by a management device that manages job information, acquiring job information related to a job executed by the server, searching target job information including a predetermined character string from the acquired job information, and executing the search For the server that has output the target job information, the verification command associated with the target job information is executed to verify the error, and the error status of the server is investigated based on the verified verification result For executing a survey information acquisition command.

  According to the present invention, when the business application called from the job scheduler cannot return the detailed information at the time of error occurrence, the cause of the error is identified from the error message of the related server generated in the meantime, and the necessary investigation information is acquired immediately There is an effect that can be done.

It is a figure which shows the application environment of the management system of this Embodiment. It is a figure which shows the functional block of the management apparatus of this Embodiment. It is a flowchart which shows the flow of the management process of this Embodiment. It is a figure which shows the example of a job execution result management table. It is a figure which shows the example of a system common definition table. It is a figure which shows the example of a job operation management table. It is a figure which shows the example of a message management table. It is a figure which shows the example of a confirmation information management table. It is a figure which shows the example of a server related information management table. It is a figure which shows the example of a common server information management table.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing an application environment of the management system according to the present embodiment.

  In FIG. 1, a data center 1 constructed as a large-scale network infrastructure is connected to a bank ATM 3 such as an automatic teller machine (ATM) installed in a convenience store or the like via a network 2 such as a public line. Yes. The data center 1 controls the operation of the bank ATM 3 and is connected via a network 2 to a bank host 4 which is a bank host computer. The data center 1 relays transaction data between the bank ATM 3 and the bank host 4.

  The data center 1 includes a plurality of WWW servers 11 connected to the network 2, a plurality of business servers 12 that perform transaction data exchange, operation control, operation monitoring, etc. with a plurality of bank ATMs 3 via the WWW server 11, business servers A plurality of devices such as a plurality of database servers 13 for storing various data used by 12 and a management device 14 are installed.

  The management device 14 includes a job scheduler, starts a job based on a job execution schedule stored in advance, and calls a business application of the business server 12. The management apparatus 14 acquires the start time and end time of the started job, and message information output from the OS and middleware of each server (WWW server 11, business server 12, and database server 13). The message information includes an error message. In addition, the management device 14 executes “management processing” to be described later.

  The “management process” is repeated at regular intervals (for example, 60 seconds) while the management apparatus is activated.

FIG. 2 is a diagram illustrating functional blocks of the management apparatus according to the present embodiment.
The management device 14 manages the inside of the data center 1 constructed by a plurality of WWW servers 11, a plurality of business servers 12, a plurality of database servers 13, and the like. The management device 14 includes a job information acquisition unit 21, a target job information search unit 22, an error verification unit 23, and an investigation information acquisition unit 24. These are collectively referred to as “management processing”.

  The job information acquisition unit 21 acquires job information related to a job executed by the business server 12 or the like. The job information acquisition unit 21 stores the acquired job information in a memory in a table format. The job information acquisition unit 21 acquires job information related to a job that satisfies a predetermined condition based on a job start time, a job end time, and an average job execution time.

  The target job information search unit 22 searches for target job information including a predetermined character string from the job information acquired by the job information acquisition unit 21. The target job information search unit 22 searches for job information stored in the memory.

  The error verification unit 23 executes a verification command associated with the target job information on the server that has output the target job information searched by the target job information search unit 22, for example, the business server 12, and verifies the error. .

  The investigation information acquisition unit 24 executes an investigation information acquisition command for investigating the error status of the server based on the verification result verified by the error verification unit 23.

  If the management device 14 cannot return detailed information when an abnormality occurs in the business application called from the job scheduler while the business server 12 or the like is operating, an error message or error isolation of a related server that occurred during that time. Execute a verification command. Then, the cause of the error is identified from the execution result, and necessary investigation information is acquired immediately. Thereby, even when the business application called from the job scheduler cannot return an abnormality, the problem can be identified from the related error. Even when there is a defect such as no response in the processing of the business application itself called from the job scheduler, an error can be detected.

Next, the “management process” executed by the management apparatus 14 will be described.
FIG. 3 is a flowchart showing the flow of management processing according to the present embodiment. FIG. 4 is a diagram illustrating an example of a job execution result management table, and each piece of information is stored each time the job scheduler starts / ends a job.

FIG. 5 is a diagram illustrating an example of a system common definition table. FIG. 6 is a diagram illustrating an example of a job operation management table. FIG. 7 is a diagram illustrating an example of a message management table. When an error event or the like occurs from each server, the server notifies the management device and stores the message in a message monitoring process (known technology) in the management device.
FIG. 8 is a diagram illustrating an example of the confirmation information management table. FIG. 9 is a diagram illustrating an example of a server-related information management table. FIG. 10 is a diagram illustrating an example of the common server information management table.

  A specific example of “management processing” executed by the management apparatus 14 will be described with reference to FIGS. 3 to 10. Each of the tables illustrated in FIGS. 4 to 10 starts at 21:00 (21: 00: 00: 00) every day, and “Job A” is normally completed in 30 minutes (1800 seconds) on October 26, 2014 (2014 / 10/26) is used.

  In steps S3001 to S3005, the job execution result management table illustrated in FIG. 4 and the system common definition table illustrated in FIG. 5 are referred to and it is determined whether or not the job execution is abnormal.

  First, in step S3001, it is determined whether or not each job has been executed for the set job. For example, if values (time data) are stored in “job start time” and “job end time” in the job execution result management table of FIG. 4, it is determined that the job execution has been completed. In FIG. 4, “job name” stores the name of the job, “job average time” stores the average time taken to execute the job, and “job start time” includes the most recent job. Is stored, and the “job end time” stores the time when the most recent job execution is completed.

  If it is determined that the job execution has been completed (step S3001: YES), it is determined in step S3002 whether the time taken to execute the completed job is too long compared to the normal execution time. To do. For example, whether or not the value obtained by subtracting “job start time” from “job end time” in FIG. 4 is greater than the value obtained by adding “margin time” in FIG. 5 to “job average time” in FIG. Time-job start time> job average time + margin time) is determined. If it is large, the processing time is longer than usual, which may cause a problem such as system load. In FIG. 5, “job name” stores the name of the job, and “margin time” stores a predetermined value that takes into account variations in the execution time of the job.

  In the present embodiment, the time between the job end time and the job start time does not cross 24: 00: 00: 00.

  If it is determined in step S3002 that it takes too much time (step S3002: YES), the process proceeds to step S3006.

  On the other hand, if it is determined in step S3002 that it does not take too much time (step S3002: NO), whether or not the time taken to execute the completed job in step S3003 is not much longer than the normal execution time. Determine whether. For example, whether or not the value obtained by subtracting “job start time” from “job end time” in FIG. 4 is smaller than the value obtained by subtracting “margin time” in FIG. 5 from “job average time” in FIG. Time-job start time <job average time-margin time) is determined. If it is smaller, the processing time is not longer than usual, so the processing may be interrupted.

  If it is determined in step S3003 that it is not too long (step S3003: YES), the process proceeds to step S3006.

  On the other hand, when it is determined in step S3003 that it does not take too much time (step S3003: NO), it is determined that the execution of the job is normal, and it is determined whether the execution of the next job is abnormal. In step S3016, the process is repeated for the number of all jobs. Note that the processing in step S3016 will be described later.

  If it is determined in step S3001 that the execution of the job has not been completed (step S3001: NO), it is determined in step S3004 whether the job is being executed. For example, when a value (time data) is stored in “job start time” in the job execution result management table of FIG. 4 and a value (time) is not stored in “job end time” (initial state), Determine that the job is running.

  If it is determined that the job is not being executed (step S3004: NO), it is determined that the job has not yet been activated, and the process proceeds to step S3016 and is repeated by the number of all jobs. Note that the processing in step S3016 will be described later.

  On the other hand, if it is determined that the job is being executed (step S3004: YES), in step S3005, it is determined whether or not the time required for executing the job is excessively longer than the normal execution time. To do. For example, whether or not the value obtained by subtracting “job start time” in FIG. 4 from the current time is greater than the value obtained by adding “margin time” in FIG. 5 to “job average time” in FIG. 4 (current time−job start Time> job average time + margin time) is determined. If it is large, the processing time is longer than usual, so there is a possibility of troubles such as a system load or a state where the response cannot be made.

  In the present embodiment, the period between the current time and the job start time does not cross 24: 00: 00: 00.

  If it is determined in step S3005 that it takes too much time (step S3005: YES), the process proceeds to step S3006.

  On the other hand, if it is determined in step S3005 that it does not take too much time (step S3005: NO), it is determined that the job is currently being executed normally, and the process proceeds to step S3016 and is repeated by the number of all jobs. Note that the processing in step S3016 will be described later.

  Next, when it is determined in steps S3002, S3003, and S3005 that the job execution is abnormal, in step S3006, the job operation management table illustrated in FIG. . For example, the job seems to be completed but takes too much time (step S3002: YES), the job seems to be completed but takes too much time (step S3003: YES), or If the job is being executed but takes too much time (step S3005: YES), the name of the server that started the job is acquired from the “job start server name” corresponding to the “job name” in FIG. The name of the server related to the job is acquired from the “job related server name” corresponding to the “job name” in FIG. In FIG. 6, “job name” stores the name of the job, “job start time” stores the scheduled time for starting the job, and “job start server name” stores the job scheduler. The name of the server that executes the business application that is started is stored, and the name of the server that is used by the job such as referring to data is stored in the “job-related server name”.

  In step S3007, the message management table illustrated in FIG. 7 is referred to, and the character string of the message output from the business server 12 or the like is searched based on the server name of the business server 12 or the like acquired in step S3006. In FIG. 7, the name of the business server 12 or the like is stored in “server name”, and the output time of the message information output from the business server 12 or the like in unit time, for example, one day, in “message information time”. “Message information” stores message information output from the business server 12 or the like within a unit time.

  In step S3008, it is determined whether all “verification commands” executed in the next step S3009 have been executed.

  If there is a “verification command” that has not been executed (step S3008: NO), in step S3009, referring to the confirmation information management table illustrated in FIG. 8, the “server name” such as the business server 12 acquired in step S3006 and Based on the character string in the “message information” acquired in step S3007, the “verification command” for the corresponding server name is executed, and the result is stored in the “confirmation result”. The execution of the “verification command” and the storage in the “confirmation result” are repeated until the execution. In FIG. 8, “server name” stores the name of the business server 12 and the like, and “search string” is a trigger for determining whether to perform verification according to the output message information. The keyword character string to be stored is stored, the command name to be verified is stored in “verification command”, the result of verification is stored in “confirmation result”, for example “1” if abnormal, If it is normal, “0” is stored, “Survey information acquisition command” stores the command or program information for acquiring the survey information, and “Survey information” is acquired by executing the “Survey information acquisition command”. Survey information is stored.

  The stored survey information is separately accumulated until it is manually cleared when a detailed survey is performed.

  On the other hand, if it is determined in step S3008 that all “verification commands” have been executed (step S3008: YES), in step S3010, the confirmation information management table illustrated in FIG. It is determined whether more than half of the “confirmation results” are “1” abnormalities.

  If it is determined that more than half of the “confirmation results” are not “1” (step S3010: NO), the process proceeds to step S3012. On the other hand, if it is determined that the value is “1” (step S3010: YES), the related server is verified in step S3011. For example, with reference to the server related information management table illustrated in FIG. 9, “related server name” is acquired for the business server 12 or the like whose “confirmation result” is “1” or more. Then, with reference to the confirmation information management table illustrated in FIG. 8, the “verification command” is executed for the server of the “related server name”, and the result is stored in the “confirmation result”. In FIG. 9, the name of the business server 12 or the like is stored in the “server name”, the name of the business server 12 or the like as a related server is stored in the “related server name”, and the “common server name” is displayed in the “common server name”. Stores the names of commonly used database servers 13 and the like.

  Next, in step S3012, it is determined whether the problem is a common server problem. For example, if more than half of the “confirmation results” of the servers that detected the abnormality are “1” abnormalities and more than half of the “execution results” of the related servers are “1” abnormalities, Judge that there is.

  If it is determined that the problem is a common server problem (step S3012: YES), in step S3013, the common server information management table illustrated in FIG. Execute "Information acquisition command" and store "Investigation information". In FIG. 10, the name of the database server 13 or the like is stored in “server name”, the command name for acquiring survey information is stored in “survey information acquisition command”, and “survey information” includes “ The survey information acquisition command "is executed, and the acquired survey information is stored.

  The stored survey information is separately accumulated until it is manually cleared when a detailed survey is performed.

  On the other hand, if it is determined in step S3012 that the problem is not a common server problem (step S3012: NO), the “confirmation result” is a problem specific to the server in which “1” is abnormal. With reference to the exemplified confirmation information management table, a “survey information acquisition command” is executed for the corresponding server, and the survey information is stored. For example, if less than half of the “confirmation results” of the server that detected the abnormality is “1”, or more than half of the “confirmation results” of the server that detected the abnormality is “1” and related If less than half of the “execution results” of the server is “1”, it is determined that the problem is not the problem of the common server but the problem specific to the server whose “confirmation result” is “1”.

  In step S3015, only the “confirmation result” in the job execution result management table illustrated in FIG. 4 and the confirmation information management table illustrated in FIG. 8 is initialized, and the process proceeds to step S3016. In step 3016, it is determined whether all the jobs of “job name” illustrated in FIG. 4 have been processed. If it is determined that all jobs are not processed (step S3016: NO), the process returns to step S3001, and the above processes are repeated by the number of jobs.

  On the other hand, if it is determined that all jobs have been processed (step S3016: YES), the “management process” is terminated.

  The embodiments of the present invention have been described above with reference to the drawings. However, the management apparatus to which the present invention is applied is not limited to the above-described embodiments.

  Although the present embodiment has been described, according to the present embodiment, even if a business application called from the job scheduler cannot return an error (abnormality), the essential error cause can be determined from the related error message. Can be identified. This reduces the work burden on the operations manager and shortens the time for identifying the cause of the error. Even if there is a defect such as no response in the processing of the business application itself called from the job scheduler, the error information can be detected. Further, there is no waste in server resources, and only necessary information can be acquired immediately. In addition, it is possible to specify an essential error cause without correcting a program (business application) that has been operating for many years.

  The above-described embodiment of the present invention can be realized by hardware or firmware or software on a DSP (Digital Signal Processor) board or CPU board as one function of the management apparatus.

  The management apparatus to which the present invention is applied is not limited to the above-described embodiment as long as the function is executed. Needless to say, the apparatus may be a system that performs processing via a network such as a LAN or a WAN.

  It can also be realized by a system including a CPU, a ROM or RAM memory connected to a bus, an input device, an output device, an external recording device, a medium driving device, and a network connection device. That is, a hard disk, a memory such as ROM and RAM, an external recording device, and a portable recording medium in which the software program for realizing the system according to the above-described embodiment is recorded are supplied to the management device. Needless to say, this can also be achieved by reading and executing the program.

  In this case, the program itself read from the portable recording medium or the like realizes the novel function of the present invention, and the portable recording medium or the like on which the program is recorded constitutes the present invention.

  Examples of portable recording media for supplying the program include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, DVD-RAMs, magnetic tapes, and nonvolatile memory cards. Various recording media recorded via a network connection device (in other words, a communication line) such as a ROM card, electronic mail or personal computer communication can be used.

  The computer (information processing apparatus) executes the program read out on the memory, thereby realizing the functions of the above-described embodiment, and an OS running on the computer based on the instructions of the program. Performs part or all of the actual processing, and the functions of the above-described embodiments are also realized by the processing.

  Furthermore, a program read from a portable recording medium or a program (data) provided by a program (data) provider is stored in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. After being written, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiment are realized by the processing. obtain.

  That is, the present invention is not limited to the embodiments described above, and can take various configurations or shapes without departing from the gist of the present invention.

1 Data Center 2 Network 3 Bank ATM
4 Bank host 11 WWW server 12 Business server 13 Database server 14 Management device 21 Job information acquisition unit 22 Target job information search unit 23 Error verification unit 24 Investigation information acquisition unit

Claims (4)

A data center having a plurality of servers, a management device for managing a data center that relays transaction processing executed between a host computer of a financial institution and an automatic transaction device,
A job information acquisition unit that acquires job information related to a job executed on the server;
A target job information search unit for searching for target job information including a predetermined character string from the job information acquired by the job information acquisition unit;
An error verification unit that verifies an error by executing a verification command associated with the target job information with respect to a server that outputs the target job information searched by the target job information search unit;
Based on the verification result verified by the error verification unit, a survey information acquisition unit that executes a survey information acquisition command for investigating the error status of the server,
A management apparatus comprising: The job information acquisition unit stores the acquired job information in a memory in a table format,
The target job information search unit searches for job information stored in the memory.
The management apparatus according to claim 1. The job information acquisition unit acquires job information related to a job that satisfies a predetermined condition based on a job start time, a job end time, and an average execution time of the job;
The management apparatus according to claim 1, wherein the management apparatus is a management apparatus. A data center having a plurality of servers, a management method executed in a management device that manages a data center that relays transaction processing executed between a host computer of a financial institution and an automatic transaction device,
Get job information about jobs executed on the server,
Search the target job information including a predetermined character string from the acquired job information,
For the server that has output the retrieved target job information, execute a verification command associated with the target job information to verify the error,
Based on the verified verification result, execute a survey information acquisition command for investigating the error status of the server,
A management method characterized by that.

Images