JBoss install directory structure
The binary distribution unpacks into a top-level JBoss install directory, often referred to as the JBOSS_DIST directory. There are four sub-directories immediately below this:
NOTE: Some directories are dynamically created when you start JBoss. Some directories may not exist in
bin: contains various scripts and associated files. This is where the run and shutdown scripts, which start and stop JBoss, reside.
client: stores configuration and jar files which may be needed by a Java client application or an external web container. You can select archives as required or use jbossall-client.jar.
docs: contains useful information
docs/dtd: contains the XML DTD used in JBoss for reference (these are also a useful source of documentation on JBoss configuration specifics).
examples: contains optional configurations:
bindingmanager: example configuration for the binding service for running multiple copies on jboss with different ports on the same machine.
jca: example JCA configuration files for setting up datasources for different databases (such as MySQL, Oracle, Postgres) and access to legacy EIS systems.
jms: example configurations for different jbossmq persistence, state manager and connection factorys
standalone: a script to make a minimal jbossmq server configuration
jmx: additional and legacy management deployments
netboot: a web application used when netbooting jboss
remoting: an early access of the remoting service from JBoss4
tomcat: scripts for installing different versions of Tomcat
varia: additional services
loadbalancer: a deployment for running jboss as a http loadbalancer
lib: jar files which are needed to run the JBoss microkernel. You should never add any of your own jar files here.
server: each of the subdirectories in here is a different ServerConfiguration. The configuration is selected by passing the option -c <config-name> to the run script.
<config-name>: a server configuration started with the -c <config-name> option
conf: configuration files including the bootstrap services in jboss-service.xml
props: default users/roles properties files for the jmx console (from 4.0.2)
xmdesc: XMBean descriptors for those MBeans with extended descriptions
lib: static jar files for the services
deploy: services and applications that are hot deployed
data: data files that survive reboot
tmp: temporary files that do not survive reboot
work: work files for Tomcat
minimal: a minimal jndi and jmx kernel
default: the default configuration (does not include clustering or corba)
all: all services including clustering and corba
farm: deployments in here are hot deployed across the cluster
deploy-hasingleton: deployments in here are only run on one node in the cluster at a time