CN112101803A - Business process monitoring method, device, system, equipment and medium - Google Patents

Abstract

The application discloses a business process monitoring method, a device, a system, equipment and a medium, wherein the method is executed by a server associated with a business process engine, and the method comprises the following steps: receiving state information reported by each task node of a pre-created service flow in a service flow engine, wherein the service flow comprises at least two task nodes, and the state information at least comprises task starting time and task ending time reported by each task node; and determining whether each task node has overtime fault or not based on the state information of each task node and node configuration information corresponding to each task node, wherein the node configuration information is configured in advance when the flow of the service flow engine is defined. According to the technical scheme provided by the embodiment of the application, the problem of overtime faults of each task node in the business process is judged in real time by analyzing the state information reported by the task nodes, and the monitoring efficiency of the business process is effectively improved.

Description

Business process monitoring method, apparatus, system, device and medium

technical field

The present application generally relates to the technical field of enterprise management software, and specifically relates to a business process monitoring method, apparatus, system, device and medium.

Background technique

In modern social life, it is a common business processing method to implement a business process through a business terminal to achieve a business purpose. The business process is determined by connecting at least two task nodes according to business logic.

In the related art, generally after the execution of the business process is completed, it is judged whether the business process has a fault during the execution process. At present, for a complex business process with many task nodes, when it is determined that the execution process of the business process is faulty, the faulty task node cannot be accurately determined, so that the fault cannot be accurately and efficiently repaired.

SUMMARY OF THE INVENTION

In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a business process monitoring method, apparatus, system, device and medium that can monitor whether a task node in a business process has a timeout fault.

In a first aspect, an embodiment of the present application provides a business process monitoring method, the method is executed by a server associated with a business process engine, and the method includes:

Receive status information reported by each task node of a pre-created business process in the business process engine, the business process includes at least two task nodes, and the state information at least includes the task start time or task end time reported by each task node;

Based on the state information of each task node and the node configuration information corresponding to each task node, it is determined whether each task node has a timeout fault, and the node configuration information is pre-configured during the process definition of the business process engine.

In a second aspect, an embodiment of the present application provides a business process monitoring device, the device is configured on a server associated with a business process engine, and the device includes:

The first receiving module is configured to receive state information reported by each task node of a pre-created business process in the business process engine, the business process includes at least two task nodes, and the state information at least includes the task reported by each task node start time or task end time;

The first determination module is configured to determine whether each task node has a timeout failure based on the state information of each task node and the node configuration information corresponding to each task node, and the node configuration information is defined in the process of the business process engine. pre-configured.

In a third aspect, an embodiment of the present application provides a business process monitoring system, where the system includes a business terminal and a server including:

The business terminal, which includes a business process engine running on it, is configured to report the status information of each task node of the business process pre-created in the business process engine to the server, the business process includes at least two task nodes, the The status information includes at least the task start time or task end time reported by each task node;

The server is configured to receive status information from the service terminal, and based on the status information of each task node and the node configuration information corresponding to each task node, determine whether each task node has a timeout failure, and the node configuration information is in the service node. The process engine's process definition is pre-configured.

In a fourth aspect, an embodiment of the present application provides a computer device, the computer device includes a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor is configured to implement the method of the first aspect when executing the program .

In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and the computer program is used to implement the method of the first aspect.

The method, device, system, device and medium for monitoring a business process provided by the embodiments of the present application, the method receives the state information reported by all task nodes in the business process, and based on the state information reported by each task node and its corresponding Configured configuration information to determine whether each task node has a timeout fault, so as to accurately determine the faulty task node, realize real-time monitoring of each task node in the process of business process processing, and improve the accuracy of fault monitoring in the business process process. to ensure accurate and efficient repair of faults.

Description of drawings

Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

FIG. 1 is an implementation environment architecture diagram of monitoring of a business process provided by the application embodiment;

2 is a schematic flowchart of a method for monitoring a business process provided by an application embodiment;

3 is a schematic flowchart of another method for monitoring a business process provided by the application embodiment;

4 is a schematic diagram of a deployment and monitoring process of a business process provided by an embodiment of the application;

5 is a flowchart of an order processing process for a product provided by the application embodiment;

6 is a schematic structural diagram of an apparatus for monitoring a business process provided by an embodiment of the application;

7 is a schematic structural diagram of another apparatus for monitoring a business process provided by an embodiment of the application;

8 is a schematic structural diagram of another apparatus for monitoring a business process provided by an embodiment of the application;

9 is a schematic structural diagram of another apparatus for monitoring a business process provided by an embodiment of the application;

FIG. 10 is a schematic structural diagram of another business process monitoring device provided by an embodiment of the application.

Detailed ways

The present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the related invention, but not to limit the invention. In addition, it should be noted that, for the convenience of description, only the parts related to the invention are shown in the drawings.

It should be noted that the embodiments in the present application and the features of the embodiments may be combined with each other in the case of no conflict. The present application will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.

With the development of Internet technology, using efficient and convenient business systems to process business has become a common business processing method in modern life. Business systems can usually integrate multiple business processes to meet the needs of business purposes. For example, the enterprise management system can be equipped with a leave approval process, a cargo management process and a fund application process.

The design of the business process is one of the core tasks in the process of building a business system. The process engine can arrange and combine at least one task node according to a certain protocol to achieve a business purpose. Flowable is a commonly used process engine that allows developers to design business processes in the form of flowcharts based on the BPMN2.0 (English: Business Process Model and Notation, Chinese: Business Process Model and Notation) protocol standard, reducing business process design. difficulty.

Usually, the monitoring mechanism can be configured in the protocol for designing the business process. After the execution of the business process, the status information of the business process obtained by the monitoring mechanism can be used to help operators determine whether the business process is faulty during the execution process. However, for the business process designed based on the BPMN2.0 protocol standard, in the actual execution process of the business process, it is generally only judged whether the entire business process is faulty. For example, by monitoring the start time and end time of the business process, the The time difference between the start time and the end time of the business process is compared with the allowable execution time of the business process to determine whether the execution time of the business process has timed out. After the execution of the business process, the business process fault monitoring technology is used to determine whether the execution process of the business process is faulty. For a complex business process including multiple task nodes, since it is impossible to accurately monitor the faulty task node, it is very difficult for operation and maintenance personnel. Troubleshooting caused a great burden.

