Technical Stuff

Start from basics

INTRODUCTION TO JBOSS

INTRODUCTION TO JBOSS
INTRODUCTION TO JBOSS
5 (100%) 5 votes

Every One ! Today we will go through Introduction to Jboss.

So, Lets begin !!!

JBOSS

As most of the organization still use JbossEAP 5, so lets start from JbossEAP 5.

JBoss Enterprise Application Platform is an open source  and based on Java Enterprise Edition (J2EE) services. JBoss Enterprise Application Platform is cross platform. It is used on any operating system that supports Java. The JBoss Enterprise Application Platform was developed by JBoss, now a division of Red Hat.

DIRECTORY STRUCTURE

bin Contains scripts for starting and stopping the server.
client Contains JAR files and configuration files needed to run a Java client.
server The JBoss server configuration are located under the server directory. The default server configuration set is the server/default set.
lib Contains JAR Library files used to run Jboss microkernel.
conf The conf directory contains server configuration files.
data The data directory is available for use by services that want to store content in the file system.
deploy It is use to deploy the application
lib It contain library files.
log It contain log files.
tmp The tmp directory is used by JBoss to store temporarily files such as unpacked deployments.

DIFFERENT TYPES OF PROFILES

Default

It is a  JavaEE 5 server profile.  Has most frequently used EE services. Default does not include JAXR, IIOP, clustering services.

All :

It is a bundles all services (including  clustering and RMI/IIOP).

Production:

It is based on “all” profile, tuned for production; with log verbosity reduced, deployment scanning every 60 seconds, and memory usage tuned to accommodate production deployment requirements.

It is based on ‘all’ profile and is a fully certified Java EE 5 configuration.

Web :

It is lightweight configuration created around JBossWeb and provides services required for web application deployment and a subset of Java EE technologies. Does not include JBoss Transaction JTS or XTS, Enterprise Java Bean 1.x or 2.x capabilities, JBoss Messaging, JCA, or JBoss IIOP

Minimal:

It is bare minimum required to start. Includes logging, JNDI and URL deployment scanner. Use JMX/JBoss to start your own services.  No web container, EJB or JMS support is included.

Happy Learning !!!

If you have doubt or queries, you can definetely comment us or can mail us on [email protected]

If you have any recommedation for future blog, You can email us on [email protected]

Top Searches :

1.Introduction to Middleware
2. Installation of Jboss
3. Log4j
4. Heap Dump
5. Thread Dump
6. VAPT – Disabling Apache Coyoto
7. VAPT – HTTP Methods

6 thoughts on “INTRODUCTION TO JBOSS

Leave a Reply

%d bloggers like this: