About setting up runtime utilities on JBoss

JBoss JMS requires that the files listed here be added to your classpath.

Note: The classpath information provided in this section is intended as a starting point for your implementation. Depending upon the JMS, JNDI, and JDK you are using you may need to add or remove jars from the lists given here.

If you are using JBoss JMS, add the following jars in the classpath using the <INSTALL_DIR>/bin/install3rdparty script:

  • javassist.jar
  • jboss-aop-client.jar
  • jboss-common-core.jar
  • jboss-logging-log4j.jar
  • jboss-logging-spi.jar
  • jboss-mdr.jar
  • jboss-remoting.jar
  • jnp-client.jar
  • trove.jar
  • jboss-serialization.jar
  • jboss-messaging-client.jar

Do not include any *ui.jar files.

  • If you are using the JBoss Messaging, add the jbossmq-client.jar in the classpath using the <INSTALL_DIR>/bin/install3rdparty script. This is for agents only - do not add JBoss jars to APPdynamicclasspath.cfg.
  • If you are using JBoss application server, add the log4j.jar file from JBoss at the beginning of your CLASSPATH.
  • If you are invoking a JSP page for the first time, there may be a short delay while the JBoss application server compiles the JSP page. To avoid this delay, precompile the JSP files before creating the smcfs.ear file.