The amq: endpoint works exactly like the activemq: endpoint in Apache Camel; only it uses the fabric to automatically discover the broker. So there is no configuration required; it'll just work out of the box and automatically discover whatever ActiveMQ message brokers are available; with failover and load balancing.
So you use it like this from Camel routes:
In addition to auto discovery and load balancing of ActiveMQ brokers, the amq: endpoint works great with Broker Groups.
A great use case for broker groups is if you want to have data centre or geographic clusters of brokers. e.g. one for the US, one for Europe and one for Asia. Then fabric8 automatically creates a Profile for each mq client in each group. (e.g. mq-client-us, mq-client-europe, mq-client-asia).
Then by just adding the profile for the broker group you wish to connect to to your container (e.g. "mq-client-europe") then the amq: endpoint will automatically connect to that broker group ("Europe").
See the Broker Clients documentation for more details.