WildFly Domain Controller Post-Install Configuration: Difference between revisions
Line 47: | Line 47: | ||
</blockquote> | </blockquote> | ||
The value can also be hardcoded in <tt>host.xml</tt> as follows: | |||
<pre> | |||
... | ... | ||
<interfaces> | <interfaces> | ||
<interface name="management"> | <interface name="management"> | ||
Line 69: | Line 57: | ||
... | ... | ||
</interfaces> | </interfaces> | ||
</pre> | |||
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. |
Revision as of 04:12, 12 February 2016
Internal
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:
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:
The value can also be hardcoded in host.xml as follows:
... <interfaces> <interface name="management"> <inet-address value="10.155.78.202"/> </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.