7.2. Standard Server Profiles
The JBoss Enterprise Application Platform ships with six server profiles. Each server profile is contained in a directory named
<JBOSS_HOME>/server/<PROFILE>/
. You can look into each server profile's directory to see the services, applications, and libraries included in the server profile.
Note
The exact contents of the
<JBOSS_HOME>/server/<PROFILE>
directory depends on the server profile service implementation and is subject to change as the management layer and embedded server evolve.
- all
- The
all
profile provides clustering support and other enterprise extensions. - production
- The production server profile is based on the
all
server profile and provides configuration optimized for production environments. - minimal
- Starts the core server container without any of the enterprise services. Use the
minimal
server profile as a base to build a customized version of JBoss Enterprise Application Platform that only contains the services you need. - default
- The
default
server profile is mostly used by application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).Note
Thedefault
server profile is used if a profile is not specified via the command-line or in a configuration file. - standard
- The standard server profile is the server profile that has been tested for Java EE compliance. The major differences with the existing server profiles is that call-by-value and deployment isolation are enabled by default, along with support for
rmiiiop
andjuddi
(taken from the all config). - web
- The web server profile is an experimental, lightweight configuration created around JBoss Web that will follow the developments of the Java EE 6 web server profile. Except for the
servlet/jsp
container, it provides support for JTA/JCA and JPA. It also limits itself to allowing access to the server only through the http port. Please note that this server profile is not Java EE certified and will most likely change in the following releases.
The detailed services and APIs supported in each of those server profiles will be discussed throughout.
7.2.1. Changing Profile
If you want to change the profile used by the server, the method depends on whether the server was started at the command line or as a service.
If the server is being started at the command line, specify the required profile with the -c parameter:
run.sh -c profile
. For example, run.sh -c all
on Red Hat Enterprise Linux or run.bat -c all
command on Microsoft Windows starts the server in the all server profile.
If the server is being started as a service, reconfigure the profile used by the service then stop and restart the service. Refer to the Run the Enterprise Application Platform as a Service section of the Installation Guide for details of where the profile is specified.
Important
There is no
Server Started
message shown at the console when the server is started using the production
profile. This message can be found in the server.log
file located in the <JBOSS_HOME>/jboss-as/server/production/logs/log
subdirectory.