JP4708685B2 - CLI command input method / program / program recording medium / device, data recording medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to creation of a GUI (Graphical User Interface) for creating a command to be input to a device equipped with a CLI (Command Line Interface).
[0002]
[Prior art]
Conventionally, when constructing a device that inputs a command to a device in which a CLI is mounted using a GUI, the GUI is designed and mounted for each command or for each several commands.
[0003]
The prior art has the following problems.
[0004]
The first problem is that when the number of commands to be created by the GUI becomes enormous, the cost required for design and implementation becomes enormous at the same time. In general, command images of command input devices are often similar even when the commands are different, and it is inefficient to design and implement a dedicated GUI for each command.
[0005]
The second problem is that when the command input target device changes, it is necessary to design and re-implement the entire command input device, and the CLI command input device asset once created cannot be used. In CLI command input, the process of command input → response reception is fixed, and the command character string is almost determined in the form of command name + parameter list. It is inefficient to design and implement the input device.
[0006]
Although problems specific to CLI have not been examined, Patent Document 1 discloses an invention that solves the problem that system parameters such as commands created using a GUI cannot be used between different systems, as in the above problem. The invention described in the above.
[0007]
[Patent Document 1]
Japanese Patent Laid-Open No. 2001-134424
[Problems to be solved by the invention]
However, the invention described in Patent Document 1 discloses a method for creating and recording a system parameter, but does not disclose any specific method for inputting / reflecting the system parameter to the input target system.
[0009]
Further, since the invention described in Patent Document 1 assumes that SQL (Structured Query Language) is used, a DB (Data Base) system that stores information for creating system parameters is an RDB (relational DB). It will be limited to. The invention described in Patent Document 1 mentions reliability and ease of search as advantages of using a DB. However, reliability is not a standard function for RDBMS (relational DB system). Certainly, it is equipped in a general RDBMS, but since it is often a function unique to each RDBMS, it is not different from implementing it independently in the system. Regarding the ease of search, superiority appears when the number of search targets reaches tens of thousands, and depending on the number of search targets, the cost of introducing a database is likely to be higher. .
[0010]
An object of the present invention is to provide a CLI command input method that can handle a plurality of types of commands and command input target devices and does not use a DB for command creation.
[0011]
[Means for Solving the Problems]
In order to achieve the above object, according to the CLI command input method of the present invention, when the CLI command input device is activated, the CLI command input device generates first information and a command for generating a predetermined GUI. Reading a definition file in which second information is described, creating a predetermined GUI using the first information, and waiting for parameter input from the user via the GUI, and the GUI When a parameter is input from the user via the CLI, the CLI command input device creates a command using the parameter and the second information, and transmits the command to a device equipped with the CLI. It is characterized by having.
[0012]
The first information in the definition file includes a GUI component corresponding to the parameter input by the user and information on the constraint condition of the parameter, and the second information includes information on the command name and the parameter prefix. Including.
[0013]
As described above, since the GUI is created by reading the definition file when the CLI command input device is started up, for example, when adding or changing a GUI or a command, the first information or the second information in the definition file is used. There is no need to redesign the entire system as in the prior art.
[0014]
Furthermore, the definition file is preferably described using XML. Using XML is advantageous in terms of cost compared to the invention described in Patent Document 1. Since the actual state of XML is text, maintenance is also easier than RDB. In the present invention, since the format of the definition file is not limited, RDB may be used as necessary.
[0015]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments of the present invention will be described in detail with reference to the drawings.
[0016]
Referring to FIG. 1, a CLI command input system according to an embodiment of the present invention includes a definition file 1, a CLI command input device 2, and a CLI command input target device 3.
[0017]
The CLI command input device 2 includes a definition analysis unit 21, a GUI generation unit 22, a GUI unit 23, a command analysis unit 24, and a communication unit 25.
[0018]
The definition analysis unit 21 analyzes the definition read from the definition file 1, extracts information necessary for GUI generation and information necessary for command analysis, and outputs them to the GUI generation unit 22 and the command analysis unit 24, respectively.
[0019]
The GUI generation unit 22 generates a GUI from information necessary for GUI generation received from the definition analysis unit 21.
[0020]
The GUI unit 23 is a part that is generated by the GUI generation unit 22 and serves as an input / output interface with the user. The GUI unit 23 specifies a parameter for the input command and displays a response from the CLI command input target device 3.
[0021]
The command analysis unit 24 creates a command image to be input from parameter information input to the GUI unit 23 and information necessary for command analysis received from the definition analysis unit 21, and requests the communication unit 25 to input a command.
[0022]
The communication unit 25 controls communication with the CLI command input target device 3 and inputs the command image received from the command analysis unit 24. Further, the GUI unit 23 is requested to display a response from the CLI command input target device 3.
[0023]
The CLI command input target device 3 is an arbitrary device on which CLI is mounted. In the present embodiment, it is assumed that commands are input to the router via Telnet. The CLI command input target device 3 processes the command input from the CLI command input device 2 and returns the response.
[0024]
Referring to FIG. 2, an example of the definition file 1 is shown. The definition file 1 stores information necessary for GUI generation and information necessary for command analysis. XML (extensible Markup Language) is used for the description of the definition file 1. Although the format of the definition file is not limited to XML, the CLI command input device can be most effectively configured by describing it in XML due to the nature of the definition file. This is because the extensibility of the CLI command input device and the extensibility of XML are very compatible, and it is not necessary to develop a new parser or management system for implementation, so the development efficiency is improved. Because it is.
[0025]
Next, the flow of processing of the CLI command input system of this embodiment will be described with reference to FIG.
[0026]
First, the flow of processing when the CLI command input device 2 is activated will be described.
[0027]
In step 301, the CLI command input device 2 reads the definition file 1. Since the definition file 1 read here is an XML document as shown in FIG. 2, in step 302, the definition analysis unit 21 verifies the validity by DTD (Document Type Definition). Here, DTD defines a strict grammatical structure of an XML document. If it is determined in step 303 that the definition file 1 read here is invalid, in step 307 the activation fails and the process ends. When the validity is confirmed in step 303, the command is cut out in step 304.
[0028]
In FIG. 2, a portion surrounded by <command> tags corresponds to one command, and command information and GUI information corresponding to one command are stored therein. The command name is designated by <name>, and the prefix of each parameter of the command is designated by <prefix> in <args>. The command information is cut out and stored in the memory.
[0029]
In step 305, the GUI component is cut out. What is cut out here are the GUI components required by each parameter and their constraint conditions.
[0030]
In FIG. 2, a set of <label> and <input> in <args> represents one parameter, <label> is a parameter name, and <input> is a GUI component. Further, <type> in <input> specifies a specific GUI component, and <limit> specifies a constraint condition. Specifically, in the parameter 1 of FIG. 2, the GUI component has four items specified by <item> using combbox, and there is no restriction condition. In parameter 2, the GUI component is restricted to a value from 0 to 99 that can be input as a constraint condition using spinbox. In parameter 3, the value that can be input as a constraint condition is limited to a character string of length 12 using textfield.
[0031]
In step 306, a GUI (GUI unit 23) is constructed by the GUI generation unit 22 based on the information cut out in step 305.
[0032]
Referring to FIG. 4, an example of a GUI (GUI unit 23) that is actually constructed is shown. At this point, the GUI enters a state where it is waiting for execution.
[0033]
Next, an operation when a parameter is input to the GUI (GUI unit 23) and a loading execution instruction is issued (when the loading execution button in FIG. 4 is pressed) will be described.
[0034]
In step 308, it is checked whether the parameter input in the GUI unit 23 matches the constraint condition. If the condition is not met at step 309, an error is output at step 316 and the process returns to the waiting state for input. If the condition is met in step 309, the command analysis unit 24 performs command character string construction processing in step 310.
[0035]
In FIG. 4, it is assumed that “mif” is selected for the package, “03” for the number, and “XXX” for the node name. The command character string constructed at this time is command name + prefix of parameter 1 + value of parameter 1 + prefix + of parameter 2. That is, the command character string to be constructed is “dgt eqp mif num = 03 node = XXX”.
[0036]
In step 311, the command character string is passed to the communication unit 25, and the communication unit 25 logs in to the CLI command input target device 3 using Telnet. If the communication up to login is not processed normally in step 312, the GUI unit 23 outputs an error and returns to the input execution waiting state in step 316. When it is confirmed in step 312 that the login has been performed normally, in step 313, the command character string received from the command analysis unit 24 is input to the CLI command input target device 3. Thereafter, in step 314, the communication unit 25 receives a command input result response from the CLI command input target device 3, and requests the GUI unit 23 to output the received character string in step 315. When the response is completed, the process returns to the waiting state for input.
[0037]
【The invention's effect】
As described above, the present invention has the following effects.
[0038]
Since the CLI command input GUI is dynamically generated by the definition file, the GUI can be added / changed only by adding / changing the definition file without changing the program itself for generating the GUI. As a result, it is possible to greatly reduce labor compared to creating GUI programs one by one.
[0039]
By clarifying and disclosing the interface of the command analysis unit 24 → the communication unit 25 and the communication unit 25 → the GUI unit 23, it is possible to replace the communication unit 25 only with the CLI command input target device and replace the CLI. Commands can be input to the device regardless of the protocol used in the CLI.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a CLI command input system according to an embodiment of the present invention.
FIG. 2 is a diagram showing an example of a definition file 1;
FIG. 3 is a flowchart showing a flow of processing of the CLI command input system of the present embodiment.
FIG. 4 is a diagram illustrating an example of a GUI generated by a CLI command input device 2;
[Explanation of symbols]
1 Definition File 2 CLI Command Input Device 3 CLI Command Input Target Device 21 Definition Analysis Unit 22 GUI Generation Unit 23 GUI Unit 24 Command Analysis Unit 25 Communication Units 301 to 316 Steps

Claims (13)

In a method in which a CLI command input device inputs a CLI command to a device mounted with CLI via the GUI,
When the CLI command input device is activated, the CLI command input device reads a definition file in which first information for creating a predetermined GUI and second information for creating a command are described. Creating the predetermined GUI using the first information and waiting for parameter input from a user via the predetermined GUI;
When a parameter is input from a user via the predetermined GUI, the CLI command input device creates a command using the parameter and the second information, and the command is mounted on the CLI. A method comprising: transmitting to a device. The method according to claim 1, further comprising: displaying the response on the predetermined GUI when the CLI command input device receives a response to the command from a device implementing the CLI. The first information includes a GUI component corresponding to the parameter and information on a constraint condition of the parameter, and the second information includes information on a command name and a prefix of the parameter. Or the method of 2. The method according to claim 1, wherein the definition file is described using XML. The program which makes a computer perform each step of any one of Claim 1 to 4. 5. A computer-readable recording medium on which a program for causing a computer to execute each step according to claim 1 is recorded. In a CLI command input device that inputs a CLI command to a device equipped with a CLI via the GUI,
When the CLI command input device is activated, a definition file in which first information for creating a predetermined GUI and second information for creating a command is described is read, and the first information is used. Means for creating the predetermined GUI and waiting for parameter input from the user via the predetermined GUI;
When a parameter is input from a user via the predetermined GUI, a command is created using the parameter and the second information, and the command is transmitted to a device that implements the CLI. A CLI command input device characterized by comprising: The CLI command input device according to claim 7, further comprising means for displaying the response on the predetermined GUI when a response to the command is received from a device equipped with the CLI. 8. The first information includes a GUI component corresponding to the parameter and information on a constraint condition of the parameter, and the second information includes information on a command name and a prefix of the parameter. Or a CLI command input device according to 8; The CLI command input device according to claim 7, wherein the definition file is described using XML. In addition to the first information for creating the predetermined GUI and the parameters input by the user from the predetermined GUI created by the CLI command input device based on the first information, the device implementing the CLI A data recording medium on which a definition file including second information for creating a command to be input is recorded. 12. The first information includes a GUI component corresponding to the parameter and information on a constraint condition of the parameter, and the second information includes information on a command name and a prefix of the parameter. The data recording medium described in 1. The data recording medium according to claim 11 or 12, wherein the first information and the second information are described by XMR.

Images