Directory structure

A standard JBoss installation includes the following directories immediately below the top directory <jboss-home>, as shown in Figure 2.1:

bin
It contains all the executable files (both scripts and JARs) included in the JBoss distribution to
- start the server with a Batch (MS-Windows) or Shell (Unix) script.
- run the EJX deployment descriptor editor by double-clicking on it (if your platform supports this) or issuing the command java -jar ejx.jar
- run the EJB Verifier in Ant.
- monitor EJB caching.
lib and lib/ext
These two directories contain java libraries in JAR format that JBoss uses. The lib directory contains JARs that need to be in the system class path; the JARs in lib/ext are made available to the JBoss server MLet-based classloader.
If there is a need to add some java libraries to JBoss, like JDBC driver JARs, for example, these should be dropped in the lib/ext directory to be picked up by JBoss automatically.
db
Directory containing other directories with files related to the Hypersonic and Instantdb databases (configuration, indexing, tables, etc.) as well as queue files belonging to JBossMQ, the JMS provider.
deploy
This is the deployment directory. Just drop your JAR and EAR files here and they will be deployed automatically.
log
The JBoss log files are located in this directory. File logging is turned on by default.
conf
The JBoss configuration set(s) are located here. By default there is only one configuration set, located in subdirectory default. Adding more than one configuration set is permitted. The bundled installation of JBoss with a web container (either Tomcat or Jetty) creates an additional configuration set (tomcat or jetty). See the section called “Configuration files” for more details.
client
This is the directory where libraries required for clients are placed. A typical client requires jboss-client.jar, jbosssx-client.jar, jaas.jar, jnp-client.jar, ejb.jar and jta-spec1_0_1.jar. If your client is not running JDK 1.3, it will require jndi.jar as well. If you are going to be using the JBossMQ JMS provider, you will also need jbossmq-client.jar.
docs
It contains the JBoss API documentation, Javadoc-style, and other documentation in HTML format.
external
It contains the libraries jboss-util.jar and metadata.jar.
src
Under this directory you will find the full tree of Java classes, in source form, that make up JBoss.
tmp
This is a work directory used by the AutoDeployer to store files temporarily.

Figure 2.1. Distribution directory layout