JP6214818B2 - Command management apparatus, command management method, and command management program - Google Patents

Description

  The present invention relates to command execution.

Currently, in operations (disaster response operations, failure response operations, etc.) for computer systems, it is common for an operator to read a command to be executed from a document, and the operator manually presses the read command one by one. Is.
As described above, when an operator's manual operation is involved, there is a possibility that a work mistake or a work leakage may occur.

Some existing operation management software automatically executes scripts according to a set schedule.
However, with this operation management software, the agent must be installed on all target servers.
Further, with this operation management software, it is necessary to newly develop workflow definitions and scripts in Run Book Automation (RBA: a function for automating the IT operation management process).
For this reason, there is a concern about an increase in development load in this operation management software.

For servers where RBA cannot be installed, it is possible to introduce a command execution support tool that creates commands as templates and saves command execution. However, the operator must select commands to be executed and input arguments. Must be done by work.
Therefore, even if this command execution support tool is introduced, there is a possibility that an operation error or an operation omission may occur because an operator's manual operation is involved.

As a method for enabling a command to be automatically executed without manual operation by an operator, there is a method of surrounding a command with a tag and automatically identifying the command by the tag.
In Patent Document 1, Patent Document 2, and Patent Document 3, there is a technique in which a tag is set for each command in an execution processing script (for example, a script described in a markup language such as XML), and the command is read based on the tag. It is disclosed.

JP 2002-342086 A JP 2003-216427 A JP 2005-122377 A

However, in Patent Document 1, Patent Document 2, and Patent Document 3, it is necessary to create an execution processing script, and the development load is large.
In addition, the above-described existing operation management software requires a workflow definition in RBA and a new development of a script, resulting in a large development load.
Further, even if an operation of using a command execution support tool is performed on a server to which RBA cannot be introduced, an operation by a worker's manual operation is involved, so that a work error or work leakage occurs.

  The present invention has been made in view of such circumstances, and is intended to automate command execution and prevent operator errors and omissions without creating a new script for command execution. With a purpose.

The command management device according to the present invention is:
A delimiter is extracted from a second document file generated by adding an execution method key and a delimiter, which are identifiers of a command execution method, to each command in the first document file including a plurality of commands, and the command A command reading unit that reads from the second document file a combination of the execution method key and the command set;
An execution method determination unit that determines an execution method of a command included in the command set based on an execution method key included in the command set for each command set read by the command reading unit;
For each command set read by the command reading unit, a command execution unit that executes a command included in the command set with the execution method determined by the execution method determination unit.

According to the present invention, the command and the execution method key can be read from the second document file generated from the first document file.
For this reason, command execution can be automated without creating a new script for command execution, and operator errors and omissions can be prevented.

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. FIG. 6 shows an example of a second document file according to the first embodiment. FIG. 4 is a diagram showing an example of an execution method table according to the first embodiment. The flowchart figure which shows the operation example of the worker at the time of starting of the command automatic execution part which concerns on Embodiment 1, and a command automatic execution part. FIG. 4 is a flowchart showing an operation example of a command reading unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of an execution method determination unit according to the first embodiment. FIG. 6 is a flowchart showing an operation example of a command execution unit according to the first embodiment. FIG. 10 is a diagram showing an example of a second document file according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a command execution unit according to the second embodiment. FIG. 10 is a diagram showing a system configuration example according to the third embodiment. FIG. 10 is a flowchart showing an example of operation of an operator and a command automatic execution unit when a command automatic execution unit according to the third embodiment is activated. The figure which shows the hardware structural example of the command management apparatus which concerns on Embodiment 1-3.

Embodiment 1 FIG.
*** Explanation of configuration ***
FIG. 1 shows a system configuration example according to the present embodiment.

The worker use terminal device 100 is a terminal device used by a worker.
The worker use terminal device 100 is also simply referred to as a work user terminal.

The work execution terminal device 200 is a terminal device that is remotely accessed by the worker use terminal device 100.
The work execution terminal device 200 corresponds to an example of a command management device.
The work execution terminal device 200 is also simply referred to as a work execution terminal.

The file server device 700 is a server device that stores the second document file 800.
In the second document file 800, a command and an execution method key that is an identifier of a command execution method and a command reading tag that is a delimiter are described.
Note that the file server device 700 is also simply referred to as a file server.

A DB (database) server apparatus 1300 is a server apparatus having an execution method key DB 1000.
An execution method table 1100 is stored in the execution method key DB 1000.
The execution method table 1100 describes a plurality of execution method keys, and a command execution method is defined for each execution method key.
The DB server device 1300 is also simply referred to as a DB server.

The execution target server device 1200 is a server device on which the work execution terminal device 200 executes a command.
Note that the execution target server device 1200 is also simply referred to as an execution target server.

The work execution terminal device 200 includes an automatic command execution unit 300 as a functional module.
The automatic command execution unit 300 includes a command reading unit 400, an execution method determination unit 500, and a command execution unit 600.
The command reading unit 400 extracts a command reading tag as a delimiter from the second document file 800 and reads a combination of the command and the execution method key from the second document file 800.
A combination of a command and an execution method key is called a command set.
The execution method determination unit 500 determines, for each command set read by the command reading unit 400, the execution method of the command included in the command set based on the execution method key included in the command set.
More specifically, the execution method determination unit 500 accesses the DB server device 1300 using the execution method key included in the command set, and obtains information on the command execution method from the DB server device 1300.
The command execution unit 600 executes a command included in the command set by the execution method determined by the execution method determination unit 500 for each command set read by the command reading unit 400.

In the present embodiment, every time the command reading unit 400 reads a command set from the second document file 800, the command reading unit 400 calls the execution method determination unit 500.
The execution method determination unit 500 executes the command included in the read command set based on the execution method key included in the command set read by the command reading unit 400 each time it is called by the command reading unit 400. And the command execution unit 600 is called.
Each time the command execution unit 600 is called by the execution method determination unit 500, the command execution unit 600 executes a command included in the command set read by the command reading unit 400 using the execution method determined by the execution method determination unit 500.

FIG. 2 shows an example of the second document file 800.
In the second document file 800, a command (for example, “ps-eaf | grep process” in FIG. 2) is sandwiched between two types of tags.
That is, in the second document file 800, a command is sandwiched between an execution method key (for example, “ccccc” in FIG. 2) and a command reading tag (for example, “xxxx” in FIG. 2).
An execution method key is described immediately before and after the command, and a command reading tag is described outside the command and the execution method key.
Each of the command, command reading tag, and execution method key has a line feed, and a line feed code (for example, “¥ n”) is set before and after.
The second document file 800 is a document file generated by adding an execution method key and a command reading tag to each command in the first document file 850 including only a comment, a line feed code, and a command.
That is, in the first document file 850, in addition to the comment and the line feed code, only “ps-eaf | grep process”, “1”, and “¥¥ abc ¥ def ¥ zzzz.exe” are described. .
As described above, in the second document file 800, two execution method keys “ccccc” and two command reading tags “xxxx” are added to the command “ps-eaf | grep process”.
Similarly, in the second document file 800, two execution method keys “aaaaaa” and two command reading tags “xxxx” are added to the command “1”.
Similarly, in the second document file 800, two execution method keys “fffff” and two command reading tags “xxxx” are added to the command “¥¥ abc ¥ def ¥ zzzz.exe”.

FIG. 3 shows an example of the execution method table 1100.
The execution method table 1100 includes an execution method key column in which an execution method key is described, and a method column in which an execution method corresponding to the execution method key described in the execution method key column is described.
In the method column, a command execution method is described.

*** Explanation of operation ***
4, 5, 6, and 7 show an operation flow according to the present embodiment.
FIG. 4 shows an operation example of the worker who uses the operator terminal device 100 and the command automatic execution unit 300 when the command automatic execution unit 300 is activated.
FIG. 5 shows an operation example of the command reading unit 400.
FIG. 6 shows an operation example of the execution method determination unit 500.
FIG. 7 shows an operation example of the command execution unit 600.
4 to 7 show processing examples of the command management method and command management program of the present application.

In FIG. 4, the worker logs in to the worker use terminal device 100 (S1).
The worker remotely logs in to the work execution terminal device 200 from the worker use terminal device 100 (S2) and activates the command automatic execution unit 300 (S3).
The command automatic execution unit 300 accesses the file server device 700 and displays a document file list for selecting the second document file 800 on the display of the operator terminal device 100 (S4).
The operator selects the second document file 800 (S5).
The command automatic execution unit 300 tries to read the second document file 800, and when the second document file 800 is read (YES in S6), the command reading unit 400 is called (S7).
The operation of the command reading unit 400 will be described with reference to FIG.
On the other hand, when the second document file 800 cannot be read (NO in S6), the command automatic execution unit 300 displays a reading error screen on the display of the worker terminal device 100 (S9), and processing Exit.

In FIG. 5, the command reading unit 400 refers to the second document file 800 read in S6 of FIG. 4 (S11), and reads the character string in the second document file 800 (S12).
If a command reading tag (for example, “¥ xxxxxxxx ¥ n” in FIG. 2) sandwiched between line feed codes in the process of S <b> 12 can be retrieved (YES in S <b> 13), the command reading unit 400 sandwiches between the retrieved line feed codes. The command reading tag to be stored is stored in the memory (S14).
Next, the command reading unit 400 reads the character string of the second document file 800 again immediately after the reading position of S13 (S15).
If a command reading tag (for example, “¥ xxxxxxxx ¥ n” in FIG. 2) sandwiched between the same line reading codes as the command reading tags stored in the memory in S <b> 14 can be retrieved (YES in S <b> 16). ), The command reading unit 400 extends from the last line feed code of the command reading tag sandwiched by the line feed code searched in S13 to the first line feed code of the command reading tag sandwiched by the line feed code searched in S16. A character string between them (for example, “¥ nccccc ¥ nps−eaf | grep process ¥ nccccc ¥ n” in FIG. 2) is cut out (S17).
Then, the command reading unit 400 stores the character string cut out in S17 as a command set in the memory (S18).
When S18 is completed, the command reading unit 400 calls the execution method determination unit 500 (S19).
In the case of NO in S13 or NO in S16, the command reading unit 400 displays an error screen with no search target on the display of the operator terminal device 100 (S21), and ends the process (S99). ).
The process shown in FIG. 5 corresponds to an example of a command reading process.

In FIG. 6, the execution method determination unit 500 reads the command set stored in the memory in S18 of FIG. 5 (S23).
Next, the execution method determination unit 500 determines whether or not an execution method key (for example, “¥ nccccc ¥ n” in FIG. 2) sandwiched between the command set and the line feed code can be retrieved, and the command set uses the line feed code. If the execution method key to be sandwiched can be retrieved (YES in S24), the execution method key sandwiched by the retrieved line feed code is stored in the memory (S25).
Next, the execution method determination unit 500 deletes the line feed code from the execution method key sandwiched between the line feed codes stored in the memory in S25, and stores the execution method key after removal of the line feed code in the memory (S26) (for example, “ Delete two "\ n" from "\ nccccc \ n" and store "ccccc" in the memory).
Next, the execution method determination unit 500 reads the command set again immediately after the reading position in S24 (S27).
If an execution method key (for example, “¥ nccccc ¥ n” in FIG. 2) sandwiched by the same line feed code as the execution method key sandwiched by the line feed code stored in the memory in S25 can be retrieved (YES in S28). The execution method determination unit 500 determines the characters between the last line feed code of the execution method key sandwiched by the line feed code searched in S24 and the first line feed code of the execution method key sandwiched by the line feed code searched in S28. A column (for example, “¥ nps−eaf | grep process ¥ n” in FIG. 2) is cut out (S29).
Then, the execution method determination unit 500 stores the character string cut out in S29 in the memory as command information (S30).
Next, the execution method determination unit 500 accesses the DB server device 1300, and in the execution method table 1100 in the execution method key DB 1000, an execution method key that is the same as the execution method key stored in the memory in S26 is described. Look for method key columns.
If the corresponding execution method key column can be searched (YES in S31), the data (execution method) of the method column corresponding to this execution method key column is acquired, and the acquired data is stored in the memory as an execution method argument (S32). ).
When S32 is completed, the execution method determination unit 500 calls the command execution unit 600 (S33).
In the case of NO in S24 or NO in S28, the execution method determination unit 500 displays an error screen with no search target on the display of the worker terminal device 100 (S36), and ends the process (S36). S99).
If NO in S31, the execution method determination unit 500 displays an error screen with no target column data on the display of the operator terminal device 100 (S35), and ends the process (S99).
The process illustrated in FIG. 6 corresponds to an example of an execution method determination process.

In FIG. 7, the command execution unit 600 reads the command information stored in the memory in S30 (S38).
Next, the command execution unit 600 removes the line feed code from the command information read in S38, and stores the command after removal of the line feed code in the memory (S39) (for example, “\ nps-eaf | grep in FIG. 2). delete two "\ n" from "process \ n" and store "ps-eaf | grep process" in memory).
Next, the command execution unit 600 reads the execution method argument stored in the memory in S32 (S40), and tries to call a process corresponding to the execution method argument.
When the process corresponding to the execution method argument can be called (YES in S41), the command execution unit 600 uses the execution method corresponding to the execution method argument to execute the command stored in the memory in S39 for the execution target server device 1200. Is executed (S42).
When S42 is completed, the command execution unit 600 determines whether there is a character string that has not yet been read.
Specifically, the command execution unit 600 determines whether there is a character string after the line feed code following the command reading tag searched in S16 of FIG.
If there is a character string that has not yet been read (YES in S43), the processing after S12 is performed (S44).
In the case of NO in S41, the command execution unit 600 displays an error screen with no corresponding process on the display of the worker use terminal device 100 (S46), and ends the process (S99).
If NO in S43, the command execution unit 600 displays a process end screen on the display of the operator terminal device 100, and ends the process (S99).
The process shown in FIG. 7 corresponds to an example of a command execution process.

*** Explanation of effects ***
As described above, in the present embodiment, by reading the command and the execution method key from the second document file in which the command included in the first document file is sandwiched between the command reading tag and the execution method key, Commands prepared in advance can be automatically executed by an appropriate execution method.
For this reason, according to this Embodiment, an operator's work mistake and procedure mistake can be prevented, and reduction of work load can be aimed at.
In addition, since the second document file using the first document file prepared in advance is used, the development load on the developer can be reduced.

Embodiment 2. FIG.
In the first embodiment described above, the command set is read one by one from the second document file 800, and the command included in the command set is automatically executed by the corresponding execution method each time the command set is read. Indicated.
In the present embodiment, a value representing the execution order of commands is set in the command reading tag, the command set read from the second document file 800 is listed, and the command set includes the command reading tag values in the order of values. An example of automatically executing a command to be executed by a corresponding execution method will be described.

*** Explanation of configuration ***
FIG. 8 shows an example of the second document file 800 according to the present embodiment.
In the second document file 800 of FIG. 8, numerical values (for example, “e1”, “e2”, “e3” in FIG. 8) are described in the command reading tag.
In order to describe numerical values in the command reading tag, it is necessary to set the reading order of the command reading tag in advance.
FIG. 8 shows that the commands are executed in the order of e1, e2, and e3.

