2.1.1. JBoss Top Level Directory Structure

Installing creates a top level directory, which will be named jboss-eap-4.2 if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the JBOSS_DIST directory. There are four sub-directories immediately below this:

doc: contains the product documentation.
jboss-as: contains sub directories that contain server start scripts, JARs, server configuration sets and working directories. You need to know your way around the distribution layout to locate JARs for compiling code, updating configurations, deploying your code, etc.
seam: contains the files for Hibernate and the JBoss Seam Framework.
Uninstaller: contains the uninstaller program uninstaller.jar.

Below is the layout of the installation directory of . In the figure, the default server configuration file set is shown expanded. In a clean installation, within the server/default directory only the conf, deploy, and lib directories exist. The data, log, tmp and work sub-directories are created by JBoss and won’t exist until you’ve run the server at least once. Section 2.3, “Starting and Stopping the Server” will teach you to run the server.

jboss-eap-4.2                            // jboss.home_url
	|+ doc
	|+ jboss-as
		|+ bin
		|+ client
		|+ docs
		|+ icons
		|+ lib                              // jboss.lib.url
		|+ scripts
		|+ server
			|+ all                          // jboss.server.name
			|+ default                      // jboss.server.home.url
				|+ conf                     // jboss.server.config.url
				|+ deploy
				|+ lib                      // jboss.server.lib.url
				|+ data
				|+ log
				|+ tmp
				|+ work
			|+ minimal
			|+ production
	|+ seam
	|+ Uninstaller                      // jboss.uninstaller.url

Several of the locations may be overridden. For these locations, the org.jboss.system.server.ServerConfig interface constant and its corresponding system property string are shown in the figure. The names ending in URL correspond to locations that can be specified using a URL to access remote locations, for example, HTTP URLs against a web server.