JP7036603B2 - Operation management system - Google Patents

Description

The present invention relates to an operation management system, and more particularly to an operation management system capable of operating and managing various types of systems.

Conventional operation management system functions include a failure countermeasure function that detects and recovers from hardware and software failures, a configuration management function that manages hardware placement and storage device free space, and traffic and CPU usage rates. There is a performance management function that manages the above, and a system that has one or more of these functions is an operation management system. Patent Document 1 discloses a system management device having a failure countermeasure function, stores failure response information regarding a failure that may occur in the managed device, and acquires and responds to the corresponding failure response information when a failure occurs. It is stated to do.

Japanese Unexamined Patent Publication No. 2017-102870

Even in the conventional operation management system, it was possible to manage multiple types of devices. This allows the operation management system to directly access the managed device, acquire necessary information such as logs and status, grasp the situation, and perform some operation on the managed device as needed. This is because, for example, information acquisition and operation are realized in cooperation with a management target device via API (Application Programming Interface). Therefore, various information could not be acquired and operated for the managed device whose interface specifications were not clarified, and it could not be managed. Alternatively, it is necessary to refer to the developer who developed this managed device, grasp the interface specifications, incorporate the operation that matches the specifications into the system management device, and modify the managed device as necessary. Was there. In particular, many general-purpose machines such as mainframes and office computers have not been disclosed to the outside, so they could not be targeted by the operation management system.

The present invention has been made in view of these problems, and an object of the present invention is to provide an operation management system for managing a managed device that could not be managed in the past.

The operation management system according to the present invention has an automatic execution unit that receives a command statement related to operation management for the managed device and executes a command to the user interface of the managed device, and a job for a plurality of command statements for the managed device. The job registration unit to be registered as, the automatic execution log recording unit that records the automatic execution log in which the automatic execution unit executes each instruction statement of the job in association with the target job, and the automatic execution log recording unit that is associated with the job selected by the user. From the display unit that displays the automatic execution log to the user and the log output by the managed device, the related log related to the execution of each instruction by the automatic execution unit is extracted and recorded together with the instruction of the corresponding job. It is equipped with a log recording unit .

According to the present invention, a plurality of instructions constituting a job are sequentially executed for the user interface of the managed device, the automatic execution log generated by the execution is recorded, and the automatic execution log is displayed to the user in association with the job. Therefore, even a managed device that could only be managed by the user's direct operation can be managed.

It is a schematic diagram which shows the structure of the whole operation management system which concerns on this embodiment. It is an operation management job screen about the operation management system which concerns on this embodiment. This is a job editing screen related to the operation management system according to this embodiment. This is a user interface of the managed device (mainframe) according to the present embodiment. This is a job edit screen (for automatic execution) related to the operation management system according to this embodiment. It is a sequence diagram of the operation management system which concerns on this embodiment. This is the integrated log screen of the operation management system according to this embodiment.

Hereinafter, the same or equivalent components, members, and processes shown in the drawings shall be designated by the same reference numerals, and duplicate description thereof will be omitted as appropriate. In addition, some of the members that are not important for explanation are omitted in each drawing.

As shown in FIG. 1, the operation management system according to the present embodiment includes a plurality of managed devices 11 ... 1n to be system-managed and an operation management server 21 ... 2n that manages the managed devices, respectively. And the terminal devices 31 and 32 that operate and control the operation management server 21 ... 2n. Each device is connected to the network 40 and can communicate data with each other by a predetermined authority. Here, although the system hardware configuration shown in FIG. 1 is used in the present embodiment, various various hardware configurations can be adopted. Further, although the operation management system in a broad sense includes the managed devices 11 ... 1n, the operation management system in a narrow sense includes an operation management server 21, an automatic execution device 51, and a terminal device 31. ..

Various systems are assumed for the managed devices 11 ... 1n, and various business devices such as devices constituting a securities system, devices constituting a banking system, and devices constituting a distribution system are applicable. The managed devices 11 ... 1n may cooperate with each other to form one system.

