CN115080152B

CN115080152B - Broker configuration method and device of message middleware, computer equipment and medium

Info

Publication number: CN115080152B
Application number: CN202210996232.1A
Authority: CN
Inventors: 高永飞; 张益军; 王峰; 王金明
Original assignee: Feihu Information Technology Tianjin Co Ltd
Current assignee: Feihu Information Technology Tianjin Co Ltd
Priority date: 2022-08-19
Filing date: 2022-08-19
Publication date: 2022-12-27
Anticipated expiration: 2042-08-19
Also published as: CN115080152A

Abstract

The application provides a Broker configuration method, a device, computer equipment and a medium of message middleware, under the scene that Broker components are required to be deployed on a group of servers with the same performance, namely a request object, when a Broker deployment request is responded, the Broker configuration templates related to a Broker cluster to which the Broker components to be deployed of the request object belong can be called from a plurality of pre-constructed Broker configuration templates and then output, so that deployment personnel can carry out targeted calibration confirmation on configuration contents of the displayed Broker configuration templates, a Broker deployment confirmation instruction is responded, the uniform deployment of the Broker components to be deployed of the group of servers with the same performance can be completed according to configuration contents contained in the determined Broker configuration templates, and compared with an implementation mode that Broker components are sequentially deployed on each server through a command line tool, the Broker deployment efficiency is greatly improved, and the Broker configuration modification flexibility and reliability are ensured.

Description

Broker configuration method and device of message middleware, computer equipment and medium

Technical Field

The application relates to the field of big data application, in particular to a Broker configuration method and device of message middleware, computer equipment and a medium.

Background

The RocketMQ is used as an open source message middleware of a pure java, distributed and queue model, and the Broker is used as a core component of the RocketMQ message middleware and used for realizing message storage and transmission between a Producer (Producer) and a Consumer (Consumer) so that the message middleware can bear message flow of high concurrency scenes and process messages at trillion level.

In practical application, a command line tool of a rocktmq can be utilized to start a Brocker operation, query a configuration item to be modified, and complete modification of configuration content of the configuration item. However, the efficiency of the current implementation of the Broker configuration is very low due to hundreds of items in the configuration, and the reliability of configuration modification is reduced due to the high error probability of the command line operation.

Disclosure of Invention

In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:

the application provides a Broker configuration method for message middleware, which includes:

responding to a Broker deployment request, and calling a Broker configuration template associated with a Broker cluster to which a Broker component to be deployed of a request object belongs;

outputting the called Broker configuration template, and displaying a plurality of Broker configuration items and configuration contents of the plurality of Broker configuration items on the Broker configuration template;

and in response to a Broker deployment confirmation instruction, deploying a Broker component aiming at the request object according to the confirmed configuration content contained in the Broker configuration template.

Optionally, the invoking a Broker configuration template associated with a Broker cluster to which a Broker component to be deployed of a request object belongs in response to a Broker deployment request includes:

responding to a Broker deployment request, and outputting a Broker deployment interface;

displaying the determined request object and a Broker cluster to which a Broker component to be deployed of the request object belongs in the Broker deployment interface in response to an input operation on the Broker deployment interface;

and calling a Broker configuration template associated with the Broker cluster from at least one pre-constructed Broker configuration template.

Optionally, the method for constructing the Broker configuration template includes:

acquiring a plurality of Broker configuration items contained in message middleware;

performing templating grouping processing on the acquired Broker configuration items, and outputting a plurality of obtained Broker configuration templates; each Broker configuration template comprises a plurality of Broker configuration items, and the configuration contents of each Broker configuration item can be edited, wherein the configuration contents comprise configuration attribute information and deployment indication information of the corresponding Broker configuration item;

associating the Broker configuration template to at least one Broker cluster in response to a Broker cluster association operation with respect to the Broker configuration template;

responding to the editing operation of any one of the Broker configuration templates associated with the Broker cluster, and updating the configuration content corresponding to the Broker configuration template to obtain an updated Broker configuration template;

and associating the updated Broker configuration template with the Broker cluster and storing the Broker configuration template.

Optionally, the responding to the Broker cluster association operation with respect to the Broker configuration templates, associating the Broker configuration templates to at least one Broker cluster, includes:

responding to the Broker cluster configuration request, outputting a Broker cluster configuration interface, and displaying a Broker cluster selection item and the plurality of determined Broker configuration templates in the Broker cluster configuration interface;

responding to the Broker cluster selection operation of the Broker cluster selection item, and determining a Broker cluster to be configured;

and responding to the Broker configuration template selection operation aiming at the Broker cluster to be configured, and associating the selected at least one Broker configuration template with the Broker cluster to be configured.

Optionally, the configuration attribute information of the Broker configuration item includes: one or more combinations of configuration item identification, default configuration parameters, description information, configuration parameter prompt information, configuration options and configuration item serial numbers in the Broker configuration template;

the deployment indication information of the Broker configuration item includes: whether dynamic modification is supported, whether the Broker component is a necessary configuration item for deploying the Broker component, and the operation type aiming at the Broker cluster; the operation types comprise deletion, modification and addition;

the updating the configuration content corresponding to the Broker configuration template in response to the editing operation on the Broker configuration template associated with any one of the Broker clusters to obtain an updated Broker configuration template includes:

deleting the corresponding Broker configuration item in response to the deletion operation of any one of the selected Broker configuration templates; and/or the presence of a gas in the atmosphere,

responding to the modification triggering operation of any one of the selected Broker configuration items in the Broker configuration template, and triggering the corresponding Broker configuration item to enter an editing state;

in response to the modification input operation of at least one configuration content of the Broker configuration item in the editing state, modifying the corresponding configuration content; and/or the presence of a gas in the gas,

in response to the adding operation of any one of the selected Broker configuration templates, adding the Broker configuration item to the Broker configuration template for the associated Broker cluster, and determining the Broker configuration item for the associated Broker cluster and the configuration content of the Broker configuration item contained in the Broker configuration template.

Optionally, the performing templated grouping on the obtained Broker configuration items and outputting the obtained plurality of Broker configuration templates includes:

grouping all the acquired Broker configuration items based on the configuration contents of the Broker configuration items to obtain a plurality of Broker configuration item groups;

performing templating treatment on the plurality of Broker configuration item groups respectively to obtain corresponding Broker configuration templates;

and outputting the Broker configuration template, and presenting the Broker configuration items corresponding to the Broker configuration item group in the Broker configuration template.

Optionally, the method further includes:

in the operation process of the Broker component, responding to an update request aiming at a Broker configuration item to be updated, and determining the Broker component to be updated to which the Broker configuration item to be updated belongs;

calling a Broker configuration template associated with a Broker cluster to which the Broker component to be updated belongs;

outputting the called Broker configuration template, and presenting the Broker configuration item to be updated on the Broker configuration template;

responding to the modification operation of the Broker configuration item to be updated, obtaining the update configuration content of the Broker configuration item to be updated, and adjusting the update indication state of the Broker configuration item to be updated; the update indication state is used for representing that the Broker configuration item to be updated is updated;

responding to an updating instruction aiming at the updated configuration content, detecting that the Broker component to be updated supports dynamic modification, and synchronously updating the updated configuration content to the corresponding Broker component to be updated for execution;

wherein the Broker component corresponding Broker configuration item is persisted.

The present application also proposes a Broker configuration apparatus of a message middleware, the apparatus comprising:

the calling module is used for responding to the Broker deployment request and calling a Broker configuration template related to a Broker cluster to which a Broker component to be deployed of a request object belongs;

the output module is used for outputting the called Broker configuration template, and displaying a plurality of Broker configuration items and configuration contents of the plurality of Broker configuration items on the Broker configuration template;

and the deployment module is used for responding to a Broker deployment confirmation instruction and deploying the Broker components aiming at the request object according to the confirmed configuration content contained in the Broker configuration template.

The present application further proposes a computer device, the computer device comprising:

a communication interface;

a memory for storing a program for implementing the Broker configuration method of the message middleware as described above;

and the processor is used for loading and executing the program stored in the memory to realize the Broker configuration method of the message middleware.

The present application also proposes a computer-readable storage medium, on which a computer program is stored, the computer program being loaded and executed by a processor to implement the Broker configuration method of the message middleware as described above.

Based on the technical scheme, the method and the device have the advantages that grouping and templating are carried out on a plurality of Broker configuration items, the plurality of obtained Broker configuration templates are associated with and stored in each Broker cluster, so that in a scene that Broker components need to be deployed on a certain or same-performance group of servers, namely, request objects, when a Broker deployment request is responded, the Broker cluster to which the Broker components to be deployed of the request objects belong is determined, the Broker configuration templates associated with the Broker cluster are called from the plurality of pre-constructed Broker configuration templates and then output, deployment personnel can carry out targeted calibration confirmation on configuration contents of the displayed Broker configuration templates, the Broker deployment of the Broker components to be deployed of the same-performance group of servers can be completed according to configuration contents contained in the determined Broker configuration templates in response to a Broker deployment confirmation instruction, the Broker deployment efficiency is greatly improved compared with an implementation mode that Broker components are sequentially deployed on each server through an instruction line tool, and Broker deployment efficiency is greatly improved, and flexibility and reliability of Broker configuration modification are guaranteed.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a flowchart illustrating an alternative example of a Broker configuration method of message middleware provided in the present application;

fig. 2 is a schematic diagram of an alternative system architecture of a Broker configuration method applied to the message middleware proposed in the present application;

fig. 3 is a schematic diagram of a Broker configuration template of a conventional configuration type in the Broker configuration method of the message middleware proposed in the present application;

fig. 4 is a flowchart illustrating another alternative example of a Broker configuration method of message middleware proposed in the present application;

fig. 5 is a schematic diagram of an alternative Broker deployment interface in the Broker configuration method for message middleware according to the present application;

fig. 6 is a schematic diagram of a Broker configuration method for message middleware according to the present application, illustrating a new Broker component deployment process;

fig. 7 is a flowchart illustrating a further alternative example of a Broker configuration method of the message middleware proposed in the present application;

fig. 8 is a schematic diagram showing a plurality of Broker configuration items to be grouped in the Broker configuration method of the message middleware proposed in the present application;

fig. 9 is a schematic diagram showing a plurality of Broker configuration templates grouped according to Broker configuration items in the Broker configuration method of the message middleware proposed in the present application;

fig. 10 is a schematic diagram of a Broker configuration template construction method in the Broker configuration method of the message middleware proposed in the present application;

fig. 11 is a schematic diagram of an implementation method of association between a Broker cluster and a Broker configuration template in the Broker configuration method of the message middleware provided in the present application;

fig. 12 is a flowchart illustrating a further alternative example of a Broker configuration method of the message middleware proposed in the present application;

FIG. 13 is a schematic diagram of an online dynamic adjustment interface of a Broker configuration item in the Broker configuration method of the message middleware proposed in the present application;

fig. 14 is a schematic structural diagram of an alternative example of a Broker configuration apparatus of the message middleware proposed in the present application;

fig. 15 is a schematic structural diagram of yet another alternative example of a Broker configuration apparatus of the message middleware proposed in the present application;

fig. 16 is a hardware configuration diagram of an alternative example of a computer device suitable for the Broker configuration method of the message middleware proposed in the present application;

fig. 17 is a hardware configuration diagram of still another alternative example of a computer device suitable for the Broker configuration method of the message middleware proposed in the present application.

Detailed Description

Aiming at the description content in the background technology part, in order to improve the configuration efficiency and reliability of the message middleware, when a Broker of the distributed message middleware, namely an operation and maintenance RocktMQ, is deployed, a uniform configuration mode can be adopted for a group of servers with the same performance to realize the deployment of each configuration item of the Broker; for servers with different performances, flexibly adjusting configuration items of the Broker; and all the configuration items can be adjusted in real time when the Broker is operated. However, the existing rockmq command line tool cannot be used in deploying the Broker, that is, cannot complete configuration and adjustment of configuration items when the Broker is deployed, especially deploy the Broker for uniform configuration of a group of servers with the same performance, and cannot accurately know state change conditions of the configuration items, such as whether the configuration items are modified, what default values are, and the like.

In order to improve the problems, the method and the device realize templating and grouping management of all configuration items of the Broker in a webpage mode, and when the Broker of each server is deployed, uniform configuration of a group of servers with the same performance and flexible modification of the configuration items of the Broker of different servers with the same performance can be realized through configuration template functions; and when the breaker runs, the default value can be referred, so that real-time dynamic configuration modification of each configuration item is realized, and the safety and the efficiency of the breaker operation and maintenance are improved.

The technical solutions in the embodiments of the present application will be described below clearly and completely with reference to the drawings in the embodiments of the present application, and it should be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Referring to fig. 1, a schematic flowchart of an optional example of a message middleware configuration method provided in this embodiment is shown, where the method may be applied to an MQCloud system (i.e., a one-stop service platform integrating a client SDK, monitoring and early warning, and clustering operation and maintenance), as shown in fig. 2, and may be executed by an electronic device in charge of management of Broker deployment, operation and maintenance, which may include but is not limited to a desktop computer, a notebook computer, a user terminal such as a smart transportation/medical device, a robot, and a virtual reality device, and may be determined according to a service scenario requirement, as shown in fig. 1, the message middleware configuration method provided in this embodiment may include:

s11, responding to a Broker deployment request, and calling a Broker configuration template associated with a Broker cluster to which a Broker component to be deployed of a request object belongs;

in combination with the above description of the technical solution of the present application, the present application proposes to complete Broker deployment configuration on a message middleware before a Broker is run, and in order to improve configuration efficiency, proposes a concept of a Broker configuration template, and performs packet templating on hundreds of Broker configuration items in advance, so that when performing Broker component deployment configuration on a group of servers with the same performance, the pre-constructed Broker configuration template can be reused, and a plurality of configuration items required for deploying the Broker need not to be selected one by one for each server, thereby greatly improving configuration efficiency and reliability. For the construction process of the Broker configuration template, reference may be made to the description of the corresponding parts of the following embodiments, which are not described in detail herein.

Based on the above analysis, in combination with the system architecture shown in fig. 2, when determining that Broker deployment is performed on one or a group of servers (i.e., servers in a name server (name server) cluster, which may be referred to as a request object) in the message middleware, the electronic device may obtain a Broker deployment request for the message middleware, parse the Broker deployment request, determine a server identifier of the Broker requested to be deployed, and a component identifier of the Broker deployment performed on the service cluster having the server identifier, and then retrieve a Broker configuration template associated with the Broker cluster to which a component to be deployed belongs from a plurality of pre-constructed Broker configuration templates, that is, retrieve a Broker configuration template associated with the determined component identifier.

The implementation method of how to invoke the Broker configuration template based on the received Broker deployment request may be determined by combining with a storage manner of the Broker configuration template, including but not limited to the associated storage implementation manner described above, and this embodiment is not described in detail here.

Step S12, outputting the called Broker configuration template, and displaying a plurality of Broker configuration items and configuration contents thereof on the Broker configuration template;

continuing with the above description, in order to achieve personalized deployment of the Broker configuration items for the requested server or a group of servers, and simultaneously ensure the efficiency of Broker deployment, the Broker configuration template output for deploying the Broker components is directly called for the deployment personnel to check and determine the configuration content in the output Broker configuration template.

For example, as shown in fig. 3, the schematic diagram of a Broker configuration template of the conventional configuration type, the Broker configuration template includes a plurality of Broker configuration items that may include: the method includes the following steps of conventionally configuring Broker configuration templates, wherein the Broker configuration templates comprise Broker names, broker role, flushDiskType (disk refreshing type/disk refreshing mechanism), broker IP1 (IP protocol 1 of a Broker), broker IP2 (IP protocol 2 of a Broker), listenport (monitoring port), broker Cluster Name (Broker cluster name), broker addresses, and storePathRootDir (storage path root directory).

For each Broker configuration item contained in the Broker configuration template, the configuration content is usually described from multiple aspects, such as key-value (value represents default configuration of Broker); description information (recorded as description) of the Broker configuration item; a prompt to configure a Broker (noted as a prompt); whether it is a necessary option for Broker deployment (noted as mandatory); support modification, deletion, and addition to a cluster configuration (denoted as operation); ordering in all Broker configurations (numbered); whether the configured value is one of several options (marked as an option); the Broker is not required to be restarted to be in effect in real time (recorded as dynamic modification) after configuration modification, and the like.

In practical applications, each configuration content of the Broker configuration item does not necessarily need to be modified, and some configuration contents may directly adopt default contents, so that, for the content of the output Broker configuration template, all configuration contents listed above may not be shown, as shown in fig. 3, a Broker default value (denoted as a default value) of each Broker configuration item included in the Broker configuration template, a specific configuration (denoted as an on-line value) adopted for the associated Broker cluster, a dynamic modification, and in order to solve a corresponding Broker configuration item, descriptions and the like may also be included, but are not limited to the configuration contents of the Broker configuration template corresponding to the conventional configuration type shown in fig. 3, and may be adaptively adjusted according to the situation, which is not described in detail herein by way of example.

In some embodiments, the Broker deployment personnel verify the configuration content of the displayed Broker configuration template, and after determining that the configuration content of each Broker configuration item has no problem, the Broker deployment personnel can directly perform subsequent deployment operation according to the configuration content; if the configuration content of one or more Broker configuration items is not suitable for deploying the object (such as one or a group of servers mentioned above)/is wrong, the configuration content can be directly modified.

Therefore, the display area of the output Broker configuration template may include a configuration editing area corresponding to each Broker configuration item, and the configuration editing area displays corresponding configuration content, so that the configuration content is triggered to enter an editing state, and then the displayed configuration content is modified, so as to obtain appropriate/correct configuration content.

And S13, responding to the Broker deployment confirmation instruction, and deploying the Broker assembly aiming at the request object according to the configuration content contained in the determined Broker configuration template.

After determining that the configuration content included in the called Broker configuration template has no problem, as shown in fig. 3, a "one-key installation" button may be clicked to generate a Broker deployment confirmation instruction for the output configuration content, it should be noted that, as shown in fig. 3, the Broker deployment confirmation instruction may include not only the confirmed configuration content, but also a server (i.e., a request object) selected to deploy a Broker, and information such as a configuration file installation path (which may be selected by customization, may adopt a default installation path, and may also be referred to as a deployment path) for deploying the Broker to the server.

In this way, when the Broker deployment confirmation instruction is responded, the Broker component deployment for the selected server can be completed according to the preset installation path by using the determined configuration content of the Broker component to be deployed, and in the deployment process, a Broker component deployment progress can be output.

In summary, in the embodiment of the present application, a plurality of Broker configuration items are templated in advance to obtain a plurality of Broker configuration templates of different types, and the plurality of Broker configuration templates are stored in association with corresponding Broker clusters, so that in a scenario where Broker components need to be deployed for a group of servers of a certain or the same performance, when responding to a Broker deployment request, a Broker cluster to which the Broker component to be deployed of a request object belongs may be determined first, and then the Broker configuration template associated with the Broker cluster is called from the plurality of pre-constructed Broker configuration templates and output, so that a deployment worker may perform targeted calibration and confirmation on configuration contents of the displayed Broker configuration template, respond to a Broker deployment confirmation instruction, and complete deployment of the Broker components to be deployed for a group of servers of the same performance according to configuration contents included in the determined Broker configuration templates, and compared with an implementation manner of sequentially deploying the Broker components for each server through a command line tool, broker deployment efficiency is greatly improved, and Broker deployment flexibility and reliability are ensured.

Referring to fig. 4, which is a flowchart illustrating a further optional example of a message middleware configuration method proposed in the present application, this embodiment may describe an optional detailed manner of the message middleware configuration method described above, but is not limited to the detailed implementation method described in this embodiment, and as shown in fig. 4, the method may include:

s41, responding to a Broker deployment request and outputting a Broker deployment interface;

step S42, responding to the input operation of the Broker deployment interface, and displaying the determined request object, the Broker cluster to which the Broker component to be deployed of the request object belongs and the deployment path in the Broker deployment interface;

referring to a schematic diagram of an alternative example of a Broker deployment interface shown in fig. 5, a server to deploy a Broker this time, that is, a request object requesting to deploy a Broker component, may be selected from a cascade menu popped up by clicking "xxx", and may be a group of servers with the same performance, or a server with unique performance, and then, the computer device may determine, based on the selected request object, a Broker cluster to which the Broker component to be deployed is to be deployed, which may be determined according to a grouping result of all Broker components in the message middleware, and this embodiment of the present application is not described in detail herein.

In order to meet the deployment requirement, the Broker deployment path of the request object can be customized, so that the Broker deployment interface can include an edit item of an installation/deployment path in addition to the edit item of the request object and the edit item of the affiliated Broker cluster, so that a deployment person can customize the Broker deployment path for the determined request object, and the customization configuration process of the deployment path is not described in detail in the application.

It should be noted that, the number and types of editing items included in the Broker deployment interface are not limited in the present application, and for example, editing items related to the deployment progress of the Broker component deployment process and the like may also be included, and the layout content of the Broker deployment interface may be flexibly adjusted according to actual requirements. It can be understood that, for a request object that does not need to define a deployment path by user, a default deployment path may be directly adopted, so that the editor item of the installation path may not be shown in the Broker deployment interface.

S43, calling a Broker configuration template associated with the Broker cluster from at least one Broker configuration template which is constructed in advance;

step S44, displaying the called Broker configuration template on a Broker deployment interface, and displaying a plurality of Broker configuration items and configuration contents thereof in the Broker configuration template;

in combination with the above description related to the technical solution of the present application, in order to improve the Broker component deployment efficiency and reliability, a large number of Broker configuration items are grouped and templated in advance, so that when one or more request objects need to be deployed with a Broker component, the Broker configuration template output associated with the Broker cluster to which the request object belongs may be directly invoked, and regarding the process of invoking and displaying the Broker configuration templates, reference may be made to the above embodiment and the description of the corresponding portion of fig. 3, which is not described herein again.

S45, responding to the editing operation of the configuration editing area aiming at any configuration content to obtain a Broker configuration file of a Broker component to be deployed;

for configuration content displayed in the Broker deployment interface, the configuration content may not meet the Broker deployment requirement of the request object, and in this case, the configuration content of the currently displayed Broker template may be edited and modified directly according to the Broker deployment requirement, so as to obtain configuration content more adapted to the service requirement of the request object. Therefore, when the electronic device outputs the called Broker configuration template, the configuration editing area of each of the plurality of Broker configuration items can be displayed on the Broker configuration template, and a configurator can edit and modify the configuration content of the corresponding Broker configuration item in the configuration editing area.

The display method comprises the steps of displaying configuration editing areas of different configuration contents, displaying corresponding configuration editing areas on the display device, and displaying corresponding configuration editing areas on the display device.

It should be noted that, in the case that the configuration content of the displayed Broker configuration template is directly called to meet the Broker deployment requirement, the configuration content may not be edited and modified, and the computer device may not execute the step S45, and may directly enter the subsequent step.

And S46, responding to the Broker deployment confirmation operation on the Broker deployment interface, and deploying the Broker components according to the deployment path of the request object according to the configuration content contained in the confirmed Broker configuration template.

In practical application, after determining information such as a request object, an installation path (i.e., a deployment path) for deploying a Broker component according to the method described above by combining with the newly-created Broker deployment process shown in fig. 6, JDK (Java Development Kit, which is a Software Development Kit (SDK) in Java language) verification may be performed first, that is, it is verified whether the JDK is configured to complete the deployment requirement this time, and if the configuration completion degree is greater than or equal to 1.8, the JDK configuration verification may be considered to pass, which is not described in detail in the present application.

In addition, various checking processes such as checking whether a port is occupied (for example, checking at least one port for deployment/installation in the determined configuration content), checking whether an installation directory is occupied (namely, directory checking) and the like can be further performed.

After the above-mentioned various checks, but not limited to the above-mentioned checks, if the check passes, the corresponding installation package may be downloaded from the database (repository), and stored in the download directory of the server as the request object, such as the tmp directory downloaded to the server, and then, since the installation package is usually a compressed file, it may be automatically decompressed to the determined installation directory, or manually decompressed to the determined installation directory, to generate a configuration file containing the determined configuration content, such as generating mq.conf, run.sh, and topic configurations, and after the configuration initialization processing, such as executing os.sh, the deployed Broker component may be started, acquiring the started process information, and outputting a Broker start process.

Optionally, in the deploying/installing process of the Broker component, if a problem occurs in the installation, the installation process may be suspended, and the corresponding prompt information is output (for example, the prompt information is displayed by an output prompt box), and the installation is continued after the problem is solved, so as to finally obtain the actual installation path of the deployed Broker component, such as/opt/mqclosed/Broker-a, and the like.

The embodiment may describe an implementation process of constructing the aforementioned Broker configuration template and storing the constructed Broker configuration template in association with each Broker cluster, but is not limited to the implementation method described below.

As shown in fig. 7, a schematic flowchart of another optional example of the Broker configuration method for message middleware provided in the present application is shown, and the method may still be executed by the MQCloud system, and for an implementation process of Broker component deployment on one or a group of servers (collectively referred to as request objects) by using a pre-constructed Broker configuration template, reference may be made to the description of the above embodiment, and this embodiment is not repeated. As shown in fig. 7, the method may include:

step S71, acquiring a plurality of Broker configuration items contained in the message middleware;

in the present application, it is proposed to add a configuration template function on the basis of the MQCloud system (i.e. an open source monitoring operation and maintenance platform), so that all Broker configuration items included in the message middleware are obtained through the configuration template function and a communication manner such as a web manner, including but not limited to the Broker configuration items listed in fig. 8. The number and types of the obtained Broker configuration items can be flexibly adjusted according to actual requirements, so that the subsequently constructed Broker configuration template can support all the versions of the Broker assemblies as much as possible, and the application is not listed.

Step S72, performing templated grouping processing on the obtained Broker configuration items, and outputting a plurality of obtained Broker configuration templates;

for example, after acquiring all the Broker configuration items of the Broker components of different versions, the application proposes to manage the Broker configuration items by grouping so that the Broker configuration items of hundreds of items become well-ordered, and therefore, the Broker configuration items are grouped, one Broker configuration template is formed by the Broker configuration items belonging to the same group, and a plurality of groups of Broker configuration templates are obtained, such as various types of Broker configuration templates, such as a scene configuration, a discovery mechanism, a theme topic & subscription, a write current limiting mechanism, a request processing thread pool, and memory preheating, shown in fig. 9.

In practical application of the application, for hundreds or even more Broker configuration items, in combination with the description content of the description column shown in fig. 8, the description content can represent the service function of the Broker configuration item, so that the application can perform group templating processing on a plurality of obtained Broker configuration items according to the description content of each Broker configuration item, and the implementation process of the application is not described in detail.

In the process of templating the group of the plurality of Broker configuration items, the Broker configuration template groups of hundreds of Broker configuration items can be determined according to, but not limited to, the grouping method described above, that is, the description contents of the Broker configuration items are clustered, a plurality of function services (each function service can be considered as one type) are determined, and the function names of the plurality of function services are used to generate corresponding Broker configuration template names. Then, each Broker configuration item of the same group/type can be used as a candidate Broker configuration item of the corresponding Broker configuration template to be stored in association with the template id of the Broker configuration template according to the clustering/grouping method described above.

In order to improve the reliability and accuracy of the configuration content of the plurality of automatically determined Broker configuration templates, the present application may further perform personalized processing on the configuration content of each Broker configuration template in combination with the actual requirement of the corresponding function service, such as adjusting the Broker configuration items included in each Broker configuration template, and/or adjusting one or more configuration contents of one or more Broker configuration items, and the like.

For any one of the above mentioned Broker configuration items, the configuration content can be described in terms of its configuration attribute, various deployment instructions, etc., that is, the configuration content of each Broker configuration item can include configuration attribute information and deployment instruction information, etc. of the Broker configuration item, where the configuration attribute information can include, but is not limited to, key values (content represented by key and value, which can be combined with the description of the corresponding part above), description information, ranking numbers in multiple Broker configuration items included in the Broker configuration template where the Broker configuration item is located, etc.; the deployment indication information may include, but is not limited to: the content of the prompt, the optional, the operation, the dynamic modification, the option, etc. may refer to the description of the corresponding part of the above embodiments regarding the meaning/content indicated by these deployment indication information.

For example, in the Broker configuration template set display interface shown in fig. 9, when configuration contents of one or more Broker configuration templates need to be edited, an editing identifier (e.g., a pen-shaped icon in fig. 9) corresponding to the Broker configuration template may be touched to display a plurality of candidate Broker configuration items and configuration contents corresponding to the candidate Broker configuration items included in the Broker configuration template, so as to edit two Broker configuration templates, which are common configuration and discovery mechanisms, as an example, a user may touch the editing identifiers corresponding to the two Broker configuration templates to output the Broker configuration template display interface shown in fig. 10.

In still other embodiments, after performing the grouping templating process on all the obtained Broker configuration items, the Broker configuration template display interface shown in fig. 10 may be directly output, or other triggering methods may be used to trigger the output of the Broker configuration template display interface, which is not limited to the above-described implementation manner, as appropriate. It should be noted that fig. 10 does not show all the Broker configuration items included in the Broker configuration templates, and can be determined according to the actual grouping result.

Then, the user can check whether each Broker configuration item and the configuration content thereof contained in each Broker configuration template are complete and correct through the Broker configuration template presentation interface, and if a certain Broker configuration template is not complete corresponding to the displayed Broker configuration item, after triggering the Broker configuration template to enter an editing state (for example, clicking a presentation area where the Broker configuration template is located, and the like, and the implementation manner of how to trigger the Broker configuration template to perform the editing state is not limited in the present application), can click a "+ configuration template" function button, and output the Broker configuration item presentation interface, so that the user can select one or more Broker configuration items to be added from a plurality of Broker configuration items presented in the Broker configuration item presentation interface, and add the selected Broker configuration item and the configuration content thereof to the Broker configuration template in the editing state.

Similarly, if one or more Broker configuration items corresponding to a certain Broker configuration template presented on the Broker configuration template presentation interface are grouped incorrectly, a deletion identifier corresponding to the Broker configuration item, such as a trash box-shaped icon shown in fig. 10, may be clicked, so as to delete the corresponding Broker configuration item and its configuration content from the currently grouped Broker configuration templates, and adaptively modify the configuration content of the Broker configuration item included in the Broker configuration template, such as adjusting a "serial number" of the Broker configuration item.

In addition, the method and the device can also perform editing operation on each configuration content of any Broker configuration item to adjust the corresponding configuration content, so as to better adapt to the service requirement.

Step S73, responding to the Broker cluster association operation aiming at the Broker configuration templates, and determining at least one Broker configuration template associated with each Broker cluster;

since the application proposes that each Broker component in the same Broker cluster of the message middleware adopts a uniform configuration, after the application performs the grouping templating process on all Broker configuration items according to the method described above to obtain a plurality of Broker configuration templates, it is desirable to associate the plurality of Broker configuration templates with different Broker clusters, thereby improving the configuration efficiency of the plurality of Broker components of the same Broker cluster. Therefore, the user can perform the Broker cluster association operation on the plurality of currently determined Broker configuration templates according to a preset manner, such as flexibly selecting the Broker configuration templates required for adding or deleting the Broker clusters to be configured and the Broker configuration items contained in the Broker configuration templates in the current display interface.

In order to realize the management relationship between the Broker configuration template and the Broker cluster, referring to the Broker cluster configuration interface shown in fig. 11, triggering may be performed in an editing area corresponding to a cluster, and outputting a cluster display menu including a plurality of Broker clusters to be configured, from which a user may select a Broker cluster to be configured at this time, such as a Broker cluster "shown in fig. 11, and then, may flexibly select, from the plurality of Broker configuration templates to be selected, a Broker configuration template to be associated with the Broker cluster and a Broker configuration item included in the Broker configuration template, such as selecting the Broker configuration template" common configuration ", and may also flexibly select each currently output Broker configuration item, and after determining the Broker configuration item required by the Broker cluster, click a function button" join cluster ", and associate the" common configuration "with the" core-cluster ". This is done to associate each Broker cluster with each Broker configuration template, but is not limited to the operation described in this embodiment.

Step S74, responding to the editing operation of the Broker configuration template associated with any Broker cluster, and updating the configuration content of the corresponding Broker configuration template to obtain an updated Broker configuration template;

in conjunction with the above description about the implementation process of step S73, the Broker configuration items included in the Broker configuration templates associated with the Broker clusters can be completed in the above association process, such as the implementation method described above in conjunction with fig. 11. Alternatively, as in the method described in step S74, the application may also flexibly determine one or more types of the Broker configuration templates associated with the Broker cluster, and further determine the Broker configuration items required by the Broker cluster included in each Broker configuration template.

Optionally, according to the analysis, the user may trigger the Broker configuration template that needs to adjust the Broker configuration item, so that the Broker configuration template is edited, and then, the Broker configuration item of the Broker configuration template may be added or deleted, or even each configuration content included in the Broker configuration item may be modified and updated, so as to obtain the configuration content of each Broker configuration item required by the Broker cluster.

And step S75, associating the updated Broker configuration template with the Broker cluster and storing the updated Broker configuration template.

After the association operation of the Broker configuration templates required by each Broker cluster is completed according to the above method, the determined association relationship, the Broker cluster types having the association relationship, and the configuration contents of the Broker configuration templates may be stored, and the specific storage manner is not limited in the present application and may be determined as the case may be.

Based on the method, under application scenes such as Broker deployment or operation and the like, a plurality of Broker assemblies contained in the same Broker cluster can be directly called to be multiplexed, so that the plurality of Broker assemblies can be uniformly configured, and thus, uniform Broker configuration can be adopted for servers with the same performance to deploy the Broker assemblies; for deploying the Broker components for servers with different performances, the Broker configuration templates required by association can be flexibly selected, the deployment of the Broker components can be rapidly and accurately completed, and the Broker configuration items can be flexibly adjusted in the Broker deployment stage according to actual requirements. For how to invoke the Broker configuration template to complete the implementation process of Broker component deployment of the request object, reference may be made to the description of the corresponding part of the above embodiment, and this embodiment is not described in detail here.

