Chapter 1. Overview
AMQ OpenWire JMS is a Java Message Service (JMS) 1.1 client for use in messaging applications that send and receive OpenWire messages.
AMQ OpenWire JMS 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.
AMQ OpenWire JMS is based on the JMS client from Apache ActiveMQ.
1.1. Key features
- JMS 1.1 compatible
- SSL/TLS for secure communication
- Automatic reconnect and failover
- Distributed transactions (XA)
- Pure-Java implementation
1.2. Supported standards and protocols
AMQ OpenWire JMS supports the following industry-recognized standards and network protocols:
- Version 1.1 of the Java Message Service API.
- Modern TCP with IPv6
1.3. Supported configurations
AMQ OpenWire JMS supports the following OS and language versions:
Red Hat Enterprise Linux 6, 7, and 8 with the following JDKs:
- OpenJDK 8
- Oracle JDK 8
- IBM JDK 8
- Microsoft Windows 10 Pro with Oracle JDK 8
- Microsoft Windows Server 2012 R2 and 2016 with Oracle JDK 8
For more information, see Red Hat AMQ 7 Supported Configurations.
1.4. Terms and concepts
This section introduces the core API entities and describes how they operate together.
| Entity | Description |
|---|---|
|
| An entry point for creating connections. |
|
| A channel for communication between two peers on a network. It contains sessions. |
|
| A context for producing and consuming messages. It contains message producers and consumers. |
|
| A channel for sending messages to a destination. It has a target destination. |
|
| A channel for receiving messages from a destination. It has a source destination. |
|
| A named location for messages, either a queue or a topic. |
|
| A stored sequence of messages. |
|
| A stored sequence of messages for multicast distribution. |
|
| An application-specific piece of information. |
AMQ OpenWire JMS sends and receives messages. Messages are transferred between connected peers using message producers and consumers. Producers and consumers are established over sessions. Sessions are established over connections. Connections are created by connection factories.
A sending peer creates a producer to send messages. The producer has a destination that identifies a target queue or topic at the remote peer. A receiving peer creates a consumer to receive messages. Like the producer, the consumer has a destination that identifies a source queue or topic at the remote peer.
A destination is either a queue or a topic. In JMS, queues and topics are client-side representations of named broker entities that hold messages.
A queue implements point-to-point semantics. Each message is seen by only one consumer, and the message is removed from the queue after it is read. A topic implements publish-subscribe semantics. Each message is seen by multiple consumers, and the message remains available to other consumers after it is read.
See the JMS tutorial for more information.
1.5. Document conventions
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\...).
