2.3. JBoss Enterprise Application Platform 6 Profiles

The concept of profiles that was used in previous versions of JBoss Enterprise Application Platform is no longer used. JBoss Enterprise Application Platform 6 now uses a small number of configuration files to hold all information about its configuration.

Modules and drivers are loaded on an as-needed basis, so the concept of a default profile which was used in previous versions of JBoss Enterprise Application Platform 6, where profiles were used to make the server start more efficiently, does not apply. At deployment time, module dependencies are determined, ordered, and resolved by the server or domain controller, and loaded in the correct order. During undeployment, modules are unloaded when no deployment needs them any longer.

It is possible to disable modules or undeploy drivers or other services manually by removing the subsystems from the configuration. However, for most cases this is unnecessary. If none of your applications use a module, it will not be loaded.