What is Jboss

{ What New in Jboss,JBOSS server type}

Jboss version
Clients which using Jboss in our environment
Jboss vs other application server
application server v/s web server
how to install jboss
Standalone mode v/s Domain mode
overview of jboss directory structure
how to access jboss from server end {{{ How to Manage Jboss}}}
User Management
Network and Port configuration
how to create instance
how to deploy code on instance
Datasource Management
JVM
thread dump and heap dump

What is JBOSS:
Jboss is Enterprise Application Platform Software commonly called as EAP built on
open standard and compliant with Jave EE.
EAP implement java EE 6 specification and compliant with various profiles that are
defined in java EE 6.

In 2006 Apr Redhat acquired Jboss

What New in Jboss

##############

JBOSS = java bean open source software

Cloud ready architecture
Fast : Services are started concurrently to eliminate unneccessary delays
Simplified Configuration files : All of the configuration for an EAP instance now
appears in at most two files .doman .xml , host.xml --- domain mode
standalone.xml--standalone
Light weight : memory footprint of jboss is very less compared to previous version
New Management tool : EAP has two new tools command line interface
management console
Jboss EAP can be implemented in two ways Domain mode(centralized
management ) and standalone(single server) mode.

JBOSS Servers type:

1.Community Version (Java AS or Wildfly)
2.Enterprise Version (EAP =Enterprise Application Platform)

Jboss version
Though there are earlier versions of JBoss like JBoss 1.0 and JBoss 2.0, the first stable release of JBoss
is JBoss 3.0. The different versions of JBoss starting from JBoss 3.0 are listed below:

JBoss 3.0: The JBoss 3.0 was the stable release of JBoss. There were several releases in JBoss
3.0 series. The last stable release in the 3.0 series was JBoss 3.0.8 and it was released on 6th June
2003.

JBoss 3.2: The next release of JBoss was JBoss 3.2. There were several releases in this series
namely JBoss 3.2.1, JBoss 3.2.2 and so on. The last stable release in the series was JBoss
3.2.8SP1 and it got released on 2nd March 2006.

JBoss 4.0: The JBoss 4.0 had many releases in the series, namely JBoss 4.0.0, JBoss 4.0.1
SP1 and so on. The last stable release in the JBoss 4.0 series was JBoss 4.0.5. The JBoss 4.0.5
got released on 18th October 2006.

JBoss 4.2: JBoss 4.2 had many releases in this series namely JBoss 4.2.1, JBoss 4.2.2 and so
on. The stable release in the series was JBoss 4.2.3 and JBoss 4.2.3 got released on 18th July
2008.

JBoss 5.0: JBoss 5.0.1 was the last stable release in the series of JBoss 5.0. JBoss 5.0.0 Beta1,
JBoss 5.0.0 Beta 2 and many other releases happened in this JBoss 5.0 series. JBoss team has
also released JBoss 5.0.0 CR1 releases before the final release of JBoss 5.0.1.

JBoss 5.1: JBoss 5.1 had three releases in the series namely JBoss 5.1.0 Beta1, JBoss 5.1.0
CR1, JBoss 5.1.0. The last sable release in this series was JBoss 5.1.0 and it was released on 23rd
May 2009.

JBoss 6.0: JBoss 6.0 had many releases in the series, they are: JBoss 6.0.0 M1, JBoss6.0.0 M2
and so on. The last stable release in the series was JBoss 6.1.0 final; this was released on 16th
August 2011.

JBoss 7.0: JBoss 7.0 had many maintenance releases in the series namely JBoss 7.0 Alpa1,
JBoss 7.0 Beta1, JBoss 7.0 Beta 2 and so on. The final stable release in the series was JBoss 7.0.2
and it got released on 22nd September 2011.

Clients which using Jboss in our environment

Bestbuy using Jboss-eap-5.1
Sephora US using jboss-eap-4.3
Sephora SA using jboss-eap-4.x
Vitamin Shoppe using jboss-eap-4.x
Finishline using jboss-eap-4.x
Where x is representing minor version of jboss example :4.0,4.1..4.3 etc

Jboss vs other application server

Jboss is leaves very less memory foot print when compared to other app server
Fast: service are started concurrently to eliminate unnecessary waits and leverage
multicore processor ,While non-critical services remain passive until first use.
Simplified configuration files: EAP instance now appears in atmost two
configuration files (standalone and domain.xml and host.xml)
Domain :Domain mode allow you to deploy and manage eap instances in multi
server topology .
Modular:EAP6 has small core which can be plug in and plug out as per
requirement.
New Management tools: Management console (web) and Command line interface
or native interface .

Redhat provides free subscription for one year and provide support for production
issue for one year.
Once the subscription completes the jboss application server continue to work but
the production support will not be provided by Redhat .How ever we can still enjoy
the community support.

Difference between web server and application server.

Comparison chart
Application Server
A server that exposes business logic to
What is it? client applications through various
protocols including HTTP.
Application server is used to serve web
based applications and enterprise
Job based applications(i.e servlets, jsps and
ejbs...). Application servers may
contain a web server internally.

Web Server
A server that handles HTTP
protocol.
Web server is used to serve web
based applications.(i.e servlets
and jsps)

Application Server
To deliver various applications to
another device, it allows everyone in
the network to run software off of the
Functions
same machine.

Supports distributed transaction and EJB's

Resource
utilization

High.

Web servers are suited for static content.

App server are suited for dynamic content.

Jboss installation :
*

Methods of installation :