The system configuration example according to the present embodiment is the same as that shown in FIG.
However, in this embodiment, the operation of the command execution unit 600 is different.
In this embodiment, each time the command execution unit 600 is called by the execution method determination unit 500, the command execution unit 600 reads the execution order value described in the command reading tag of the command set read by the command reading unit 400, and the command A set of the command included in the command set read by the reading unit 400 and the execution method determined by the execution method determination unit 500 is registered in the execution list.
Then, the command execution unit 600 registers pairs of execution order values, commands, and execution methods in the execution list for all command sets included in the second document file 800 of FIG. The command registered in the execution list is executed in accordance with the execution method registered in the execution list in accordance with the execution order value.
Hereinafter, differences from the first embodiment will be mainly described.
Matters not described below are the same as those in the first embodiment.

*** Explanation of operation ***
Next, the operation will be described.
The steps up to calling the command execution unit 600 (S34) in FIGS. 4, 5, and 6 are the same as those in the first embodiment, and thus the description thereof is omitted.
Hereinafter, internal processing of the command execution unit 600 according to the present embodiment will be described with reference to FIG.

The command execution unit 600 reads the command information stored in the memory at S30 (S38).
Next, the command execution unit 600 removes the line feed code from the command information read in S38, and stores the command after removal of the line feed code in the memory (S39) (for example, “\ nps-eaf | grep in FIG. 2). Delete two "\ n" from "process \ n" and store "ps-eaf | grep process" in memory).
Next, the command execution unit 600 reads the execution method argument stored in the memory in S32 (S40).
Further, the command execution unit 600 acquires a command reading tag sandwiched between the line feed codes stored in the memory in S14, deletes the line feed code, and executes the command read tags after the line feed code is deleted. The data is stored in the memory (S47).
Next, the command execution unit 600 associates the execution order data stored in the memory in S47 with the execution method argument read in S40 and the command stored in the memory in S39 (for example, the execution order data, the execution method argument, and the command Are combined with “: e1: command: ps−eaf | grep process”), and the execution order data, the execution method argument, and the command are registered in the execution list (S48).
Next, the command execution unit 600 determines whether there is a character string that has not yet been read.
Specifically, the command execution unit 600 determines whether there is a character string after the line feed code following the command reading tag searched in S16 of FIG.
If there is a character string that has not yet been read (YES in S49), the processing after S12 is performed (S54).
When all the character strings have been read (NO in S49), the execution list includes “e1: command: ps-eaf | grep process; e2: argument: 1; e3: file: “¥¥ abc ¥ def ¥ zzzz.exe” is registered.
The command execution unit 600 calls the combination of the execution method argument and the command according to the values of the execution order (“1”, “2”, “3” of e1, e2, and e3) (S50).
In the above example, the command execution unit 600 calls “command: ps-eaf | grep process” associated with e1, and then calls “argument: 1” associated with e2. Next, “file: ¥¥ abc ¥ def ¥ zzzz.exe” associated with e <b> 3 is called.
And the command execution part 600 calls the process according to an execution system argument about each called combination.
When the process corresponding to the execution method argument can be called (YES in S51), the command execution unit 600 executes the command to the execution target server device 1200 using the execution method corresponding to the execution method argument (S52). .
When S52 is completed, the command execution unit 600 displays a process end screen on the display of the worker use terminal device 100, and ends the process (S99).
If NO in S51, the command execution unit 600 displays an error screen with no corresponding process on the display of the operator terminal device 100 (S55), and ends the process (S99).

*** Explanation of effects ***
As described above, in this embodiment, the commands to be executed are listed in a lump, and the commands are continuously executed according to a predetermined order, thereby improving the throughput without losing the advantages of the first embodiment. Can be expected.

Embodiment 3 FIG.
In the first embodiment and the second embodiment described above, the example in which the command is executed by the client application has been described. In the present embodiment, an example in which the command is executed by the Web application will be described.

*** Explanation of configuration ***
FIG. 10 shows a system configuration example of the present embodiment.
In FIG. 10, the operator terminal device 100, the file server device 700, the second document file 800, the execution method key DB 1000, the execution method table 1100, the execution target server device 1200, and the DB server device 1300 are as shown in FIG. This is the same and will not be described.
The work execution terminal device 200 is a terminal device that is remotely accessed by the worker use terminal device 100.
The application server device 1400 is a server device that the work execution terminal device 200 accesses from a browser.
In the present embodiment, the application server device 1400 corresponds to an example of a command management device.
The command automatic execution unit 300, the command reading unit 400, the execution method determination unit 500, and the command execution unit 600 included in the application server device 1400 are the same as those described in the first embodiment. Perform the operation described.
Hereinafter, differences from the first embodiment will be mainly described.
Matters not described below are the same as those in the first embodiment.

*** Explanation of operation ***
FIG. 11 shows an operation example of the operator and the command automatic execution unit 300 when the command automatic execution unit 300 is activated.
FIG. 11 corresponds to FIG.
In FIG. 11, as compared with FIG. 4, only a process (S56) for calling the command automatic execution unit 300 from the browser of the work execution terminal device 200 is added.
The processes after S1, S2, and S3 are the same as those in FIG. 4, and after S8, the processes in FIGS. 5 and 6 are performed, and then the processes in FIG. 7 and FIG. 9 are performed.

*** Explanation of effects ***
As described above, the command can be automatically executed not only in the client application shown in the first and second embodiments but also in the Web application.

*** Others ***
As mentioned above, although embodiment of this invention was described, you may implement in combination of 2 or more among these embodiment.
Alternatively, one of these embodiments may be partially implemented.
Alternatively, two or more of these embodiments may be partially combined.
In addition, this invention is not limited to these embodiment, A various change is possible as needed.
For example, in the first to third embodiments, an example in which a command is sandwiched between execution method keys and further sandwiched between command reading tags has been described. Instead, a command is sandwiched between a command reading delimiter and an execution method key. You may make it.
Specifically, an arrangement such as “xxxx”, “¥ n”, “ps−eaf | grep process”, “¥ n”, “ccccc” may be used.

*** Explanation of hardware configuration ***
Finally, a hardware configuration example of the command management device (work execution terminal device 200 or application server device 1400) will be described with reference to FIG.
The command management device is a computer.
The command management device includes hardware such as a processor 901, an auxiliary storage device 902, a memory 903, a communication device 904, an input interface 905, and a display interface 906.
The processor 901 is connected to other hardware via the signal line 910, and controls these other hardware.
The input interface 905 is connected to the input device 907.
The display interface 906 is connected to the display 908.

The processor 901 is an IC (Integrated Circuit) that performs processing.
The processor 901 is, for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or a GPU (Graphics Processing Unit).
The auxiliary storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or an HDD (Hard Disk Drive).
The memory 903 is, for example, a RAM (Random Access Memory).
The communication device 904 includes a receiver 9041 that receives data and a transmitter 9042 that transmits data.
The communication device 904 is, for example, a communication chip or a NIC (Network Interface Card).
The input interface 905 is a port to which the cable 911 of the input device 907 is connected.
The input interface 905 is, for example, a USB (Universal Serial Bus) terminal.
The display interface 906 is a port to which the cable 912 of the display 908 is connected.
The display interface 906 is, for example, a USB terminal or an HDMI (registered trademark) (High Definition Multimedia Interface) terminal.
The input device 907 is, for example, a mouse, a keyboard, or a touch panel.
The display 908 is, for example, an LCD (Liquid Crystal Display).

In the auxiliary storage device 902, the command reading unit 400, the execution method determination unit 500, and the command execution unit 600 (hereinafter, the command reading unit 400, the execution method determination unit 500, and the command execution unit 600 shown in FIG. A program that realizes the function of “denoted” is stored.
This program is loaded into the memory 903, read into the processor 901, and executed by the processor 901.
Further, the auxiliary storage device 902 also stores an OS (Operating System).
Then, at least a part of the OS is loaded into the memory 903, and the processor 901 executes a program that realizes the function of “unit” while executing the OS.
Although one processor 901 is illustrated in FIG. 12, the command management apparatus may include a plurality of processors 901.
A plurality of processors 901 may execute a program for realizing the function of “unit” in cooperation with each other.
In addition, information, data, signal values, and variable values indicating the processing results of “unit” are stored in the memory 903, the auxiliary storage device 902, or a register or cache memory in the processor 901.

The “part” may be provided as “circuitry”.
Further, “part” may be read as “circuit”, “process”, “procedure”, or “processing”.
“Circuit” and “Circuitry” include not only the processor 901 but also other types of processing circuits such as a logic IC or GA (Gate Array) or ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array). It is a concept to include.

  DESCRIPTION OF SYMBOLS 100 Worker use terminal device, 200 Work execution terminal device, 300 Command automatic execution part, 400 Command reading part, 500 Execution method determination part, 600 Command execution part, 700 File server apparatus, 800 2nd document file, 850 1st Document file, 1000 execution method key DB, 1100 execution method table, 1200 execution target server device, 1300 DB server device, 1400 application server device.

Claims (7)

A delimiter is extracted from a second document file generated by adding an execution method key and a delimiter, which are identifiers of a command execution method, to each command in the first document file including a plurality of commands, and the command A command reading unit that reads from the second document file a combination of the execution method key and the command set;
An execution method determination unit that determines an execution method of a command included in the command set based on an execution method key included in the command set for each command set read by the command reading unit;
A command management apparatus comprising: a command execution unit that executes a command included in a command set in the execution method determined by the execution method determination unit for each command set read by the command reading unit. The command reading unit
Each time the command set is read from the second document file, the execution method determination unit is called,
The execution method determination unit
Each time it is called by the command reading unit, it determines the execution method of the command included in the read command set based on the execution method key included in the command set read by the command reading unit, and call,
The command execution unit
2. The command management according to claim 1, wherein a command included in a command set read by the command reading unit is executed by the execution method determined by the execution method determining unit every time the execution method determining unit calls the command. apparatus. The command reading unit
Each time the command set is read from the second document file in which the command execution order value is described in the delimiter, the execution method determination unit is called.
The execution method determination unit
Each time it is called by the command reading unit, it determines the execution method of the command included in the read command set based on the execution method key included in the command set read by the command reading unit, and call,
The command execution unit
Each time it is called by the execution method determination unit, the value of the execution order described in the delimiter of the command set read by the command reading unit, the command included in the command set read by the command reading unit, A set of execution methods determined by the execution method determination unit is registered in an execution list, and a set of execution order values, commands, and execution methods for all command sets included in the second document file is the execution list. 2. The command registered in the execution list is executed in accordance with an execution method registered in the execution list in accordance with an execution order value registered in the execution list after being registered in the list. Command management device. The command reading unit
A delimiter is extracted from the second document file generated when the execution method key as a tag sandwiches a command, and the delimiter as a tag sandwiches the command and the execution method key, and a command set is extracted from the second document file. The command management device according to claim 1, which is read from the command management device.   The command management apparatus according to claim 1, wherein the command management apparatus is an application server apparatus. A computer extracts a delimiter from a second document file generated by adding an execution method key and a delimiter, which are identifiers of a command execution method, to each command in a first document file including a plurality of commands. A combination of a command and an execution method key is read from the second document file as a command set,
The computer determines the execution method of the command included in the command set based on the execution method key included in the command set for each read command set,
A command management method in which the computer executes a command included in a command set by a determined execution method for each read command set. A delimiter is extracted from a second document file generated by adding an execution method key and a delimiter, which are identifiers of a command execution method, to each command in the first document file including a plurality of commands, and the command A command reading process for reading from the second document file as a command set a combination of the execution method key and
An execution method determination process for determining an execution method of a command included in the command set based on an execution method key included in the command set for each command set read by the command reading process;
A command management program for causing a computer to execute a command execution process for executing a command included in a command set by the execution method determined by the execution method determination process for each command set read by the command reading process.

Images