Chapter 1. Overview
AMQ Python is a library for developing messaging applications. It enables you to write Python applications that send and receive AMQP messages.
AMQ Python is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. For an overview of the clients, see AMQ Clients Overview. For information about this release, see AMQ Clients 2.6 Release Notes.
1.1. Key features
- An event-driven API that simplifies integration with existing applications
- SSL/TLS for secure communication
- Flexible SASL authentication
- Automatic reconnect and failover
Distributed tracing based on the OpenTracing standard (RHEL 7 and 8)Important
Distributed tracing in AMQ Clients is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
- Seamless conversion between AMQP and language-native data types
- Access to all the features and capabilities of AMQP 1.0
1.2. Supported configurations
AMQ Python supports the following OS and language versions:
- Red Hat Enterprise Linux 6 with Python 2.6
- Red Hat Enterprise Linux 7 with Python 2.7
- Red Hat Enterprise Linux 8 with Python 3.6
- Microsoft Windows 10 Pro with Python 2.7
- Microsoft Windows Server 2012 R2 and 2016 with Python 2.7
AMQ Python is supported in combination with the following AMQ components and versions:
- All versions of AMQ Broker
- All versions of AMQ Interconnect
- All versions of AMQ Online
- A-MQ 6 versions 6.2.1 and higher
For more information, see Red Hat AMQ 7 Supported Configurations.
1.3. Terms and concepts
This section introduces the core API entities and describes how they operate together.
Table 1.1. API terms
A top-level container of connections.
A channel for communication between two peers on a network. It contains sessions.
A context for sending and receiving messages. It contains senders and receivers.
A channel for sending messages to a target. It has a target.
A channel for receiving messages from a source. It has a source.
A named point of origin for messages.
A named destination for messages.
An application-specific piece of information.
A message transfer.
AMQ Python 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.4. Document conventions
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