JP2008046669A - Operation management program, operation management method and device for executing the method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce the labor of the manager of a system even when the system is changed in the case of managing the operation of each management object of this system. <P>SOLUTION: When a system is changed, a sequence dependence information management table 170 in which information relating to the operation of the other management object as the operation presupposition of a management object is stored for each of a plurality of management object ID and a job management table 180 in which the ID of the necessary management object directly engaged in job execution is stored for every job are changed. When accepting an execution request job (S1401), a job management program 140 extracts the management object necessary for the execution of the job by referring to the job management table 180 (S1403), and all the management objects for operating the necessary management object are extracted by referring to the sequence dependence information management table (S1403), and the operation sequence of each management object is decided (S1404). An operation status management program 120 operates each operation object according to the decided operation sequence. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention is an operation management for starting and / or ending operation of a plurality of devices and / or a plurality of management targets of a system including a program (hereinafter, management target) mounted on the devices according to a predetermined order. The present invention relates to a program, an operation management method, and an apparatus for executing the method.

  In recent years, in order to facilitate system operation management, everything that is no longer required at the time of turning on the power of all devices, starting the program, and ending the job is necessary for a job (a series of business units in the system) A program that implements an operation management method that pre-designs the execution order of processing such as stopping the program and turning off the power of the equipment, and turning the equipment on and off, starting and stopping the program according to the execution order Various products are sold.

  As an idea for realizing the operation management method, there is one described in Patent Document 1 below. The idea is that the system administrator uses a predetermined symbol to represent each task to be executed on the computer, and connects the tasks indicated by the symbol with a link with a direction so that the task execution order can be determined. It is determined.

Patent No. 3624657

  However, in the above prior art, every time there is a change in the type of business, a change in the target device or program, the system administrator etc. must design the execution order of the business, and the business or target device As the number of programs increases, the burden becomes enormous, and there is a problem that a great load is imposed on the system administrator and the like. In particular, in the upcoming ubiquitous information society, it is said that a huge number of RFID (Radio Frequency ID) readers and various sensors are installed in the system. It is expected that designing will become increasingly difficult.

  Therefore, an object of the present invention is to execute an operation management program, an operation management method, and this method that can reduce the burden on a system administrator or the like associated with a system change even in a system with a large number of devices and programs. It is in providing the apparatus which performs.

An operation management program for solving the above problems is
In an operation management program for starting and / or ending operation of a plurality of management targets of a system having a plurality of management targets according to a predetermined order,
A target identifier registration step for accepting a managed object identifier and storing the received identifier in a configuration management table storing the managed object identifier for each of a plurality of managed objects;
The order in which the order dependency information of the management target is received for each of the plurality of management target identifiers by receiving the order dependency information on the operation or stop of the other management target as a precondition for the start or end of the management target An order dependency information registration step for storing the received order dependency information of the management target in the dependency information table;
An operation target receiving step for receiving an identifier of a management target to be started or stopped among a plurality of management target identifiers stored in the configuration management table;
When the management target identifier is received in the operation target reception step, all the extracted management objects related to the operation start or operation end of the management target are extracted with reference to the order dependency information table. An order generation step for determining the order of the operation start or operation end of the management target;
Is executed by a computer.

Here, the operation management program is
The job executed by the system and the identifier of the mandatory management target directly involved in the execution of the job are accepted as job execution requirements, and the job management table storing the job execution requirements of the job for each of a plurality of jobs, A job registration step for storing the received job and the job execution requirements of the job;
When receiving the execution of any one of the plurality of jobs stored in the job management table in the operation target reception step, all of the jobs essential for execution of the job are referred to with reference to the job management table. An operation target extraction step for extracting a management target identifier;
To the computer,
In the order generation step, with reference to the order dependency table, all the management objects related to the operation start or operation end of all the management objects extracted in the operation object extraction step are extracted and extracted. Define the order of operation start or operation end for all management targets.
It may be a thing.

In addition, other operation management programs for solving the above problems are:
In an operation management program for starting and / or ending operation of a management target of a system having a plurality of management targets according to a predetermined order,
The job executed by the system and the identifier of the mandatory management target directly involved in the execution of the job are accepted as job execution requirements, and the job management table storing the job execution requirements of the job for each of a plurality of jobs, A job registration step for storing the received job and the job execution requirements of the job;
The order in which the order dependency information of the management target is received for each of the plurality of management target identifiers by receiving the order dependency information on the operation or stop of the other management target as a precondition for the start or end of the management target An order dependency information registration step for storing the received order dependency information of the management target in the dependency information table;
An operation target receiving step for receiving any one of the plurality of jobs stored in the job management table;
When receiving the job in the operation target reception step, an operation target extraction step of extracting all management target identifiers essential for execution of the job with reference to the job management table;
Referring to the order dependency table, extracting all management objects related to the start or end of operation of all the management targets extracted in the operation target extraction step, and extracting all the management target operations An order generation step for determining the order of start or end of operation;
Is executed by a computer.