The operation management servers 21 ... 2n each manage at least one of the managed devices 11 ... 1n, and one operation management server operates and manages a plurality of managed devices 11 ... 1n. Alternatively, a plurality of operation management servers may operate and manage one or a plurality of managed devices. The operation management server 21 ... 2n operates and manages the managed devices 11 ... 1n, and monitors the status (normal / abnormal) and performance of the managed devices 11 ... 1n (monitoring results are: Managed device 11 ... Recorded every 1n), notify the operation manager when an abnormality is detected / when the performance exceeds a predetermined threshold. Depending on the operation management server 21 ... 2n, when an abnormality is detected, a response corresponding to the abnormality may be automatically performed. Generally speaking, a failure countermeasure function that detects and recovers from hardware and software failures, a configuration management function that manages hardware layout and free space of storage devices, and a performance management function that manages traffic and CPU usage rates, etc. Provides the function of.

The terminal device 31 is a device used by the operation manager, and accesses the operation management servers 21 ... 2n via the terminal device 31 to perform necessary operations. The terminal device 32 is a device used by an assistant who assists the operation manager, and receives an instruction from the operation manager and performs necessary work on the managed devices 11 ... 1n via the terminal device 32. .. The terminal device 32 is not necessarily a necessary system component because of its auxiliary position.

The network 40 includes a wired network or a wireless network or a combination thereof, and may include an Internet, an intranet, a LAN, a WAN, a WiFi, a Bluetooth®, a wireless telephone network, and the like.

When the terminal device 31 receives a job management instruction from the operation manager, it accesses the operation management servers 21 ... 2n, acquires necessary information, and displays the operation management job screen. As shown in FIG. 2, on the operation management job screen, the device list of the managed devices for which job management is set is displayed on the left side, and when one device is selected from the device list on the left side, the device selected on the right side is set. A list of jobs that have been completed is displayed. As the operation content of the job, the above-mentioned monitoring for operation management, abnormality notification, and abnormality response can be targeted, or control to the managed devices 11 ... 1n can be targeted. Although a simple job is shown in FIG. 2 for convenience of explanation, "node life / death monitoring", "system information monitoring", "process operation status monitoring", "system detailed information monitoring", and "log monitoring" should also be registered as jobs. You can also.

When any one job is selected and the edit mode is set, the job name, the node name of the managed device 11 ... 1n, the operation manager ID that manages the job, and the managed device 11 are displayed on the job edit screen. The operation content to be executed is displayed in 1n. The operation content may be a command passed to the managed device 11 ... 1n (may be accompanied by an argument), or the command may be renamed so as to be easy for the user to understand. Various information displayed on this job edit screen can be edited, and when a new job registration is instructed from the operation management job screen, a screen similar to the job edit screen is displayed and various contents can be newly set. .. Here, in addition to the fact that the operation administrator can select and execute any job from the job list in FIG. 2, by setting the date and time specification and the periodic specification, the specified date and time and the specified periodical can be set. You may accept the setting to execute the job at the time of day. Although the operation manager sets the operation management server 21 ... 2n on the operation management job screen and the job edit screen using the terminal device 31, the operation management server 21 ... 2n is constructed. You may operate the computer and directly set the operation management server 21 ... 2n.

