WildFly Domain Controller Post-Install Configuration

Internal

• WildFly Unzip Installation

Overview

This procedure is part of WildFly Unzip Installation. Once completed, return to WildFly Unzip Installation to continue the post-install procedure.

Local Domain Controller

For the domain controller, the host and the domain controller are collocated, so the host controller configuration file host.xml should specify a local domain controller:

<domain-controller>
       <local/>
</domain-controller>

This is the default configuration.

host.xml Host Name

The host.xml comes with default conventional host names. However, if building a custom environment, it's a good idea to change the host name to match the actual host name the domain controller runs on. This will make the information displayed by various console more descriptive and user friendly.

Example:

<host name="dc1" xmlns="urn:jboss:domain:1.7">
    ...
</host>

More details about the host name are available here:

host.xml host name

Management Interface Bind Address

The domain controller accept connections from the subordinated host controllers over the management interfaces defined in its host.xml.

The value of address to bind to can be externalized as jboss.bind.address.management. For more details on how to configure jboss.bind.address.management, see:

Setting 'jboss.bind.address.management' for domain controllers

be hardcoded either in host.xml or 

The network interface is "management" and the bind address can be specified in domain.conf as:

{{{ HOST_CONTROLLER_JAVA_OPTS="${HOST_CONTROLLER_JAVA_OPTS} -Djboss.bind.address.management=10.155.78.202" }}}

Alternatively, you can specify it directly in the host.mxl configuration file directly, because system properties defined in domain.conf are exposed to all processes.

{{{

   ...

   <interfaces>
       <interface name="management">
           <inet-address value="10.155.78.202"/>
       </interface>
       ...
   </interfaces>

}}}