JP2010224977A - Operation job integration management system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a management system that collectively manages operation of workflow systems which do not sufficiently provide commands or API (Application Programming Interface), and reduces time and effort of developing a result analysis program even when specifications of the workflow system are changed. <P>SOLUTION: An operation work integrated management system is arranged in a management server connected to a plurality of workflow systems via a network, and includes: an operation work integrated management main system 101 which has a template storage part 102 for storing a template 103 for recording a work flow, and an execution history storage part 106 for recording the execution history of the work flow; and a command execution program which is interposed between the workflow system and a target computer system thereof, operates the target computer system in response to a command from the workflow system, and records the execution history of the work flow into the execution history storage part of the operation work integration management main system. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an operation business integrated management system and program capable of collectively operating and managing different workflow systems of a plurality of workflow servers.

  2. Description of the Related Art Conventionally, a workflow system in a business processing computer system electronically stores, for example, an operation procedure for an operation task for operating a data center server system, and automatically operates a target computer system according to the operation procedure. By doing so, the operation work is facilitated. An example of such a workflow system is an operation business that automatically performs payroll calculation on a day designated by the company by a business processing computer system for a payroll server system of a company located in a data center. is there.

  And the business processing computer system that manages this workflow system tends to increase the number of services by providing a new service due to the invention of a new computer technology. It is a complicated and frequent operation. When the system is operated according to the customer's request, the operation work is required to shorten the time until the completion notification in response to the request from the customer and improve the quality of the provided service.

  In order to achieve these goals, the operation work of the operation work is performed manually by the operator by automating the operation work performed by the operator and dealing with the mixed environment of heterogeneous workflow systems used in the operation work. It is necessary to reduce the part. As a publicly known example, Japanese Patent Application Laid-Open No. 2004-178477 discloses a case where a workflow management system collects item data and execution history from each workflow system in order to collectively manage and manage different workflow systems without being aware of the difference. A system for controlling the disclosure of each other's information by acquiring and integrating the information is provided, whereby a method is disclosed in which a user acquires the necessary information simply by accessing the workflow management system.

JP 2004-178477 A

However, in the above-described workflow management system of Patent Document 1, in order to acquire workflow system information, a command or API (Application Programming Interface) for providing information necessary for operation work to the outside is provided. It was necessary to prepare for each workflow system.
And the result of the workflow system output when a command or API is used in the workflow management system is different for each workflow system. For this reason, if the command or API corresponding to the information to be acquired by the workflow management system is insufficient, the workflow management system has insufficient information. Had to be obtained directly from. Needless to say, this workflow management system cannot acquire information on a workflow system in which no command or API exists.

  Further, in this conventional method, a result analysis program is required to process the output result by the command or API and acquire necessary information. When a new workflow system is used, such as when a specification change occurs due to a workflow system version upgrade after the workflow management system is operated, the result analysis program is newly developed to cope with the change. There was a need.

  As described above, the conventional technology requires that the information acquired by the workflow management system be provided with a plurality of conditions and commands and APIs that can be sufficiently provided by the workflow system. It became feasible to manage the operation.

  Therefore, there is a need for a management system that can collectively manage and manage a plurality of different types of workflow systems without using commands or APIs.

  The present invention has been made in view of such circumstances, and a first object of the present invention is to collect a workflow system that does not sufficiently provide commands and APIs to the outside, and different workflow systems. It is to provide an operation business integrated management system and program that can be operated and managed in the future.

  A second object of the present invention is to provide an operation business integrated management system and program that can reduce the time and effort to newly develop a result analysis program when a specification change occurs due to a workflow system version upgrade. .

  As a result of diligent research in view of the above-mentioned problems, the present inventors have arranged an operation business integrated management server that collectively manages and manages workflow systems, and executed commands on each workflow server where the workflow system is installed. I came up with the program.

  That is, the present invention is an operation business integrated management system that collectively manages the workflow systems of a plurality of workflow servers, and is disposed in a management server connected to the plurality of workflow servers via a network. An operation work integrated management means comprising a computer comprising a template storage section for storing a template made up of a file in which operation procedures of the operation work are registered, and an execution history storage section for registering information on the execution history of the operation work, It is arranged between the workflow system and the target computer system of the workflow system in the workflow server, and operates the computer system according to the operation procedure registered in the template. Command execution means for registering the executed history information in the execution history storage unit, and the command execution means sends the operation procedure information of the operation work of the workflow system to which the command execution means is input to the operation work integrated management means. In addition, an operation business integrated management system for operating and executing the operation target computer system and registering information of the operated execution history in the execution history storage unit is provided.

  In the operation business integrated management system of the present invention, the command execution means includes information about the start of the operation business before the first execution history of the operation procedure actually performed in the operation business registered in the template, and the operation business. In this case, after the last execution history of the operation procedure actually performed, information on the end of the operation task is registered in the execution history storage unit.

  As a result, the start and end of execution history of various operation tasks by using a plurality of templates, and the result information are registered in the execution history storage unit without any difference in the workflow system, and without using commands or APIs. It can be grasped in the operation business integrated management system.

  In the operation business integrated management system according to the present invention, the template includes a command definition file describing the command for operating the operation target computer system to be read and used by the command execution means in place of the workflow system, It is characterized by comprising a flow definition file that can be interpreted by the workflow system describing the flow.

  As a result, instead of the workflow system, the command execution means reads the command and flow of the command definition file and operates the computer system to be operated.

  In the operation business integrated management system according to the present invention, the template includes a parameter file that is read and used by a command execution unit.

  Thereby, it is possible to give a degree of freedom by using a part of the operation of the operation work as a parameter.

  The operation business integrated management program according to the present invention is an operation business integrated management program that collectively manages the workflow systems of a plurality of workflow servers, and is disposed on a management server connected to the plurality of workflow servers via a network. Integrated operation management management comprising a computer comprising a template storage unit for storing a template consisting of a file in which the operation procedure of the operation task of the workflow system is registered, and an execution history storage unit for registering execution history information of the operation task Means and the workflow system in the workflow server between the workflow system and the computer system to be operated by the workflow system, and the operation procedure registered in the template Command execution means for operating the computer system and registering the information of the operated execution history in the execution history storage unit, and the operation procedure information of the operation work of the workflow system to which the command execution means is input. In the operation business integrated management program for sending to the operation business integrated management means, operating and executing the computer system to be operated, and registering information of the operated execution history in the execution history storage unit, the plurality of workflow servers and An operation business integrated management means arranged in a management server connected via a network stores a template in which the operation procedure of the operation business of the workflow system is registered in a template storage unit; A step of registering an execution history of an operation task in an execution history storage unit, and an operation registered in the template by a command execution program arranged between the plurality of workflow systems and a target computer system of the workflow system. The step of operating the computer system according to the procedure, registering the operated execution history in the execution history storage unit, and the operation procedure information of the operation task of the workflow system inputted by the command execution means are integrated into the operation task A step of sending to the management means; and a step of operating the computer system to be operated and registering information of the operated execution history in the execution history storage unit.

  In the operation work integrated management program of the present invention, the command execution means includes information on the start of the operation work before the first execution history of the operation procedure actually performed in the operation work registered in the template, and the operation work. In this case, after the last execution history of the operation procedure actually performed, information on the end of the operation task is registered in the execution history storage unit.

