What is JONAS_ROOT structure ?

JONAS_ROOT structure

JONAS_ROOT is the installation directory of JOnAS with the following structure :

deploy/ directory

The main location used for deployment.

At JOnAS startup, all deployment plans, Java EE archives and OSGi bundles are deployed in the following order : 

  1. Deployment plan repositories

  2. OSGi bundles

  3. RAR archives

  4. Deployment plan resources

  5. EJB archives

  6. WAR archives

  7. EAR archives

Note For each category, file names are chosen in alphabetical order.

bin/ directory

contains the scripts used to launch JOnAS (Unix and Windows scripts)

conf/ directory

contains the JOnAS configuration files.

examples/ directory

sub tree containing all the JOnAS examples

lib/ directory

Used for extending class loaders. It contains 5 sub directories : 

  1. bootstrap/  : Jars loaded by the JOnAS bootstrap

  2. common/  : Legacy directory where Ant tasks are stored

  3. endorsed/  : Jars overridding JVM libraries

  4. ext/  : For non-bundle extensions

  5. internal-ee-tld/  : Internal use only !

logs/ directory

where the log files are created at run-time (when the JONAS_ROOT is used as a JONAS_BASE)

templates/ directory

This sub tree contains the following subdirectories used by JOnAS during the generation process (eg, JONAS_BASE generation)

• conf/ is an empty template of the JONAS_BASE structure used by tools able to create a JONAS_BASE environment.
• newjb/ contains the configuration files for creating a JONAS_BASE environment.
• newjc/ contains the configuration files for creating a cluster environment.

repositories/ directory

This sub tree contains the following repositories used to store OSGi bundles, Java EE applications and deployment plans.

• maven2-internal/ contains both OSGi bundles and applications (jonasAdmin, documentation, ...) for JOnAS.
  It is used for internal purpose and should not be modified. This directory is structured as a Maven2 repository.
• url-internal/ contains the deployment plans of each JOnAS services. It is used for internal purpose and should not be modified.
• <repository-id>/ contains archives downloaded through deployment plans from this repository.