CN105573851B - Flow cooperative processing method and system - Google Patents
Flow cooperative processing method and system Download PDFInfo
- Publication number
- CN105573851B CN105573851B CN201510944075.XA CN201510944075A CN105573851B CN 105573851 B CN105573851 B CN 105573851B CN 201510944075 A CN201510944075 A CN 201510944075A CN 105573851 B CN105573851 B CN 105573851B
- Authority
- CN
- China
- Prior art keywords
- flow
- cooperative
- server
- collaborative
- main
- 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
Images
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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- 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
Abstract
The application discloses a flow cooperative processing method and a system, wherein a main flow server sends a cooperative message comprising an identification of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located to a service platform when determining that a current active node to which the main flow runs needs to perform flow cooperative processing, the service platform sends a notification message comprising the identification of the cooperative flow to the cooperative flow server according to the address of the cooperative flow server to trigger the cooperative flow server to start the cooperative flow corresponding to the identification of the cooperative flow and receive feedback information indicating a cooperative flow execution result sent by the cooperative flow server, and when determining that the feedback information meets a preset condition, sends operation indication information to the main flow server to notify the main flow server to continue to run the main flow. According to the scheme of the application, the flow cooperative processing between the main flow server and the cooperative flow server can be realized, and a series of cross-system complex business operations can be completed.
Description
Technical Field
The present application relates to the technical field of workflow processing, and more particularly, to a method and a system for processing a flow.
Background
The workflow middleware is a mature middleware product and is widely applied to solving the process computerization problems of governments and enterprises. The workflow is abstract, summary and description of a workflow and business rules among operation steps of the workflow.
Because users are distributed in different geographic locations and organizations and work on different software and hardware platforms, the situation that the workflow engines are mutually invoked often occurs, and therefore a flow cooperative processing scheme is urgently needed to cooperatively complete the processing of the business.
Disclosure of Invention
In view of this, the present application provides a flow cooperative processing method and a system, which are used to provide a flow cooperative processing method to prompt a main flow server and a cooperative flow server to cooperatively complete business processing.
In order to achieve the above object, the following solutions are proposed:
a flow cooperative processing method is applied to a service platform, and comprises the following steps:
receiving a cooperative message which is sent by a main process server and comprises an identifier of a cooperative process and an address of the cooperative process server where the cooperative process is located, wherein the cooperative message is sent to a service platform when the main process server determines that a current active node to which the main process runs needs to perform process cooperative processing;
sending notification information to the collaborative flow server according to the address of the collaborative flow server, wherein the notification information includes an identifier of the collaborative flow and is used for the collaborative flow server to start a collaborative flow corresponding to the identifier of the collaborative flow;
receiving feedback information which is sent by the collaborative process server and indicates a collaborative process execution result, and sending operation indication information to the main process server when the feedback information is determined to meet a preset condition, wherein the operation indication information is used for informing the main process server to continue to operate the main process.
Preferably, the cooperative message further includes an identifier of the main process, and further, the operation indication information sent to the main process server carries the identifier of the main process, so as to notify the main process server to continue to operate the main process corresponding to the identifier of the main process.
Preferably, before the sending notification information to the collaborative process server according to the address of the collaborative process server, the method further includes:
creating a flow cooperative processing event in a flow cooperative recording log, wherein the flow cooperative processing event comprises an identifier of the main flow and an identifier of the cooperative flow.
Preferably, after receiving the feedback information indicating the execution result of the collaborative process sent by the collaborative process server, the method further includes:
and storing the feedback information into the flow cooperative processing event.
Preferably, the process of determining whether the feedback information satisfies a preset condition is:
judging whether the feedback information indicates that the cooperative flow is initiated, if so, determining that the feedback information meets a preset condition;
alternatively, the first and second electrodes may be,
and judging whether the feedback information indicates that the cooperative flow is executed completely, if so, determining that the feedback information meets the preset condition.
A flow cooperative processing method is applied to a main flow server running a main flow, and comprises the following steps:
when determining that the current active node to which the main process runs needs to perform process cooperative processing, locking the current active node and inquiring the type of the process cooperative processing;
if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to a service platform, wherein the cooperative message comprises an identifier of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located, and the cooperative message is used for triggering the service platform to send notification information to the cooperative flow server according to the address of the cooperative flow server so as to start the cooperative flow corresponding to the identifier of the cooperative flow;
and receiving operation indication information sent by the service platform, and continuing to operate the main process, wherein the operation indication information is the operation indication information sent to the main process server when the service platform receives feedback information which is sent by the collaborative process server and indicates the execution result of the collaborative process, and the operation indication information is judged to be sent to the main process server when the feedback information meets the preset condition.
Preferably, if the type of the flow cooperative processing is a synchronization type, while the step of sending the cooperative message to the service platform is executed, the method further includes:
and continuing to operate the main process.
Preferably, the cooperative message further includes an identifier of the main process, and further, the received operation indication information sent by the service platform carries the identifier of the main process.
A flow cooperative processing method is applied to a cooperative flow server for operating a cooperative flow, and comprises the following steps:
receiving notification information sent by a service platform, wherein the notification information comprises an identifier of a collaborative process, and the notification information is notification information sent to a collaborative process server by the service platform in response to a collaborative message which is sent by a main process server and comprises the identifier of the collaborative process and an address of the collaborative process server where the collaborative process is located;
and starting the cooperative flow corresponding to the identification of the cooperative flow, and sending the execution result of the cooperative flow as feedback information to the service platform.
A process co-processing system, comprising: main flow server, service platform and collaborative flow server, wherein:
when the main process server determines that the current active node to which the main process runs needs to be subjected to process cooperative processing, the current active node is locked, and the type of the process cooperative processing is inquired; if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to a service platform, wherein the cooperative message comprises an identifier of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located;
the service platform sends notification information to the collaborative flow server according to the address of the collaborative flow server, wherein the notification information comprises the identification of the collaborative flow;
when receiving notification information sent by a service platform, the cooperative flow server starts a cooperative flow corresponding to the identification of the cooperative flow, and sends an execution result of the cooperative flow as feedback information to the service platform;
and when the service platform determines that the feedback information meets the preset condition, the service platform sends operation indication information to the main process server to trigger the main process server to continue to operate the main process.
It can be seen from the foregoing technical solutions that, in the flow cooperative processing method provided in the embodiments of the present application, when it is determined that the current active node to which the main flow runs needs to perform flow cooperative processing, sending a cooperative message including an identifier of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located to a service platform, sending notification information including the identifier of the cooperative flow to the cooperative flow server by the service platform according to the address of the cooperative flow server, triggering the cooperative process server to start the cooperative process corresponding to the identification of the cooperative process, and further receiving feedback information indicating the execution result of the cooperative process sent by the cooperative process server, and when the feedback information is determined to meet the preset condition, sending operation indication information to the main process server to inform the main process server to continue operating the main process. According to the scheme of the application, the flow cooperative processing between the main flow server and the cooperative flow server can be realized, and a series of cross-system complex business operations can be completed.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic diagram of a flow cooperative processing signaling interaction disclosed in an embodiment of the present application;
fig. 2 is a flowchart of a flow cooperative processing method disclosed from the perspective of a main flow server in the embodiment of the present application;
FIG. 3 is a flowchart of a flow collaborative processing method disclosed from the perspective of a service platform in the embodiment of the present application;
fig. 4 is a flowchart of a flow collaborative processing method disclosed from the perspective of a collaborative flow server in the embodiment of the present application;
fig. 5 is a schematic structural diagram of a flow cooperative processing system disclosed in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
First, referring to fig. 1, fig. 1 is a schematic diagram of a flow cooperative processing signaling interaction disclosed in an embodiment of the present application.
In the process of the flow cooperative processing, signaling interaction is performed among the main flow server 11, the service platform 12 and the cooperative flow server 13, which is shown in detail in fig. 1.
As shown in fig. 1, the method includes:
step S1, when determining that the current active node to which the main process runs needs to perform the process coordination, the main process server 11 locks the current active node and queries the type of the process coordination;
specifically, a main process is run on the main process server, and the main process includes a plurality of active nodes and runs according to a set flow direction. When the current active node is operated to a certain active node, whether the current active node needs to perform flow cooperative processing or not is inquired.
For the process of inquiring whether the current active node needs to perform the process cooperative processing, the process cooperative relationship can be configured in advance, and the identifiers of a plurality of processes needing to be subjected to the cooperation and the nodes subjected to the cooperation in the processes are recorded in the process cooperative relationship.
If it is determined that a certain active node needs to perform flow cooperative processing, the current active node is locked, and the type of the flow cooperative processing is further queried. After the back active node is locked, the main process cannot continue to run.
The types of flow coprocessing include synchronous types and asynchronous types. The synchronization type is that the execution condition of the cooperative flow and the execution of the main flow are not affected mutually, and no sequence requirement exists. The asynchronous type is that the execution of the main flow must depend on the execution condition of the cooperative flow, for example, the main flow can be executed only after the cooperative flow is initiated or executed.
Step S2, when determining that the type of the process cooperative processing is an asynchronous type, the main process server 11 sends a cooperative message to the service platform 12;
the cooperative message includes an identifier of the cooperative process and an address of a cooperative process server where the cooperative process is located. The number of the collaborative process servers may be multiple, and each collaborative process server may run multiple collaborative processes simultaneously. Therefore, the collaboration message sent by the main process server 11 to the service platform 12 needs to carry the identifier of the collaboration process and the address of the collaboration process server where the collaboration process is located.
Optionally, the collaboration message may further include an identifier of the main flow.
Step S3, the service platform 12 sends notification information to the collaborative process server 13 according to the address of the collaborative process server;
wherein the notification information includes an identifier of the collaborative flow. The notification information is used to trigger the cooperative process server 13 to start the cooperative process.
Step S4, when receiving the notification information sent by the service platform 12, the collaborative process server 13 starts a collaborative process corresponding to the identifier of the collaborative process;
specifically, if the collaborative flow corresponding to the identifier of the collaborative flow has already been created, the created collaborative route may be directly started, otherwise, the collaborative flow may be created first, and then the created collaborative flow may be started.
Step S5, the cooperative process server 13 sends the execution result of the cooperative process as feedback information to the service platform 12;
specifically, after the cooperative process is started, the cooperative process server 13 sends an execution result of the cooperative process to the service platform 12.
Optionally, the notification information sent by the service platform 12 to the collaborative process server 13 may include a collaborative configuration parameter, where the collaborative configuration parameter is used to notify the collaborative process server 13 when to feed back the execution result of the collaborative process to the service platform 12, for example, the execution result is fed back after the collaborative process is initiated, or the execution result is fed back after the collaborative process is completed.
Step S6, when determining that the feedback information meets the preset condition, the service platform 12 sends operation instruction information to the main process server 11;
specifically, for each collaborative process, a preset condition corresponding to the collaborative process is set, and when it is determined that the feedback information sent by the collaborative process server 13 satisfies the preset condition, the operation instruction information is sent to the main process server 11. The preset condition may include that the feedback information indicates that the collaborative process has been initiated, or that the feedback information indicates that the collaborative process has been executed.
In step S7, the main process server 11 continues to operate the main process when receiving the operation instruction information.
On the basis of the above, if the main flow server 11 determines in step S2 that the type of the flow cooperation process is the asynchronous type, the main flow server 11 may continue to execute the main flow while sending the cooperation message to the service platform 12.
According to the scheme of the application, the flow cooperative processing between the main flow server and the cooperative flow server can be realized, and a series of cross-system complex business operations can be completed.
Optionally, the service platform described in the present application may provide an entry for configuration and maintenance of the user collaboration relationship. The user can perform configuration and maintenance of the collaborative relationship through the service platform, such as: and adding, deleting, forbidding, enabling and the like the cooperative relationship.
The user can select the flow to be coordinated, the asynchronous or synchronous type, the operation needing the coordination and the like through a configuration and maintenance interface of the coordination relation provided by the service platform.
The user configured collaborative relationship may be stored in a collaborative configuration database for the main process server and the collaborative process server to query.
Next, the present application scheme is described in detail from the perspective of the main process server, the service platform, and the collaborative process server, respectively.
First, referring to fig. 2, fig. 2 is a flowchart of a flow cooperative processing method disclosed from the perspective of a main flow server in the embodiment of the present application.
As shown in fig. 2, the method includes:
s200, when it is determined that the current active node to which the main process runs needs to be subjected to process cooperative processing, locking the current active node, and inquiring the type of the process cooperative processing;
specifically, the main process runs on the main process server, and the main process includes a plurality of active nodes, which are sequentially executed according to a set sequence. When a certain active node is operated, when the current active node is determined to need to carry out flow cooperative processing, the current active node is firstly locked, and the type of the flow cooperative processing is inquired.
The main flow will temporarily be unable to continue after locking the current active node. The types of flow coprocessing include synchronous types and asynchronous types.
Further, whether the current active node needs to perform the process of the process cooperative processing may be determined by querying a preset cooperative relationship library, where each process cooperative relationship is configured in the cooperative relationship library, and related information of the process that needs to be cooperatively processed (for example, an identifier of the process, an address of a server where the process is located, and the like) and which active node needs to perform the process cooperative processing in the process are recorded.
Step S210, if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to a service platform;
the cooperative information is used for triggering a service platform to send notification information to the cooperative flow server according to the address of the cooperative flow server so as to start the cooperative flow corresponding to the cooperative flow identifier.
The collaboration message sent by the main process server to the service platform may be obtained by querying a preset collaboration relation library.
Step S220, receiving the operation instruction information sent by the service platform, and continuing to operate the main process.
Specifically, the operation indication information is feedback information indicating a cooperative process execution result and sent by the service platform when receiving the cooperative process server, and operation indication information sent to the main process server when judging that the feedback information meets a preset condition.
And when the main process server receives the operation indication information, unlocking the current active node in the locking state, and further continuing to operate the main process.
According to the scheme of the application, when the main process running on the main process server runs to a certain active node needing the process cooperative processing, the cooperative processing of the process is realized through the service platform and the cooperative process server.
Optionally, when the type of the flow cooperative processing is determined, if it is determined that the type of the flow cooperative processing is a synchronization type, the method may further include, while performing step S210:
and continuing to operate the main process.
That is, if the type of the flow cooperative processing is the synchronous type, the execution sequence of the main flow and the cooperative flow is parallel, and the main flow does not need to wait for the feedback of the execution result of the cooperative flow to restart the execution.
Optionally, the collaboration message may further include an identifier of the main flow. That is, when the main process server sends the collaboration message to the service platform, the main process server also sends the identifier of the main process. The identification of the main process can be used for the business platform to record the process co-processing event. In addition, if a plurality of main processes send the cooperative message to the service platform, the service platform can uniquely mark the main processes through the identification of the main processes. And when the service platform receives the feedback information sent by the collaborative process corresponding to the identifier of the collaborative process in the collaborative message and determines that the feedback information meets the preset condition, the service platform sends operation indication information to the main process server, wherein the operation indication information carries the identifier of the main process, and the main process server can determine the corresponding main process according to the identifier of the main process so as to continue to operate the main process.
Next, referring to fig. 3, fig. 3 is a flowchart of a flow cooperative processing method disclosed from the perspective of the service platform in the embodiment of the present application.
As shown in fig. 3, the method includes:
step S300, receiving a cooperative message which is sent by a main process server and comprises an identification of a cooperative process and an address of a cooperative process server where the cooperative process is located;
specifically, as can be seen from the previous embodiment, the cooperative message is a cooperative message sent to the service platform by the main process server when it is determined that the current active node to which the main process runs needs to perform the process cooperative processing.
Step S310, sending notification information to the collaborative process server according to the address of the collaborative process server;
the notification information includes an identifier of the collaborative process, and the notification information is used for a collaborative process server to start a collaborative process corresponding to the identifier of the collaborative process.
Step S320, receiving feedback information indicating a result of executing the collaborative process sent by the collaborative process server, and sending operation instruction information to the main process server when it is determined that the feedback information satisfies a preset condition.
The operation indication information is used for informing the main process server to continue operating the main process.
The service platform provided by the embodiment realizes interaction of communication instructions between the main process server and the collaborative process server, and ensures collaborative processing of the processes.
Optionally, the above-mentioned collaboration message may further include an identification of the main flow. Furthermore, when the service platform sends the operation indication information to the main process server again, the identifier of the main process may be written into the operation indication information to notify the main process server to continue to operate the main process corresponding to the identifier of the main process.
Optionally, before the step S310, the method may further include:
creating a flow cooperative processing event in a flow cooperative recording log, wherein the flow cooperative processing event comprises an identifier of the main flow and an identifier of the cooperative flow.
The flow collaborative recording log of the service platform records a plurality of flow collaborative processing events, and the flow collaborative processing events record the main flow of the collaborative processing and the identification of the collaborative flow.
Further, when receiving feedback information indicating a result of executing the collaborative process sent by the collaborative process server, the service platform may store the feedback information in the process collaborative processing event.
Optionally, the service platform may further query a collaborative configuration parameter of the collaborative process, and then send the collaborative configuration parameter to the collaborative process server when sending the notification information to the collaborative process server. The collaborative configuration parameter is used for indicating when the collaborative server sends the execution result of the collaborative flow as feedback information to the service platform. Generally, after the initiation of the collaborative process is monitored, or after the execution of the collaborative process is monitored to be completed, the execution result of the collaborative process is sent to the service platform as feedback information.
On this basis, the process of determining whether the feedback information meets the preset condition, that is, whether the feedback information meets the requirement of the cooperative configuration parameter is determined:
judging whether the feedback information indicates that the cooperative flow is initiated, if so, determining that the feedback information meets a preset condition; alternatively, the first and second electrodes may be,
and judging whether the feedback information indicates that the cooperative flow is executed completely, if so, determining that the feedback information meets the preset condition.
Further, referring to fig. 4, fig. 4 is a flowchart of a flow collaborative processing method disclosed from the perspective of a collaborative flow server in the embodiment of the present application.
As shown in fig. 4, the method includes:
step S400, receiving notification information sent by a service platform, wherein the notification information comprises an identifier of a collaborative process;
the notification information is notification information sent by the service platform to the collaborative process server in response to the collaborative message which is sent by the main process server and includes the identification of the collaborative process and the address of the collaborative process server where the collaborative process is located.
Step S410, starting a cooperative flow corresponding to the identifier of the cooperative flow, and sending an execution result of the cooperative flow as feedback information to the service platform.
And when receiving the notification information sent by the service platform, the cooperative flow server starts the cooperative flow corresponding to the identification of the cooperative flow in the notification information. And sending the execution result of the collaborative flow as feedback information to the service platform.
The notification information may carry the cooperative configuration parameters of the cooperative process, and the cooperative process server may refer to the feedback time indicated by the cooperative configuration parameters, and send the feedback information to the service platform after the cooperative process is initiated or the cooperative process is executed.
Further, if the collaborative process corresponding to the identifier of the collaborative process in the notification information is not created in the collaborative process server, the collaborative process is created first, and then the created collaborative process is started.
The embodiments described above introduce the present application from the perspective of the main process server, the service platform, and the collaborative process server, respectively.
On the basis of the above embodiments, the service platform of the present application may also provide an interface for the user to perform process collaborative monitoring. According to the embodiment, the flow collaborative recording log of the service platform records the collaborative processing events of each flow. Therefore, the corresponding flow cooperative processing event can be inquired according to the flow identification input by the user. Of course, the flow cooperative processing event meeting the conditions can be displayed to the user according to the query date input by the user.
Finally, the embodiment of the application discloses a flow cooperative processing system. Referring to fig. 5, fig. 5 is a schematic structural diagram of a flow cooperative processing system disclosed in the embodiment of the present application.
As shown in fig. 5, the system includes:
when determining that the current active node to which the main process runs needs to perform process cooperative processing, the main process server 11 locks the current active node and queries the type of the process cooperative processing; if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to the service platform 12, where the cooperative message includes an identifier of the cooperative flow and an address of a cooperative flow server 13 where the cooperative flow is located;
the service platform 12 sends notification information to the collaborative process server 13 according to the address of the collaborative process server 13, where the notification information includes an identifier of the collaborative process;
when receiving the notification information sent by the service platform 12, the cooperative flow server 13 starts a cooperative flow corresponding to the identifier of the cooperative flow, and sends the execution result of the cooperative flow as feedback information to the service platform 12;
when determining that the feedback information meets the preset condition, the service platform 12 sends operation instruction information to the main process server 11 to trigger the main process server 11 to continue operating the main process.
According to the flow cooperative processing system provided by the application, the flow cooperative processing between the main flow server and the cooperative flow server can be realized, and a series of cross-system complex business operations can be completed.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A flow cooperative processing method is characterized in that the method is applied to a service platform and comprises the following steps:
receiving a cooperative message which is sent by a main process server and comprises an identification of a cooperative process and an address of the cooperative process server where the cooperative process is located, wherein the cooperative message is the cooperative message which is sent to a service platform when the main process server determines that a current active node to which the main process runs needs to be subjected to process cooperative processing, locks the current active node, inquires the type of the process cooperative processing, and when the type of the process cooperative processing is an asynchronous type or when the main program of the current active node is continuously run after the type of the process cooperative processing is judged to be a synchronous type;
sending notification information to the collaborative flow server according to the address of the collaborative flow server, wherein the notification information includes an identifier of the collaborative flow and is used for the collaborative flow server to start a collaborative flow corresponding to the identifier of the collaborative flow;
receiving feedback information which is sent by the collaborative process server and indicates a collaborative process execution result, and sending operation indication information to the main process server when the feedback information is determined to meet a preset condition, wherein the operation indication information is used for informing the main process server to continue to operate the main process.
2. The method according to claim 1, wherein the coordination message further includes an identifier of the main flow, and further, the operation indication information sent to the main flow server carries the identifier of the main flow, so as to notify the main flow server to continue to operate the main flow corresponding to the identifier of the main flow.
3. The method according to claim 2, before the sending notification information to the collaborative process server according to the address of the collaborative process server, further comprising:
creating a flow cooperative processing event in a flow cooperative recording log, wherein the flow cooperative processing event comprises an identifier of the main flow and an identifier of the cooperative flow.
4. The method according to claim 3, wherein after receiving the feedback information indicating the execution result of the collaborative process sent by the collaborative process server, the method further comprises:
and storing the feedback information into the flow cooperative processing event.
5. The method of claim 1, wherein determining whether the feedback information satisfies a preset condition is performed by:
judging whether the feedback information indicates that the cooperative flow is initiated, if so, determining that the feedback information meets a preset condition;
alternatively, the first and second electrodes may be,
and judging whether the feedback information indicates that the cooperative flow is executed completely, if so, determining that the feedback information meets the preset condition.
6. A flow cooperative processing method is characterized by being applied to a main flow server running a main flow, and comprises the following steps:
when determining that the current active node to which the main process runs needs to perform process cooperative processing, locking the current active node and inquiring the type of the process cooperative processing;
if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to a service platform, wherein the cooperative message comprises an identifier of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located, and the cooperative message is used for triggering the service platform to send notification information to the cooperative flow server according to the address of the cooperative flow server so as to start the cooperative flow corresponding to the identifier of the cooperative flow;
receiving operation indication information sent by the service platform, and continuing to operate the main process, wherein the operation indication information is feedback information which is sent by the service platform and indicates a cooperative process execution result and is sent to the main process server when the feedback information meets a preset condition;
and if the type of the flow cooperative processing is a synchronous type, continuing to run the main flow while executing the step of sending the cooperative message to the service platform.
7. The method according to claim 6, wherein the coordination message further includes an identifier of the main flow, and further, the received operation indication information sent by the service platform carries the identifier of the main flow.
8. A process co-processing system, comprising: main flow server, service platform and collaborative flow server, wherein:
when the main process server determines that the current active node to which the main process runs needs to be subjected to process cooperative processing, the current active node is locked, and the type of the process cooperative processing is inquired; if the type of the flow cooperative processing is an asynchronous type, sending a cooperative message to a service platform, wherein the cooperative message comprises an identifier of a cooperative flow and an address of a cooperative flow server where the cooperative flow is located;
the service platform sends notification information to the collaborative flow server according to the address of the collaborative flow server, wherein the notification information comprises the identification of the collaborative flow;
when receiving notification information sent by a service platform, the cooperative flow server starts a cooperative flow corresponding to the identification of the cooperative flow, and sends an execution result of the cooperative flow as feedback information to the service platform;
when the service platform determines that the feedback information meets a preset condition, the service platform sends operation indication information to the main process server to trigger the main process server to continue to operate the main process;
and if the type of the flow cooperative processing is a synchronous type, continuing to run the main flow while executing the step of sending the cooperative message to the service platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510944075.XA CN105573851B (en) | 2015-12-16 | 2015-12-16 | Flow cooperative processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510944075.XA CN105573851B (en) | 2015-12-16 | 2015-12-16 | Flow cooperative processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105573851A CN105573851A (en) | 2016-05-11 |
| CN105573851B true CN105573851B (en) | 2020-06-12 |
Family
ID=55884020
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510944075.XA Active CN105573851B (en) | 2015-12-16 | 2015-12-16 | Flow cooperative processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105573851B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107909330B (en) * | 2017-08-31 | 2020-10-09 | 平安科技（深圳）有限公司 | Workflow data processing method and device, storage medium and computer equipment |
| CN110675130A (en) * | 2019-09-30 | 2020-01-10 | 佛山市众联成云科技有限公司 | Cross-main-body workflow collaboration method |
| CN111291091A (en) * | 2020-02-07 | 2020-06-16 | 北京神州泰岳智能数据技术有限公司 | Data processing method and device and data processing system |
| CN117314354B (en) * | 2023-10-07 | 2024-04-16 | 广州石伏软件科技有限公司 | Cross-system collaboration method and system based on flow engine |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104463508A (en) * | 2014-12-30 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Coordination method and device between multiple workflow systems |
| CN104750544A (en) * | 2013-12-30 | 2015-07-01 | 中国银联股份有限公司 | Process management system and process management method applied to distributed system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7475275B2 (en) * | 2005-10-27 | 2009-01-06 | International Business Machines Corporation | Method for fault handling in a co-operative workflow environment |
| CN104992271B (en) * | 2015-06-23 | 2020-03-10 | 四川久远银海软件股份有限公司 | System for collaborative operation of different process instances and implementation method thereof |
-
2015
- 2015-12-16 CN CN201510944075.XA patent/CN105573851B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104750544A (en) * | 2013-12-30 | 2015-07-01 | 中国银联股份有限公司 | Process management system and process management method applied to distributed system |
| CN104463508A (en) * | 2014-12-30 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Coordination method and device between multiple workflow systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105573851A (en) | 2016-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105573851B (en) | Flow cooperative processing method and system | |
| US7266734B2 (en) | Generation of problem tickets for a computer system | |
| AU2016352206A1 (en) | Data processing method and device | |
| JP2015514247A5 (en) | ||
| CN110619226A (en) | Platform-based data processing method, system, equipment and storage medium | |
| CN110597695A (en) | Alarm method, alarm device, computer equipment and readable storage medium | |
| CN111355802A (en) | Information pushing method and device | |
| CN110535939B (en) | Service discovery and preemption method, device, computer equipment and storage medium | |
| CN113961332A (en) | Method and device for realizing workflow engine, electronic equipment and storage medium | |
| CN110955460A (en) | Service process starting method and device, electronic equipment and storage medium | |
| JP2015032293A (en) | Document management apparatus and document management program | |
| CN110990145A (en) | Background task processing mechanism and method for distributed system | |
| CN113220480B (en) | Distributed data task cross-cloud scheduling system and method | |
| EP3503479A1 (en) | Flow entry management method and device | |
| CN113094053B (en) | Delivery method and device of product and computer storage medium | |
| CN108829709A (en) | Distributed database management method, apparatus, storage medium and processor | |
| CN113094088A (en) | Database configuration information acquisition method and device, computer equipment and storage medium | |
| CN115114303A (en) | Service data auditing method, platform and system | |
| CN112035411A (en) | Log alarm method, device and system and electronic equipment | |
| CN113553126B (en) | Data processing method and device | |
| CN111178044B (en) | Method and device for determining target text elements | |
| CN108600077B (en) | Timing message processing method and message management server | |
| CN115604135B (en) | Service monitoring method and device | |
| CN115981710A (en) | Code conflict warning method and device, electronic equipment and storage medium | |
| CN109597820B (en) | Client information synchronization method, device and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |