JP2015207059A - Procedure creation program, procedure creation method, and procedure creation device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a procedure creation program, a procedure creation method, and a procedure creation device with which it is possible to create a post-change work procedure by the diverted use of a pre-change procedure in accordance with a system change.SOLUTION: Provided is a procedure creation program which, when a change to a hardware or software element constituting a system occurs, causes the process of creating a post-change procedure from a pre-change procedure for operating the element to be executed by a computer, where the program extracts a difference pertaining to a system element before and after the change, generates a first post-change procedure on the basis of the element to be operated on and operation item, post-change system configuration information, and a rule for creating a post-change procedure, extracts a second procedure for operating on the element pertaining to the difference from the generated first post-change procedure, processes the pre-change procedure on the basis of the extracted second procedure, and sets the processed procedure to a third post-change procedure.

Description

  The present application relates to a procedure creation program, a procedure creation method, and a procedure creation apparatus for creating a procedure related to system operation.

  In order to operate the system, there is an operation procedure manual that describes a procedure for an operator to operate elements constituting the system. Since the operation procedure is the order of operations for the elements constituting the system, it is necessary to update the operation procedure manual when the elements of the system are changed. Conventionally, when system elements are changed, the operation procedure manual is manually updated. On the other hand, there is a method for automatically creating an operation procedure manual based on the rules for creating the operation procedure manual (see, for example, Patent Documents 1 and 2).

JP2013-127656A JP 2013-140573 A

  By the way, when the system element is changed, the system administrator has a desire to update the operation procedure manual without changing the past procedure with a track record as much as possible. In other words, the system administrator desires to update the operation procedure manual by diverting the existing operation procedure manual as much as possible. However, since the conventional method of automatically creating the operation procedure manual creates the operation procedure manual based on the creation rules, the procedure that does not need to be changed is changed regardless of the change in the elements of the system.

  One of the objects of the present application is to provide a procedure creation program, a procedure creation method, and a procedure creation device that can create a procedure after the change by diverting the procedure of the work before the change according to the change of the system. is there.

  One aspect of the present application is a procedure creation program for causing a computer to execute a process for creating a procedure after a change from a procedure before a change to operate an element when a hardware or software element constituting the system is changed. After the change, based on the rules for generating the difference between the system elements before and after the change and generating the operation target elements and operation items, the changed system configuration information and the changed procedure From the generated first procedure after the change, the second procedure for operating the element related to the difference is extracted, and based on the extracted second procedure, the procedure before the change is processed, Set the processed procedure as the third procedure after the change.

  According to one aspect of the present application, it is possible to create a post-change procedure using the work procedure before the change according to the change of the system.

It is a block diagram which shows the hardware structural example of a procedure preparation apparatus. It is explanatory drawing which shows an example of the system which is the object which produces | generates a procedure. It is explanatory drawing which shows the hierarchical structure regarding the operation | work of a system operation. It is explanatory drawing which shows an example of system configuration information. It is explanatory drawing which shows an example of LayerUp. It is explanatory drawing which shows an example of a procedure rewriting rule. It is explanatory drawing which shows an example of a work expansion | deployment rule. It is explanatory drawing which shows an example of a procedure expansion | deployment rule. It is explanatory drawing which shows the example 1 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows the example 2 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows the example 3 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows the example 4 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows Example 5 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows the example 6 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows the example 7 of the tree structure produced | generated by a procedure production | generation process. It is explanatory drawing which shows an example of the procedure produced | generated in a procedure production | generation process. It is a functional block diagram which shows the function structural example of a procedure preparation apparatus. It is a flowchart which shows an example of the outline | summary procedure of the process which produces the procedure used for the system operation after a change. It is explanatory drawing which shows the system configuration example before a change and after a change. It is explanatory drawing which shows the system configuration information before a change. It is explanatory drawing which shows the system configuration information after a change. It is explanatory drawing which shows the existing procedure in the system before a change. It is explanatory drawing which shows the difference information of a system configuration. It is explanatory drawing which shows the procedure automatically produced | generated with respect to the system after a change. It is explanatory drawing which shows a part of tree structure automatically produced | generated with respect to the system after a change. It is explanatory drawing which shows an example of a partial procedure. It is a flowchart which shows an example of the procedure of a partial procedure extraction process. It is explanatory drawing which shows an example which has arrange | positioned the partial procedure and the operation which comprises a partial procedure in the head or the tail of the existing procedure. It is explanatory drawing which shows the system configuration example before a change and after a change. It is a flowchart which shows an example of the procedure of the existing procedure change necessity determination process. It is explanatory drawing which shows the system configuration example before a change and after a change. It is explanatory drawing which shows the system configuration information after a change. It is explanatory drawing which shows difference information. It is explanatory drawing which shows the procedure automatically produced | generated with respect to the system after a change. It is explanatory drawing which shows an example of the provisional procedure after a change in which operation of the partial procedure was put in between. It is a flowchart which shows an example of the procedure of an additional procedure process. It is explanatory drawing which shows an example of the output about the new procedure in the system after a change. It is a functional block diagram which shows the function structural example of a procedure preparation apparatus. It is explanatory drawing which shows an example of the data layout of partial procedure data. It is a flowchart which shows an example of the procedure of a partial procedure storage process. It is a flowchart which shows an example of the procedure of a procedure creation process after a change.

  A procedure creation apparatus according to the present embodiment will be described with reference to the drawings. The procedure creation apparatus creates a procedure for operating hardware or software elements constituting the system in order to operate the system. The worker who operates the system performs the work by referring to the procedure manual of the document in which the operation of the element, that is, the work is described in order. The procedure creation device may generate only data relating to the work procedure, or may create a procedure manual based on the data. In the following, it is assumed that the procedure creation device creates data related to the work procedure.

Embodiment 1
FIG. 1 is a block diagram illustrating a hardware configuration example of the procedure creation device 10. The procedure creation device 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, and a RAM (Random Access Memory) 13. The procedure creation device 10 includes a hard disk 14, an optical drive 15, a display unit 16, an operation unit 17, a timer 18, and a communication unit 19.

  The CPU 11 is a processor for executing an instruction set described in a software program. The CPU 11 controls each component of the procedure creation device 10. The CPU 11 reads the program 1P stored in the hard disk 14 to the RAM 13 and executes the program 1P read to the RAM 13.

  The ROM 12 is a read-only storage medium. The ROM 12 is, for example, a nonvolatile semiconductor memory. The ROM 12 stores a BIOS (Basic Input / Output System) executed by the CPU 11 when the procedure creation apparatus 10 is started up, firmware, and the like.

  The RAM 13 is a main storage device. The RAM 13 is, for example, an SRAM or a DRAM, and temporarily stores work variables, data, and the like necessary in the course of processing executed by the CPU 11. Note that a flash memory, a memory card, or the like may be used instead of the RAM 13.

The hard disk 14 is an auxiliary storage device. The hard disk 14 may be replaced with a flash memory capable of storing a large amount of information or an optical disk 1d such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a BD (Blu-ray (registered trademark) Disc). . The hard disk 14 may be mounted inside the procedure creation device 10 or may be placed outside the procedure creation device 10. The hard disk 14 may be replaced by a storage device (for example, a database server) accessible via the network 1N.
The hard disk 14 stores a program 1P executed by the CPU 11 and various data.

  The optical drive 15 is a storage device that reads information from an optical disc 1d such as a CD, DVD, or BD, which is an external storage medium, and stores the information on the optical disc 1d.

  The display unit 16 is a display device that displays an image. The display part 16 has screens, such as a liquid crystal display, an organic EL (Electro Luminescence) display, a CRT (Cathode Ray Tube) display, for example, and displays the various information which concerns on the program 1P on the said screen according to the instruction | indication from CPU11.

  The operation unit 17 is an input device such as a keyboard, a mouse, a touch panel, and a power switch on which a user performs various inputs. The operation unit 17 generates an input signal based on an operation by the user. The generated input signal is output to the CPU 11 via the bus 1b.

  The timer 18 is a device that counts a predetermined time by counting clocks. The timer 18 outputs the time measurement result to the CPU 11.

  The communication unit 19 is a wired or wireless communication modem, a LAN (Local Area Network) card, a router, a USB (Universal Serial Bus) terminal, a connection connector, or the like. The communication unit 19 is connected to the network 1N.

Note that the CPU 11 may read the program 1P from the optical disc 1d via the optical drive 15. The CPU 11 may read the program 1P from an external information processing apparatus or storage device via the communication unit 19. Further, a semiconductor memory 1m such as a flash memory storing the program 1P may be mounted in the procedure creation device 10.
The CPU 11 may store various data in an external information processing apparatus or storage device via the communication unit 19 instead of storing the various data in the hard disk 14. Further, the CPU 11 may store various data on the optical disc 1 d via the optical drive 15.

  The procedure creation device 10 automatically generates a procedure before or after a change when an element constituting the system is changed. The procedure creation apparatus 10 creates a post-change procedure using the pre-change procedure as much as possible, using the automatically generated procedure, the pre-change procedure, and the like. Therefore, before describing the function and operation of the procedure creation apparatus 10, a method by which the procedure creation apparatus 10 automatically generates a procedure will be described.

  FIG. 2 is an explanatory diagram illustrating an example of a system that is a target for generating a procedure. The target system includes a hardware element and a software element. The hardware elements are represented by squares, and the software elements are represented by rounded squares.

  The hardware elements include “Web Server” and “Ap1 Server”. Ap is the meaning of the application. “Web Server” is connected to the external Internet. An arrow from “Web Server” to “Ap1 Server” indicates a relationship in which “Web Server” is the related source and “Ap1 Server” is the related destination.

  The software elements include “apache” and “jobnet”. The daemon “apache” is executed on “Web Server”. “Jobnet” is executed on “Ap1 Server”.

  FIG. 3 is an explanatory diagram showing a hierarchical structure related to system operation work. System operation tasks, ie, element operations, can be expressed by hierarchical tree-structured nodes. The node here can be regarded as a class. A generic term for classes corresponding to work is called an action. Classes belonging to actions include tasks, works, procedures, and instructions from the top to the bottom. A task is a class classified by business.

  A task has one or more workpieces. A work is a class that is a basic unit of work. An example of a work is stopping “Ap1 Server”. The work has one or more procedures. A procedure is a work step for realizing a workpiece. A procedure has one or more instructions. An instruction is a class of work performed in a procedure created for system operation. An example of the instruction is “Ap1 Server” stop, “Ap1 Server” stop confirmation, and the like.

  A class belonging to an action is generally expressed by a set of (action, target). A target is an element to be operated. The procedure creation device 10 receives work contents. The action contents include work items and work objects. Here, the work item is, for example, stop or start. The work target is a target. The procedure creation apparatus 10 sets a set of (work item, work target) to a set of (work, target) from the received work item and work target. The procedure creation apparatus 10 rewrites a set of (work, target) into a set of (procedure, target) and expands it into a tree structure. Furthermore, the procedure creation apparatus 10 rewrites the (procedure, target) set to the (instruction, target) set and expands the tree structure. The procedure creation apparatus 10 creates a procedure of work based on a set of (instruction, target).

  Specifically, a method in which the procedure creation apparatus 10 automatically generates a procedure will be described. The procedure creation apparatus 10 automatically generates a procedure using a work item, a work target, system configuration information, a procedure rewrite rule, and a work procedure rule. Since the work item and the work target have already been described, the system configuration information, the procedure rewrite rule, and the work procedure rule will be described.

  FIG. 4 is an explanatory diagram showing an example of system configuration information. The system configuration information includes element information 21 and related information 22. FIG. 4A shows the element information 21. FIG. 4B shows the related information 22. The element information 21 includes an element, a type, a name, and a notation. The element is a kind of element constituting the system, and is hardware or software. The type is an element classification name, such as a server, an application, or a load balancer. The name is a more detailed name of the element. The notation is a notation specification of the element. In the present embodiment, elements are represented in a markup format using tags. In FIG. 4A, a <Server> </> tag indicates that the element type is a server, and an <Application> </> tag indicates that the element type is an application.

  The related information 22 is information indicating a related relationship between elements. The related information 22 includes a type, a related source, and a related destination. The type is a related type. The association source is an element on the related side. The related destination is an element on the related side.

  “Depend” attached when the type is data access indicates an operation of specifying a related element based on the relation when the operation is a stop, for example, related to a procedure rewriting rule described later. “LayerUp” attached when the type is server / application related, similarly relates to a procedure rewriting rule described later, and indicates an operation of specifying related elements based on the related relationship.

  FIG. 5 is an explanatory diagram showing an example of LayerUp. “LayerUp” means that an element in the immediately higher hierarchy is specified for an operation target in a certain hierarchy. For example, when the target is an OS, the middle-level middleware is the target for “LayerUp”. When the target is an application, the SLB service in the immediately upper layer becomes the target at the time of “LayerUp”.

  FIG. 6 is an explanatory diagram illustrating an example of a procedure rewriting rule. The procedure rewriting rule is a rule for rewriting a set of (action, target) to a new set of (action, target). In the following, the (action, target) set to be rewritten is called the left side, and the new (action, target) set is called the right side. The procedure rewriting rule in FIG. 6 is described in the XML format.

  Specifically, the procedure rewriting rule includes a rule for rewriting a work and a rule for rewriting a procedure when a class belonging to an action is expanded from the work level to the instruction level. FIG. 6A shows a rule for rewriting a workpiece. FIG. 6B shows a rule for rewriting a procedure.

  <Rule> is rule identification information. <Node> is an element to be rewritten. <Left> indicates information on the left side. <Right> indicates information on the right side. <actionClass> indicates the class to be rewritten, and any of work, procedure, and instruction is set. <actionAttribute> is an attribute of the element to be rewritten, and is an attribute of an action defined by a work procedure rule described later. <expression> is how to expand the node. <objectFunction> is an operation for expanding the class to be rewritten. <actionFunction> indicates the operation when rewriting the class. For example, “Expand” is an operation of expanding a set of (action, target) to be rewritten into a set of (action, target) in a lower layer.

  FIG. 6A shows an example of a procedure rewriting rule when RuleID is “R8”, <actionAttribute> is stop, and <actionClass> is work. FIG. 6A shows a rule that is rewritten into a set of (action, target) and a set of (action, target) in the lower layer for all the related targets called Depend. FIG. 6B shows an example of a procedure rewrite rule when RuleID is “R5”, <actionAttribute> is stop, and <actionClass> is a procedure. FIG. 6B shows a rule to be rewritten into a LayerUp (action, target) pair and a lower layer (action, target) pair.

The work procedure rule includes a work expansion rule and a procedure expansion rule.
FIG. 7 is an explanatory diagram showing an example of the work development rule 25. FIG. 8 is an explanatory diagram showing an example of the procedure expansion rule 26. 7 and 8, the data of the work expansion rule 25 and the procedure expansion rule 26 are respectively represented in a table format. The work expansion rule 25 is a rule for expanding a work to a lower procedure in the hierarchy shown in FIG. The procedure expansion rule 26 is a rule for expanding a procedure to a lower instruction in the hierarchy shown in FIG.

  The work expansion rule 25 includes RuleID, Workname, WorkAttribute, TargetClass, Condition, and ProcedureName. RuleID is an identification symbol of the work development rule 25. WorkName is the name of the work and is set to start, stop, apply patch, and the like. WorkAttribute is work attribute information, and is set to stop, start, normal, and the like. “stop” indicates that the work is a target stop. “start” indicates that the work is a target start. normal indicates that the work is a normal operation.

  TargetClass is a target class and defines LogicalServer, Application, and the like. Condition is an application condition of the work development rule 25, and a server type, an OS type, and the like are set.

  ProcedureName is a name of a procedure expanded from a work, and a sequence of procedures, a work, etc. can be set in addition to a single procedure. For example, in the rule of RuleID = W7 in the work expansion rule 25 of FIG. 7, the work called patch application is expanded to stop the work class (represented as <work>), “patch application” of the procedure class, and start of the work class. It means that.

  The procedure creation apparatus 10 expands the work corresponding to RuleID, Workname, WorkAttribute, TargetClass, and Condition into a procedure corresponding to ProcedureName based on the work expansion rule 25.

  The procedure expansion rule 26 includes RuleID, ProcedureName, and InstructionName. RuleID is an identification symbol of the procedure expansion rule 26. ProcedureName is the name of the procedure, and server node stop / start, job net stop / start, daemon stop / start, patch application, etc. are set. ProcedureAttribute is attribute information of the procedure, and “stop”, “start”, “normal”, and the like are set like the WorkAttribute of the work expansion rule 25.

  InstructionName is the name of an instruction developed from the procedure, and one or a plurality of instructions are set. Instructions are server node stop / start, server node stop / start confirmation, job net stop / start, job net stop / start confirmation, daemon stop / start, daemon stop / start confirmation, patch module preparation, patch application, patch application confirmation Etc.

  Based on the procedure expansion rule 26, the procedure creation device 10 expands a procedure corresponding to RuleID and ProcedureName into an instruction corresponding to InstructionName.

More specifically, a method in which the procedure creation device 10 automatically generates a procedure will be described.
The CPU 11 receives work items and work objects. Here, it is assumed that the work target is “Ap1 Server” and the work item is stopped.
FIG. 9 is an explanatory diagram of an example 1 of the tree structure generated by the procedure generation process. The CPU 11 adds the set (stop, Ap1 Server) as a child node of the root to the work level tree structure.

  The CPU 11 checks whether or not there is a procedure rewriting rule for rewriting the (stop, Ap1 Server) group. Since <actionClass> in the procedure rewrite rule in FIG. 6A is Work and <actionAttribute> is stop, the set of (stop, Ap1 Server) matches the condition of <Left> in R8 of the procedure rewrite rule. Therefore, the CPU 11 determines to apply the procedure rewriting rule of R8 to the set of work level (stop, Ap1 Server).

  The CPU 11 refers to the related information 22 in FIG. 4B because <objectFuntion>, which is the first node condition of <Right> in the procedure rewrite rule R8, is Dependent. The CPU 11 specifies the association source element “Web Server” for the target “Ap1 Server” that is the association destination, and generates a set of (stop, Web Server).

FIG. 10 is an explanatory diagram of a second example of the tree structure generated by the procedure generation process.
The CPU 11 adds the generated (stop, Web Server) pair as an older brother node as shown in the tree structure of FIG. 10 so that the relationship of the node is the same level (work level) and the relationship of the node changes from relationship source to relationship destination. To do.

  The CPU 11 refers to the work expansion rule 25 in FIG. 7 because <actionFunction>, which is the node condition next to <Right> in the procedure rewriting rule R8, is Expand. The work expansion rule 25 corresponding to the pair (stop, Ap1 Server) is a rule of RuleID = W1 in which WorkName is stop and TargetClass is LogicalServer. The CPU 11 determines to apply the work development rule 25 of W1 to the set (stop, Ap1 Server). The ProcedureName of W1 is a server stop. Therefore, the CPU 11 rewrites the set of (stop, Ap1 Server) to a set of (server stop, Ap1 Server) at the lower procedure level.

FIG. 11 is an explanatory diagram of a third example of the tree structure generated by the procedure generation process.
The CPU 11 adds the rewritten (server stop, Ap1 Server) set to the tree structure as a child node of the (stop, Ap1 Server) set, as shown in FIG.

  The CPU 11 checks whether or not there is a corresponding procedure rewriting rule for the procedure level (server stop, Ap1 Server) set added to the tree structure. Since <actionClass> in the procedure rewrite rule of FIG. 6B is Procedure and <actionAttribute> is Stop, the set of (server stop, Ap1 Server) matches the condition of <Left> in R5 of the procedure rewrite rule. Therefore, the CPU 11 determines to apply the procedure rewriting rule of R5 to a set of procedure level (server stop, Ap1 Server).

  The CPU 11 refers to the related information 22 in FIG. 4B because <objectFuntion>, which is the first node condition of <Right> in the procedure rewrite rule R5, is LayerUp. The CPU 11 specifies the element “jobnet” of the relation source located in the immediately upper hierarchy with respect to the target “Ap1 Server” that is the relation destination, and generates a set of (job net stop, jobnet).

FIG. 12 is an explanatory diagram of a fourth example of the tree structure generated by the procedure generation process.
As shown in the tree structure of FIG. 12, the CPU 11 creates a set of (job net stop, jobnet) (server) so that the first hierarchy (procedure level) and the first and second node relationships are relation source → relation destination. Add it as an elder node for the pair (Stop, Ap1 Server).

  The CPU 11 refers to the procedure expansion rule 26 in FIG. 8 because <actionFunction>, which is the node condition next to <Right> in the procedure rewrite rule R5, is Expand. The procedure expansion rule 26 corresponding to a set of procedure level (server stop, Ap1 Server) is a rule of RuleID = P1 in which ProducerName is a server node stop and ProducerAttribute is stop. The CPU 11 applies the procedure expansion rule 26 of P1 to the set (server stop, Ap1 Server). The InstructionName of P1 is a server node stop and a server node stop confirmation. Therefore, the CPU 11 rewrites the set of (server stop, Ap1 Server) into a set of (server node stop, Ap1 Server) and (server node stop confirmation, Ap1 Server) at the instruction level one level lower.

FIG. 13 is an explanatory diagram of a fifth example of the tree structure generated by the procedure generation process.
The CPU 11 sets the rewritten (server node stop, Ap1 Server) and (server node stop confirmation, Ap1 Server) as child nodes for the procedure level (server stop, Ap1 Server) set as shown in FIG. Add to the tree structure.

FIG. 14 is an explanatory diagram of a sixth example of the tree structure generated by the procedure generation process.
The CPU 11 similarly rewrites the procedure level (job net stop, jobnet) set to (job net stop, jobnet), (job net stop confirmation, jobnet) set. As shown in FIG. 14, the CPU 11 adds a combination of (job net stop, jobnet) and (job net stop confirmation, jobnet) to the tree structure as a child node for the (job net stop, jobnet) pair.

FIG. 15 is an explanatory diagram of an example 7 of the tree structure generated by the procedure generation process.
The CPU 11 executes the above rewriting process until all (action, target) pairs are expanded into (instruction, target) pairs.
As shown in FIG. 15, the CPU 11 takes out the instruction level pairs in order from the first node based on the predecessor relationship of the nodes when all the combinations are expanded into instruction level (instruction, target) pairs.

  FIG. 16 is an explanatory diagram illustrating an example of a procedure generated in the procedure generation process. The CPU 11 arranges the set of (instruction, target) that has been taken out and sets it as an operation procedure for the element.

Next, functions of the procedure creation device 10 will be described.
FIG. 17 is a functional block diagram illustrating a functional configuration example of the procedure creation device 10. The procedure creation apparatus 10 includes functional units such as a reception unit 100, a difference extraction unit 200, a procedure automatic generation unit 300, a partial procedure extraction unit 400, a determination unit 500, a setting unit 600, and an output unit 700. The receiving unit 100 is a functional unit corresponding to the operation unit 17. The receiving unit 100 receives work contents, that is, work items and work objects.

  The difference extraction unit 200 has a function of extracting a difference between an element related to the system before the change and an element related to the system after the change by comparing the system configuration information before the change with the system configuration information after the change. Part. Further, the difference extraction unit 200 extracts a difference between the relationship between elements related to the system before the change and the relationship between elements related to the system after the change. The difference extraction unit 200 stores the extracted difference as difference information in the RAM 13 or the hard disk 14.

  If the change content is an addition of an element to the system or a change in the relationship between elements, the procedure automatic generation unit 300 refers to the procedure automatic generation rule and the work content received by the reception unit 100 and the system after the change It is a configuration unit that automatically generates a new procedure from configuration information. The procedure automatic generation rules here are procedure rewrite rules and work procedure rules. Further, when the change content is deletion of an element from the system, the procedure automatic generation unit 300 refers to the procedure automatic generation rule, and determines the procedure from the work content received by the reception unit 100 and the system configuration information before the change. Is automatically generated.

The partial procedure extraction unit 400 is a functional unit that extracts a partial procedure for operating the elements of the difference before and after the change based on the difference information extracted by the difference extraction unit 200. Hereinafter, this partial procedure is referred to as a partial procedure. The partial procedure extraction unit 400 stores a procedure generated based on the difference element (corresponding to a partial tree expanded in the procedure generation process) in the RAM 13 or the hard disk 14 as a partial procedure.
Further, the partial procedure extraction unit 400 detects a procedure rewrite rule applied to the difference element in the process in which the procedure automatic generation unit 300 generates a new procedure. The partial procedure extraction unit 400 acquires a procedure rewrite rule sequence up to detection of the configuration information difference. The partial procedure extraction unit 400 stores the acquired procedure rewrite rule sequence in the RAM 13 or the hard disk 14.
The processing executed by the partial procedure extraction unit 400 is performed in parallel with the processing by the procedure automatic generation unit 300.

  The determination unit 500 determines whether or not there is a contradiction in the relationship between elements operated by the partial procedure when the partial procedure is incorporated into the procedure before the change without changing the procedure before the change as much as possible. It is. Hereinafter, the procedure before the change is referred to as an existing procedure. In addition, when the change content is deletion of an element from the system, the determination unit 500 processes the existing procedure based on the partial procedure, but there is no contradiction in the relation of the element operated by the partial procedure. Does not determine whether or not.

  The determination unit 500 determines whether or not the specified procedure expansion rule is included in the procedure rewrite rule sequence acquired by the partial procedure extraction unit 400. The designated procedure development rule is a rule for directly applying the work development rule 25 or the procedure development rule 26 among the procedure rewriting rules, and developing a predetermined procedure regardless of the system configuration. The sequence of procedures deployed by the designated procedure deployment rule cannot be changed. Therefore, if the determination unit 500 determines that the specified procedure expansion rule is included in the acquired procedure rewrite rule sequence, the determination unit 500 determines that the existing procedure cannot be diverted for the procedure creation for the system after the change. .

The setting unit 600 is a functional unit that sets an existing procedure in which a partial procedure is incorporated as a new procedure without changing the existing procedure as much as possible according to the determination result of the determination unit 500. In addition, the setting unit 600 sets a new procedure change location with respect to the existing procedure. When the determination unit 500 determines that the existing procedure cannot be diverted, the setting unit 600 does not set a new procedure and a procedure change part.
Note that the processing executed by the setting unit 600 uses the result of the existing procedure in which the partial procedure is incorporated by the determination unit 500.

  The output unit 700 is a functional unit that outputs a new procedure for the changed system set by the setting unit 600 and a procedure change location. The output unit 700 outputs the new procedure generated by the automatic procedure generation unit 300 when the setting unit 600 does not set a new procedure and procedure change part.

FIG. 18 is a flowchart illustrating an example of an outline procedure of processing for creating a procedure used for system operation after change.
The CPU 11 receives an operation target element and an operation item (step S1). The CPU 11 extracts a difference from the system configuration information before and after the change (step S2). The CPU 11 automatically generates a procedure before or after the change based on the received operation target element and operation item, configuration information in the system after or before the change, and a procedure automatic generation rule (step S3).

  The CPU 11 extracts a partial procedure for manipulating the extracted difference element from the automatically generated procedure before or after the change (step S4). In step S4, when the system change is an addition of an element or a change in the related information 22 between elements, the CPU 11 extracts a partial procedure for operating the extracted difference element from the automatically generated procedure after the change. When the system change is element deletion, the CPU 11 extracts a partial procedure for operating the extracted difference element from the automatically generated procedure before the change. The CPU 11 processes the procedure before the change using the extracted partial procedure (step S5).

  The CPU 11 determines whether or not the processed procedure is consistent with the relationship between the difference elements before and after the change (step S6). The CPU 11 sets the processed procedure as the procedure used for the system operation after the change according to the determined result (step S7). In step S7, when the change content is deletion of an element, the CPU 11 sets the procedure processed in step S5 as the procedure used for the system operation after the change without passing through step S6. CPU11 outputs the procedure used for the system operation after the set change and procedure change location (step S8), and complete | finishes a process.

The operation of the procedure creation device 10 will be described.
FIG. 19 is an explanatory diagram illustrating a system configuration example before and after the change. FIG. 19A shows the system configuration before the change. FIG. 19B shows the system configuration after the change.
The system to be changed includes a hardware element and a software element. As in FIG. 2, the hardware elements are represented by squares, and the software elements are represented by rounded squares.

  The hardware elements in the system before the change include “ServerX” and “ServerY”. The software elements in the system before the change include “ApA” and “ApB”. “ApA” is executed on “ServerX”. “ApB” is executed on “ServerY”. An arrow from “ApB” to “ApA” indicates a relation in which “ApB” is the relation source and “ApA” is the relation destination.

  In the system after the change shown in FIG. 19B, hardware elements and software elements are added. The added element box is hatched. The added hardware element is “ServerZ”. The added software elements are “ApC” and “ApD”. “ApC” is executed on “ServerY”. “ApD” is executed on “ServerZ”. An arrow from “ApD” to “ApC” indicates a relation in which “ApD” is the relation source and “ApC” is the relation destination.

  FIG. 20 is an explanatory diagram showing system configuration information before the change. FIG. 20A shows the element information 21. FIG. 20B shows the related information 22. The display mode of the element information 21 in FIG. 20A and the related information 22 in FIG. 20B is the same as the display mode in FIGS. 4A and 4B, respectively.

  FIG. 21 is an explanatory diagram showing the system configuration information after the change. FIG. 21A shows the element information 21. FIG. 21B shows the related information 22. The display mode of the element information 21 of FIG. 21A and the related information 22 of FIG. 21B is the same as the display mode of FIGS. 4A and 4B, respectively.

  The CPU 11 receives work items and work objects. Here, it is assumed that the CPU 11 accepts the stop of “ServerX, Y”.

FIG. 22 is an explanatory diagram showing an existing procedure in the system before the change. In order to stop the hardware “ServerX” and “ServerY”, it is necessary to stop the related application first. Also, when stopping a plurality of applications, it is necessary to stop from the related source application. Therefore, in the existing procedure, first, the association source “ApB” is stopped, and then the association destination “ApA” is stopped. Since either “ServerX” or “ServerY” may be stopped first, 3 is written in the operation order of FIG. When the elements to be worked are arranged according to the procedure, for example, it is as follows.
“ApB” → “ApA” → “ServerX” → “ServerY”

The CPU 11 extracts the difference between the system configuration information before and after the change from the system configuration information shown in FIGS. 20 and 21 respectively. The CPU 11 extracts the difference by comparing the data of the element information 21 and the related information 22 before and after the change line by line.
FIG. 23 is an explanatory diagram showing difference information of the system configuration. FIG. 23A shows the difference of the element information 21. FIG. 23B shows the difference of the related information 22. The display mode of the element information 21 in FIG. 23A and the related information 22 in FIG. 23B is obtained by adding a classification item to the display mode in FIGS. 4A and 4B.
Since the change contents of the system dealt with here are addition of elements and addition of related information, addition is described in the classification of FIGS. 23A and 23B, respectively. In addition, when the change content of the system is a change of association between elements, deletion of an element, or the like, change or deletion is written in the classification, respectively.

  FIG. 23A shows “ServerZ”, “ApC”, and “ApD” added to the system before the change as element differences. FIG. 23B shows the relation between “ApD” and “ApC”, the relation between “ApC” and “ServerY”, and the relation between “ApD” and “ServerZ” added to the system before the change as the relation differences. ing.

The CPU 11 automatically generates a procedure in which the work content is “ServerX, Y” stop for the system after the change. The automatic generation method is the same as the method described above.
FIG. 24 is an explanatory diagram showing a procedure automatically generated for the system after the change. When the elements to be worked are arranged according to the automatically generated procedure, it is as follows.
“ApB” → “ApA” → “ServerX” → “ApD” → “ApC” → “ServerY”
In the automatically generated procedure, “ApD” → “ApC” is inserted between “ServerX” → “ServerY” in the existing procedure. Accordingly, in the automatically generated procedure, the existing procedure is not used as it is.

  FIG. 25 is an explanatory diagram showing a part of the tree structure automatically generated for the system after the change. When the CPU 11 automatically generates a procedure, it expands the node and adds it to the tree structure. At that time, the CPU 11 determines whether or not the application condition of the procedure rewriting rule applied when the node is expanded corresponds to the difference system configuration. When the CPU 11 determines that the application condition of the applied procedure rewriting rule corresponds to the system configuration, the CPU 11 adds the node to the partial procedure root node, and the procedure rewriting rule applied until it is determined to correspond to the difference system configuration. Get the column. For example, in the example of FIG. 25, when a procedure rewrite rule of RuleID = R5 is applied when rewriting a set of procedure level (stop physical server node, ServerY) to a set of procedure level (stop application, ApC) Is shown. The CPU 11 uses the obtained sequence of procedure rewrite rules as a material used in later determination processing. The subsequent determination processing is processing for determining whether or not the sequence of procedure rewrite rules includes a specified procedure expansion rule.

  The CPU 11 acquires a partial tree having the partial procedure route as a root from the generated tree structure for each partial procedure route node. In FIG. 25, two subtrees surrounded by a broken line are subtrees having a partial procedure route as a root. The CPU 11 extracts leaf nodes from the subtree, and outputs the extracted leaf nodes in an order that matches the related information 22 in the system after the change. That is, the CPU 11 outputs a partial procedure.

FIG. 26 is an explanatory diagram showing an example of a partial procedure. There are two partial procedures here, and for convenience, they are referred to as partial procedure 1 and partial procedure 2, respectively. FIG. 26A shows partial procedure 1. FIG. 26B shows partial procedure 2. FIG. 26C shows the procedure rewriting rules applied until the partial procedure 1 is detected. FIG. 26D shows the procedure rewriting rules applied until the partial procedure 2 is detected.
When the elements to be worked are arranged according to the partial procedure 1, it is as follows.
“ApD” → “ApC”
When the elements to be worked are arranged according to the partial procedure 2, it is as follows.
“ApC” → “ServerY”

FIG. 27 is a flowchart illustrating an example of the procedure of the partial procedure extraction process.
The CPU 11 selects an automatically generated unprocessed node (step S11). CPU11 memorize | stores the procedure rewriting rule applied to the selected node (step S12). The CPU 11 determines whether or not the application condition of the applied procedure rewriting rule corresponds to the difference system configuration information (step S13). When the CPU 11 determines that the application condition of the applied procedure rewriting rule does not correspond to the difference system configuration information (step S13: NO), the CPU 11 returns the process to step S11.

  When the CPU 11 determines that the application condition of the applied procedure rewriting rule corresponds to the difference system configuration information (step S13: YES), the CPU 11 adds the selected node to the partial procedure root node, and the procedure rewriting rule up to this point A column is acquired (step S14). The CPU 11 determines whether or not all nodes have been processed (step S15). If the CPU 11 determines that not all nodes have been processed (step S15: NO), the process returns to step S11. If the CPU 11 determines that all nodes have been processed (step S15: YES), it selects an unprocessed partial procedure root node (step S16).

  The CPU 11 acquires a partial tree having the selected partial procedure root node as a root from the tree structure (step S17). The CPU 11 sequentially outputs the leaf nodes of the acquired partial tree (step S18). That is, the CPU 11 outputs a partial procedure. The CPU 11 determines whether or not all partial procedure route nodes have been processed (step S19). If the CPU 11 determines that all partial procedure route nodes have not been processed (step S19: NO), the process returns to step S16. CPU11 complete | finishes a process, when it determines with having processed all the partial procedure root nodes (step S19: YES).

  When the extracted partial procedure is included in the existing procedure, the CPU 11 applies the existing procedure to the new procedure after the system configuration change. Even if the system elements are changed, as long as the existing procedure includes a partial procedure, the system after the change can be operated by the existing procedure. As a result, existing procedures with a track record will be used.

  When the extracted partial procedure is not included in the existing procedure at all, the CPU 11 places the partial procedure at the beginning or end of the existing procedure. The CPU 11 applies the existing procedure in which the partial procedure is arranged at the head or tail to the new procedure after the system configuration change. The fact that the partial procedure is placed at the beginning or end of the existing procedure means that the existing procedure is not changed at all. Thereby, diversion of the existing procedure can be aimed at.

  When one operation constituting the partial procedure is included in the existing procedure and another operation constituting the partial procedure is not included in the existing procedure, the CPU 11 places the other operation at the beginning or end of the existing procedure. However, it is determined whether there is a contradiction in the order of the partial procedures. When the CPU 11 determines that there is no contradiction in the order of the partial procedures when another operation not included in the existing procedures is arranged at the beginning or the end of the existing procedure, the CPU 11 determines another operation related to the partial procedure at the beginning or the end. Apply the existing procedure with the operation to the new procedure after changing the system configuration.

When the CPU 11 determines that there is a contradiction in the order of the partial procedures when another operation that is not included in the existing procedure is placed at the beginning or end of the existing procedure, the other operation that is not included in the existing procedure is Place between procedures. When another operation not included in the existing procedure is arranged between the existing procedures, the CPU 11 determines whether there is a contradiction in the order of the partial procedures. When the CPU 11 determines that there is no contradiction in the order of the partial procedures when another operation not included in the existing procedure is arranged between the existing procedures, the other operation not included in the existing procedure is in between. Apply the existing procedure to the new procedure after changing the system configuration.
Even if an operation that constitutes a partial procedure is arranged between existing procedures, the existing procedure is partially diverted.

  When the CPU 11 determines that there is a contradiction in the order of the partial procedures when another operation not included in the existing procedure is arranged between the existing procedures, the CPU 11 replaces the newly generated procedure with the new procedure after the system configuration change. Applies to

A specific example will be described in which a partial procedure or an operation constituting a partial procedure is arranged at the beginning or end of an existing procedure. A specific example in which operations that constitute a partial procedure and that are not included in the existing procedure are arranged between the existing procedures will be described after explaining the later-described flow of processing the existing procedure based on the partial procedure. .
FIG. 28 is an explanatory diagram showing an example in which a partial procedure and operations constituting the partial procedure are arranged at the beginning or end of an existing procedure. FIG. 28 shows a procedure in which the partial procedure 1 of FIG. 26A is arranged at the beginning of the existing procedure of FIG. 22 and the stop operation of “ApC” constituting the partial procedure 2 of FIG. 26B is arranged at the beginning of the existing procedure of FIG. Show.

The elements to be operated by the partial procedure 1 are “ApD” → “ApC” when arranged in the operation order. The elements to be operated by the partial procedure 2 are “ApC” → “ServerY” when arranged in the operation order. The operation sequences 1 and 2 in FIG. 28 are consistent with the partial procedure 1. The stop operation of “ApC” constituting the partial procedure 2 is not included in the existing procedure. The stop operation of “ServerY” constituting the partial procedure 2 is included in the existing procedure. When the stop operation of “ApC” not included in the existing procedure is arranged at the beginning of the existing procedure (in this case, it overlaps with the case where partial procedure 1 is arranged at the beginning of the existing procedure), the new procedure shown in FIG. Thus, there is no contradiction in the order “ApC” → “ServerY” of the partial procedure 2. Therefore, by applying the procedure of FIG.
That the new procedure is consistent with the partial procedure means that the new procedure is consistent with the related information 22 in the difference information.

A description will be given of a new procedure after the system change created by the procedure creation device 10 when an element constituting the system is deleted.
FIG. 29 is an explanatory diagram illustrating a system configuration example before and after the change. FIG. 29A shows the system configuration before the change. FIG. 29B shows the system configuration after the change.
The system to be changed includes a hardware element and a software element. As in FIG. 2, the hardware elements are represented by squares, and the software elements are represented by rounded squares.

  The hardware elements in the system before the change include “ServerX” and “ServerY”. The software elements in the system before the change include “ApA”, “ApB”, and “ApC”. “ApA” is executed on “ServerX”. “ApB” and “ApC” are executed on “ServerY”. An arrow from “ApA” to “ApB” indicates a relation in which “ApA” is the relation source and “ApB” is the relation destination.

  In the system after the change, “ApB” which is a software element is deleted. Therefore, the related information from “ApA” to “ApB” is also deleted.

Here, it is assumed that the operation content is “ServerY” stop. It is assumed that the existing procedure is “ApC” → “ApA” → “ApB” → “ServerY” when the elements to be stopped are arranged in the operation order. The new procedure automatically generated for the system after the change is "ApC" → "ServerY" when the elements to be stopped are arranged in the operation order. The CPU 11 extracts two partial procedures from “ApB”, which is the difference between the elements before and after the change, and from “ApA” to “ApB”, which is the difference related information 22. These two partial procedures are “ApA” → “ApB” and “ApB” → “ServerY” when the elements to be stopped are arranged in the operation order. Here, for convenience, the partial procedure corresponding to “ApA” → “ApB” is referred to as partial procedure 3, and the partial procedure corresponding to “ApB” → “ServerY” is referred to as partial procedure 4.
In the case of a system change in which an element is deleted, the CPU 11 automatically generates a procedure based on the system configuration before the change and extracts a partial procedure for operating the difference element.

The CPU 11 determines whether or not all of the elements operated in the partial procedure are not included in the elements operated in the new procedure automatically generated. In the case of the partial procedure 3, all the elements “ApA” and “ApB” are not included in the automatically operated new element “ApC” → “ServerY”. In such a case, the CPU 11 deletes the partial procedure 3 from the existing procedure. On the other hand, in the case of the partial procedure 4, some elements “ServerY” are included and some elements “ApB” are not included in the automatically operated element “ApC” → “ServerY”. In such a case, the CPU 11 deletes the operation for “ApB” that is not included in the element operated by the automatically generated new procedure from the existing procedure. However, since the operation for “ApB” is deleted from the existing procedure when the partial procedure 3 is deleted from the existing procedure, the CPU 11 does not perform the process related to the partial procedure 4. Thus, the CPU 11 creates a procedure for the changed system. If the elements to be operated in the newly created procedure are arranged in the operation order, “ApC” → “ServerY”.
When deleting a procedure or operation from an existing procedure, there is no contradiction in the association of elements operated in the partial procedure, so the CPU 11 does not execute a determination process considering the association between elements constituting the partial procedure.

FIG. 30 is a flowchart illustrating an example of a procedure of an existing procedure change necessity determination process. In the existing procedure change necessity determination process, the CPU 11 determines whether or not the existing procedure needs to be changed, and changes the existing procedure using the partial procedure when it is necessary to change the existing procedure. If the CPU 11 determines in the existing procedure change necessity determination process that there is no need to change the existing procedure, the CPU 11 does not change the existing procedure. As a result of the existing procedure change necessity determination process, the existing procedure that is recombined in the partial procedure or the existing procedure that is not changed becomes a new procedure after the system change created by the procedure creation device 10.
In the existing procedure change necessity determination process, the CPU 11 sets the automatically generated new procedure as a new procedure after the system change if the already acquired procedure rewrite rule column includes the designated procedure expansion rule.

  Hereinafter, the partial procedure in the case where the system change is the addition of an element or the change of the related information 22 between elements is referred to as an additional partial procedure. The partial procedure when the system change is element deletion is referred to as a deletion partial procedure.

  The CPU 11 selects an unprocessed partial procedure (step S201). The CPU 11 determines whether or not the procedure rewrite rule sequence acquired until the selected partial procedure is extracted includes the designated procedure expansion rule (step S202). If the CPU 11 determines that the procedure rewrite rule sequence includes the designated procedure expansion rule (step S202: YES), the CPU 11 sets the automatically generated new procedure as a new procedure after the system change (step S203), and ends the process. To do.

  When the CPU 11 determines that the procedure rewrite rule sequence does not include the designated procedure expansion rule (step S202: NO), the CPU 11 determines whether or not the procedure rewrite rule sequence related to all partial procedures has been processed (step S204). If the CPU 11 determines that the procedure rewrite rule sequence relating to all the partial procedures has not been processed (step S204: NO), the process returns to step S201. If the CPU 11 determines that the procedure rewrite rule sequence relating to all the partial procedures has been processed (step S204: YES), it sets the existing procedure to the provisional procedure after the change (step S205). The post-change provisional procedure is a provisional procedure for creating a new procedure after changing the system by diverting the existing procedure as much as possible.

  The CPU 11 selects an unprocessed partial procedure (step S206). The CPU 11 determines whether or not the selected partial procedure is an additional partial procedure (step S207). If the CPU 11 determines that the selected partial procedure is an additional partial procedure (step S207: YES), the CPU 11 executes an additional procedure process (step S208) and advances the process to step S212.

  When the CPU 11 determines that the selected partial procedure is not an additional partial procedure (step S207: NO), the CPU 11 determines whether or not all the elements operated in the partial procedure are not included in the element information 21 of the system after the change. (Step S209). Here, the case where the partial procedure is not an additional partial procedure is a case where the partial procedure is a deleted partial procedure. If the CPU 11 determines that all of the elements operated in the partial procedure are not included in the changed system element information 21 (step S209: YES), the CPU 11 deletes the partial procedure from the post-change provisional procedure (step S210). If the CPU 11 determines that not all of the elements operated in the partial procedure are included in the element information 21 of the system after the change (step S209: NO), the CPU 11 executes the operation deletion process of step S211 shown below. . When not all the elements operated in the partial procedure are included in the element information 21 of the system after the change, when some of the elements operated in the partial procedure are not included in the element information 21 of the system after the change It is. CPU11 deletes operation with respect to the element which is not contained in the element information 21 of the system after a change among the elements operated by a partial procedure from a temporary procedure after a change (step S211).

  The CPU 11 determines whether or not all partial procedures have been processed (step S212). If the CPU 11 determines that all partial procedures have not been processed (step S212: NO), the process returns to step S206. When determining that all partial procedures have been processed (step S212: YES), the CPU 11 sets the post-change provisional procedure as a new procedure after the system change (step S213), and ends the processing.

  The additional procedure process in FIG. 30 includes a process of placing operations that are not included in the post-change provisional procedure among the operations performed in the partial procedure, between the post-change provisional procedures. Therefore, before explaining the flow of the additional procedure process, the process of placing operations that are not included in the post-change provisional procedure among the operations performed in the partial procedure will be described with a specific example. To do.

FIG. 31 is an explanatory diagram showing a system configuration example before and after the change. FIG. 31A shows the system configuration before the change. The system configuration shown in FIG. 31A is the same as the system configuration shown in FIG. 19A. FIG. 31B shows the system configuration after the change.
The system to be changed includes a hardware element and a software element. As in FIG. 2, the hardware elements are represented by squares, and the software elements are represented by rounded squares.

  The hardware elements in the system before the change include “ServerX” and “ServerY”. The software elements in the system before the change include “ApA” and “ApB”. “ApA” is executed on “ServerX”. “ApB” is executed on “ServerY”. An arrow from “ApB” to “ApA” indicates a relation in which “ApB” is the relation source and “ApA” is the relation destination.

  “ApC”, which is a software element executed on “ServerY”, is added to the system after the change. In the system after the change, a relation having “ApB” as a relation source and “ApC” as a relation destination is added. Furthermore, naturally, a relation from software “ApC” to hardware “ServerY” is added.

  The system configuration information before the change is the same as that shown in FIG. Further, the existing procedure in the system before the change is the same as that shown in FIG. Therefore, it is assumed that the post-change provisional procedure here is the same as that shown in FIG.

  FIG. 32 is an explanatory diagram showing the system configuration information after the change. FIG. 32A shows the element information 21. FIG. 32B shows the related information 22. The display mode of the element information 21 in FIG. 32A and the related information 22 in FIG. 32B is the same as the display mode of FIGS. 4A and 4B, respectively.

The CPU 11 extracts the difference between the system configuration information before and after the change from the system configuration information shown in FIGS. 20 and 32, respectively. The CPU 11 extracts the difference by comparing the data of the element information 21 and the related information 22 before and after the change line by line.
FIG. 33 is an explanatory diagram showing difference information. FIG. 33A shows the difference of the element information 21. FIG. 33B shows the difference of the related information 22. The display mode of the element information 21 in FIG. 33A and the related information 22 in FIG. 33B is obtained by adding a classification item to the display mode in FIGS. 4A and 4B.

  FIG. 33A shows “ApC” added to the system before the change as an element difference. FIG. 33B shows the relationship between “ApB” and “ApC” and the relationship between “ApC” and “ServerY” added to the system before the change as the difference in the related information.

  The CPU 11 receives work items and work objects. Here, it is assumed that the CPU 11 accepts the stop of “ServerX, Y”. The CPU 11 automatically generates a procedure in which the work content is “ServerX, Y” for the changed system. The automatic generation method is the same as the method described above.

FIG. 34 is an explanatory diagram showing a procedure automatically generated for the system after the change. When the elements to be stopped are arranged according to the automatically generated procedure, it is as follows.
“ApB” → “ApA” → “ServerX” → “ApC” → “ServerY”
When the elements to be stopped are arranged according to the post-change provisional procedure, it is as follows.
“ApB” → “ApA” → “ServerX” → “ServerY”
In the automatically generated procedure, “ApC” is inserted between “ServerX” and “ServerY” in the provisional procedure after the change. Therefore, in the automatically generated procedure, the post-change provisional procedure is not used as it is.

The CPU 11 extracts two partial procedures from the automatically generated procedure based on the difference information. These two partial procedures are “ApB” → “ApC” and “ApC” → “ServerY” when the elements to be stopped are arranged in the operation order. Here, for convenience, the partial procedure corresponding to “ApB” → “ApC” is referred to as partial procedure 5, and the partial procedure corresponding to “ApC” → “ServerY” is referred to as partial procedure 6.
The CPU 11 first tries to incorporate the partial procedure 5 into the provisional procedure after the change. Thereafter, the CPU 11 tries to incorporate the partial procedure 6 into the provisional procedure after the change.

  “ApB” that is an element that is operated in the partial procedure 5 is included in the elements that are operated in the provisional procedure after the change, but “ApC” that is an element that is operated in the partial procedure 5 is not included. Therefore, the CPU 11 does not change the order of operations to “ApB” in the post-change provisional procedure, and places the operation to “ApC” at the beginning or end of the post-change provisional procedure. It is determined whether or not the order of 6 is inconsistent. If the operation to “ApC” is arranged at the beginning of the provisional procedure after the change, “ApC” → “ApB” in the procedure after the arrangement, the order of the partial procedure 5 is reversed and contradicts. On the other hand, when the operation to “ApC” is arranged at the end of the provisional procedure after the change, “ServerY” → “ApC” in the procedure after the arrangement, the order of the partial procedure 6 is reversed and contradicts.

Next, the CPU 11 arranges the operation to “ApC” between the post-change provisional procedures without changing the post-change provisional procedures as much as possible, so that the order of the partial procedure 5 and the partial procedure 6 is inconsistent. Determine whether.
FIG. 35 is an explanatory diagram showing an example of the post-change provisional procedure in which the operation of the partial procedure is inserted. FIG. 35 shows a case where the operation to “ApC” is arranged between the post-change provisional procedure as the second operation from the beginning of the post-change provisional procedure. The post-change provisional procedure shown in FIG. 35 is consistent with the order of the partial procedure 5 and the partial procedure 6, and is not contradictory. In addition, a part of the post-change provisional procedure “ApA” → “ServerX” → “ServerY” after the operation to “ApC” is arranged is diverted. Therefore, the CPU 11 creates the procedure shown in FIG. 35 and ends the process of incorporating the partial procedure 5 into the changed temporary procedure. At this point, the post-change provisional procedure is updated from the procedure of FIG. 22 to the procedure of FIG.

  35. All elements “ApC” and “ServerY” that are elements operated in the partial procedure 6 are already included in the elements operated in the provisional procedure after the change in FIG. Therefore, the CPU 11 ends the process of incorporating the partial procedure 6 into the provisional procedure after the change.

FIG. 36 is a flowchart illustrating an example of the procedure of the additional procedure process.
The CPU 11 determines whether or not the partial procedure is included in the post-change provisional procedure (step S31). CPU11 complete | finishes a process, when it determines with a partial procedure being included in the provisional procedure after a change (step S31: YES). The partial procedure is included in the post-change provisional procedure when all operations performed in the partial procedure are included in the post-change provisional procedure. If the partial procedure is not included in the post-change provisional procedure, all of the operations performed in the partial procedure are not included in the post-change provisional procedure, and some of the operations performed in the partial procedure are not included in the post-change provisional procedure Including cases. If some of the operations performed in the partial procedure are not included in the post-change interim procedure, some of the operations performed in the partial procedure are included in the post-change interim procedure, and other portions are not included in the post-change interim procedure Is the case.

  When the CPU 11 determines that the partial procedure is not included in the post-change provisional procedure (step S31: NO), the CPU 11 determines whether all operations performed in the partial procedure are not included in the post-change provisional procedure (step S32). ). If the CPU 11 determines that all the operations performed in the partial procedure are not included in the post-change provisional procedure (step S32: YES), the CPU 11 places the partial procedure at the beginning or end of the post-change provisional procedure (step S33), and performs processing Exit.

  If the CPU 11 determines that all the operations performed in the partial procedure are not included in the post-change provisional procedure (step S32: NO), the CPU 11 executes step S34. If all operations performed in the partial procedure are not included in the post-change provisional procedure, some of the operations performed in the partial procedure are included in the post-change provisional procedure, and other operations are included in the post-change provisional procedure. Is not included. In step S <b> 34, the CPU 11 places an operation that is not included in the post-change provisional procedure among the operations performed in the partial procedure, at the beginning or end of the post-change provisional procedure, and determines whether or not there is no conflict with the order of the partial procedures. judge.

  When the CPU 11 determines that the operations that are not included in the post-change provisional procedure among the operations performed in the partial procedure are arranged at the beginning or end of the post-change provisional procedure and are not inconsistent with the order of the partial procedures (step S34: YES), Step S35 is executed, and the process is terminated. In step S <b> 35, the CPU 11 places the operation of the partial procedure not included in the post-change provisional procedure at either the beginning or the end of the post-change provisional procedure so as to match the association between the elements operated in the partial procedure. .

  When the CPU 11 determines that there is no conflict with the order of the partial procedures by placing an operation that is not included in the post-change provisional procedure among the operations performed in the partial procedure at the beginning or end of the post-change provisional procedure ( Step S34: NO), Step S36 is executed, and the process is terminated. The case where there is no contradiction with the order of the partial procedures is the case where there is a contradiction with the order of the partial procedures. In step S36, the CPU 11 arranges the operations of the partial procedures not included in the post-change provisional procedure between the post-change provisional procedures so as to match the association between the elements operated in the partial procedures.

