TWI714390B - Method for controlling operation flow - Google Patents

Abstract

The present invention provides a method for controlling an operation flow, which includes: obtaining an operation flow, wherein the operation flow records a plurality of upstream programs and downstream programs and the version number and execution timing of each of the foregoing programs; obtaining a plurality of task connecting identification formats generated by the upstream programs, and accordingly generating a plurality of process connecting identification flags; in response to determining that the specific identification flag in the process connecting identification flags has been verified based on a task connecting identification rule, notifying the downstream programs to execute subsequently.

Description

Work flow control method

The present invention relates to a process management mechanism, and particularly relates to a method of operating process control.

In the prior art, for relatively complex application system environments (such as: application system environments spanning multiple hosts, operating functions are frequently put on/off shelves), there is currently no mechanism that can efficiently assemble and manage workflow execution . In this case, in addition to the inability to clearly and effectively manage the on/off schedule of each operation function (for example, different operation functions can be switched at a certain point in time) and assembly into a new operation process, it may also be due to certain operation procedures Need to wait for manual start and cause unnecessary delay (for example, the idle time of the host due to waiting for execution).

In view of this, the present invention provides a work flow control method, which can be used to solve the above technical problems.

The present invention provides a work flow control method, including: obtaining a work flow from a process configuration setting database by a process execution agent component, wherein the work flow records multiple upstream operating programs and multiple downstream operating programs in the aforementioned operating programs The individual version number and execution timing of the operating program, and the foregoing upstream operating program forms an upstream process, and the foregoing downstream operating program forms a downstream process following the upstream process; a process serial proxy component obtains multiple generated by the foregoing upstream operating program The business cascade identification format, and a plurality of process cascade identification flags are generated accordingly; in response to the determination that at least one specific identification flag in the aforementioned process cascade identification flag has passed a business cascade identification rule, the process is cascaded The agent component notifies the aforementioned downstream operating program to continue execution.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

In summary, the method of the present invention can implement a work flow assembly technology with high scalability and supporting a distributed architecture. In addition, it can dynamically switch the operating function version of the host system and the process can support an automatic serial connection mechanism to achieve an adaptable application system environment. In this way, the present invention can meet the increasingly complex and diversified needs of the application system operation in the enterprise. Details will be described below.

Please refer to FIG. 1 and FIG. 2, where FIG. 1 is a flowchart of a work flow control method according to an embodiment of the present invention, and FIG. 2 is an application scenario diagram according to an embodiment of the present invention. In an embodiment of the present invention, the method in FIG. 1 can be executed by the process job execution agent component 210 and the process cascade agent component 220 in FIG. 2 in cooperation. The following describes each step of FIG. 1 with the content of FIG. 2.

In the embodiment of the present invention, the process execution agent component 210 and the process cascade agent component 220 are, for example, programs that can be installed on one or more hosts at the same time to coordinate the operation processes of the operating programs on each host.

In one embodiment, the process execution agent component 210 can be used to obtain the version information of each operation program and synchronize it to the process configuration database 212. For example, the process operation execution agent component 210 can monitor the version status of each operation program at any time. In one embodiment, in response to the process operation execution agent component 210 detecting any operation program submitted (commit) to the version control tool, the process operation execution agent component 210 can extract the operation information and version number information of the operation program , And store it in the process configuration setting database 212. Therefore, multiple operating programs and their respective operating information and version information can be recorded in the process configuration setting database 212, but the present invention is not limited to this.

In the embodiment of the present invention, the process configuration setting database 212 may provide a user setting management interface 213 for the user to set the operation flow of one or more operating programs in the process configuration setting database 212. In addition, the process configuration setting database 212 can be used to store various settings performed using the user setting management interface 213. For example, the user can select one or more operating programs through the user setting management interface 213, and set the execution host environment, execution sequence, execution timing, and program version of these operating programs.

Taking FIG. 2 as an example, assuming that the user wants to control the operating programs 216, 217, and 221 to be executed in sequence, the user can perform corresponding settings through the user setting management interface 213. Similarly, assuming that the user wants to control the operating programs 223 and 218 to be executed in sequence, the user can also make corresponding settings through the user setting management interface 213.

In different embodiments, the data content that can be stored in the process configuration setting database 212 may include: (1) Basic information of the operating program: program serial number, program name; (2) Operating program host environment data: program serial number, thread Serial number, program path, program execution parameters, host address (IP), execution program account; (3) Operating program version and executable range: serial number, program serial number, program version number, executable start time, executable end time.

In addition, the user can also define the upstream and downstream relationships between operating programs through the user setting management interface 213. Taking FIG. 2 as an example, the user can, for example, set the set formed by operating programs 216, 217, and 221 as the upstream process 214, and set the set formed by the operating programs 223, 218 as the downstream process 215 following the upstream process 214. . That is, the downstream process 215 can only be executed after the upstream process 214 is completed. In this case, the upstream process 214 and the downstream process 215 can form a set of work processes, but the present invention is not limited to this.

It should be understood that the upstream and downstream flow patterns shown in FIG. 2 are only for example, and are not intended to limit the possible implementation of the present invention. In other embodiments, users can access more or fewer operating programs according to their needs, and can also divide more levels of upstream and downstream process relationships. In order to facilitate the understanding of the concept of the present invention, the operation process shown in FIG. 2 (which includes the upstream process 214 and the downstream process 215) is taken as an example to illustrate the steps in FIG. 1.

First, in step S110, the process operation execution agent component 210 can obtain the operation process (which includes the upstream process 214 and the downstream process 215) from the process configuration setting database 212. In FIG. 2, the operating programs 216, 217, and 221 in the upstream process 214 can be temporarily referred to as upstream operating programs, the operating program 223 in the downstream process 215 can be temporarily referred to as downstream operating programs, and the process operation execution agent component 210 obtains The operation flow can indicate the individual version number and execution timing of the aforementioned upstream and downstream operation programs, but not limited to this.

After that, in step S120, the process cascade proxy component 220 can obtain multiple service cascade identification formats generated by the upstream operating program, and generate multiple process cascade identification flags accordingly. In the embodiment of the present invention, each upstream operating program may include one or more threads, and the one or more threads may be executed on one or more hosts. In addition, each thread of each upstream operating program can generate a business connection identification format correspondingly after completing execution, and the process connection agent component 220 can convert the business connection identification format into a corresponding process after obtaining the business connection identification format. Concatenate the identification flag.

Taking the operating program 216 as an example, it may include three threads 216a to 216c, and these threads 216a to 216c can be executed on one host individually, but it is not limited to this. In one embodiment, after the execution of the thread 216a is completed, a service connection identification format A16a can be generated accordingly, where the service connection identification format A16a can include a dynamic parameter field. In one embodiment, the service connection identification format A16a is, for example, "DAtoCY_${YYYMMDD}", and "${YYYMMDD}" is the dynamic parameter field, but it is not limited to this.

In one embodiment, when the process concatenation proxy component 220 detects the service concatenation identification format A16a, the process concatenation proxy component 220 can change the position of the dynamic parameter column in the service concatenation identification format A16a to the current system parameters. In order to generate the process cascade identification flag B16a corresponding to the thread 216a.

In different embodiments, the designer can select appropriate current system parameters according to requirements. Assuming that the selected current system parameter is today's date, the process concatenation agent component 220 can change the position of the dynamic parameter column in the service concatenation identification format A16a to today's date to generate a process concatenation identification flag B16a. For example, assuming that the date of the day is "July 01, 108", the process connection identification flag B16a generated by the process connection proxy component 220 may be "DAtoCY_1080701", but the present invention is not limited to this.

After that, the process connection agent component 220 can record the process connection identification flag B16a and the thread number (for example, number 1) of the thread 216a in the threads 216a~216c of the operating program 216 in the process connection identification database 222 in. In addition, the process connection proxy component 220 may also mark the use status of the process connection identification flag B16a in the process connection identification database 222 as an unused state to indicate that the process connection identification flag B16a has not been operated by any downstream operations. Program access, but not limited to this.

In one embodiment, if the process cascade proxy component 220 detects that the process cascade identification flag B16a has been used by any downstream operating program, the process cascade proxy component 220 can set the process cascade identification flag The use state of B16a is changed to the used state, so as to prevent the process chain identification flag B16a from being used by other downstream operating programs, but it is not limited to this.

