anchor.diff:  ==== Domain Wide Configuration – domain.xml
   
   Once a Host Controller has processed its host-specific configuration, it
  -knows whether it is configured to act as the master Domain Controller.
  +knows whether it is configured to act as the Domain Controller.
   If it is, it must parse the domain wide configuration file, by default
   located at `domain/configuration/domain.xml`. This file contains the
   bulk of the settings that should be applied to the servers in the domain
  
positive.code: 
  WildFly stores its configuration in centralized XML configuration files,
  one per server for standalone servers and, for managed domains, one per
  host with an additional domain wide policy controlled by the master
  host. These files are meant to be human-readable and human editable.
  
  [TIP]
  
  
negative.code: 
  |host.xml |The default host configuration, tailored for an easy out of
  the box experience experimenting with a managed domain. This
  configuration specifies the Host Controller should become the primary Host Controller,
  aka the Domain Controller, but it also launches a couple of servers.
  |=======================================================================
  
  