Required JARS

Overview

To simplify deploying Fuse MQ Enterprise it is recommended that you place the activemq-all.jar file on the broker's CLASSPATH. It contains all of the classes needed by a message broker. This is the default set up for a Fuse MQ Enterprise installation.

However, if you want more control over the JARs in the broker's CLASSPATH you can add the individual JARs. There are several JARs that are required. In addition, there are a few that are only needed when certain features are used.

Required JARs from Fuse MQ Enterprise

The following JARs are installed with Fuse MQ Enterprise and must be placed on the broker's CLASSPATH:

activemq-core.jar
activeio-core.jar
slf4j-api.jar

JEE JARs

The JARs containing the JEE APIs are also required by the broker. These could be located in one of the following locations:

the jee.jar from Oracle
your JEE container's installation
the Geronimo specs JARs:
- geronimo-spec-jms.jar
- geronimo-spec-jta.jar
- geronimo-spec-j2ee-management.jar

Feature specific JARs

If you want to use persistent messaging you will need to add JARs to the broker's CLASSPATH for the desired persistence manager.

For KahaDB you will need kahadb.jar.

For JDBC you will need the JARs for your database's JDBC driver.

Comments powered by Disqus