Firstly you need to add the jars to your classpath.
To make ActiveMQ easy to use, the default activemq-all.jar comes complete with all the libraries required. If you prefer to have explicit control over all the jars used by ActiveMQ here is the full list of individual jars required
- activemq-kahadb-store.jar (if you wish to use persistence)
- J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo’s freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows…
If you want to grab a J2EE specification jar we recommend the Apache repository
- spring.jar - if you wish to use the XML configuration file for configuring the Message Broker
- if you wish to use message persistence then you need to add a persistent jar to your classpath (see below). If you just want a lightweight message bus with no durability you can leave this step out but we highly recommend persistence for production deployments.
We support persistence via Specialized KahaDB file system message store or JDBC. For full explict control over configuration check out the Xml Configuration. If you wish to use KahaDB, include kahadb.jar in your classpath. In case of JDBC you’ll need to include appropriate database driver.
If you’re just doing some testing or in-VM SEDA based messaging you may wish to disable persistence. You can use the Xml Configuration for this.
If you want to write your own application, you can just instantiate an ActiveMQConnectionFactory, configure its properties directly and then you’re ready to use the standard JMS API to create Connections, Sessions, MessageProducer and MessageConsumer instances.
You can also take a look at our unit tests for more examples on how to use ActiveMQ.
- Sun’s JMS Tutorial is a handy place to start looking at how to use the JMS API directly
- The ActiveMQ Website for specifics on how to use ActiveMQ
- ActiveMQ Topologies
- ActiveMQ Clustering
- ActiveMQ Network of Brokers
- Staged Event Driven Architecture (SEDA)