According to the operation business integrated management system and program of the present invention,
(1) By placing the operation business integrated management main system on the management server connected to the workflow server via the network, the workflow of the operation business integrated management system can be used without using the commands and API provided by the workflow system. It becomes possible to grasp the information of the execution history, and it becomes possible to manage and manage a plurality of workflow systems collectively.
(2) Since the information of the execution history of the workflow system can be grasped from the function of the operation business integrated management system independently of the function of the workflow system, the result required to acquire the information necessary for the conventional operation work The analysis program is no longer required, and the result analysis program creation man-hours can be reduced even if the specifications are changed due to the version upgrade of the workflow system.

1 is an overall configuration diagram of a computer system to which an operation business integrated management system according to an embodiment of the present invention is applied. It is a figure which shows the screen of the high-order application of this invention. It is a figure explaining preparation of a template from the operation procedure of the operation work of the present invention. It is a data flow figure which shows the flow of the information which the business flow registered into the workflow system transmits with respect to the operation business integrated management system of this invention. It is a flowchart of the instance registration part and instantiation of this invention. It is a flowchart of the instance start registration part of this invention. It is a flowchart of the instance completion registration part of this invention. It is a flowchart of the instance detail start registration part of this invention. It is a flowchart of the instance detailed end registration part of this invention. It is a flowchart of the instance information acquisition part of this invention. It is a flowchart of the command execution part of this invention. It is a flowchart of the instance start registration command part of this invention. It is a flowchart of the instance termination registration command part of this invention. It is a flowchart of the instance detail start registration part of this invention. It is a flowchart of the instance detailed end registration part of this invention. It is a figure explaining the table stored in the execution history storage part of this invention. It is a figure explaining the table stored in the template management part of this invention. It is a figure which shows the table stored in the execution log | history storage part of this invention. It is a figure which shows the table stored in the template management part of this invention.

  Hereinafter, an embodiment for implementing an operation business integrated management system of the present invention will be described in detail with reference to the drawings. 1 to 19 are diagrams illustrating embodiments of the present invention. In these drawings, the same reference numerals denote the same components, and the basic configuration and operation are the same. To do.

