anchor.diff:  ----
   
   ~(See domain/configuration/host.xml)~ +
  -From the preceeding examples we can see that we also had a `jvm`
  -reference at server group level in the domain controller. The jvm's name
  -*must* match one of the definitions in the host controller. The values
  -supplied at domain controller and host controller level are combined,
  -with the host controller taking precedence if the same parameter is
  +From the preceding examples we can see that we also had a `jvm`
  +reference at server group level in the Domain Controller. The jvm's name
  +*must* match one of the definitions in the Host Controller. The values
  +supplied at Domain Controller and Host Controller level are combined,
  +with the Host Controller taking precedence if the same parameter is
   given in both places.
   
   Finally, as seen, we can also override the `jvm` at server level. Again,
  -the jvm's name *must* match one of the definitions in the host
  -controller. The values are combined with the ones coming in from domain
  -controller and host controller level, this time the server definition
  +the jvm's name *must* match one of the definitions in the Host Controller.
  +The values are combined with the ones coming in from Domain
  +Controller and Host Controller level, this time the server definition
   takes precedence if the same parameter is given in all places.
   
   Following these rules the jvm parameters to start each server would be
  
positive.code: Please consult the chapter "Interface Configuration" for a more detailed
  explanation on how to configure network interfaces.
  
  Next by default the master domain controller is configured to require
  authentication so a user needs to be added that can be used by the slave
  domain controller to connect.
  
  Make use of the `add-user` utility to add a new user, for this example I
  am adding a new user called slave.
  
  [NOTE]
  
  `add-user` MUST be run on the master domain controller and NOT the
  slave.
  
  [[host-controller-configuration]]
  == Host Controller Configuration
  
  Once the domain controller is configured correctly you can proceed with
  any host that should join the domain. The host controller configuration
  requires three steps:
  
  * The logical host name (within the domain) needs to be distinct
  * The host controller needs to know the domain controller IP address
  
  Provide a distinct, logical name for the host. In the following example
  we simply name it "slave":
  
  [source,xml,options="nowrap"]
  ----
  <host xmlns="urn:jboss:domain:3.0"
       name="slave">
  [...]
  </host>
  ----
  
negative.code: [[server-groups]]
  == Server groups
  
  The Domain Controller defines one or more server groups and associates
  each of these with a profile and a socket binding group, and also:
  
  [source,xml,options="nowrap"]
  ----
  