1.Extracting the ZIP download.

2.Via Java jar file installation.

3.RPM installation.

##################

Web Server
Keeping HTML, PHP, ASP etc
files available for the web
browsers to view when a user
accesses the site on the web,
handles HTTP requests from
clients.
Servlets and JSP
Low

Standalone mode v/s Domain mode

Domain Mode:
Domain mode is the way with which you can manage multiple hosts from single
location (Referred to as managed domain ) .Domain controller process acts as
central management control point communicating with various host controllers in
the domain .
All of the hosts share a common management policy and the domain controller
ensures that each server is configured according to that policy .
Domain controller also reffered to as the master and the other hosts in the domain
are referred to as slaves.
Domain crontoller is configured in file named domain.xml each host can have
specific configuration which is in a file named host.xml

When host starts its setting from host.xml are combined with settings from
domain.xml on the domain controller

Standalone mode :
If central management capabilities of domain mode not required the option left for
us is Standalone mode.
EAP can be deployed in standalone mode which is similar to previous versions of
jboss EAP.
Standalone is ideal for running a single instance of EAP with single server.
Configuration file: EAP_HOME/standalone/configuration/standalone.xml

Important :

Only difference between standalone and domain mode is the management

capabilities .EAP features like clustering , HA , failover and other Java EE
technologies are all available in either standalone or domain mode.

The Management Console and Management CLI are brand new interfaces for
managing your domain
or standalone JBoss Enterprise Application Platform 6 instance. There is no longer
any need to edit
XML configuration files by hand. The Management CLI even offers batch mode, so
that you can script
and automate management tasks

Application security, including security domains, are managed centrally for

simplified configuration.

overview of jboss directory structure :

The directory layout of JBoss Enterprise Application Platform 6 has been simplified. T
he m odules/
directory now contains the application server modules, instead of using common
and server-specific
lib/ directories. T he dom ain/ and standalone/ directories contain the artifacts and
configuration files for domain and standalone deployments.

The classloading mechanism has been made completely modular, so that modules
are loaded and
unloaded on demand. This provides performance and security benefits, as well as
very fast start-up
and restart times

Datasource management is streamlined. Database drivers can be deployed just like

other services.
In addition, datasources are created and managed directly in the Management
Console or
Management CLI.

JBoss Enterprise Application Platform 6 starts and stops very quickly, which is
especially beneficial
to developers. It uses fewer resources and is extremely efficient in its use of system
resources.

Manage the Application Server

####################
Editing the XML files
Managing via Admin console
Managing via CLI or Native Console.

###################
2.2. Installation Structure and Details
appclient

Application Client Container:

The Application Client Container (ACC) includes a set of Java classes, libraries, and
other files that are required for and distributed with Java client programs that
execute in their own Java Virtual Machine (JVM). The ACC manages the execution of
Java EE application client components (application clients), which are used to access
a variety of Java EE services (such as JMS resources, EJB components, web services,
security, and so on.) from a JVM outside the Oracle GlassFish Server.

The ACC communicates with the GlassFish Server using RMI-IIOP protocol and
manages the details of RMI-IIOP communication using the client ORB that is bundled
with it. Compared to other Java EE containers, the ACC is lightweight.

bin directory:
contains the binary files which are used to start up the jboss.

###########
bundles directory :
Contains OSGi bundles which pertain to JBoss
Enterprise Application Platform 6 internal
functionality.

#######

docs/

License files, schemas, and examples.

#########
domain/

Configuration files, deployment content, and

writable areas used when JBoss Enterprise Application Platform 6 runs as a
managed domain.
#########
modules/

Modules which are dynamically loaded by JBoss Enterprise Application Platform 6

when services request them.

#########
standalone/
Configuration files, deployment content, and writable areas used when JBoss
Enterprise Application Platform 6 runs as a standalone
server.
#########
welcome-content/
Contains content used by the Welcome web
application which is available on port 8080 of a
default installation.
######

Directory under domain

configuration/
Configuration files for the managed domain.

These files are modified by the Management

Console and Management CLI, and are not meant
to be edited directly.
######################

data/
Information about deployed services. Services are
deployed using the Management Console and
Management CLI, rather than by a deployment
scanner. Therefore, do not place files in this
directory manually.
log/ Contains the run-time log files for the host and
process controllers which run on the local
instance.
servers/
Contains the equivalent data/, log/, and tmp/ directories for each server instance in
a domain,
which contain similar data to the same directories within the top-level dom ain/
directory. tmp/ Contains temporary data such as files pertaining to the shared-key
mechanism used by the Management CLI to authenticate local users to the
managed domain.

User Management

Network and Port configuration

<interface> element is used to define an interface using

the <interface> child element .

Management iP:
Public ip :
Unsecure ip or native ip:
T he first example shows a specific inet-address value specified for both the
management and public relative name groups.
Example 5.1. An interface group created with an inet-address value
<interfaces>
<interface nam e="m anagem ent">
<inet-address value="127.0.0.1"/>
</interface>
<interface nam e="public">
<inet-address value="127.0.0.1"/>
</interface>

</interfaces>
In the following example a global interface group uses the any-address element to
declare a wild-card
address.
Example 5.2. A global group created with a wild-card declaration
<interface nam e="global">
<!-- Use the wild-card address -->
<any-address/>
</interface>
T he following example declares a network interface card under a relative group with the
name
external.
Example 5.3. An external group created with an NIC value
<interface nam e="external">
<nic nam e="eth0"/>
</interface>

how to create instance