The operation management server 21 ... 2n executes the job set by the terminal device 31 to the job-targeted managed devices 11 ... 1n. In FIG. 1, the managed device 11 ... 1n and the operation management server 21 ... 2n to be managed are connected to the same LAN (LOCAL Area Network), and the operation management server 21 ... 2n Sends the command set in the target job to the managed devices 11 ... 1n via the LAN. It is also possible to construct the managed device 11 ... 1n and the operation management server 21 ... 2n on the same computer. In that case, commands are given between mutual processes in the own machine without going through the network. Will be handed over. When sending a command over the network, it may be necessary to execute the login process in advance. The job edit screen of FIG. 3 is a screen opened by selecting a value reference job shown in FIG. In this job, access the managed node "Finace_node01" as the operation administrator "openmanager01" and log in. In the operation content, the command to be sent to the managed node "Finace_node01" is input. "Login (openmanager01, ****)" means to log in with the account "openmanager01" and the password "****". "Get (id0123, value)" means to acquire the owned asset "value" of the user "id0123", and "Logout (opemanager01)" means to log out. These commands are commands for FINace_node01 to receive external control, but if it is a node of another system, it has a different command system, and even if it operates the same, another command is required. For example, the operation management server 21 prepares a command system that is easy for the user to understand, and when the operation management server 21 sends a command to the managed device 11, it is converted into the command system of the managed device 11 and transmitted. You may.

Depending on the mainframe (hereinafter, the explanation will be given for the mainframe, but the same applies to general-purpose machines including office computers, etc., not limited to the mainframe), external operations from other than the UI (User Interface) of the mainframe. If there is a device that cannot be directly controlled and the device is managed, the job cannot be registered as it is because there is no command to send or pass to the device. Until now, when the operation administrator wants to execute some job on a device that cannot be directly controlled, the operation administrator has directly started the UI of the mainframe and executed the operation. In particular, if the mainframe located in the computer room or data center does not have a remote UI, the operation administrator will directly visit the location of the computer where the uncontrollable device is built and that computer. It was a very time-consuming task because the operation was performed using the keyboard of. On the other hand, the operation management server 21 ... 2n is equipped with an automatic execution function, and the operation management server 21 ... 2n itself or another process generated by the operation management server 21 ... 2n automatically executes the user's operation as it is. .. For example, the UI of the mainframe is activated by pressing a specific icon, and operations such as clicking and data input are performed on behalf of the user for the UI of the activated mainframe. An OS (Operating System) is built on the computer, and the UI of the mainframe receives user operations from the operation management servers 21 ... 2n via the OS. These operations can be performed by the operation manager setting the operation contents for the UI of the mainframe on the operation management server 21 via the operation terminal 31. As a specific method, two methods are shown here (the first method is called a recording type operation setting, and the second method is called a function list type operation setting). In the recording type operation setting, the operation management server 21 stores the operation content of the operation manager on the mainframe UI by having the user perform a sample operation once. The operation management server 21 monitors the operation of the operation manager and stores the operation contents for the UI of the mainframe. Specifically, in the case of GUI, which object in the UI of the mainframe is clicked or a value is input is stored. The UI of the mainframe shown in FIG. 4 is a login screen and a search result screen, and a plurality of text labels, text boxes, and OK button objects are arranged on each screen. For example, the text box next to the text label of "USERID" is given the object identification information of "obj001", whereby the object can be uniquely identified. The operation management server 21 replaces the stored operation contents with functions and arguments that can be understood by the operation management server 21 and records them as the operation contents of the job edit screen. This function and the argument may be a programming language or a script language system unique to the operation management server 21, or may be, for example, a general-purpose programming language or a script language system.

FIG. 5 is a description of the operation contents in the script language unique to the operation management server 21. "Run (finance_ui)" is an instruction to start the UI "finance_ui" of the mainframe, and by executing this instruction to the computer on which the managed device 11 is built, the UI "finance_ui" of the mainframe is changed. It will be started and the login screen will be displayed first. For "Set value (obj001, opemanager01)" and "Set value (obj002, ****)", enter the ID "opemanager01" in the text box "obj001" next to the text label "USERID" on the login screen, and enter the text label "opemanager01". It is an instruction to enter the password "*****" in the text box "obj002" next to "PASSWORD", and "Click (obj003)" is an instruction to press the OK button "obj003". "Set value (obj004, id0123)" is a command to input "id0123" in the text box "obj004" of the search screen (not shown), and "Click (obj005)" is a command to press the OK button of this search screen. FIG. 4B is a search result screen showing the search results searched by the search by the search screen, and "Copy (obj006, var001)" is the value "value" placed next to the text label "value" in the screen. It is an instruction to input the value "50" input to "obj006" to the variable "var001". "Send (var001)" is an instruction to send the variable "var001" to the operation management server 21. "Click (obj007)" is an instruction to press the close button "obj007". The job edit screen of FIG. 3 is a short command statement because it is an API command for the managed device 11, whereas the job edit screen (automatic) of FIG. 5 has an interpreter and an OS for the UI of the mainframe. It is a long statement to command via.