The CPU 11 outputs the post-change provisional procedure as a new procedure in the system after the change.
FIG. 37 is an explanatory diagram showing an example of output regarding a new procedure in the system after the change. FIG. 37 shows an example in which the new procedure is output in a table format when the operation is “ServerX, Y” stop when the system configuration before the change shown in FIG. 19A is changed to the system configuration shown in FIG. 19B. Is shown. At the right end of the table in FIG. In the case of FIG. 37, additions are shown as changes in the stop for “ApD” in operation order 1 and the stop for “ApC” in operation order 2. In this way, the CPU 11 outputs the new procedure in the system after the change and the change location of the operation for the existing procedure.

According to the procedure creation device 10, it is possible to create a procedure that diverts an existing procedure before the change according to a change in the elements constituting the system. By using the extracted partial procedure to create a new procedure in the updated system from the existing procedure, it is possible to prevent changes to the existing procedure with a track record as much as possible.
According to the procedure creation device 10, since the change range of the operation procedure can be acquired before the system change, the overall influence can be measured. As a result, it is possible to review the situation of the system change so as to suppress the scope of influence on the operation.

  When a part of the automatically generated procedure is extracted as a component flow, when the extracted component flow includes a component procedure at the time of extracting the component procedure, the system configuration that generates the component procedure can be acquired. Thereby, it can be set as the system configuration requirement in the case where the component flow is applied to other procedures.

Embodiment 2
The second embodiment relates to a form in which the partial procedure is diverted. When the procedure creation device 10 automatically generates a procedure, the procedure creation device 10 stores the extracted partial procedure and the related information 22 of the element operated in the partial procedure in association with each other in the hard disk 14. When creating a new procedure for another system change, the procedure creating apparatus 10 creates a new procedure by using the partial procedure stored in the hard disk 14.
In the second embodiment, the same reference numerals are assigned to the same components as those in the first embodiment, and detailed description thereof is omitted.

FIG. 38 is a functional block diagram illustrating a functional configuration example of the procedure creation device 10. In FIG. 38, many of the functional units that overlap the functional block diagram of FIG. 17 are omitted. The procedure creation device 10 includes a partial procedure storage unit 800 and a post-change procedure creation unit 900.
The partial procedure accumulating unit 800 is a functional unit that stores the partial procedure extracted by the partial procedure extracting unit 400 in the partial procedure data 1D in association with the related information 22 of the element operated in the partial procedure. The partial procedure data 1D is a storage unit that accumulates partial procedures.

  FIG. 39 is an explanatory diagram showing an example of the data layout of the partial procedure data 1D. Although the partial procedure data 1D in FIG. 39 is in a table format, it is needless to say that the partial procedure data 1D may be in other data formats. The partial procedure data 1D includes a management ID, a partial procedure ID, and a corresponding system configuration. The management ID is an identification symbol that identifies the data of the partial procedure data 1D. The partial procedure ID is an identification symbol that identifies the partial procedure. The correspondence system configuration is related information 22 between elements associated with partial procedures.

  The post-change procedure creation unit 900 is a functional unit that creates a new procedure for another system change using the partial procedure stored in the partial procedure data 1D by the partial procedure storage unit 800. Another system change is a system change related to a subsequent version upgrade for a target system update in which the partial procedure storage unit 800 stores the partial procedure in the partial procedure data 1D. Alternatively, another system change is an update of another system different from the target system in which the partial procedure accumulation unit 800 accumulates the partial procedure in the partial procedure data 1D. In any case, the procedure created by the post-change procedure creation unit 900 is performed for a system change different from the target system change for which the partial procedure storage unit 800 has accumulated the partial procedure in the partial procedure data 1D.

  The post-change procedure creation unit 900 inputs an existing procedure and difference information based on system configuration information before and after system update. The difference information includes related information 22 relating to the element of the difference. The post-change procedure creating unit 900 searches the partial procedure data 1D for a partial procedure corresponding to the related information 22 relating to the difference element before and after the system change for the post-change system to be created. Then, the post-change procedure creating unit 900 executes the existing procedure change necessity determination process shown in FIG. 30 using the searched partial procedure, and creates a new procedure for another system change.

  The partial procedure accumulation process will be described. In step S13 of the partial procedure extraction process shown in FIG. 27, the CPU 11 determines whether or not the selected node corresponds to a difference element. In the second embodiment, when the CPU 11 determines that the selected node corresponds to the difference element (step S13: YES), after executing the process of acquiring the related information 22 related to the difference corresponding to the selected node, Step S14 is executed. That is, the CPU 11 acquires related information 22 relating to the difference corresponding to the selected node between step S13 and step S14.

  The CPU 11 stores the acquired related information 22 and the extracted partial procedure in the partial procedure data 1D in association with each other in the output process in step S18 of the partial procedure extraction process shown in FIG. The data of management ID = 001, 002 in FIG. 39 exemplifies partial procedure 1 and partial procedure 2 in FIG. 26 and related information 22 related to the difference information in FIG. 23B, respectively.

  In addition, when registering new data in the partial procedure data 1D, the CPU 11 scans the partial procedure data 1D to check whether the same partial procedure as the partial procedure corresponding to the related information 22 has already been registered in the partial procedure data 1D. To make a decision. When the CPU 11 determines that the same partial procedure has been registered in the partial procedure data 1D, the CPU 11 does not register new data in the partial procedure data 1D in order to avoid duplicate registration. On the other hand, if the CPU 11 determines that the same partial procedure has not been registered in the partial procedure data 1D, the CPU 11 generates a new management ID and registers the new data in the partial procedure data 1D.

FIG. 40 is a flowchart illustrating an example of the procedure of the partial procedure accumulation process.
CPU11 extracts a difference from the element which comprises the system before and after a change (step S41). The CPU 11 automatically generates a procedure before or after the change based on the received operation target element and operation item, configuration information in the system after or before the change, and a procedure automatic generation rule (step S42). CPU11 extracts a partial procedure according to the procedure shown in FIG. 27 (step S43). In step S43, the CPU 11 acquires related information 22 between elements corresponding to the partial procedure. The CPU 11 stores the related information 22 between the acquired elements and the extracted partial procedure in the partial procedure data 1D in association with each other, thereby accumulating the partial procedure in the hard disk 14 (step S44) and ends the process.

FIG. 41 is a flowchart illustrating an exemplary procedure of post-change procedure creation processing.
The CPU 11 extracts difference information in the system before and after the change related to another system change (step S51). The difference information in step S51 includes one or a plurality of related information 22 between the elements of the difference. The CPU 11 selects unprocessed related information 22 from the extracted difference information (step S52). The CPU 11 searches the partial procedure data 1D for a partial procedure corresponding to the selected related information 22 (step S53). The CPU 11 determines whether the search is successful (step S54). When the CPU 11 determines that the search is successful (step S54: YES), the CPU 11 executes the existing procedure change necessity determination process shown in FIG. 30 (step S55).

  When it is determined that the search has not been successful (step S54: NO), the CPU 11 executes the procedure automatic generation process described in the first embodiment (step S56). The CPU 11 extracts a partial procedure corresponding to the related information 22 selected in step S52 from the procedure automatically generated by the procedure automatic generation process (step S57). The CPU 11 stores the extracted partial procedure in the partial procedure data 1D in association with the related information selected in step S52 (step S58), and advances the process to step S55. The CPU 11 determines whether all the related information 22 has been processed (step S59). If the CPU 11 determines that all the related information 22 has not been processed (step S59: NO), the process returns to step S52. CPU11 complete | finishes a process, when it determines with having processed all the relevant information 22 (step S59: YES).

  According to the procedure creation device 10, a partial procedure can be diverted. The procedure creation apparatus 10 reuses the partial procedure by storing the extracted partial procedure in the storage device in the same manner that the existing procedure with an operation record should be used as much as possible. Thereby, the procedure creation apparatus 10 can improve the processing speed of creating a new procedure and a changed part of the system configuration.

  The operation unit 17 is an example of a reception unit. The CPU 11 is an example of an extraction unit, a generation unit, a second procedure extraction unit, a determination unit, a setting unit, and an output unit. The RAM 13 or the hard disk 14 is an example of a storage unit.

  Regarding the above embodiment, the following additional notes are disclosed.

(Appendix 1)
A procedure creation program for causing a computer to execute a process for creating a procedure after change from a procedure before change for operating an element when a change occurs in hardware or software elements constituting the system,
Extract differences related to system elements before and after the change,
Based on the rule for generating the operation target element and operation item, the changed system configuration information and the changed procedure, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
A procedure creation program that causes a computer to execute a process that sets the processed procedure as the third procedure after the change.

(Appendix 2)
A procedure creation program for causing a computer to execute a process for creating a procedure after change from a procedure before change for operating an element when a change occurs in hardware or software elements constituting the system,
Extract the system elements before and after the change and the differences related to the relationship between the elements,
Based on the rule for generating the operation target element and operation item, the changed system configuration information and the changed procedure, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
Determine whether the processed procedure is consistent with the association between the elements related to the difference,
A procedure creation program that causes a computer to execute a process that sets the processed procedure as the third procedure if it is determined that they match.

(Appendix 3)
When the process for extracting the difference extracts an element added to the system before the change or an element whose relation has been changed from the system before the change, it is determined whether the second procedure is included in the procedure before the change And
The procedure creation program according to supplementary note 1 or supplementary note 2, wherein when determining that the second procedure is not included in the procedure before the change, the second procedure is arranged at the beginning or end of the procedure before the change.

(Appendix 4)
The procedure creation program according to attachment 3, wherein, when it is determined that the second procedure is included in the procedure before the change, the procedure before the change is set as the third procedure.

(Appendix 5)
Extract differences related to the relationship between system elements before and after the change,
When it is determined that the second procedure is not included in the procedure before the change, it is determined whether one operation performed in the second procedure is included in the operation performed in the procedure before the change,
When it is determined that the one operation is not included in the operation performed in the procedure before the change, the one operation is arranged at the beginning or the end of the procedure before the change,
Determining whether or not the pre-change procedure including the arranged one operation is consistent with the association between the elements related to the difference;
The procedure creation program according to supplementary note 3 or supplementary note 4, wherein when it is determined to be consistent, the pre-change procedure including the one operation is set as a third procedure.

(Appendix 6)
When it is determined that the procedure before the change including the one operation is not consistent with the association between the elements related to the difference, the one operation is arranged between the procedures before the change,
Determining whether or not the pre-change procedure including the arranged one operation is consistent with the association between the elements related to the difference;
The procedure creation program according to appendix 5, wherein when it is determined that the steps match, the procedure before the change including the one operation is set as a third procedure.

(Appendix 7)
Based on the operation target element and operation item, the configuration information of the system before the change, and the rules for generating the procedure before the change, the fourth procedure before the change is generated,
From the generated fourth procedure before the change, extract the second procedure for operating the element related to the difference,
When the process of extracting the difference has extracted an element deleted from the system before the change, it is determined whether or not all of the elements operated in the second procedure are not included in the configuration information of the system after the change,
If it is determined that not all of the elements are included in the configuration information of the system after the change, the procedure in which the second procedure is deleted from the procedure before the change is set as the third procedure. Any one of Appendix 1 to Appendix 6 The procedure creation program described in one.

(Appendix 8)
When some of the elements operated in the second procedure are not included in the system configuration information after the change, operations for elements not included in the system configuration information after the change among the elements operated in the second procedure The procedure creation program according to appendix 7, wherein the procedure that is deleted from the procedure before the change is set as the third procedure

(Appendix 9)
The procedure creation program according to any one of Supplementary Note 1 to Supplementary Note 8, wherein, when the second procedure includes a procedure that is prohibited from being changed, the generated first procedure after the change is set as a third procedure.

(Appendix 10)
The procedure creation program according to any one of Supplementary Note 1 to Supplementary Note 9, wherein the second procedure and an association between elements operated in the second procedure are associated with each other and stored in an accessible storage unit.

(Appendix 11)
For the second system different from the system, extract the difference related to the relationship between the elements of the second system before and after the change,
Based on the relationship between the extracted elements related to the difference, search the second procedure from the storage unit,
Based on the searched second procedure, process the procedure related to the second system before the change,
The procedure creation program according to appendix 10, wherein the processed procedure is set as the third procedure of the second system.

(Appendix 12)
A procedure creation method for creating a post-change procedure from a pre-change procedure for operating an element when a change occurs in hardware or software elements that constitute the system,
Extract differences related to system elements before and after the change,
Based on the rule for generating the operation target element and operation item, the system configuration information after the change and the procedure before the change, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
Procedure creation method that sets the processed procedure as the third procedure after the change.

(Appendix 13)
A procedure creation device that creates a post-change procedure from a pre-change procedure for operating an element when a change occurs in hardware or software elements that constitute the system,
An extraction unit for extracting a difference related to system elements before and after the change;
A reception unit that receives an operation target element and an operation item;
Based on the elements and operation items received by the receiving unit, the configuration information of the changed system, and the rules for generating the changed procedure, a generating unit that generates the first procedure after the change,
A second procedure extraction unit for extracting a second procedure for operating an element related to the difference extracted by the extraction unit from the first procedure after the change generated by the generation unit;
Based on the second procedure extracted by the second procedure extraction unit, a processing unit that processes the procedure before the change,
A procedure creation apparatus comprising: a setting unit configured to set the procedure processed by the processing unit as a third procedure after the change.

(Appendix 14)
The procedure creation apparatus according to attachment 13, further comprising an output unit that outputs a third procedure set by the setting unit.

(Appendix 15)
The procedure creation device according to appendix 14, wherein the output unit outputs the changed content changed from the procedure before the change to the third procedure.

10 Procedure creation device 11 CPU
13 RAM
14 Hard disk 17 Operation unit 1P program

Claims (12)

A procedure creation program for causing a computer to execute a process for creating a procedure after change from a procedure before change for operating an element when a change occurs in hardware or software elements constituting the system,
Extract differences related to system elements before and after the change,
Based on the rule for generating the operation target element and operation item, the changed system configuration information and the changed procedure, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
A procedure creation program that causes a computer to execute a process that sets the processed procedure as the third procedure after the change. A procedure creation program for causing a computer to execute a process for creating a procedure after change from a procedure before change for operating an element when a change occurs in hardware or software elements constituting the system,
Extract the system elements before and after the change and the differences related to the relationship between the elements,
Based on the rule for generating the operation target element and operation item, the changed system configuration information and the changed procedure, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
Determine whether the processed procedure is consistent with the association between the elements related to the difference,
A procedure creation program that causes a computer to execute a process that sets the processed procedure as the third procedure if it is determined that they match. When the process for extracting the difference extracts an element added to the system before the change or an element whose relation has been changed from the system before the change, it is determined whether the second procedure is included in the procedure before the change And
The procedure creation program according to claim 1 or 2, wherein, when it is determined that the second procedure is not included in the procedure before the change, the second procedure is arranged at the head or the end of the procedure before the change. The procedure creation program according to claim 3, wherein when it is determined that the second procedure is included in the procedure before the change, the procedure before the change is set as the third procedure. Extract differences related to the relationship between system elements before and after the change,
When it is determined that the second procedure is not included in the procedure before the change, it is determined whether one operation performed in the second procedure is included in the operation performed in the procedure before the change,
When it is determined that the one operation is not included in the operation performed in the procedure before the change, the one operation is arranged at the beginning or the end of the procedure before the change,
Determining whether or not the pre-change procedure including the arranged one operation is consistent with the association between the elements related to the difference;
The procedure creation program according to claim 3 or 4, wherein, when it is determined that the steps match, the procedure before the change including the one operation is set as a third procedure. When it is determined that the procedure before the change including the one operation is not consistent with the association between the elements related to the difference, the one operation is arranged between the procedures before the change,
Determining whether or not the pre-change procedure including the arranged one operation is consistent with the association between the elements related to the difference;
The procedure creation program according to claim 5, wherein, when it is determined to be consistent, the procedure before the change including the one operation is set as a third procedure. Based on the operation target element and operation item, the configuration information of the system before the change, and the rules for generating the procedure before the change, the fourth procedure before the change is generated,
From the generated fourth procedure before the change, extract the second procedure for operating the element related to the difference,
When the process of extracting the difference has extracted an element deleted from the system before the change, it is determined whether or not all of the elements operated in the second procedure are not included in the configuration information of the system after the change,
If it is determined that all of the elements are not included in the configuration information of the system after the change, a procedure in which the second procedure is deleted from the procedure before the change is set as a third procedure. The procedure creation program according to any one of the above. When some of the elements operated in the second procedure are not included in the system configuration information after the change, operations for elements not included in the system configuration information after the change among the elements operated in the second procedure The procedure creation program according to claim 7, wherein a procedure that is deleted from the procedure before the change is set as a third procedure. The procedure creation program according to any one of claims 1 to 8, wherein the second procedure and an association between elements operated in the second procedure are associated with each other and stored in an accessible storage unit. For the second system different from the system, extract the difference related to the relationship between the elements of the second system before and after the change,
Based on the relationship between the extracted elements related to the difference, search the second procedure from the storage unit,
Based on the searched second procedure, process the procedure related to the second system before the change,
The procedure creation program according to claim 9, wherein the processed procedure is set as a third procedure of the second system. A procedure creation method for creating a post-change procedure from a pre-change procedure for operating an element when a change occurs in hardware or software elements that constitute the system,
Extract differences related to system elements before and after the change,
Based on the rule for generating the operation target element and operation item, the system configuration information after the change and the procedure before the change, the first procedure after the change is generated,
From the generated first procedure after the change, extract the second procedure for operating the element related to the difference,
Based on the extracted second procedure, process the pre-change procedure,
Procedure creation method that sets the processed procedure as the third procedure after the change. A procedure creation device that creates a post-change procedure from a pre-change procedure for operating an element when a change occurs in hardware or software elements that constitute the system,
An extraction unit for extracting a difference related to system elements before and after the change;
A reception unit that receives an operation target element and an operation item;
Based on the elements and operation items received by the receiving unit, the configuration information of the changed system, and the rules for generating the changed procedure, a generating unit that generates the first procedure after the change,
A second procedure extraction unit for extracting a second procedure for operating an element related to the difference extracted by the extraction unit from the first procedure after the change generated by the generation unit;
Based on the second procedure extracted by the second procedure extraction unit, a processing unit that processes the procedure before the change,
A procedure creation apparatus comprising: a setting unit configured to set the procedure processed by the processing unit as a third procedure after the change.

Images