Visualization system for whole business process
Injecting through bytecode injection technology Injects the visualized characteristic bytecode into the islands of the enterprise, generate data from the business process, and realize the entire process of business through the storage and display of the data processing end, solve the data integration and real -time problems, realize the system system Bottleneck recognition and online issues repair.
Patent Information
- Application Number
- CN202411191506.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-28
- Publication Date
- 2025-01-28
AI Technical Summary
When enterprises composed of multiple island systems are visualized throughout the business process, they face challenges such as data integration, real-time data transmission and visual display.
The bytecode injection technology dynamically injects the visualized characteristic bytecode into the business system, generates the business process data, and visualizes the entire process of business through the storage and display of the data processing end.
Realize the integration and real -time visualization of business processes of cross -system, accurately identify system bottlenecks and abnormalities, and support the repair of online problems and system optimization.
Smart Images

Figure CN119378963A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a visualization system for the entire business process. Background Art
[0002] The visualization of the entire business process uses charts, dashboards, etc. to monitor and analyze the entire business process in real time, aiming to quickly identify bottlenecks and failures, optimize processes, and improve efficiency and customer satisfaction. However, the entire business process of most companies is often composed of multiple isolated systems with different construction times, different technical architectures, and different data standards, resulting in many challenges in data integration, real-time data transmission, and visualization display when carrying out the visualization of the entire business process. Summary of the invention
[0003] In view of this, the present application proposes a visualization system for the entire business process to solve or partially solve the above problems.
[0004] Based on the above purpose, the present application provides a visualization system for the entire business process, characterized in that it is applied to a business system group including at least one business system, and the visualization system includes:
[0005] The bytecode injection end is configured to use a bytecode injection tool based on a set rule to inject bytecode into at least one process of the at least one business system for business processing, so as to use the bytecode to collect, detect and process data of the at least one process, and thereby generate business process data;
[0006] The data processing end is connected to the bytecode injection end and is configured to receive the business process data and store and display the business process data.
[0007] In some exemplary embodiments, the bytecode injection end includes:
[0008] a parameter detection unit, provided in any business system of the at least one business system, and configured to perform the bytecode injection on an input parameter of the any business system;
[0009] A business processing unit, provided in any business system of the at least one business system, and configured to perform the bytecode injection on at least one business processing process of the any business system;
[0010] The result collection unit is arranged in any business system of the at least one business system, and is configured to perform the bytecode injection on the operation result of the any business system.
[0011] In some exemplary embodiments, the parameter detection unit includes:
[0012] a separate detection module configured to obtain first data corresponding to an input parameter of any business system by using the bytecode injection, detect the first data according to a first rule, and generate the business process data;
[0013] The combined detection module is configured to use the bytecode injection to obtain second data corresponding to the input parameters of any business system, perform detection according to the second rule in the set scenario, and generate the business process data.
[0014] In some exemplary embodiments, the service processing unit includes:
[0015] a parameter detection module, configured to obtain third data corresponding to the parameters of the at least one business processing process by using the bytecode injection, detect the third data according to a third rule, and generate the business process data;
[0016] The result feedback module is configured to use the bytecode injection to obtain fourth data corresponding to the result of the at least one business processing process, detect the third data according to a fourth rule, and generate the business process data.
[0017] In some exemplary embodiments, the service processing unit further includes:
[0018] The abnormal scenario reinforcement module is configured to determine the abnormal position corresponding to the result that does not comply with the corresponding rules when the result feedback module detects the result that does not comply with the corresponding rules; when the update processing process code corresponding to the abnormal position is obtained, the update processing process code is set at the abnormal position using the bytecode injection method.
[0019] In some exemplary embodiments, the result collection unit includes:
[0020] A result detection module is configured to obtain fifth data corresponding to the output result of any business system by using the bytecode injection, detect the fifth data according to a fifth rule, and generate the business process data;
[0021] The result collection module is configured to use the bytecode injection to obtain sixth data corresponding to the input result of any business system, perform detection according to the sixth rule in the set scenario, and generate the business process data.
[0022] In some exemplary embodiments, the data processing end includes:
[0023] A data management unit is configured to receive the business process data transmitted by the bytecode injection end, and store and distribute the business process data;
[0024] A historical data analysis unit configured to perform data analysis on the stored business process data;
[0025] The business process display unit is configured to receive the business process data distributed by the data management unit to display the business process, and receive and display the data analysis result of the historical data analysis unit.
[0026] In some exemplary embodiments, the data management unit includes:
[0027] A data writing module is configured to write the business process data obtained from the bytecode injection end into a corresponding data storage device;
[0028] A data distribution module, configured to distribute the business process data obtained from the bytecode injection end;
[0029] The data reading module is configured to provide a reading interface for the business process display unit.
[0030] In some exemplary embodiments, the historical data analysis unit includes:
[0031] A data analysis module is configured to obtain the stored business process data according to the seventh rule and analyze the processing results of the obtained business process data;
[0032] a performance analysis module, configured to obtain stored business process data according to the eighth rule, and analyze the processing efficiency of the obtained business process data;
[0033] The abnormality analysis module is configured to obtain abnormal data from the stored business process data and analyze the abnormal data.
[0034] In some exemplary embodiments, the business process display unit includes:
[0035] A real-time display module, configured to receive the business process data distributed by the data management unit and display the business process;
[0036] A history display module is configured to receive stored business process data and display historical business processes;
[0037] The analysis and presentation module is configured to receive the analysis data from the historical data analysis unit and perform business analysis presentation.
[0038] From the above, it can be seen that the visualization system of the entire business process provided by the present application is applied to a business system group including at least one business system, and the visualization system includes: a bytecode injection end, which is configured to use a bytecode injection tool based on set rules to inject bytecode into at least one process of business processing of the at least one business system, so as to collect, detect and process data of the at least one process using the bytecode, and thereby generate business process data; a data processing end, which is connected to the bytecode injection end and is configured to receive the business process data, store and display the business process data. The present application dynamically injects business process visualization feature bytecode into the original executable file of the business system in the complete business chain through a bytecode injection tool, so that business process data in the format of a business chain data structure can be generated during the operation of the business system, and the business process data generated by all systems can form a complete business chain, and then the business process data storage, the message queue of the data processing end, and the business process display are used to realize the visualization of the entire business process. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0040] Figure 1 A schematic diagram of the system structure framework of the entire service process provided by an embodiment of the present application is shown.
[0041] Figure 2 A schematic diagram of the structure of a visualization system for the entire business process provided by an embodiment of the present application is shown.
[0042] Figure 3 A schematic diagram showing the effect of the bytecode injection method provided in an embodiment of the present application is shown.
[0043] Figure 4 A schematic diagram of the structure of a parameter detection unit provided in an embodiment of the present application is shown.
[0044] Figure 5 A schematic diagram of the structure of a business processing unit provided in an embodiment of the present application is shown.
[0045] Figure 6 A schematic diagram of the structure of a result collection unit provided in an embodiment of the present application is shown.
[0046] Figure 7 A schematic diagram of the structure of a data management unit provided in an embodiment of the present application is shown.
[0047] Figure 8 A schematic diagram of the structure of a historical data analysis unit provided in an embodiment of the present application is shown.
[0048] Fig. 9 A schematic diagram of the structure of a business process display unit provided in an embodiment of the present application is shown.
[0049] Fig.10 A flow chart of real-time processing of business process data provided by an embodiment of the present application is shown.
[0050] Fig.11 A schematic diagram of the process of viewing historical data provided by an embodiment of the present application is shown.
[0051] Fig.12 A schematic diagram of the process of historical data analysis provided by an embodiment of the present application is shown. DETAILED DESCRIPTION
[0052] In order to make the purpose, technical solutions and advantages of this specification more clear, this specification is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.
[0053] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements, objects or method steps appearing before the word cover the elements, objects or method steps listed after the word and their equivalents, without excluding other elements, objects or method steps. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0054] As described in the background technology section, visualization of the entire business process refers to the process of real-time monitoring and analysis of the entire business process from start to finish through visualization methods such as charts, dashboards, and real-time data. This technology can not only help companies improve operational efficiency, but also provide strong support for decision-making. The implementation steps are generally data collection, data processing, and visualization display. When the business involves multiple systems and multiple devices, there may be differences in data formats and protocols between different systems and devices, resulting in greater difficulty in data integration and processing. At present, in terms of visualization of the entire business process, the more advanced solution is to use third-party software to collect all system logs, and through the powerful log collection, parsing, storage, search and visualization capabilities of the third-party software, to achieve visualization of the entire business process.
[0055] In some embodiments, a method of using third-party software to collect all system logs and realizing visualization of the entire business process through the log collection, parsing, storage, search and visualization capabilities of the third-party software can solve the problem of displaying the entire business process of the business system group. However, due to the large amount of log data generated by the system group, different log formats and protocols exist in different business systems, the performance of each system is different and there are some historical problems that have not yet been fixed, and the deployment of third-party software requires a large amount of storage and computing resources. This leads to many difficulties in actual application.
[0056] In view of the above actual situation, the embodiment of the present application provides a visualization system for the entire business process. The present application dynamically injects business process visualization feature bytecodes into the original executable files of the business system in the complete business chain through a bytecode injection tool, so that business process data in the format of a business chain data structure can be generated during the operation of the business system, and all the business process data generated by the system can form a complete business chain, and then the business process data storage, the message queue of the data processing end, and the business process display are used to realize the visualization of the entire business process. More specifically, in response to the above problems, a lightweight business process visualization system based on ECA rules is proposed. The system is based on a business process visualization model, and dynamically injects business process visualization feature bytecodes into the original executable files of the business system in the complete business chain through a bytecode injection tool, so that process data in the format of a business chain data structure can be generated during the operation of the business system, and all the process data generated by the system can form a complete business chain, and then the business process data storage, message queue, and business process display are used to realize the visualization of the entire business process.
[0057] First, if Figure 1 As shown, in some embodiments, the business process visualization model can be composed of four parts: a business system group, a business process data storage device, a message queue, and a business process display terminal.
[0058] after, Figure 2FIG. 1 is a schematic diagram showing a structure of a visualization system for the entire business process provided by an embodiment of the present application. Figure 2 As shown, the visualization system of the entire business process proposed in the embodiment of the present application is applied to Figure 1 The business process visualization model shown is specifically applied to a business system group including at least one business system. The system of this embodiment is intended to effectively detect and acquire data from the business system throughout the entire process, and to display and store the data, so as to achieve full visualization of the business process. Specifically, the visualization system may include:
[0059] The bytecode injection end 100 is configured to use a bytecode injection tool based on set rules to inject bytecode into at least one process of business processing of the at least one business system, so as to use the bytecode to collect, detect and process data of the at least one process, and thereby generate business process data.
[0060] The data processing end 200 is connected to the bytecode injection end 100 and is configured to receive the business process data, store and display the business process data.
[0061] In this embodiment, the bytecode injection tool can be a Java bytecode injection tool in a specific application, which is a tool that can modify or enhance Java bytecode. This type of tool can change the behavior of the program without modifying the source code, thereby optimizing, enhancing or other specific purposes of the program. Common Java bytecode injection tools include the following: ASM, Javassist, ByteBuddy, Byteman, etc. Among them, Byteman is a Java bytecode injection tool, which is mainly used to monitor and modify Java programs at runtime. It can be used to debug and test applications, as well as troubleshoot and perform performance analysis in a production environment. It tests applications by injecting scripts into application code, using a technology called fault injection to simplify the testing and development of Java applications. In general, the corresponding bytecode injection tool must meet specific setting rules to achieve the corresponding function. Taking Byteman as an example, when performing bytecode injection, it is generally necessary to meet the ECA rule. Specifically, Byteman's ECA (Event Condition Action) rule is one of its core features, which is used to accurately specify the behavior of the application at runtime. The ECA rule is divided into three parts: event, condition and action. An event specifies the trigger point for bytecode injection, i.e. where to inject the code. It can be specified at the entry point of a method (AT ENTRY), exit point (AT EXIT), specific line number (AT LINE number), field read / write (AT READ / WRITE), method call (AT INVOKE), etc. A condition is a Java Boolean expression that determines whether an action should be executed when an event occurs. The action part is executed only when the condition is true. An action is a Java expression or code sequence that is executed when the condition is true. It can call a method, modify a variable value, throw an exception, etc. Byteman then allows users to define custom methods in the rule file, which can be called in the action part of a Byteman rule. The use of custom methods can enhance the flexibility and reusability of Byteman scripts. Custom methods are usually defined in a Java class, which can be a separate class or a subclass that extends the Byteman Helper class. The Helper class is a base class provided by Byteman to support custom Helper methods. In a Byteman rule file, you can use the HELPER keyword to specify a helper class for a custom method and call that method in the DO part of an action.
[0062] In this embodiment, the bytecode injection terminal 100 can use the bytecode injection tool introduced above to dynamically inject the business process visualization feature bytecode into the original executable files of each business system. Based on the business process visualization model, low-intrusive and low-system resource investment function expansion is achieved. The entire model only needs to add additional storage resources and computing resources such as databases, message queues, and business process display terminals. Figure 3 As shown, the injected bytecode includes: built-in operation set bytecode, custom helper class bytecode and ECA rule script bytecode. In this way, data can be collected, detected and processed for at least one process of business processing of at least one business system, and finally business process data can be generated according to the corresponding collection, detection and processing results, for example Figure 1 As shown, each process of business system 1 can be injected, and each process of business system 2 can be injected at the same time.
[0063] Afterwards, the data processing end 200 mainly assists the bytecode injection end, collects and stores the collected business process data, or directly displays the real-time business process, and can also use the stored business process data to analyze historical data, etc. Specifically, the data processing end 200 can present the complete business process by displaying each business data, thereby realizing the visualization of the entire business process.
[0064] From this, it can be seen that this embodiment realizes lightweight business process visualization based on ECA rules through dynamic bytecode injection technology. In terms of data quantity, only the necessary specified business process data is generated to reduce the amount of data displayed and analyzed; in terms of data format, the complete business chain is clearly expressed through a proprietary business process visualization model and process data structure; in terms of identifying system bottlenecks, based on the time difference and abnormal duration between business chain nodes, the system performance and business processing bottlenecks are accurately identified; in terms of system problem discovery and repair, online problem discovery is realized based on business process visualization, and online repair is realized based on dynamic bytecode injection technology; in terms of function expansion resource occupancy, low-intrusive and low-system resource investment function expansion is realized based on dynamic bytecode injection technology. The system realizes the injection of functional bytecodes such as parameter detection, business processing, and result collection through Java dynamic bytecode injection technology, H5 front-end technology, ECharts graphic components, etc., and constructs the integrated visualization of the business process of the business system group through process data management, historical data analysis, business process display and other functions.
[0065] In some embodiments, Figure 2As shown, the bytecode injection end 100 can be further divided into a parameter detection unit 101, a business processing unit 102 and a result collection unit 103. The data processing end 200 can be further divided into a data management unit 201, a historical data analysis unit 202 and a business process display unit 203.
[0066] The parameter detection unit 101 is set in any business system of the at least one business system and is configured to perform the bytecode injection on the input parameters of the any business system. The parameter detection unit 101 can be used to detect the input parameters of the business system, and the detection range includes the business system interface input parameter detection, the previous business system collection result detection, and the parameter combination detection according to the business logic. Figure 4 As shown, the parameter detection unit 101 may further include a separate detection module 1011, configured to use the bytecode injection to obtain first data corresponding to the input parameter of any business system, detect the first data according to a first rule, and generate the business process data. A combined detection module 1012 is configured to use the bytecode injection to obtain second data corresponding to the input parameter of any business system, detect according to a second rule in a set scenario, and generate the business process data.
[0067] Specifically, the separate detection module 1011 can implement a set of input parameter detection custom methods based on ECA rules based on Byteman, supporting the detection of basic data types such as Byte, Short, Integer, Long, Float, Double, Boolean and String. The entry (AT ENTRY) of the business system entry function is used as the event trigger point, and the custom method is called to detect these input parameters, and a business process data is formed according to the inspection result, that is, the entry (ATENTRY) of the entry function is used as the injection point to obtain the first data, and then the corresponding detection rule (i.e., the first rule) is determined according to the specific form or specific scenario of the acquired data, so as to perform detection and generate business process data. The combination detection module 1012 can implement a custom method for detecting combination parameters of specific businesses based on ECA rules based on Byteman, with the entry (AT ENTRY) of the business system entry function as the event trigger point, call a custom method to detect these input parameters, and form a business process data based on the inspection result, that is, with the entry (AT ENTRY) of the business system entry function as the injection point, obtain the second data, and then set the second rule according to the different scenarios in which the parameters are to be used, so as to perform detection and generate business process data.
[0068] The parameter detection unit 101 writes the business process data generated by the individual detection module 1011 and the combined detection module 1012 into the business process data storage through the data management unit 201 and distributes it to the business process display unit 203 based on the message queue.
[0069] For any business system in which the business processing unit 102 is placed in the at least one business system, the bytecode injection is configured to be performed on at least one business process of the business system. The business processing unit 102 can be used to provide feedback on the normality of changes in business parameters during operation, provide feedback on the functional results and performance results of business processing, and reinforce the discovered program problems. Figure 5 As shown, the business processing unit 102 may further include a parameter detection module 1021, which is configured to use the bytecode injection to obtain third data corresponding to the parameters of the at least one business processing process, detect the third data according to a third rule, and generate the business process data; a result feedback module 1022, which is configured to use the bytecode injection to obtain fourth data corresponding to the result of the at least one business processing process, detect the third data according to the fourth rule, and generate the business process data.
[0070] Furthermore, in some scenarios, business processing process exceptions are often encountered. The process exception here can be an error, such as a bug, etc., or it can be found that the efficiency or effect of the corresponding processing process is lower than expected, which can also be considered as an exception. In response to such anomalies, the business processing unit 102 can further include an abnormal scenario reinforcement module 1023, which is configured to determine the abnormal position corresponding to the result that does not conform to the corresponding rules when the result feedback module detects a result that does not conform to the corresponding rules; when the update processing process code corresponding to the abnormal position is obtained, the update processing process code is set at the abnormal position using the bytecode injection method.
[0071] Specifically, the parameter detection module 1021 can implement a custom method based on Byteman to detect changes in business parameters during operation based on ECA rules. The business parameters are detected using the method entry (AT ENTRY) and exit (AT EXIT) as event trigger points, and the custom method is called to detect these input parameters. A business process data is formed according to the inspection result, that is, the method entry (AT ENTRY) and exit (AT EXIT) are used as event trigger points (bytecode injection points) to obtain the third data, and then the corresponding detection rules (i.e., the third rules) are determined according to the specific form or specific scenario of the acquired data, so as to perform detection and generate business process data. The result feedback module 1022 can implement a custom method based on Byteman to detect the functional results, performance results, etc. of business processing based on ECA rules. The method exit (ATEXIT) is used as the event trigger point for detection, and the custom method is called to detect these input parameters, and a business process data is formed according to the inspection result, that is, the method exit (AT EXIT) is used as the event trigger point (bytecode injection point), and the fourth data is obtained, and then the corresponding detection rule (i.e., the fourth rule) is determined according to the specific form or specific scenario of the acquired data, so as to perform detection and generate business process data. The abnormal scenario reinforcement module 1023 can implement a custom method for reinforcing program problems based on ECA rules based on Byteman, and modify the execution branch at the specific line number (AT LINE number) where the problem point appears, so as to realize online reinforcement of the problem and form a business process data, wherein the problem point is the abnormal position corresponding to the result determined to be inconsistent with the corresponding rule; and the process of modifying the branch is to set the update processing process code at the abnormal position by bytecode injection when the update processing process code corresponding to the abnormal position is obtained.
[0072] The business processing unit 102 writes the business process data generated by the parameter detection module 1021, the result feedback module 1022 and the abnormal scenario reinforcement module 1023 into the business process data storage through the data management unit 201 and distributes it to the business process display unit 203 based on the message queue.
[0073] The result collection unit 103 is set in any business system of the at least one business system, and is configured to perform the bytecode injection on the operation result of any business system. The result collection unit 103 can be used to detect whether the business operation result is consistent with the expectation, and collect the result into a business process data. Figure 6As shown, the result collection unit 103 may further include a result detection module 1031, which is configured to use the bytecode injection to obtain fifth data corresponding to the output result of any business system, detect the fifth data according to the fifth rule, and generate the business process data; the result collection module 1032 is configured to use the bytecode injection to obtain sixth data corresponding to the input result of any business system, detect according to the sixth rule in a set scenario, and generate the business process data.
[0074] Specifically, the result detection module 1031 can implement a custom method based on Byteman to detect and judge whether the business operation results are consistent with expectations based on the ECA rules. The method exit (AT EXIT) is used as the event trigger point for detection, and the custom method is called to detect these input parameters, and a business process data is formed according to the inspection result, that is, the method exit (AT EXIT) is used as the event trigger point (bytecode injection point), and the fifth data is obtained, and then the corresponding detection rule (i.e., the fifth rule) is determined according to the specific form or specific scenario of the acquired data, so as to perform detection and generate business process data. The result collection module 1032 can implement a custom method based on Byteman to collect the results into a specific structure based on the ECA rules. The method exit (AT EXIT) is used as the event trigger point for detection, and the custom method is called to detect these input parameters, and a business process data is formed according to the inspection result, that is, the method exit (AT EXIT) is used as the event trigger point (bytecode injection point), and the sixth data is obtained, and then the sixth rule is set according to the different scenarios in which the parameters are to be used, so as to perform detection and generate business process data.
[0075] The result collection unit 103 writes the business process data generated by the result detection module 1031 and the result collection module 1032 into the business process data storage through the data management unit 201 and distributes it to the business process display unit 203 based on the message queue.
[0076] The data management unit 201 is configured to receive the business process data transmitted by the bytecode injection terminal 100, store and distribute the business process data. The data management unit 201 can be used to manage the business process data, provide an interface for writing, distributing and reading the business process data, and store the business process data persistently. Figure 7As shown, the data management unit 201 may further include: a data writing module 2011, configured to write the business process data obtained from the bytecode injection terminal 100 to a corresponding data storage device; a data distribution module 2012, configured to distribute the business process data obtained from the bytecode injection terminal 100; and a data reading module 2013, configured to provide a reading interface for the business process display unit 203.
[0077] Specifically, the data writing module 2011 can provide the business system with a writing interface for business process data and store the data in the business process data storage device; the data distribution module 2012 can distribute business process data to the business process display unit 203 based on the message queue; the data reading module 2013 provides the business process display unit 203 with a reading interface for business process data.
[0078] The parameter detection unit 101, the business processing unit 102 and the result collection unit 103 call the data writing module 2011 to store the generated business process data in the business process data storage device, and call the data distribution module 2012 to distribute the business process data to the business process display unit 203 based on the message queue; the business process display unit 203 reads the historical business process data stored in the business process data storage device through the data reading module 2013, and views and analyzes the historical business process data.
[0079] The historical data analysis unit 202 is configured to perform data analysis on the stored business process data. The historical data analysis unit 202 can analyze the business process, business processing performance, business processing abnormality rate, etc. through historical data. Figure 8 As shown, the historical data analysis unit 202 may further include: a data analysis module 2021, configured to obtain stored business process data according to the seventh rule, and analyze the processing results of the obtained business process data; a performance analysis module 2022, configured to obtain stored business process data according to the eighth rule, and analyze the processing efficiency of the obtained business process data; an abnormality analysis module 2023, configured to obtain abnormal data in the stored business process data, and analyze the abnormal data.
[0080] Specifically, the data analysis module 2021 can provide a variety of conditions for reading historical data in the business process data storage, and analyze whether these historical data meet the needs of the scene or the needs of the corresponding task in the corresponding scene, that is, obtain the stored business process data according to the seventh rule, and combine the obtained data into a format suitable for display of graphic components such as line graphs, bar graphs, and scatter graphs. The performance analysis module 2022 can provide a variety of conditions for reading historical data in the business process data storage, obtain the time difference and abnormal duration between business chain nodes, accurately identify system performance and business processing bottlenecks, that is, obtain the stored business process data according to the eighth rule, and combine the obtained complete business process data into a format suitable for display of graphic components such as line graphs and bar graphs, providing a basis for system optimization. The abnormal analysis module 2023 can provide a variety of conditions for reading historical data in the business process data storage, obtain relevant abnormal point information, and combine the data into a format suitable for display of graphic components such as line graphs, providing a basis for system optimization.
[0081] The business process display unit 203 calls the data analysis module 2021, the performance analysis module 2022, and the exception analysis module 2023 to perform business process analysis, performance analysis, and abnormal data analysis; the data analysis module 2021, the performance analysis module 2022, and the exception analysis module 2023 obtain the historical data required for analysis through the data management unit 201 and perform corresponding analysis.
[0082] The business process display unit 203 is configured to receive the business process data distributed by the data management unit 201 to display the business process, and receive and display the data analysis results of the historical data analysis unit 202. The business process display unit 203 can display real-time business processes, historical business processes and historical data analysis results. Fig. 9 As shown, the business process display unit 203 may further include: a real-time display module 2031, configured to receive the business process data distributed by the data management unit 201 and perform business process display; a historical display module 2032, configured to receive stored business process data and perform historical business process display; an analysis display module 2033, configured to receive the analysis data of the historical data analysis unit 202 and perform business analysis display.
[0083] Specifically, based on H5 technology, ECharts graphic components, etc., the visualization display of the entire business process is realized, providing users with clear and understandable business process visualization functions. The real-time display module 2031 can receive the real-time data of the business process from the message queue through the data management unit 201, and display the entire business process and business point details through graphic components such as line charts, bar charts, and scatter charts. The historical display module 2032 can read the business process historical data from the business process data storage through the data management unit 201, and display the entire business process and business point details through graphic components such as line charts, bar charts, and scatter charts. The analysis and display module 2033 can obtain the results of the historical data analysis carried out by the historical data analysis unit 202, and display the business processing performance, abnormal points, etc. of the entire business process through graphic components such as line charts and bar charts.
[0084] In more specific scenarios, such as Figure 1 and Figure 2 As shown, the business process data generated in the complete business process from business start to business end is stored in the business process data storage device, and the whole process includes: parameter detection, business processing, and result collection. The real-time data of the business process is sent to the business process display terminal through the message queue for real-time display. The business process display terminal reads the business process historical data of the business process data storage device to carry out historical business process analysis. A business process data is uniquely identified by the business sequence number, business system sequence number, sub-business sequence number, and sub-business fragment sequence number. The structure of the business process data is Json format data including the following key fields: business sequence number, business system sequence number, sub-business sequence number, sub-business fragment sequence number, and business data. Among them, the business data includes: start time, end time, business operation results, business execution performance data, etc. All business process data generated by a full business process execution constitute a complete business chain. The sequence number of each system in the business system group in a specific business is determined by configuration. When displaying the full business process, it is displayed in order according to the configured sequence number. The business with sequence number 1 is the start business of the complete business, and the business with the largest sequence number is the end business of the complete business.
[0085] It can be seen from the above embodiments that a visualization system for the entire business process provided by the embodiments of the present application is applied to a business system group including at least one business system, and the visualization system includes: a bytecode injection end, which is configured to use a bytecode injection tool based on set rules to inject bytecode into at least one process of business processing of the at least one business system, so as to collect, detect and process data of the at least one process using the bytecode, and thereby generate business process data; a data processing end, which is connected to the bytecode injection end and is configured to receive the business process data, store and display the business process data. The present application dynamically injects business process visualization feature bytecode into the original executable file of the business system in the complete business chain through a bytecode injection tool, so that business process data in the format of a business chain data structure can be generated during the operation of the business system, and the business process data generated by all systems can form a complete business chain, and then the business process data storage, the message queue of the data processing end, and the business process display are used to realize the visualization of the entire business process.
[0086] Furthermore, in some embodiments, the visualization system corresponding to the entire business process in the above embodiments can be divided into a business process data real-time processing process, a historical business process data viewing process, and a historical business process data analysis process during the application process.
[0087] Afterwards, for the real-time processing flow of business process data, the business process data is generated by the parameter detection unit 101, the business processing unit 102 and the result collection unit 103 during operation. Taking the parameter detection unit 101 as an example, Fig.10 As shown, the specific processing flow can be as follows to illustrate the real-time processing flow of business process data. After the parameter detection unit 101 generates the business process data, firstly, the data writing module 2011 of the data management unit 201 is called to write the data into the business process data storage, and secondly, the data distribution module 2012 of the data management unit 201 is called to distribute the business process data to the business process display unit 203 through the message queue, and the business process display unit 203 performs real-time display of the business process through the business process real-time display module 2031.
[0088] For historical business process data viewing process, such as Fig.11 As shown, the history display module 2032 of the business process display unit 203 calls the data reading module 2013 of the data management unit 201 to obtain historical data from the business process data storage, and finally returns the analysis result to the business process display unit 203. The business process display unit 203 displays the historical business process data through the history display module 2032.
[0089] For historical business process data analysis flow, such as Fig.12As shown, the analysis and display module 2033 of the business process display unit 203 calls the data analysis module 2021, the performance analysis module 2022, the abnormal analysis module 2023, etc. of the historical data analysis unit 202 to perform historical data analysis. The historical data analysis unit 202 calls the data reading module 2013 of the data management unit 201 to obtain historical data from the business process data storage, and hands the data to the historical data analysis unit 202 for corresponding analysis, and finally returns the analysis result to the business process display unit 203. The business process display unit 203 performs historical business process data analysis and display through the analysis and display module 2033.
[0090] It should be noted that the aforementioned various process methods of the embodiments of the present application can be executed by a single device, such as a computer or server. The various process methods of the embodiments of the present application can also be applied to distributed scenarios and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only execute one or more steps in the various process methods of the embodiments of the present application, and the multiple devices will interact with each other to complete the described method.
[0091] It should be noted that the above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0092] As can be seen from the above, the embodiments of the present application solve the problems of business process data formatting, real-time business process data transmission, visual display of the entire business process, system bottleneck identification, abnormal identification and problem repair, and as little investment in system computing resources as possible through the following technical implementations. 1) Business process data formatting: Design a visual model and process data structure for the entire business process to clearly represent complex business processes, ensuring that all key business process data can be captured and integrated in an orderly manner during the entire execution cycle of the business system group from the start of the business to the end of the business, and then weave a coherent and complete business chain. 2) Business process data transmission real-time: Based on message queues and applying parallel processing technology, the storage and display of business process data are carried out in parallel. When the business system writes the business process data into the business process data storage device, it immediately distributes the data to the business process display terminal through the message queue, thereby realizing the immediacy and efficiency of data processing, and ensuring the real-time visibility and response speed of the business process data. 3) Business process visual display: Use advanced H5 front-end technology combined with ECharts graphic components to achieve real-time visual presentation of the entire business process and intuitive display of historical data analysis results. This solution not only improves the user experience, but also facilitates users to quickly understand business dynamics and provide strong support for decision-making. 4) System bottleneck identification: Based on the time difference and abnormal duration between business chain nodes, accurately identify system performance and business processing bottlenecks. This method not only helps to quickly locate the source of the problem, but also provides a scientific basis for system optimization and business improvement. 5) Abnormal identification and problem repair: Provide custom reinforcement methods for program abnormalities, and analyze the business process data fed back during system operation to timely discover and locate program abnormalities. For newly discovered problems, by updating custom reinforcement methods, effective repair of problems and further reinforcement of the system are achieved to ensure the stable operation and continuous optimization of the system. 6) System computing resources: The Java dynamic bytecode injection technology is used on the original system to realize the visualization of the entire business process, and low-intrusive function expansion is achieved on the basis of retaining the original system architecture. This solution only requires additional configuration of an appropriate amount of data storage resources and a small amount of computing resources to efficiently complete the in-depth analysis and intuitive display of data, maximize the use of existing system resources, and reduce the overall deployment cost.
[0093] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.
[0094] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.
[0095] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.
[0096] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.
Claims
1. A visualization system for the entire business process, characterized in that: Applied to a business system group including at least one business system, the visualization system comprises: The bytecode injection end is configured to use a bytecode injection tool based on a set rule to inject bytecode into at least one process of the at least one business system for business processing, so as to use the bytecode to collect, detect and process data of the at least one process, and thereby generate business process data; The data processing end is connected to the bytecode injection end and is configured to receive the business process data and store and display the business process data.
2. The visualization system according to claim 1, characterized in that The bytecode injection end includes: a parameter detection unit, provided in any business system of the at least one business system, and configured to perform the bytecode injection on an input parameter of the any business system; A business processing unit, provided in any business system of the at least one business system, and configured to perform the bytecode injection on at least one business processing process of the any business system; The result collection unit is arranged in any business system of the at least one business system, and is configured to perform the bytecode injection on the operation result of the any business system.
3. The visualization system according to claim 2, characterized in that The parameter detection unit comprises: a separate detection module configured to obtain first data corresponding to an input parameter of any business system by using the bytecode injection, detect the first data according to a first rule, and generate the business process data; The combined detection module is configured to use the bytecode injection to obtain second data corresponding to the input parameters of any business system, perform detection according to the second rule in the set scenario, and generate the business process data.
4. The visualization system according to claim 2, characterized in that The business processing unit includes: a parameter detection module, configured to obtain third data corresponding to the parameters of the at least one business processing process by using the bytecode injection, detect the third data according to a third rule, and generate the business process data; The result feedback module is configured to use the bytecode injection to obtain fourth data corresponding to the result of the at least one business processing process, detect the third data according to a fourth rule, and generate the business process data.
5. The visualization system according to claim 4, characterized in that The service processing unit further includes: The abnormal scenario reinforcement module is configured to determine the abnormal position corresponding to the result that does not comply with the corresponding rules when the result feedback module detects the result that does not comply with the corresponding rules; when the update processing process code corresponding to the abnormal position is obtained, the update processing process code is set at the abnormal position using the bytecode injection method.
6. The visualization system according to claim 2, characterized in that: The result collection unit includes: A result detection module is configured to obtain fifth data corresponding to the output result of any business system by using the bytecode injection, detect the fifth data according to a fifth rule, and generate the business process data; The result collection module is configured to use the bytecode injection to obtain sixth data corresponding to the input result of any business system, perform detection according to the sixth rule in the set scenario, and generate the business process data.
7. The visualization system according to claim 1, characterized in that: The data processing end includes: A data management unit is configured to receive the business process data transmitted by the bytecode injection end, and store and distribute the business process data; A historical data analysis unit configured to perform data analysis on the stored business process data; The business process display unit is configured to receive the business process data distributed by the data management unit to display the business process, and receive and display the data analysis result of the historical data analysis unit.
8. The visualization system according to claim 7, characterized in that The data management unit comprises: A data writing module is configured to write the business process data obtained from the bytecode injection end into a corresponding data storage device; A data distribution module, configured to distribute the business process data obtained from the bytecode injection end; The data reading module is configured to provide a reading interface for the business process display unit.
9. The visualization system according to claim 7, characterized in that: The historical data analysis unit comprises: A data analysis module is configured to obtain the stored business process data according to the seventh rule and analyze the processing results of the obtained business process data; a performance analysis module, configured to obtain stored business process data according to the eighth rule, and analyze the processing efficiency of the obtained business process data; The abnormality analysis module is configured to obtain abnormal data from the stored business process data and analyze the abnormal data.
10. The visualization system according to claim 7, characterized in that: The business process display unit includes: A real-time display module is configured to receive the business process data distributed by the data management unit and display the business process; A history display module is configured to receive stored business process data and display historical business processes; The analysis and presentation module is configured to receive the analysis data from the historical data analysis unit and perform business analysis presentation.