Show Table of Contents
Chapter 13. Subsystem Configuration
13.1. Subsystem Configuration Overview
Introduction
JBoss EAP 6 uses a simplified configuration, with one configuration file per domain or per standalone server. In domain mode, a separate file exists for each host controller as well. Changes to the configuration persist automatically, so XML should not be edited manually. The configuration is scanned and overwritten automatically by the Management API. The command-line based Management CLI and web-based Management Console allow you to configure each aspect of JBoss EAP 6.
JBoss EAP 6 is built on the concept of modular classloading. Each API or service provided by the Platform is implemented as a module, which is loaded and unloaded on demand. Most modules include a configurable element called a subsystem. Subsystem configuration information is stored in the unified configuration file
EAP_HOME/domain/configuration/domain.xml for a managed domain or EAP_HOME/standalone/configuration/standalone.xml for a standalone server. Many of the subsystems include configuration details that were configured via deployment descriptors in previous versions of JBoss EAP.
Subsystem Configuration Schemas
Each subsystem's configuration is defined in an XML schema. The configuration schemas are located in the EAP_HOME/docs/schema/ directory of your installation.
The following subsystems are known as simple subsystems, because they do not have any configurable attributes or elements. They are generally listed at the top of the configuration file.
Simple Subsystems
ee– the Java EE 6 API implementationejb– the Enterprise JavaBeans (EJB) subsystemjaxrs– the JAX-RS API, provided by RESTeasy.sar– the subsystem which supports Service Archives.threads– the subsystem which supports process threads.weld– the Contexts and Dependency Injection API, provided by Weld.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.