In some embodiments, the editing operation of the configuration content contained in the Broker configuration template described in the above embodiments can be implemented according to, but not limited to, the following implementation method, whether in the Broker configuration template construction stage or in the Broker cluster association processing stage. The Broker configuration item configuration attribute information is formed by combining one or more combinations of configuration item identification, default configuration parameters, description information, configuration parameter prompt information, configuration options, configuration item serial numbers in the Broker configuration template to which the Broker configuration item belongs and the like; the implementation method for updating the configuration content of the Broker configuration template can include, for example, whether dynamic modification is supported, whether the Broker configuration template is an indispensable configuration item for deploying the Broker component, and a related description of deployment indication information of the Broker configuration item for the operation type (such as deletion, modification, addition, and the like) of the Broker cluster:

in response to the deletion operation of any one of the selected Broker configuration templates, deleting the corresponding Broker configuration item, touching the trash bin icon of the Broker configuration item shown in fig. 10 and 11, and deleting the Broker configuration item in the row; and/or triggering the corresponding Broker configuration item to enter an editing state in response to the modification triggering operation of any Broker configuration item in the selected Broker configuration template; and in response to the modification input operation of at least one configuration content of the Broker configuration item in the editing state, modifying the corresponding configuration content. For example, with the schematic construction interface of the Broker configuration template shown in fig. 10, any configuration content that needs to be modified can be double-clicked, so that the configuration content is put into an editing state, the configuration content is modified, and the like.

Optionally, in the process of constructing the Broker configuration template, when the Broker configuration items included in the Broker configuration template can be flexibly selected, in addition to deleting or modifying the Broker configuration items according to the method described above (for example, a large number of Broker configuration items are classified and identified based on a classifier, and the obtained default Broker configuration item belongs to the type of the Broker configuration template), the computer device may further add the Broker configuration item to the Broker configuration template for the associated Broker cluster in response to an adding operation of any one of the selected Broker configuration templates, that is, flexibly adjust the Broker configuration items required by the Broker cluster, so as to determine the Broker configuration items for the associated Broker cluster included in the Broker configuration template and the configuration content of the Broker configuration items, that is, accurately determine the configuration content of each Broker configuration template.

To sum up the relevant description of each embodiment on the technical scheme provided by the application, a large number of Broker configuration items are subjected to grouping templating processing in advance to obtain a plurality of Broker configuration templates, so that when large-scale Broker component deployment is performed on each server with the same performance, unified configuration can be realized by calling the corresponding Broker configuration templates, the configuration content of each Broker configuration item can be flexibly modified, and compared with manual one-by-one Broker component deployment on each server, the Broker deployment efficiency and accuracy are greatly improved. For servers with different performances, the Broker component can be flexibly adjusted when being deployed.

Referring to fig. 12, a flow diagram of another alternative example of the Broker configuration method for the message middleware provided in the present application is shown, in practical application of the present application, one or more Broker configuration items may also be dynamically modified in a Broker configuration template manner when the Broker component is running, and applied to the Broker component in real time, that is, real-time adjustment of the Broker configuration items of the running Broker component is supported. In this regard, as shown in fig. 12, the implementation method may include:

step S121, in the operation process of the Broker component, responding to an update request aiming at the Broker configuration item to be updated, and determining the Broker component to be updated to which the Broker configuration item to be updated belongs;

as analyzed above, when a Broker component is modified while running in MQCloud, the Broker component can be informed using the proprietary communication protocol of the message middleware rockmq, so that the configuration center of the Broker component queries to which Broker component the Broker configuration item to be updated belongs.

Referring to a schematic diagram of the principle shown in fig. 13, when monitoring an update demand for modifying one or more Broker configuration items (denoted as Broker configuration items to be updated), the MQCloud may respond to an update request for the Broker configuration items to be updated, determine, by a Broker configuration center (i.e., broker configuration management equipment), a Broker component to be updated to which the Broker configuration items to be updated belong according to a corresponding relationship between each Broker component and the Broker configuration item determined at a deployment/new creation stage of the Broker component, and feed back a query result to the MQCloud.

Step S122, a Broker configuration template associated with a Broker cluster to which a Broker component to be updated belongs is called;

step S123, outputting the called Broker configuration template, and presenting a Broker configuration item to be updated on the Broker configuration template;

in combination with the above embodiments to construct the Broker configuration templates and the description of the Broker configuration templates and their association with each Broker cluster, in order to improve the real-time adjustment efficiency of the Broker configuration items, the Broker configuration templates associated with the Broker clusters to which the Broker components to be updated belong may be pulled from the Broker cluster configurations, including the configuration contents included in the Broker configuration templates, and then the pulled Broker configuration templates and the configuration contents included in the pulled Broker configuration templates may be output for the updater to perform online modification on the Broker configuration items to be updated. The output mode of the Broker configuration item to be updated is not detailed in the present application, and may be determined according to the situation.

Step S124, responding to the modification operation of the Broker configuration item to be updated, obtaining the update configuration content of the Broker configuration item to be updated, and adjusting the update indication state of the Broker configuration item to be updated;

for the Broker configuration item to be updated of the Broker component to be updated currently in the operating state, the updater may trigger the Broker configuration item to be updated to enter the editing state according to the actual updating requirement, referring to but not limited to the editing manner described above, and then modify each configuration content included in the Broker configuration item to be updated, so as to obtain the modified updated configuration content. For example, as shown in fig. 13, in the list of the configuration contents of "online value", the "yes" (i.e. the default value true) of the configuration contents before updating may be modified to "no" in the list of the Broker configuration items of topic & subscription in the Broker configuration template, i.e. the "autocorretasubscriptiongroupcomponent" is automatically created, so as to trigger the current Broker component to subsequently execute the "autocorretasubscriptiongroupconfiguration item, the default configuration is no longer used, but the modified configuration contents are used instead.

In addition, the update indication state of the Broker configuration item to be updated can be adjusted, as shown in fig. 13, the modified name of the Broker configuration item to be updated is displayed in bold, so as to visually display the modified Broker configuration item to be distinguished from the unmodified Broker configuration item. It can be seen that the above-mentioned update indication status can be used to indicate that the Broker configuration item to be updated is updated, including but not limited to the font bold status listed above, and the indication status can also be updated by adjusting the display color of the updated Broker configuration item, adding underlining, tilting the font, etc., so that the viewer can clearly identify which Broker configuration item has been modified.

Step S125, in response to the update instruction for the updated configuration content, detecting that the Broker configuration item to be updated supports dynamic modification, and synchronously updating the updated configuration content to the corresponding Broker component to be updated for execution.

In conjunction with the above description of the configuration content of the Broker configuration item, it is possible for different Broker configuration items to support dynamic modification, i.e., dynamic modification is not required to be performed in real time by restarting the Broker component, or dynamic modification is not required, i.e., the Broker component needs to be restarted to be performed after online modification. In this way, after completing the modification of at least one configuration content (which may include, but is not limited to, that shown in fig. 13) of the Broker configuration item to be updated, the "update" function button may be touched, so that the computer device may respond to the update instruction for the update configuration content to implement real-time modification of the Broker configuration item of the Broker component.

In the process of modifying the Broker configuration item to be updated in real time, the computer device can detect whether the Broker configuration item to be updated supports dynamic modification, and if so, can directly and synchronously update the obtained update configuration content to the corresponding Broker component for execution, and online real-time adjustment of the Broker configuration item is realized without restarting the Broker component. It should be noted that, regarding the update configuration content, the Broker configuration item to be updated only for the corresponding Broker component to be updated is valid, and the same Broker configuration item to be updated configured for other Broker components is invalid.

In practical application, the Broker configuration center may perform persistent storage (for example, storage in a json format file manner, etc.) on the Broker configuration items corresponding to each Broker component, so as to avoid loss of configuration content, but the application does not limit the implementation method of persistent storage of the Broker configuration items. Therefore, the Broker configuration center stores the configuration contents of all the Broker configuration items, so that in the process of Broker operation, when the Broker configuration items are dynamically adjusted, the Broker components to which the Broker configuration items to be updated belong can be queried according to the configuration contents, so that when the Broker configuration items of the Broker components are remotely modified, the modified update configuration contents can be obtained online and synchronously updated to the corresponding operating Broker components for execution, so that the Broker components operate according to the update configuration contents.

In conclusion, by performing grouping templating treatment on a large number of Broker configuration items, when the Broker components are deployed, different Broker clusters can adopt different Broker configuration templates, so that uniform deployment of a plurality of Broker components in each Broker cluster is realized; and flexible modification is supported when the Broker component is deployed aiming at a single server with different performances, and personalized deployment requirements are met. In addition, when the Broker component runs, on-line dynamic configuration is realized by referring to the configuration content of the default Broker configuration item, and in the dynamic query or modification process, the update indication state of the modified Broker configuration item can be adjusted to be visually distinguished from the unmodified Broker configuration item, so that other Broker configuration items to be updated can be continuously modified. In the face of hundreds of Broker configurations, the operation and maintenance efficiency and safety of the Broker are greatly improved.

Referring to fig. 14, a schematic structural diagram of an alternative example of the Broker configuration apparatus for message middleware proposed in the present application is shown in fig. 14, where the apparatus may include:

the invoking module 141 is configured to respond to a Broker deployment request, and invoke a Broker configuration template associated with a Broker cluster to which a Broker component to be deployed of a request object belongs;

an output module 142, configured to output the called Broker configuration template, where a plurality of Broker configuration items and configuration contents of each of the plurality of Broker configuration items are displayed on the Broker configuration template;

the deploying module 143 is configured to respond to a Broker deployment confirmation instruction, and deploy a Broker component for the request object according to configuration content included in the confirmed Broker configuration template.

Optionally, the retrieving module 141 may include:

the Broker deployment interface output unit is used for responding to a Broker deployment request and outputting a Broker deployment interface;

the information display unit is used for responding to the input operation of the Broker deployment interface, and displaying the determined request object and a Broker cluster to which a Broker component to be deployed of the request object belongs in the Broker deployment interface;

and the configuration template calling unit is used for calling the Broker configuration templates associated with the Broker cluster from at least one pre-constructed Broker configuration template.

In still other embodiments, as shown in fig. 15, the apparatus may further include:

a Broker configuration item acquisition module 144, configured to acquire a plurality of Broker configuration items included in the message middleware;

the templating processing module 145 is used for performing templating grouping processing on the acquired Broker configuration items and outputting a plurality of acquired Broker configuration templates; each Broker configuration template comprises a plurality of Broker configuration items, the configuration content of each of the plurality of Broker configuration items can be edited, and the configuration content comprises configuration attribute information and deployment indication information of the corresponding Broker configuration item;

an association processing module 146, configured to associate the Broker configuration templates to at least one Broker cluster in response to a Broker cluster association operation with respect to the Broker configuration templates;

the configuration content updating module 147 is configured to respond to an editing operation on a Broker configuration template associated with any one of the Broker clusters, and update configuration content corresponding to the Broker configuration template to obtain an updated Broker configuration template;

a Broker configuration item storage module 148, configured to associate and store the updated Broker configuration template with the Broker cluster.

Optionally, based on the description of the above embodiment, the association processing module 146 may include:

the Broker cluster configuration interface output unit is used for responding to the Broker cluster configuration request and outputting a Broker cluster configuration interface, and the Broker cluster selection item and the plurality of determined Broker configuration templates are displayed in the Broker cluster configuration interface;

the Broker cluster selection configuration unit is used for responding to the Broker cluster selection operation of the Broker cluster selection item and determining a Broker cluster to be configured;

and the association unit is used for responding to the Broker configuration template selection operation aiming at the Broker cluster to be configured, and associating the selected at least one Broker configuration template with the Broker cluster to be configured.

The configuration attribute information of the Broker configuration item may include: one or more combinations of configuration item identification, default configuration parameters, description information, configuration parameter prompt information, configuration options, configuration item serial numbers in the affiliated Broker configuration template and the like; the deployment indication information of the Broker configuration item may include: whether dynamic modification is supported, whether the Broker component is a necessary configuration item for deploying the Broker component, the operation type aiming at the Broker cluster and the like; the operation type may include, but is not limited to, deletion, modification, addition, and the like, and the content included in the configuration attribute information and the deployment indication information of the Broker configuration item is not limited in this application, and may be determined as the case may be.

Optionally, the configuration content updating module 147 may include:

a deleting unit, configured to delete the corresponding Broker configuration item in response to a deletion operation on any one of the Broker configuration items in the selected Broker configuration template; and/or the presence of a gas in the gas,

the modification triggering unit is used for responding to modification triggering operation of any one of the selected Broker configuration templates and triggering the corresponding Broker configuration item to enter an editing state;

the modification unit is used for responding to the modification input operation of at least one configuration content of the Broker configuration item in an editing state and modifying the corresponding configuration content; and/or the presence of a gas in the gas,

an adding unit, configured to, in response to an adding operation on any one of the selected Broker configuration templates, add the Broker configuration item to the Broker configuration template for the associated Broker cluster, and determine the Broker configuration item for the associated Broker cluster and the configuration content of the Broker configuration item, which the Broker configuration template contains.

In still other embodiments, the templating process 145 may include:

the grouping unit is used for grouping all the acquired Broker configuration items based on the configuration contents of the Broker configuration items to obtain a plurality of Broker configuration item groups;

the template processing unit is used for respectively carrying out template processing on the plurality of Broker configuration item groups to obtain corresponding Broker configuration templates;

the Broker configuration template output unit is used for outputting the Broker configuration template, and Broker configuration items corresponding to the Broker configuration item group are presented in the Broker configuration template.

In still other embodiments presented in the present application, the apparatus may further include:

the Broker component to be updated determining module is used for responding to an update request aiming at a Broker configuration item to be updated in the operation process of the Broker component and determining the Broker component to be updated to which the Broker configuration item to be updated belongs;

the Broker configuration template calling module is used for calling a Broker configuration template associated with a Broker cluster to which the Broker component to be updated belongs;

the Broker configuration item to be updated output module is used for outputting the called Broker configuration template, and the Broker configuration item to be updated is presented on the Broker configuration template;

