A host controller is launched, when the script
domain.bat script is run on a host. The primary responsibility of a host controller is server management. It delegates domain management tasks and is responsible for starting and stopping the individual application server processes that run on its host. It interacts with the domain controller to help manage the communication between the servers and the domain controller. Multiple host controllers of a domain can interact with only a single domain controller. Hence, all the host controllers and server instances running on a single domain mode can have a single domain controller and must belong to the same domain.
Each host controller by default reads its configuration from the
file located in the unzipped JBoss EAP 6 installation file on its host's filesystem. The
file contains the following configuration information that is specific to the particular host:
List of the names of the actual JBoss EAP 6 instances that are meant to run from this installation
Any of the following configurations:
how the host controller contacts the domain controller to register itself and access the domain configuration
how to find and contact a remote domain controller
telling the host controller to itself act as the domain controller
Configuration of items that are specific to the local physical installation. For example, named interface definitions declared in domain.xml can be mapped to an actual machine-specific IP address in host.xml. Abstract path names in domain.xml can be mapped to actual filesystem paths in host.xml.