Thursday, June 6, 2013

JBoss 7 Directory Structure

In this article we will see the Directory Structure of JBoss 7.When we extract the Zip package we see the following Directory Structure

bin : contains all the scripts that are necessary in starting , stopping the JBoss Server Instance. There are separate scripts for starting a Domain as well as a Stand alone Instances.

Bundles : Contains OSGI Bundles
docs/schema : Schema Definition Files
modules :AS 7 is based on a modular classloading architecture. The various modules used in the server are stored here.
welcome-content :Default Welcome Page content

There are 2 other important Directory available .

Stand alone

In "standalone" mode each JBoss Application Server 7 instance is an independent process.The necessary files needed for running this Stand alone process can be found under the /standalone directory

Configuration : Configurations files for running a Stand alone server are available in here.
Data : Persistent information written by the server to survive a restart of the server
deployments : All Deployments go in Here.
lib/ext : Location for installed library jars referenced by applications using the Extension-List mechanism
log : standalone server log files
tmp : location for temporary files written by the server

Collections of multiple servers that can be called as a Domain. These configuration files for the Domain are available in this locations

Besides the AS instances, two more processes are created:
the Domain Controller which acts as management control point of the domain
Host Controller which interacts with the domain Controller to control the lifecycle of the AS instances running on that Host.

The configuration files, deployment content and writeable areas used by domain mode processes run from a JBoss Application Server 7 installation are found in the following subdirectories under the top level "domain" directory

configuration : Configuration files for the Domain and Host Controller are available in here .Information about the servers running n this domain are also available in here
Content : an internal working area for the Host Controller that controls this installation. This is where it internally stores deployment content. This directory is not meant to be manipulated by end users.
lib/ext : Location for installed library jars referenced by applications
log : Location where the Host Controller process writes its logs. The Process Controller, a small lightweight process that actually spawns the other Host Controller process and any Application Server processes also writes a log here.
Servers : Writable area used by each Application Server instance that runs from this installation. Each Application Server instance will have its own subdirectory, created when the server is first started. In each server's subdirectory there will be the following subdirectories:
data {-}- information written by the server that needs to survive a restart of the server
log {-}- the server's log files
tmp {-}- location for temporary files written by the server

Starting a Stand alone Server

We can start the Stand alone Jboss by running the


JBoss Bootstrap Environment

JBOSS_HOME: /soa/jboss-as-7.1.1.Final

JAVA: /usr/jdk1.6.0_14/bin/java

JAVA_OPTS: -server -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml


17:24:56,147 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:24:56,506 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:24:56,587 INFO [] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:24:57,835 INFO [org.xnio] XNIO Version 3.0.3.GA
17:24:57,839 INFO [] JBAS015888: Creating http management service using socket-binding (management-http)
17:24:57,865 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
17:24:57,891 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
17:24:58,018 INFO [] JBAS011502: Removing bootstrap log handlers
17:24:58,022 INFO [] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
17:24:58,054 INFO [] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
17:24:58,110 INFO [] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
17:24:58,149 INFO [] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
17:24:58,156 INFO [] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
17:24:58,242 INFO [] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
17:24:58,262 INFO [] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final
17:24:58,425 INFO [] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
17:24:58,566 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--
17:24:58,613 INFO [] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:24:58,692 INFO [] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
17:24:58,707 INFO [] (MSC service thread 1-4) JBAS011802: Starting Naming Service
17:24:58,824 INFO [] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
17:24:59,410 INFO [] (MSC service thread 1-3) JBAS017100: Listening on /
17:24:59,418 INFO [] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /soa/jboss-as-7.1.1.Final/standalone/deployments
17:24:59,426 INFO [] (MSC service thread 1-4) JBAS017100: Listening on /
17:24:59,523 INFO [] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
17:24:59,541 INFO [] (Controller Boot Thread) JBAS015951: Admin console listening on
17:24:59,541 INFO [] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 4188ms - Started 133 of 208 services (74 services are passive or on-demand)

Once we see the “Started” message .we are sure that the Server is Up and running.We can also start another profile using

./ --server-config=standalone-full.xml

We can also start the Server in only admin mode for performing the admin tasks like
./ --admin-only

Here are the Basic Screens

Happy Learning :-)