Chapter 1. Overview
AMQ C++ is a C++ library for writing messaging applications. It allows you to write client and server applications that send and receive AMQP messages.
AMQ C++ is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. See Introducing Red Hat JBoss AMQ 7 for an overview of the clients and other AMQ components. See AMQ Clients 1.2 Release Notes for information about this release.
AMQ C++ is based on the Proton API from Apache Qpid.
1.1. Key Features
AMQ C++ is a flexible and capable messaging API. It enables any application to speak AMQP 1.0.
- An event-driven API that simplifies integration with existing applications
- Access to all the features and capabilities of AMQP 1.0
- SSL/TLS and SASL for secure communication
- Seamless conversion between AMQP and language-native data types
- Heartbeating and automatic reconnect for reliable network connections
1.2. Supported Standards and Protocols
AMQ C++ supports the following industry-recognized standards and network protocols.
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
1.3. Supported Configurations
AMQ C++ supports the following OS and language versions. See Red Hat JBoss AMQ 7 Supported Configurations for more information.
- Red Hat Enterprise Linux 6 and 7 with GNU C++, compiling as C++03 or C++11
- Microsoft Windows Server 2012 R2 with Microsoft Visual Studio 2013
The code presented in this guide uses C++11 features. AMQ C++ is also compatible with C++03, but the code will require minor modifications.
1.4. Terms and Concepts
This section introduces the core API entities and describes how they operate together.
| Entity | Description |
|---|---|
| Container | A top-level container of connections |
| Connection | A channel for communication between two peers on a network |
| Session | A serialized context for producing and consuming messages |
| Sender | A channel for sending messages to a target |
| Receiver | A channel for receiving messages from a source |
| Source | A named point of origin for messages |
| Target | A named destination for messages |
| Message | A mutable holder of application content |
| Delivery | A message transfer |
AMQ C++ sends and receives messages. Messages are transferred between connected peers over senders and receivers. Senders and receivers are established over sessions. Sessions are established over connections. Connections are established between two uniquely identified containers. Though a connection can have multiple sessions, often this is not needed. The API allows you to ignore sessions unless you require them.
A sending peer creates a sender to send messages. The sender has a target that identifies a queue or topic at the remote peer. A receiving peer creates a receiver to receive messages. The receiver has a source that identifies a queue or topic at the remote peer.
The sending of a message is called a delivery. The message is the content sent, including all metadata such as headers and annotations. The delivery is the protocol exchange associated with the transfer of that content.
To indicate that a delivery is complete, either the sender or the receiver settles it. When the other side learns that it has been settled, it will no longer communicate about that delivery. The receiver can also indicate whether it accepts or rejects the message.
1.5. Document Conventions
This document uses the following conventions for the sudo command and file paths.
The sudo Command
In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo, as any changes can affect the entire system.
For more information about using sudo, see The sudo Command.
About the Use of File Paths in this Document
In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/...). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example, C:\Users\...).
