Learn how to configure the load balancer arbiter from Centralized Management. Complete these steps every time a new backend host is added to the environment to scaleout backends.

Prerequisites

  • The connection must point to the FQDN of the primary backend or additional backend host.
  • The listening port must be 2020.

Procedure

  1. Log in to Centralized Management at https://<frontend-host>:58443/centralized-management.
  2. Navigate to SolutionPacks > Other Components.
  3. Locate the load-balancer-arbiter component and click the Reconfigure button.
  4. Click on the drop down against Arbiter configuration and select Add a new arbiter configuration
    1. Update the backend hostname with the DNS name of primary backend host.
    2. Change the Web-Service Gateway to the primary backend host.
    3. Update the backend database hostname with the DNS name of primary backend host.
  5. Add a configuration for all the apg backends installed on the additional backend host. Complete this step whenever a new additional backend host is added to the environment to scale out backends.
    For example:
    SolutionPack Reconfiguration Fields describes the values that you should enter for each field on the SolutionPack Reconfiguration page.
  6. Click the + button and add an entry for each of the backend instances (apg1, apg2, apg3 and apg4) created on the additional backend host.
  7. Provide the appropriate backend data port, web-service gateway, backend instance name, and DB connection details for each of the instances.
  8. Modify the Alerting data collection section and provide the primary backend DNS name for Alerting Backend hostname.
  9. Modify the Frontend Web service section and provide the frontend DNS name for Tomcat hostname.
  10. Once everything is updated, click Reconfigure.
  11. After you have setup the arbiter, check the logs under /opt/APG/Collecting/Collector-Manager/Load-Balancer/logs to see if all of the APG backend instances were correctly installed.
    For example: 
    # cat /opt/APG/Collecting/Collector-Manager/Load-Balancer/logs/collecting-0-0.log | grep "LoadFactorDecision::isReady"
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Starting decision with current load factor of:
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Backend1 0.0/750000.0 (0.0)
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Backend2 0.0/750000.0 (0.0)
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Backend3 0.0/750000.0 (0.0)
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Backend4 0.0/750000.0 (0.0)
INFO -- [2014-06-05 12:28:44 EDT] -- LoadFactorDecision::isReady(): Backend0 595.0/750000.0 (7.933333333333333E-4)