ActiveMQ (original) (raw)

Using ActiveMQ Classic > Initial Configuration

Initial Configuration

Firstly you need to add the jars to your classpath.

Required JARs

To make ActiveMQ Classic 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 Classic here is the full list of individual jars required

If you want to grab a J2EE specification jar we recommend the Apache repository

Optional JARS

Persistence Support

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.

In 5.x you can do this by setting the persistent=false property to false either in the Xml Configuration or on the broker URL.

Next steps

One of the first things you might want to do is start a broker. Once you have a broker running you could try some example programs

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 Classic.

Additional Resources

Specifications