Here, each operation management program described above is
Command registration that receives the operation start command and operation end command of the management target and stores the received command in the operation command management table in which the operation start command and operation end command of the management target are stored for each of the plurality of management targets Steps,
When the operation start or operation end order of all the extracted management targets is determined in the order generation step, refer to the operation command management table storing the operation start command and the operation end command for each of the plurality of management targets. Then, an operation processing step for sequentially starting or ending operation of a plurality of operation objects according to a predetermined order,
It may be executed by the computer.

  The operation management method for solving the above problem can be achieved by causing a computer to execute one of the operation management programs described above.

  In addition, an operation management apparatus for solving the above problems can be configured by installing any of the operation management programs described above in a computer.

  The details of the means for solving the problems disclosed by the present application will become apparent from the description of the best mode for carrying out the invention and the drawings.

  According to the present invention, even in a system with a large number of devices and programs, even when the system is changed, the order-dependent information of the management target accompanying the change of the system and the job executed by the system after the change are changed. By registering mandatory management targets that are directly involved in execution, the operation sequence of all management targets necessary for the execution of each job is automatically generated, reducing the burden on the system administrator, etc. it can.

  In addition, according to the present invention, even in a system with a large number of devices and programs, it is possible to support frequent turning on / off of devices, starting and stopping of programs, and thus an energy saving effect is also expected. it can.

  Hereinafter, an embodiment of an operation management apparatus according to the present invention will be described with reference to the drawings.

  As shown in FIG. 1, the operation management apparatus 100 according to the present embodiment includes a plurality of management target devices 200 (a management target device 200a, a management target device 200b, a management target device 200c, a management target device 200d, a management target device 200e, a management target device). A generic name of the target device 200f) and the communication path 300 (communication path 300a, communication path 300b, communication path 300c, communication path 300d, communication path 300e) that connects between the operation management apparatus 100 and the management target apparatus 200 or between the management target apparatuses 200. , A communication path 300f, a communication path 300g, and a communication path 300h). It should be noted that the management target device 200g and the communication paths 300i and 300j with () in the figure are added by changing the system.

  The management target device 200 constituting the system is, for example, a PC (Personal Computer), a printer, various information processing devices, an RFID (Radio Frequency ID) reader, a power remote control device, a router, and the like. It is a device whose operation start, operation end, and operation status are confirmed. The management target device 200 is a device that includes at least a communication interface (not shown), and further includes one or more programs (not shown) that are checked in the operation management device 100 for operation start, operation end, and operation status. The communication interface is an interface such as a wired LAN card, a wireless LAN card, an RS-232C port, and the like, and communicates with at least one operation management device 100 or the management target device 200 via the communication path 300.

  The communication path 300 is a standard communication path such as a wired LAN, a wireless LAN, or RS-232C.

  The operation management device 100 is a device such as a PC, for example, and includes at least a CPU 101, a memory 102, a storage device 103, a communication interface 104, and an input / output device 105. The storage device 103 is a device that stores programs and data, such as a hard disk and a flash memory. The communication interface 104 is, for example, an interface such as a wired LAN card, a wireless LAN card, or an RS-232C port, and communicates with at least one management target device 200 via the communication path 300. The input / output device 105 includes an input device such as a keyboard and a mouse and an output device such as a display and a printer. The CPU 101 is an arithmetic device that executes a program stored in the storage device 103 while using the memory 102.

  The storage device 103 stores each management target device 200 constituting the system and an operation management program 10 that manages the operation of the program installed in the management target device 200. The operation management program 10 includes a configuration management program 110 for managing the system configuration, an operation state management program 120 for managing the operation state of the management target, and other management targets as prerequisites for the start and end of the operation of the management target. An order-dependent information management program 130 for managing order-dependent information related to the operation or stop of the system, a job management program 140 for managing jobs executed by the system, and a data reception / registration process for data reception and registration processing associated with system changes, etc. A registration program 190. The storage device 103 further includes a configuration management table 150 in which the IDs of the management target devices 200 constituting the system, program IDs installed in the management target devices 200, and the like, operating states for the respective management targets, and the like. Operation status management table 160 storing order, order dependency information management table 170 storing order dependency information for each management target, management target required for job operation for each job executed by the system, etc. Are stored in the job management table 180. Hereinafter, the management target device 200 and the programs installed in the management target device 200 are included in the management target.

  As shown in FIG. 2, the configuration management table 150 includes at least management target device ID 150a, management target device information 150b, connection device ID 150c, management target program ID 150d, and management target program information 150e as record fields. Including. Note that the data with () in FIG. 2, FIG. 3, and FIG. 4 and the data with () after the arrow in FIG. 6 are changed or added as the system changes. Data are shown.

  The management target device ID 150a lists all the management target device IDs that are IDs for identifying each management target device 200 managed by the operation management device 100. Here, the management target device ID of the management target device 200a is D200a, the management target device ID of the management target device 200b is D200b, the management target device ID of the management target device 200c is D200c, and the management target device ID of the management target device 200d. Is D200d, the management target device ID of the management target device 200e is D200e, the management target device ID of the management target device 200f is D200f, and the management target device ID of the operation management device 100 is D100.

  In the management target device information 150b, information such as the name of the management target device 200 corresponding to the management target device ID 150a of the record is set.

  The connection device ID 150c lists all the management target device IDs of other management target devices 200 connected to the management target device 200 corresponding to the management target device ID 150a of the record. For example, according to FIG. 1, the management target device 200b is connected to the management target device 200a and the management target device 200d. Therefore, the connection target ID 150c of the record corresponding to the management target device 200b includes the management target device of the management target device 200a. D200a that is the ID and D200d that is the management target device ID of the management target device 200d are listed.

  The management target program ID 150d is an ID for identifying each of the programs managed by the operation management apparatus 100 among the programs installed in the management target apparatus 200 corresponding to the management target apparatus ID 150a of the record. The management target program ID is listed. Here, the operation management apparatus 100 includes a program whose management target program ID is P001 among programs installed in the management target apparatus 200b and a management target program ID among programs installed in the management target apparatus 200d. Indicates operation management of the P001 program and the P002 program.

  In the management target program information 150e, information such as the full path of the program corresponding to the management target program ID 150d of the record is set. Here, the fact that the full path of the program whose management target program ID 150d is P001 among the programs installed in the management target apparatus 200b is “C: ¥ prg1” is stored. The configuration management table 150 is preset by input from the input / output device 105.

  The configuration management program 110 reads data from the configuration management table 150 described above, writes (registers) data in the configuration management table 150, and manages a plurality of management target devices 200 managed by the operation management device 100. This is a program for managing programs installed in each management target device 200 and managing the connection relationship between management targets.

  The operation state management table 160 is a table in which data for starting the operation, data for ending the operation, data for confirming the operation state, and the like are stored as management targets managed by the operation management apparatus 100. FIG. As shown in FIG. 5, at least the management object ID 160a, the operation start command 160b, the operation end command 160c, the operation state confirmation command 160d, and the operation state 160e are included as record fields.

  The management target ID 160a lists all of the management target device IDs of the management target devices 200 managed by the operation management device 100 and the management target program IDs of the programs managed by the operation management device 100. The field of the management target ID 160a further includes fields of 160aD and 160aP. The management target device ID of each management target device 200 to be managed in operation is set in 160aD, and the management target of the program to be managed in operation is in 160aP. A program ID is set. For example, here, D200a is set in 160aD of the record corresponding to the management target apparatus 200a that is managed by the operation management apparatus 100, and nothing is set in 160aP. Of the programs managed by the operation management apparatus 100, the record 160aP corresponding to the program (ID = P001) installed in the management target apparatus 100b is set with P001, which is the ID of the program, in 160aD. Is set to D200b.

  In the operation start command 160b, a command for starting operation of the management target device 200 or program corresponding to the management target ID 160a of the record is set. Here, the command for starting the operation of the management target device 200e whose management target ID 160a is D200e is “pwon adr_c adr_e”, and the command for starting the operation of the management target ID 160a having the D200bP001 is “start adr_b P001”. And so on. Note that the command “pwron adr_c adr_e” indicates that the operation management apparatus 100 has started the operation of the management target apparatus 200e in the management target apparatus 200c. In addition, the command “start adr_b P001” indicates that the operation management apparatus 100 causes the management target apparatus 200b to start operating the program installed in the management target apparatus 200b and whose management target program ID is P001. Show.

  In the operation end command 160c, a command for the operation management apparatus 100 to end the operation of the management target corresponding to the management target ID 160a of the record is set. Here, the command for terminating the managed device 200e whose management target ID 160a is D200e is “pwroff adr_c adr_e”, and the command for terminating the program whose management target ID 160a is D200bP001 is “stop adr_b P001”. And so on. Note that the command “pwroff adr_c adr_e” indicates that the operation management apparatus 100 causes the management target apparatus 200c to terminate the operation of the management target apparatus 200e. The command “stop adr_b P001” indicates that the operation management apparatus 100 has caused the management target apparatus 200b to terminate the operation of the program with the management target program ID P001 installed in the management target apparatus 200b. Show.

  In the operation status confirmation command 160d, a command for the operation management apparatus 100 to confirm the operation status of the management target corresponding to the management target ID 160a of the record is set. Here, the command for confirming the operation state of the management target device 200e whose management target ID 160a is D200e is “pwrchk adr_c adr_e”, and the command for confirming the operation state of the program whose management target ID 160a is D200bP001 is “status adr_b P001”. ”And so on. Note that the command “pwrchk adr_c adr_e” indicates that the operation management apparatus 100 causes the management target apparatus 200c to check the operation state of the management target apparatus 200e. In addition, the command “status adr_b P001” indicates that the operation management apparatus 100 causes the management target apparatus 200b to check the operation state of the program whose management target program ID is P001 included in the management target apparatus 200b. Show.

  In the operation status 160e, a result of confirming the operation status of the management target corresponding to the management target ID 160a of the record by the operation status confirmation command 160d of the record is set. In this case, OFF is set.

  A part of the operation state management table 160, specifically, the management target ID 160a, the operation start command 160b, the operation end command 160c, and the operation state confirmation command 160d are preset by input from the input / output device 105.

  The operation state management program 120 reads data from the operation state management table 160 described above, writes (registers) data in the operation state management table 160, and further manages the operation target device managed by the operation management device 100. 200 and a program installed in the management target apparatus 200 for checking the operation start, operation end, and operation state.

  The order dependency information management table 170 is data for managing the dependency relation of the operation start order and the dependency relation of the operation end order of the management target managed by the operation management apparatus 100. As shown in FIG. The field includes at least a management target ID 170a, an order dependency target ID 170b, operation start order dependency information 170c, and operation end order dependency information 170d.

  The management object ID 170a is the same as that listed in the field of the management object ID 160a of the operation state management table 160 in FIG. 3, that is, the ID of the management object.

  The order-dependent target ID 170b includes an ID of a management target that must be operating when the management target corresponding to the management target ID 170a of the record is started or stopped when the management target is stopped. All are listed.

  In the operation start order dependency information 170c, when starting the management target corresponding to the management target ID 170a of the record, the management target corresponding to the order dependency target ID 170b of the record must be operating or stopped. Whether it should be set is set. At this time, if the management target corresponding to the order-dependent target ID 170b of the record must be operating, “<−” is set, and other records correspond to the order-dependent target ID 170b of the record. If the management target corresponding to the management target ID 170a of the record has to be stopped when the management target is activated, “<...” Is set. Here, for example, it is shown that when starting a program whose management target ID 170a is D200bP001, the management target device 200b and the program P001 installed in the management target device 200d must be operating. Also, when starting the operation of the program whose management target ID 170a is D200dP001, the management target device 200d must be operating, while the management device 200e and the program installed in the management target device 200d (ID = D200dP001) Indicates that it must be stopped.

  The operation end order dependency information 170d indicates whether or not the management target corresponding to the order dependency target ID 170b of the record must be stopped when the management target corresponding to the management target ID 170a of the record is ended. Is set. At this time, if the management target corresponding to the order-dependent target ID 170b of the record has to be stopped, “<−” is set. Here, for example, when the management target device whose management target ID 170a is D200a is terminated, the management target device 200b and the management target device 200c must be stopped. Basically, if the operation start order dependency information 170c of the record whose management target ID 170a is α and the order dependency target ID 170b is β is “<−” or “<...”, The management target ID 170a is often used. Since the operation end order dependency information 170d of the record whose order dependency target ID 170b is α has a relationship of “<−”, the operation end order dependency information 170d is set only by setting the operation start order dependency information 170c. Can be set automatically. However, when the relationship does not hold, it is necessary to correct the operation end order dependency information 170d.

  FIG. 5 schematically illustrates the operation start dependency relationships of all the management targets shown in the order dependency information management table 170 described above. In the figure, the relationship between the management target and the operation start dependency target is indicated by an arrow toward the management target with the operation start dependency target as a base point. In addition, when the operation start dependent target must be operating (in the case of “<-”), the management target must be stopped when the operation start dependent target is started. The case (in the case of “<...”) Is indicated by a dashed arrow. For example, for a program whose management target ID 170a is 200dP002, solid arrows are drawn from the management target device 200d and the management target device 200f, which are operation start dependent targets, and the management target ID 170a is started from the program (ID = 200dP002). A dashed arrow is drawn for the program of D200dP001. 4 and 5, the same circled numbers are assigned to the corresponding parts in FIGS. 4 and 5 in order to clarify the correspondence between the two figures.

  As described above, the dependency relationship of the operation start order indicated in the field of the management target ID 170a, the field of the order dependency target ID 170b, and the field of the operation start order dependency information 170c in the order dependency information management table 170 in FIG. The dependency relationship of the operation start order of the management targets shown in FIG. 5 corresponds to 1: 1 and can be converted to each other. Accordingly, when the order dependency information management table 170 of FIG. 4 is preset, the input / output device 105 is operated while the operation start order dependency information diagram of FIG. Data can be easily set in each of the field of the management target ID 170a, the field of the order dependency target ID 170b, and the field of the operation start order dependency information 170c of the order dependency information management table 170. In addition, an operation end order dependency information diagram is created and displayed on the input / output device 105, and the input / output device 105 is operated to manage the field of the management target ID 170 a of the order dependency information management table 170 and the order dependency target. Data can also be set in each of the field of ID 170b and the field of operation end order dependency information 170d.

  The order-dependent information management program 130 reads data from the order-dependent information management table 170 described above, writes (registers) data in the order-dependent information management table 170, and is managed by the operation management apparatus 100. It is a program for managing the dependency relationship of the operation order.

  The job management table 180 is a table for managing a job as a series of business units in the system. As shown in FIG. 6, at least a job ID 180a, job information 180b, a job execution requirement 180c, The operation start order information ID 180d and the operation start order information 180e are included.

  The job ID 180a lists job IDs that are IDs for identifying each job that is a series of business units in the system. Information such as the name of the job corresponding to the job ID 180a of the record is set in the job information 180b.

  In the job execution requirement 180c, an operation target required for the operation of the job corresponding to the job ID 180a of the record is set. If there are multiple operation targets, use “× (logical product)” if each operation target is required, and “+ (logical sum)” if any of the operation targets is required. Is used. For example, when the job ID 180a is J001, the job execution requirement 180c is “D200bP001 × D200e × D200f”. Therefore, the operation of the job J001 includes the operation of the program whose management target ID is D200bP001 and the management target ID. It shows that the operation of the management target device that is D200e and the operation of the management target device whose management target ID is D200f are essential. Further, when the job ID 180a is J002, the job execution requirement 180c is “D200bP001 × (D200e + D200f)”. Therefore, the operation of the job J002 requires the management target apparatus 200 having the management target ID D200e. It shows that one of the management target devices whose management target ID is D200f and the operation of the program whose management target ID is D200bP001 are essential.

  Note that the management target that is essential for job execution refers to the management target that is directly involved in job execution when the job is executed. Is not included. Further, when determining the job execution requirement 180c, if there are a plurality of operation targets required for the operation of the job, the IDs of the operation targets are associated with each other by “× (logical product)” or “+ (logical sum). However, the method for setting the job execution requirement 180c is not limited to the logical expression, and various changes can be made without departing from the scope of the invention.

  In the operation start order information 180e, the management target ID set in the job execution requirement 180c and the management target ID necessary for operating the management target are set in a state in which they are arranged in the operation order. The operation start order information ID 180d is set with an ID given to the operation start order information 180e. The operation start order information ID 180d and the operation start order information 180e are generated by the job management program 140 every time the job is operated, as will be described later. For example, when the job ID 180a is J002, D200a, D200b, D200c, D200d, D200eD200dP001, and D200bP001 are set in the operation start order information 180e from the top. When the operation start order information 180e is set in this way, when the job J002 is operated, each operation target is operated in the order of the above operation target ID column.

  A part of the job management table 180, specifically, the job ID 180a, the job information 180b, and the job execution requirement 180c are preset by input from the input / output device 105.

  The job management program 140 reads data from the job management table 180 described above, writes (registers) data in the job management table 180, manages job execution requirements 180c, operation start order information 180e, and the like. This is a program for generating operation sequence information 180e and operation sequence information ID 180d. When the job management program 140 ends the operation of the job, it deletes the operation start order information ID 180d and the operation start order information 180e corresponding to the job from the job management table 180.

  Next, the operation of the operation management apparatus 100 when the tables 150, 160, 170, and 180 are preset is described with reference to the flowchart shown in FIG. In the following description, the operating entity is a program from the viewpoint of ease of understanding, but the actual operating entity is the CPU 101 that executes each program.

  First, the job management program 140 receives a job ID and a management target ID as necessary, or receives only a management target ID (S1401). Hereinafter, an example in which J002 is received as the job ID and D200e is received as the management target ID in step 1401 will be described.

  When receiving the job ID, the job management program 140 reads the job execution requirement 180c (“D200bP001 × (D200e + D200f)”) of the record of the job ID (J002) received in step 1401 from the job management table 180. When “+ (logical sum)” is included in the read job execution requirement 180c, it is uncertain which of the left and right of the logical sum should be operated. Therefore, the management target ID (D200e) received in step 1401 should be operated. Determine the job execution requirements. That is, the job execution requirement is determined as “D200bP001 × D200e” (S1402). If the management target ID (D200e) is not accepted in step 1401, for example, the management target indicated before “+ (logical sum)” or the status after “+ (logical sum)” is displayed. This can be dealt with by pre-determining the management target that is to be operated. When the job execution requirement 180c read from the job management table 180 does not include “+ (logical sum)”, the read job execution requirement is determined as it is as the job execution requirement.

  As described above, in this step 1402, in accordance with the job execution requirement 180c, all essential management targets that are directly involved in the execution of the job are extracted.

  Then, the job management program 140 reads the order dependency information management table 170 and creates an operation start order dependency information diagram while extracting all management targets related to the execution of the job (ID = J002) (S1403). If it is determined in step 1401 that the job ID is not received and only the management target ID is received, the user who has input the management target ID simply wants to operate the management target specified by the management target ID. Since it is an intention, step 1402 is not executed, and the process immediately proceeds to step 1403. Also in this case, the operation start order dependency information diagram is created while referring to the order dependency information management table 170 and extracting all the management objects related to the operation of the management object.

  In step 1403, the order-dependent information management table 170 is referred to, and the management target ID (D200bP001, D200e) included in the job execution requirement determined in step 1402 or the management target ID received in step 1401 is used as a starting point. The operation start order dependency information diagram is created while extracting the management target ID. Specifically, the management target (ID = D200b, D200dP001) that must be in operation when the management target (ID = D200bP001), which is included in the job execution requirement and becomes one of the base points, is extracted, Furthermore, when starting the operation of another management target (ID = D200b) as the base point, the management target (ID = D200a) that must be operating is extracted, and an arrow from the extracted management target to the management target of the base point Add. Further, when starting the operation of the extracted management object, the management object to be operated is extracted. Thereafter, the above processing is repeated until there is no management target to be extracted. Note that what is hatched in FIG. 8 is the management target of the management target ID (D200bP001, D200e) included in the job execution requirement determined in S1402, and is the management target that is the starting point of the processing of S1403. When an arrow is added, “<−” and “<...” In the order-dependent information management table 170 are distinguished.

  Then, the job management program 140 creates the operation start order dependency information table 190 shown in FIG. 9, creates operation start order information from this table 190, and uses this operation start order information as the operation start order of the job management table 180. In addition to writing to the field of information 180e, the ID of this operation start order information is set, and this ID is written to the field of operation start order information ID 180d of the job management table 180 (S1404).

  Here, the configuration of the operation start order dependency information table 190 and the creation of the operation start order information using this table 190 will be described.

  In this operation start order dependency information table 190, a management target ID field 190a is set on the horizontal axis, and an order dependency target ID field 190b is set on the vertical axis, and all management necessary for the operation of the job is set for each. Target IDs, that is, all management target IDs shown in the operation start order dependency information diagram of FIG. 8 are set. In the job management program 140, the operation start order dependency information 170c in which the management target ID 170a of the order dependency information management table 170 is γ and the order dependency target ID 170b is θ is the management target ID 190a of the operation start order dependency information table 190. All of them are copied to the cell whose order dependency target ID 190b is θ at γ. Further, a field 190c for the number of order-dependent target IDs is set on the vertical axis, and the number of “<−” or “<...” Included in the column of the management target ID 190a is set in this field 190c.

  The job management program 140 searches from the left to the right for the order dependency target ID number 190c in the operation start order dependency information table 190 that is “0”, and if there is one, the operation start order 190d in that column is set to “1”. Set. Further, “<−” and “<...” In the row of the order dependency target ID 190b (D200a) equal to the management target ID 190a (D200a) are deleted, and the number of order dependency target IDs 190c in the column of the deleted management target ID 190a is obtained. Decrement.

  The above process, that is, the process until the order-dependent target ID number 190c is searched for “0” and the order-dependent target ID number 190c is decremented is repeated. However, in the operation start order 190d of the management target ID having the order dependent target ID number 190c of “0”, a value obtained by adding 1 to the previously set value, that is, “1” is set to “1”. 2 ”is set. When the above processing is executed and the sequence numbers are set in all the fields of the operation start order 190d, the values set in the fields of the operation start order 190d become the operation order of the corresponding management target. The job management program 140 sets each management target ID in order from the top in the operation start order information 180e of the job management table 180 according to the operation order of each management target.

  The job management program 140 designates the operation start order information ID (J002G) of the job and transmits a job operation request to the operation state management program 120 (S1405).

  When receiving the job operation request, the operation state management program 120 reads the operation start order corresponding to the operation start order information ID (J002G) included in the job operation request from the job management table 180.

  Then, the operation state management program 120 follows the operation start order (when the operation start order generation information ID 180d is J002G1, in the order of D200a, D200b, D200c, D200d, D200e, D200dP001, D200bP001), If the operation state 160e of the record of the operation state management table 160 corresponding to is ON, the process proceeds to the management ID in the next order.

  Specifically, the operation state management program 120 indicates that the operation state 160e of the record of the operation state management table 160 corresponding to the management object ID in the order is OFF, and that of the management object ID of the management object ID is determined by the order dependency information management table 170. If all of the operating states 160e that should not be operating before are OFF, the command set in the operation start command 160b of the record is transmitted to the management target, and the management target is operated. Then, the command set in the operation status check command 160d is transmitted to the management target, and after confirming that the management target is operating, the operation status 160e is set to ON, and the next order The process moves to the management target ID.

  In addition, the operation state management program 120 indicates that the operation state 160e of the record of the operation state management table 160 corresponding to the management object ID in the order is OFF, and the order dependency information management table 170 precedes that of the management object ID. If one of the operating states 160e that should not be in operation is ON, all of those that should not be in operation are set in the record operation end command 160c corresponding to those that should not be in operation. The command set in the operation state confirmation command 160d is executed, it is confirmed that the operation is stopped, and the operation state 160e is set to OFF. Then, the command set in the operation start command 160b of the record corresponding to the management target ID in that order is executed, the command set in the operation state confirmation command 160d is executed, and it is confirmed that the command is executed. Then, the operation state 160e is set to ON, and the process proceeds to the management target ID in the next order.

  With the above processing, the job can be executed in the system according to the present embodiment. The operation state management program 120 stores which job and which management object ID has been completed, and can resume operation later.

  In the above, the method for starting the job operation has been mainly described. However, the method for ending the job operation can be realized by the same method.

  Next, data registration processing of the operation management apparatus 100 when the system is changed will be described according to the flowchart shown in FIG. In the following, as shown in FIG. 1, a new management target device 200g is added to the original system, and the management target device 200g and the management target devices 200d and 200c are connected via communication paths 300i and 300j. Will be described.

  First, the data reception / registration program 190 receives data to be registered in the configuration management table 150 from the input / output device 105 regarding the management target to be changed. In this case, the ID (D200g) of the added management target device 200g, the name of the management target device 200g, and the IDs (D200c, D200d) of the management target device connected to the management target device 200g are received. When the data is received, the data is transferred to the configuration management program 110 and registered in the configuration management table 150 (S1901). As a result, the data in parentheses in FIG. 2 is registered in the configuration management table 150.

  Subsequently, the data reception / registration program 190 receives data to be registered in the operating state management table 160 from the input / output device 105 regarding the management target to be changed. In this case, the ID (D200g) of the added management target device 200g, the operation start command (pron adr_c adr_g) of the management target device 200g, the operation end command (pwroff adr_c adr_g) of the management target device 200g, and this management The operating state confirmation command (pwrchk adr_c adr_g) of the target device 200g is received. When the data is received, the data is transferred to the operating state management program 120 and registered in the operating state management table 160 (S1902). As a result, the data in parentheses in FIG. 3 is registered in the operating state management table 160. Note that the field of the operation state 160e of the operation state management table 160 is not written at this time, but is written at the operation stage of the management target prior to the execution of the job as described above.

  Next, the data reception / registration program 190 receives data to be registered in the order-dependent information management table 170 from the input / output device 105 regarding the management target to be changed. In this case, the ID (D200g) of the added management target device 200g, the dependency target ID (D200c, D200dP001) of the management target device 200g, and the dependency target are operating when the management target device 200g is started to operate. Information indicating whether or not the dependency target must be stopped when the managed device 200g is terminated is received. At the same time, the management target ID (D200c) paired with them, the dependency target ID (D200g) pair, the management target ID (200dP001), and the dependency target ID (D200g) pair For information on whether or not the dependent target must be operating when this managed object is started, and whether or not the dependent target must be stopped when this managed object is ended Such information is also accepted. When the data is received, the data is transferred to the order dependency information management program 130 and registered in the order dependency information management table 170 (S1903). As a result, the data in parentheses in FIG. 4 is registered in the order-dependent information management table 170.

  Further, the reception / registration program 190 receives data to be registered in the job management table 180 from the input / output device 105 regarding a job related to the management target to be changed. In this case, the job ID (J001) related to the management target to be changed and the job execution requirement (D200bP001 × D200e × D200f × D200g) of this job are received. When the data is received, the data is transferred to the job management program 140 and registered in the job management table 180 (S1904). As a result, D200bP001 × D200e × D200f × D200g is registered in the field of the job execution requirement 180e of the order dependency information management table 170.

  This completes the data registration process when the system is changed.

  As described above, for example, when a job with job ID J001 is executed in the system after the change, as described with reference to FIG. 7, by inputting the ID (J001) of this job (S1401). The job management program 140 automatically generates the operation order of all management targets necessary for execution of this job, that is, the operation start order information (S1404), and the operation state management program 120 generates the operation start order information based on the operation start order information. Thus, each management target is operated sequentially. The operation order of the management target after the change is D200a, D200b, D200c, D200d, D200e, D200f, D200g, D200dP002, D200dP001, D200bP001.

  As described above, in this embodiment, even when there is a system change, information on a management target (for example, a management target ID) associated with the system change, and an operation target directly related to the operation of the management target If relations (for example, order-dependent target ID), change data of job execution requirements associated with a system change, and the like are input to the operation management apparatus 100, in other words, data of only the portion of the change portion associated with the system change If input to the operation management apparatus 100, the operation order of all management targets necessary for execution of each job is automatically generated, so that the burden on the system administrator or the like can be reduced.