In the function list type operation setting, the UI of the mainframe to be operated is specified, and the same contents as the operation contents of the operation administrator are set from the object list information of the UI of this mainframe, the operation function list, and the conditional expression. It's a way to go. The recording type operation setting and the function list type operation setting can be combined, and since the function list type operation setting corresponds to simple coding, a sample operation can be easily performed with the recording type operation setting and the detailed operation is the function list type operation setting. It is also possible to set from the operation function list and the conditional expression. It should be noted that the automatic execution by setting the operation content can be applied to the directly controllable device other than the directly controllable device. This is effective when you want to execute an operation that cannot be realized by the API command or the combination of API commands for the directly controllable device.

When a job is executed by the operation management server 21 ... 2n, the execution result may be returned for the execution depending on the operation target device, and the operation management server 21 ... 2n returns the execution result for each job. It is stored in and the execution result is displayed according to the operation of the operation administrator.

Here, the automatic execution device 51 ... 5n, which is an independent device for the automatic execution function by the operation management server 21 ... 2n, is a computer on which the operation target device 11 ... 1n is constructed, and the operation management server. It can also be built on a computer on which 21 ... 2n is built, or on another new computer, and the contents, the operation contents of the job or the identification information of the operation contents are acquired from the operation management server 21 ... 2n. Then, the automatic execution device 51 ... 5n executes. When the automatic execution device 51 ... 5n is built on the computer on which the operation target device 11 ... 1n is built, the operation is performed on the own device, while the automatic execution device 51 is performed on a computer other than the own device. ... When 5n is constructed, the operation is executed from the outside, so that it is a remote operation. In the case of this configuration, instead of setting the operation content of the job in the operation management server 21 ... 2n, it may be set directly in the automatic execution device 51 ... 5n. Further, since the job is executed by the automatic execution devices 51 ... 5n, the execution results are also acquired by the automatic execution devices 51 ... 5n, and the automatic execution devices 51 ... 5n are assigned to the operation management servers 21 ... 2n. Will be returned.

When an error occurs, it is necessary to notify the operation management server 21 ... 2n of the error that has occurred in the managed devices 11 ... 1n. When a command is executed to a directly controllable device, the result of command execution (including the result of error) is notified, so the operation administrator is registered by registering the content in the corresponding job or history. You can check the result including the error.

On the other hand, when the instruction of the operation content is executed to the device that cannot be directly controlled, the result including the error is not notified from the managed device 11 ... 1n to the operation management server 21 ... 2n as it is. Since the error screen is started when an error occurs while operating the UI of the main frame, the error screen or the error text of the error screen is notified to the operation management server 21 ... 2n and registered in association with the corresponding job. By doing so, the operation manager can grasp the error content by referring to the error screen or the error text. In addition, although the example of notifying only the error screen was explained, by hard-copying the operation target screen and sending the screen image each time each instruction statement is executed, the operation administrator does not depend on normal processing or error processing. It is possible to grasp the substance of processing. If an error occurs, referencing the operation target screen of the processing before that may lead to the resolution of the error.

Next, the operation of the entire system including the system management device according to the present embodiment will be described with reference to FIG. In this operation description, for convenience of explanation, the managed device 11, the operation management server 21, the terminal device 31, and the automatic execution device 51 will be described, and the managed devices 11 ... 1n other than the managed device 11 will be described. Of the managed devices and the operation management servers 21 ... 2n, the operation management servers other than the operation management server 21 are not used in the description. When the operation manager accesses the operation management server 21 from the operation terminal 31 and logs in as the operation manager, the operation management job screen showing the nodes and jobs to be managed by the target operation manager is displayed on the operation terminal 31. The operation manager registers new jobs and edits already registered jobs as necessary. In the job settings, the date and time to be executed can be set, and when the set date and time arrives, the operation management server 21 shifts to the job execution process. In addition to job reservation execution, it is also possible to instruct the operation manager to execute the selected job in real time. Here, the operation of real-time execution will be described.

The operation terminal 31 instructs the operation management server 21 to execute the specified job, the operation management server 21 specifies the specified job, and acquires the instruction group which is the operation content of the specified job (S110). The operation management server 21 makes a job execution request including the acquired instruction group to the automatic execution device 51 waiting on the computer on which the managed device 11 specified by the job is built (S115). Here, the operation of the automatic execution device 51 to acquire the instruction group will be described. However, the instruction group to be executed by the target automatic execution device 51 is acquired from the operation management server 21 and recorded in advance, and the instruction group is identified. May be an operation of reading out the instruction group corresponding to the received ID from the storage area by receiving the message from the managed device 11. The automatic execution device 51 that has received the instruction group executes the instruction at any time (S120). The instruction is, in principle, an operation control for the UI of the managed device 11, and the managed device 11 receives the operation control via the OS and executes the operation (S125). Various data may be output depending on the operation content, and the output value is acquired and recorded on the automatic execution device 51 side (S130), and at the same time, the screen that is active after the operation is executed is hard-copied (S135). ). Next, it is determined whether or not all the instructions have been executed, and if all the instructions have not been executed, the process returns to S120. When all the instructions are executed, the recorded output values and the hard copy of each screen are associated with each instruction and data is transmitted to the operation management server 21 as an automatic execution log (S145). The operation management server 21 records the received automatic execution log in association with the job (S150). Using the operation terminal 31, the operation manager can refer to the automatic execution log of the job whose execution has been completed (S155).

A typical example of using this operation is operation management in which an abnormality detection monitoring job is periodically performed, nothing is done if there is no abnormality detection, and a corresponding job corresponding to the abnormality detection is performed if there is an abnormality detection. .. Similarly, it is also possible to perform operation management by periodically referring to the log of the managed device 11 and performing a log reference job to report to the operation management server 21 when a predetermined keyword is included.

According to the system management device according to the present embodiment, the interface specifications are not known, and the managed device, which is a device that cannot be directly controlled, is targeted for operation management without the user operating the managed device with the user interface. be able to.

In the present embodiment, if there is a problem by referring to the automatic execution log, it is possible to analyze it, correct the instruction group of the job based on the analysis result, and consider the maintenance of the managed device 11. can. Here, in addition to the automatic execution log, only the portion related to the instruction group of the target job can be extracted from the log output by the managed device 11 itself and transmitted together with the automatic execution log. Better analysis is possible by being able to refer to the log of the corresponding portion of the managed device 11 in addition to the automatic execution log. When the execution date and time are assigned to the log of the managed device 11, the automatic execution device 51 also assigns the execution time of each instruction to the automatic execution log, and collates the execution dates and times of the mutual logs, so that the operation administrator Can be referred to after specifying the log related to the specified instruction by specifying either the execution date and time or the instruction of the job. FIG. 7 is an integrated log screen showing the execution result including the log. This integrated log screen is started by selecting a job and instructing to refer to the log. If multiple execution results are linked to a job by executing the job multiple times, it is necessary to select one of them (the operation of displaying only the latest execution result may be acceptable). In this integrated log screen, the instruction group of the target job, the automatic execution log, the log generated by the managed device 11, and the screen related to the test execution can be confirmed in an integrated manner. In addition to this, by selecting one of the instruction groups, the target log in the corresponding automatic execution log, the target log in the managed device log, and the corresponding screen of the screen hard copy are displayed and displayed. .. As a result, the operation manager can correct the instruction statement as it is if there is a problem in the log or the screen. It is also possible to confirm whether the modified instruction group is properly executed by executing the modified instruction group as it is and displaying the integrated log screen again. Here, an example of selecting one of the instruction groups has been described, but one object is selected from a plurality of automatic execution logs, managed device logs, or screen hard copies to reveal the corresponding instruction group. The operation may be a display operation. For example, the user can select a screen hard copy of the error screen to check the corresponding instruction or log. Here, associating the instructions of the instruction group with the automatic execution log is naturally possible because the automatic execution device 51 executes the instructions by itself and generates the log. Next, the association with the managed device log is performed by comparing each execution date and time of the automatic execution log with each log date and time of the managed device log.

