Red Hat JBoss Enterprise Application Platform Administration I

You configure Red Hat JBoss Enterprise Platform (JBoss EAP) in a single XML file. For a standalone server, the file is standalone.xml in the JBOSS_HOME/standalone/configuration/ directory. The general structure of standalone.xml is similar to the following content:

<server xmlns="urn:jboss:domain:16.0">
    <extensions>
	    ...list of extensions here
    </extensions>

    <system-properties>
        ...system properties defined here
    </system-properties>

    <management>
	    ...management interfaces defined here
    </management>

    <profile>
	    ...list of subsystems and their configurations
    </profile>

    <interfaces>
	    ...interface definitions
    </interfaces>

    <socket-binding-group>
	    ...socket binding definitions
    </socket-binding-group>

    <deployments>
	    ...deployed applications go here
    </deployments>
</server>

Extensions are modules that extend the core capabilities of the server. A module is a bundle composed of a library developed in Java and an XML configuration file that provides Jakarta Enterprise Edition (Jakarta EE) compliant functionalities. An extension defines one or more subsystems based on a module. The <extensions> element contains a list of <extension> elements that make a subsystem available to that server. For example, the following excerpt describes a list of extensions available to a server, including ejb3, which is responsible for providing the Enterprise Java Beans (EJB) runtime:

    <extensions>
        <!-- list all extensions that you want made available to this server -->
        <extension module="org.jboss.as.clustering.infinispan"/>
        <extension module="org.jboss.as.deployment-scanner"/>
        <extension module="org.jboss.as.ejb3"/>
        <extension module="org.jboss.as.jpa"/>
    </extensions>

Each extension must be declared in the standalone.xml file. Each extension refers to a module. The module has to be at the JBOSS_HOME/modules/system/layers/base/ directory. In order to manage the extension, JBoss EAP requires a <subsystem> tag where all customization needed for that subsystem is declared. This is discussed later during the course.

The <management> section is used for defining the following elements:

A profile is a collection of subsystems. A subsystem is where you configure the extensions of the JBoss EAP standalone instance. Adding a subsystem to a profile has two purposes:

The domain mode defines different profiles, but the standalone server mode defines only one.

The <profile> element includes a collection of <subsystem> child elements, and each <subsystem> entry consists of the unique configuration settings of that particular extension. Some subsystem definitions do not require any settings, like the jsf and jaxrs subsystems:

<profile>
     <subsystem xmlns="urn:jboss:domain:jsf:1.1"/>
     <subsystem xmlns="urn:jboss:domain:jaxrs:2.0"/>

     ...other subsystem definitions...
</profile>

Some subsystems might include many configuration settings, such as the datasources subsystem:

<profile>
     <subsystem xmlns="urn:jboss:domain:datasources:6.0">
            <datasources>
                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true" statistics-enabled="${wildfly.datasources.statistics-enabled:${wildfly.statistics-enabled:false}}">
                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>sa</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>
</profile>

The child elements of the <subsystem> elements are unique for each individual subsystem. You must inspect the corresponding schema to learn about the subsystem and determine how to configure a particular one. The schema documents are in the JBOSS_HOME/docs/schema directory.

For example, to view the settings for configuring the datasources subsystem, inspect its schema at the JBOSS_HOME/docs/schema/wildfly-datasources_6_0.xsd file.