CN118282998A - Message middleware operation and maintenance method and device and communication system - Google Patents
Message middleware operation and maintenance method and device and communication system Download PDFInfo
- Publication number
- CN118282998A CN118282998A CN202410376839.9A CN202410376839A CN118282998A CN 118282998 A CN118282998 A CN 118282998A CN 202410376839 A CN202410376839 A CN 202410376839A CN 118282998 A CN118282998 A CN 118282998A
- Authority
- CN
- China
- Prior art keywords
- information
- message middleware
- message
- queue
- application system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 82
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000004891 communication Methods 0.000 title claims abstract description 20
- 238000012544 monitoring process Methods 0.000 claims abstract description 83
- 230000002159 abnormal effect Effects 0.000 claims abstract description 62
- 230000005540 biological transmission Effects 0.000 claims abstract description 11
- 238000012545 processing Methods 0.000 claims description 45
- 238000004458 analytical method Methods 0.000 claims description 35
- 230000008030 elimination Effects 0.000 claims description 2
- 238000003379 elimination reaction Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 29
- 230000006870 function Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 239000003795 chemical substances by application Substances 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 229940108461 rennet Drugs 0.000 description 1
- 108010058314 rennet Proteins 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application provides a message middleware operation and maintenance method, a device and a communication system, wherein the message middleware is arranged between a first application system and a second application system, a proxy service module is arranged between the message middleware and the first application system, the proxy service module is used for realizing message transmission between the message middleware and the first application system, the proxy service module can monitor the message middleware to obtain monitoring information, the monitoring information can comprise at least one of queue manager information, queue channel information, queue information and abnormal log information, if the abnormal information exists in the monitoring information based on a preset early warning rule, warning information is generated, and the warning information is sent to a warning unit, so that multidimensional monitoring and automatic warning of the message middleware are realized from the aspects of the state and the application log of the message middleware, effective risk management and control of the message middleware are realized, and the usability and operation and maintenance efficiency between the application and the message middleware are improved.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a method and apparatus for operating and maintaining a message middleware, and a communication system.
Background
Message middleware is used to ensure messaging between heterogeneous applications, typically connected between a first application system and a second application system, for enabling messaging between the first application system and the second application system. The Message middleware can be, for example, a Message Queue (MQ), for example, IBM MQ/TongLINKQ/rabitmq, etc., and in the financial field, the Message middleware has become a tie between each bank system and interconnection and interworking with external channels, so that ensuring safe, reliable and stable operation based on the Message middleware has become an important guarantee and premise for developing each banking service.
As outsourcing software, the functions of monitoring, early warning, analysis, emergency treatment and the like of the message middleware are currently realized by each system through additional operation and maintenance codes, the operation and maintenance codes and application codes are coupled together, the later maintenance cost is high, the application methods are thousands of and strange, the unified standard is lacking, the functions are not effectively integrated into an operation and maintenance system of the self-service system, and effective risk management and control are difficult.
Disclosure of Invention
Therefore, the application aims to provide a message middleware operation and maintenance method, a message middleware operation and maintenance device and a communication system, which realize the operation and maintenance of the message middleware through a proxy service module, decouple operation and maintenance codes and application codes and reduce maintenance cost. The specific scheme is as follows:
In a first aspect, the present application provides a method for operating and maintaining a message middleware, where the message middleware is disposed between a first application system and a second application system, and a proxy service module is disposed between the message middleware and the first application system, and the proxy service module is used to implement message transfer between the message middleware and the first application system, and the method is applied to the proxy service module, and includes:
Monitoring the message middleware to obtain monitoring information, wherein the monitoring information comprises at least one of queue manager information, queue channel information, queue information and abnormal log information;
if abnormal information exists in the monitoring information based on a preset early warning rule, early warning information is generated;
and sending the early warning information to an early warning unit.
Optionally, the method further comprises:
generating operation and maintenance analysis information according to at least one of the monitoring information and the alarm information;
and sending the operation and maintenance analysis information to display equipment.
Optionally, the method further comprises:
Based on an automatic processing rule, the state of the message middleware is controlled according to the abnormal information, and/or fault elimination is carried out according to the abnormal information.
Optionally, the queue manager information includes at least one of a connection number and status information of the queue manager, the queue information includes a queue depth and a message processing time, and the exception log information includes summary information of the exception log.
Optionally, message transmission is realized between the proxy service module and the first application system through a local message queue.
In a second aspect, an embodiment of the present application further provides a message middleware operation and maintenance device, where the message middleware is disposed between a first application system and a second application system, and a proxy service module is disposed between the message middleware and the first application system, where the proxy service module is used to implement message transfer between the message middleware and the first application system, and the device is applied to the proxy service module, and includes:
The monitoring service unit is used for monitoring the message middleware to obtain monitoring information, wherein the monitoring information comprises at least one of queue manager information, queue channel information, queue information and abnormal log information;
The early warning service unit is used for generating early warning information if abnormal information exists in the monitoring information based on a preset early warning rule;
and the early warning sending unit is used for sending the early warning information to the early warning unit.
Optionally, the apparatus further includes:
The operation and maintenance analysis service unit is used for generating operation and maintenance analysis information according to at least one of the monitoring information and the alarm information;
And the operation and maintenance analysis sending unit is used for sending the operation and maintenance analysis information to the display equipment.
Optionally, the apparatus further includes:
and the scene processing service unit is used for controlling the state of the message middleware according to the abnormal information based on an automatic processing rule and/or performing fault removal according to the abnormal information.
Optionally, the queue manager information includes at least one of a connection number and status information of the queue manager, the queue information includes a queue depth and a message processing time, and the exception log information includes summary information of the exception log.
Optionally, message transmission is realized between the proxy service module and the first application system through a local message queue.
In a third aspect, an embodiment of the present application further provides a communication system, including:
A first application system;
A second application system;
Message middleware arranged between the first application system and the second application system;
The proxy service module is arranged between the message middleware and the first application system, and is used for realizing message transmission between the message middleware and the first application system, and executing the method.
The embodiment of the application provides a message middleware operation and maintenance method, a device and a communication system, wherein the message middleware is arranged between a first application system and a second application system, a proxy service module is arranged between the message middleware and the first application system and is used for realizing message transmission between the message middleware and the first application system, the proxy service module can monitor the message middleware to obtain monitoring information, the monitoring information can comprise at least one of queue manager information, queue channel information, queue information and abnormal log information, if the abnormal information exists in the monitoring information based on a preset early warning rule, alarm information is generated, and the alarm information is sent to an early warning unit. In addition, the proxy service module realizes the butt joint and operation and maintenance of the application system and the message middleware, decouples the operation and maintenance monitoring of the application system and the message middleware, promotes the integration of an operation and maintenance system, provides uniform general operation and maintenance service, effectively improves the usability and operation and maintenance efficiency between the application and the message middleware, and has higher demonstration effect and popularization value for the scene based on the message middleware communication.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are some embodiments of the application and that other drawings may be obtained from these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;
Fig. 2 is a schematic structural diagram of another communication system according to an embodiment of the present application;
FIG. 3 is a functional schematic of a proxy service module according to an embodiment of the present application;
Fig. 4 is a schematic flow chart of a message middleware operation and maintenance method according to an embodiment of the present application;
fig. 5 is a schematic diagram of monitoring a message middleware according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an early warning process according to an embodiment of the present application;
fig. 7 is a schematic diagram of an application anomaly early warning process according to an embodiment of the present application;
FIGS. 8-11 are diagrams illustrating various operation and maintenance analyses according to embodiments of the present application;
FIG. 12 is a schematic illustration of an automated process in accordance with an embodiment of the present application;
FIG. 13 is a schematic diagram of another automated process in accordance with an embodiment of the present application;
FIG. 14 is a schematic illustration of a manual process according to an embodiment of the present application;
Fig. 15 is a block diagram of a message middleware operation and maintenance device according to an embodiment of the present application;
fig. 16 is a block diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order that the above objects, features and advantages of the application will be readily understood, a more particular description of the application will be rendered by reference to the appended drawings.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application, but the present application may be practiced in other ways other than those described herein, and persons skilled in the art will readily appreciate that the present application is not limited to the specific embodiments disclosed below.
For easy understanding, the following describes in detail a message middleware operation and maintenance method, device and communication system provided in the embodiments of the present application with reference to the accompanying drawings.
Referring to fig. 1, a schematic structural diagram of a communication system according to an embodiment of the present application may be provided in an application server, where the communication system is used to support the server to provide corresponding application services, and the communication system includes a first application system 400 and a second application system 100, and a message middleware 200 between the first application system 400 and the second application system 100. The first application system 400 and the second application system 100 may be heterogeneous application systems, and the message middleware 200 may be, for example, a Message Queue (MQ), such as IBM MQ/TongLINKQ/rabitmq, etc.
Messages are information carriers passed between applications, MQ may include Message Queue (MQ) servers, message Queue (MQ) channels, and MQ queues (referred to as QLs), where MQ managers are responsible for providing message services to applications, are message queue managers for maintaining and managing message queues, MQ channels are a unidirectional point-to-point communication connection between two queue managers, messages can only flow in a single way in MQ channels, MQ queues are similar to message containers for depositing messages.
In the embodiment of the present application, a proxy service module 300 may be disposed between the first application system 400 and the message middleware 200, where the proxy service module 300 may exist as hardware for providing proxy service, or may exist as a functional module for providing proxy service, and the proxy service module 300 may implement message passing between the message middleware 200 and the first application system 400, that is, provide a service for sending and receiving a message.
Referring to fig. 2, a schematic structural diagram of another communication system according to an embodiment of the present application is provided, where the first application system 400 may be a server cluster application system, for example, the first application system 400 may include at least one of an MQ outbound service in a global banking and finance telecommunications association (SWIFT) service, an MQ outbound service in a rennet cross-border payment system (CIPS) service, and an MQ outbound service in a foreign currency payment system (CFXPS) service.
The second application system 100 may be an application cluster front end that interacts with the first application system 400 for connection with external channels (e.g., switch/CIPS/CFXPS/large/small/super networks, etc.) when the first application system 400 is an MQ outbound service in a switch service, the second application system 100 may be an application connected to switch, when the first application system 400 is an MQ outbound service in a CIPS service, the second application system 100 may be an application connected to CIPS (i.e., application a and application B), when the first application system 400 is an MQ outbound service in a CFXPS service, the second application system 100 may be an application connected to CFXPS (i.e., application C and application D).
Message middleware 200 is a message queue that connects first application system 400 and second application system 100, and the message queue may be disposed in an application front end processor, where multiple message queues may communicate through a high availability architecture (HA), such as MQ in a SWIFT service, and MQ1 and MQ2 between an application connected to the SWIFT service, where the two may communicate through the HA.
The proxy service module 300 acts as a proxy layer, and a local message queue may be further deployed in the queue manager of the proxy service module 300, and communication may be performed between the proxy service module 300 and the first application system 400 through the local Message Queue (MQ).
Referring to fig. 3, a functional schematic diagram of a proxy service module according to an embodiment of the present application implements a non-invasive message middleware integrated operation and maintenance scheme. The proxy service module may also perform the operation and maintenance operation of the message middleware through an independent process, i.e. the proxy service may include the operation and maintenance operation. Specifically, referring to fig. 2 and fig. 3, the proxy service module may further monitor the message middleware to obtain monitoring information, that is, may provide a monitoring service; the agent service module can also generate early warning information according to the monitoring information, namely early warning service can be provided; the agent service module can also generate operation and maintenance analysis information according to at least one of the monitoring information and the monitoring information, namely, operation and maintenance analysis service can be provided; the proxy service module can also perform scene processing under abnormal scenes based on automatic processing rules, namely can provide scene processing services, and the scene processing can control the state of message middleware and/or perform fault removal according to abnormal information.
The function of the proxy service module is described in detail in the form of a method. Referring to fig. 4, a flow chart of a message middleware operation and maintenance method according to an embodiment of the present application is shown, where the method is applied to a proxy service module, and may include the following steps.
S101, monitoring the message middleware to obtain monitoring information.
In the embodiment of the present application, referring to fig. 3, the monitoring information may include at least one of MQ-level information and application-level information, where the MQ-level information may include at least one of queue manager information, queue channel information, queue information, and other information of multiple dimensions, the application-level information includes abnormal log information, that is, the monitoring information includes at least one of queue manager information, queue channel information, queue information, and abnormal log information, where the queue manager information includes at least one of a connection number and status information of the queue manager, the queue channel information includes status information of the queue channel, a channel number, and the like, the queue information includes status information of the queue, a queue depth, a message processing time, and the like, and the abnormal log information includes summary information of the abnormal log.
The number of connections of the queue manager is the number of handles connected with the MQ, each MQ has a default upper limit of the number of connections, the actual number of connections exceeds the upper limit of the number of connections to be in an abnormal state, the depth of the MQ queue is the number of messages already piled up by the queue, and the abnormal log can comprise a message sending failure log, a format verification failure log, repeated records and the like.
Referring to fig. 5, a monitoring schematic diagram of a message middleware according to an embodiment of the present application is shown, where a monitoring service in a proxy service module monitors MQ1 and MQ2, and monitors to obtain monitoring information such as status information of an MQ manager, a connection number of the MQ queue manager (denoted as an MQ connection number), an MQ channel number, status information of an MQ queue, an MQ queue depth, and an MQ queue message processing time. Where T is a message processing time, which may include a total time of queue message processing and/or a processing time of each message, etc. The processing time of each message can be determined according to the storing time and the fetching time of the message.
The monitoring information may be recorded in an MQ information list, addresses in the MQ information list are used to identify queues, and the manager, the channel and the queues respectively represent state information thereof, and the available state is an MQ available state determined according to the state of the manager, the state of the channel and the state of the queues. The monitoring service in the proxy service module records the monitoring information into the MQ information table, and the early warning service judges whether to trigger an alarm or not according to the monitoring data in the table.
S102, if abnormal information exists in the monitoring information based on a preset early warning rule, early warning information is generated.
S103, sending early warning information to an early warning unit.
The preset early warning rule can support availability early warning, threshold early warning, application abnormality early warning and the like of the message middleware, and when the monitoring information is matched with the preset early warning rule, the monitoring information is determined to be abnormal information, the early warning information can be generated according to the abnormal information so as to inform operation and maintenance personnel. The preset early warning rule is an early warning rule preset by an operation and maintenance person, and referring to fig. 6, an early warning process schematic diagram provided by the embodiment of the application is shown, wherein the early warning rule can include an MQ availability rule, a queue depth and the like.
The availability pre-warning can be implemented according to the manager availability state, the channel availability state and the like, the preset pre-warning rule can comprise a corresponding MQ availability rule, and when the monitoring information is matched with the MQ availability rule, the monitoring information is confirmed to be abnormal information, for example, when the state information of the queue manager is unavailable or the state information of the queue channel is unavailable, the state information of the queue manager or the state information of the queue channel is confirmed to be abnormal information.
The threshold early warning may be implemented according to a queue depth, a message processing time, a connection number, and the like, and the preset early warning rule may include a corresponding threshold rule, and when the monitoring information matches the threshold rule, the monitoring information is confirmed to be abnormal information, for example, when the queue depth exceeds the threshold, the message processing time exceeds the threshold, or the connection number exceeds the threshold, the queue depth, the message processing time, or the connection number is determined to be abnormal information. The message processing time can be determined according to the message time difference, which refers to the time difference between the message storing and the message retrieving.
The application of the abnormal early warning can be realized according to abnormal log information and the like, the preset early warning rule can comprise a corresponding log rule, when the monitoring information is matched with the log rule, the monitoring information is confirmed to be abnormal information, for example, keywords of abstract information of the abnormal log are matched with the abnormal words in the log rule, and the abstract information of the abnormal log is confirmed to be abnormal information.
The early warning information can be generated according to the abnormal information, and the early warning information is used for reflecting the abnormal information, so that the operation and maintenance personnel can perform fault removal according to the early warning information after acquiring the early warning information.
Referring to fig. 7, a schematic diagram of an application anomaly early warning process according to an embodiment of the present application is shown, where a monitoring service of a proxy service module may perform log monitoring according to log scanning rule setting information, where the log scanning rule may include a path name, a keyword, and the like, and the log scanning rule is preset by a staff. Under the application abnormal scene, an abnormal log can be generated, the application abnormal scene can comprise message sending failure, message format verification failure, repeated record and the like, the generated abnormal log can comprise MQ information, verification failure information, repeated record identification and the like, abstract information of the abnormal log can be obtained based on the abnormal log, early warning service in the agent service module can perform early warning monitoring based on early warning rule setting information, and when the abstract information of the abnormal log is matched with a log rule, the abnormal information is confirmed and early warning information is generated.
And then, the early warning information can be sent to an early warning unit, and the early warning unit can be a display unit or other early warning equipment.
In the embodiment of the application, the operation and maintenance analysis information can be generated according to at least one of the monitoring information and the alarm information, and the operation and maintenance analysis information can be sent to the display equipment, wherein the operation and maintenance analysis information can comprise a manager state diagram, a manager connection number diagram, a channel state diagram, a queue depth information diagram, a queue message time difference diagram, log abnormal summary information and the like. When the monitoring information comprises information of an MQ layer and information of an application layer, the monitoring information and log information of the message middleware can be effectively fused through operation and maintenance analysis service, and multidimensional information analysis display is provided, so that operation and maintenance personnel can conduct analysis and judgment according to the displayed operation and maintenance analysis information.
Referring to fig. 8-11, which are schematic diagrams illustrating various operation and maintenance analysis in an embodiment of the present application, fig. 8 shows a schematic diagram of a MQ manager state, fig. 9 shows a schematic diagram of a channel state, a queue depth, a queue message processing time, and a queue message processing time, respectively, in different time periods, fig. 10 shows a schematic diagram of a queue message processing time, respectively.
In the embodiment of the application, the automatic processing rule can be set, so that the early warning event is processed according to the automatic processing rule. Specifically, the state of the message middleware may be controlled according to the anomaly information based on the automatic processing rule, and/or the fault removal may be performed according to the anomaly information. That is, for abnormal scenarios, the proxy service module may provide a switch control service for controlling the status of the message middleware, or may provide an automatic processing service for automatically performing troubleshooting. Of course, the proxy service module may not provide service, and may be manually processed by the operation and maintenance personnel.
Referring to fig. 12, which is a schematic diagram of an automatic processing procedure in an embodiment of the present application, a monitoring service monitors to obtain monitoring information and records available message middleware into an MQ available list according to a status of the message middleware, and a switch control service in a proxy service module may automatically close unavailable message middleware according to a configuration rule, where a unit with "x" and a channel are unavailable. Of course, the early warning service can also generate early warning information to inform operation and maintenance personnel to process.
Referring to fig. 13, a schematic diagram of another automatic processing procedure in an embodiment of the present application is shown, where a monitoring service monitors and obtains monitoring information and records the monitoring information in an MQ information list, and performs early warning discrimination and generates early warning information according to abnormal information in the monitoring information, and an automatic processing unit may perform fault removal according to the abnormal information according to a preset automatic processing rule, for example, take out a blocked message 1 so that a message 2 may be processed. The fetched message 1 may be rejoined in other locations of the queue or backed up for later retrieval.
Referring to fig. 14, a schematic diagram of a manual processing procedure in an embodiment of the present application is shown, where a monitoring service monitors and records monitoring information in an MQ information list, early warning information may be generated according to abnormal information in the monitoring information, an operation and maintenance analysis service may generate operation and maintenance analysis information, and an operation and maintenance person may perform troubleshooting according to at least one of the operation and maintenance analysis information and the early warning information, for example, take out a blocked message 1 so that a message 2 may be processed.
That is, in the embodiment of the application, the message middleware can be monitored, early warning information can be automatically generated, operation and maintenance analysis information can be generated, and fault removal or closing of the message middleware can be automatically performed. Through comprehensive operation and maintenance analysis service, message middleware monitoring information and application logs are effectively fused, multi-bit analysis display is provided, and misjudgment of event processing is reduced; manual and automatic processing is supported through the multi-scene processing function. Through operation and maintenance analysis display and scene processing functions, the flexibility of system processing is greatly improved.
The embodiment of the application provides a message middleware operation and maintenance method, wherein a message middleware is arranged between a first application system and a second application system, a proxy service module is arranged between the message middleware and the first application system, the proxy service module is used for realizing message transmission between the message middleware and the first application system, the proxy service module can monitor the message middleware to obtain monitoring information, the monitoring information can comprise at least one of queue manager information, queue channel information, queue information and abnormal log information, if the abnormal information exists in the monitoring information based on a preset early warning rule, warning information is generated, and the warning information is sent to a warning unit, so that multidimensional monitoring and automatic warning of the message middleware are realized from the aspects of the state and the application log of the message middleware, the blank of the operation and maintenance scene of the message middleware is filled, and effective risk management and control of the message middleware is realized. In addition, the proxy service module realizes the butt joint and operation and maintenance of the application system and the message middleware, decouples the operation and maintenance monitoring of the application system and the message middleware, promotes the integration of an operation and maintenance system, provides uniform general operation and maintenance service, effectively improves the usability and operation and maintenance efficiency between the application and the message middleware, and has higher demonstration effect and popularization value for the scene based on the message middleware communication.
Based on the above message middleware operation and maintenance method, the embodiment of the application also provides a message middleware operation and maintenance device, which is arranged in the proxy service module and is used for executing the message middleware operation and maintenance method, wherein the message middleware is arranged between a first application system and a second application system, a proxy service module is arranged between the message middleware and the first application system, and the proxy service module is used for realizing message transmission between the message middleware and the first application system. Referring to fig. 15, a block diagram of a message middleware operation and maintenance device according to an embodiment of the present application may include:
A monitoring service unit 110, configured to monitor the message middleware to obtain monitoring information, where the monitoring information includes at least one of queue manager information, queue channel information, queue information and exception log information;
The early warning service unit 120 is configured to generate early warning information if it is determined that abnormal information exists in the monitoring information based on a preset early warning rule;
And the early warning sending unit 130 is used for sending the early warning information to the early warning unit.
Optionally, the apparatus further includes:
The operation and maintenance analysis service unit is used for generating operation and maintenance analysis information according to at least one of the monitoring information and the alarm information;
And the operation and maintenance analysis sending unit is used for sending the operation and maintenance analysis information to the display equipment.
Optionally, the apparatus further includes:
and the scene processing service unit is used for controlling the state of the message middleware according to the abnormal information based on an automatic processing rule and/or performing fault removal according to the abnormal information.
Optionally, the queue manager information includes at least one of a connection number and status information of the queue manager, the queue information includes a queue depth and a message processing time, and the exception log information includes summary information of the exception log.
Optionally, message transmission is realized between the proxy service module and the first application system through a local message queue.
In yet another aspect, an embodiment of the present application provides a communication system, including:
A first application system;
A second application system;
Message middleware arranged between the first application system and the second application system;
The proxy service module is arranged between the message middleware and the first application system, and is used for realizing message transmission between the message middleware and the first application system, and executing the method.
In yet another aspect, an embodiment of the present application provides a computer device, referring to fig. 16, which shows a structural diagram of the computer device provided in the embodiment of the present application, as shown in fig. 16, where the device includes a processor 310 and a memory 320:
The memory 310 is used for storing program codes and transmitting the program codes to the processor;
the processor 320 is configured to execute the message middleware operation and maintenance method provided in the foregoing embodiment according to an instruction in the program code.
The computer device may comprise a terminal device or a server, and the aforementioned message middleware operations and maintenance means may be configured in the computer device.
In yet another aspect, an embodiment of the present application further provides a storage medium, where the storage medium is used to store a computer program, where the computer program is used to execute the message middleware operation and maintenance method provided in the foregoing embodiment.
In addition, the embodiment of the application also provides a computer program product comprising instructions, which when run on a computer, cause the computer to execute the message middleware operation and maintenance method provided by the embodiment.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by program instruction hardware, and the above program may be stored in a computer readable storage medium, where the program when executed performs steps including the above method embodiments; and the aforementioned storage medium may be at least one of the following media: read-only Memory (ROM), RAM, magnetic disk or optical disk, etc.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.
The foregoing is merely a preferred embodiment of the present application, and the present application has been disclosed in the above description of the preferred embodiment, but is not limited thereto. Any person skilled in the art can make many possible variations and modifications to the technical solution of the present application or modifications to equivalent embodiments using the methods and technical contents disclosed above, without departing from the scope of the technical solution of the present application. Therefore, any simple modification, equivalent variation and modification of the above embodiments according to the technical substance of the present application still fall within the scope of the technical solution of the present application.
Claims (10)
1. The message middleware operation and maintenance method is characterized in that the message middleware is arranged between a first application system and a second application system, a proxy service module is arranged between the message middleware and the first application system, the proxy service module is used for realizing message transmission between the message middleware and the first application system, and the method is applied to the proxy service module and comprises the following steps:
Monitoring the message middleware to obtain monitoring information, wherein the monitoring information comprises at least one of queue manager information, queue channel information, queue information and abnormal log information;
if abnormal information exists in the monitoring information based on a preset early warning rule, early warning information is generated;
and sending the early warning information to an early warning unit.
2. The method according to claim 1, wherein the method further comprises:
generating operation and maintenance analysis information according to at least one of the monitoring information and the alarm information;
and sending the operation and maintenance analysis information to display equipment.
3. The method according to claim 1, wherein the method further comprises:
Based on an automatic processing rule, the state of the message middleware is controlled according to the abnormal information, and/or fault elimination is carried out according to the abnormal information.
4. A method according to any of claims 1-3, wherein the queue manager information comprises at least one of a connection number and status information of a queue manager, the queue information comprises a queue depth and a message processing time, and the exception log information comprises summary information of an exception log.
5. A method according to any of claims 1-3, characterized in that messaging is effected between the proxy service module and the first application system via a local message queue.
6. The utility model provides a message middleware operation and maintenance device which characterized in that, message middleware sets up between first application system and second application system, message middleware with be provided with the proxy service module between the first application system, the proxy service module is used for realizing message transmission between message middleware and the first application system, the device is applied to the proxy service module includes:
The monitoring service unit is used for monitoring the message middleware to obtain monitoring information, wherein the monitoring information comprises at least one of queue manager information, queue channel information, queue information and abnormal log information;
The early warning service unit is used for generating early warning information if abnormal information exists in the monitoring information based on a preset early warning rule;
and the early warning sending unit is used for sending the early warning information to the early warning unit.
7. The apparatus of claim 6, wherein the apparatus further comprises:
The operation and maintenance analysis service unit is used for generating operation and maintenance analysis information according to at least one of the monitoring information and the alarm information;
And the operation and maintenance analysis sending unit is used for sending the operation and maintenance analysis information to the display equipment.
8. The apparatus of claim 6, wherein the apparatus further comprises:
and the scene processing service unit is used for controlling the state of the message middleware according to the abnormal information based on an automatic processing rule and/or performing fault removal according to the abnormal information.
9. The apparatus of any of claims 6-8, wherein the queue manager information comprises at least one of a connection number and status information of a queue manager, the queue information comprises a queue depth and a message processing time, and the exception log information comprises summary information of an exception log.
10. A communication system, comprising:
A first application system;
A second application system;
Message middleware arranged between the first application system and the second application system;
A proxy service module disposed between the message middleware and the first application system, the proxy service module configured to implement message passing between the message middleware and the first application system, the proxy service module further configured to perform the method of any one of claims 1-5.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410376839.9A CN118282998A (en) | 2024-03-29 | 2024-03-29 | Message middleware operation and maintenance method and device and communication system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410376839.9A CN118282998A (en) | 2024-03-29 | 2024-03-29 | Message middleware operation and maintenance method and device and communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN118282998A true CN118282998A (en) | 2024-07-02 |
Family
ID=91637405
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202410376839.9A Pending CN118282998A (en) | 2024-03-29 | 2024-03-29 | Message middleware operation and maintenance method and device and communication system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN118282998A (en) |
-
2024
- 2024-03-29 CN CN202410376839.9A patent/CN118282998A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110661659B (en) | Alarm method, device and system and electronic equipment | |
US10528405B2 (en) | Methods, apparatus and computer programs for managing persistence | |
US8732516B2 (en) | Method and system for providing customer controlled notifications in a managed network services system | |
US7460654B1 (en) | Processing of enterprise messages integrating voice messaging and data systems | |
US6778644B1 (en) | Integration of voice messaging and data systems | |
CN112911013B (en) | Cloud application processing method and device, computer equipment and storage medium | |
CN107292117B (en) | Processing method and device for quality guarantee of mass shared medical images | |
CN112910733A (en) | Full link monitoring system and method based on big data | |
CN113760634A (en) | Data processing method and device | |
CN101409638A (en) | Method, system and apparatus for warning distributed business system fault | |
CN104734895B (en) | Service monitoring system and business monitoring method | |
CA2736700C (en) | Monitoring a mobile data service associated with a mailbox | |
US6779186B2 (en) | Method for operating and maintenance by base station using remote procedure call in IMT-2000 system | |
CN113193990A (en) | Fault processing method and device | |
CN118282998A (en) | Message middleware operation and maintenance method and device and communication system | |
US20140214969A1 (en) | Managing electronic mail for an end-user that is unavailable | |
CN115250233B (en) | Gray scale routing control method, gray scale routing assembly and computer equipment | |
CN101305389A (en) | Independent message stores and message transport agents | |
CN113157461B (en) | Method and device for transmitting message in task list execution process | |
KR100322910B1 (en) | Method and appratus for banking-network | |
CN114745426A (en) | Method, device and equipment for monitoring abnormity of terminal, readable storage medium and system | |
CN106209502A (en) | system monitoring method, device and server | |
CN117411929B (en) | Business process monitoring method, device, equipment and storage medium | |
CN118260294B (en) | Manufacturing pain signal summarizing method, system, medium and equipment based on AI | |
CN114338688B (en) | Data management method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |