7.2. Standard Server Profiles
<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.
<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.
allprofile provides clustering support and other enterprise extensions.
- The production server profile is based on the
allserver profile and provides configuration optimized for production environments.
- Starts the core server container without any of the enterprise services. Use the
minimalserver profile as a base to build a customized version of JBoss Enterprise Application Platform that only contains the services you need.
defaultserver profile is mostly used by application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).
defaultserver profile is used if a profile is not specified via the command-line or in a configuration file.
- 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
juddi(taken from the all config).
- 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/jspcontainer, 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.
7.2.1. Changing Profile
run.sh -c profile. For example,
run.sh -c allon Red Hat Enterprise Linux or
run.bat -c allcommand on Microsoft Windows starts the server in the all server profile.
Server Startedmessage shown at the console when the server is started using the
productionprofile. This message can be found in the
server.logfile located in the