ARTEMIS-5050: misc improvements to 'Broker-to-Broker Connectivity' docs/index
This commit is contained in:
parent
d9d84f814c
commit
f2a410e9bc
|
@ -59,15 +59,15 @@ include::metrics.adoc[leveloffset=1]
|
||||||
|
|
||||||
include::core-bridges.adoc[leveloffset=1]
|
include::core-bridges.adoc[leveloffset=1]
|
||||||
include::clusters.adoc[leveloffset=1]
|
include::clusters.adoc[leveloffset=1]
|
||||||
include::federation.adoc[leveloffset=1]
|
|
||||||
include::federation-address.adoc[leveloffset=1]
|
|
||||||
include::federation-queue.adoc[leveloffset=1]
|
|
||||||
include::ha.adoc[leveloffset=1]
|
include::ha.adoc[leveloffset=1]
|
||||||
include::network-isolation.adoc[leveloffset=1]
|
include::network-isolation.adoc[leveloffset=1]
|
||||||
include::restart-sequence.adoc[leveloffset=1]
|
include::restart-sequence.adoc[leveloffset=1]
|
||||||
include::activation-tools.adoc[leveloffset=1]
|
include::activation-tools.adoc[leveloffset=1]
|
||||||
include::connection-routers.adoc[leveloffset=1]
|
|
||||||
include::amqp-broker-connections.adoc[leveloffset=1]
|
include::amqp-broker-connections.adoc[leveloffset=1]
|
||||||
|
include::federation.adoc[leveloffset=1]
|
||||||
|
include::federation-address.adoc[leveloffset=1]
|
||||||
|
include::federation-queue.adoc[leveloffset=1]
|
||||||
|
include::connection-routers.adoc[leveloffset=1]
|
||||||
include::jms-bridge.adoc[leveloffset=1]
|
include::jms-bridge.adoc[leveloffset=1]
|
||||||
|
|
||||||
//== Security
|
//== Security
|
||||||
|
|
|
@ -2,10 +2,7 @@
|
||||||
:idprefix:
|
:idprefix:
|
||||||
:idseparator: -
|
:idseparator: -
|
||||||
|
|
||||||
Instead of waiting for clients to connect, a broker can initiate a connection to another endpoint on a specific protocol.
|
Instead of waiting for clients to connect, a broker can also initiate a connection to another server.
|
||||||
|
|
||||||
Currently, this feature supports only the AMQP protocol.
|
|
||||||
However, in the future, it might be expanded to other protocols.
|
|
||||||
|
|
||||||
Broker connections are configured by the `<broker-connections>` XML element in the `broker.xml` configuration file.
|
Broker connections are configured by the `<broker-connections>` XML element in the `broker.xml` configuration file.
|
||||||
|
|
||||||
|
@ -65,6 +62,9 @@ The following types of operations are supported on an AMQP server connection:
|
||||||
|
|
||||||
* Mirrors
|
* Mirrors
|
||||||
** The broker uses an AMQP connection to another broker and duplicates messages and sends acknowledgements over the wire.
|
** The broker uses an AMQP connection to another broker and duplicates messages and sends acknowledgements over the wire.
|
||||||
|
* Federation
|
||||||
|
** Broker federation allows the local broker to create remote receivers for addresses or queues that have local demand.
|
||||||
|
Conversely it can also send federation configuration to the remote broker causing it to create receivers on the local broker based on remote demand on an address or queue over this same connection.
|
||||||
* Senders
|
* Senders
|
||||||
** Messages received on specific queues are transferred to another endpoint.
|
** Messages received on specific queues are transferred to another endpoint.
|
||||||
* Receivers
|
* Receivers
|
||||||
|
@ -245,7 +245,7 @@ It is recommended to not have active consumers on both servers.
|
||||||
|
|
||||||
=== Example
|
=== Example
|
||||||
|
|
||||||
There is an example as part of the distribution showing dual broker configuration (or disaster recovery) in `./examples/features/broker-connection/disaster-recovery`.
|
There is an example as part of the broker xref:examples.adoc[examples] showing dual broker configuration (or disaster recovery) in `./examples/features/broker-connection/disaster-recovery`.
|
||||||
|
|
||||||
On the provided example above, two brokers are configured to mirror each other and whatever happens in one broker is immediately copied over to the other broker.
|
On the provided example above, two brokers are configured to mirror each other and whatever happens in one broker is immediately copied over to the other broker.
|
||||||
|
|
||||||
|
@ -535,3 +535,7 @@ When federation consumers are created this value can be used to ensure that thos
|
||||||
The default is `-1`.
|
The default is `-1`.
|
||||||
include-federated::
|
include-federated::
|
||||||
Controls if consumers on a queue which come from federation instances should be counted when observing a queue for demand, by default this value is `false` and federation consumers are not counted.
|
Controls if consumers on a queue which come from federation instances should be counted when observing a queue for demand, by default this value is `false` and federation consumers are not counted.
|
||||||
|
|
||||||
|
=== Examples
|
||||||
|
|
||||||
|
A number of examples for using the federation functionality in a variety of situations can be found in the broker xref:examples.adoc[examples] under directory _./examples/features/broker-connection_.
|
||||||
|
|
|
@ -62,15 +62,20 @@ image::images/activemq-logo.png[align="center"]
|
||||||
|
|
||||||
* xref:core-bridges.adoc#core-bridges[Core Bridges]
|
* xref:core-bridges.adoc#core-bridges[Core Bridges]
|
||||||
* xref:clusters.adoc#clusters[Clustering]
|
* xref:clusters.adoc#clusters[Clustering]
|
||||||
* xref:federation.adoc#federation[Federation]
|
|
||||||
** xref:federation-address.adoc#address-federation[Address Federation]
|
|
||||||
** xref:federation-queue.adoc#queue-federation[Queue Federation]
|
|
||||||
* xref:ha.adoc#high-availability-and-failover[High Availability & Failover]
|
* xref:ha.adoc#high-availability-and-failover[High Availability & Failover]
|
||||||
** xref:network-isolation.adoc#network-isolation-split-brain[Network Isolation]
|
** xref:network-isolation.adoc#network-isolation-split-brain[Network Isolation]
|
||||||
** xref:restart-sequence.adoc#restart-sequence[Restart Sequence]
|
** xref:restart-sequence.adoc#restart-sequence[Restart Sequence]
|
||||||
** xref:activation-tools.adoc#activation-sequence-tools[Activation Tools]
|
** xref:activation-tools.adoc#activation-sequence-tools[Activation Tools]
|
||||||
|
* xref:amqp-broker-connections.adoc#broker-connections[AMQP Broker Connections]
|
||||||
|
** xref:amqp-broker-connections.adoc#amqp-server-connections[Server Connections]
|
||||||
|
** xref:amqp-broker-connections.adoc#mirroring[Mirroring]
|
||||||
|
** xref:amqp-broker-connections.adoc#federation[AMQP Federation]
|
||||||
|
*** xref:amqp-broker-connections.adoc#local-and-remote-address-federation[Address Federation]
|
||||||
|
*** xref:amqp-broker-connections.adoc#local-and-remote-queue-federation[Queue Federation]
|
||||||
|
* xref:federation.adoc#federation[Core Federation]
|
||||||
|
** xref:federation-address.adoc#address-federation[Address Federation]
|
||||||
|
** xref:federation-queue.adoc#queue-federation[Queue Federation]
|
||||||
* xref:connection-routers.adoc#connection-routers[Routing Connections]
|
* xref:connection-routers.adoc#connection-routers[Routing Connections]
|
||||||
* xref:amqp-broker-connections.adoc#broker-connections[Broker Connections]
|
|
||||||
* xref:jms-bridge.adoc#the-jms-bridge[JMS Bridge]
|
* xref:jms-bridge.adoc#the-jms-bridge[JMS Bridge]
|
||||||
|
|
||||||
== Security
|
== Security
|
||||||
|
|
Loading…
Reference in New Issue