WildFly Domain Controller Post-Install Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
This procedure is part of [[WildFly Unzip Installation#Domain_Controller_Configuration|WildFly Unzip Installation]]. Once completed, return to [[WildFly Unzip Installation#Domain_Controller_Configuration|WildFly Unzip Installation]] to continue the post-install procedure. | This procedure is part of [[WildFly Unzip Installation#Domain_Controller_Configuration|WildFly Unzip Installation]]. Once completed, return to [[WildFly Unzip Installation#Domain_Controller_Configuration|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 <tt>host.xml</tt> should specify a local domain controller: | |||
<pre> | |||
<domain-controller> | |||
<local/> | |||
</domain-controller> | |||
</pre> | |||
Revision as of 02:55, 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>
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: