Press any key to continue . . .
As you can see from the preceding listing, you have to create a management user by spe-
cifying a username and password for it. You should answer the previous question with
either yes or y to indicate that the user will be used to connect to the domain controller
from the host controller. The generated secret value is the Base64-encoded password of
the newly created user.
Now we can start the domain controller by specifying the address that will be used for
public and management interfaces (in our example, 192.168.1.10 ) with the following
domain.sh -host-config=host-master.xml -b 192.168.1.10
We have set the bind address of the physical network to the host configuration with the
jboss.bind.address.management property. The management interface must be
reachable for all the hosts in the domain in order to establish a connection with the do-
After the domain controller is configured and started, the next step is to set up the other
hosts that will connect to the domain controller. On each host, we also need an installation
of WildFly, where we will configure the host.xml file. (As an alternative, you can
name the host file as you like and start the domain with the -host-config parameter,
for example, ./domain.sh -host-config=host-slave.xml .)
The first thing is to choose a unique name for each host in our domain in order to avoid
name conflicts. Otherwise, the default is the hostname of the server.
<host name="server1" xmlns="urn:jboss:domain:2.0">
Also, you have to choose a unique name for the other host:
Search WWH ::