<Overall configuration>
FIG. 1 is an overall configuration diagram of a computer system to which an operation business integrated management system of the present invention is applied.
This computer system includes an upper-level application 2 in which an operation SE1 who is an operation manager of the entire computer system selects a business flow, an operation target computer system, and the like, and operation / operation integrated management connected to the upper-level application 2 via a network. A server 100, an operation business integrated management system 101 arranged in the operation business integrated management server 100, and a plurality (two in this embodiment) of workflow servers 120 connected to the operation business integrated management server 100 via a network, 130, the workflow system A121 arranged in the workflow server 120, the workflow system A121, the operation target computer system A140, and the operation target computer system. The command execution program 122 of the present invention interposed between B141, the workflow system B131 disposed in the workflow server 130, and the command execution program 132 of the present invention interposed between the workflow system B131 and the operation target computer system C142. Composed.

  The operation business integrated management system of this embodiment operates and manages a plurality of workflow systems whose operation targets are server systems such as data centers, and integrates the operation procedures of the operation business of the workflow system. It is registered in the template of the management system, and the operation business integrated management system operates and executes the operation target computer system based on the operation procedure, and the operation business execution history information is registered in the operation business integrated management system. .

  In FIG. 1, the dark colored portion represents the operation business integrated management system of the present invention, and the operation business integrated management system is arranged in the operation business integrated management server 100 connected to the workflow system A 121 and the workflow system B 131 via the network. The operation business integrated management main system 101 composed of computers, the workflow system A 121 of the workflow server 120, the command execution program 122 interposed between the operation target computer system A 140 and the operation target computer system B 141, and the workflow system B 131 of the workflow server 130. And the command execution program 132 interposed between the computer system C142 and the operation target computer system C142.

  Note that the number and type of workflow servers 120 and 130 connected to the operation / operation integrated management main system 101 vary depending on the operation mode, and the number of command execution programs 122 and 132 increases or decreases accordingly.

  The host application 2 uses each function using an interface provided by the operation business integrated management main system 101. As an example of the host application 2, there is a web application that selects a transmission request by the operation SE1 on the display screen shown in FIG. 2 and inputs and transmits necessary information.

  In the display screen of the upper application 2 in FIG. 2, the function of the instance registration unit 108 of the operation / work integrated management main system 101 is selected by the request input unit 201. The business flow selection unit 202 selects the business A as the business flow. In addition, information necessary for operation work in the data center name column 203, resource name column 204, virtual machine name column 205, and access authority column 206 of the parameter list for inputting parameters (for example, data center 1, resource A, virtual machine) D, access authority C) is input, and the workflow system selection unit 207 selects the workflow system A 121 as the workflow system for performing the operation. Thereafter, when the operation SE1 clicks the send button 208, the operation work integrated management main system 101 registers in the workflow system A121.

<Operation business integrated management main system 101>
The operation business integrated management main system 101 includes a package template storage unit 102 for storing a template 103 having a command file for executing an operation business selected from the upper application 2 by the operation SE1, and a flow definition file of the template 103 as a workflow system. An assembly file storage unit 104 for storing the assembly file 105 to be registered in the application, an execution history storage unit 106 for registering the result of operating the operation target computer system according to the work flow, a template management unit 107 for managing the template 103, An instance registration unit 108 for registering the flow definition file in the workflow system based on the contents input to the application 2, and the workflow system An instance start registration unit 109 for registering in the execution history storage unit 106 that the line has started, and an instance end registration for registering in the execution history storage unit 106 the end of the execution of the business flow and the result of the business flow in the workflow system Unit 110, an instance detail start registration unit 111 for registering in the execution history storage unit 106 the completion of the execution of the business flow in the workflow system and the result of the business flow, and the process system of the workflow in the workflow system The instance details end registration unit 112 that registers the completion of the operation execution to the execution history storage unit 106 and the status of the instances of all workflow systems based on the contents received from the upper application 2 are searched. , Search result in upper application 2 And an instance information acquisition unit 113 to provide.

The following (1) to (10) of the operation business integrated management main system 101 will be described in detail below.
(1) Package template storage unit 102
(2) Template 103
(3) Instance registration unit 108
(4) Instance start registration unit 109
(5) Instance termination registration unit 110
(6) Instance details start registration unit 111
(7) Instance details end registration unit 112
(8) Instance information acquisition unit 113
(9) Execution history storage unit 106
(10) Template management unit 107

(1) Package template storage unit 102
As shown in FIG. 1, the package template storage unit 102 stores a plurality of templates 103 corresponding to the number of operation tasks performed by the operation task integrated management main system 101. The plurality of stored templates 103 are selected from the upper application 2.

(2) Template 103
The template 103 includes a command definition file 302, a parameter file 303, and a flow definition file 304. FIG. 3 shows an example of creating the template 103 from the operation procedure of the operation task 301. The operation task 301 (operation procedure 1 to operation procedure 4) of the actual workflow system A 121 shown on the left side of FIG. It is described in the template 103 by dividing it into three files: a definition file 302, a parameter file 303, and a flow definition file 304. Among these, the parameter file 303 is for giving a degree of freedom as a selectable parameter for a part of the command. In addition, if a file other than these three files is required for operation operations, that file is also handled as a configuration file of the template 103. After preparing the files configuring these templates 103 and registering them in the template management unit 107, the configuration files are stored in the package template storage unit 102, whereby the template 103 is selected from the upper application 2 and executes the operation task. It becomes possible.

