Firstly, verify that your JVM is installed properly by following these instructions.
Now chose a directory for Qpid broker installation. This directory will be used for the Qpid JARs and configuration files. It need not be the same location as the store used for the persistent messages or the log file (you will chose this location later). For the remainder this example we will assumed that location /usr/local/qpid has been chosen.
Extract the Qpid package qpid-java-broker-0.20.tar.gz into the directory.
mkdir /usr/local/qpid cd /usr/local/qpid tar xvzf qpid-java-broker-0.20.tar.gz>
The extraction of the Qpid package will have created a directory qpid-broker-x.x
ls -la qpid-broker-0.20/ total 152 drwxr-xr-x 8 qpid qpid 272 25 Jul 23:22 . drwxr-xr-x 45 qpid qpid 1530 30 Sep 10:51 .. -rw-r--r--@ 1 qpid qpid 65925 20 Jul 20:10 LICENSE -rw-r--r--@ 1 qpid qpid 3858 20 Jul 20:10 NOTICE -rw-r--r--@ 1 qpid qpid 1346 20 Jul 20:10 README.txt drwxr-xr-x 10 qpid qpid 340 30 Sep 00:24 bin drwxr-xr-x 9 qpid qpid 306 21 Aug 23:17 etc drwxr-xr-x 34 qpid qpid 1156 25 Jul 23:22 lib
Qpid requires a work directory. This directory is used for the default location of the Qpid log file and is used for the storage of persistent messages. The work directory can be set on the command-line (for the lifetime of the current shell), but you will normally want to set the environment variable permanently the user's shell profile file (~/.bash_profile for Bash etc).
If the directory referred to by QPID_WORK does not exist, the Java Broker will attempt to create it on start-up.
The broker has an optional message store implementations backed by Oracle BDB JE. If you wish to use these stores you will need to provide the optional Oracle BDB JE dependency. For more details, see Section 8.4, “BDB Store”