All directories referred to in the next section are relative to <jboss-home> i.e top directory of the JBoss installation. As shown in Figure 2.1. directories are the following:
All the binaries included with JBoss distribution are located in this directory. Using the Batch (Windows) or Shell (UNIX) scripts here, you can start the server. You can also run the EJX deployment descriptor editor by double-clicking on it (if your platform supports that) or issuing the command: java -jar ejx.jar
The two directories contain java libraries in jar and zip format that JBoss uses. There is a split between those libraries which had to be in the system classpath (.ie jars in lib directory) vs the other ones in lib/ext directory that are made available to the JBoss server MLet based classloader.
If there is a need to add some java libraries to JBoss, for example jdbc driver jars, these should be dropped in lib/ext directory and will be picked up by JBoss automatically.
Directory containing hypersonic and instantdb databases related files (configuration files, indexing tables etc ) as well as JBossMQ - JMS provider message queue files.
This is JBoss's deployment directory. Just drop your jars here and they will be deployed automatically.
JBoss log files are located in this directory. File logging is turned on by default.
JBoss configuration set(s) are located here. By default there is only one configuration set - "default". Adding more than one configuration set is permitted. See the section called “Configuration files” for more details.
Libraries required for clients are in the client directory. A typical client requires jboss-client.jar, jbosssx-client.jar, jaas.jar, jnp-client.jar, ejb.jar, and jta-spec1_0_1.jar. If you client is not running JDK 1.3, it will require jndi.jar as well. If you are going to be using JBossMQ JMS provider you will also need jbossmq-client.jar.