THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Getting the Bits.
To work out what to download or where to start Download
Running it / Administration
These sections show you how to run the brokers, basic configuration and management
- Running & Administration and getting started with the Java Broker
- Running & Administration for the C++ Broker
- Managing the C++ Broker
Making sure it runs correctly
For more details on starting the brokers, see Administration section.
The simplest way to check that the install is working correct is to try some of the examples. Each clients
has a set of examples included with it (or at least JMS, Java, C++ and Python do)
If working from svn, a good smoke test is to run the python tests as they can be run against
any version of AMQP and any broker.
To do so
export PYTHONPATH=~/qpid/python # or wherever you have it
./run-tests
.........EFF.... /.../ #each . is a test E is an error, F is a fail
#or to do a specific version
./run-tests
Options:
?/-h/-help : this message
s/-spec <spec.xml> : URL of AMQP XML specification or one of these abbreviations:
0-8 - use the default 0-8 specification.
0-9 - use the default 0-9 specification.
e/-errata <errata.xml> : file containing amqp XML errata
b/-broker [<user>/<password>@]<host>:<port> : broker to connect to
v/-verbose : verbose - lists tests as they are run.
d/-debug : enable debug logging.
i/-ignore <test> : ignore the named test.
I/-ignore-file : file containing patterns to ignore.
S/-skip-self-test : skips the client self tests in the 'tests folder'
F/-spec-folder : folder that contains the specs to be loaded
Finally, if developing in svn, each build system has tests integrated into the build system for that language