Chapter 2. Installation
2.1. Prerequisites
AMQ Broker requires the following components.
- JRE 8 (for running AMQ Broker)
- JDK 8 (for running the examples)
- Maven 3.2 (for running the examples)
Note that the broker runtime requires only a JRE. However, running the included examples requires a full JDK as well as Maven.
If you are installing AMQ Broker on a supported version of Red Hat Enterprise Linux, you can use the yum command to install any needed pre-requisites. For example, the command below installs OpenJDK 8 and Maven.
$ sudo yum install java-1.8.0-openjdk maven
You can also download supported versions of a JDK and Maven from their respective websites, OpenJDK and Apache Maven for example. Consult Supported Configurations to ensure you are using a supported version of Java.
2.2. Downloading an AMQ Broker Archive
A platform-independent, archived distribution of AMQ Broker is available for download from the Red Hat Customer Portal. See Using Your Subscription for more information on how to access the customer portal using your Red Hat subscription. You can download a copy of the distribution by following the steps below.
Procedure
- Open a browser and log in to the Red Hat Customer Portal at https://access.redhat.com/downloads/. The Product Downloads page is displayed.
- Find the category titled JBoss Integration and Automation containing a link to Red Hat AMQ Broker.
- Click the hyperlink Red Hat AMQ Broker. The Software Downloads page is displayed.
- Select the desired AMQ Broker version from the Version drop-down menu.
- On the Releases tab, click the Download link for the specific AMQ Broker file you want to download.
2.3. Installing on Linux
Prerequisites
You must first download the installation archive from the Red Hat Customer Portal.
Procedure
Create a new user named
amq-brokerand provide it a password.sudo useradd amq-broker sudo passwd amq-broker
Create the directory
/opt/redhat/amq-brokerand make the newamq-brokeruser and group the owners of it.sudo mkdir /opt/redhat sudo mkdir /opt/redhat/amq-broker sudo chown -R amq-broker:amq-broker /opt/redhat/amq-broker
Change the owner of the archive to the new user.
sudo chown amq-broker:amq-broker amq-broker-7.x.x-bin.zip
Move the installation archive to the directory you just created.
sudo mv amq-broker-7.x.x-bin.zip /opt/redhat/amq-broker
As the new user
amq-broker, extract the contents with a singleunzipcommand.su - amq-broker cd /opt/redhat/amq-broker unzip amq-broker-7.x.x-bin.zip
A directory named something similar to AMQ7-7.2-redhat-1 will be created. In the documentation this location is referred to as INSTALL_DIR.
2.4. Installing on Windows
Prerequisites
You must first download the zip version of the archive from the Red Hat Customer Portal.
Procedure
-
Use Windows Explorer to create the directory folder
\redhat\amq-brokeron the desired letter drive,C:for example. - Use Windows Explorer to move the installation archive to the new directory and extract it.
- Extract the file contents into a directory by right-clicking on the zip file and choosing Extract All.
A directory named something similar to AMQ7-x.x-redhat-1 will be created. In the documentation this location is referred to as INSTALL_DIR.
2.5. Archive Contents
The directory created by extracting the archive is the top-level directory for the AMQ Broker installation. This directory is referred to as INSTALL_DIR and includes a number of important directories noted in the table below.
Table 2.1. Contents of INSTALL_DIR
| If you want to find… | Look here… |
|---|---|
| API documentation |
|
| Binaries and scripts needed to run AMQ Broker |
|
| Configuration files |
|
| JMS and Java EE examples |
|
| Jars and libraries needed to run AMQ Broker |
|
| XML Schemas used to validate AMQ Broker configuration files |
|
| Web context loaded when AMQ Broker runs. |
|

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.