Red Hat SummitRed Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Este contenido no está disponible en el idioma seleccionado.
Appendix A. Required JARS
Overview
To simplify deploying Red Hat JBoss A-MQ 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 Red Hat JBoss A-MQ 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 Red Hat JBoss A-MQ
The following JARs are installed with JBoss A-MQ and must be placed on the broker's
CLASSPATH:
activemq-broker.jaractivemq-client.jaractiveio-core.jarslf4j-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.jarfrom Oracle - your JEE container's installation
- the Geronimo specs JARs:
geronimo-spec-jms.jargeronimo-spec-jta.jargeronimo-spec-j2ee-management.jar
Persistent messaging JARs
If you want to use persistent messaging you will need to add JARs to the broker's
CLASSPATH for the desired persistence store. The JAR names follow the pattern activemq-store-store. The following message stores are included:
activemq-amq-store.jaractivemq-jdbc-store.jaractivemq-kahadb-store.jaractivemq-leveldb-store.jar
Additionally, you will need to include any other JARs required by the persistence manager used by the store:
- For KahaDB you will need
kahadb.jar. - For JDBC you will need the JARs for your database's JDBC driver.
