7.2. Install and Configure a Worker Node

Procedure 7.1. Configure a Worker Node

1. Configure the network interfaces.

   By default, the network interfaces all default to 127.0.0.1. Every physical host which hosts either a standalone server or one or more servers in a server group needs its interfaces to be configured to use its public IP address, which the other servers can see.
   To change the IP address of a JBoss Enterprise Application Platform host, you need to shut it down and edit its configuration file directly. This is because the Management API which drives the Management Console and Management CLI relies on a stable management address.
   Follow these steps to change the IP address on each server in your cluster to the master's public IP address.
   1. Shut down the server completely.
   2. Edit either the host.xml, which is in EAP_HOME/domain/configuration/ for a managed domain, or the standalone-ha.xml file, which is in EAP_HOME/standalone/configuration/ for a standalone server.
   3. Locate the <interfaces> element. Three interfaces are configured, management, public, and unsecured. For each of these, change the value 127.0.0.1 to the external IP address of the host.
   4. For hosts that participate in a managed domain but are not the master, locate the <host element. Note that it does not have the closing > symbol, because it contains attributes. Change the value of its name attribute from master to a unique name, a different one per slave. This name will also be used for the slave to identify to the cluster, so make a note of it.

   5. Optional Step

      For newly-configured hosts which need to join a managed domain, find the <domain-controller> element. Comment out or remove the <local /> element, and add the following line, changing the IP address (X.X.X.X) to the address of the domain controller. This step does not apply for a standalone server.

      <remote host="X.X.X.X" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/>

      Copy to Clipboard Toggle word wrap
   6. Save the file and exit.

2. Configure authentication for each slave server.

   Each slave server needs a username and password created in the domain controller's or standalone master's ManagementRealm. On the domain controller or standalone master, run the EAP_HOME/add-user.sh command. Add a user with the same username as the slave, to the ManagementRealm. When asked if this user will need to authenticate to an external JBoss AS instance, answer yes. An example of the input and output of the command is below, for a slave called slave1, with password changeme.

   user:bin user$ ./add-user.sh
   
   What type of user do you wish to add? 
    a) Management User (mgmt-users.properties) 
    b) Application User (application-users.properties)
   (a): a
   
   Enter the details of the new user to add.
   Realm (ManagementRealm) : 
   Username : slave1
   Password : changeme
   Re-enter Password : changeme
   About to add user 'slave1' for realm 'ManagementRealm'
   Is this correct yes/no? yes
   Added user 'slave1' to file '/home/user/jboss-eap-6.0/standalone/configuration/mgmt-users.properties'
   Added user 'slave1' to file '/home/user/jboss-eap-6.0/domain/configuration/mgmt-users.properties'
   Is this new user going to be used for one AS process to connect to another AS process e.g. slave domain controller?
   yes/no? yes
   To represent the user add the following to the server-identities definition <secret value="Y2hhbmdlbWU=" />
   

   Copy to Clipboard Toggle word wrap

3. Copy the <secret> element from the add-user.sh output.

   Copy the value from the last line of the add-user.sh output. You need to add this value to your slave's configuration file in the next step.

4. Modify the slave host's security realm to use the new authentication.

   Re-open the slave host's host.xml or standalone-ha.xml file and locate the <security-realms> element. Add the following block of XML code directly below the <security-realm name="ManagementRealm"> line, replacing the <secret value="Y2hhbmdlbWU="/> line with the one from the previous step.

          <server-identities>
              <secret value="Y2hhbmdlbWU="/>
          </server-identities>
   
   

   Copy to Clipboard Toggle word wrap
   Save and exit the file.

5. Restart the server.

   The slave will now authenticate to the master using the its host name as the username and the encrypted string as its password.