FIG. 1 is an implementation environment architecture diagram of a business process monitoring method provided by an embodiment of the present application. As shown in FIG. 1 , the implementation environment architecture includes: a service terminal 110 and a server 120 .

The service terminal 100 may be pre-installed with a software system for managing an enterprise, and the software system may execute a specific business process in response to an operation input by the user, so as to achieve a business purpose corresponding to the business process. The software system can rely on the business process engine to manage business operations.

During the execution of the business process, the service terminal 110 can send the state information of each task node in the business process to the server 120, so that the server 120 can judge whether the task node appears during the execution process based on the state information of each task node If there is a fault, the state information of the task node includes first state information of the task node start execution event and second state information of the end execution event. After the execution of the business process, the service terminal 110 may also send the state information of the business process to the server 120, so that the server 120 can judge whether the business process fails during the execution process based on the state information of the business process, and the state of the business process The information includes third state information of the business process end execution event.

In this application, the type of the service terminal 100 may include, but is not limited to, a smart phone, a tablet computer, a television, a notebook computer, a desktop computer, and the like, which are not specifically limited in this embodiment of the application.

The server 120 has data processing and storage functions, and can use the status information of the task nodes in the business process sent by the service terminal 110 and the configuration information corresponding to the task nodes pre-stored in the server, and/or use the service sent by the service terminal 110. The state information of the process and the configuration information corresponding to the business process pre-stored in the server, determine whether each task node and/or business process in the business process being executed in the service terminal 110 has a timeout fault, and monitor the fault. The results are stored in the database, and the faulty task node or faulty business process is reminded.

The server 120 can be, for example, an OLA server, which can be mainly used to manage and store the basic configuration data of SLA/OLA; receive status information reported by the OLA generated during the actual running of the business process instance, and the status information is, for example, of a task node. The start time and end time can also be responsible for calculating the final calculation result of SLA/OLA and storing it. And monitor the task nodes whose OLA has timed out, and remind the task nodes whose OLA has timed out. The server 120 and the service terminal 110 may be connected in a plug-in manner.

The server 120 may be a server, or a server cluster composed of several servers, or the server 120 may include one or more virtualization platforms, or the server 120 may be a cloud computing service center.

A communication connection is established between the service terminal 110 and the server 120 through a wired or wireless network. Optionally, the above-mentioned wireless network or wired network uses standard communication technologies and/or protocols. The network is usually the Internet, but can be any network, including but not limited to Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless network , private network, or any combination of virtual private networks.

For ease of understanding and description, the business process monitoring method, system, apparatus, device, and medium provided by the embodiments of the present application are described in detail below with reference to FIG. 2 to FIG. 10 .

An embodiment of the present application provides a business process monitoring method. The method is executed by a server. As shown in FIG. 2 , the method includes:

S201. Receive state information reported by each task node of a pre-created business process in the business process engine.

In the embodiment of the present application, the above-mentioned business process includes two or more task nodes. The status information includes at least the task start time or the task end time reported by each task node.

The business process engine is the underlying support platform for managing the business of the enterprise. It may include multiple modules, such as functional modules such as a process loading module, a process execution module, and a data synchronization module. The process loading module can load the configuration data into the cache of the service terminal; the process instance and the process configuration are stored in the cache. The process configuration includes process definition, and the process instance includes process status, process data, and the like. The user can call the process through the interface to execute the process instance in the cache. After the process instance is executed, it is persisted and stored in the persistence layer. Process monitoring can monitor process instances in the cache and process logs in the persistence layer.

Process definition refers to the process framework defined by business logic.

A business process refers to a business composition contained in a process definition, which can also be referred to as a business process instance. The monitoring of the operation of the business process instance can be evaluated by the SLA indicator (full name Service Level Agreement in English, service level agreement in Chinese). Process instance ends). Expected SLA values can be pre-configured to identify when the business process instance is expected to run to completion. The actual SLA value refers to the time it takes for the business process instance to actually run.

The task node refers to the tasks included in the business process. The monitoring of the completion of task nodes can be evaluated through OLA (English full name Operation Level Agreement, Chinese: Operation Level Agreement). OLA refers to the completion of the operation of any task node in a business process instance (that is, starting from the business process instance). The time from the start to the end of the business process instance). The expected OLA value can be pre-configured to identify the time when the business nodes included in the expected business process instance run to completion. The actual OLA value refers to the time used by the actual operation of the business nodes included in the business process instance.

The status information of the task node refers to the reported event status of the task node. The state information may include statistical key attributes of task nodes. Statistical key attributes can be characterized by time attributes, identification attributes, etc. corresponding to the reported event status. For example, the state information may include a process ID (ProcessDefinitionKey), a process instance ID (InstanceID), a task node ID (TaskKey), and a task node ID (TaskID).

Process ID, used to indicate the type of business process, belongs to the category of process definition. A process ID can start multiple process instances. The collection of multiple tasks is a process definition corresponding to a process ID

The process instance ID (namely, the business process identifier) is used to indicate a specific business process instance, which belongs to the category of the business process running process.

The task node identifier is used to indicate a certain task node in a certain type of process, which belongs to the category of process definition.

The task node ID is used to indicate the unique identifier of a task node in a specific actually running business process. The same task ID corresponds to different task IDs in different business processes.

In the embodiment of the present application, in order to monitor the execution process of the business process, two or three global listeners are configured in the process definition of the business process engine, and the monitoring scope of each global listener is all task nodes deployed in the business process. . According to the different monitoring content, configure the first global listener to monitor the start execution event reported by each task node; the second global listener to monitor the end execution event reported by each task node; the third global listener to monitor the business process End execution event.

During the execution of any business process, the business logic of the first global listener is to monitor the business state corresponding to the execution start event reported by each task node in the business process.

The task start time corresponding to the execution start event, the process ID, process instance ID, task node ID and task node ID of the business process can be obtained from the business state. The task start time (StartTime) refers to the start time when a task node in the business process starts to execute an event, which is reported by the process engine.

The business status can also include other statistical configuration attributes. For example, the unit body (ItemId) refers to the unit body object running under a task node in a specific process instance. For example, different device sets can be used to identify the unit body. The time used by different unit objects in the running of a certain task is mainly applicable to the scenario of batch processing of the process; the level (LevelId) refers to the urgency of running under a task node in the process instance;

The task time (ExecuteHours) refers to the time required for a task node to actually run in the business process. The time is calculated based on the task start time and the task end time through a pre-configured time algorithm in the server.

Whether the task is in time (IsInTime) is an identifier indicating whether the completion of a task node in the business process is within the allowable time limit.

The business logic of the second global listener is to monitor the business state corresponding to the end execution event reported by each task node in the business process.

The task end time corresponding to the end execution event can be obtained from the business state. The task end time (EndTime) refers to the end time of the end execution time of a task node in the business process, which is reported by the process engine. Other state information is the same as the description of the first global listener.

In the embodiment of the present application, each global listener is the logic configured on the business process engine, and each global listener has nothing to do with the specific business process logic, does not change the internal logic of the business process engine itself, and does not affect the business process The execution of the process and the functionality of the process engine.

When the service process is executed on the service terminal, the first global listener and the second global listener in the service process engine can monitor the status information of each task node in the service process. After the first global listener monitors the task node execution start event, it generates first state information, and sends the first state information to the server by calling a server interface, which may be, for example, a Record API interface. The server receives the task start time reported through the first global listener.

After the second global listener monitors the end execution event of the task node, second status information is generated, and the second status information is sent to the server by calling the server interface, and the server can receive the task end time reported by the second global listener. .

The server may store the first state information and the second state information in a first database, where the first database is used to store the state information of each service node of the service process sent by the service terminal, wherein the service process includes two Or more than two task nodes.

S202. Determine whether each task node has a timeout fault based on the state information of each task node and the node configuration information corresponding to each task node.

In the above steps, the node configuration information is pre-configured during the process definition of the business process engine. The node configuration information includes at least a task node time limit corresponding to each task node.

In this embodiment of the present application, the node configuration information refers to a business process and a set of attribute information of each task node included in the business process.

In the process of process definition, that is, when building a flowchart, the business process and the configuration data contained in the business process are written into the process definition. For example, BPMN2.0 process definition. When the server deploys the process definition, the process definition is parsed, and the process configuration information corresponding to the business process and the node configuration information corresponding to each business node can be obtained.

The process configuration information refers to the basic attribute parameters for configuring the business process instance. For example, SLAs configure key attributes. The key attributes of SLA configuration include process identification, SLA time limit (LimitedHours), SLA taking time limit algorithm (LimitedArithmetic), time calculation algorithm (Arithmetic), classification level (LevelId), etc. Among them, the SLA time limit refers to the maximum time allowed for a process instance from the beginning to the final end (ie, the time limit requirement). The SLA time limit algorithm is applicable to processes initiated at different times, and the allowed SLA time limit is different, that is, an algorithm can be used to dynamically determine the SLA time limit. The time calculation algorithm is to calculate the effective time consumed by the business process instance from the process start time to the process end time. Such as natural day time algorithm, working day time algorithm, etc. The classification level is used to indicate the urgency of a specific process instance. Under the same type of process, different process instances can define different classification levels, and different classification levels correspond to different SLA time limits (Limited Hours).

The node configuration information refers to the basic attribute parameters for configuring each task node in the business process. For example, OLA configures key attributes. The key attributes of the OLA configuration may include process identification (ProcessDefinitionKey), task identification (TaskKey), OLA time limit (LimitedHours), OLA time limit algorithm (LimitedArithmetic), time calculation algorithm (Arithmetic), classification level (LevelId) and so on. Among them, the OLA time limit refers to the maximum time allowed (ie time limit requirement) for a certain task node in a process instance from the start of operation (task start time) to the final end (task end time). The OLA time limit algorithm is suitable for processes initiated at different times, and the allowed OLA time limit is different, that is, the OLA time limit can be dynamically determined by a certain algorithm. The time calculation algorithm refers to calculating the effective time consumed by a task node in the process instance from the task start time to the task end time. Such as natural day time algorithm, working day time algorithm, etc. The classification level is used to indicate the urgency of a task node in a specific business process instance. Under the same type of process, different process instances can define different classification levels, and different classification levels correspond to different OAL time limits ( Limited Hours).

In order to realize the real-time monitoring of the execution process of the business process, in the design process of the business process, the BPMN2.0 core standard protocol of the business process design is not destroyed, and the standard protocol is extended to pre-configure each task node in the business process Multiple attribute information to generate the final business flow chart.

When the business process flow diagram is deployed on the business process engine of the service terminal, the business process engine can parse the extended BPMN2.0 protocol, obtain the attribute information of each task node in the business process, and generate a map corresponding to each task node. The node configuration information corresponding to each task node in the business process is sent to the server by using the service terminal.

When the business process engine deploys one or more business processes, the node configuration information corresponding to each task node in each business process can be obtained, and the node configuration information corresponding to each task node in the one or more business processes can be obtained. It is sent to the server, so that the server can store the multiple node configuration information of the one or more business processes in the configuration information database.

The process of generating node configuration information corresponding to each task node can be:

For each business process, read the process ID, process instance ID, task node ID of each task node in the business process, task node ID and task node attributes of the task node from the extended BPMN2.0 protocol information.

Optionally, the task node attribute information may include: a task node level representing the urgency of a certain task node, and a first time limit corresponding to the task node level, where the first time limit is the maximum allowed task node under the task node level. Long execution time, the first time limit algorithm for determining the first time limit and the first time algorithm for determining the actual time consuming of executing the task node. Wherein, the first time algorithm may be a natural day time algorithm or a working day time algorithm or the like. The first time limit algorithm may be a time configuration field or algorithm logic for determining the first time limit, and the time configuration field may be 2h or 3h, indicating that the first time limit is 2 hours or 3 hours. The algorithm logic for determining the first time limit may be determined based on actual needs, which is not limited in this embodiment of the present application. For example, the algorithm logic for determining the first time limit may be: for a certain task node, taking 15:00 pm every day as the time limit, when the server receives a start execution event for the task node at 9:00 am on a certain day The first state information of the task node is determined to be the first time limit of the task node in the execution process of the current day at 21:00; status information, it is determined that the first time limit of the task node in this execution process is 8:00 the next day.

