WildFly Domain Controller Post-Install Configuration
Internal
Overview
This procedure is part of WildFly Unzip Installation. Once completed, return to WildFly Unzip Installation to continue the post-install procedure.
Note: The domain controller must be fully configured and up and running when configuring subordinated host controllers, since we need to interact with the domain controller during the subordinated host controller installation (create users, etc.)
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:
Management Interface Bind Address
The domain controller accepts 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:
The value can also be hardcoded in host.xml as follows:
...
<interfaces>
<interface name="management">
<inet-address value="1.2.3.4"/>
</interface>
...
</interfaces>
One factor to consider when deciding between externalizing the value or hardcoding it is that an externalized system property defined in domain.conf is exposed to all processes (process controller, host controller, domain controller and server instance.
Management Interface Bind Address Change Effect on CLI
Changing the management bind address has a side effect the fact that the CLI cannot connect to localhost:9999 or localhost:9990 as it is configured by default. In order to work around, the new address could be specified on CLI command line (see Connect CLI to a Specific Controller) or its configuration file can be updated (see CLI Configuration - Management Interface Bind Address).
Confirmation that It Binds Correctly
$JBOSS_HOME/domain/log/host-controller.log
EAP 6:
22:28:18,337 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 10.155.78.202:9999
EAP 7:
[Host Controller] 19:43:44,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://172.20.1.11:9990/management
Security
At this point, the local administrative user should have been configured already (see WildFly Unzip Installation#Security).
Subordinate host controllers use their names to authenticate against the "ManagementRealm" on the domain controller, and we'll add the corresponding "users" as we add remote host controllers. Configuring subordinate host controller security if part of the Subordinate WildFly Host Controller Post-Install Configuration procedure.
Configure the Server Groups
Configure the server groups, their profile association and their socket binding groups in domain.xml.
Configure the Servers that are Running on this Host
Update host.xml accordingly, specify the server names and their association with a server group defined in domain.xml.
Various other Domain Configuration
Remove Unneeded Profiles
In domain mode, you can optionally remove unneeded profiles and their corresponding socket binding groups from domain.xml.