JP5379618B2 - Computer system - Google Patents

Description

The present invention is related to a computer system for the command to the monitored devices on the network.

  An operation system is a program for operating a computer system. For example, on a network, this program is operated by a network server to monitor and manage devices, connections, applications, and the like of the entire network. In such a configuration, an HMI (Human Machine Interface) terminal for displaying the configuration state of the computer system is a computer system to be monitored and each device constituting the computer system (hereinafter, “monitored device”). Data and commands are input for monitoring.

  The monitoring target device monitored by the operation system provides various services to the user, and the operation system registers, changes, and references data related to the service to the monitoring target device. When data setting or the like is performed on the monitoring target device, a command is input from the server to the monitoring target device using the HMI terminal. In addition, in order to improve efficiency in terms of maintenance, etc., when it is desired to simultaneously set data for a plurality of monitoring target devices, a command is simultaneously input from the server to each monitoring target device (for example, Patent Document 1).

JP-A-6-75912

  However, in the technique described in Patent Document 1, there is a command that should not be simultaneously input to a plurality of monitoring target devices depending on the command to be input, but this is not taken into consideration. For example, when a plurality of monitoring target devices simultaneously input a command for updating one database to a plurality of monitoring target devices, the input monitoring target devices start a database writing process all at once. There is a possibility that contention will occur in processing, and service may be affected by performance error due to contention error or processing waiting. For this reason, it is necessary for the operator to classify commands that can be entered at the same time as commands that should not be entered at the same time with respect to commands to be entered into the monitoring target device, and it takes time to sort the commands one by one. There was a point.

The present invention has been made to solve such a problem. A command that is prohibited from being simultaneously input to a monitored device is erroneously input at the same time, causing a service error due to a conflict error or waiting for processing. An object of the present invention is to provide a computer system that can prevent the situation from occurring.

In order to achieve the object, the present invention comprises a server (110) , a plurality of monitoring target devices (103) monitored by the server , and a database shared by each of the monitoring target devices. In the computer system in which the monitoring target device operates in accordance with the input command and the database is updated by the monitoring target device, the server inputs the input method setting file (162) in which the input method of each command is described. And a destination setting file (172) in which the priority order of each monitoring target device when the command is input to the monitoring target device is connected to the monitoring target device so that they can communicate with each other individually. And the same number of device communication individual units (132) as the number of the monitoring target devices. If the command is a simultaneous submission prohibition command for writing to the database, the simultaneous submission prohibition command is sent to the monitoring target device corresponding to the submission destination in the priority submission order described in the submission destination setting file. It is characterized in that each device communication individual unit is inserted in turn .
However, the numbers in parentheses are examples.

According to the present invention, a computer system for implementing obviate a situation in which it simultaneously put into the monitoring target device is erroneously charged simultaneously commands that are prohibited, thereby causing the like outages by conflict errors and pending It becomes possible to provide.

It is a block diagram of a computer system showing an example of an embodiment of the present invention. It is a figure which shows the structure of a script file. It is a figure which shows the structure of a division | segmentation script file. It is a figure which shows the structure of an injection | throwing-in method setting file. It is a figure which shows the structure of an input destination setting file. It is a flowchart which shows operation | movement of a HMI terminal. It is a flowchart which shows operation | movement of the terminal communication part in a server. It is a flowchart which shows operation | movement of the apparatus communication process part in a server. It is a flowchart which shows operation | movement of the apparatus communication separate part in a server. It is a figure which shows the example of the command thrown into a monitoring object apparatus.

An embodiment of a computer system according to the present invention will be described with reference to FIGS. 1 to 10. Note that, in describing the embodiment, parts having similar configurations or functions are denoted by the same reference numerals, and repeated description thereof may be omitted.