In this step, based on the status information and the configuration information corresponding to the task node, the process of determining whether the task node has a timeout fault may be:

The server compares the received first state information and the first identifier in the second state information, and when the two first identifiers are consistent, determines that the first state information and the second state information are services corresponding to the first identifier Status information of the task node in the process, the first identification at least includes the process identification, process instance ID, task node identification and task node ID of the business process. The server uses the first identifier to search the configuration information database for the configuration information of the task node corresponding to the first identifier, reads the first time algorithm in the configuration information, and uses the first time algorithm to determine the start time and end time of the task node When the first time difference is greater than the first time limit in the configuration information, it is determined that the task node has a timeout fault, and the fault diagnosis result of the task node corresponding to the first identification is recorded, and the result can be is stored in the second database, where the second database is used to store the statistical data of the fault diagnosis results of the business process.

The first time difference is the actual execution time of the task node, and the timeout fault indicates that the actual execution time of the task node corresponding to the first identifier exceeds the longest allowed execution time of the task node, which proves that the task node is executing A failure occurred in the process. The fault diagnosis result usually includes the process ID of the business process, the ID of the process instance, the ID of the task node and the ID of the task node, the start time, the end time, the level of the process, the level of the task node, the first time difference, whether the task node has timed out, and/or Or the service terminal ID of the node that executes the task.

The business process monitoring method provided by the embodiment of the present application can receive the status information reported by all task nodes in the business process, and determine whether the task node has a timeout fault based on the status information reported by each task node and its corresponding node configuration information , so as to accurately determine the faulty task node, realize real-time monitoring of each task node in the business process, improve the accuracy of fault monitoring in the business process, and ensure accurate and efficient fault repair.

On the basis of the above embodiments, the embodiments of the present application further provide a business process monitoring method. The method is executed by a server. As shown in FIG. 3 , the method includes:

S301. Read and store node configuration information and process configuration information.

The node configuration information and the process configuration information are basic configuration data configured when the process definition is created based on the business process engine; and are obtained by parsing the process definition when the process definition is deployed.

In the above steps, the process configuration information includes at least the process node time limit corresponding to the business process. The process configuration information may also include: process identification, SLA time limit, SLA taking time limit algorithm, time calculation algorithm, and classification level. E.g,

The SLA time limit refers to the maximum time allowed for a process instance from the beginning to the final end (ie, the time limit requirement).

The SLA time limit algorithm is applicable to processes initiated at different times, and the allowed SLA time limit is different, that is, an algorithm can be used to dynamically determine the SLA time limit.

The time calculation method refers to calculating the effective time consumed by the process instance from the process start time to the process end time. Such as natural day time algorithm, working day time algorithm, etc.

The classification level is used to indicate the urgency of a specific process instance. Under the same type of process, different process instances can define different classification levels, and different classification levels correspond to different SLA time limits (Limited Hours).

In this step, the business terminal can respond to the deployment operation of the business process engine, parse the protocol of at least one business process in the business system, obtain the configuration information corresponding to each task node in each business process, and send it to the server, The server may receive configuration information corresponding to each task node in at least one business process, and store the configuration information in the configuration information database.

S302. Receive state information reported by each task node of a pre-created business process in the business process engine.

In the above steps, the business process includes at least two task nodes, and the status information includes at least the task start time and the task end time reported by each task node.

S303 , based on the state information of each task node and the node configuration information corresponding to each task node, determine whether each task node has a timeout fault.

In the above steps, the node configuration information is pre-configured during the process definition of the business process engine. The node configuration information includes at least a task node time limit corresponding to each task node.

It should be noted that, in this embodiment of the present application, for the processes of steps S302 to S303, reference may be made to steps S201 to S202 in the foregoing embodiment, which will not be repeated in this embodiment of the present application.

S304, the process start time corresponding to the business process reported by the first task node of the business process through the first listener of the business process engine;

S305: Receive the process end time corresponding to the business process reported by the last task node of the business process through the third listener of the business process engine.

In the above steps, the process of obtaining the process start time of the business process may be:

After receiving the status information of any task node in the currently executing business process sent by the service terminal, the server reads the service node identifier and process instance ID in the state information, and determines that there is no other reporting state information under the process instance ID. If the service node identifier is used, the service node that reports the status information is considered to be the start of the entire service process, and the SLA start time is recorded. Otherwise, it is considered that the business node reporting the status information is not the start of the entire business process, and only the start time of the task OLA is recorded.

It can be determined whether the task node is the first task node in the business process. For example, by: receiving the status information reported by any task node in the business process;

Obtain the business process ID and the current task node ID in the status information;

When it is determined that there is no other task node identification under the business process identification, indicating that the task node corresponding to the current task node identification is the first task node of the business process;

The task start time reported by the first task node is recorded as the process start time corresponding to the business process.

The method may also include:

The mapping relationship between the business node identifier of the business process, the process instance ID and the start time of the business process is stored.

Wherein, the process of judging whether the task node is the first task node in the business process may be:

Use the task node identifier and the business process identifier to find out whether there is state information corresponding to the business process identifier and the task node identifier in the first database, and if not, determine that the task node is the first task in the business process node, and the state information is the first state information; if it exists, use the business process identifier of the business process and the business node identifier to search for the mapping relationship to obtain the start time of the business process.

The process by which the server obtains the end time of the business process may include:

In the embodiment of the present application, a third global listener is configured in the business process engine, and the monitoring scope of the third global listener is all executable business processes deployed in the business system. During the execution of any business process, the business logic of the third global listener is:

Monitor and obtain the end execution event of the business process and the end time of the business process, and simultaneously obtain the business process identifier and the business node identifier, the end execution event identifier of the business process and the end time of the business process, as the third state information;

The third state information is sent to the server by calling the server interface.

When a business process is being executed on the business terminal, the third global listener in the business process engine can monitor the status information reported by each task node in the business process. After the third global listener monitors the end execution event of the business process, it generates third state information according to the content of the state information parsed from the reported state information, and sends the third state information to the server by calling the server interface. The third listener receives the end time of the business process reported by the business node.

Optionally, during the execution of the service process, the server may send a query request to the service terminal at preset time intervals, and the service terminal may respond to the query request and determine whether the currently executing service process in the service terminal is completed. If so, the third state information of the business process can be sent to the server.

S306 , based on the end time of the business process, the start time of the business process, and the process configuration information corresponding to the business process, determine whether a timeout failure occurs in the business process.

In this embodiment of the present application, the process attribute information can be pre-configured for the business process during the design process of the business process, and the process attribute of the business process in the expanded BPMN2.0 protocol can be parsed during the deployment process of the business process flow. information to generate process configuration information corresponding to the business process.

When deploying one or more business processes in the business process engine, obtain the process configuration information and node configuration information corresponding to each business process, and send the process configuration information and node configuration information corresponding to each business process to the server, So that the server can store the process configuration information and node configuration information of one or more business processes in the configuration information database.

The process of generating process configuration information corresponding to the business process may be:

For each business process, the process identification, process instance ID and business process attribute information of the business process are read from the extended BPMN2.0 protocol to form process configuration information corresponding to the business process.

Optionally, the business process attribute information may include: a process level indicating the urgency of a certain business process, and a second time limit corresponding to the process level, where the second time limit is the longest allowed execution of the business process under the process level. time, a second time limit algorithm for determining the second time limit and a second time algorithm for determining the actual time consuming when executing the business process. Wherein, the second time algorithm may be a natural day time algorithm or a working day time algorithm, etc.; the second time limit algorithm may be a time configuration field or an algorithm logic for determining the second time limit, and the algorithm logic may be determined based on actual needs. The application embodiment does not limit the thorn. For example, the algorithm logic for determining the second time limit may be: for a certain business process, taking 11:00 pm every day as the time limit, when the server receives the data at 8:00 o'clock in the morning on a certain day. When the first state information about the first task node of the business process is reached, it is determined that the second time limit of the business process in this execution process is 20:00 on the current day; when the server receives information about the The first state information of the first task node of the business process determines that the second time limit of the business process in this execution process is 9:00 the next day.

In this step, based on the process end time of the business process, the process start time of the business process, and the configuration information corresponding to the business process, the process of determining whether a timeout failure occurs in the business process may be:

The server can read the process identifier and the process instance ID from the received third state information as the second identifier, use the second identifier to search the configuration information database for the configuration information corresponding to the business process corresponding to the second identifier, and read the The second time algorithm in the configuration information, using the second time algorithm to determine the second time difference between the start time and the end time of the business process, when the second time difference is greater than the second time limit in the configuration information, determine the service When a timeout fault occurs in the process, the fault diagnosis result of the business process is recorded, and the result can be saved in the second database. Wherein, the second time difference is the actual duration of the business process, and the fault diagnosis result usually includes the process identifier of the business process, the process instance ID, the second start time, the end time, the process level, the second time difference, the business process Indicates whether the process has timed out and/or the ID of the business terminal that executes the business process.

Optionally, the server determines a certain task node in the business process, or after a timeout failure occurs in the business process, it can send reminder information to the business terminal, so that the business terminal can handle the task node or business process in time after receiving the reminder information. tasks, timely discover and prompt timeout faults during business process processing.

In this embodiment of the present application, during the design process of the business process, the execution order of two or more task nodes in the business process is pre-configured. For example, after task node 1 is completed, task node 2 is executed, and then other task nodes are executed in turn. After the entire task node is completed, a business process is completed.

The above embodiments provided in this application can monitor each task node in the business process in real time, and determine whether the task node is faulty based on the first state information and the second state information corresponding to each task node. In the related art, only the entire business process can be monitored, and the above method adopted in the embodiment of the present application can effectively monitor the execution of each task node in each business process, effectively improving the performance of the business process engine. Monitoring efficiency of running business processes.

In the above-mentioned embodiment provided in this application, processing resources can also be saved by multiplexing the first global listener. When the first global listener monitors the status information reported by the first task node of the business process, it can be based on The state information identifies the process start time of the business process. Compared with the paired configuration of the listeners in the related art, the embodiments provided by the present application can effectively improve the multiplexing efficiency of the listeners.

In addition, the above embodiments provided by the present application can also remind the faulty task node, which further improves the maintenance efficiency of the business process.

As shown in FIG. 4, FIG. 4 shows a schematic diagram of the deployment and monitoring process of the business process provided in the embodiment of the present application, including a business process deployment stage and a business process execution stage. The definition protocol requests to call the business process deployment interface provided by the process engine in the business terminal, deploy the business flow chart in the business system of the business terminal, and parse the node configuration information corresponding to the business node in the business flow chart and the business process Process configuration information corresponding to the process, and send the node configuration information and process configuration information to the server for storage.

In the business process execution stage, the first global listener configured in the business process engine can monitor the start execution event of each task node, generate first state information, and send the first state information to the server by calling the server interface.

The second global listener can monitor the end execution event of each task node, generate second state information, and send the second state information to the server by invoking the server interface.

The logical computing layer of the server determines whether the task node sending the first state information and the second state information has an execution timeout fault based on the received first state information and the second state information, and if so, stores the fault diagnosis result in the database . FIG. 4 shows the process of reporting status information, diagnosing overtime faults, and recording the diagnosis results for the task node 2 .

Further, the third global listener configured in the business process engine can monitor the end execution event of the business process, generate third state information, send the third state information to the server by calling the server interface, and use the fault in the task node. The start execution event of the business process identified during the diagnostic process.

The logical computing layer of the server determines the process start time of the business process based on the state information reported by the business node, then judges whether the business process has an execution timeout fault based on the process start time and the third state information, and stores the fault diagnosis result in the database.

The following is an example of the application of the enterprise management system in the order processing process environment. The order processing process may be different for different products. As shown in Figure 5, it is assumed that the order processing flow for product A includes four task nodes: receiving orders, checking user accounts, executing orders, and providing invoices.

In the business process design stage, for the design of the order processing process of product A, you can use the BPMN2.0 protocol standard to define the process ID B of the order processing process, define the task node ID of the receiving order task node as c, and define the user account check task node. The identifier of the task node is d, the identifier of the task node that defines the task node of executing orders is e, and the identifier of the task node that defines the task node of providing invoices is f.

Define the process instance ID of the order processing process of product A as B1, define the task node ID of the order receiving task node in the order processing process of product A as c1, define the task of the user account check task node in the order processing process of product A The node ID is d1, and the task node ID of the ordering task node that defines the raw material order task in the order processing flow of product A is e1, which defines the invoice task node that provides the raw material order task in the order processing flow of product A. The task node identification ID is f1.

Further, the attribute information of the order processing process of product A is set in the BPMN2.0 protocol standard, and the attribute information of the order processing process of product A may include: the process level of process instance B1 is L1, and the second time limit is 4 minutes, the second time algorithm is the natural time algorithm; the task node attribute information of each task node in the order processing flow of product A is set in the BPMN2.0 protocol standard, wherein the task node identifies the task node level of c1 is l3, the first time limit is 30 seconds, and the first time algorithm is the natural time algorithm; the task node level of the node identification d1 is l2, the first time limit is 50 seconds, and the first time algorithm is the natural time algorithm; the task node identification e1 The task node level is l1, the first time limit is 80 seconds, and the first time algorithm is the natural time algorithm; the task node level of the task node identification f1 is l6, the first time limit is 20 seconds, and the first time algorithm is the natural time algorithm. Among them, the level of the task node or the urgency of the business process decreases as the value increases. Similarly, order processing for other products can be designed in the same way. At the same time, the first global listener, the second global listener and the third global listener are preconfigured in the business process engine supporting the BPMN2.0 protocol standard.

In the deployment stage of the business process, the business process engine used to execute the enterprise management system can parse the attribute information of the order processing processes of multiple products in the extended BPMN2.0 protocol, and generate order processing processes corresponding to each product. The attribute information corresponding to each task node in the order processing process of each product is generated, and the service terminal sends the attribute information to the server, and the server can receive the configuration information and store it in the configuration information database. The process configuration information corresponding to the order processing process of product A includes: process identifier B, process instance B1, process level L1, second time limit of 4 minutes, and second time algorithm natural time algorithm.

The node configuration information corresponding to the order receiving task node in the order processing flow of product A includes: process ID B, process instance B1 and process level L1, node ID c, task node ID c1, task node level l3, first time limit 30 Seconds, the first time algorithm natural time algorithm.

The node configuration information corresponding to the user account check task node in the order processing process of product A includes: process identifier B, process instance B1 and process level L1, task node ID d1, task node level l2, first time limit 50 seconds, first Time Algorithm Natural Time Algorithm.

The node configuration information corresponding to the order execution task node in the order processing flow of product A includes: process ID B, process instance B1 and process level L1, task node ID e1, task node level is l1, first time limit is 80 seconds, first Time Algorithm Natural Time Algorithm.

The node configuration information corresponding to the invoice task node provided in the order processing process of product A includes: process ID B, process instance B1 and process level L1, task node ID f1, task node level is l6, the first time limit is 20 seconds, and the first time limit is 20 seconds. One Time Algorithm Natural Time Algorithm.

In the execution stage of the business process, it is assumed that the business terminal g1 receives the purchase request for product A and starts to execute the order processing process. The first global listener listens to the start execution event of the task node receiving the order, and obtains the process identifier B and process instance B1. , task node identification c and task node c1, start execution event identification h1 and start time at 16:20:10 on July 20, 2020, determine these information as the first state information r1 and send it to the server; the server receives the first After the state information r1, read the process identifier B and the process instance B1 in the first state information r1, search and compare in the first database according to the process identifier B and the process instance B1, and determine that the first database does not exist with the process identifier B. The state information corresponding to the process instance B1, then determine that the task node c1 is the first state information of the first task node in the process instance B1, and store the process identifier B, the process instance B1 and the start of the business process (process instance B1). The time is the mapping relationship between 16:20:10 on July 20, 2020.

The second global listener listens to the end execution event of the receiving order task node, and obtains the process ID B, process instance B1, task node ID c and task node c1, end execution event ID h2 and end time at 16:00 on July 20, 2020 At 20 minutes and 15 seconds, the information is determined as the second state information r2 and sent to the server.

Further, the server reads the process identifier B, the process instance B1, the task node identifier c and the task node c1 in the first state information r1 as the first identifier j1, and reads the process identifier B, the process instance in the second state information r2. B1. The task node identification c and the task node c1 are used as the first identification j2. Since the first identification j1 and the first identification j2 are equal, it can be determined that the first state information r1 and the second state information r2 are: products corresponding to the first identification In the order processing process of A, the status information of the order task node is received; and the start time at 16:20:10 on July 20, 2020 and the end time at 16:20:15 on July 20, 2020 are read from the status information , and use the first identification to find the configuration information of the task node corresponding to the first identification in the configuration information stored in the configuration information database as follows: task node level 13, first time limit 30 seconds, first time algorithm natural time algorithm, then Using the natural time algorithm to determine the first time difference between 16:20:15 on July 20, 2020 and 16:20:10 on July 20, 2020, the first time difference is 5 seconds, and the first time difference is less than 5 seconds The first time limit is 30 seconds. It is determined that the execution process of the task node receiving the order has not timed out, and the process ID B, process instance B1, task node ID c and task node c1, process level L1, task node level l3, start time July 2020 At 16:20:10 on the 20th, the end time is at 16:20:15 on July 20, 2020, the first time difference is 5 seconds, the task execution node is the non-timeout identifier o1 and/or the business terminal g1, and it is determined to be faulty The diagnosis results are stored in the second database.

The business terminal and the server can continue to process the order processing flow for product A in the same way to the providing invoice task node, and the third global listener monitors the end execution event of the providing invoice task node, and obtains the process identifier B, process instance B1, second End execution event identifier h3 and end time of the business process at 16:27:15 on July 20, 2020, determine the third state information from these information, and send the third state information to the server. After the server receives the third state information, it reads the process identifier B, the process instance B1 and the end time of the business process at 16:27:15 on July 20, 2020, and uses the process identifier B and the process instance B1 as the second identifier , and use the second identifier to search and determine the start time of the business process corresponding to the second identifier at 16:20:10 on July 20, 2020.

Next, according to the second identifier, the process configuration information corresponding to the business process is searched in the configuration information database, and the process level L1 corresponding to the order processing process of product A is read from the process configuration information, and the second time limit 4 minutes, second time algorithm natural time algorithm. Then, the second time difference between 16:27:15 on July 20, 2020 and 16:20:10 on July 20, 2020 is calculated as 7 minutes and 5 seconds, and the second time difference is 7 When 5 seconds is greater than the second time limit of 4 minutes, it is determined that the order processing process of product A has timed out.

