anchor.diff:  
   |--read-only-server-config |- |A relative path which is interpreted to
   be relative to jboss.server.config.dir. This is similar to
  ---server-config but if this alternative is specified the server willnot
  -overwrite the file when the management model is changed. However a full
  +--server-config but if this alternative is specified the server will not
  +overwrite the file when the management model is changed. However, a full
   versioned history is maintained of the file.
   
   |--graceful-startup | true | Start the servers in gracefully, queuing or cleanly rejecting incoming requests until the server is fully started.
  
positive.code: |=======================================================================
  |Name |Default if absent |Value
  
  |--admin-only |- |Set the server's running type to ADMIN_ONLY causing it
  to open administrative interfaces and accept management requests but not
  start servers or, if this host controlleris the master for the domain,
  accept incoming connections from slave host controllers.
  
  |--domain-config -c |domain.xml |A relative path which is interpreted to
  be relative to jboss.domain.config.dir. The name of the domain wide
  
negative.code: |=======================================================================
  |Name |Function
  
  |--backup |Causes the secondary host controller to create and maintain a
  local copy (domain.cached-remote.xml) of the domain configuration. If
  ignore-unused-configuration is unset in host.xml,a complete copy of the
  domain configuration will be stored locally, otherwise the configured
  value of ignore-unused-configuration in host.xml will be used. (See
  ignore-unused-configuration for more details.)
  
  |--cached-dc |If the secondary host controller is unable to contact the
  domain controller to get its configuration at boot, this option
  will allow the secondary host controller to boot and become operational using
  a previously cached copy of the domain configuration
  (domain.cached-remote.xml.) If the cached configuration is not present,
  this boot will fail. This file is created using one of the
  following methods:- A previously successful connection to the
  domain controller using --backup or --cached-dc.- Copying the domain
  configuration from an alternative host to
  domain/configuration/domain.cached-remote.xml.The unavailable
  domain controller will be polled periodically for availability, and once
  becoming available, the secondary host controller will reconnect to the
  domain controller and synchronize the domain configuration. During
  the interval the domain controller is unavailable, the secondary host
  controller will not be able to make any modifications to the domain
  configuration, but it may launch servers and handle requests to deployed
  applications etc.
  |=======================================================================
  
  