CN112200505B - Cross-business system process monitoring device and method, corresponding equipment and storage medium - Google Patents
Cross-business system process monitoring device and method, corresponding equipment and storage medium Download PDFInfo
- Publication number
- CN112200505B CN112200505B CN202011400740.6A CN202011400740A CN112200505B CN 112200505 B CN112200505 B CN 112200505B CN 202011400740 A CN202011400740 A CN 202011400740A CN 112200505 B CN112200505 B CN 112200505B
- Authority
- CN
- China
- Prior art keywords
- message
- service
- service system
- waiting node
- workflow engine
- 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
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- 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
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Software Systems (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a process monitoring device and method for cross-service system, corresponding equipment and storage medium, wherein the device comprises: a message queue for managing message exchanges between the workflow engine and the business system; the first access module is used for accessing the service system to the message queue; the second access module is used for accessing the workflow engine to the message queue; and the waiting node generation module is used for generating a corresponding waiting node for each service system in the workflow engine, wherein each waiting node is used for identifying that the execution result of the corresponding service system needs to be waited in the process of running the process example, and each waiting node is identified as executed according to the message exchange activation with the corresponding service system and in response to the reception of the first service step completion message, so that the process of the process example is continuously advanced. The invention can simply and quickly realize the process monitoring of the cross-service system.
Description
Technical Field
The present application relates to the field of electrical digital data processing, and in particular, to a process monitoring apparatus and method for a cross-business system, and a corresponding device and storage medium.
Background
The workflow is a business process which can be executed by user participation or automatically, and is abstract, summary and description of business processes and business rules among operation steps of the business processes. Workflow systems, i.e. the logic and rules that organize how the work in a workflow is up and down, are represented in a computer in a suitable model and run. Workflow runs are typically done by a workflow engine.
With the increase of complexity of application systems, one business process often needs to span multiple external business systems to be completed. The service system often includes a monitoring module therein to monitor the operation data in the system. But the business process spanning multiple business systems cannot be uniformly monitored and have a full appearance. In order to realize comprehensive and efficient monitoring of the business process, a plurality of business systems need to be spanned, the data of the whole business call chain is tracked, the comprehensive analysis and the early warning are carried out in time, and the online problems of all the business systems are positioned efficiently and accurately.
The cross-system service process monitoring can be completed only by integrating a plurality of service systems. However, the implementation technologies and languages of different business systems are often different, which increases the complexity and difficulty of implementing integration.
Disclosure of Invention
In order to overcome the defects in the prior art, the invention provides a cross-business system flow monitoring device and method, corresponding equipment and a storage medium, which can simply and quickly realize cross-business system flow monitoring.
In a first aspect of the present invention, there is provided a process monitoring apparatus across a service system, the apparatus comprising:
a message queue for managing message exchanges between the workflow engine and the business system;
the first access module is used for accessing a service system into the message queue so as to exchange messages between the service system and the message queue, wherein the service system at least comprises a first service system and a second service system;
the second access module is used for accessing the workflow engine to the message queue so as to exchange messages between the workflow engine and the message queue;
and the waiting node generation module is used for generating a corresponding waiting node for each service system in the workflow engine, wherein each waiting node is used for identifying that the execution result of the corresponding service system needs to be waited in the process of running the process example, and each waiting node is identified as executed according to the message exchange activation with the corresponding service system and in response to the reception of the first service step completion message, so that the process of the process example is continuously advanced.
In an embodiment, each waiting node remains in a running state after it has executed.
In an embodiment, the apparatus further includes a recording module, configured to record and count a subsequent service step completion message received by a waiting node after the waiting node receives a first service step completion message; and the warning module is used for sending out a warning message when the count of the business step completion message received by a waiting node exceeds a preset threshold value.
In an embodiment, the apparatus further includes a display module configured to display a result of the running of the process instance in response to all the waiting nodes having been identified as executed.
In an embodiment, the apparatus further includes a notification module, configured to send an exception event notification in response to a failure of the parsed service execution result.
In a second aspect of the present invention, a method for monitoring a process across business systems is provided, including:
providing a message queue for managing message exchanges between the workflow engine and the business system;
accessing a service system to the message queue, and enabling messages to be exchanged between the service system and the message queue, wherein the service system at least comprises a first service system and a second service system;
accessing a workflow engine to the message queue, enabling messages to be exchanged between the workflow engine and the message queue;
and generating a corresponding waiting node for each service system in the workflow engine, wherein each waiting node is used for identifying that the execution result of the corresponding service system needs to be waited in the process of running the process instance, and each waiting node is activated according to the message exchange with the corresponding service system and identified as being executed in response to receiving the first service step completion message, so that the process of the process instance is continuously advanced.
In a third aspect of the invention, a computer device is provided, comprising a processor, a memory and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program realizes the steps of the method according to the second aspect of the invention.
According to a fourth aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method according to the second aspect of the present invention. On the premise, the monitoring of cross-system business processes is realized and early warning capability is provided.
According to the invention, based on the workflow engine, on the premise of not influencing the internal processing logic of the existing service system, the message queue is integrated, and the data reception of the service flow of the cross-service system is realized by waiting for the node to receive the message. The invention fully utilizes the characteristics of the message queue and the flexible definition of the existing workflow engine, the message queue plays a decoupling role, so that the external business system does not directly depend on the workflow engine, the external business system and the workflow engine can be realized by using respective technologies without generating mutual dependence, and the business system can achieve the effect of quickly implementing business process monitoring only by changing the sending and receiving messages.
In addition, the waiting node can repeatedly receive the message data of the service system for a plurality of times to collect and monitor the data. And by utilizing the reminding function of the workflow engine, when the monitoring data is abnormal or reaches a threshold value, an early warning message is sent to appointed personnel for reminding.
Other features and advantages of the present invention will become more apparent from the detailed description of the embodiments of the present invention when taken in conjunction with the accompanying drawings.
Drawings
FIG. 1 is a schematic diagram of an embodiment of an apparatus according to the present invention;
FIG. 2 is a first example of an application of the process monitoring apparatus shown in FIG. 1;
FIG. 3 is a second example of an application of the process monitoring apparatus shown in FIG. 1;
fig. 4 is a flow chart of an embodiment of a method according to the present invention.
For the sake of clarity, the figures are schematic and simplified drawings, which only show details which are necessary for understanding the invention and other details are omitted.
Detailed Description
Embodiments and examples of the present invention will be described in detail below with reference to the accompanying drawings.
The scope of applicability of the present invention will become apparent from the detailed description given hereinafter. It should be understood, however, that the detailed description and the specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only.
Fig. 1 is a schematic structural diagram of a preferred embodiment of a process monitoring apparatus for a cross-business system according to the present invention, the process monitoring apparatus comprising:
and the message queue 102 is used for managing message exchange between the workflow engine and the business system. The number of service systems varies depending on the application, but there are at least two, and two are used as an example here.
A first access module 104, configured to access two service systems, such as an a system and a B system, to a message queue, thereby enabling messages to be exchanged between the service systems and the message queue. The system a is a system whose processing is advanced in the flow, and is also referred to as a first system. The B system is a system whose processing follows the a system in the flow, and is also referred to as a second system.
A second access module 106, configured to access the workflow engine to the message queue through the message broker, thereby enabling messages to be exchanged between the workflow engine and the message queue. Different message queues have different connection modes and message sending modes, the message agent is adapted to various message queues and performs analysis, serialization and deserialization operations of message contents, and the message agent also enables the workflow engine not to be concerned about whether the message comes from an external message queue or is generated by an internal operation instruction.
And a waiting node generating module 108, configured to generate a corresponding waiting node for each service system in the workflow engine, where each waiting node is configured to identify that an execution result of the corresponding service system needs to be waited during a process of running the process instance, and where each waiting node is identified as being executed according to message exchange activation with the corresponding service system and in response to receiving a first service step completion message, so that the process of the process instance continues to be advanced. The data structure of the manual tasks in the workflow engine is fixed and is determined by the workflow engine. After a task is generated by the workflow engine, the task is generally distributed to designated personnel for processing, and a task processor calls a task completion interface of the workflow engine to mark that the task is completed. In the invention, the workflow engine realizes the generation of the waiting node and the completion of the definition content of the waiting node through processing logic different from other tasks. The waiting node task is to wait for a specific message, which consists of a message type identifier and a message content, which are determined before the flow definition. The message may come from outside or from inside the system. And the process instance runs to the waiting node, the task to be handled is not generated, the process instance is temporarily suspended (the instance data is saved), and the process instance is activated (the instance data is read again) after a specific message (comprising the process instance id and the message type) is received. The message type of each waiting node within a flow definition is not allowed to be the same.
In an embodiment, each waiting node remains in a running state after having executed, so that historical data collection and accumulation can be performed by repeatedly receiving messages for multiple times. In this case, the apparatus of the present invention may further include a recording module, configured to record and count a subsequent service step completion message received by a waiting node after the waiting node receives the first service step completion message. And when the service step completion message of the current instance and the waiting node is subsequently received, data accumulation and recording are carried out. In an embodiment, the apparatus of the present invention may further include an alert module, configured to send an alert message to a specified person by using a notification mechanism such as a short message and a mail of a workflow engine when a count of service step completion messages received by a waiting node exceeds a predetermined threshold, so as to implement service flow monitoring and early warning.
Fig. 2 shows a first application example of the process monitoring apparatus shown in fig. 1, wherein a business system includes a system a and a system B, and there is a relationship between the system a and the system B. The related data refers to data of the system A, and the system B can be directly used without data conversion. For example: the department files or manufacturer files of the two systems are coded in the same way, and can be directly used without data conversion. If the two service system nodes are not directly associated with each other, an automatic service node needs to be added between the two service system nodes, and a corresponding service method is called to perform data conversion, for example, the department code of the system A is converted into the department code of the system B. Whether the relation exists or not is determined according to the actual conditions of different service systems in the flow definition, and whether the nodes are added to carry out data conversion processing or not is determined. In other words, in the flow definition, there is a data conversion node between the a system and the B system, and the two are related. When a service flow starts, an external a system that starts a service sends a flow initiation message to a message queue, where the flow initiation message carries key data that identifies the service, and the key data is a piece of service data that identifies a certain service with a unique identifier, for example: service type code + document primary key (database primary key). The workflow engine receives the process initiating message, generates a process instance according to the process definition, generates a globally unique process instance id and key data corresponding to the business, records the process variable, and sends a process initiating result message to the message queue, wherein the process initiating result message comprises the process instance id. The process instance is executed according to the process definition, enters a first waiting node, the workflow engine stores the running state of the instance to a persistent storage (database), the process instance enters a waiting state, and the process instance is executed continuously after waiting for the arrival of the specified type of message (service step completion message) containing the instance id. And after receiving the process initiation result message, the system A records the process instance id for subsequent processing, and when the processing is completed, sends a service step completion message corresponding to the first waiting node to the message queue, wherein the service step completion message comprises a message type id, the process instance id and other service execution result information (service data of the instance). After receiving the service step completion message, the workflow engine finds a waiting node corresponding to the process instance according to the message type id and the process instance id, analyzes the service execution result in the message according to the message format of the waiting node waiting, finds a corresponding process instance according to the process instance id, reads instance data, wakes up the process instance, records a corresponding process instance variable, identifies that the service execution corresponding to the current waiting node is completed, continues to execute downwards according to the definition, enters the next waiting node, and enters the next stage of the service flow.
In the execution process of a business process instance, a business phase may be repeatedly executed for multiple times, and a message containing the same process instance id and different business execution result information may be sent for multiple times. And when receiving a first service step completion message of the waiting node, the workflow engine identifies that the waiting node is completed and pushes the instance to enter the next stage. After the waiting node is completed, the instance receives the service step completion message of the waiting node again, and records the message in the database as historical accumulated data of the waiting node, and accumulates the quantity according to a predefined rule.
Fig. 3 shows a second application example of the process monitoring apparatus shown in fig. 1, wherein the business system includes a system a and a system B, and there is no association between the system a and the system B. The flow initiation and execution of the a-system is similar to the application example of fig. 2. However, when the process execution reaches the waiting node of the system A, the process execution message is sent to a preset external service system, namely the system B, through the message queue, the service step execution message can contain key data and process instance id required by the system B, the system B is informed of starting to execute specific services, then, the process state is stored to persistent storage, and the process instance enters the waiting state and is not operated any more temporarily. And after receiving the service step execution message, the system B starts service logic execution according to the key data in the message body until the system B finishes service processing, and sends a service step completion message to the message queue to indicate that the service processing is finished, wherein the message carries the process instance id and the service execution result. And the workflow engine receives a service step completion message sent by the system B, analyzes a process instance id and a service execution result in the message, finds a corresponding process instance according to the process instance id, reads instance data, awakens the process instance, records a process instance variable of the corresponding process instance, identifies that the service execution corresponding to the current waiting node is completed, continues to execute downwards according to the process definition, and enters the next stage.
In an embodiment, the apparatus of the present invention further includes a notification module, configured to send an abnormal event notification to a designated person by using a notification mechanism such as a short message and a mail of the workflow engine in response to a failure of the analyzed service execution result. For example, system a is an approval system, initiating a business trip application; the B system is a budget system. And the estimated amount exists in the business trip request form, and after the system A passes the system A, the budget amount of the project needs to be preempted in the system B. If the project monthly budget balance is not sufficient, execution of budget amount preemption fails, which means that the service execution results fail. And if the service execution result is successful, the service flow continues to be carried out downwards. Of course, a manual task may also be introduced to perform manual intervention, additional processing is performed, a service step completion message including a successful result is sent again after the processing is completed, and the workflow engine identifies the service flow after receiving the message, and continues to advance to the next step.
In an embodiment, the inventive device further comprises a display module. After the last waiting node receives the service step completion message, the process points to the end node, marking the end of the process instance. The display module achieves the visual target of the business process monitoring by utilizing the process instance viewing interface of the workflow engine, can display the operation stage of the business process instance, displays the content of the process variable and achieves the effect of monitoring the process index.
The embodiment utilizes the workflow engine and the message queue, takes the workflow instance as the monitoring entity, integrates all the business systems by the message queue, takes the message as the process drive and collects data, shows the running state of the business process by the graphical interface of the running state of the workflow engine instance, monitors and warns by combining the notification capability provided by the workflow engine, and quickly, simply and flexibly monitors the business process.
FIG. 4 is a flow chart of a preferred embodiment of a cross-business system flow monitoring method according to the present invention, the method comprising:
in step S402, providing a message queue for managing message exchange between the workflow engine and the business system;
in step S404, accessing a service system to the message queue, enabling to exchange messages between the service system and the message queue, where the service system at least includes a first service system and a second service system;
in step S406, accessing a workflow engine to the message queue, enabling messages to be exchanged between the workflow engine and the message queue;
in step S408, a corresponding waiting node is generated in the workflow engine for each service system, wherein each waiting node is used to identify that the execution result of the corresponding service system needs to be waited during the process of running the process instance, and wherein each waiting node is activated according to the message exchange with the corresponding service system and identified as executed in response to receiving the first service step completion message, so that the process of the process instance continues to be advanced.
In another embodiment, the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method embodiment shown and described in conjunction with fig. 4 or other corresponding method embodiments, which are not described herein again.
In another embodiment, the present invention provides a computer device, which includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the processor implements the steps of the method embodiment shown and described in conjunction with fig. 4 or other corresponding method embodiments when executing the computer program, and details are not repeated herein.
The various embodiments described herein, or certain features, structures, or characteristics thereof, may be combined as suitable in one or more embodiments of the invention. Additionally, in some cases, the order of steps depicted in the flowcharts and/or in the pipelined process may be modified, as appropriate, and need not be performed exactly in the order depicted. In addition, various aspects of the invention may be implemented using software, hardware, firmware, or a combination thereof, and/or other computer implemented modules or devices that perform the described functions. Software implementations of the present invention may include executable code stored in a computer readable medium and executed by one or more processors. The computer-readable medium may include a computer hard drive, ROM, RAM, flash memory, portable computer storage media such as CD-ROM, DVD-ROM, flash drives, and/or other devices with a Universal Serial Bus (USB) interface, and/or any other suitable tangible or non-transitory computer-readable medium or computer memory on which executable code may be stored and executed by a processor. The present invention may be used in conjunction with any suitable operating system.
As used herein, the singular forms "a", "an" and "the" include plural references (i.e., have the meaning "at least one"), unless the context clearly dictates otherwise. It will be further understood that the terms "has," "includes" and/or "including," when used in this specification, specify the presence of stated features, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof. The term "and/or" as used herein includes any and all combinations of one or more of the associated listed items.
The foregoing describes some preferred embodiments of the present invention, but it should be emphasized that the invention is not limited to these embodiments, but can be implemented in other ways within the scope of the inventive subject matter. Various modifications and alterations of this invention will become apparent to those skilled in the art without departing from the spirit and scope of this invention.
Claims (9)
1. A process monitoring apparatus across business systems, the apparatus comprising:
a message queue for managing message exchanges between the workflow engine and the business system;
the first access module is used for accessing a service system into the message queue so as to exchange messages between the service system and the message queue, wherein the service system at least comprises a first service system and a second service system;
the second access module is used for accessing the workflow engine to the message queue so as to exchange messages between the workflow engine and the message queue;
a waiting node generating module, configured to generate a corresponding waiting node for each service system in the workflow engine, where each waiting node is used to identify that an execution result of the corresponding service system needs to be waited in a process of running a process instance, and where each waiting node is identified as executed according to message exchange activation with the corresponding service system and in response to receiving a first service step completion message, so that a process of the process instance continues to be advanced; wherein each waiting node remains in a running state after having been executed;
and the recording module is used for recording and counting the subsequent service step completion messages received by the waiting node after the waiting node receives the first service step completion message.
2. The process monitoring device of claim 1, further comprising:
and the warning module is used for sending out a warning message when the count of the business step completion message received by a waiting node exceeds a preset threshold value.
3. The process monitoring device of claim 1, further comprising:
and the display module is used for responding to the fact that all the waiting nodes are identified as executed, and displaying the operation result of the flow instance.
4. The process monitoring device of claim 1, wherein the message exchange comprises:
responding to the starting of the business process of the first business system, and sending a process starting message to the message queue by the first business system;
the workflow engine responds to the received process initiating message to generate a process instance, sends a process initiating result message to the message queue and executes the process instance;
the first service system responds to the received process initiation result message and responds to the completion of processing, and sends a service step completion message corresponding to the corresponding waiting node to the message queue;
and the workflow engine responds to the received service step completion message, analyzes a service execution result in the message, wakes up the process instance, marks that the service execution corresponding to the current waiting node is completed, and executes the process instance downwards.
5. The process monitoring device of claim 1, wherein the message exchange comprises:
responding to the starting of the business process of the first business system, and sending a process starting message to the message queue by the first business system;
the workflow engine responds to the received process initiating message to generate a process instance, sends a process initiating result message to the message queue and executes the process instance;
the first service system responds to the received process initiation result message and responds to the completion of processing, and sends a first service step completion message corresponding to the first waiting node to the message queue;
the workflow engine responds to the received first service step completion message, identifies that the service execution corresponding to the first waiting node is completed, and sends a service step execution message to the second service system through the message queue;
the second service system responds to the received service step execution message to start service logic execution and responds to the completion of service processing to send a second service step completion message to the message queue;
and the workflow engine responds to the received second service step completion message, analyzes the service execution result in the message, wakes up the process instance, identifies that the service execution corresponding to the second waiting node is completed, and executes the process instance downwards.
6. The process monitoring device according to claim 4 or 5, wherein the device further comprises:
and the notification module is used for responding to the failure of the analyzed service execution result and sending out an abnormal event notification.
7. A method for monitoring a process across business systems, the method comprising:
providing a message queue for managing message exchanges between the workflow engine and the business system;
accessing a service system to the message queue, and enabling messages to be exchanged between the service system and the message queue, wherein the service system at least comprises a first service system and a second service system;
accessing a workflow engine to the message queue, enabling messages to be exchanged between the workflow engine and the message queue;
generating a corresponding waiting node for each service system in the workflow engine, wherein each waiting node is used for identifying that the execution result of the corresponding service system needs to be waited in the process of running the process instance, and each waiting node is activated according to the message exchange with the corresponding service system and identified as being executed in response to receiving a first service step completion message, so that the process of the process instance is continuously advanced; wherein each waiting node remains in a running state after having been executed;
and recording and counting subsequent service step completion messages received by the waiting node after the waiting node receives the first service step completion message.
8. A computer device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, wherein the steps of the method according to claim 7 are implemented when the processor executes the computer program.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method as claimed in claim 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011400740.6A CN112200505B (en) | 2020-12-04 | 2020-12-04 | Cross-business system process monitoring device and method, corresponding equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011400740.6A CN112200505B (en) | 2020-12-04 | 2020-12-04 | Cross-business system process monitoring device and method, corresponding equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112200505A CN112200505A (en) | 2021-01-08 |
| CN112200505B true CN112200505B (en) | 2022-02-08 |
Family
ID=74033820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011400740.6A Active CN112200505B (en) | 2020-12-04 | 2020-12-04 | Cross-business system process monitoring device and method, corresponding equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112200505B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117667362B (en) * | 2024-01-31 | 2024-04-30 | 上海朋熙半导体有限公司 | Method, system, equipment and readable medium for scheduling process engine |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114051055B (en) * | 2022-01-12 | 2022-05-13 | 江苏银承网络科技股份有限公司 | Data transmission method and device in different systems |
| CN114444136B (en) * | 2022-02-08 | 2024-08-30 | 上海富数科技有限公司 | Method and system for decoupling computing engine and platform |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3474162A1 (en) * | 2016-06-20 | 2019-04-24 | Alibaba Group Holding Limited Fourth Floor, One Capital Place | Streaming data distributed processing method and device |
| CN111061550A (en) * | 2019-12-03 | 2020-04-24 | 北京每日优鲜电子商务有限公司 | Task processing method, device, equipment and storage medium |
| CN111092933A (en) * | 2019-11-20 | 2020-05-01 | 泰康保险集团股份有限公司 | Business process management method, system, medium and electronic device for micro-service architecture |
-
2020
- 2020-12-04 CN CN202011400740.6A patent/CN112200505B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3474162A1 (en) * | 2016-06-20 | 2019-04-24 | Alibaba Group Holding Limited Fourth Floor, One Capital Place | Streaming data distributed processing method and device |
| CN111092933A (en) * | 2019-11-20 | 2020-05-01 | 泰康保险集团股份有限公司 | Business process management method, system, medium and electronic device for micro-service architecture |
| CN111061550A (en) * | 2019-12-03 | 2020-04-24 | 北京每日优鲜电子商务有限公司 | Task processing method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117667362B (en) * | 2024-01-31 | 2024-04-30 | 上海朋熙半导体有限公司 | Method, system, equipment and readable medium for scheduling process engine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112200505A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112200505B (en) | Cross-business system process monitoring device and method, corresponding equipment and storage medium | |
| EP3932025B1 (en) | Computing resource scheduling method, scheduler, internet of things system, and computer readable medium | |
| CN108804215A (en) | A kind of task processing method, device and electronic equipment | |
| CN112181619B (en) | Batch service scheduling method, device, equipment and medium | |
| CN110275992B (en) | Emergency processing method, device, server and computer readable storage medium | |
| CN107819640A (en) | Monitoring method and device for robot operating system | |
| CN108632106A (en) | System for monitoring service equipment | |
| CN108536356A (en) | Agent information processing method and device and computer readable storage medium | |
| CN112256783A (en) | Data export method and device, electronic equipment and storage medium | |
| CN113658351B (en) | Method and device for producing product, electronic equipment and storage medium | |
| CN110008034A (en) | Task automated execution method, apparatus, electronic equipment and storage medium | |
| US20150120940A1 (en) | Apparatus and method for changing resource using pattern information, and recording medium using the same | |
| CN116860344A (en) | Flow management method, system, equipment and medium | |
| CN116938720A (en) | Service control method and device based on service cluster, electronic equipment and medium | |
| CN115499493A (en) | Asynchronous transaction processing method and device, storage medium and computer equipment | |
| CN115525568A (en) | Code coverage rate inspection method and device, computer equipment and storage medium | |
| CN112631860A (en) | Industrial Internet of things data transmission Worker service monitoring method and device | |
| JP2005141466A (en) | Computer monitoring device and message processing method for processing message about computer to be monitored | |
| CN110825560A (en) | Execution error processing method, device, equipment and computer readable storage medium | |
| CN105808348A (en) | Data service scheduling apparatus, system and method | |
| CN112799794A (en) | Big data scheduling method, device and system and storage device | |
| CN117667362B (en) | Method, system, equipment and readable medium for scheduling process engine | |
| CN115827678B (en) | Method, device, medium and electronic equipment for acquiring service data | |
| US12093587B1 (en) | System, method, and computer program for unified management of multiple master-agent job execution environments | |
| CN113778570B (en) | Distributed system breakpoint retry method based on AOP+Threadlocal technology |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |