Setting Up DMR Using Broker Manager

You can use Broker Manager to set up Dynamic Message Routing (DMR). Before you configure your event mesh, ensure that you:

For setup steps for the Solace Event Broker CLI, see Setting Up DMR Using the Solace Event Broker CLI.

This topic includes the following tasks:

Creating a Cluster

If you are configuring DMR for event broker services, create your clusters using Cluster Manager and your external links using Mesh Manager. If you create clusters or external links in another way, you cannot use Mesh Manager to administer your event mesh. If you need internal links, you can create them using Broker Manager or the Solace Event Broker CLI.

To create a cluster using Broker Manager, perform these steps:

  1. Open Broker Manager. For instructions, see Using Broker Manager with Self-Managed Event Brokers.
  2. On the navigation bar, select Clustering.
  3. Click Create a New Cluster.

    Screenshot showing the options described in the surrounding text.

  4. Enter a name and a password for the cluster.
  5. (Optional) Edit the following settings as required for the cluster:

    SettingDescription
    Basic AuthenticationSpecifies whether the cluster uses basic authentication.

    Type

    Specifies the type of basic authentication the cluster uses for DMR links.
    • Internal Database — The cluster uses the locally configured password.
    • None — The cluster does not use authentication.
    Client Certificate AuthenticationSpecifies whether client certificate authentication is used for cluster links.
    ContentSpecifies the Privacy-Enhanced Mail (PEM)-formatted content for the client certificate used to log in to the remote node. It must consist of a private key and between one and three certificates comprising the certificate trust chain.

    Validate Server Name

    Specifies whether the TLS authentication mechanism of verifying the name is used to connect to the bridge. If enabled, the name used to connect to the bridge is checked against the names specified in the certificate returned by the remote event broker.

    Maximum Chain DepthSpecifies the maximum number of signing certificate authority (CA) certificates that are present in the chain back to a trusted self-signed root CA certificate.
    Validate Certificate DatesSpecifies whether certificate "Not Before" and "Not After" validity dates are used.
    Direct Messaging OnlySpecifies whether the cluster uses direct messaging.

  6. Click Apply.
  7. You may get a warning about the spool size being too small. Unless you are moving large amounts of data between event brokers, you can click Continue to bypass the warning with no repercussions. For information about changing the maximum amount of spool usage, see Configuring Max Spool Usage and Configuring Message Spool Sizes.

You have now created a cluster for your event broker. You can see your cluster in the Summary tab. If you want to add more nodes to the cluster, see Adding a Node to a Cluster.

Configuring DMR Links

A cluster link connects nodes within a cluster or between two different clusters and allows them to exchange topology information, subscriptions, and data. A cluster link is composed of a control channel, a client profile, and one data channel per Message VPN.

External Links

Links between nodes that belong to different clusters are called external links. External links have a DMR bridge, which connects gateway nodes and allows messages published in one cluster to be delivered to the consumers of another cluster. Only clusters that are directly connected via an external link can exchange messages.

If you are configuring DMR for event broker services, create your clusters using Cluster Manager and your external links using Mesh Manager. If you create clusters or external links in another way, you cannot use Mesh Manager to administer your event mesh. If you need internal links, you can create them using Broker Manager or the Solace Event Broker CLI.

You can use Broker Manager to configure DMR external links for your event mesh.

For more information, see Configuring DMR External Links.

Internal Links

Links between nodes that belong to the same cluster are called internal links. Internal links allow messages published in one node to be delivered to consumers connected to another node. For subscriptions to be shared between every node in a cluster, internal links must be configured between every pair of nodes.

You can use Broker Manager to configure DMR internal links for your event mesh.

For more information, see Configuring DMR Internal Links.

Deleting Links Between Nodes

Deleting a link from a node removes the connection from one side of the DMR link. If the link is deleted from only one node, it remains on the other node and may cause topology issues or prevent new links from being configured between the nodes.

To remove a link between two nodes, perform these steps:

  1. If you haven't already, open Broker Manager for the event broker that you used to configure one of the clusters you want to unlink. For instructions, see Using Broker Manager with Self-Managed Event Brokers.
  2. On the navigation bar, select Clustering.
  3. Right click the link you want to remove. Select Delete Link and then click OK.

    Screenshot showing the options described in the surrounding text.

  4. Navigate to Broker Manager for the event broker that you used to configure the other cluster you want to unlink.
  5. Repeat steps 2 and 3 to delete the link.
  6. If you do not delete the link from both nodes, the link will still be enabled and viewable on the Summary tab for one node, but it will not be operational.

    Screenshot showing the options described in the surrounding text.