Set the process ID B, process instance B1, process level L1, start time at 16:20:10 on July 20, 2020, end time at 16:27:15 on July 20, 2020, and the second time difference of 7 minutes In 5 seconds, the order processing process timeout flag O2 and/or the service terminal g1 is stored in the second database as the fault diagnosis result.

The business process monitoring method provided by the embodiment of the present application can receive the status information reported by the task node in the business process, and determine whether the task node has a timeout fault based on the status information and the node configuration information corresponding to the task node. In the embodiment of the present application, the faulty task node and/or business process can be accurately determined in the above-mentioned manner, so as to realize real-time monitoring of each task node in the business process processing process, timely discover the fault of the task node, and improve the monitoring of faults in the business process. The highest accuracy ensures accurate and efficient repair of faults.

And the embodiment of the present application can also obtain the process start time and process end time of the business process; based on the process end time of the business process, the process start time of the business process and the process configuration information corresponding to the business process, it is determined whether a timeout fault occurs in the business process .

In the embodiment of the present application, by accurately determining the faulty business process, the real-time monitoring of the business process is realized, the fault of the business process is detected in time, the accuracy of fault monitoring in the business process is improved, and the fault is repaired accurately and efficiently.

An embodiment of the present application provides a business process monitoring device. As shown in FIG. 6 , the device 40 includes:

The first receiving module 401 is configured to receive status information of task nodes in the business process. The business process includes at least two task nodes that receive the state information reported by each task node of the pre-created business process in the business process engine. The process includes at least two task nodes, and the status information includes at least the task start time and task end time reported by each task node;

The first determination module 402 is configured to determine whether each task node has a timeout fault based on the state information of each task node and the node configuration information corresponding to each task node, and the node configuration information is the process of the business process engine. Preconfigured at definition time.

The above-mentioned node configuration information at least includes a task node time limit corresponding to each task node.

Optionally, as shown in Figure 7, the device further includes:

The second receiving module 403 is configured to read and store the node configuration information and the process configuration information; the node configuration information and the process configuration information are basic configuration data configured when the process definition is created based on the business process engine; and when the process definition is deployed Obtained by parsing the process definition.

Optionally, the first receiving module 401 is configured to:

Receive the task start time reported by each business node through the first global listener of the business process engine;

The task end time reported by each business node through the second global listener of the business process engine is received.

Optionally, the first determining module 402 is configured to:

Determine the first time difference value corresponding to each task node based on the task start time and the task end time;

When the first time difference value is greater than the time limit of the task node corresponding to the first time difference value, it is determined that the task node corresponding to the first time difference value has a timeout fault.

Optionally, as shown in Figure 8, the device further includes:

The reading module 404 is configured to receive the process start time corresponding to the business process reported by the first task node of the business process through the first listener of the business process engine; The process end time corresponding to the business process reported by the three listeners;

The second determining module 405 is configured to determine whether a timeout failure occurs in the business process based on the process start time, process end time and process configuration information corresponding to the business process. The process configuration information at least includes the process node time limit corresponding to the business process.

Optionally, the status information further includes the task node identifier, then the acquisition module 404 is configured as:

Receive the status information reported by any task node in the business process;

Obtain the business process ID and the current task node ID in the status information;

When it is determined that there is no other task node identification under the business process identification, indicating that the task node corresponding to the current task node identification is the first task node of the business process;

The task start time reported by the first task node is recorded as the process start time corresponding to the business process.

Optionally, as shown in Figure 9, the device further includes:

The sending module 406 sends prompt information to the service terminal when it is determined that the task node has a timeout failure, or when it is determined that the service process has a timeout failure.

To sum up, the business process monitoring device provided by the embodiment of the present application determines whether a task node has a timeout fault based on the received status information reported by a task node, so as to accurately determine the faulty task node and realize the process of processing the business process. Each task node in the system is monitored in real time to improve the accuracy of fault monitoring in the business processing process and ensure accurate and efficient fault repair.

An embodiment of the present application provides a business process monitoring system. As shown in FIG. 1 , the system includes: a business terminal 110 and a server 120 .

The business terminal 110 includes a business process engine running on it, and is used to report the status information of each task node of the business process pre-created in the business process engine to the server, and the business process includes at least two task nodes, and the status information At least include the task start time and task end time reported by each task node;

The server 120 is configured to receive status information from the service terminal, and based on the status information of each task node and the node configuration information corresponding to each task node, determine whether each task node has a time-out fault, and the node configuration information is in the service The process engine's process definition is pre-configured.

The node configuration information includes at least a task node time limit corresponding to each task node.

Optionally, the server 110 is further configured to read and store node configuration information and process configuration information; the node configuration information and process configuration information are basic configuration data configured when creating a process definition based on the business process engine; and when deploying It is obtained by parsing the process definition when the process is defined.

Optionally, the status information may include the start time and end time of the task node, then the server 110 is further configured to receive the task start time reported by each business node through the first global listener of the business process engine;

Receive the task end time reported by each business node through the second global listener of the business process engine;

Determine the first time difference value corresponding to each task node based on the task start time and the task end time;

When the first time difference value is greater than the time limit of the task node corresponding to the first time difference value, it is determined that the task node corresponding to the first time difference value has a timeout fault.

Optionally, the server 120 is further configured to receive the process start time corresponding to the business process reported by the first task node of the business process through the first listener of the business process engine;

receiving the process end time corresponding to the business process reported by the last task node of the business process through the third listener of the business process engine;

Based on the process start time, the process end time and the process configuration information corresponding to the business process, it is determined whether a timeout failure occurs in the business process, and the process configuration information at least includes the process node time limit corresponding to the business process.

Optionally, the state information further includes a task node identifier, and the server 110 is further configured to: receive the state information reported by any task node in the business process; obtain the business process identifier and the current task node identifier in the state information; When it is determined that there are no other task node identifiers under the business process identifier, indicate that the task node corresponding to the current task node identifier is the first task node of the business process; record the task start time reported by the first task node as the process start corresponding to the business process time.

Optionally, the server 120 is further configured to send prompt information to the service terminal 110 when it is determined that the task node has a timeout failure, or when it is determined that the service process has a timeout failure.

To sum up, the monitoring system for the business process provided by the embodiment of the present application can determine whether a task node has a timeout failure based on the status information reported by the business node configured in the business terminal, and can accurately determine the failed task node. Each task node in the business process is monitored in real time to improve the accuracy of fault monitoring in the business process and ensure accurate and efficient fault repair.

Referring to FIG. 10 below, FIG. 10 is a schematic structural diagram of a computer system of a server according to an embodiment of the present application.

As shown in FIG. 10 , the computer system includes a central processing unit (CPU) 501 which can be processed according to a program stored in a read only memory (ROM) 502 or a program loaded from a storage section 503 into a random access memory (RAM) 503 Various appropriate actions and processes are performed. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501 , the ROM 502 , and the RAM 503 are connected to each other through a bus 504 . An input/output (I/O) interface 505 is also connected to bus 504 .

The following components are connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc. ; and a communication section 509 including a network interface card such as a LAN card, a modem, and the like. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I/O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program carried on a machine-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 503 and/or installed from the removable medium 511 . When the computer program is executed by the central processing unit (CPU) 501, the above-described functions defined in the system of the present application are executed.

It should be noted that the computer-readable medium shown in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In this application, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more functions for implementing the specified logical function(s) executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

The units or modules involved in the embodiments of the present application may be implemented in a software manner, and may also be implemented in a hardware manner. The described unit or module may also be provided in the processor, for example, it may be described as: a processor including: a first receiving module and a first determining module. Wherein, the names of these units or modules do not constitute a limitation on the units or modules themselves under certain circumstances. For example, the first receiving module may also be described as "a device for receiving pre-created business processes in the business process engine. The module of status information reported by each task node".

As another aspect, the present application also provides a computer-readable storage medium. The computer-readable storage medium may be included in the electronic device described in the above-mentioned embodiments; in electronic equipment. The aforementioned computer-readable storage medium stores one or more programs, and when the aforementioned programs are used by one or more processors to execute the business process monitoring method described in this application.

The above description is only a preferred embodiment of the present application and an illustration of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to the technical solution formed by the specific combination of the above-mentioned technical features, and should also cover the above-mentioned technical features without departing from the inventive concept. Other technical solutions formed by any combination of its equivalent features. For example, a technical solution is formed by replacing the above-mentioned features with the technical features disclosed in this application (but not limited to) with similar functions.

Claims (11)

1. A business process monitoring method, performed by a server associated with a business process engine, the method comprising:

receiving state information reported by each task node of a pre-created business process in a business process engine, wherein the business process comprises at least two task nodes, and the state information at least comprises task starting time and task ending time reported by each task node;

and determining whether each task node has overtime faults or not based on the state information of each task node and node configuration information corresponding to each task node, wherein the node configuration information is configured in advance when the process of the business process engine is defined.

2. The business process monitoring method according to claim 1, wherein the business process engine includes a first global listener and a second global listener configured in advance, and the receiving of the status information reported by each task node of the business process created in advance in the business process engine includes:

receiving the task start time reported by each service node through a first global listener of the service process engine;

and receiving the task ending time reported by each service node through a second global listener of the service process engine.

3. The business process monitoring method of claim 2, wherein said determining whether said task node has failed comprises:

determining a first time difference value corresponding to each task node based on the task start time and the task end time;

and when the first time difference value is greater than the task node time limit corresponding to the first time difference value, determining that the task node corresponding to the first time difference value has an overtime fault.

4. The business process monitoring method of any one of claims 1-3, wherein the business process engine further comprises a third preconfigured global listener, the method comprising:

receiving a process starting time corresponding to the business process reported by a first task node of the business process through a first listener of the business process engine;

receiving a process end time corresponding to the business process reported by a last task node of the business process through a third listener of the business process engine;

and determining whether the business process has overtime faults or not based on the process starting time, the process ending time and process configuration information corresponding to the business process, wherein the process configuration information at least comprises process node time limit corresponding to the business process.

5. The business process monitoring method according to claim 4, wherein the status information further includes task node identifiers, and if the first task node that receives the business process reports the process start time corresponding to the business process through the first global listener of the business process engine, the method includes:

receiving reported state information of any task node in the business process;

acquiring a service flow identifier and a current task node identifier in the state information;

when determining that no other task node identifier exists under the service process identifier, indicating the task node corresponding to the current task node identifier as a first task node of the service process;

and recording the task starting time reported by the first task node as the process starting time corresponding to the service process.

6. The business process monitoring method according to claim 1, wherein before receiving the status information reported by each task node of the business process pre-created in the business process engine, the method further comprises:

reading and storing the node configuration information and the process configuration information; the node configuration information and the process configuration information are basic configuration data configured when a process definition is created based on the business process engine; and the flow definition is analyzed when the flow definition is deployed.

7. The business process monitoring method of claim 4, further comprising:

and when determining that the task node has overtime fault or when determining that the business process has overtime fault, sending prompt information.

8. A business process monitoring apparatus configured on a server associated with a business process engine, the apparatus comprising:

the first receiving module is configured to receive state information reported by each task node of a pre-created business process in a business process engine, wherein the business process comprises at least two task nodes, and the state information at least comprises task starting time and task ending time reported by each task node;

a first determining module configured to determine whether each task node has a timeout fault based on the state information of each task node and node configuration information corresponding to each task node, where the node configuration information is pre-configured when a process of the business process engine is defined.

9. A service process monitoring system is characterized in that the system comprises a service terminal and a server, and the system comprises:

the service terminal comprises a service process engine running on the service terminal and is configured to report state information of each task node of a service process pre-established in the service process engine to a server, wherein the service process comprises at least two task nodes, and the state information at least comprises task starting time and task ending time reported by each task node;

the server is configured to receive the state information from the service terminal, and determine whether each task node has a timeout fault based on the state information of each task node and node configuration information corresponding to each task node, where the node configuration information is configured in advance when a process of the service process engine is defined.

10. A computer device, characterized in that the computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, the processor being adapted to implement the method according to any of claims 1-7 when executing the program.

11. A computer-readable storage medium, characterized in that a computer program is stored thereon for implementing the method according to any one of claims 1-7.

Images