CN113778572B - Method for automatically linking multiple CLI programs into task flow - Google Patents
Method for automatically linking multiple CLI programs into task flow Download PDFInfo
- Publication number
- CN113778572B CN113778572B CN202111142620.5A CN202111142620A CN113778572B CN 113778572 B CN113778572 B CN 113778572B CN 202111142620 A CN202111142620 A CN 202111142620A CN 113778572 B CN113778572 B CN 113778572B
- Authority
- CN
- China
- Prior art keywords
- script
- task
- sub
- universal
- executing
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method for automatically connecting a plurality of CLI programs into a task flow, which comprises the following steps: constructing a universal task database and a connection script pool; customizing a business process node diagram according to the actual business process requirements of the project; each node binds a corresponding one of the universal tasks; and for the general tasks of each node, adopting a connection script serial mode to sequentially execute. The invention provides a method for automatically connecting a plurality of CLI programs into task flows, which can completely multiplex formed universal tasks in service flows, and connect each universal task in series into a complete service flow through a connection script, so that the service flow automation can be realized with lower cost, and the production efficiency is greatly improved.
Description
Technical Field
The invention belongs to the technical field of task automation, and particularly relates to a method for automatically linking a plurality of CLI programs into a task flow.
Background
Even with the same technology stack, each item eventually has some differences in the execution standard, but its general business flow is basically consistent. In the prior art, because the execution standards of the projects are different, each project needs to completely re-customize the service automation flow, and the problems of low service flow reusability and high realization cost of the service automation flow of the project are solved.
Disclosure of Invention
Aiming at the defects existing in the prior art, the invention provides a method for automatically connecting a plurality of CLI programs into a task flow, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides a method for automatically connecting a plurality of CLI programs into a task flow, which comprises the following steps:
step 1, constructing a general task database; the general task database is used for storing a plurality of general tasks; each general task is provided with a general task ID, a task parameter receiving interface and a task parameter output interface;
step 2, constructing a linking script pool; the engagement script pool is used for storing a plurality of engagement scripts; each of the linking scripts corresponds to a universal task ID and an execution sequence, and the execution sequence refers to: before the corresponding general task is executed, executing the linking script, namely, a prepositive linking script; or after the corresponding general task is executed, executing the linking script, namely the post linking script; each connection script is provided with a script parameter receiving interface and a script parameter output interface;
step 3, customizing a business process node diagram according to the actual business process requirements of the project; the business process node diagram comprises a plurality of nodes; each node binds a corresponding one of the universal tasks; wherein the universal tasks refer to the universal tasks queried from the universal task database;
step 4, let i=1;
step 5, the main process locates the ith node in the business process node diagram i Thereby obtaining the ith node i Binding universal task i ；
Step 6, the main process searches the linking script pool and judges whether the general task exists or not i Corresponding pre-connection script, if any, will be associated with the universal task i The corresponding pre-join script is expressed as a pre-join script BS i Step 7-step 9 is performed; otherwise, executing the step 10;
step 7, the main process determines whether there is a forward link script BS i The first transmission parameter is transmitted, if yes, the first transmission parameter is obtained, the first transmission parameter is transmitted to the first subprocess, and then the first subprocess is informed to execute the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the first sub-process of executing the pre-connection script BS i ；
Step 8, the first sub-process receives the execution front-end connection script BS i After the notification message of (1), first determining whether a first transfer parameter from the host process is receivedNumber, if not, directly executing the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the first transmission parameter to the pre-connection script BS i Executing the pre-connection script BS i ；
The first sub-process executes the pre-connection script BS i After finishing, sending a notification message of finishing execution to the main process;
step 9, after receiving the notification message of completion of execution of the first sub-process, the main process captures a standard output stream of the first sub-process, and judges whether the first sub-process has a second transmission parameter which needs to be transmitted downwards; if so, the main process captures the second transfer parameter and performs step 10; otherwise, directly executing the step 10;
step 10, the main process determines whether there is a second transfer parameter transferred to the second sub-process, if so, transfers the second transfer parameter to the second sub-process, and then notifies the second sub-process to execute the universal task i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the second subprocess of executing the universal task i ；
Step 11, the second sub-process receives the task i After the notification message of (1), firstly judging whether a second transfer parameter from the main process is received, if not, directly executing the general task i The method comprises the steps of carrying out a first treatment on the surface of the If yes, the second transfer parameter is transferred to the universal task i Executing the universal task i ；
The second subprocess executes the universal task i After finishing, sending a notification message of finishing execution to the main process;
step 12, after receiving the notification message of completion of execution of the second sub-process, the main process captures a standard output stream of the second sub-process, and judges whether the second sub-process has a third transfer parameter to be transferred downwards; if so, the main process captures the third transfer parameter and performs step 13; otherwise, directly executing the step 13;
step 13, the main process searches the linking script pool to judge whether the linking script pool exists or notThe universal task i Corresponding post-join script, if any, will be associated with the generic task i The corresponding post-join script is expressed AS post-join script AS i Step 14-step 16 are performed; otherwise, go to step 17;
step 14, the main process determines whether there is a backward link script AS i If yes, acquiring the third transfer parameter, transferring the third transfer parameter to a third sub-process, and then notifying the third sub-process to execute the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the third sub-process of executing the post-connection script AS i ；
Step 15, the third sub-process receives the execution post-connection script AS i After the notification message of (1), firstly judging whether a third transfer parameter from the main process is received, if not, directly executing the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the third transmission parameter to the post-connection script AS i Executing the post-connection script AS i ；
The third sub-process executes the post-connection script AS i After finishing, sending a notification message of finishing execution to the main process;
step 16, after receiving the notification message of completion of execution of the third sub-process, the main process captures the standard output stream of the third sub-process, and judges whether the third sub-process has a fourth transfer parameter which needs to be transferred downwards; if yes, the main process captures the fourth transfer parameter, and assigns the fourth transfer parameter to the first transfer parameter, and then step 17 is executed; otherwise, directly executing the step 17;
step 17, judging the ith node i If the node is the last node in the business process node diagram, completing the process of automatically connecting a plurality of CLI programs into a task process, and ending the process; if not, let i=i+1, return to step 5.
Preferably, the generic task is a computer application or executable script that is allowed to execute in the command line interface CLI.
The method for automatically linking a plurality of CLI programs into a task flow has the following advantages:
the invention provides a method for automatically connecting a plurality of CLI programs into task flows, which can completely multiplex formed universal tasks in service flows, and connect each universal task in series into a complete service flow through a connection script, so that the service flow automation can be realized with lower cost, and the production efficiency is greatly improved.
Drawings
Fig. 1 is a flow chart of a method for automatically linking a plurality of CLI programs into a task flow according to the present invention.
Detailed Description
In order to make the technical problems, technical schemes and beneficial effects solved by the invention more clear, the invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The invention provides a method for automatically connecting a plurality of CLI programs into task flows, which can completely multiplex formed universal tasks in service flows, and connect each universal task in series into a complete service flow through a connection script, so that the service flow automation can be realized with lower cost, and the production efficiency is greatly improved.
The invention provides a method for automatically connecting a plurality of CLI programs into task flows, which adjusts the difference of each link on different service lines to be consistent through a connection script so as to meet the requirement of an automatic execution standard. The engagement script functions as a hook and may be executed one or more before/after each general task is run.
In the task execution flow, each general task is executed in a sub-process manner. Before and after each general task is run, the main process searches whether a linking script needing to be executed exists in a linking script pool. And if yes, executing, otherwise, neglecting to jump to the next general task in the task flow, and ending the execution of the whole task flow.
Referring to fig. 1, the present invention provides a method for automatically linking a plurality of CLI programs into a task flow, comprising the following steps:
step 1, constructing a general task database; the general task database is used for storing a plurality of general tasks; each general task is provided with a general task ID, a task parameter receiving interface and a task parameter output interface;
wherein, the general task refers to a common operation flow which is experienced in the business flow. Taking the mobile phone application as an example, the development general procedure may include (but is not limited to): setting application information, compiling, packaging, signing programs, publishing and the like. Then each step can be a separate general task.
The general task does not need to consider special cases between each project, such as: the application information is in text format or other document format, how package compiling parameters between different projects are set, etc.
In the present invention, the general purpose tasks are not limited to a particular computer programming language limitation, allowing for either computer applications or executable scripts to be executed in a Command Line Interface (CLI).
The generic task may pass parameters to the next task (which may be a generic task or a join script). The way of delivering the parameters is in the form of stdout (standard output stream).
Specifically, the main process intercepts specific content (i.e., delivery parameters) to be delivered by capturing the standard output stream content of the sub-process. The method of interception may be bit interception (for example, the last 100 bits of the intercepted content) or interception by a format rule (for example, "@ next path=dir\child dir, @ next name=game"). After the current sub-process is finished, the main process transfers the command parameters to the next sub-process when scheduling to execute the next task, for example: "run (nextsask-path=dir\child dir-name=game)".
And (3) receiving general task parameters: before the general task is executed, the parameters transferred by the previous task are acquired by acquiring the value of the previous subprocess, so that the specific logic processing of the general task is performed.
Step 2, constructing a linking script pool; the engagement script pool is used for storing a plurality of engagement scripts; each of the linking scripts corresponds to a universal task ID and an execution sequence, and the execution sequence refers to: before the corresponding general task is executed, executing the linking script, namely, a prepositive linking script; or after the corresponding general task is executed, executing the linking script, namely the post linking script; each connection script is provided with a script parameter receiving interface and a script parameter output interface;
the linking script is used for processing the automation flow difference of each item, such as setting application information listed in the previous step, setting item compiling parameters and the like. Even additional operations such as backup of results required for packing completion can be handled by the join script. The implementation details of the connection script technology are as follows:
the linking scripts are stored in a unified linking script pool, so that after each task is executed, whether the next linking script needs to be executed or not is required to be searched from the linking script pool. To achieve automatic association with a generic task node, the engagement script needs to follow a naming convention. The naming rule is "task name __ before/after- -execution order. Script extension". Taking compiling task (build) as an example, the pre-join script may be named: build __ before-0. Py, build __ before-1. Sh, etc., the post-join script may be named: build __ after-0. Py, build __ after-1. Bat, etc.
The parameters of the connection script are transmitted and received according to the rule, and the parameters are the same as the general task processing rule.
Step 3, customizing a business process node diagram according to the actual business process requirements of the project; the business process node diagram comprises a plurality of nodes; each node binds a corresponding one of the universal tasks; wherein the universal tasks refer to the universal tasks queried from the universal task database;
step 4, let i=1;
step 5, the main process locates the ith node in the business process node diagram i Thereby obtaining the ith node i Binding universal task i ；
Step 6, the mainThe process searches the linking script pool and judges whether the universal task exists or not i Corresponding pre-connection script, if any, will be associated with the universal task i The corresponding pre-join script is expressed as a pre-join script BS i Step 7-step 9 is performed; otherwise, executing the step 10;
step 7, the main process determines whether there is a forward link script BS i The first transmission parameter is transmitted, if yes, the first transmission parameter is obtained, the first transmission parameter is transmitted to the first subprocess, and then the first subprocess is informed to execute the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the first sub-process of executing the pre-connection script BS i ；
Step 8, the first sub-process receives the execution front-end connection script BS i After the notification message of (1), firstly judging whether the first transfer parameter from the main process is received, if not, directly executing the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the first transmission parameter to the pre-connection script BS i Executing the pre-connection script BS i ；
The first sub-process executes the pre-connection script BS i After finishing, sending a notification message of finishing execution to the main process;
step 9, after receiving the notification message of completion of execution of the first sub-process, the main process captures a standard output stream of the first sub-process, and judges whether the first sub-process has a second transmission parameter which needs to be transmitted downwards; if so, the main process captures the second transfer parameter and performs step 10; otherwise, directly executing the step 10;
step 10, the main process determines whether there is a second transfer parameter transferred to the second sub-process, if so, transfers the second transfer parameter to the second sub-process, and then notifies the second sub-process to execute the universal task i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the second subprocess of executing the universal task i ；
Step 11, the second sub-process receives the task i Is informed ofAfter the message, firstly judging whether a second transfer parameter from the main process is received, if not, directly executing the general task i The method comprises the steps of carrying out a first treatment on the surface of the If yes, the second transfer parameter is transferred to the universal task i Executing the universal task i ；
The second subprocess executes the universal task i After finishing, sending a notification message of finishing execution to the main process;
step 12, after receiving the notification message of completion of execution of the second sub-process, the main process captures a standard output stream of the second sub-process, and judges whether the second sub-process has a third transfer parameter to be transferred downwards; if so, the main process captures the third transfer parameter and performs step 13; otherwise, directly executing the step 13;
step 13, the main process searches the linking script pool to judge whether the universal task exists or not i Corresponding post-join script, if any, will be associated with the generic task i The corresponding post-join script is expressed AS post-join script AS i Step 14-step 16 are performed; otherwise, go to step 17;
step 14, the main process determines whether there is a backward link script AS i If yes, acquiring the third transfer parameter, transferring the third transfer parameter to a third sub-process, and then notifying the third sub-process to execute the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the third sub-process of executing the post-connection script AS i ；
Step 15, the third sub-process receives the execution post-connection script AS i After the notification message of (1), firstly judging whether a third transfer parameter from the main process is received, if not, directly executing the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the third transmission parameter to the post-connection script AS i Executing the post-connection script AS i ；
The third sub-process executes the post-connection script AS i After finishing, to the mainThe process sends notification information after execution;
step 16, after receiving the notification message of completion of execution of the third sub-process, the main process captures the standard output stream of the third sub-process, and judges whether the third sub-process has a fourth transfer parameter which needs to be transferred downwards; if yes, the main process captures the fourth transfer parameter, and assigns the fourth transfer parameter to the first transfer parameter, and then step 17 is executed; otherwise, directly executing the step 17;
step 17, judging the ith node i If the node is the last node in the business process node diagram, completing the process of automatically connecting a plurality of CLI programs into a task process, and ending the process; if not, let i=i+1, return to step 5.
The method for automatically linking a plurality of CLI programs into a task flow has the following advantages:
the invention provides a method for automatically connecting a plurality of CLI programs into task flows, which can completely multiplex formed universal tasks in service flows, and connect each universal task in series into a complete service flow through a connection script, so that the service flow automation can be realized with lower cost, and the production efficiency is greatly improved.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which is also intended to be covered by the present invention.
Claims (2)
1. A method for automatically linking a plurality of CLI programs into a task flow, comprising the steps of:
step 1, constructing a general task database; the general task database is used for storing a plurality of general tasks; each general task is provided with a general task ID, a task parameter receiving interface and a task parameter output interface;
step 2, constructing a linking script pool; the engagement script pool is used for storing a plurality of engagement scripts; each of the linking scripts corresponds to a universal task ID and an execution sequence, and the execution sequence refers to: before the corresponding general task is executed, executing the linking script, namely, a prepositive linking script; or after the corresponding general task is executed, executing the linking script, namely the post linking script; each connection script is provided with a script parameter receiving interface and a script parameter output interface;
step 3, customizing a business process node diagram according to the actual business process requirements of the project; the business process node diagram comprises a plurality of nodes; each node binds a corresponding one of the universal tasks; wherein the universal tasks refer to the universal tasks queried from the universal task database;
step 4, let i=1;
step 5, the main process locates the ith node in the business process node diagram i Thereby obtaining the ith node i Binding universal task i ；
Step 6, the main process searches the linking script pool and judges whether the general task exists or not i Corresponding pre-connection script, if any, will be associated with the universal task i The corresponding pre-join script is expressed as a pre-join script BS i Step 7-step 9 is performed; otherwise, executing the step 10;
step 7, the main process determines whether there is a forward link script BS i The first transmission parameter is transmitted, if yes, the first transmission parameter is obtained, the first transmission parameter is transmitted to the first subprocess, and then the first subprocess is informed to execute the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the first sub-process of executing the pre-connection script BS i ；
Step 8, the first sub-process receives the execution front-end connection script BS i After the notification message of (1), firstly judging whether the first transfer parameter from the main process is received, if not, directly executing the pre-connection script BS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the first transmission parameter to the pre-connection script BS i Executing the pre-connection script BS i ；
The first sub-process executes the pre-connection script BS i After finishing, sending a notification message of finishing execution to the main process;
step 9, after receiving the notification message of completion of execution of the first sub-process, the main process captures a standard output stream of the first sub-process, and judges whether the first sub-process has a second transmission parameter which needs to be transmitted downwards; if so, the main process captures the second transfer parameter and performs step 10; otherwise, directly executing the step 10;
step 10, the main process determines whether there is a second transfer parameter transferred to the second sub-process, if so, transfers the second transfer parameter to the second sub-process, and then notifies the second sub-process to execute the universal task i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the second subprocess of executing the universal task i ；
Step 11, the second sub-process receives the task i After the notification message of (1), firstly judging whether a second transfer parameter from the main process is received, if not, directly executing the general task i The method comprises the steps of carrying out a first treatment on the surface of the If yes, the second transfer parameter is transferred to the universal task i Executing the universal task i ；
The second subprocess executes the universal task i After finishing, sending a notification message of finishing execution to the main process;
step 12, after receiving the notification message of completion of execution of the second sub-process, the main process captures a standard output stream of the second sub-process, and judges whether the second sub-process has a third transfer parameter to be transferred downwards; if so, the main process captures the third transfer parameter and performs step 13; otherwise, directly executing the step 13;
step 13, the main process searches the linking script pool to judge whether the universal task exists or not i Corresponding post-join script, if any, will be associated with the generic task i The corresponding post-join script is expressed AS post-join script AS i Step 14-step 16 are performed; otherwise, go to step17；
Step 14, the main process determines whether there is a backward link script AS i If yes, acquiring the third transfer parameter, transferring the third transfer parameter to a third sub-process, and then notifying the third sub-process to execute the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If not, directly informing the third sub-process of executing the post-connection script AS i ；
Step 15, the third sub-process receives the execution post-connection script AS i After the notification message of (1), firstly judging whether a third transfer parameter from the main process is received, if not, directly executing the post-connection script AS i The method comprises the steps of carrying out a first treatment on the surface of the If yes, transmitting the third transmission parameter to the post-connection script AS i Executing the post-connection script AS i ；
The third sub-process executes the post-connection script AS i After finishing, sending a notification message of finishing execution to the main process;
step 16, after receiving the notification message of completion of execution of the third sub-process, the main process captures the standard output stream of the third sub-process, and judges whether the third sub-process has a fourth transfer parameter which needs to be transferred downwards; if yes, the main process captures the fourth transfer parameter, and assigns the fourth transfer parameter to the first transfer parameter, and then step 17 is executed; otherwise, directly executing the step 17;
step 17, judging the ith node i If the node is the last node in the business process node diagram, completing the process of automatically connecting a plurality of CLI programs into a task process, and ending the process; if not, let i=i+1, return to step 5.
2. The method of claim 1, wherein the common task is a computer application or executable script that allows execution in a command line interface CLI.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111142620.5A CN113778572B (en) | 2021-09-28 | 2021-09-28 | Method for automatically linking multiple CLI programs into task flow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111142620.5A CN113778572B (en) | 2021-09-28 | 2021-09-28 | Method for automatically linking multiple CLI programs into task flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113778572A CN113778572A (en) | 2021-12-10 |
| CN113778572B true CN113778572B (en) | 2023-09-15 |
Family
ID=78854093
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111142620.5A Active CN113778572B (en) | 2021-09-28 | 2021-09-28 | Method for automatically linking multiple CLI programs into task flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778572B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1392019A1 (en) * | 2002-08-19 | 2004-02-25 | Alcatel Canada Inc. | Command line interface processor with dynamic update of attribute dependencies. |
| CN101404696A (en) * | 2008-11-03 | 2009-04-08 | 中兴通讯股份有限公司 | Visible service flow tracing method and system, service flow processing system |
| CN102760074A (en) * | 2011-04-26 | 2012-10-31 | Sap股份公司 | High-load business process scalability |
| CN109144618A (en) * | 2018-09-10 | 2019-01-04 | 中铝视拓智能科技有限公司 | A kind of service flow execution method and relevant apparatus |
| CN110399207A (en) * | 2019-06-29 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Timed task processing method, system and storage medium in distributed memory system |
| CN112348326A (en) * | 2020-10-23 | 2021-02-09 | 中国建设银行股份有限公司 | Bank business processing method and system |
| CN112380255A (en) * | 2020-11-16 | 2021-02-19 | 广东亿迅科技有限公司 | Service processing method, device, equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4352722B2 (en) * | 2003-02-25 | 2009-10-28 | 株式会社日立製作所 | Business process processing method and system, and processing program therefor |
| TWI289388B (en) * | 2003-12-12 | 2007-11-01 | Hon Hai Prec Ind Co Ltd | Command line interface system and the method of control |
| US20060190579A1 (en) * | 2005-02-23 | 2006-08-24 | Alcatel | Assisted command script template creation |
-
2021
- 2021-09-28 CN CN202111142620.5A patent/CN113778572B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1392019A1 (en) * | 2002-08-19 | 2004-02-25 | Alcatel Canada Inc. | Command line interface processor with dynamic update of attribute dependencies. |
| CN101404696A (en) * | 2008-11-03 | 2009-04-08 | 中兴通讯股份有限公司 | Visible service flow tracing method and system, service flow processing system |
| CN102760074A (en) * | 2011-04-26 | 2012-10-31 | Sap股份公司 | High-load business process scalability |
| CN109144618A (en) * | 2018-09-10 | 2019-01-04 | 中铝视拓智能科技有限公司 | A kind of service flow execution method and relevant apparatus |
| CN110399207A (en) * | 2019-06-29 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Timed task processing method, system and storage medium in distributed memory system |
| CN112348326A (en) * | 2020-10-23 | 2021-02-09 | 中国建设银行股份有限公司 | Bank business processing method and system |
| CN112380255A (en) * | 2020-11-16 | 2021-02-19 | 广东亿迅科技有限公司 | Service processing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113778572A (en) | 2021-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103019874B (en) | Method and the device of abnormality processing is realized based on data syn-chronization | |
| CN101141742B (en) | Application communication method of terminal | |
| CN101227630A (en) | Method for monitoring application program based on window platform | |
| CN101963915A (en) | Building method of compilation and system thereof | |
| CN103177104A (en) | Searching method and device of application program | |
| CN112636966A (en) | Application batch deployment method based on remote debugging protocol | |
| CN113778572B (en) | Method for automatically linking multiple CLI programs into task flow | |
| CN111984346A (en) | Method, system, device and storage medium for call chain tracking in micro-service environment | |
| CN110505298A (en) | Optimization system and its method based on transmitting file on linux system | |
| CN112199662B (en) | Permission verification system based on self-adaptive plug-in | |
| CN102591714A (en) | Process calling method, system and application server | |
| CN204925778U (en) | Stage multimode cooperative control system | |
| CN111404738B (en) | Flow table and configuration hot modification method of network controller | |
| CN103150162B (en) | Improve the method for embedded software code degree of share | |
| CN111416889B (en) | Communication method and system adapted through GATT and exception handling | |
| CN110187891B (en) | Program development method and system for multi-core programmable controller | |
| CN105204866A (en) | Equipment command calling method and system | |
| CN102469118B (en) | A kind of method and device realizing information exploitation | |
| CN111711996A (en) | Method and device for stable transmission of TCP communication | |
| KR102120231B1 (en) | Automatic generation method of sensor node program using state transition diagram | |
| CN204925762U (en) | Stage multimode cooperative system | |
| CN106775719A (en) | Cross-platform lightweight data storehouse method for packing and system based on mobile terminal | |
| CN103024021B (en) | A kind of information transferring method and system | |
| CN115988087B (en) | Service calling method and device based on bus, electronic equipment and storage medium | |
| CN117472844B (en) | Multi-chip module and data processing method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |