THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Static exchange routes are added and deleted using qpid-tool route route add and qpid-tool route route del respectively. The following example creates a static exchange route with a binding key of "global.#" on the default topic exchange:
...
| No Format |
|---|
$ qpid-route
Usage: qpid-route [OPTIONS] dynamic add <dest-broker> <src-broker> <exchange> [tag] [exclude-list]
qpid-route [OPTIONS] dynamic del <dest-broker> <src-broker> <exchange>
qpid-route [OPTIONS] route add <dest-broker> <src-broker> <exchange> <routing-key> [tag] [exclude-list]
qpid-route [OPTIONS] route del <dest-broker> <src-broker> <exchange> <routing-key>
qpid-route [OPTIONS] queue add <dest-broker> <src-broker> <exchange> <queue>
qpid-route [OPTIONS] queue del <dest-broker> <src-broker> <exchange> <queue>
qpid-route [OPTIONS] route list [<dest-broker>]
qpid-route [OPTIONS] route flush [<dest-broker>]
qpid-route [OPTIONS] route map [<broker>]
qpid-route [OPTIONS] link add <dest-broker> <src-broker>
qpid-route [OPTIONS] link del <dest-broker> <src-broker>
qpid-route [OPTIONS] link list [<dest-broker>]
Options:
--timeout seconds (10) Maximum time to wait for broker connection
-v [ --verbose ] Verbose output
-q [ --quiet ] Quiet output, don't print duplicate warnings
-d [ --durable ] Added configuration shall be durable
-e [ --del-empty-link ] Delete link after deleting last route on the link
-s [ --src-local ] Make connection to source broker (push route)
-t-ack <transport>N [ --transport <transport>]
Acknowledge transfers over the bridge in batches of N
-t <transport> Specify[ --transport to<transport>]
use for links, defaults to tcp
Specify transport to use for links, defaults to tcp
dest-broker and src-broker are in the form: [username/password@] hostname | ip-address [:<port>]
ex: localhost, 10.1.1.7:10000, broker-host:10000, guest/guest@localhost
|
...
Transport | Description |
|---|---|
tcp | (default) A cleartext TCP connection |
ssl | A secure TLS/SSL over TCP connection |
rdma | A Connection using the RDMA interface (typically for an Infiniband network) |
The tag and exclude-list arguments are not needed. They have been left in place for backward compatibility and for advanced users who might have very unusual requirements. If you're not sure if you need them, you don't. Leave them alone. If you must know, please refer to "Message Loop Prevention" in the advanced topics section below. The prevention of message looping is now automatic and requires no user action.
Caveats, Limitations, and Things to Avoid
...
If the link between the two sites has network latency, this can be compensated for by increasing the ack frequency with --ack N to achieve better batching across the link between the two sites.
Caveats, Limitations, and Things to Avoid
Redundant Paths
The current implementation of federation in the M4 broker imposes constraints on redundancy in the topology. If there are parallel paths from a producer to a consumer, multiple copies of messages may be received.
A future release of Qpid will solve this problem by allowing redundant paths with cost metrics. This will allow the deployment of networks that are tolerant of connection or broker loss.
Lack of Flow Control
M4 broker federation uses unlimited flow control on the federation sessions. Flow control back-pressure will not be applied on inter-broker subscriptions.
Lack of Cluster Failover Support
The client functionality embedded in the broker for inter-broker links does not currently support cluster fail-over. This will be added in a subsequent release.
Example Scenarios
Using QPID to bridge disjoint IP networks
...
Multi-tiered topology
| No Format |
|---|
+-----+
| 5 |
+-----+
/ \
+-----+ +-----+
| 2 | | 6 |
+-----+ +-----+
/ | \ | \
+-----+ +-----+ +-----+ +-----+ +-----+
| 1 | | 3 | | 4 | | 7 | | 8 |
+-----+ +-----+ +-----+ +-----+ +-----+
|
...