ActiveMQ supports the AMQP 1.0 protocol which is an OASIS standard.
Its very easy to enable ActiveMQ for AMQP. Just add a connector to the broker using the amqp URL.
It is enabled in the default ActiveMQ server configuration.
For more help see Run Broker.
The AMQP implementation fully supports an ActiveMQ security mechanism. This means that the broker accepts plain SASL authentication. Also, the authorization policies will be applied when you try to access (read/write) certain destinations.
For better scalability (and performance) you might want to run the AMQP protocol over the NIO transport. To do that just use amqp+nio transport prefix instead of amqp. For example, add the following transport configuration in your XML file:
It's easy to configure ActiveMQ to use AMQP over a SSL connection. All you have to do is use the amqp+ssl transport prefix instead of amqp. For example, add the following transport configuration in your XML file:
You should prefix destination address with `queue://` to use Queue based destinations or `topic://` to use topic based destinations. If an AMQP address is used without the prefix, it will be used as a Queue.
There are three basic conversion strategies that can be used with AMQP and interoperating with the JMS API.
Set the transformer transport option on the transportConnector to the desired mapping strategy. For example, to interoperate with JMS at the payload level, set the transformer option to jms
You can use Apache Qpid Proton.