It is explanatory drawing which shows the function block of the operation management apparatus in one Embodiment which concerns on this invention, and the structure of the system which an operation management apparatus manages. It is explanatory drawing which shows the structure of the configuration management table in one Embodiment which concerns on this invention. It is explanatory drawing which shows the structure of the operation state management table in one Embodiment which concerns on this invention. It is explanatory drawing which shows the structure of the order dependence information management table in one Embodiment which concerns on this invention. It is an operation start order dependence information figure in one embodiment concerning the present invention. It is explanatory drawing which shows the structure of the job management table in one Embodiment which concerns on this invention. It is a flowchart which shows operation | movement of the operation management apparatus at the time of starting operation of the job in one Embodiment which concerns on this invention. FIG. 14 is an operation start order dependency information diagram when J002 is designated as the job ID and D200e is designated as the management target ID in the embodiment according to the present invention. It is explanatory drawing which shows the operation start order dependence information table | surface when J002 is designated as job ID and D200e as management object ID in one Embodiment which concerns on this invention. It is a flowchart which shows the data registration process at the time of the system change in one Embodiment which concerns on this invention.

Explanation of symbols

  100: operation management device, 110: configuration management program, 120: operation state management program, 130: order dependency information management program, 140: job management program, 150: configuration management table, 160: operation state management table, 170: order dependency Information management table 180: Job management table 190: Data reception / registration program 200: Management target device

Claims (10)

In an operation management program for starting operation and / or ending operation according to a predetermined order for a plurality of devices and / or a plurality of management targets of a system including a program (hereinafter, management target) mounted on the devices,
A target identifier registration step for accepting a managed object identifier and storing the received identifier in a configuration management table storing the managed object identifier for each of a plurality of managed objects;
The order in which the order dependency information of the management target is received for each of the plurality of management target identifiers by receiving the order dependency information on the operation or stop of the other management target as a precondition for the start or end of the management target An order dependency information registration step for storing the received order dependency information of the management target in the dependency information table;
An operation target receiving step for receiving an identifier of a management target to be started or stopped among a plurality of management target identifiers stored in the configuration management table;
When the management target identifier is received in the operation target reception step, all the extracted management objects related to the operation start or operation end of the management target are extracted with reference to the order dependency information table. An order generation step for determining the order of the operation start or operation end of the management target;
An operation management program for causing a computer to execute. In the operation management program according to claim 1,
The job executed by the system and the identifier of the mandatory management target directly involved in the execution of the job are accepted as job execution requirements, and the job management table storing the job execution requirements of the job for each of a plurality of jobs, A job registration step for storing the received job and the job execution requirements of the job;
When receiving the execution of any one of the plurality of jobs stored in the job management table in the operation target reception step, all of the jobs essential for execution of the job are referred to with reference to the job management table. An operation target extraction step for extracting a management target identifier;
To the computer,
In the order generation step, with reference to the order dependency table, all the management objects related to the operation start or operation end of all the management objects extracted in the operation object extraction step are extracted and extracted. Define the order of operation start or operation end for all management targets.
An operation management program characterized by that. In an operation management program for starting operation and / or ending operation in accordance with a predetermined order, a plurality of devices and / or a system equipped with a program (hereinafter, management target) installed in the device,
The job executed by the system and the identifier of the mandatory management target directly involved in the execution of the job are accepted as job execution requirements, and the job management table storing the job execution requirements of the job for each of a plurality of jobs, A job registration step for storing the received job and the job execution requirements of the job;
The order in which the order dependency information of the management target is received for each of the plurality of management target identifiers by receiving the order dependency information on the operation or stop of the other management target as a precondition for the start or end of the management target An order dependency information registration step for storing the received order dependency information of the management target in the dependency information table;
An operation target receiving step for receiving any one of the plurality of jobs stored in the job management table;
When receiving the job in the operation target reception step, an operation target extraction step of extracting all management target identifiers essential for execution of the job with reference to the job management table;
Referring to the order dependency table, extracting all management objects related to the start or end of operation of all the management targets extracted in the operation target extraction step, and extracting all the management target operations An order generation step for determining the order of start or end of operation;
An operation management program for causing a computer to execute. In the operation management program according to any one of claims 1 to 3,
An operation command that receives an operation start command and an operation end command of a management target and stores the received command in an operation command management table in which the operation start command and operation end command of the management target are stored for each of a plurality of management targets Registration step;
When the operation start or operation end order of all the extracted management targets is determined in the order generation step, the operation command management table storing the operation start command and the operation end command for each of a plurality of management targets is stored. Referring to the operation processing step for sequentially starting or ending operation of a plurality of operation objects according to a predetermined order,
An operation management program executed by the computer. Operation management method for starting and / or ending operation of a plurality of devices and / or a plurality of management targets of a system having a program (hereinafter referred to as management target) mounted on the devices according to a predetermined order. In
In the storage area of the computer,
A configuration management table in which an identifier of the management target is stored for each of a plurality of management targets;
An order-dependent information table in which order-dependent information related to the operation or stop of another management target is stored for each identifier of the plurality of management targets, as a precondition for starting or stopping the operation of the management target;
Is set in advance,
A target identifier registration step of receiving a management target identifier and storing it in the configuration management table;
An order-dependent information registration step of receiving the order-dependent information of the management target in which the identifier is registered in the target-identifier registration step and storing it in the order-dependent information table;
An operation target receiving step for receiving an identifier of a management target to be started or stopped among a plurality of management target identifiers stored in the configuration management table;
When the management target identifier is received in the operation target reception step, all the extracted management objects related to the operation start or operation end of the management target are extracted with reference to the order dependency information table. An order generation step for determining the order of the operation start or operation end of the management target;
The operation management method characterized by causing the computer to execute. In an operation management method for starting and / or ending operation of a plurality of devices and / or a system provided with a program (hereinafter referred to as a management target) mounted on the devices according to a predetermined order by a computer ,
In the storage area of the computer,
A job management table in which job execution requirements are stored for each of a plurality of jobs, and an identifier of a mandatory management target directly involved in the execution of the job executed by the system;
An order-dependent information table in which order-dependent information related to the operation or stop of another management target is stored for each identifier of the plurality of management targets, as a precondition for starting or stopping the operation of the management target;
Is set in advance,
A job registration step of accepting a job executed by the system and a job execution requirement of the job and storing the job in the job management table;
Receiving an identifier of the management target and the order-dependent information of the management target, and storing it in the order-dependent information table;
An operation target receiving step for receiving any one of the plurality of jobs stored in the job management table;
When receiving the job in the operation target reception step, an operation target extraction step of extracting all management target identifiers essential for execution of the job with reference to the job management table;
Referring to the order dependency table, extracting all management objects related to the start or end of operation of all the management targets extracted in the operation target extraction step, and extracting all the management target operations An order generation step for determining the order of start or end of operation;
The operation management method characterized by causing the computer to execute. In the operation management method according to any one of claims 5 and 6,
In the storage area of the computer, an operation command management table in which operation start commands and operation end commands to be managed are stored for each of a plurality of management objects is set in advance,
An operation command registration step for receiving an operation start command and an operation end command to be managed and storing them in the operation command management table;
When the order of operation start or operation end of all the extracted management targets is determined in the order generation step, a plurality of operation targets are sequentially started in accordance with the determined order with reference to the operation command table. Or, the operation process step to end the operation
An operation management method comprising causing the computer to execute. In an operation management apparatus for starting and / or ending operation of a plurality of devices and / or a plurality of management targets of a system including a program (hereinafter, management target) mounted on the devices according to a predetermined order,
A configuration management table in which an identifier of the management target is stored for each of a plurality of management targets;
An order-dependent information table in which order-dependent information related to the operation or stop of another management target is stored for each identifier of the plurality of management targets, as a precondition for starting or stopping the operation of the management target;
A target identifier registration means for receiving a management target identifier and storing it in the configuration management table;
Order-dependent information registration means for receiving the order-dependent information of the management target in which the identifier is registered by the target identifier registration means, and storing it in the order-dependent information table;
Among the plurality of management target identifiers stored in the configuration management table, an operation target reception unit that receives a management target identifier that starts or ends operation;
When the operation target accepting unit receives the identifier of the management target, all the extracted management objects related to the operation start or operation end of the management target are extracted while referring to the order dependency information table. Order generation means for determining the order of the operation start or operation end of the management target;
An operation management device characterized by comprising: In an operation management apparatus for starting and / or ending operation of a plurality of devices and / or a system provided with a program (hereinafter, management target) installed in the devices according to a predetermined order,
A job management table in which job execution requirements are stored for each of a plurality of jobs, and an identifier of a mandatory management target directly involved in the execution of the job executed by the system;
An order-dependent information table in which order-dependent information related to the operation or stop of another management target is stored for each identifier of the plurality of management targets, as a precondition for starting or stopping the operation of the management target;
Job registration means for accepting a job to be executed by the system and job execution requirements for the job and storing the job in the job management table;
An order-dependent information registration unit that receives an identifier of a management target and order-dependent information of the management target, and stores the received order in the order-dependent information table;
An operation target receiving means for receiving any one of the plurality of jobs stored in the job management table;
When the operation target receiving unit receives the job, an operation target extraction unit that extracts all management target identifiers essential for the execution of the job with reference to the job management table;
Referring to the order dependency table, extracting all management objects related to the start or end of operation of all the management targets extracted in the operation target extraction step, and extracting all the management target operations Order generation means for determining the order of start or end of operation;
An operation management device characterized by comprising: In the operation management device according to any one of claims 8 and 9,
An operation command management table in which an operation start command and an operation end command of a management target are stored for each of a plurality of management targets;
An operation command registration means for receiving an operation start command and an operation end command to be managed and storing them in the operation command management table;
When the order of operation start or operation end of all the extracted management targets is determined in the order generation step, a plurality of operation targets are sequentially started in accordance with the determined order with reference to the operation command table. Or an operation processing means for terminating the operation;
Operation management device characterized by comprising

Images