|
Page Edited :
qpid :
Getting Started Guide
Getting Started Guide has been edited by Carl Trieloff (Apr 12, 2008). Content:Installing & Using Qpid (Java)IntroductionThe information below details how to install and use the main Broker and Client packages. Essentially, to make use of the Qpid AMQP infrastructure you need to be able to run a broker instance to handle messaging traffic and talk to your client code. Your own application code will make use of the Qpid client package provided to interface with the broker. Related pages to get you going PrerequisitesThe Qpid broker requires Java 5 or later to be available. For maximum performance Java 6 is recommended. The Java JMS client can be run using Java 1.4, 5 or 6. Note that the 1.4 client libraries come in a separate package. Downloading & Installing QpidThe latest binary and source distributions of Qpid Broker and Client packages are available from the downloads page. If you want to use a newer version than an official release then you should check out the code from the Subversion repository and then consult the Build How To page. Broker InstallUnpack the archive into any directory of your choice e.g c:/qpid Once unpacked, the package will be installed in a directory with a release label (i.e. qpid-1.0-incubating-M2) and the directories underneath should look something like this: /bin Contains various startup utilities: qpid-server is a bash script which runs the broker on linux/unix. You should set the environment variable QPID_HOME to point at your install path e.g. C:/qpid/qpid-1.0-incubating-M2. This enables the startup script to find default config files in the installed etc directory. qpid-run is a script which allows shell commands to be executed which the qpid-server script utilises. qpid-server.bat is a dos script which runs the broker on Windows. See note above about QPID_HOME. The other scripts in this directory can be safely ignored for now. /lib Contains all the jars used by the broker, mainly in their own subdirectories. The broker-launch.jar contains a manifest file which puts the requisite jars into the classpath for broker startup. Other files & jars in here can be safely ignored for now. /etc Contains the config files used by the broker on startup. /client This comes with the broker package at the moment and contains the client package. The client can also be downloaded independently. See client section below for details. /doc Contains javadoc for the broker. If running on a unix or linux platform check that the appropriate permissions have been applied to the .sh scripts. If not, then update i.e. chmod 755 *.sh Client Only InstallDownload the qpid-client-<build#>.zip or qpid-client-<build#>.tar.gz package as appropriate for the platform you are installing on. Once you have downloaded the package then unpack it into a directory i.e. c:/qpid-client Once unpacked, the package will be installed in a directory with a release label (i.e. qpid-0.9) and then under the client directory should look something like this: /lib This dir contains all the jars needed by the client code and the client jars themselves. /doc Contains javadoc for the client code. Environment VariablesSetting JAVA environmentYou must make JDK 1.5 available by setting the JAVA_HOME environment variable and adding the JAVA_HOME/bin directory to your PATH. To check that you have completed this change successfully, simply type java -version You should see something like java version "1.6.0_02" The Qpid scripts set the classpath and other flags required for the broker to run. Configuring PersistencePlease visit our 3rd Party Libraries page to get more information on how to set up your chosen persistence implementation for Qpid. Running the Qpid BrokerThere are scripts provided to run the broker on Windows and on Linux/Unix. Running the Qpid Broker on Linux/Unix
Command Line ArgumentsYou can get a list of all command line arguments by using the -h argument. In particular, -p overrides the port specified in the config file and -b overrides the bind interface (default is wildcard). Checking the broker has started upYou can check that the broker has started up successfully by viewing the output it sends to stdout and looking for the start up port info: Note that you may have to edit the log4j.xml in the /etc directory to add an appender for the server.Main class to see loggeds output like this on startup. Running the Qpid Broker on WindowsSimply set the QPID_HOME variable and run the .bat script. All other details as identical to running on Linux/Unix. So for example: Getting HelpYou can view our FAQ and Troubleshooting Guide for assistance. If you can't find the information that you need there, then email our qpid users list |
Unsubscribe or edit your notifications preferences
