CN116055355A - Method and system for interface monitoring based on enterprise service bus - Google Patents

Abstract

The present invention provides an interface monitoring method and system based on an enterprise service bus, comprising: step 1: configuring application system interface parameters, and performing connectivity detection on the interface according to the parameter information; step 2: detecting interface transaction messages and business volume Monitor; Step 3: Analyze the message and route and forward the transaction request initiated by the customer. The present invention can provide a configurable solution for application system interface monitoring, monitoring and interface routing under the premise that the overall application system interface call or integration mode remains unchanged, and can configure monitoring and monitoring suitable for business characteristics according to actual business needs Strategies to ensure that the interfaces provided by the application system and the mutual calls between systems run smoothly.

Description

Method and system for interface monitoring based on enterprise service bus

technical field

The invention relates to the technical field of interface monitoring, in particular to an interface monitoring method and system based on an enterprise service bus.

Background technique

The docking between application systems based on enterprise service bus (ESB) integration needs to define, design, and develop interfaces according to requirements, and manage and publish them in ESB, and then verify between docking systems. Calls between systems become safe and orderly. At the same time, it also faces the following problems:

(1) With the increase in the scale of the docking system and the deployment of distributed application systems, the time-consuming process of ESB governance, release, and verification is also increasing, and the governance, release, and deployment of interfaces directly affect the cycle of system launch;

(2) The scale of the application system increases, and the number of external interfaces increases. The availability of the interface and the real-time monitoring of the interface business volume are very important. During the operation of the application system, it is necessary to make preparations for expansion or flow control in advance according to the monitoring indicators, and Respond immediately to alerts;

(3) For the deployment of distributed application systems under the microservice architecture, the interface for providing external services is no longer provided by one or two servers, but in the form of multiple clusters. On the premise of increasing the number of interfaces, meeting the requirements of distributed application deployment is a problem that needs to be considered.

Patent document CN112071408A (application number: CN201910501547.2) discloses a business data monitoring component applied to an enterprise service bus, which includes an enterprise service bus of a hospital information integration platform. The service access port is connected to the service execution agency, and the enterprise service bus also includes a service data monitoring and disposal interface, which is connected to the service access port. Yet this patent can't solve above-mentioned technical problem.

Contents of the invention

Aiming at the defects in the prior art, the object of the present invention is to provide an interface monitoring method and system based on enterprise service bus.

The interface monitoring method based on the enterprise service bus provided by the present invention includes:

Step 1: Configure the interface parameters of the application system, and perform connectivity detection on the interface according to the parameter information;

Step 2: Monitor the interface transaction messages and business volume;

Step 3: Carry out message analysis and route forwarding for the transaction request initiated by the client.

Preferably, said step 1 includes:

Initialize the interface configuration, configure the service set code, sub-service code, interface version number and interface input parameters according to the target interface definition, after completing the initial interface configuration, write the configuration information into the persistence layer for storage, view and modify the saved Interface configuration information;

Select the interface to be detected and initiate a detection, automatically generate an interface request message according to the configuration information of the application system interface, and send a request to the target system interface, and judge the availability of the application system interface by analyzing the return message of the application system; or configure a timing The task monitors the availability of the application system interface according to the preset frequency.

Preferably, said step 2 includes:

By parsing the transaction message, record the transaction serial number, interface service code set, service subcode, request access time, response time and request return code, and save it to the persistence layer;

By analyzing the request message, provide data format or perform parameter conversion to meet the needs of custom request parameters in multi-application system docking;

Real-time presentation of monitoring information by counting transaction requests, response information, and business volume information per unit time;

By configuring alarm rules, the monitoring information is converted into alarm information, displayed on the front end or released to the outside world; blacklist configuration is supported, and transactions in the blacklist will be directly blocked.

Preferably, the step 3 includes: determining the service processing cluster through the interface service set code and sub-service code, if the interface service set code and sub-service code in the request message are not in the configuration list, then directly return the request to the client; if If the interface service set code and sub-service code in the request message are in the configuration list, the request will be forwarded to the corresponding backend service for processing.

Preferably, the request message is analyzed for the interface call application initiated by the client, and the request message is converted into the format required by the application server according to different message formats and request body parameters, and illegal requests are blocked at the same time;

According to the service set code and sub-service code in the request message, the request information is forwarded to the back-end application server for processing. After the back-end application server completes the processing, the response code is recorded in the persistence layer according to the transaction serial number;

Analyze interface request and response information, count and display the request success rate and failure rate of the same interface, and trigger an alarm if the request failure rate exceeds the set threshold.

The interface monitoring system based on the enterprise service bus provided by the present invention includes:

Application interface monitoring module: configure the interface parameters of the application system, and detect the connectivity of the interface according to the parameter information;

Interface business volume monitoring module: monitor interface transaction messages and business volume;

Transaction message forwarding module: perform message analysis and route forwarding for transaction requests initiated by customers.

Preferably, the application interface monitoring module includes:

Initialize the interface configuration, configure the service set code, sub-service code, interface version number and interface input parameters according to the target interface definition, after completing the initial interface configuration, write the configuration information into the persistence layer for storage, view and modify the saved Interface configuration information;

Select the interface to be detected and initiate a detection, automatically generate an interface request message according to the configuration information of the application system interface, and send a request to the target system interface, and judge the availability of the application system interface by analyzing the return message of the application system; or configure a timing The task monitors the availability of the application system interface according to the preset frequency.

Preferably, the interface traffic monitoring module includes:

By parsing the transaction message, record the transaction serial number, interface service code set, service subcode, request access time, response time and request return code, and save it to the persistence layer;

By analyzing the request message, provide data format or perform parameter conversion to meet the needs of custom request parameters in multi-application system docking;

Real-time presentation of monitoring information by counting transaction requests, response information, and business volume information per unit time;

By configuring alarm rules, the monitoring information is converted into alarm information, displayed on the front end or released to the outside world; blacklist configuration is supported, and transactions in the blacklist will be directly blocked.

Preferably, the transaction message forwarding module includes: determining the service processing cluster through the interface service set code and sub-service code, if the interface service set code and sub-service code in the request message are not in the configuration list, then directly return the request to the client If the interface service set code and sub-service code in the request message are in the configuration list, the request will be forwarded to the corresponding back-end service for processing.

Preferably, the interface call application initiated by the client reaches the interface traffic monitoring module through the enterprise service bus, and after analyzing the request message, the request message is converted into the format required by the application server according to different message formats and request body parameters , and block illegal requests at the same time, and then forward legal requests to the transaction message forwarding module, and save the request information;

The transaction message forwarding module forwards the request information to the back-end application server for processing according to the service set code and sub-service code in the request message, and after the back-end application server completes the processing, it records the response code in the persistence layer;

The interface traffic monitoring module analyzes interface request and response information, counts and displays the request success rate and failure rate of the same interface, and triggers an alarm if the request failure rate exceeds a set threshold.

Compared with the prior art, the present invention has the following beneficial effects:

(1) The present invention verifies the usability and connectivity of the interface in advance before the interface is deployed on the production environment for the first time or before the revised production environment goes online, so as to ensure that the interface is ready in the ESB when the back-end application service goes online;

(2) The present invention can real-time monitor the running situation of the interface issued by the application system in the production environment, ensuring the quality of service;

(3) According to the maintenance needs of the application system, the present invention can flexibly configure the server end that provides the interface in the background, and provide a safe and controllable routing scheme in daily operation and maintenance such as gray scale upgrade.

(4) The present invention can provide a configurable solution for application system interface monitoring, monitoring and interface routing under the premise that the overall application system interface call or integration mode remains unchanged, and can be configured according to the actual business needs. Monitoring and monitoring strategies to ensure the smooth operation of the interface provided by the application system and the mutual calls between the systems. In addition, the application of the present invention does not need to be strongly coupled with the application system, and it can be flexibly configured according to the needs of the application system and has strong scalability. features.

Description of drawings

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

Fig. 1 is a flow chart of the method of the present invention;

