Chapter 2. JBoss Enterprise Application Platform Overview

JBoss Enterprise Application Platform 5 is an open-source JEE-based middleware solution. It is built on top of the consolidated JBoss Application Server 5 called JBoss Enterprise Application Server, which introduces the JBoss Microcontainer.
The JBoss architecture essentially consists of the microcontainer, bootstrap beans loaded into the microcontainer, a collection of deployers for loading various deployment types, and various MBean (*-jboss-beans.xml) and legacy MBean (*.jboss-service.xml) deployments. For more information refer to the Administration and Configuration Guide.

Important

In this guide, we assume you have set up your environment and installed JBoss Enterprise Application Platform. If this is not the case, refer to the Installation Guide.

2.1. Server Profiles

JBoss Enterprise Application Server, the core of JBoss Enterprise Application Platform, can be run with different basic configurations. The configuration are based on server profiles. A profile defines which services and components are available for the server instance of that profile. JBoss Enterprise Application Platform is shipped with predefined profiles; however, you can customize these profiles, remove and add individual services and components to them, as well as to create your own profiles (refer to the Administration and Configuration Guide).
The following JBoss Enterprise Application Server profiles are delivered with the product and located in the <JBOSS_HOME>jboss-as/server/ directory:
all
The all profile covers all available services and components, including the RMI/IIOP and clustering services, which are not loaded in the default configuration.
default
The default profile is a base Java EE 5 server profile containing a default set of services. It covers the most frequently used services required to deploy a Java EE application. The JAXR service, the IIOP service and the clustering services are not included. This profile is applied if a server is started without specifying a configuration.
production
The production profile is based on the all profile and is intended for production. It has a reduced log verbosity, deployment scanning takes place every 60 seconds, and memory usage is tuned to accommodate production deployment requirements.
minimal
The minimal profile uses the minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. You can use it when using JMX/JBoss to start your own services without any other Java EE 5 technologies. It starts only the server: no web container, EJB, or JMS support is available.
standard
The standard profile is the JavaEE 5 certified configuration of services.
web
The web profile is a lightweight web-container oriented profile that previews the JavaEE 6 web profile.
The default profile is used if you do not specify a configuration when running a server.