Next, each file will be described.
Command definition file 302
The command definition file 302 is a file that is read and used by the command execution program 122. As shown in FIG. 3, each operation performed on behalf of the workflow system A 121 (for example, command 1 resource pool creation command definition, command 2 virtual This is a file describing machine creation command definitions, command 3 access authority setting command definitions, command 4 environment information acquisition command definitions). In the description of the operation, by defining a part as a parameter, it is possible to deal with many similar business flows with one command.

Parameter file 303
The parameter file 303 is a file that is read and used by the command execution program 122. As shown in FIG. 3, the parameter values described in the command definition file 302 (for example, parameter 1 resource pool name A, parameter 2 virtual machine name) B, parameter 3 is a file describing access authority C). One or more parameters can be defined, and the value is updated by the instance registration unit 108 in FIG. The update method is a method in which the value in the parameter file is updated to the value input by the operation SE1, and the value not input is not updated.

-Flow definition file 304
The flow definition file 304 is a file that can be interpreted by the workflow system. As shown in FIG. 3, the flow of operation work actually used (for example, the flow 1 resource pool creation command call, the flow 2 virtual machine creation command call, , Flow 3 access authority setting command call, flow 4 environment information acquisition command call). Since the flow definition file 304 is described in a method unique to the workflow system, it is possible to select an operation target computer system and a workflow system having a function specialized for operation execution.

  FIG. 4 is a diagram showing a flow of information transmitted by the business flow registered in the workflow system to the operation business integrated management system and information registered in the execution history storage unit 106. When the workflow of the workflow system A 121 is set as a start process 501, a process 502, a process 503, and a normal end process 504, these workflow processes input a command name to the command execution program 122. The flow definition file 304 is described as much as possible, and the flow of the information is transmitted to the operation business integrated management system. The information flow will be described in detail below.

<Starting process 501>
First, in the first start process 501 of the business flow, the flow definition file 304 is described so that the workflow system A 121 inputs the instance identifier and the instance start registration command to the instance start registration command unit 124 of the command execution program 122.
Further, the command execution program 122 registers the instance information 505 (instance identifier) input to the instance start registration command unit 124 in the instance start registration unit 109 of the operation business integration management main system 101 of the operation business integration management server 100.
Then, the operation business integrated management main system 101 registers the instance information (the instance identifier, the execution status that the workflow has entered execution, and the status start date and time) from the instance start registration unit 109 in the execution history storage unit 106. To do.

<Process 502>
Next, in the second process 502 of the business flow, the flow definition file 304 is described so that the workflow system A 121 inputs the instance information (instance identifier and command name) to the command execution unit 123 of the command execution program 122.
Further, the command execution unit 123 of the command execution program 122 operates the operation target computer system A 140 with the instance information 506 (command line describing an instance identifier, a command name, and specific operation contents), and this instance information. 506 is registered in the instance detail start registration unit 111 of the operation / operation integrated management main system 101.
Then, the operation business integrated management main system 101 receives the instance information from the instance detail start registration unit 111 (instance identifier, command name, command line, execution status executed by the process 502, and the start date and time of this status). Is registered in the execution history storage unit 106.

<Process 503>
Next, in the business flow process 503, the flow definition file 304 is described so that the workflow system A 121 causes the command execution unit 123 of the command execution program 122 to input the instance information (instance identifier and command name).
Further, the command execution unit 123 of the command execution program 122 receives instance information 507 (instance identifier, instance detail identifier, process activation success code indicating whether the process 503 has been completed successfully or failed, The operation target computer system B 141 is operated with the instance detail result code), and the instance information 506 is registered in the instance detail end registration unit 112 of the operation work integrated management main system 101.
Then, the operation business integrated management main system 101 receives the instance information (instance identifier, instance detail identifier, process activation success code, instance detail result code, and termination when this process 503 is terminated) from the instance detail termination registration unit 112. The status and the end date / time of the status) are registered in the execution history storage unit 106.

<Normal end process 504>
Finally, in the normal end process 504, the flow definition file 304 is described so that the workflow system A 121 causes the instance information (instance identifier and instance end registration command) to be input to the instance end registration command unit 125 of the command execution program 122.
Further, the command execution program 122 uses the instance information 508 (the instance identifier and the instance result code indicating whether the workflow is successful or unsuccessful) from the instance start registration command unit 124 as the instance end registration unit 110 of the operation / operation integrated management main system 101. Register with.
Then, the operation / work integrated management main system 101 registers the instance information (instance identifier, instance result code, end status, and end date / time of the end of the task) from the instance end registration unit 110 in the execution history storage unit 106. .

  As described above, by registering the operation history of the business flow in the execution history storage unit 106, the operation business integrated management main system 101 indicates which process is currently being executed from the start to the end of the business flow. The operation history registered in the execution history storage unit 106 can be grasped by the operation business integrated management main system 101 without depending on the workflow system. Therefore, according to the operation business integrated management system of the present invention, it is possible to grasp the execution status of the process of the business flow even when a specification change occurs due to the version upgrade of the workflow system. No new development is required.

  Further, the number of templates 103 stored in the package template storage unit 102 may be increased or decreased in accordance with the number of operation tasks performed in the operation task integrated management main system 101.

