6.2. Configuration

To configure the Microcontainer bootstrap you can use the $JBOSS_HOME/server/$PROFILE/conf/bootstrap.xml and $JBOSS_HOME/server/$PROFILE/conf/bootstrap/*.xml files where $PROFILE represents the name of the server profile; either production or default. The bootstrap.xml simply references Microcontainer deployment descriptors that should be loaded in the indicated order. The current default profile bootstrap.xml references are:
logging.xml
Logging manager and bridge configuration.
vfs.xml
JBoss VFS caching beans.
classloader.xml
The root class loading beans for the peer class loading model.
aop.xml
JBoss AOP integration and AspectManager beans.
jmx.xml
JBoss JMX kernel initialization.
deployers.xml
Core deployers for -jboss-beans.xml and -service.xml.
profile.xml
Full featured repository based profile service referenced by bootstrap.xml
The main beans are:
ProfileService
Loads the deployments associated with the specified server profile. Constantly examines server/$PROFILE/conf/jboss-service.xml, server/$PROFILE/deployers and server/$PROFILE/deploy for deployments.
AspectManager
AOP aspects.
MainDeployer
Deployer aspects are registered with the MainDeployer as an ordered list via an injection of the deployers property.
ServiceClassLoaderDeployer
Manages the class loading aspect of deployment.
JARDeployer
A structural deployment aspect which handles the legacy nested deployment behavior of adding non-deployable JARs to the current deployment classpath.
FileStructure
A structural deployment aspect which recognizes common deployment file types by suffix, as specified by FileManager.
AspectDeployer
Handles AOP descriptor deployments.
BeanDeployer
Translates *-jboss-beans.xml into KernelDeployment for the descriptor beans.
KernelDeploymentDeployer
Translates a KernelDeployment into the constituent BeanMetaData instances for the kernel beans.
SARDeployer
Handles legacy *-service.xml MBean descriptors and maps them as ServiceDeployment POJOs.
ServiceDeploymentDeployer
Translates the ServiceDeployment POJO into the constituent ServiceMetaData that represent the various MBeans.
ServiceDeployer
Creates the MBean services from deployment ServiceMetaData instances.
JMXKernel
Manages JMX kernel and MBeanServer instantiation in the JBoss domain. It is used by SARDeployer and will be used to expose kernel beans via JMX in the future.
HDScanner
Queries the profile service for changes to the deploy directory contents. It then redeploys updated content, undeploys removed content, and adds new deployment content to the profile service.