The Advanced Message Queuing Protocol (AMQP) is an open internet protocol for business messaging. The specification of the AMQP protocol is available at http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties.

In addition to Universal Messaging's own protocol, NSP and NHP interfaces are capable of also accepting AMQP connections over TCP sockets, while NSPS and NHPS interfaces can accept AMQP connections over SSL/TLS for client implementations that support it.

In order to connect to a Universal Messaging server using AMQP, your application needs to use an amqp://host:port URL (NSP and NHP interfaces) or amqps://host:port URL (NSPS and NHPS interfaces). AMQP connections are treated in the same way as any other connections by the Universal Messaging realm. If the username is present, the Universal Messaging subject is username@hostname, otherwise the subject is <AnonymousUser>@hostname where <AnonymousUser> is configured under Configuration > Protocol AMQP Config > AnonymousUser.

Software AG recommends that you establish an AMQP JMS connection using the QPID Proton or Swift MQ client libraries, and using a SASL plain over TLS connection.

This way you can define realm and channel or queue ACLs as you would for any Universal Messaging connection. For example, using the one of the JMS Sample applications with AMQP without a username/password to connect to amqp://localhost:10000 will result in a Universal Messaging subject of <AnonymousUser>@localhost.

AMQP applications can publish events to channels and queues, which should exist in advance.

Events published via AMQP are fully interoperable with any Universal Messaging subscriber on any client platform supported and can be snooped using the Universal Messaging Enterprise Manager:

AMQP applications can subscribe to pre-existing channels and queues.

The Universal Messaging server supports the creation of temporary topics and queues using an AMQP JMS session's createTemporaryTopic() and createTemporaryQueue() methods. Currently only the "delete-on-close" lifetime policy is supported; a Node dynamically created with this lifetime policy will be deleted at the point that the Link which caused its creation ceases to exist.

Client applications can perform transactional work over AMQP. Universal Messaging implements the local transaction operations defined in the AMQP specification. For example, if an application communicates to the realm server using a JMS AMQP client library (e.g. Apache Qpid JMS client) it can take advantage of the local transaction functionalities defined in the JMS specification.

The JMS sample applications provided with the distribution of the Universal Messaging server can be configured to communicate over the AMQP protocol.

For more information, see the page Using the JMS Sample Applications with AMQP in the JMS code examples in the Developer Guide.