Automatic configuration method for RabbitMq component of message passing scene among multiple systems

Abstract

The invention discloses an automatic configuration method for RabbitMq components of a message transmission scene among multiple systems, which relates to the technical field of automatic configuration and comprises the following steps: a message publisher submits a message publishing statement on a message platform among the multiple systems, performs service matching on the message publishing statement in combination with the actual service requirement of a message subscriber, and if the service matching is successful, the message publisher transmits the message publishing statement to the message subscriber; if service matching fails, submitting a subscription application, and if service matching fails, terminating the subscription process; the message platform combines the message publishing declaration and the subscription application, generates a configuration instruction set by utilizing an automatic decision rule, judges whether the configuration instruction set triggers a resource dynamic self-configuration mechanism or not, and executes resource dynamic self-configuration and verifies a configuration result if the configuration instruction set triggers the resource dynamic self-configuration mechanism; and if not, keeping the current resource configuration state. According to the method, intelligent mapping between service semantics and infrastructures is realized, automatic deployment of publishing and subscribing relationships is supported, and unified and efficient centralized management can be carried out on component configuration.

Description

Technical Field

[0001] This invention relates to the field of automatic configuration technology, and more specifically, to an automatic configuration method for RabbitMQ components in a multi-system message passing scenario. Background Technology

[0002] In the field of distributed system architecture, with the expansion of business scale and the surge in the number of heterogeneous systems (such as microservices, legacy systems, and cloud-native applications), efficient and reliable message passing between systems has become a core requirement for supporting business collaboration and ensuring service quality. Although Service-Oriented Architecture (SOA) achieves basic service interaction through service contracts and quality equivalence principles, under the requirements of high concurrency and multi-scenario message subscription processing, it is urgent to rely on message queue middleware (referred to as "message middleware") to achieve the integration and optimization of distributed systems.

[0003] Message middleware, based on efficient and reliable message passing mechanisms, provides platform-independent data exchange capabilities. Through message passing and message queuing models, it endows distributed systems with key functions such as application decoupling, elastic scaling, redundant storage, traffic shaping, asynchronous communication, and data synchronization, and has become a core component in Internet and enterprise applications. Among them, RabbitMQ (an open-source message-oriented middleware) that follows the AMQP protocol has become the mainstream technology choice for message passing scenarios between heterogeneous systems due to its high concurrency processing capabilities, flexible routing mechanisms, and good decoupling characteristics.

[0004] However, the existing RabbitMQ configuration management method has significant technical shortcomings in complex multi-system interaction scenarios, making it difficult to meet the needs of large-scale operation and maintenance: Configuration relies on manual operation, resulting in low efficiency and reliability: Currently, RabbitMQ configuration needs to be completed through its native management console. When message passing needs to be implemented between multiple systems, each access system needs to independently maintain RabbitMQ connection parameters (such as account and password), queue / exchange declaration information, binding rules, and data serialization strategies. The entire process relies on manual modification of configuration, which is not only inefficient but also prone to errors such as configuration omissions and duplicate configurations, directly affecting the stability of message passing.

[0005] The disconnect between configuration and business attributes leads to high maintenance costs: In the typical scenario of "one system publishing messages and multiple systems subscribing", the RabbitMQ native management console only displays technical configuration information and cannot intuitively associate it with business attributes (such as the business scenario and service affiliation of the message). This requires technical personnel to communicate and confirm the correspondence between configuration and business, which significantly increases learning and communication costs.

[0006] The difficulty of operation and maintenance increases dramatically in large-scale scenarios: When the number of nodes in a distributed system expands to dozens or even hundreds, and the types of message publishing and subscription scenarios increase to thousands or even tens of thousands, the above-mentioned manual and decentralized configuration management mode will lead to an exponential increase in maintenance costs. It cannot adapt to the operation and maintenance needs of large-scale and highly available distributed systems, and becomes a technical bottleneck that restricts the efficient expansion of business.

[0007] No effective solutions have yet been proposed to address the problems in the relevant technologies. Summary of the Invention

[0008] To address the problems in related technologies, this invention proposes an automatic configuration method and system for RabbitMQ components in inter-system message passing scenarios, thereby overcoming the aforementioned technical problems existing in existing related technologies.

[0009] Therefore, the specific technical solution adopted by the present invention is as follows: According to one aspect of the present invention, an automatic configuration method for RabbitMQ components in a multi-system message passing scenario is provided, the method comprising: The message publisher submits a message publication statement on the messaging platform across multiple systems, and performs business matching on the message publication statement based on the actual business needs of the message subscriber. If the business matching is successful, a subscription application is submitted; if the business matching fails, the subscription process is terminated. The messaging platform combines message publishing declarations and subscription requests, uses automated decision rules to generate configuration instruction sets, and determines whether the configuration instruction sets trigger the dynamic resource self-configuration mechanism. If triggered, it executes the dynamic resource self-configuration and verifies the configuration result; if not triggered, it maintains the current resource configuration state.

[0010] Furthermore, the message publisher submits a message publication declaration on the inter-system messaging platform, and performs business matching of the message publication declaration with the actual business needs of the message subscribers. If the business matching is successful, a subscription application is submitted; if the business matching fails, the subscription is terminated. The process includes: Based on a messaging platform across multiple systems, the message publisher enters the messaging platform's messaging page and submits a message publishing statement in a preset format; Message subscribers browse the submitted message publishing statements and perform business matching on the message publishing statements in conjunction with actual business needs to determine whether the message publishing statements meet the actual business needs. If the message release statement meets the actual business needs, the message subscriber will proceed to the subscription application page and submit a subscription application; if the message release statement does not meet the actual business needs, the subscription process will be terminated.

[0011] Furthermore, the message release statement includes: the release system, message type, content description, and sample message.

[0012] Furthermore, the subscription request includes: the subscription system, a description of the requirements, and the target message type.

[0013] Furthermore, the messaging platform combines message publishing declarations and subscription requests, utilizes automated decision rules to generate configuration instruction sets, and determines whether the configuration instruction sets trigger the dynamic resource self-configuration mechanism. If triggered, it executes dynamic resource self-configuration and verifies the configuration result; if not triggered, it maintains the current resource configuration state, including: The messaging platform updates the list data based on the preset list data and the submitted message release statements and subscription requests; By combining the updated list data with automated decision-making rules, a configuration instruction set containing target elements is generated; Based on the message queue middleware's dynamic resource self-configuration mechanism, determine whether the configuration instruction set triggers the dynamic resource self-configuration mechanism; If the configuration instruction set triggers the dynamic resource self-configuration mechanism, then the dynamic resource self-configuration is executed, and the configuration result is verified; if the configuration instruction set does not trigger the dynamic resource self-configuration mechanism, then the current resource configuration state is maintained.

[0014] Furthermore, the target elements include: message publisher, message subscriber, and message type.

[0015] Furthermore, the configuration instruction set includes: In the business scenario, the message publisher system is treated as the message producer. It generates the name of the exchange based on its own business system number and publishes the message publishing declaration to the message queue middleware through the exchange. The message is routed and identified by the routing key. In the business scenario, the message subscriber system is treated as a message consumer. It generates the name of the message queue based on its own business system number and receives messages through the message queue. Treat the business scenario as the message type and identify the route using the routing key.

[0016] Furthermore, dynamic self-configuration of execution resources includes: If the system account in the configuration instruction set does not exist, the message platform will create the corresponding system account according to the preset naming rules based on the identification information of the message publisher and message subscriber, and generate a random password through an encryption algorithm. If the switch in the configuration instruction set does not exist, the message platform creates the switch and configures the lifecycle policy, granting the message publisher write permissions to the switch. If the message queue does not exist in the configuration instruction set, a subscriber queue will be created for the message subscriber, the dead letter queue and time-to-live policy will be configured, and the message subscriber will be granted read permission to the subscriber queue. If the routing key in the configuration instruction set does not exist, a routing key is generated based on the message type. If the binding relationship in the configuration instruction set does not exist, a ternary binding relationship is established between the switch, the routing key, and the subscriber queue, and the binding relationship is persistently stored.

[0017] Further verification of the configuration results includes: The message publisher configures connection information through the software dependency package provided by the messaging platform, instantiates a message entity class based on the connection information, and executes message sending through the message sending technology. If the message is sent successfully, the connectivity verification between the message publisher and the messaging platform is passed; if the message is sent unsuccessfully, the connectivity verification between the message publisher and the messaging platform fails. The message subscriber configures the subscription information through the software dependency package provided by the message platform and establishes a connection between the subscription information and the message queue. If the connection is established successfully, the connectivity verification between the message subscriber and the message platform is passed; if the connection fails to be established, the connectivity verification between the message subscriber and the message platform fails. The messaging platform simulates a message publisher sending a test message. If the message subscriber receives the test message, the connectivity verification of the message link from publisher to subscriber is successful; if the message subscriber does not receive the test message, the connectivity verification of the message link from publisher to subscriber is unsuccessful.

[0018] According to another aspect of the present invention, an automatic configuration system for RabbitMQ components in a multi-system message passing scenario is also provided, the system comprising: The subscription management module is used by message publishers to submit message publishing declarations across multiple systems' message platforms. It also performs business matching on message publishing declarations based on the actual business needs of message subscribers. If the business matching is successful, a subscription application is submitted; if the business matching fails, the subscription process is terminated. The resource configuration module is used by the messaging platform to combine message publishing declarations and subscription requests, generate configuration instruction sets using automated decision rules, and determine whether the configuration instruction set triggers the dynamic resource self-configuration mechanism. If it is triggered, the dynamic resource self-configuration is executed and the configuration result is verified; if it is not triggered, the current resource configuration state is maintained.

[0019] The beneficial effects of this invention are as follows: This invention enables intelligent mapping between business semantics and infrastructure, supports automated deployment of publish and subscribe relationships, and provides unified and efficient centralized management of RabbitMQ configuration. This effectively avoids link failures caused by manual configuration and achieves black-box operation of message middleware configuration. It not only meets the future needs of continuous business development but also sustainably copes with the increasing complexity of inter-system message transmission scenarios, achieving integrity and efficiency in the configuration process. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of an automatic configuration method for RabbitMQ components in a multi-system message passing scenario according to an embodiment of the present invention; Figure 2 This is a block diagram illustrating the principle of an automatic configuration system for RabbitMQ components in a multi-system message passing scenario according to an embodiment of the present invention.

[0022] In the picture: 1. Subscription Management Module; 2. Resource Configuration Module. Detailed Implementation

[0023] To further illustrate the various embodiments, the present invention provides accompanying drawings, which are part of the disclosure of the present invention. These drawings are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these drawings, those skilled in the art should be able to understand other possible implementation methods and the advantages of the present invention.

[0024] According to embodiments of the present invention, an automatic configuration method and system for RabbitMQ components in a multi-system message passing scenario are provided.

[0025] The present invention will now be further described in conjunction with the accompanying drawings and specific embodiments, such as... Figure 1 As shown, an automatic configuration method for RabbitMQ components in a multi-system message passing scenario according to an embodiment of the present invention includes: The message publisher submits a message publication statement on the messaging platform across multiple systems. The message publisher then performs a business matching process based on the actual business needs of the message subscribers. If the business matching is successful, a subscription application is submitted. If the business matching fails, the subscription process is terminated.

[0026] In this optional embodiment, the message publisher submits a message publication declaration on a multi-system messaging platform and performs business matching on the message publication declaration based on the actual business needs of the message subscriber. If the business matching is successful, a subscription application is submitted; if the business matching fails, the subscription process is terminated. Based on the inter-system messaging platform, the message publisher enters the messaging platform's messaging page and submits a message publishing statement according to the preset format.

