Graphical ESB platform and data transmission push calling method

Abstract

The invention relates to the technical field of ESB systems, and provides a graphical ESB platform which comprises a system architecture, a graphical configuration interface, a data mapping engine, a protocol conversion module, a calling execution engine, a monitoring and early warning system, a log management function, a service governance function and a preset component. Container arrangement and management are carried out through Kubernetes, a graphical configuration interface allows a user to complete complex service integration and data flow configuration through simple dragging and connecting operations, and a data mapping engine supports data structure conversion of complex scenes such as one-to-many, many-to-one and condition mapping. According to the method, the development efficiency and the system flexibility are improved, service integration and data flow configuration are simplified through graphical configuration interface and micro-service architecture design, non-professional technicians can also rapidly operate, meanwhile, the high concurrent processing capacity and the transverse expansibility of the system are ensured, and rapid changes of service requirements are effectively supported.

Description

Technical Field

[0001] The present invention relates to the technical field of ESB systems, and in particular to a graphical ESB platform and a data transmission push calling method. Background Art

[0002] As an integrated architecture model, Enterprise Service Bus (ESB) plays a key role in enterprise system integration. Traditional ESB systems usually adopt a centralized architecture and implement communication and data exchange between different systems through standardized message formats and protocols. However, with the increasing complexity of enterprise IT environments and the rapid changes in business needs, traditional ESB systems face many challenges in terms of flexibility, scalability, and ease of use.

[0003] Current mainstream enterprise service bus (ESB) products generally face a series of challenges, including the complexity of the configuration process, which usually involves cumbersome XML configuration or specific scripting languages ​​to define services and data flows. In addition, the visualization capabilities of these systems are often insufficient, and they can only provide basic process design views, but cannot clearly display and manage complex service relationships and data mappings. The centralized architecture also limits the scalability of the system, making it difficult to adapt to the needs of large-scale and high-concurrency integration scenarios. In terms of monitoring, existing ESB products often lack effective real-time monitoring and early warning mechanisms, which makes the diagnosis and resolution of problems complicated and affects the overall stability and reliability of the system. At the same time, in terms of protocol adaptation, with the diversification of protocols and data formats, traditional ESB products show limitations in adapting to different systems and are difficult to meet the needs of heterogeneous system integration. In addition, due to the complex configuration and low degree of visualization, the daily maintenance and update of these systems need to rely on professional technicians, resulting in increased maintenance costs. In addition, the existing ESB system is also not flexible enough in terms of service governance, especially in terms of service version management, access control and traffic management, which makes it difficult to meet the needs of enterprises for full life cycle management of services. Finally, the development efficiency of traditional ESB systems is low, they rely on a lot of code writing, and they lack support for rapid development and iteration, which is inconsistent with the current trend of agile development.

[0004] Therefore, the present invention proposes an innovative graphical ESB platform and data transmission push calling method to solve the above problems. Summary of the invention

[0005] In view of the deficiencies of the prior art, the present invention provides a graphical ESB platform and a data transmission push calling method to help enterprises reduce the complexity and cost of system integration, while improving business response speed and IT operation and maintenance efficiency.

[0006] To achieve the above objectives, the present invention is implemented through the following technical solutions:

[0007] A graphical ESB platform includes a system architecture, a graphical configuration interface, a data mapping engine, a protocol conversion module, a call execution engine, a monitoring and early warning system, log management, service governance functions and preset components. The system architecture adopts a microservice architecture design, has a built-in core module, and performs container orchestration and management through Kubernetes. The graphical configuration interface allows users to complete complex service integration and data flow configuration through simple drag and drop and connection operations. The data mapping engine supports data structure conversion in complex scenarios such as one-to-many, many-to-one, and conditional mapping. The protocol conversion module defines protocol conversion rules through configuration to achieve seamless conversion between protocols. The call execution engine supports synchronous call mode and provides service orchestration and routing functions. The monitoring and early warning system collects key indicators such as the number of service calls, response time, and error rate by achieving all-round service performance monitoring, and displays them intuitively through a customizable dashboard. The log management supports multi-dimensional log retrieval and visual analysis by recording detailed service call logs. The service governance function integrates an API gateway to achieve unified security authentication and access control.

[0008] Preferably, the core module includes an interface service management module, a service adaptation module, a monitoring and early warning module and a log management module, and the interface service management module, the service adaptation module, the monitoring and early warning module and the log management module are all independently deployed in the form of Docker containers.

[0009] Preferably, the graphical configuration interface includes a service process designer, a data mapping tool and a service configuration panel. The service process designer uses the ANTV X6 library to implement drag-and-drop process design, the data mapping tool is developed based on vue and supports visual field mapping, and the service configuration panel is built using the Element UI component library to provide a service parameter configuration interface.

[0010] Preferably, the data mapping engine supports data conversion types such as field renaming, type conversion, and conditional mapping.

[0011] Preferably, the protocols supported by the protocol conversion module include HTTP / HTTPS, SOAP, and REST.

[0012] Preferably, the preset components include a data conversion component, a protocol adapter component and a business logic component, the data conversion component is used for field mapping, the protocol adapter component is used for automatic protocol conversion, and the business logic component is used for platform processing processes such as conditional judgment and loop processing.

[0013] A graphical ESB platform data transmission push calling method includes the following steps:

[0014] Step 1: API gateway receives external requests;

[0015] Step 2: The request is processed through authentication, authorization, and current limiting;

[0016] Step 3: The gateway forwards the request to the service module;

[0017] Step 4: The service module parses the request and determines the service call chain;

[0018] Step 5: Call the data mapping engine to perform data conversion;

[0019] Step 6: If protocol conversion is required, call the corresponding protocol conversion;

[0020] Step 7: Call the target service according to the configured process by calling the execution engine;

[0021] Step 8: Process the service return results and perform necessary data conversion;

[0022] Step 9: Push the processed data to the specified destination including message queue, WebSocket, etc.

[0023] Step 10: Record the complete call process log.

[0024] Preferably, the execution engine is called in step seven, and the specific steps include:

[0025] S1. Receive service request;

[0026] S2, parsing request content;

[0027] S3, execute the service call chain;

[0028] S4, summarizing the processing results;

[0029] S5. Return a response.

[0030] Preferably, the entire process from step 1 to step 10 is monitored by a monitoring and early warning system, and the specific steps are as follows:

[0031] S1. Each service module records time monitoring indicators through logs;

[0032] S2. After the alarm is triggered, a notification is sent through the channel mode integrated in the platform. The notification format supports any format such as email, in-site message, etc.

[0033] Preferably, during the steps 1 to 10, distributed log collection and analysis are performed using log management using the ELK stack, and the specific steps are as follows:

[0034] S1. Each service module uses log4j2 to output structured logs;

[0035] S2. Use Filebeat to collect log files of each module;

[0036] S3, use Logstash to parse and convert logs;

[0037] S4, the processed logs are stored in Elasticsearch;

[0038] S5. Perform log retrieval and visual analysis through Kibana.

[0039] The present invention provides a graphical ESB platform and a data transmission push calling method, which has the following beneficial effects:

[0040] 1. The present invention improves development efficiency and system flexibility. Through a graphical configuration interface and microservice architecture design, it simplifies service integration and data flow configuration, allowing non-professional technicians to quickly get started. At the same time, it ensures the system's high concurrent processing capability and horizontal scalability, effectively supporting rapid changes in business needs.

[0041] 2. The present invention strengthens system integration and service governance. By adopting flexible service adaptation and data conversion mechanisms, the platform supports multiple protocols and data formats, and enhances the integration capabilities of heterogeneous systems. At the same time, through real-time monitoring, intelligent early warning and log management, the reliability and maintainability of the system are improved, and comprehensive service governance functions are provided.

[0042] 3. The present invention reduces costs and accelerates digital transformation. It significantly reduces the total cost of ownership of enterprises by improving development and maintenance efficiency and optimizing system scalability. At the same time, it provides a wealth of preset components and templates, thereby accelerating the process of digital transformation of enterprises, helping enterprises to quickly complete the modernization of core systems and enhance market competitiveness. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A system diagram of a graphical ESB platform of the present invention;

[0044] Figure 2 is a system diagram of the core module of the present invention;

[0045] Figure 3 A system diagram of the graphical configuration interface of the present invention;

[0046] Figure 4 It is a core user interface diagram of the graphical ESB platform of the present invention. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0048] Example:

[0049] As one aspect of this application, please see the attached Figure 1 -Attached Figure 3 , an embodiment of the present invention provides a graphical ESB platform, including a system architecture, a graphical configuration interface, a data mapping engine, a protocol conversion module, a call execution engine, a monitoring and early warning system, log management, service governance functions and preset components.

[0050] The system architecture adopts microservice architecture design, with built-in core modules, including interface service management module, service adaptation module, monitoring and early warning module and log management module. The interface service management module, service adaptation module, monitoring and early warning module and log management module are independently deployed in the form of Docker containers, and the containers are orchestrated and managed through Kubernetes.

