WildFly Domain Controller Post-Install Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 20: Line 20:


=<tt>host.xml</tt> Host Name=
=<tt>host.xml</tt> Host Name=
The <tt>host.xml</tt> 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.
Example:
<pre>
<host name="dc1" xmlns="urn:jboss:domain:1.7">
    ...
</host>
</pre>





Revision as of 03:01, 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.

Example:

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


A domain controller must be accessible via its management interface from the management network. Subordinate host controllers get their configuration that way. Details on how to configure jboss.bind.address.management are available here:

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