Fig. 2 is a schematic structural diagram of the system of the present invention.

Detailed ways

The present invention will be described in detail below in conjunction with specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

Example 1:

As shown in Fig. 1, the present invention provides a kind of interface monitoring method based on enterprise service bus, comprising: step 1: configure application system interface parameters, and carry out connectivity detection to interface according to parameter information; Step 2: interface transaction message and The business volume is monitored; Step 3: Carry out message analysis and routing and forwarding of the transaction request initiated by the customer.

The step 1 includes: initializing the interface configuration, configuring the service set code, sub-service code, interface version number and interface input parameters according to the target interface definition, and writing the configuration information into the persistence layer for storage after completing the initializing interface configuration. View and modify the saved interface configuration information; select the interface to be detected and initiate detection, automatically generate an interface request message according to the configuration information of the application system interface, and send a request to the target system interface, and analyze the return message of the application system. Judge the availability of the application system interface; or configure a scheduled task to monitor the availability of the application system interface according to the preset frequency.

Said step 2 includes: by parsing the transaction message, recording the transaction serial number, interface service code set, service subcode, request access time, response time and request return code, and saving it to the persistence layer; by analyzing the request message , to provide data format or parameter conversion to meet the needs of custom request parameters in multi-application system docking; to present monitoring information in real time by counting transaction requests, response information, and business situation information per unit time; by configuring alarm rules , convert the monitoring information into alarm information, display it on the front end or release it to the outside world; support blacklist configuration, and directly block transactions in the blacklist.

The step 3 includes: determining the service processing cluster through the interface service set code and the sub-service code, if the interface service set code and the sub-service code in the request message are not in the configuration list, then directly return the request to the client; if the request message If the interface service set code and sub-service code in the configuration list are in the configuration list, the request will be forwarded to the corresponding backend service for processing.

Analyze the request message for the interface call application initiated by the client, convert the request message into the format required by the application server according to different message formats and request body parameters, and block illegal requests at the same time; according to the service in the request message Set the code and sub-service code, forward the request information to the back-end application server for processing, after the back-end application server completes the processing, record the response code to the persistence layer according to the transaction serial number; analyze the interface request and response information, make statistics and display The request success rate and failure rate of the same interface, if the request failure rate exceeds the set threshold, an alarm will be triggered.

Example 2:

The present invention also provides an interface monitoring system based on the enterprise service bus, the interface monitoring system based on the enterprise service bus can be realized by executing the process steps of the interface monitoring method based on the enterprise service bus, that is, those skilled in the art can The enterprise service bus-based interface monitoring method is understood as a preferred implementation of the enterprise service bus-based interface monitoring system.

The system of the present invention provides interface monitoring, interface service monitoring and interface message forwarding functions, and is deployed between the ESB and the client or target application service. The deployment form and business process are shown in FIG. 1 . The system specifically includes: an application interface monitoring module ESB-TEST, an interface traffic monitoring module ESB-MONITORING and a transaction message forwarding module ESB-GATEWAY.

The application interface monitoring module provides the function of configuring the interface parameters of the application system and initiates connectivity detection on the interface according to the parameter information. First, initialize the interface configuration, and configure the service set code, sub-service code, interface version number, interface input parameters, etc. of the interface according to the definition of the target interface. After the initial configuration is completed, the configuration information is written to the persistence layer for storage. Supports viewing and modifying saved interface configuration parameters. Secondly, select the interface to be detected and initiate the detection, and the application interface monitoring module automatically generates an interface request message according to the configuration parameters of the system interface, and sends the request to the target system interface. The application interface monitoring module judges the usability of the application system interface by analyzing the return message of the application system. The application interface monitoring module also supports the configuration of timing tasks to monitor the availability of the application system interface according to the preset frequency.

The interface traffic monitoring module provides interface transaction message monitoring and traffic monitoring capabilities. The interface traffic monitoring module records the transaction serial number, interface service code set, service subcode, request access time, response time, request return code, etc. by analyzing the transaction message, and saves it in the persistence layer. At the same time, the interface traffic monitoring module provides the ability to convert data formats or parameters by analyzing request messages, so as to solve the need for custom request parameters in multi-system docking. The interface business volume monitoring module presents monitoring information in real time by counting transaction requests, response information, business situation volume information per unit time, etc. The interface traffic monitoring module supports converting monitoring information into alarm information by configuring alarm rules. The alarm information can be directly displayed on the front end of the interface traffic monitoring module or released externally for centralized monitoring. In addition, the interface traffic monitoring module supports blacklist configuration, and will directly intercept transactions in the blacklist.

The transaction message forwarding module provides transaction request routing and forwarding capabilities, and is implemented based on a configuration method. The transaction message forwarding module supports interface service type, interface service set code, sub-service code and service processing cluster address. The transaction message forwarding module uniquely determines the service processing cluster through the interface service set code and sub-service code. If the service set code and sub-service code in the request message are not in the configuration list, the transaction message forwarding module directly returns the request to the client; If the service set code and sub-service code in the request message are in the configuration list, the transaction message forwarding module forwards the request to the corresponding backend service for processing.

The application interface monitoring module is used to test the interface published by the target application system on the ESB. If the test result finds that the call to the target application system interface fails, it can help the relevant system maintenance personnel to locate the problem.

The interface traffic monitoring module and the transaction message forwarding module are applicable to the scenario where the application system serves as the server and provides an interface through the ESB for other systems or clients to call. The interface call application initiated by the client reaches the interface traffic monitoring module of the interface monitoring tool through the ESB. The interface traffic monitoring module analyzes the request message and converts the request message into the application server according to different message formats and request body parameters. The required format improves the adaptability of the interface. At the same time, intercept illegal requests, then forward legal requests to the transaction message forwarding module, and save the request information.

The transaction message forwarding module forwards the request to the back-end application server for processing according to the service set code and sub-service code in the request message. After the backend application completes the processing, it records the response code to the persistence layer according to the transaction serial number.

The interface traffic monitoring module analyzes interface request and response information, supports statistics and displays the request success rate and failure rate of the same interface, and will trigger an alarm if the request failure rate exceeds a set threshold.

Those skilled in the art know that, in addition to realizing the system, device and each module thereof provided by the present invention in a purely computer-readable program code mode, the system, device and each module thereof provided by the present invention can be completely programmed by logically programming the method steps. The same program is implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers, among others. Therefore, the system, device and each module provided by the present invention can be regarded as a hardware component, and the modules included in it for realizing various programs can also be regarded as the structure in the hardware component; A module for realizing various functions can be regarded as either a software program realizing a method or a structure within a hardware component.

Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art may make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. In the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims (10)

1. An interface monitoring method based on an enterprise service bus, comprising the following steps:

step 1: configuring interface parameters of an application system, and detecting connectivity of the interface according to parameter information;

step 2: monitoring interface transaction messages and traffic;

step 3: and carrying out message analysis and route forwarding on the transaction request initiated by the client.

2. The method for monitoring an interface based on an enterprise service bus according to claim 1, wherein the step 1 comprises:

initializing interface configuration, namely writing configuration information into a persistence layer for storage after completing the initialization interface configuration according to service set codes, sub-service codes, interface version numbers and interface input parameters of a target interface definition configuration interface, and checking and modifying the stored interface configuration information;

selecting an interface to be detected, initiating detection, automatically generating an interface request message according to configuration information of an application system interface, sending a request to a target system interface, and judging the availability of the application system interface by analyzing a returned message of an application system; or configuring a timing task, and monitoring the availability of the application system interface according to a preset frequency.

3. The method for monitoring an interface based on an enterprise service bus according to claim 1, wherein the step 2 comprises:

recording a transaction serial number, an interface service code set, a service subcode, a request access time, a response time and a request return code by analyzing the transaction message, and storing the transaction serial number, the interface service code set, the service subcode, the request access time, the response time and the request return code in a persistence layer;

the request message is analyzed to provide a data format or perform parameter conversion so as to meet the requirement of the user-defined request parameters in the multi-application system docking;

the monitoring information is presented in real time by counting transaction requests, response information and business condition information in unit time;

the monitoring information is converted into alarm information through configuration of alarm rules, and the alarm information is displayed at the front end or is released outwards; the blacklist configuration is supported and transactions within the blacklist will be intercepted directly.

4. The method for monitoring an interface based on an enterprise service bus according to claim 1, wherein the step 3 comprises: determining a service processing cluster through the interface service set codes and the sub-service codes, and if the interface service set codes and the sub-service codes in the request message are not in the configuration list, directly returning the request to the client; if the interface service set code and the sub-service code in the request message are in the configuration list, the request is forwarded to the corresponding back-end service processing.

5. The interface monitoring method based on the enterprise service bus according to claim 1, wherein the interface calling application initiated at the client is analyzed to convert the request message into a format required by the application server according to different message formats and request body parameters, and an illegal request is blocked;

according to the service set codes and the sub-service codes in the request message, forwarding the request information to a back-end application server for processing, and after the back-end application server finishes processing, recording a response code to a persistence layer according to the transaction serial number;

analyzing interface request and response information, counting and displaying the request success rate and failure rate of the same interface, and triggering an alarm if the request failure rate exceeds a set threshold value.

6. An interface monitoring system based on an enterprise service bus, comprising:

an application interface monitoring module: configuring interface parameters of an application system, and detecting connectivity of the interface according to parameter information;

interface traffic monitoring module: monitoring interface transaction messages and traffic;

a transaction message forwarding module: and carrying out message analysis and route forwarding on the transaction request initiated by the client.

7. The enterprise service bus-based interface monitoring system of claim 6, wherein the application interface monitoring module comprises:

initializing interface configuration, namely writing configuration information into a persistence layer for storage after completing the initialization interface configuration according to service set codes, sub-service codes, interface version numbers and interface input parameters of a target interface definition configuration interface, and checking and modifying the stored interface configuration information;

selecting an interface to be detected, initiating detection, automatically generating an interface request message according to configuration information of an application system interface, sending a request to a target system interface, and judging the availability of the application system interface by analyzing a returned message of an application system; or configuring a timing task, and monitoring the availability of the application system interface according to a preset frequency.

8. The enterprise service bus-based interface monitoring system of claim 6, wherein the interface traffic monitoring module comprises:

recording a transaction serial number, an interface service code set, a service subcode, a request access time, a response time and a request return code by analyzing the transaction message, and storing the transaction serial number, the interface service code set, the service subcode, the request access time, the response time and the request return code in a persistence layer;

the request message is analyzed to provide a data format or perform parameter conversion so as to meet the requirement of the user-defined request parameters in the multi-application system docking;

the monitoring information is presented in real time by counting transaction requests, response information and business condition information in unit time;

the monitoring information is converted into alarm information through configuration of alarm rules, and the alarm information is displayed at the front end or is released outwards; the blacklist configuration is supported and transactions within the blacklist will be intercepted directly.

9. The enterprise service bus-based interface monitoring system of claim 6, wherein the transaction message forwarding module comprises: determining a service processing cluster through the interface service set codes and the sub-service codes, and if the interface service set codes and the sub-service codes in the request message are not in the configuration list, directly returning the request to the client; if the interface service set code and the sub-service code in the request message are in the configuration list, the request is forwarded to the corresponding back-end service processing.

10. The interface monitoring system based on the enterprise service bus according to claim 6, wherein the interface call application initiated by the client arrives at the interface traffic monitoring module through the enterprise service bus, the request message is converted into the format required by the application server according to different message formats and request body parameters through request message analysis, illegal requests are blocked at the same time, and then legal requests are forwarded to the transaction message forwarding module, and request information is stored;

the transaction message forwarding module forwards the request information to a back-end application server for processing according to the service set codes and the sub-service codes in the request message, and the back-end application server records the response code to the persistence layer according to the transaction serial number after finishing processing;

the interface traffic monitoring module analyzes interface request and response information, counts and displays the request success rate and failure rate of the same interface, and triggers an alarm if the request failure rate exceeds a set threshold.

Images