Configuring slaves - host-slave.xml

In the previous section, we initialized the domain configuration. In this step, we will set up communications links between the domain controller and the hosts. For each host, edit the domain/configuration/host-slave.xml configuration file:

$cd host1/domain/configuration/
$ vi host-slave.xml<host xmlns="urn:jboss:domain:4.1" name="host1">  
 use the correct name for host2 as well

Change the management interface default port to 19999 for host1 and 29999 for host2; 9999 is already used by the domain controller. The HTTP interface is not active by default on the slave host:

<native-interface security-realm="ManagementRealm">
 <socket interface="management" port="${jboss.management.native.port:19999}"/>
</native-interface>

Set up the right configuration so that the host can join the domain controller:

<domain-controller>
 <remote security-realm="ManagementRealm">
<discovery-options>
    <static-discovery name="primary"                     protocol="${jboss.domain.master.protocol:remote}" host="${jboss.domain.master.address :127.0.0.1}" port="${jboss.domain.master.port:9999}"/>
 </discovery-options>
 </remote>
</domain-controller>

Define a default value for the controller IP:

addresshost="${jboss.domain.master.address :127.0.0.1}" add :127.0.0.1.

This can also be set in the command line when the host starts using Djboss.domain.master.addess=127.0.0.1. The discovery options can list many controller addresses, and hosts will try to connect to the first active controller listed in this section.
Remove the content of the servers tag; later, we will look at how to create server group and instances:

<servers> </servers>

Repeat the same step on host2 with port 29999.