[0027] In this optional embodiment, the message publishing statement includes: publishing system, message type, content description, and sample message.

[0028] Message subscribers browse the submitted message publishing statements and perform business matching on the message publishing statements in conjunction with actual business needs to determine whether the message publishing statements meet the actual business needs. If the message release statement meets the actual business needs, the message subscriber will proceed to the subscription application page and submit a subscription application; if the message release statement does not meet the actual business needs, the subscription process will be terminated.

[0029] In this optional embodiment, the subscription request includes: a subscription system, a demand description, and a target message type.

[0030] The messaging platform combines message publishing declarations and subscription requests, uses automated decision rules to generate configuration instruction sets, and determines whether the configuration instruction sets trigger the dynamic resource self-configuration mechanism. If triggered, it executes the dynamic resource self-configuration and verifies the configuration result; if not triggered, it maintains the current resource configuration state.

[0031] In this optional embodiment, the messaging platform combines message publishing declarations and subscription requests, uses automated decision rules to generate a configuration instruction set, and determines whether the configuration instruction set triggers a dynamic resource self-configuration mechanism. If triggered, dynamic resource self-configuration is executed and the configuration result is verified; if not triggered, the current resource configuration state is maintained, including: The messaging platform updates the list data based on the preset list data and the submitted message release statements and subscription requests; By combining the updated list data with automated decision-making rules, a set of configuration instructions containing the target elements is generated.

[0032] In this optional embodiment, the target elements include: message publisher, message subscriber, and message type.

[0033] In this optional embodiment, the configuration instruction set includes: In the business scenario, the message publisher system is treated as the message producer. It generates the name of the exchange based on its own business system number and publishes the message publishing declaration to the message queue middleware through the exchange. The message is routed and identified by the routing key. In the business scenario, the message subscriber system is treated as a message consumer. It generates the name of the message queue based on its own business system number and receives messages through the message queue. Treat the business scenario as the message type and identify the route using the routing key.

[0034] Based on the message queue middleware's dynamic resource self-configuration mechanism, determine whether the configuration instruction set triggers the dynamic resource self-configuration mechanism; If the configuration instruction set triggers the dynamic resource self-configuration mechanism, then the dynamic resource self-configuration is executed, and the configuration result is verified; if the configuration instruction set does not trigger the dynamic resource self-configuration mechanism, then the current resource configuration state is maintained.

[0035] In this optional embodiment, dynamic self-configuration of resources includes: If the system account in the configuration instruction set does not exist, the message platform will create the corresponding system account according to the preset naming rules based on the identification information of the message publisher and message subscriber, and generate a random password through an encryption algorithm. If the switch in the configuration instruction set does not exist, the message platform creates the switch and configures the lifecycle policy, granting the message publisher write permissions to the switch. If the message queue does not exist in the configuration instruction set, a subscriber queue will be created for the message subscriber, the dead letter queue and time-to-live policy will be configured, and the message subscriber will be granted read permission to the subscriber queue. If the routing key in the configuration instruction set does not exist, a routing key is generated based on the message type. If the binding relationship in the configuration instruction set does not exist, a ternary binding relationship is established between the switch, the routing key, and the subscriber queue, and the binding relationship is persistently stored.

[0036] In this optional embodiment, verifying the configuration results includes: The message publisher configures connection information through the software dependency package provided by the messaging platform, instantiates a message entity class based on the connection information, and executes message sending through the message sending technology. If the message is sent successfully, the connectivity verification between the message publisher and the messaging platform is passed; if the message is sent unsuccessfully, the connectivity verification between the message publisher and the messaging platform fails. The message subscriber configures the subscription information through the software dependency package provided by the message platform and establishes a connection between the subscription information and the message queue. If the connection is established successfully, the connectivity verification between the message subscriber and the message platform is passed; if the connection fails to be established, the connectivity verification between the message subscriber and the message platform fails. The messaging platform simulates a message publisher sending a test message. If the message subscriber receives the test message, the connectivity verification of the message link from publisher to subscriber is successful; if the message subscriber does not receive the test message, the connectivity verification of the message link from publisher to subscriber is unsuccessful.

[0037] It should be noted that the automatic configuration method for RabbitMQ components in multi-system message passing scenarios specifically includes: 1. Automatic translation of business semantics into resources: Message type → route key mapping: `rkey.<system abbreviation>.<message type>` (e.g., `rkey.order.create`); Queue naming convention: `<subscription system>.queue`, ensuring global uniqueness; Switch naming convention: `exc.<publishing system>.direct`, ensuring global uniqueness.

[0038] 2. Conflict prevention mechanism: For scenarios where multiple systems subscribe to the same message, an independent queue mode is adopted for security isolation purposes. This means that each consumer system has its own independent queue, which can achieve system decoupling and fault isolation when connecting to multiple systems.

[0039] 3. Minimum permission self-adaptive mechanism: Dynamically generate permission rules based on publish / subscribe roles: <publishing system>_producer is only allowed to write to the specified exchange exc.<publishing system>.direct, and <subscribe system>_consumer is only allowed to read from the specified queue <subscribe system>.queue, ensuring that the publisher cannot read any queue (to prevent data snooping) and the subscriber cannot write to the exchange (to prevent message pollution).

[0040] Furthermore, in a specific embodiment, the automatic configuration method for RabbitMQ components in a multi-system message passing scenario includes: Step 1: Business Semantics Declaration (User Interface Layer): 1. Message publisher's actions: The system administrator submits a message release statement on the unified messaging platform, which includes: { "Publishing System": "Order System" "Message Type":"Order Creation Event", "Content Description": "Includes Order ID, User ID, Amount, and Product List", Example message:{"orderId":"202406250001","amount":99.99,"items":["A01","B05"]} }

[0041] 2. Message subscriber operations: The consumer system administrator browses published message types on the platform and matches them to business requirements based on message type name, content description, and sample message. After confirming the requirements, a subscription request is submitted. { "Subscription System":"Inventory System", Requirement Description: "Deduct inventory from order items" Target message type: "Order system: Order creation event" }

[0042] Step Two: Subscription Relationship Verification (Platform Coordination Layer): 1. Platform verification of the legality of publishing / subscribing systems (e.g., whether the system is registered): The platform itself should have a list of legally registered systems. In the application example, the platform is connected to the technology management portal and updates this system list daily by calling the interface at regular intervals. The list data includes the system number and system name. When filling in the publishing / subscribing information, the system is required and can only be selected from the list.

[0043] 2. Automated decision output: Generates a "Configuration Instruction Set" containing the following elements; Publisher: Order System → Switch: exc.order.direct; Subscriber: Inventory system → Queue: inventory.queue; Message type: Order creation event → Routing key: rkey.order.create.

[0044] 3. The automated decision-making rule is as follows: (1) The system number of the publisher generates the name of the switch. For example, the system number of the order is ordered. Add the prefix exc (to indicate the general naming of the switch), add the suffix direct (to indicate the direct connection mode adopted by the platform by default), add a general separator, and the switch name exc.order.direct will be automatically output.

[0045] (2) The subscriber system number generates the queue name, such as the inventory system number inventory, plus the suffix queue (indicating a common name for the queue), plus a separator, and the queue name inventory.queue is automatically output.

[0046] (3) The message type number generates the name of the routing key. For example, the business number of creating an order is create. The prefix will contain rkey (which represents the general name of the routing key). Add the system number of the message publisher, order, and add a separator to automatically output the routing key name rkey.order.create.

[0047] Step 3: Dynamic self-configuration of RabbitMQ resources (execution engine layer): The execution engine triggers the following atomic operations in sequence (without manual intervention), as shown in Table 1.

