This topic has not yet been written. The content below is from the topic description.
all Default profile loaded when run.sh is executed without the -c parameter. The profile provides clustering support and other enterprise extensions. production The production profile is based on the all profile and provides configuration optimized for production environments. minimal Starts the core server container without any of the enterprise services. Use the minimal profile as a base to build a customized version of JBoss Enterprise Application Platform that only contains the services you need. default The default profile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3). Note The default profile is a misnomer; it is not loaded automatically if you do not specify a profile at start up. The all profile is loaded when you do not specify a profile at startup. standard The standard profile is the profile that has been tested for Java EE compliance. The major differences with the existing configurations is that call-by-value and deployment isolation are enabled by default, along with support for rmiiiop and juddi (taken from the all config). web The web profile is an experimental, lightweight configuration created around JBoss Web that will follow the developments of the Java EE 6 web 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 configuration is not Java EE certified and will most likely change in the following releases.