[0051] The graphical configuration interface allows users to complete complex service integration and data flow configuration through simple drag and drop and connection operations. The Web-based visual configuration interface is designed, and the drag-and-drop component configuration is implemented using HTML5 and SVG technology. The graphical configuration interface includes a service process designer, a data mapping tool, and a service configuration panel. The service process designer uses the ANTV X6 library to implement drag-and-drop process design, and the data mapping tool is developed based on vue and supports visual field mapping. The service configuration panel is built using the Element UI component library to provide a service parameter configuration interface.

[0052] Data mapping engine development is based on JSONPath, which supports conversion of multiple data formats such as XML and JSON. It provides a visual data field mapping tool, supports data structure conversion in complex scenarios such as one-to-many, many-to-one, conditional mapping, and supports data conversion types such as field renaming, type conversion, and conditional mapping.

[0053] The protocol conversion module defines protocol conversion rules through configuration to achieve seamless conversion between protocols. The protocols supported by the protocol conversion module include HTTP / HTTPS, SOAP, and REST.

[0054] The call execution engine builds a high-concurrency, low-latency service call execution engine, supports synchronous call mode, and provides service orchestration and routing functions.

[0055] The monitoring and early warning system implements comprehensive service performance monitoring, collects key indicators such as service call times, response time, error rate, etc., and displays them intuitively through customizable dashboards.

[0056] Log management uses the ELK (Elasticsearch, Logstash, Kibana) stack to implement distributed log collection and analysis. By recording detailed service call logs, it supports multi-dimensional log retrieval and visual analysis.

[0057] The service governance function implements fine-grained permission management based on the RBAC (role-based access control) model. It provides advanced service governance functions such as service version control, grayscale release, and traffic control, and integrates API gateway to achieve unified security authentication and access control.

[0058] The preset components include data conversion components, protocol adapter components and business logic components. The data conversion components are used for field mapping, the protocol adapter components are used to automatically convert protocols, and the business logic components are used for platform processing processes such as conditional judgment and loop processing.

[0059] Based on the graphical ESB platform provided above, as another aspect of the present application, a graphical ESB platform data transmission push calling method includes the following steps:

[0060] Step 1: API gateway receives external requests;

[0061] Step 2: The request is processed through authentication, authorization, and current limiting;

[0062] Step 3: The gateway forwards the request to the service module;

[0063] Step 4: The service module parses the request and determines the service call chain;

[0064] Step 5: Call the data mapping engine to perform data conversion;

[0065] Step 6: If protocol conversion is required, call the corresponding protocol conversion;

[0066] Step 7: Call the target service according to the configured process by calling the execution engine. The specific steps of calling the execution engine include:

[0067] S1. Receive service request;

[0068] S2, parsing request content;

[0069] S3, execute the service call chain;

[0070] S4, summarizing the processing results;

[0071] S5. Return a response;

[0072] Step 8: Process the service return results and perform necessary data conversion;

[0073] Step 9: Push the processed data to the specified destination including message queue, WebSocket, etc.

[0074] Step 10: Record the complete call process log.

[0075] The monitoring and early warning system is used to monitor the entire process from step 1 to step 10. The specific steps are as follows:

[0076] S1. Each service module records time monitoring indicators through logs;

[0077] S2. After the alarm is triggered, a notification is sent through the channel mode integrated in the platform. The notification format supports any format such as email, in-site message, etc.

[0078] During steps 1 to 10, distributed log collection and analysis are performed using log management using the ELK stack. The specific steps are as follows:

[0079] S1. Each service module uses log4j2 to output structured logs;

[0080] S2. Use Filebeat to collect log files of each module;

[0081] S3, use Logstash to parse and convert logs;

[0082] S4, the processed logs are stored in Elasticsearch;

[0083] S5. Perform log retrieval and visual analysis through Kibana.

[0084] This method is supported by continuous integration and deployment, integrated with Jenkins, and supports version control and automated deployment of service configuration. It provides multi-environment management functions, supports configuration isolation and one-click deployment of development, test, and production environments. The specific steps are:

[0085] S1. Use Git for version control;

[0086] S2, Jenkins is responsible for automated construction and deployment;

[0087] S3, realize multi-environment configuration management through Ansible;

[0088] S4. Define Kubernetes deployment templates using Helm Charts.

[0089] S5. Implement configuration version control and automated deployment through GitOps.

[0090] Please see attached Figure 4 This is the core user interface of the graphical ESB platform of the present invention. The interface adopts an intuitive drag-and-drop design, which greatly reduces the complexity of system configuration. The left side is the component library, which provides a wealth of preset components; the right side is the canvas area for service process design; the top toolbar provides common operation buttons. This visual configuration method allows even non-technical personnel to quickly get started, significantly improving development efficiency and reducing the risk of operational errors.

[0091] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A graphical ESB platform, characterized in that: It includes system architecture, graphical configuration interface, data mapping engine, protocol conversion module, call execution engine, monitoring and early warning system, log management, service governance function and preset components. The system architecture adopts microservice architecture design, built-in core modules, and container orchestration and management through Kubernetes. The graphical configuration interface allows users to complete complex service integration and data flow configuration through simple drag and drop and connection operations. The data mapping engine supports data structure conversion in complex scenarios such as one-to-many, many-to-one, and conditional mapping. The protocol conversion module defines protocol conversion rules through configuration to achieve seamless conversion between protocols. The call execution engine supports synchronous call mode and provides service orchestration and routing functions. The monitoring and early warning system collects key indicators such as service call times, response time, error rate, etc. by realizing comprehensive service performance monitoring, and displays them intuitively through customizable dashboards. The log management supports multi-dimensional log retrieval and visual analysis by recording detailed service call logs. The service governance function integrates API gateway to achieve unified security authentication and access control.

2. A graphical ESB platform according to claim 1, characterized in that: The core module includes an interface service management module, a service adaptation module, a monitoring and early warning module, and a log management module. The interface service management module, the service adaptation module, the monitoring and early warning module, and the log management module are all independently deployed in the form of Docker containers.

3. A graphical ESB platform according to claim 1, characterized in that: The graphical configuration interface includes a service process designer, a data mapping tool and a service configuration panel. The service process designer uses the ANTV X6 library to implement drag-and-drop process design. The data mapping tool is developed based on vue and supports visual field mapping. The service configuration panel is built using the Element UI component library to provide a service parameter configuration interface.

4. A graphical ESB platform according to claim 1, characterized in that: The data mapping engine supports data conversion types such as field renaming, type conversion, and conditional mapping.

5. A graphical ESB platform according to claim 1, characterized in that: The protocols supported by the protocol conversion module include HTTP / HTTPS, SOAP, and REST.

6. A graphical ESB platform according to claim 1, characterized in that: The preset components include a data conversion component, a protocol adapter component and a business logic component. The data conversion component is used for field mapping, the protocol adapter component is used for automatic protocol conversion, and the business logic component is used for platform processing processes such as condition judgment and loop processing.

7. A graphical ESB platform data transmission push calling method, using a graphical ESB platform as claimed in any one of claims 1 to 6, characterized in that: The following steps are involved: Step 1: API gateway receives external requests; Step 2: The request is processed through authentication, authorization, and current limiting; Step 3: The gateway forwards the request to the service module; Step 4: The service module parses the request and determines the service call chain; Step 5: Call the data mapping engine to perform data conversion; Step 6: If protocol conversion is required, call the corresponding protocol conversion; Step 7: Call the target service according to the configured process by calling the execution engine; Step 8: Process the service return results and perform necessary data conversion; Step 9: Push the processed data to the specified destination including message queue, WebSocket, etc. Step 10: Record the complete call process log.

8. A graphical ESB platform data transmission push calling method according to claim 7, characterized in that: In step 7, the execution engine is called, and the specific steps include: S1. Receive service request; S2, parsing request content; S3, execute the service call chain; S4, summarizing the processing results; S5. Return a response.

9. A graphical ESB platform data transmission push calling method according to claim 7, characterized in that: The monitoring and early warning system is used to monitor the entire process from step 1 to step 10. The specific steps are as follows: S1. Each service module records time monitoring indicators through logs; S2. After the alarm is triggered, a notification is sent through the channel mode integrated in the platform. The notification format supports any format such as email, in-site message, etc.

10. A graphical ESB platform data transmission push calling method according to claim 7, characterized in that: During steps 1 to 10, distributed log collection and analysis are performed using log management using the ELK stack. The specific steps are as follows: S1. Each service module uses log4j2 to output structured logs; S2. Use Filebeat to collect log files of each module; S3, use Logstash to parse and convert logs; S4, the processed logs are stored in Elasticsearch; S5. Perform log retrieval and visual analysis through Kibana.

Images