The Server Directory
all/ minimal/ node2/ web/ default/ node1/ standard/
- Known in JBoss AS JBoss.server.base.dir
- The root of server configuration sets
- JBoss comes with minimal, default and all
- Version 5.x comes with 2 new configurations: standard and web
- Defaults to the configuration set in server/default
- Configuration sets contain the actual JBoss services For example:
- To change the configuration set that JBoss AS runs with, execute: bin/run.sh -c <configuration-set>
Inclined to build a profession as JBOSS Developer?Then here is the blog post on" JBOSS Training "
bin/run.sh -c minimal bin/run.sh -call Configuration sets: minimal/
- Includes support for JNDI and logging. It does not contain any other J2EE services like Servlet/JSP container, EJB container, or JMS.
- Can serve as a starting point when creating your own configuration sets
- As the name implies, this is the default Java EE 5 configuration. Contains the most used services except JAXR, IIOP, and clustering services.
- This configuration extends the default configuration settings and also include JAXR, IIOP, and clustering services
- Certified Java EE 5 configuration is compliant. web/
- The major difference with the existing configurations is that call-by-value and deployment isolation is enabled by default, along with support for rmiiiop and juddi (taken from all config).
- Lightweight web container profile (Java EE 6 web profile). It provides support for JTA/JCA and JPA except for the servlet/JSP container.
The Server Configuration Sets
all/ minimal/ node2/ web/ default/ node1/ standard/ The currently running server/<server> dir is known in JBoss AS as JBoss.server.home.url. The name of the server (e.g. "default") is known as JBoss.server.name Configuration sets are independent of each other Each configuration set has to have at least the following four directories: conf/, deploy/, deployers/, and lib/. Other (referenced) directories such as data/, log/, tmp/, and work/ are automatically created on JBoss AS startup if they do not exist.
For an in-depth understanding on JBoss click on: