CN110764793A - Software tool and registration, installation and operation method and tool management system thereof - Google Patents
Software tool and registration, installation and operation method and tool management system thereof Download PDFInfo
- Publication number
- CN110764793A CN110764793A CN201911066189.3A CN201911066189A CN110764793A CN 110764793 A CN110764793 A CN 110764793A CN 201911066189 A CN201911066189 A CN 201911066189A CN 110764793 A CN110764793 A CN 110764793A
- Authority
- CN
- China
- Prior art keywords
- tool
- information
- software
- page
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000009434 installation Methods 0.000 title claims description 65
- 230000006870 function Effects 0.000 claims abstract description 28
- 230000002452 interceptive effect Effects 0.000 claims abstract description 4
- 230000001419 dependent effect Effects 0.000 claims description 38
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a software tool and a method for registering, installing and running the software tool as well as a tool management system, wherein the software tool comprises a main page, a main module, a page calling interface and a RunTool calling interface, the page calling interface is used for calling the main page, the main page is used for calling the main module, and the RunTool calling interface is used for directly calling the main module in a function mode; the main page is used as an interactive interface for a user to operate the software tool, and the main module is an execution instruction module for realizing the main service function of the software tool; the first mode is that a main page is called through a page calling interface, and a main module is called through the main page; the second is to directly call the main module through the RunTool call interface, and then call the executive program to realize the function of the software tool; the executive program of the software tool can be called in a page mode or a RunTool calling mode, and the calling mode is flexible and is not limited by a programming language.
Description
Technical Field
The invention relates to the field of software tools, in particular to a software tool, a registration method, an installation method, an operation method and a tool management system thereof.
Background
The existing software component technologies comprise corba, web service, micro service and the like, and the component technologies provide a modular development software system, improve the multiplexing degree of software modules, simplify the code structure complexity of the software system, reduce the coupling degree between the software systems and improve the production efficiency of software engineering. However, the software tool modules developed by using the component technologies can only be provided for programmers to use, common users cannot directly use the software tool modules, the programmers can use the software components for the users after secondary development, the common users cannot directly operate and manage the software components, in addition, the component technologies such as web services, micro services and the like limit the languages of codes, some of the component technologies can only use java languages, and some of the traditional programming languages cannot be effectively utilized for programming. Some modularized development platforms such as the applet software of the WeChat can only be directly used by common users and cannot be called by other applets, so that developers cannot reuse the functions of the modularized development platforms.
Disclosure of Invention
The present invention is directed to overcoming at least one of the above-mentioned disadvantages (shortcomings) of the prior art, and providing a software tool, a method for registering, installing and running the software tool, and a tool management system, which are used to solve the problem that a user cannot use or manage a component technology for a common user and a developer at the same time to limit a coding language.
The technical scheme adopted by the invention is as follows:
a software tool comprises a main page, a main module page calling interface and a RunTool calling interface, wherein the page calling interface is used for calling the main page, the main page is used for calling the main module, and the RunTool calling interface is used for directly calling the main module in a function mode; the main page is used as an interactive interface for a user to operate the software tool, and the main module is an execution instruction module for realizing the main service function of the software tool. .
The function of the software tool is realized by the executive program contained in the software tool, so the executive program contained in the software tool must be called to realize the function of the software tool, and the calling mode has two modes, wherein the first mode is that a main page is called through a page calling interface, and a main module can be called through the main page so as to realize the function of the software tool; the second is to directly call the main module through a RunTool call interface, thereby realizing the function of the main module; the executive program of the software tool can be called in a page mode and also in a RunTool calling mode, and the calling mode is flexible.
Furthermore, the software tool further comprises an auxiliary page, the auxiliary page is an auxiliary page required by a user when operating the software tool, and the main page is also used for being mutually called with the auxiliary page in a page jump mode. .
Furthermore, the software tool further comprises an auxiliary module, the auxiliary module is an execution instruction module for realizing the auxiliary service function of the software tool, and the main module is used for calling the auxiliary module in a module internal calling mode. .
Further, the RunTool calling interface is also used for being called by other software tools.
The execution program of the software tool has two calling modes, the two calling modes not only can enable a user to call when the software tool is used, but also can enable other software tools and users using other software tools to call when the software tool is used, the modes for calling the software tool are more various, and the users using the software tool are more extensive.
A method of registering a software tool, comprising the steps of:
receiving registration request information of a user requesting to register the software tool and a code package of the software tool;
adding a registration record of the software tool in a tool information table according to the registration request information; the registration record comprises a tool identifier, tool interface information, operating environment information, database information and a dependent tool identifier, wherein the tool identifier is an identifier for uniquely identifying the software tool, the tool interface information is information such as input parameters and output results required when the software tool is called by using a tool interface, the operating environment information refers to relevant information of operating environments such as a tool control system, a middleware system, a support SDK library and a hardware system required by the tool during operation, the database information is information of a database required to be connected during the operation of the tool, and the dependent tool identifier is a tool identifier of other software tools required to be depended on during the operation of the software tool.
Further, the input parameters include names, value types and related limits of the parameters, and the output result includes names, value types of the results.
Receiving registration request information for registering a software tool by a user and receiving a code package of the software tool, wherein the registration record of the tool is required to be added in a tool information table so as to record relevant information of the software tool, and the registration record comprises a tool identifier which is an identifier for uniquely identifying the software tool and is used as an identification mark when the software tool is identified; the registration record comprises operation environment information, wherein the operation environment information refers to relevant information of operation environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like required by the operation of the tool; the registration record comprises tool interface information, the information is used for connecting configuration information of the interface when the tool is called, the configuration information comprises input parameters and output results, the input parameters comprise names, value types and relevant limits of the parameters, and the output results comprise names and value types of the results; the registration record comprises database information, and the information is used for the information of the database which needs to be connected when the tool is operated so as to normally operate the tool; the registration record includes a dependent tool identifier, which is a tool identifier of other tools that the tool needs to depend on when running, which is used as information to identify the tool that the tool needs to depend on when running and/or doing further processing.
When a user requests to install a software tool, database information and running environment information corresponding to the software tool can be inquired according to a registration record in a tool information table, whether the target server has a running environment is judged according to the running environment information, and a code package of the software tool is installed on the target server only when the requirement is met; judging whether a database connected with a target server on which a user needs to install a software tool meets requirements or not according to the database information, and installing a code packet of the software tool on the target server only when the database meets the requirements; tool interface information corresponding to the software tool can be inquired according to the registration record in the tool information table, and whether the software tool can be called and/or how to call the software tool can be known according to the tool interface information; secondly, according to the registration record in the tool information table, a dependent tool set corresponding to the software tool is also inquired, namely a set formed by identifiers of other tools which need to be called when the tool runs is inquired, whether all dependent tools of the tool are installed on the target server or not is judged according to the dependent tool set, and under the condition that all dependent tools are installed, the code package of the tool is installed on the target server. Therefore, the situation that the user does not support when installing or operating the tool can be avoided, and the use experience of the user is improved.
The user can upload and register the executable software tool on the system platform and generate the registration record, so that other users can directly install and use the software tool according to the registration record, or other software tools or application programs can directly install and call according to the registration record, and the software tool allows programming by using a plurality of programming languages and has wider applicability.
Further, the database information includes a database name and a database product model, both of which are used for database information of connections that need to be used when invoking and/or further processing the tool.
A method of installing a software tool comprising the registration step as described above, further comprising the installation steps of:
receiving installation request information of a user requesting installation of a target tool, wherein the installation request information comprises a target tool identifier and target server information;
matching the tool identifier registered in the tool information table according to the target tool identifier to acquire corresponding database information and running environment information, wherein the database information is information of a database which needs to be connected when the tool runs, and the running environment information refers to relevant information of running environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like which need to be connected when the tool runs;
searching a corresponding target server according to the target server information;
judging whether the target server has the operating environment according to the operating environment information, and continuing the next judging step if the target server has the operating environment;
judging whether a database connected with the target server is consistent with database information or not according to the database information, and continuing the next judging step if the database is consistent with the database information;
according to the target tool identifier, matching the tool identifier registered in the tool information table, and acquiring a corresponding dependent tool identifier; judging whether other tools which need to be depended when the target tool runs are installed on the target server or not according to the dependent tool identifier, and if so, installing a code package of the target tool on the target server;
and adding an installation record of the target tool in an installation information table, wherein the installation record comprises a tool identifier and a tool installation state.
Receiving installation request information of a user requesting installation of a target tool, wherein the information comprises a target tool identifier used for determining the information of a specific target tool and target server information used for searching the position and the information of a specific target server to be installed by the target tool; the target tool identifier matches the tool identifier registered in the tool information table, and the tool identifier added with the registered record in the tool information table is searched through the target tool identifier, so that the database information, the operating environment information and the target tool identifier of the corresponding tool are obtained;
when a user requests to install a tool, database information and running environment information corresponding to the tool can be inquired according to a registration record in a tool information table, wherein the database information comprises a database name and a database product model, and the running environment information refers to relevant information of running environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like required by the operation of the tool; judging whether the target server has the operating environment according to the operating environment information, and continuing the next judging step if the target server has the operating environment; judging whether the target server supports the database product model or not according to the database product model, if so, continuing the next judging step, otherwise, judging that the database connected with the target server does not meet the requirement and finishing the installation step; and judging whether the target server is connected with a database corresponding to the database name or not according to the database name, if so, continuing the next judging step, otherwise, judging that the database connected with the target server does not meet the requirement, and finishing the installation step.
Inquiring a target tool identifier corresponding to the tool according to a registration record in a tool information table, wherein the target tool identifier is matched with the tool identifier registered in the tool information table, searching a dependent tool identifier corresponding to the tool registration record table through the target tool identifier, determining the information of the tool which needs to be dependent when the tool is operated and/or is subjected to processing according to the dependent working identifier, further judging whether the tool which needs to be dependent when the target tool is operated is installed on a target server, and if so, installing the target tool on the target server, namely installing a code package of the target tool.
When a user requests to install a software tool, a dependent tool set corresponding to the tool can be inquired according to a registration record in a tool information table, namely a set formed by identifiers of other tools needing to be called when the tool runs is inquired, whether all dependent tools of the tool are installed on a target server or not is judged according to the dependent tool set, and a code package of the tool is installed on the target server only under the condition that all dependent tools are installed. Therefore, the situation that the user does not support when installing the tool can be avoided, and the use experience of the user is improved.
After the above determination step is performed, finally, an installation record of the target tool is added to an installation information table, where the installation record includes a tool identifier and a tool installation state.
A method of operating a software tool comprising an installation step as described above, further comprising the following operating steps:
receiving operation request information of a user and/or a caller requesting to operate a target tool, wherein the operation request information comprises a target tool identifier and tool interface information;
according to the target tool identifier, matching the tool identifier of the installation record in the installation information table, and acquiring a corresponding tool installation state;
and judging whether the code packet of the target tool is installed on a target server or not according to the acquired tool installation state, if so, calling a main page through a page calling interface of the target tool on the target server according to the tool interface information, calling a main module through the main page, or calling the main module through a RunTool calling interface of the target tool so as to call an execution program of the main module, transmitting the value of an input parameter in a tool information interface to the main module, and returning the execution result of the software tool to a user and/or a caller by the main module.
And acquiring the installation state of the corresponding tool through the tool identifier in the installation record, and if the code package of the target tool is installed in the target server, calling the executive program of the software tool through the two calling modes so as to realize the function of the software tool.
A tool management system comprises a processor, wherein the processor is used for executing the method for registering, installing and running the software tool.
Compared with the prior art, the invention has the beneficial effects that: the calling modes of the software tools are two, and the method is more flexible, so that not only can a user directly operate and manage the software tools, including authorization, installation, use, distribution and the like, but also the software tools can be operated and managed through other software tools and/or application programs, and the method is not limited by the types of programming languages when the tools are registered, installed and operated.
Drawings
Fig. 1 is a schematic diagram of a software tool structure according to embodiment 1 of the present invention.
Fig. 2 is a code diagram of implementing a main page in embodiment 1 of the present invention.
Fig. 3 is a code diagram of a main module according to embodiment 1 of the present invention.
Fig. 4 is a schematic diagram of software tool registration in embodiment 2 of the present invention.
Fig. 5 is a tool information presentation view according to embodiment 2 of the present invention.
Fig. 6 is a schematic diagram of software tool installation according to embodiment 3 of the present invention.
Fig. 7 is an installation information presentation intention of embodiment 3 of the present invention.
Fig. 8 is a schematic diagram of the operation of the software tool according to embodiment 4 of the present invention.
Fig. 9 is a schematic diagram of a software tool management system according to embodiment 5 of the present invention.
Detailed Description
The drawings are only for purposes of illustration and are not to be construed as limiting the invention. For a better understanding of the following embodiments, certain features of the drawings may be omitted, enlarged or reduced, and do not represent the size of an actual product; it will be understood by those skilled in the art that certain well-known structures in the drawings and descriptions thereof may be omitted.
Example 1
As shown in fig. 1, this embodiment is a structure of a software tool, and includes a main page, a main module, a page calling interface and a RunTool calling interface, where the page calling interface is used to call the main page, the main page is used to call the main module, and the RunTool calling interface is used to directly call the main module in a function manner; the main page is used as an interactive interface for a user to operate the software tool, and the main module is an execution instruction module for realizing the main service function of the software tool. .
The function of the software tool is realized by the executive program contained in the software tool, so that the function of the software tool must be realized by calling the executive program contained in the software tool, the calling mode is two, the first mode is that a main page is called through a page calling interface, a main module is called through the main page, and then the executive program is called to realize the function of the software tool, wherein the page calling interface can be a URL calling mode, the URL calling is based on an http protocol, and is usually calling initiated to the software tool by a web end (browser), and a user can open the main page of the software tool and then call the main module by using the URL calling mode;
the second one is that the main module is called directly through a RunTool calling interface, and then the executive program is called to realize the function of the software tool, the RunTool calling interface is an interface which is realized by a RunTool function and starts the software tool to execute, and the RunTool calling interface is generally used for one software tool to call another software tool on the background of the software tool; the executive program of the software tool can be called in a page mode and also in a RunTool calling mode, and the calling mode is flexible;
further, as shown in fig. 1, the software tool further includes an auxiliary page, the auxiliary page is another auxiliary page that the user needs to use when operating the software tool, the main page can be called with the auxiliary page through page jump, the auxiliary page is not an essential page, but the main page is an essential page, the auxiliary page is an auxiliary page that the user needs to use when operating the software tool, and the main page is also used for calling with the auxiliary page in a page jump manner. .
Further, as shown in fig. 1, the software tool further includes an auxiliary module, the auxiliary module is an execution instruction module for implementing an auxiliary service function of the software tool, and the main module is configured to call the auxiliary module in a module internal call manner. The auxiliary module is not a necessary module, but the main module is a necessary module. The auxiliary module comprises one or more groups of methods for realizing the functions of the module; the internal calling mode of the main module for calling the auxiliary module refers to a module calling mode specified in the main module, the main module is responsible for receiving and analyzing a user request, then calls the specific auxiliary module, returns a result to the user after processing is completed, and the main module can start the auxiliary module to execute functions thereof through the internal calling mode.
Further, the RunTool call interface can be called by other software tools;
the execution program of the software tool has two calling modes, the calling mode through the page calling interface is a URL calling mode, the execution program can be generally called by a user through a webpage, the calling mode through the RunTool calling interface can be used by the user or other callers to directly call the software tool through other software tools or other software tools, and the RunTool calling interface is generally used for one software tool to call another software tool at the background of the software tool; the two calling modes not only enable the user to call when the software tool is used, but also enable other software tools and users using other software tools to call when the software tool is used, the modes for calling the software tool are more various, and the users using the software tool are wider.
As a preferred scheme, the implementation code of the main page is as shown in fig. 2, the implementation code of the main page is 'main.jsp', the implementation code of the main module and the auxiliary module is as shown in fig. 3, the main module is 'main ()', the auxiliary module is 'open ()' and 'close ()', the main page provides a user operation interface, the interface has two operation buttons, the main module is started to execute through the tool management system, and the main module calls the auxiliary module to execute, so as to implement the function of controlling the door to be opened and closed by the user.
Example 2
As shown in fig. 4, the present embodiment is a method for registering a tool, including the following registration steps:
a method of registering a software tool, comprising the steps of:
receiving registration request information of a user requesting to register the software tool and a code package of the software tool;
adding a registration record of the software tool in a tool information table according to the registration request information; the registration record comprises a tool identifier, tool interface information, operating environment information, database information and a dependent tool identifier, wherein the tool identifier is an identifier for uniquely identifying the software tool, the tool interface information is configuration information required when the software tool is called by using a tool interface, and the operating environment information refers to relevant information of operating environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like required by the operation of the tool; the database information is information of a database which needs to be connected when the tool runtime, and the dependent tool identifier is a tool identifier of other software tools which the software tool runtime needs to depend on. The code package is a file set formed by a source code of a tool and/or an executable file obtained by compiling the source code, when a user uploads the tool code package, the user fills in the attribute of the software tool in a registration tool interface of a platform system, after the platform system receives the registration request information and the code package of the software tool, a registration record is generated in a tool information table, as shown in fig. 4, the registration record is one of the registration records of the tool information table of the platform system, the registration record comprises a tool identifier, tool interface information, operating environment information and database information, the tool identifier is an identifier for uniquely identifying the software tool, the tool interface information is configuration information required when the software tool is called by using the tool interface, and comprises input parameters and output results, and the input parameters comprise the name, value type and related limits of the parameters, the output result comprises the name and value type of the result, the operation environment information refers to relevant information of operation environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like required by the operation of the tool, and the database information is information of a database which is required to be connected when the software tool operates.
When a user requests to install a tool, the operating environment information and the database information corresponding to the tool can be inquired according to the registration record in the tool information table, whether the target server has the operating environment is judged according to the operating environment information, the code package of the tool is installed on the target server only when the requirement is met, whether the database connected with the target server on which the user needs to install the software tool is consistent with the database information is judged according to the database information, and the code package of the software tool is installed on the target server only when the requirement is met; and inquiring tool interface information corresponding to the tool according to the registration record in the tool information table, and judging whether the software tool can be called and/or knowing how to call the software tool according to the tool interface information.
The user can upload and register the executable software tool on the system platform and generate the registration record, so that other users can directly install and use the tool according to the registration record or directly install and call by other tools or application programs according to the registration record, and the software tool allows programming by utilizing a plurality of programming languages and has wider applicability.
As shown in FIG. 5, the registration record further includes a dependent tool identifier, which is a tool identifier of other tools that the tool needs to depend on when running; other tools that the tool runtime needs to call are tools that the tool runtime needs to rely on.
When a user requests to install a tool, a dependent tool set corresponding to the tool can be inquired according to a registration record in a tool information table, namely a set formed by identifiers of other tools needing to be called when the tool runs is inquired, whether all dependent tools of the tool are installed on a target server or not is judged according to the dependent tool set, and a code package of the tool is installed on the target server only under the condition that all dependent tools are installed. Therefore, the situation that the user does not support when installing or operating the tool can be avoided, and the use experience of the user is improved.
Further, as shown in fig. 5, the database information includes a database name and a database product model number; the database name may be a symbolic string representing the name of the database to which the tool's execution is to connect and access; the database name has uniqueness in the system platform; the database product model represents the product name and model of the database management system product in which the accessed database is located.
Judging whether the database connected with the target server meets the requirements or not according to the database information, which specifically comprises the following steps: and detecting whether the database is available in the target server according to the database product model, and detecting whether the database exists in the target server according to the database name.
Preferably, the registration record may further include one or more of a tool name, a tool development language, and a tool description. Each tool is assigned with a tool name which can be used for memorizing, and the tool name can be a character string; the tool development language indicates which programming language the tool was developed from, e.g., C, C + +, Java, python, php, object-c, and so on; the tool description is a description of the functions that the tool has.
Example 3
As shown in fig. 6, this embodiment is a method for installing a tool, including the registration step described in embodiment 2, and further including the following installation steps:
the method comprises the steps that a user starts installation through input equipment on an operation interface of a platform system, a target tool to be installed and a target server to be installed by the target tool are selected, after the platform system receives installation request information of the user, according to a target tool identifier of the target tool to be installed by the user, the tool identifier recorded in a tool information table is matched, running environment information and database information of the corresponding tool are obtained, whether the target server has the running environment or not is judged, if yes, the next judging step is continued, whether a database connected with the target server is consistent with the database information or not is judged, and if yes, a code package of the target tool is installed on the target server.
When a user requests to install a tool, the operating environment information and the database information corresponding to the tool can be inquired according to the registration record in the tool information table, whether the target server has the operating environment is judged according to the operating environment information, the code packet of the tool is installed on the target server only when the requirement is met, whether the database connected with the target server on which the tool needs to be installed by the user is consistent with the database information is judged according to the database information, and the code packet of the tool is installed on the target server only when the requirement is met; and inquiring tool interface information corresponding to the tool according to the registration record in the tool information table, and judging whether the tool can be called and/or knowing how to call the tool according to the tool interface information.
Further, as shown in fig. 6, the database information includes a database name and a database product model number; the platform system detects whether the database is available in the target server according to the model number of the database product, if so, the next installation judgment is continued, and if not, the database connected with the target server is judged not to meet the requirement and installation failure information is returned to the user operation terminal; and the platform system detects whether the database exists in the target server or not according to the name of the database, if so, continues the next installation step, otherwise, judges that the database connected with the target server does not meet the requirement and returns the information of installation failure to the user operation terminal.
Further, as shown in fig. 6, before the step of installing the code package of the target tool on the target server, the method further includes the following steps: and the platform system matches the tool identifier recorded in the tool information table according to the target tool identifier to obtain a corresponding dependent working identifier, judges whether other tools which need to be dependent during the operation of the target tool are installed on the target server or not according to the dependent tool identifier, installs the code packet of the target tool on the target server if the other tools need to be dependent, and returns the information of failed installation to the user operation terminal if the other tools do not need to be dependent.
When a user requests to install a tool, a dependent tool set corresponding to the tool can be inquired according to a registration record in a tool information table, namely a set formed by identifiers of other tools needing to be called when the tool runs is inquired, whether all dependent tools of the tool are installed on a target server or not is judged according to the dependent tool set, and a code package of the tool is installed on the target server only under the condition that all dependent tools are installed. Therefore, the situation that the user does not support when installing the tool can be avoided, and the use experience of the user is improved.
Further, as shown in fig. 6, after the step of installing the code package of the target tool on the target server, the platform system adds an installation record of the target tool in an installation information table, where the installation record includes a tool identifier and a tool installation status.
The user can inquire the tools installed on the target server according to the installation information table, and can also select the tools to be operated in the installation information table for calling.
As shown in fig. 7, the installation record in the installation information table includes a tool identifier, an execution node identifier, and a code installation time. The tool identifier is an identifier of the installed tool, the execution node identifier is an identifier of an execution server, i.e., a target server, where the tool is installed, and the code installation time is a time when the installed tool is initially installed or updated.
Example 4
As shown in fig. 8, the present embodiment is a method for operating a tool, including the installation step in embodiment 3, and further including the following operation steps:
the platform system receives operation request information of a user requesting to operate a target tool through input equipment on an operation interface of the platform system, the platform system matches an identifier of the target tool of an installation record in an installation information table according to the identifier of the target tool selected to operate by the user, judges whether the target tool is installed on a target server or not, if yes, two modes of calling an execution program are provided, the first mode is that a main page is called on the target server through a page calling interface of the target tool, then a main module is called through the main page to realize the function of the main module, the value of an input parameter in a tool interface is transferred to the main module, and the main module returns the result of software tool execution to a user operation terminal.
The second one is that the caller calls the main module through the RunTool call interface of the said target tool, and then call its executive program, transfer the value of the input parameter in the tool interface to the main module, the main module returns the result that the software tool carries out to the caller's operation terminal, RunTool call interface is generally used for a software tool to use when its back end calls another tool; otherwise, the procedure returns to the registration step of embodiment 2 or the installation step of embodiment 3.
Example 5
The present embodiment is a tool management system comprising a processor configured to perform the methods of embodiments 3, 4, and 5.
Further, as shown in fig. 9, the processor includes a tool registration module, a tool installation module, and a tool operation control module, wherein the tool registration module is configured to perform the registration step according to embodiment 2, the tool installation module is configured to perform the installation step according to embodiment 3, and the tool operation control module is configured to perform the operation step according to embodiment 4.
It should be understood that the above-mentioned embodiments of the present invention are only examples for clearly illustrating the technical solutions of the present invention, and are not intended to limit the specific embodiments of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention claims should be included in the protection scope of the present invention claims.
Claims (9)
1. A software tool is characterized by comprising a main page, a main module, a page calling interface and a RunTool calling interface, wherein the page calling interface is used for calling the main page, the main page is used for calling the main module, and the RunTool calling interface is used for directly calling the main module in a function mode; the main page is used as an interactive interface for a user to operate the software tool, and the main module is an execution instruction module for realizing the main service function of the software tool.
2. The software tool of claim 1, further comprising an auxiliary page, wherein the auxiliary page is an auxiliary page that a user needs to use when operating the software tool, and wherein the main page is further configured to call the auxiliary page in a page jump manner.
3. The software tool according to claim 2, further comprising an auxiliary module, wherein the auxiliary module is an execution instruction module for implementing auxiliary service functions of the software tool, and the main module is configured to call the auxiliary module in the form of an internal module call.
4. The software tool according to any one of claims 1 to 3, wherein the RunTool call interface is further configured to be called by other software tools.
5. A method of registering a software tool, comprising the steps of:
receiving registration request information of a user requesting registration of the software tool according to any one of claims 1 to 4 and a code package of the software tool;
adding a registration record of the software tool in a tool information table according to the registration request information; the registration record comprises a tool identifier, tool interface information, operating environment information, database information and a dependent tool identifier, wherein the tool identifier is an identifier for uniquely identifying the software tool, the tool interface information is input parameters and output results required when the software tool is called by using a tool interface, the operating environment information refers to relevant information of operating environments such as a tool control system, a middleware system, a support SDK library, a hardware system and the like required by the tool operation, the database information is information of a database required to be connected when the tool operates, and the dependent tool identifier is a tool identifier of other tools required to be dependent when the tool operates.
6. The method of registering a software tool according to claim 5, wherein the input parameters include a name, a value type and associated restrictions of the parameter, and the output result includes a name, a value type of the result.
7. A method of installing a software tool, comprising the step of registering according to any of claims 5 to 6, and further comprising the step of installing:
receiving installation request information of a user requesting installation of a target tool, wherein the installation request information comprises a target tool identifier and target server information;
matching the tool identifier registered in the tool information table according to the target tool identifier to acquire corresponding database information and running environment information, wherein the database information is information of a database which needs to be connected when the tool runs;
searching a corresponding target server according to the target server information;
judging whether the target server has the operating environment or not according to the operating environment information, and continuing the next judging step if the target server has the operating environment;
judging whether a database connected with the target server is consistent with database information or not according to the database information, and continuing the next judging step if the database is consistent with the database information;
according to the target tool identifier, matching the tool identifier registered in the tool information table, and acquiring a corresponding dependent tool identifier; judging whether other tools which need to be depended when the target tool runs are installed on the target server or not according to the dependent tool identifier, and if so, installing a code package of the target tool on the target server;
and adding an installation record of the target tool in an installation information table, wherein the installation record comprises a tool identifier and a tool installation state.
8. A method of operating a software tool, comprising the installing step of claim 7, further comprising the operating steps of:
receiving operation request information of a user and/or a caller requesting to operate a target tool, wherein the operation request information comprises a target tool identifier and tool interface information;
according to the target tool identifier, matching the tool identifier of the installation record in the installation information table, and acquiring a corresponding tool installation state;
judging whether the code packet of the target tool is installed on a target server or not according to the acquired tool installation state, if so, calling a main page through a page calling interface of the target tool on the target server according to the tool interface information, and calling a main module through the main page or calling the main module through a RunTool calling interface of the target tool;
and transmitting the value of the input parameter in the tool interface to the main module, and returning the result of the software tool to the user and/or the caller by the main module.
9. A tool management system comprising a processor configured to perform the method of any one of claims 5 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911066189.3A CN110764793A (en) | 2019-11-04 | 2019-11-04 | Software tool and registration, installation and operation method and tool management system thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911066189.3A CN110764793A (en) | 2019-11-04 | 2019-11-04 | Software tool and registration, installation and operation method and tool management system thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110764793A true CN110764793A (en) | 2020-02-07 |
Family
ID=69335558
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911066189.3A Pending CN110764793A (en) | 2019-11-04 | 2019-11-04 | Software tool and registration, installation and operation method and tool management system thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110764793A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101490656A (en) * | 2005-04-15 | 2009-07-22 | 微软公司 | Registration of applications and complimentary features for interactive user interfaces |
| US20140331240A1 (en) * | 2012-01-20 | 2014-11-06 | Huawei Technologies Co., Ltd. | Method, device and system for using and invoking oauth api |
| CN106970790A (en) * | 2017-03-09 | 2017-07-21 | 腾讯科技（深圳）有限公司 | Method, relevant device and system that a kind of application program is created |
| CN107483572A (en) * | 2017-08-08 | 2017-12-15 | 北京奇艺世纪科技有限公司 | The dispositions method and device of a kind of server |
| CN108804160A (en) * | 2018-06-14 | 2018-11-13 | 广州华多网络科技有限公司 | Interface call method and device |
| CN110069308A (en) * | 2019-04-22 | 2019-07-30 | 北京字节跳动网络技术有限公司 | The page starts method, apparatus, electronic equipment and storage medium |
-
2019
- 2019-11-04 CN CN201911066189.3A patent/CN110764793A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101490656A (en) * | 2005-04-15 | 2009-07-22 | 微软公司 | Registration of applications and complimentary features for interactive user interfaces |
| US20140331240A1 (en) * | 2012-01-20 | 2014-11-06 | Huawei Technologies Co., Ltd. | Method, device and system for using and invoking oauth api |
| CN106970790A (en) * | 2017-03-09 | 2017-07-21 | 腾讯科技（深圳）有限公司 | Method, relevant device and system that a kind of application program is created |
| CN107483572A (en) * | 2017-08-08 | 2017-12-15 | 北京奇艺世纪科技有限公司 | The dispositions method and device of a kind of server |
| CN108804160A (en) * | 2018-06-14 | 2018-11-13 | 广州华多网络科技有限公司 | Interface call method and device |
| CN110069308A (en) * | 2019-04-22 | 2019-07-30 | 北京字节跳动网络技术有限公司 | The page starts method, apparatus, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6438744B2 (en) | Dynamic mapping of component interfaces | |
| CN110377438B (en) | Routing method, device and system of cross-process communication interface | |
| US20020059314A1 (en) | System and method for automatically generating program | |
| CN103716308A (en) | Multiprotocol platform communication method and multiprotocol platform | |
| CN111580813B (en) | Automatic management method for Java class hot update | |
| CN111506366A (en) | Plug-in calling method and device, electronic equipment and storage medium | |
| CN111679852A (en) | Detection method and device for conflict dependency library | |
| CN112363726A (en) | Cross-kernel version compiling method and system of kernel module | |
| CN112035122B (en) | Interface deployment method, system and storage medium | |
| CN114285852A (en) | Service calling method and device based on multi-stage service platform | |
| US20100299652A1 (en) | Apparatus and method for managing components in sca system | |
| CN112860398A (en) | Data processing method, device, equipment and medium based on rule engine | |
| CN110764793A (en) | Software tool and registration, installation and operation method and tool management system thereof | |
| CN115994004B (en) | Application program interface calling method and device | |
| US8464218B2 (en) | Method port arrangement and configuration method thereof for robot software component | |
| CN115129740B (en) | Method and system for updating distributed micro-service database in cloud native environment | |
| CN111459492A (en) | Method, device, storage medium and equipment for detecting compatibility of Dubbo service interface | |
| CN116680003A (en) | Front-end plug-in system | |
| CN107885604B (en) | Method and device for communication between heterogeneous systems, computer equipment and storage medium | |
| CN111427770B (en) | Resource testing method and related equipment | |
| CN114416202A (en) | Mobile terminal SDK calling method and system | |
| US6219717B1 (en) | Method and apparatus for implementing object transparent invocation | |
| CN111984309A (en) | Service calling method, device, server and storage medium | |
| CN111522560A (en) | Software installation method and device, storage medium and electronic equipment | |
| CN112596823A (en) | Safety control method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200207 |