the configuration content updating module is used for responding to the modification operation of the Broker configuration item to be updated and obtaining the updating configuration content of the Broker configuration item to be updated;

the state adjusting module is used for adjusting the updating indication state of the Broker configuration item to be updated; the update indication state is used for representing that the Broker configuration item to be updated is updated;

a synchronous updating module, configured to respond to an updating instruction for the updated configuration content, detect that the Broker component to be updated supports dynamic modification, and update the updated configuration content to the corresponding Broker component to be updated in a synchronous manner for execution;

It should be noted that, various modules, units, and the like in the embodiments of the foregoing apparatuses may be stored in a memory as program modules, and the processor may execute the program modules stored in the memory to implement corresponding functions, or may be implemented by combining the program modules and hardware, and for the functions implemented by the program modules and the combinations thereof and the achieved technical effects, reference may be made to the description of corresponding parts in the embodiments of the foregoing methods, and this embodiment is not described again.

The embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and the computer program is loaded and executed by a processor, so as to implement each step of the Broker configuration method for a message middleware, where a specific implementation process may refer to descriptions of corresponding parts in the foregoing embodiment, and details are not repeated in this embodiment.

Referring to fig. 16, a schematic diagram of a hardware structure of an alternative example of a computer device suitable for the Broker configuration method of the message middleware proposed in the present application, the computer device may be a terminal with certain data processing capability, such as a smart phone, a tablet computer, a robot, an intelligent medical device, an intelligent transportation device, a desktop computer, etc.; the Broker configuration method of the message middleware provided by the application can be realized by the cooperation of the terminal and the server. As shown in fig. 16, the computer device may include, but is not limited to: a communication interface 161, a memory 162, and a processor 163, wherein:

the communication interface 161 may include a data transmission interface of a communication module capable of implementing data interaction by using a wireless communication network to implement data interaction with other servers, terminals and other devices in the system. The communication module may include a wireless communication module such as a WIFI module, a 5G/6G (fifth generation mobile communication network/sixth generation mobile communication network) module, and a GPRS module. In practical applications, the communication interface 161 may further include a data interface for implementing data interaction between internal components of the computer device, such as a USB interface, a serial/parallel interface, an I/O interface, and the like.

The memory 162 may be used to store a program for implementing the Broker configuration method of the message middleware described in the above embodiments of the method; the processor 163 may load and execute the program stored in the memory to implement the steps of the Broker configuration method of the message middleware described in the corresponding method embodiment, and for a specific implementation process, reference may be made to the description of the corresponding part in the above embodiment, which is not described again.

In practical applications, the communication interface 161, the memory 162 and the processor 163 may be connected to a communication bus, and data interaction between each other and other components of the computer device may be realized through the communication bus, which may be determined according to practical requirements, and is not described in detail in this application.

In the present embodiment, the memory 162 may include a high speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device or other volatile solid state storage device. The processor 163 may be a Central Processing Unit (CPU), an application-specific integrated circuit (ASIC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices.

It should be understood that the computer device shown in fig. 16 does not constitute a limitation of the computer device in the embodiment of the present application, and in practical applications, the computer device may include more components than those shown in fig. 16, or a plurality of combined components. Illustratively, as shown in FIG. 17, the computer device may include at least one input component such as a display, a keyboard, a mouse, a microphone, a camera, etc.; at least one output component such as a speaker, an indicator light, etc., an antenna, a power manager, various sensor modules, etc., and fig. 17 does not show the components included in the computer device, which is not listed here.

Finally, it should be noted that, with respect to the above embodiments, unless the context clearly dictates otherwise, the words "a", "an" and/or "the" do not denote a singular number, but may include a plurality. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements. An element defined by the phrase "comprising a … …" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

Wherein in the description of the embodiments of the present application, "/" indicates an inclusive meaning, for example, a/B may indicate a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

Reference herein to terms such as "first," "second," or the like, is used for descriptive purposes only and to distinguish one operation, element, or module from another operation, element, or module without necessarily requiring or implying any actual such relationship or order between such elements, operations, or modules. And are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated, whereby a feature defined as "first" or "second" may explicitly or implicitly include one or more of such features.

In addition, in the present specification, the embodiments are described in a progressive or parallel manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. The device, the computer device, the system and the medium disclosed by the embodiment correspond to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether these functions are performed in hardware or software depends on the specific application of the solution and design pre-set conditions. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A Broker configuration method for message middleware, the method comprising:

in response to a Broker deployment confirmation instruction, deploying a Broker component for the request object according to configuration content contained in the confirmed Broker configuration template;

the construction method of the Broker configuration template comprises the following steps:

performing templating grouping processing on the acquired Broker configuration items, and outputting a plurality of obtained Broker configuration templates; each Broker configuration template comprises a plurality of Broker configuration items, the configuration content of each of the plurality of Broker configuration items can be edited, and the configuration content comprises configuration attribute information and deployment indication information of the corresponding Broker configuration item;

2. The method of claim 1, wherein the invoking a Broker configuration template associated with a Broker cluster to which a Broker component to be deployed of a request object belongs in response to a Broker deployment request comprises:

3. The method of claim 1, wherein associating the Broker configuration templates to at least one Broker cluster in response to a Broker cluster association operation with respect to the Broker configuration templates comprises:

associating the selected at least one Broker configuration template with the Broker cluster to be configured in response to the Broker configuration template selection operation for the Broker cluster to be configured.

4. The method of claim 1, wherein the profile attribute information of the Broker profile includes: one or more combinations of configuration item identification, default configuration parameters, description information, configuration parameter prompt information, configuration options and configuration item serial numbers in the Broker configuration template;

deleting the corresponding Broker configuration item in response to the deletion operation of any one of the selected Broker configuration templates; and/or the presence of a gas in the gas,

in response to the adding operation of any one of the Broker configuration templates, adding the Broker configuration item into the Broker configuration template for the associated Broker cluster, and determining the Broker configuration item contained in the Broker configuration template for the associated Broker cluster and the configuration content of the Broker configuration item.

5. The method of claim 1, wherein the templated grouping of the obtained Broker configuration items and outputting the obtained plurality of Broker configuration templates comprises:

respectively carrying out templating treatment on the plurality of Broker configuration item groups to obtain corresponding Broker configuration templates;

6. The method according to claim 1 or 2, characterized in that the method further comprises:

7. A Broker configuration apparatus of a message middleware, the apparatus comprising:

the deployment module is used for responding to a Broker deployment confirmation instruction and deploying the Broker assembly aiming at the request object according to the confirmed configuration content contained in the Broker configuration template;

8. A computer device, characterized in that the computer device comprises:

a communication interface;

a memory for storing a program for implementing a Broker configuration method of message middleware according to any one of claims 1 to 6;

a processor for loading and executing the program stored in the memory to implement the Broker configuration method of the message middleware of any one of claims 1-6.

9. A computer-readable storage medium, on which a computer program is stored, which, when being loaded and executed by a processor, carries out a Broker configuration method for message middleware according to any one of claims 1 to 6.