Based on the above teachings, those with ordinary knowledge in the field should be able to understand the mechanism of the process cascade proxy component 220 generating the corresponding process cascade identification flag based on the service cascade identification format generated by the threads of other operating programs. Another repeat.

In the embodiment of the present invention, the process connection identification database 222 may include at least the following two data tables: (1) business connection rules (serial number, judgment rule, rule passing threshold); (2) connection identification data (Concatenated identification flag, identification generation date, identification generation source, identification use status, thread number), the serial identification flag contains business information to improve the readability of identification; the identification generation date is connected to the proxy component 220 by the process Generated is the time when the upstream process operation is completed; identify the generation source value range for each business category, such as: billing, transaction, report, etc.

After generating the process concatenation identification flag (for example, process concatenation identification flag B16a), the process concatenation proxy component 220 can determine whether at least one specific identification flag in the generated process concatenation identification flag has passed the business string Access recognition rules.

In different embodiments, the business cascade identification rules may record the conditions that the above-mentioned specific identification flags in the process cascade identification flags need to meet, and after the above-mentioned specific identification flags meet this condition, the process cascades the proxy component 220 may determine that the above-mentioned specific identification flag has passed the service connection identification rule, and continue to execute step S130.

In an embodiment, the above-mentioned specific identification flag may include a process concatenation identification flag corresponding to each thread of a certain upstream program. In this case, suppose that the business cascade identification rules indicate that the downstream process 215 can be continued after the process cascade identification flags corresponding to each thread of a specific upstream program (ie, the above-mentioned specific identification flags) are obtained. Then, the process cascading agent component 220 can determine that the specific identification flag has passed the service cascading recognition rule after obtaining the process cascading identification flag of each thread of the specific upstream program, and continue to execute step S130.

For the convenience of description, it is assumed that the operating program 221 is the specific upstream program under consideration, and it includes the threads 221a to 221c. In one embodiment, after the execution of each thread 221a~221c is completed, the process connection agent component 220 can produce the corresponding process connection according to the service connection identification format A21a, A21b, A21c provided by each thread 221a~221c Identification flags B21a, B21b, B21c (ie, specific identification flags).

Since the number of process cascade identification flags B21a, B21b, B21c matches the number of threads 221a~221c, the process cascade proxy component 220 can determine that it has obtained the process string corresponding to each thread 221a~221c of the operating program 221a Connecting the identification flags B21a, B21b, and B21c can then determine that the process cascading identification flags B21a, B21b, B21c (ie, specific identification flags) have passed the business cascading identification rules, but it is not limited to this. In this way, when the threads of the considered specific upstream program are executed by multiple hosts, the process cascade proxy component 220 can specifically control the execution status of each host, so as to determine whether to continue the downstream process 215.

In addition, in another embodiment, assuming that the service cascading identification rule indicates that the downstream process 215 can be executed after obtaining the specific identification flag that meets a certain pattern/pre-set number, the process cascading proxy component 220 After it is determined that the specific identification flag that meets a specific pattern/pre-set number has been obtained, it is determined that the specific identification flag has passed the service connection identification rule, and step S130 is continued.

For example, suppose that the business cascade identification rules indicate that a specific identification flag with the status "DAtoCY_1080701" (its meaning, for example, needs to be calculated on 108/7/1), can be continued When the downstream process 215 is executed, the process cascade proxy component 220 can continuously detect whether a specific identification flag with the state of "DAtoCY_1080701" has been obtained. If yes, the process connection agent component 220 may determine that the above-mentioned specific identification flag has passed the service connection identification rule, and continue to execute step S130.

In step S130, in response to determining that the specific identification flag in the aforementioned process cascade identification flag has passed the business cascade identification rules, the process cascade proxy component 220 can notify the downstream operating programs (such as operating programs 223, 218) to continue execution .

In summary, the present invention can produce process serial identification flags that can identify program operations on different hosts after the execution of the upstream cross-host (multi-threading) operation process is completed. The proxy component is written into the process serial identification database, and the downstream operation process detects whether the upstream operation process is completed through the process serial proxy element. In addition, if there is a multi-host environment, as long as each host environment deploys the process operation execution agent component, the version number information of the operating program of different host environments can be synchronized to the process configuration. Therefore, the present invention can be applied to a multi-threaded and cross-host application environment.

More specifically, the present invention is particularly aimed at complex application system environments (such as: application system environments spanning multiple hosts, frequently operating functions are added/removed frequently), which can efficiently assemble and manage the execution of its operating procedures. Through the various technologies and procedures of the present invention, the on/off schedule of each operation function can be clearly managed (for example, different operation functions can be switched at a certain time) and a new operation process can be quickly assembled. At the same time, it can also be developed into a distributed environment operation process automation serial connection technology to avoid the need to manually start the operation process (causing the host idle time due to waiting for execution).

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be determined by the scope of the attached patent application.

210: Process job execution agent component 211: Version Control Tool 212: Process configuration setting database 213: User Settings Management Interface 214: Upstream process 215: Downstream process 216, 217, 218, 221, 223: operating program 216a~216c, 221a~221c: thread 220: Process serial connection proxy component 222: Process serial identification database A16a, A21a, A21b, A21c: Business serial connection identification format B16a, B21a, B21b, B21c: process identification flag S110~S130: steps

FIG. 1 is a flowchart of a method for controlling a work flow according to an embodiment of the present invention. Fig. 2 is an application scenario diagram drawn according to an embodiment of the present invention.

S110~S130: steps

Claims (6)

A method for regulating and controlling a working process includes: obtaining a working flow from a flow configuration setting database by a flow execution agent component, wherein the working flow records multiple upstream working programs and multiple downstream working among the working programs The individual version number and execution timing of the program, and the upstream operating programs form an upstream process, and the downstream operating programs form a downstream process following the upstream process; the upstream operating programs are obtained by a process serial proxy component And generate multiple process concatenation identification flags accordingly; in response to determining that at least one of the process concatenation identification flags has passed a business concatenation identification rule, The process connection agent component notifies the downstream operating programs to continue execution, wherein the upstream operating programs include a specific upstream program, and the specific upstream program includes at least one specific thread corresponding to the at least one specific identification flag, and The method further includes: in response to determining that the number of the at least one specific identification flag matches the number of the at least one specific thread, determining that the at least one specific identification flag has passed the business cascade identification rule, or is reflected in the determination The number of the at least one specific identification flag reaches a preset threshold, and it is determined that the at least one specific identification flag has passed the service connection identification rule. For example, the method described in item 1 of the scope of patent application further includes: in response to detecting a specific operating program submitted to a version control tool, the process operation execution agent component extracts the operating information and version of the specific operating program number The information is stored in a process configuration setting database, where the process configuration setting database records multiple operating programs and the operating information and version number information of each operating program. For example, the method described in item 1 of the scope of patent application, wherein each of the business cascade identification formats includes a dynamic parameter field, the process cascade identification flags are recorded in a process cascade identification database, and the upstream operating programs It includes a first program, the first program includes at least one thread, a first thread in the at least one thread generates a first service connection identification format after the execution is completed, and the proxy component is connected by the process The step of obtaining the business connection identification formats generated by the upstream operating programs and generating the process connection identification flags accordingly includes: responding to the detection of the first business connection identification generated by the first thread Format, the process cascade agent component changes the position of the dynamic parameter column in the first service cascade identification format to a current system parameter to generate a first process cascade identification flag corresponding to the first thread Mark; the first process concatenation identification flag and a thread number of the first thread in the at least one thread are recorded in the process concatenation identification database; the process is concatenated by the proxy component The use state of the first process serial identification flag in the serial identification database is marked as an unused state. For example, the method described in item 3 of the scope of patent application further includes: in response to determining that the first process cascading identification flag has been used by any of the downstream operating programs, the process cascading agent component performs the first process The use status of a process serial identification flag is changed to a used status. For the method described in item 3 of the scope of patent application, the business connection identification rules are recorded in the process connection identification database. For the method described in item 3 of the scope of patent application, the first service connection identification format is characterized as DAtoCY_${YYYMMDD}, where ${YYYMMDD} is the dynamic parameter field, and the current system parameter is a date of the day.

Images