(3) Instance registration unit 108
The instance registration unit 108 in FIG. 1 is means for registering the flow definition file 304 in FIG. 3 in the workflow system A 121 based on the contents input from the upper application 2, and the instance is a template materialized.

  The flowchart shown on the left side of FIG. 5 is a step 401 in which the upper application 2 of FIG. 1 transmits the template name and workflow system name registered in the template management unit 107 and the value of the parameter to be changed used in the template; The instance registration unit 108 instantiates the specified template 103 as an object having a specific parameter value and adapts it to the actual business, and the instance registration unit 108 instantiates the operation business, Step 403 for registering the identifier, template identifier, registration status, and workflow system identifier in the execution history storage unit 106, and the assembly file name and workflow system class in the template management unit 107 Using the assembly file 105 in the assembly file storage unit 104 and registering the flow definition file 304 in the workflow system from the name and step 405 transmitting the instance identifier and the registration result to the upper application 2. This shows the procedure.

  The flowchart on the right side of FIG. 5 shows a specific procedure of instantiation in step 402, step 406 for assigning an instance identifier, and copying a template folder as a folder before instance work, and a folder before instance work. Step 407 for updating each file, step 408 for writing the instance identifier in the flow definition file 304, step 409 for determining whether the flow definition file 304 has parameter information, and parameter information if there is parameter information. This shows a procedure including a step 410 for changing the saved parameter value to the parameter value set by the upper application 2 in the file.

  According to this flowchart, the instance registration unit 108 registers the flow definition file 304 in the workflow system A 121 based on the contents input from the upper application 2.

(4) Instance start registration unit 109
FIG. 6 is a flowchart showing the processing operation of the instance start registration unit 109 in FIGS. 1 and 4. The instance start registration unit 109 is a unit that registers in the execution history storage unit 106 that the execution of a business flow has started in the workflow system.

  This flow includes step 411 for receiving the instance start registration information 505 of FIG. 4 including the instance identifier transmitted from the instance start registration command unit 124 of the command execution program 122, and the received instance identifier in the execution history storage unit 106. A procedure comprising a step 412 for changing the start time and status of each to the current date and execution status, and a step 413 for transmitting the result performed by the instance start registration unit 109 to the command execution program 122. It is shown.

  Through this flow, the instance start registration unit 109 registers in the execution history storage unit 106 that the execution of the business flow has started in the workflow system.

(5) Instance end registration unit 110
FIG. 7 is a flowchart showing the processing operation of the instance end registration unit 110 in FIGS. 1 and 4. The instance end registration unit 110 is a means for registering in the execution history storage unit 106 the end of execution of a business flow in the workflow system and the result of the business flow.

  This flow is received in the execution history storage unit 106 in step 421 for receiving the instance termination information 508 of FIG. 6 including the instance identifier and the instance result code transmitted from the instance termination registration command unit 125 of the command execution program 122. The step 422 for changing the end time, status, and instance result code of the instance identifier to a code representing the current date, end status, success or failure, respectively, and the result executed in the instance end registration to the command execution program 122 The procedure comprised from step 423 which transmits to is shown. (The instance result code is a code indicating whether or not the instantiated business has been normally performed, and success or failure is input as a value.)

  Through this flow, the instance end registration unit 110 registers the completion of the execution of the business flow in the workflow system and the result of the business flow in the execution history storage unit 106.

(6) Instance details start registration unit 111
FIG. 8 is a flowchart showing the processing operation of the instance detail start registration unit 111 in FIGS. 1 and 4. The instance detail start registration unit 111 is a unit for registering in the execution history storage unit 106 that a business flow process starts operation execution in the operation target computer system in the workflow system.

  This flow receives the instance detail start registration information 506 of FIG. 6 including the instance identifier, the command name, and the command line described in the command definition file transmitted from the instance detail start registration command unit 126 of the command execution program 122. Step 431; Step 432 for registering the instance detail identifier, the instance identifier, the command name, the command line, the start time, and the execution status in the instance detail information table of the execution history storage unit 106 in FIG. 16; and the instance detail identifier and the instance details. This shows a procedure composed of Step 433 for transmitting the result of the start registration to the command execution program 122.

  By this flow, the instance detail start registration unit 111 starts the execution of the operation of the business flow process in the operation target computer system in the workflow system.

(7) Instance details end registration unit 112
FIG. 9 is a flowchart showing the processing operation of the instance detail end registration unit 112 in FIGS. 1 and 4. The instance detail end registration unit 112 is a means for registering in the execution history storage unit 106 the completion of operation execution on the operation target computer system and the end result of the business flow process in the workflow system.

  This flow is the instance detail end registration information 507 (process activation success code, instance detail identifier, instance identifier, and instance detail result code) of FIG. 4 transmitted from the instance detail end registration command part 127 of the command execution program 122. 441, the end time and status of the received instance detail identifier stored in the execution history storage unit 106, the process activation success code, and the instance detail result code, respectively, the current date and end status and success or The procedure includes a step 442 for changing to failure and a result code, and a step 443 for transmitting the result performed in the instance detail end registration 112 to the command execution program 122. (The process startup success code is a code indicating whether the operation described in the command definition file has been successfully called, and success or failure is entered as a value. The instance detail result code is the executed operation. In the code that represents the result of, a numeric value is entered as a value.)

  According to this flow, the instance detail end registration unit 112 registers in the execution history storage unit 106 the completion of operation execution on the operation target computer system and the end result of the workflow process in the workflow system.

(8) Instance information acquisition unit 113
FIG. 10 is a flowchart showing the processing operation of the instance information acquisition unit 113 in FIG. The instance information acquisition unit 113 is a means for searching for the status of the instances of all workflow systems based on the content received from the higher-level application 2 and providing the search result to the higher-level application 2.

  The flow shown in FIG. 10 includes a step 451 in which the higher-level application 2 transmits, as a search expression, the condition of the instance information that the execution history storage unit 106 wants to check, and a search expression received by the instance information acquisition unit 113 as an SQL statement (relational database Step 452 to be replaced with (language for operation), Step 453 for executing the SQL statement to search the corresponding record in the execution history storage unit 106, Step 454 for transmitting the execution result of the SQL statement to the upper application 2 The procedure which consists of is shown.

  Through this flow, the instance information acquisition unit 113 searches the status of the instances of all workflow systems based on the content received from the upper application 2 and provides the search result to the upper application 2.

(9) Execution history storage unit 106
FIG. 16 shows an instance information table and an instance detailed information table of the execution history storage unit 106. The execution history storage unit 106 is a database that registers the operation results of the operation target computer system according to the business flow. FIG. 18 shows an instance detailed information data table and an instance detailed information data table of the execution history storage unit 106.

  In the instance information table 16-1, for example, “# 3” stores “workflow system identifier” as an explanation of “workflow_system_id”, and in the instance detailed information table 16-2, for example, “# 4” includes “command_line”. “Execution command line” is stored as an explanation.

  In the instance detailed information data table 16-3 of FIG. 18, for example, in “# 1”, “1” is stored in the “instance_id” column, “1” is stored in the “template_id” column, “1” is stored in the “workflow_system_id” column, “End” in the “instance_status” column, “2009/01/10 11: 39: 00.000” in the “begin_datetime” column, and “2009/01/10 11: 39: 40.123” in the “end_datetime” column And “normal” is stored in the “result_code” column.

  Similarly, in the instance detailed information data table 16-4, for example, “# 2” has “2” in the “instance_id” column, “2” in the “instance_detail_id” column, “Create Resource Pool” in the “command_name” column, “ResourcePool-C Create” in the “command_line” field, “End” in the “instance_detail_status” field, “2009/01/10 11: 39: 08.234” in the “begin_datetime” field, and “end_datetime” in the “end_datetime” field "2009/01/10 11: 39: 31.345", "0" is stored in the "boot_success_code" field, and "0" is stored in the "result_code" field

(10) Template management unit 107
FIG. 17 shows a template information table, a workflow system information table, and a workflow system information table of the template management unit 107. The template management unit 107 is means for managing the template 103. FIG. 19 shows a template information data table, a workflow system class information table, and a workflow system information table of the template management unit 107.

  In the template information table 17-1 of FIG. 17, “template name” is stored as an explanation of “template_name” in “# 2”, for example, and “# 3” in “# 3” is stored in “# 3”, for example. “Status” is stored as the description of “workflow_system_class_status”, and “workflow system name” is stored as the description of “workflow_system_name” in “# 3”, for example, in the workflow system information table 17-3.

  In the template information data table 17-4 of FIG. 19, for example, in “# 2”, “1” is stored in the “template_id” column, “operation A” is stored in the “template_name” column, and “1” is stored in the “workflow_system_class_id” column. Saved.

  In the workflow system class information table 17-5 of FIG. 19, for example, in “# 1”, “1” is in the “workflow_system_id” column, “1” is in the “workflow_system_class_id” column, and “workflow system A1” is in the “workflow_system_name” column. And “executable” is stored in the “workflow_system_status” column.

  In the workflow system information table 17-6 of FIG. 19, for example, in “# 4”, “4” is stored in the “workflow_system_class_id” column, “Workflow_system_class_name” is “WorkflowD. And “WorkFlowD” is stored in the “assembly_file_name” column.

<Configuration of Command Execution Program 122>
The command execution program 122 includes a command execution unit 123 that causes the operation target computer system A140 and the operation target computer system B141 to execute a command, an instance start registration command unit 124 that sends data to the instance start registration unit 109, and the instance end registration An instance end registration command unit 125 for sending data to the unit 110, an instance detail start registration command unit 126 that operates when a command other than start and end is input, and a command other than start and end And an instance detail end registration command part 127 that operates.

<Command execution program 122>
The following (1) to (5) of the command execution program 122 will be described in detail below.
(1) Command execution unit 123
(2) Instance start registration command part 124
(3) Instance termination registration command part 125
(4) Instance details start registration command part 126
(5) Instance details end registration command part 127

(1) Command execution unit 123
FIG. 11 is a flowchart showing the processing operation of the command execution unit 123 in FIGS. 1 and 4. The command execution unit 123 is a unit that operates first when the command execution program 122 is executed.

  This flow includes a step 461 in which the workflow system A 121 inputs an instance identifier and a command name, a step 462 in which the command execution unit 123 reads a command definition file in the post-instance work folder, and a command execution unit 123 operates in the computer system to be operated. Step 463 for processing the instance detailed start registration command unit 126 before executing the operation, and after the detailed start registration command unit 126 ends, the command is executed according to the command definition file, and the execution result is written to the result file. The procedure includes a step 464 for obtaining a startup success code and an instance detail result code, and a step 465 for processing the instance detail end registration command part 127.

(2) Instance start registration command part 124
FIG. 12 is a flowchart showing the processing operation of the instance start registration command unit 124 in FIGS. 1 and 4. The instance start registration command unit 124 is a means that operates when the command execution program 122 receives an instance start registration command.

  This flow includes a step 471 in which an instance start registration command and an instance identifier are input from the workflow system A 121, a step 472 in which the input instance identifier is transmitted to the operation business integrated management main system 101, and an operation business integrated management main system. 1 and FIG. 4, the instance start registration command unit 124 receives the registration result in step 473, and after receiving the result, the pre-instance work folder in the operation business integrated management main system 101 Step 474 for obtaining a file, Step 475 for creating a folder after instance work, Step for creating a log file in the folder after instance work, and writing the processing results so far It shows the procedure consists flop 476 Metropolitan.

(3) Instance termination registration command part 125
FIG. 13 is a flowchart showing the processing operation of the instance end registration command unit 125 in FIGS. 1 and 4. The instance end registration command unit 125 is a means that operates when the command execution program 122 receives an instance end registration command.

  This flow includes a step 481 in which an instance end registration command and an instance identifier are input from the workflow system A 121, a step 482 in which the input instance identifier and instance result code are written in a log file, and an instance identifier and instance result code. Step 483 for transmitting to the operation / work integrated management main system 101, and processing performed by the instance end registration unit 110 in FIGS. 1 and 4 in the operation / work integrated management main system 101, and the instance end registration command unit 125 receiving the registration result A procedure including 484 and a step 485 for transmitting the post-instance work folder to the operation work integrated management main system 101 is shown.

(4) Instance details start registration command part 126
FIG. 14 is a flowchart showing the processing operation of the instance detail start registration command unit 126 in FIG. The instance detail start registration command unit 126 in FIG. 1 is a means that operates when the command execution program 122 receives a command other than the instance start registration command and the instance end registration command.

  This flow is called from the command execution unit 123 and transmits an instance identifier, a command name, and a command line to the operation / operation integrated management main system 101. In the operation / operation integrated management main system 101, the flow shown in FIGS. Processed by the instance detail start registration unit 111, the instance detail start registration command unit 126 shows a procedure comprising a step 492 for receiving a registration result and a step 493 for writing the contents of the result to a log file. (The result of registration includes an instance detailed identifier, which becomes an identifier of an operation to be performed from now on.)

(5) Instance details end registration command part 127
FIG. 15 is a flowchart showing the processing operation of the instance detail end registration command unit 127 in FIG. The instance detail end registration command unit 127 in FIG. 1 is a means that operates when the command execution program 122 receives a command other than the instance start registration command and the instance end registration command.

  This flow is called from the command execution unit 123 and transmits an instance identifier, an instance detail identifier, a process activation success code, and an instance detail result code to the operation / operation integrated management main system 101, and an operation / operation integrated management main system. 101 is processed by the instance detail end registration unit 112 in FIG. 1 and FIG. 4, and the instance detail end registration command unit 127 includes a step 497 for receiving the registration result and a step 498 for writing the result contents to the log file. Is shown.

<Flow of workflow system registration>
With reference to FIG. 1, the flow of processing when the operation SE1 that performs the operation business of the business processing computer system registers the operation business will be described.

  First, in the operation business integrated management main system 101, the instance registration unit 108 registers a business flow from the workflow system A 121 and the workflow system B 131 based on the information transmitted by the upper application 2 operated by the operation SE1. Hereinafter, the description will be continued assuming that the registration is performed in the workflow system A121.

  Next, the workflow system A 121 uses the command execution program 122 to execute the registered business flow on the operation target computer system A 140 and the operation target computer system B 141. At this time, the command execution program 122 uses the functions of the instance start registration command unit 124, the instance end registration command unit 125, the instance detail start registration command unit 126, and the instance detail end registration command unit 127. Necessary information is transmitted to the instance start registration unit 109, the instance end registration unit 110, the instance detail start registration unit 111, and the instance detail end registration unit 112 of the system 101.

  As described above, since the operation business integrated management main system 101 and the command execution program 122 are arranged before and after the workflow system A121, it is possible to grasp the input / output of the workflow system A121. Further, in order to grasp the execution status without using a command or API provided to the outside, the operation SE1 can execute the execution history only from the operation / operation integrated management main system 101 without being aware of the difference in the used workflow system. Information can be obtained.

  As described above with reference to FIGS. 1 to 19, in the operation work integrated management system of this embodiment, the execution history of the operation work integrated management main system 101 at the beginning and end of the work flow described in the flow definition file. A command for performing registration is added to the storage unit 106.

  Then, when the workflow system inputs a command to the command execution program, the execution history of the operation work is obtained in the execution history storage unit of the operation work integrated management system. With this description method and program, the execution status of operation work can be grasped without using commands and APIs provided by the workflow system. Can also be managed.

  As shown in FIG. 1, the operation business integrated management system of the present invention includes an OS, an application, a database, and a network system constructed on hardware resources including a computer CPU, memory, auxiliary storage device, display, input device and the like. Since the information processing called operation management integrated management is specifically realized using the above hardware resources, it falls under the technical idea using the laws of nature. In addition, it can be used for an outsourcing service for performing an operation work in a shared use type data sensor equipped with a plurality of different workflow systems for operating a business processing computer system of a plurality of customers.

1 Operational SE
2 upper application 101 operation business integrated management main system 102 package template storage unit 103 template 106 execution history storage unit 106-1 instance information table 106-2 instance detailed information table 106-3 instance information data table 106-4 instance detailed information data table 107 Template management unit 108 Instance registration unit 109 Instance start registration unit 110 Instance end registration unit 111 Instance details start registration unit 112 Instance details end registration unit 113 Instance information acquisition unit 120 Workflow server 121 Workflow system A
122 command execution program 123 command execution unit 124 instance start registration command unit 125 instance end registration command unit 126 instance detail start registration command unit 127 instance detail end registration command unit 130 workflow server 131 workflow system B
132 Command Execution Program 140 Target Computer System A
141 Target computer system B
142 Target computer system C
301 Operation Task 302 Command Definition File 303 Parameter File 304 Flow Definition File 501 Start Process 502 Process 503 Process 504 Normal End Process

Claims (6)

An operation business integrated management system that collectively manages the workflow systems of multiple workflow servers.
A template storage unit that is arranged in a management server that is connected to the plurality of workflow servers via a network and stores a template that registers the operation procedure of the operation task of the workflow system; and information on the execution history of the operation task An operation business integrated management means comprising a computer comprising an execution history storage unit for registering,
It is arranged between the workflow system and the target computer system of the workflow system in the workflow server, operates the computer system according to an operation procedure registered in the template, and executes the information of the operated execution history. Command execution means for registering in the history storage unit,
The command execution means inputs the operation procedure information of the operation task of the workflow system to the operation task integration management means, and the operation target computer system is operated and executed. An operation operation integrated management system characterized by being registered in an execution history storage unit.   The command execution means includes information on the start of the operation procedure before the first execution history of the operation procedure actually performed in the operation task registered in the template, and the last execution of the operation procedure actually performed in the operation task. 2. The operation business integrated management system according to claim 1, wherein information about the end of the operation business is registered in the execution history storage unit after the history.   The template can be interpreted by the workflow system that describes the command for operating the computer system to be operated and read by the command execution program in place of the workflow system, and the flow of operation work. The operation business integrated management system according to claim 1, further comprising a simple flow definition file.   The operation business integrated management system according to claim 1, wherein the template includes a parameter file that is read and used by command execution means. An operation business integrated management program for collectively managing the workflow systems of a plurality of workflow servers, which is arranged on a management server connected to the plurality of workflow servers via a network, and for operating operations of the workflow system An operation work integrated management means comprising a computer comprising a template storage section for storing a template made up of files registered with an execution history storage section for registering information on the execution history of the operation work, and the workflow within the workflow server. The system is arranged between the system and the computer system to be operated by the workflow system, operates the computer system according to the operation procedure registered in the template, and stores information on the operation history of the operation. Command execution means for registering in the execution history storage unit, the command execution means sends the operation procedure information of the operation work of the workflow system to which the command execution means has been input to the operation work integrated management means, and the operation target In the operation business integrated management program for operating and executing the computer system and registering the information of the operated execution history in the execution history storage unit,
A step of storing, in a template storage unit, a template in which an operation work integrated management unit arranged in a management server connected to the plurality of workflow servers via a network registers a command and a flow that are operation procedures of the operation work of the workflow system; When,
The operation business integrated management means registering an operation business execution history in an execution history storage unit;
A command execution program arranged between the plurality of workflow systems and a computer system to be operated by the workflow system operates the computer system according to an operation procedure registered in the template, and the operation execution history is recorded as the execution history. Registering in the storage unit;
Sending the operation procedure information of the operation work of the workflow system to which the command execution means is input to the operation work integrated management means;
Operating the computer system to be operated, and registering information of the operated execution history in the execution history storage unit;
Operation business integrated management program characterized by causing   The command execution means provides information on the start of the operation procedure before the first execution history of the operation procedure actually performed in the operation task registered in the template, and the last execution of the operation procedure actually performed in the operation task. 6. The operation work integrated management program according to claim 5, wherein information about the end of the operation work is registered in the execution history storage unit after the history.