[0048] Table 1: Dynamic Resource Allocation Table Step 4: Configuration activation and verification: 1. Configure the connection information (including switch address, username, and password) and verify connectivity in the publisher's system: The publishing system uses the JAR package provided by the platform to configure the connection parameters in its own system: switch name, connection platform IP address, producer account, password (see step 3 for an example), instantiates a message entity class, and calls the sendMessage method. If the message is sent successfully, the connectivity is verified successfully.

[0049] 2. The subscriber system configures consumption information (including queue address, account, and password) and verifies connectivity: The consumer system uses the JAR package provided by the platform to configure the connection parameters in its own system: queue name, connection platform IP address, consumer account, and password (see step 3 for an example). When it starts its own service, it will establish a long connection with the message queue. If the connection is established successfully, the verification is successful.

[0050] 3. The platform sends a test message to verify link connectivity: If the consumer successfully receives the correct message, the connection is verified as successful, either by the producer sending a message or by simulating a producer sending a test message on the platform.

[0051] like Figure 2 As shown, according to another embodiment of the present invention, an automatic configuration system for RabbitMQ components in a multi-system message passing scenario is also provided, the system comprising: The subscription management module 1 is used by message publishers to submit message publishing declarations across multiple systems and to perform business matching on message publishing declarations based on the actual business needs of message subscribers. If the business matching is successful, a subscription application is submitted; if the business matching fails, the subscription process is terminated. Resource configuration module 2 is used by the message platform to combine message publishing declarations and subscription requests, generate configuration instruction sets using automated decision rules, and determine whether the configuration instruction set triggers the dynamic resource self-configuration mechanism. If it is triggered, the dynamic resource self-configuration is executed and the configuration result is verified; if it is not triggered, the current resource configuration state is maintained.

[0052] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for automatic configuration of RabbitMq components in multi-system message passing scenarios, characterized in that, The method comprises: The message publisher submits a message publishing declaration to a message platform between multiple systems, and matches the message publishing declaration with the actual business needs of the message subscriber. If the business matching is successful, the message publisher submits a subscription application. If the business matching fails, the message publisher terminates the subscription process. The message platform generates a configuration instruction set using automatic decision rules based on the message publishing declaration and the subscription application, and determines whether the configuration instruction set triggers a resource dynamic self-configuration mechanism. If the configuration instruction set triggers the resource dynamic self-configuration mechanism, the message platform executes resource dynamic self-configuration and verifies the configuration result. If the configuration instruction set does not trigger the resource dynamic self-configuration mechanism, the message platform maintains the current resource configuration state.

2. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 1, characterized in that, The message publisher submits a message publishing declaration to a message platform between multiple systems, and matches the message publishing declaration with the actual business needs of the message subscriber. If the business matching is successful, the message publisher submits a subscription application. If the business matching fails, the message publisher terminates the subscription process. Based on the message platform between multiple systems, the message publisher enters a message publishing page of the message platform and submits a message publishing declaration in a preset format. The message subscriber browses the submitted message publishing declaration and matches the message publishing declaration with the actual business needs to determine whether the message publishing declaration meets the actual business needs. If the message publishing declaration meets the actual business needs, the message subscriber enters a subscription application page and submits a subscription application. If the message publishing declaration does not meet the actual business needs, the message subscriber terminates the subscription process.

3. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 2, characterized in that, The message publishing declaration includes a publishing system, a message type, a content description, and an example message.

4. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 3, characterized in that, The subscription application includes a subscription system, a demand description, and a target message type.

5. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 1, characterized in that, The message platform generates a configuration instruction set using automatic decision rules based on the message publishing declaration and the subscription application, and determines whether the configuration instruction set triggers a resource dynamic self-configuration mechanism. If the configuration instruction set triggers the resource dynamic self-configuration mechanism, the message platform executes resource dynamic self-configuration and verifies the configuration result. If the configuration instruction set does not trigger the resource dynamic self-configuration mechanism, the message platform maintains the current resource configuration state. The message platform updates a list data based on a preset list data, and combines the submitted message publishing declaration and the subscription application to update the list data. The message platform generates a configuration instruction set containing target elements based on the updated list data and automatic decision rules. The message platform determines whether the configuration instruction set triggers a resource dynamic self-configuration mechanism based on a resource dynamic self-configuration mechanism of a message queue middleware. If the configuration instruction set triggers the resource dynamic self-configuration mechanism, the message platform executes resource dynamic self-configuration and verifies the configuration result. If the configuration instruction set does not trigger the resource dynamic self-configuration mechanism, the message platform maintains the current resource configuration state.

6. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 5, characterized in that, The target elements include a message publisher, a message subscriber, and a message type.

7. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 6, characterized in that, The configuration instruction set includes: The message publisher system in a business scenario is regarded as a message producer, a name of a switch is generated based on a business system number of the message publisher system, and the message publishing declaration is published to a message queue middleware through the switch. The message is routed and identified through a routing key. The message subscriber system in the business scenario is regarded as a message consumer, a name of a message queue is generated based on a business system number of the message subscriber system, and the message is received through the message queue. The business scenario is regarded as a message type, and the message type is routed and identified through the routing key.

8. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 7, characterized in that, The execution resource dynamic self-configuration comprises: If the system account in the configuration instruction set does not exist, the message platform creates corresponding system accounts according to the identification information of the message publisher and the message subscriber based on preset naming rules, and generates a random password through an encryption algorithm; If the switch in the configuration instruction set does not exist, the message platform creates the switch and configures a life cycle policy, and grants the message publisher write permission for the switch; If the message queue in the configuration instruction set does not exist, the message platform creates a subscriber queue for the message subscriber, configures a dead letter queue and a survival time policy, and grants the message subscriber read permission for the subscriber queue; If the binding relationship in the configuration instruction set does not exist, a ternary binding relationship among the switch, the routing key and the subscriber queue is established, and the binding relationship is persistently stored. The verification of the configuration result comprises:

9. The RabbitMq component auto-configuration method of multi-system message passing scenario according to claim 8, characterized in that, The message publisher configures connection information through a software dependency package provided by the message platform, instantiates a message entity class based on the connection information, and executes message sending through a sending message technology. If the message sending is successful, the connectivity verification between the message publisher and the message platform is passed. If the message sending fails, the connectivity verification between the message publisher and the message platform is not passed; The message subscriber configures subscription information through a software dependency package provided by the message platform, and establishes a connection between the subscription information and the message queue. If the connection is successfully established, the connectivity verification between the message subscriber and the message platform is passed. If the connection fails to be established, the connectivity verification between the message subscriber and the message platform is not passed; The message platform simulates the message publisher to send a test message. If the message subscriber receives the test message, the link connectivity verification from publishing to subscribing is passed. If the message subscriber does not receive the test message, the link connectivity verification from publishing to subscribing is not passed. The system comprises:

10. A RabbitMq component auto-configuration system for a multi-system message passing scenario, configured to implement the RabbitMq component auto-configuration method of any one of claims 1-9, characterized in that, A subscription management module is configured to submit a message publishing declaration by a message publisher to a message platform among multiple systems, and to perform business matching on the message publishing declaration in combination with actual business requirements of a message subscriber. If the business matching is successful, a subscription application is submitted. If the business matching fails, the subscription process is terminated. A resource configuration module is configured to generate a configuration instruction set by using automatic decision rules in combination with the message publishing declaration and the subscription application, to determine whether the configuration instruction set triggers a resource dynamic self-configuration mechanism, to execute resource dynamic self-configuration and to verify the configuration result if the configuration instruction set triggers the resource dynamic self-configuration mechanism, and to maintain a current resource configuration state if the configuration instruction set does not trigger the resource dynamic self-configuration mechanism. ​

Images