This is an automated email from the ASF dual-hosted git repository. jbertram pushed a commit to branch 2.52.x in repository https://gitbox.apache.org/repos/asf/artemis.git
commit 0d7bb7078c35b8366cf40fe1ddfc63d3995cb3a4 Author: Timothy Bish <[email protected]> AuthorDate: Thu Feb 5 12:34:06 2026 -0500 ARTEMIS-5891 Add links to the AMQP federation configuration glossary The AMQP federation pages could use to direct links to the configuration glossary to make navigating them easier. --- docs/user-manual/amqp-address-federation.adoc | 1 + docs/user-manual/amqp-broker-connections.adoc | 2 ++ docs/user-manual/amqp-queue-federation.adoc | 1 + 3 files changed, 4 insertions(+) diff --git a/docs/user-manual/amqp-address-federation.adoc b/docs/user-manual/amqp-address-federation.adoc index 0344af2fc9..0526199829 100644 --- a/docs/user-manual/amqp-address-federation.adoc +++ b/docs/user-manual/amqp-address-federation.adoc @@ -11,6 +11,7 @@ On the remote peer a queue binding is created on the federated address which wil Once a message arrives at the federation address consumer on the initiating broker it is then published into the local address which routes the message into each of the queues bound to that address. Address federation can be configured to operate in a single direction between peers or can configured to operate in both directions between peers allowing message to flow in both directions delivering messages to consumers on either broker that were sent to the matching address on the opposing broker instance. +For a more complete reference of the AMQP Address Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary] image::images/amqp-federation-address-concept.png[] diff --git a/docs/user-manual/amqp-broker-connections.adoc b/docs/user-manual/amqp-broker-connections.adoc index cbdbfda4e3..98d197e168 100644 --- a/docs/user-manual/amqp-broker-connections.adoc +++ b/docs/user-manual/amqp-broker-connections.adoc @@ -464,6 +464,8 @@ The broker connection federation configuration consists of one or more policies </broker-connections> ---- +For a more complete reference of the AMQP Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary] + === Address federation Address federation can be thought of as full multicast over a set of loosely coupled brokers. diff --git a/docs/user-manual/amqp-queue-federation.adoc b/docs/user-manual/amqp-queue-federation.adoc index 8a42c5dcbb..8b254575c9 100644 --- a/docs/user-manual/amqp-queue-federation.adoc +++ b/docs/user-manual/amqp-queue-federation.adoc @@ -14,6 +14,7 @@ image::images/amqp-federation-queue-concept.png[] Queue federation can be configured operate in a single direction between peers or can configured to operate in both directions between peers allowing message to flow in both directions delivering messages to consumers on either broker that were sent to the matching queue on the opposing broker instance. When configured for dual federation messages can migrate back and forth between brokers depending on capacity and available local consumers, this back and forth message flow can be reduced by ensuring that the federation policy uses a pull when space is available configuration which will only pull a batch of messages from the remote if the local queue does not already have a backlog. +For a more complete reference of the AMQP Queue Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary] == Common Queue Federation Topologies --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