FIG. 1 is a configuration diagram of a computer system 100 according to the embodiment of this invention. As illustrated in FIG. 1, the computer system 100 includes an HMI terminal 101, a server 110, and a monitoring target device 103.
The HMI terminal 101 creates a script file (command file) 142 and transfers it to the server 110, a script execution unit 121 that requests the server 110 to execute the script file 142, and the server 110. A network connection unit 131 that performs communication is provided.

  Here, for example, the script file 142 is created in the syntax of Java (registered trademark) Script, and is executed from the server 110 to the monitored device 103 (hereinafter referred to as “device command”) 104 (FIG. 2). Is a file in which each line is described in order.

  The server 110 includes a control unit 210 and a storage unit 220. Further, the control unit 210 includes a terminal communication processing unit 112, a device communication processing unit 122, and a device communication individual unit 132, and the storage unit 220 includes a script file storage unit 141, a divided script file storage unit 151, and an input method setting file storage. Unit 161 and the input destination setting file storage unit 171. The operation system 102 is operated by a server 110 such as a network server, and is specifically a program that realizes the functions of the control unit 210. The server 110 includes a CPU (Central Processing Unit) (not shown), a storage device such as a RAM (Random Access Memory), a ROM (Read Only Memory), and a HDD (Hard Disk Drive) that serve as a storage area for storing the program, It consists of I / O (Input / Output) devices. The function of each unit is realized by executing a program stored in the storage unit 220 on the CPU.

  The terminal communication processing unit 112 communicates with the network connection unit 131 and the device communication processing unit 122 in the HMI terminal 101, respectively. Further, the terminal communication processing unit 112 receives the script file 142 transmitted from the HMI terminal 101 and stores it in the script file storage unit 141, or receives an instruction to execute a program by the script file 142 from the HMI terminal 101. The device communication processing unit 122 is notified.

  The device communication processing unit 122 communicates with the terminal communication processing unit 112 and the device communication individual unit 132, respectively. When receiving an instruction to execute the script file 142 from the HMI terminal 101, the device communication processing unit 122 reads the script file 142 stored in the script file storage unit 141, and divides the script file 142 for each monitoring target device 103. Then, a divided script file 152 (FIG. 3) is created and stored in the divided script file storage unit 151. By dividing the script file 142 (FIG. 2), the device command 104 (FIGS. 2 and 3) can be input for each monitoring target device 103 individually.

  When the device communication processing unit 122 determines the input method (serial input, parallel input) for inputting the device command 104 to the monitoring target device 103, the input stored in the input method setting file storage unit 161. The method setting file 162 (FIG. 4) and the input destination setting file 172 (FIG. 5) stored in the input destination setting file storage unit 171 are read. Further, after determining the input method, the device communication individual unit 132 is notified of the input method.

  Here, serial input refers to inputting the device command 104 from the server 110 to each of the monitoring target devices 103 in accordance with the priority order with respect to the plurality of monitoring target devices 103. Parallel input means that the device command 104 is simultaneously input from the server 110 to the plurality of monitoring target devices 103.

  The device communication individual unit 132 communicates with the device communication processing unit 122 and the monitoring target device 103, reads the divided script file 152, and the device command 104 according to the input method requested by the device communication processing unit 122. Is input to the monitoring target device 103.

  FIG. 2 is a diagram showing the configuration of the script file 142. As illustrated in FIG. 2, the script file 142 includes data of a monitoring device (hereinafter, also referred to as “input destination monitoring target device”) 103 that is the input destination of the device command 104 and the device command 104. The script file 142 describes device commands 104 that can be input from the operation system 102 to all the monitoring target devices 103. A plurality of device commands 104 to be input to one monitoring target device 103 can be specified.

  FIG. 3 is a diagram showing the configuration of the divided script file 152. As shown in FIG. 3, the divided script file 152 includes data of the submission destination monitoring device 103 and the device command 104. The divided script file 152 is created for each submission destination monitoring target device 103 and describes the device command 104 to be entered. As described above, by dividing the script file 142, the device command 104 can be individually input to the monitoring target device 103.

  FIG. 4 is a diagram showing the configuration of the input method setting file 162. As shown in FIG. 4, the input method setting file 162 includes data of an input identifier 114 and a device command 104. The input method setting file 162 is used to determine a command input method (serial / parallel), that is, to determine whether the device command 104 described in this file is a serial method or a parallel method. In this embodiment, the input method setting file 162 shows an example in which the device command 104 for prohibiting simultaneous input is described, that is, an example in which the device command 104 to be input in the serial method is described. Therefore, when the device command 104 described in the script file 142 matches the device command 104 described in the input method setting file 162, the serial method is selected as the command input method. Further, when the script file 142 is newly created and the device command 104 to be serially entered is newly described, the device communication processing unit 122 creates an input setting method file 162 reflecting the device command 104. Newly created.

  FIG. 5 is a diagram showing the configuration of the input destination setting file 172. As shown in FIG. 5, the input destination setting file 172 includes data from the input identifier 114 and the input destination monitoring target device 103. The input destination setting file 172 is used to determine the input order of the device commands 104 to the monitoring target device 103 when the device commands 104 are input in series. As shown in FIG. 5, the monitoring target device 103 is described for each input order when the device commands 104 are serially input. Further, when the script file 142 is newly created and the device command 104 to be serially entered is newly described, the device communication processing unit 122 creates the submission destination setting file 172 reflecting the device command 104. Newly created.

  The operation of the HMI terminal 101 will be described using the flowchart shown in FIG. 6 (see FIG. 1 as appropriate). First, the HMI terminal 101 determines whether the processing content to be processed is file transfer or file execution based on the device command 104 input to the monitoring target device 103 (step 601). If the processing content is file transfer (Yes in step 601), the script file 142 created by itself is transferred to the server 110 (step 602). This is because when a device command 104 to be input to the monitoring target device 103 is newly added in the HMI terminal 101, the script file 142 stored in the script file storage unit 141 in the server 110 needs to be updated. Therefore, it is necessary to create a new script file 142 including the device command 104 in the HMI terminal 101 and transfer it to the server 110. When the existing device command 104 existing in the script file 142 stored in the script file storage unit 141 is input to the monitoring target device 103 (No in Step 601), the execution of the script file 142 is transmitted to the server 110. Request (step 603).

  The operation of the terminal communication processing unit 112 in the server 110 will be described with reference to the flowchart shown in FIG. 7 (see FIG. 1 as appropriate). After being activated, the terminal communication processing unit 112 determines whether the processing content is transfer of the script file 142 or execution of the script file 142 in response to a processing request from the HMI terminal 101 (step 701). When the processing content is the transfer of the script file 142 from the HMI terminal 101 to the server 110 (Yes in Step 701), the script file 142 transferred from the HMI terminal 101 is received and stored in the script file storage unit (Step 702). ). When the processing content is the execution of the script file 142 (No in Step 701), the device communication processing unit 122 is notified of the fact (Step 703).

The operation of the device communication processing unit 122 in the server 110 will be described with reference to the flowchart shown in FIG. 8 (see FIG. 1 as appropriate).
When receiving an instruction to input the device command 104 to the monitoring target device 103 in the form of execution of the script file 142 from the HMI terminal 101, the device communication processing unit 122 divides the script file 142 and monitors the input destination. The divided script files 152 are created for the number of devices 103 (step 801). As a result, a divided script file 152 is created for each input destination monitoring apparatus 103. Then, the device communication individual unit 132 corresponding to the input destination monitoring device 103 that inputs the device command 104 is activated (step 802).

  Next, the device command 104 described in the script file 142 is compared with the device command 104 described in the input method setting file 162 (step 803). If the device command 104 described in the script file 142 exists in the input method setting file 162 (Yes in Step 804), the input destination setting file 162 is read, and when the device command 104 is input, from which monitored device 103 The apparatus command 104 is preferentially input or the input order is acquired (step 805). If the device command 104 described in the script file 142 does not exist in the input method setting file 162 (No in step 804), the device command 104 is requested to be input to all the activated device communication individual units 132, and the input destination is monitored. A reception result indicating that the command 104 has been received from the target apparatus 103 is received (step 806), and the process ends.

  If there is a submission destination monitoring device 103 that inputs the device command 104 (Yes in step 807), the device command 104 is input to the corresponding input destination monitoring target device 103 to the device communication individual unit 132. Request. Then, a reception result indicating that the device command 104 has been received is received from the input destination monitoring target device 103 to which the device command 104 has been input (step 808). If there is no input destination monitoring apparatus 103 to which the apparatus command 104 is input (No in step 807), the process ends.

  In this embodiment, the device command 104 described in the input method setting file 162 is the device command 104 input in series, but the device command 104 input in parallel may be described. In this case, the device commands 104 described in both the script file 142 and the input method setting file 162 are simultaneously input to the monitoring target device 103 as the device command 104 to be input in parallel.

  The operation of the device communication individual unit 132 in the server 110 will be described with reference to the flowchart shown in FIG. 9 (see FIG. 1 as appropriate). After being activated, the device communication individual unit 132 reads the divided script file 152 corresponding to the submission destination monitoring target device 103 (step 901). Next, the device command 104 is input to the monitoring target device 103 (step 902). Then, an execution result indicating that the device command 104 has been executed is received from the monitoring target device 103 (step 903).

  Next, a specific example of the device command 104 to be input to the monitoring target device 103 will be described with reference to FIG. As shown in FIG. 10, the command name to be input in parallel is “cmd1”, and the command names to be input in series are “cmd2” and “cmd3”.

  Since “cmd1” is a command for controlling the service running on the monitoring target device 103, the database shared between the monitoring target devices 103 and the other monitoring target devices 103 are not linked. Also good. For this reason, “cmd1” can input commands to the monitoring target device 103 in parallel.

  “Cmd2” is a command for updating the contents of the database shared with other monitoring target devices 103. When this command is input, a conflict occurs with another monitoring target device 103 in the database writing process, so that parallel input becomes impossible. Therefore, it becomes an object of serial insertion.

  “Cmd3” is a command for synchronizing information with other monitoring target devices 103 other than itself. Even when this command is input, writing to the database occurs and contention with other monitoring target devices 103 occurs, so parallel input becomes impossible. Therefore, it becomes an object of serial insertion.

  When the command is actually input to the monitoring target device 103, a parameter is given to the command and input as a command syntax. The command syntax of “cmd1” is input as “cmd1 param1”, and a parameter corresponding to param1 of the parameter table prepared separately is selected. The same applies to “cmd2” and “cmd3”.

  In the present embodiment, if any of the commands “cmd1,” “cmd2,” and “cmd3” does not exist in the script file 142 stored in the script file storage unit 141 of the server 110, the HMI terminal 101 A new script file 142 including this command is created and transferred to the server 110. Then, when the script file 142 related to “cmd2” and “cmd3” to be serially input is created, a submission method setting file 162 and a submission destination setting file 172 are created.

  When the HMI terminal 101 gives an instruction to input “cmd2” or “cmd3” to the monitoring target device 103, that is, an instruction to execute the script file 142, the device communication processing unit 122 reads “cmd2” in the script file 142. Alternatively, it is confirmed that “cmd3” exists in the input method setting file 162. Then, in order to input a command in accordance with the priority order of the monitoring target device 103 described in the input destination setting file 162, the device communication individual unit 132 corresponding to the monitoring target device 103 to be input is activated and input is instructed. Thus, after a command is input to the monitoring target device 103, the monitoring target device 103 notifies the server 110 that the input command has been executed.

As described above, the device command 104 that is prohibited from being simultaneously input to the monitoring target device 103 can be set for each monitoring target device 103. As a result, the device command 104 is checked by the operation system 102 at the time of command input, and if the device command 104 for which simultaneous input is prohibited is included, the command is sequentially input in series, so the monitored device 103 The maintainer does not need to separate commands that are prohibited from being simultaneously entered from other commands.
Further, by erroneously inputting the device command 104 that is prohibited from being simultaneously input, it is possible to prevent a situation in which a contention error or a service stop due to waiting for processing is caused.

100 Computer system 101 HMI terminal (terminal)
102 Operation system 103 Monitoring target device (Destination monitoring target device)
104 device command 110 server 111 script transfer unit 112 terminal communication processing unit 114 input identifier 121 script execution unit 122 device communication processing unit 131 network connection unit 132 device communication individual unit 141 script file storage unit 142 script file (command file)
151 Split Script File Storage Unit 152 Split Script File 161 Input Method Setting File Storage Unit 162 Input Method Setting File 171 Input Destination Setting File Storage Unit 172 Input Destination Setting File 210 Control Unit 220 Storage Unit

Claims (2)

A server, a plurality of monitoring target devices monitored by the server, and a database shared by each of the monitoring target devices, wherein the monitoring target device operates in response to a command input from the server, and the monitoring target In a computer system in which the database is updated by a device,
The server
A submission method configuration file that describes the submission method for each command,
A submission destination setting file in which the priority order of each monitoring target device when the command is input to the monitoring target device is described;
The same number of device communication individual units as the monitoring target devices, which are connected so as to be able to communicate with the monitoring target devices individually,
If the command is a simultaneous submission prohibition command for writing to the database with reference to the submission method setting file, the simultaneous submission prohibition command is submitted in the priority submission order described in the submission destination configuration file. Each of the device communication individual units is sequentially input to the monitoring target device corresponding to the previous one
A computer system characterized by that. The input method is from the server to the monitoring target device.
Parallel input method to input at the same time,
2. The computer system according to claim 1, including both a serial input method that inputs according to a priority order described in the input destination setting file.

Images