Each machine that hosts server instances runs a JBoss EAP host controller process. A host controller acts as a secondary controller to the domain controller. The domain controller is also a host controller, but with the domain controller role.
The host.xml default configuration file configures a host controller.
In this file you define the host controller role, primary or secondary, its IP addresses, and its server instances.
Host controllers require a management interface for primary/secondary communication.
Host controllers are started by the domain.sh script.
The script invocation usually defines system properties for the IP addresses for the host controller network interfaces, the domain controller IP address if it is a secondary controller, and the configuration files directory.
Deploying applications to a managed domain involves three steps:
Uploading the application package to the domain controller repository.
Assigning the application to one or more server groups.
Enabling the application in each of its assigned server groups. When you enable the application, JBoss EAP starts serving it through the public interfaces.
Click CREATE to build all of the virtual machines needed for the classroom lab environment. This may take several minutes to complete. Once created the environment can then be stopped and restarted to pause your experience.
If you DELETE your lab, you will remove all of the virtual machines in your classroom and lose all of your progress.