When the automatic execution device 51 is executing an instruction group, the managed device 11 may execute an operation different from the assumption. In that case, if it is determined that the automatic execution device 51 cannot perform normal processing due to a timeout or the like, it is determined. The execution of the instruction group is stopped, and the automatic execution log up to the time when the command group is stopped is transmitted to the operation management server 21.

When a new job is registered or a job is edited from the operation terminal 31 to the operation management server 21, the value is fixedly set in the argument if it is an instruction to input a value. When repeating the same instruction for multiple values, you may create the instruction statement for the number of times you want to repeat, but save multiple values in an external file or store multiple values in the database. , It is also possible to set repeated instructions to execute the same instruction for the number of values that the user wants to execute.
In the present embodiment, the operation of the operation management server 21 for operation management using the automatic execution device 51 has been described, but the operation management is performed for the device that cannot be directly controlled by using the automatic execution device 51, and the operation is managed for the device that can be directly controlled. The operation management server 21 can also directly perform an operation related to operation management on the managed device 11. At this time, the operation management server 21 may remotely perform an operation management operation on the managed device 11, or an agent for operation management is constructed on the computer on which the managed device 11 is built, and this operation management is performed. The operation management operation may be performed on the agent and various reports may be sent to the operation management server 21.

In this embodiment, an example in which the operation manager performs operation management using the terminal device 31 has been described, but as a standard, the operation manager manages the operation on the terminal device 31, and the assistant is from the operation manager. In response to the instruction, the terminal device 32 may be used to assist the operation management. For example, after a plurality of jobs have been executed, the assistant checks the automatic execution log to check whether normal processing is performed, and an abnormality occurs. If there is a job being processed, it may be a workflow that reports to the operation manager and asks for instructions.

INDUSTRIAL APPLICABILITY The present invention can be suitably used for an operation management system capable of operating and managing various systems.

Managed equipment 11, 1n
Operation management server 21
Terminal devices 31, 32
Network 40
Automatic execution device 51, 5n

Claims (5)

An operation management system that operates and manages a managed device, the automatic execution unit that receives an instruction statement related to operation management for the managed device and executes an instruction to the user interface of the managed device, and the managed device. A job registration unit that registers multiple instructions for a job as a job, and an automatic execution log recording unit that records the automatic execution log in which the automatic execution unit executes each instruction statement of a job in association with the target job, which is selected by the user. From the display unit that displays the automatic execution log associated with the job to the user and the log output by the managed device, the related log related to the execution of each instruction by the automatic execution unit is extracted and the corresponding job. An operation management system equipped with a related log recording unit that records along with the instructions of . The operation management system according to claim 1, wherein the automatic execution log records a value output by execution of each instruction by the automatic execution unit together with an instruction of a corresponding job. The operation management system according to claim 1, wherein the automatic execution log records a screen related to execution of each instruction by the automatic execution unit together with an instruction of a corresponding job. The operation management system according to claim 1, wherein a job for detecting an abnormality in a managed device and a job corresponding to the abnormality are registered in the job registration unit. The plurality of instructions of the job, the corresponding automatic execution log, and the log output by the managed device are managed in association with each other.
When any one of the instructions for the job is selected, the corresponding automatic execution log and the log output by the managed device are displayed and displayed.
The operation management system according to claim 1.

Images