Learn how to install and configure the additional backend host. This step is optional. To configure an additional backend host, choose the option when installing the software.

Prerequisites

  • Identify the host you want to configure as the Additional Backend host.
  • Identify the hosts you want to configure as the Frontend, Collectors, and Additional Backends.
  • Minimum System Requirements:
    • 64-bit Operating System
    • CPU: 4
    • Memory: 16 GB
    • Disk Space: 150 GB HDD

Procedure

  1. Start the installation as described in Installing VMware Smart Assurance M&R on UNIX.
  2. When you are prompted to select the installation type, choose the "minimal" option and complete the installation.
  3. Configure the user process limits as described in Configuring the user process limits for a Linux installation.
    At this stage, you will have a host with minimal components installed. Customize this host further by manually adding the modules required for additional backend.
  4. Install the MySQL module: 
    /opt/APG/bin/manage-modules.sh install mysql <Instance-Name>
    Answer “no” when asked to install the databases packaged with the application.
  5. Start the MySQL process: 
    /opt/APG/bin/manage-modules.sh service start mysql
  6. Install the maintenance tool for each new backend by running the following command for each apg database. Answer yes to each question.
    /opt/APG/bin/manage-modules.sh install mysql-maintenance-tool apg[1..n]
  7. Create four new databases with the names apg1, apg2, apg3, and apg4 by running the following command four times (replacing the [1..n] with a number):
    /opt/APG/bin/mysql-command-runner-apg[1..n].sh -c /opt/APG/Tools/MySQLMaintenance-Tool/apg[1..n]/conf/mysql-root-mysql.xml -Q "create database apg[1..n]";
    Note: VMware Smart Assurance recommends keeping the default APG timeseries database.
  8. Register the apg databases to the APG Backend server by running the following command for each apg database. Answer Yes to each question.
    /opt/APG/bin/manage-modules.sh install backend apg[1..n]
    Note: The MySQL Storage Adapter uses in-memory temporary tables. You should set the max_heap_table_size in …/APG/Databases/MySQL/Default/my.cnf (Unix) or my.ini (Windows) to at least 128M (depending on your installation size) to avoid errors.
  9. Allow remote access to the new databases. Each database must be configured to be accessible from other hosts. Repeat the following command replacing <HostName> with each collector, frontend, primary backend and localhost: 
    /opt/APG/bin/mysql-command-runner.sh -c /opt/APG/Tools/MySQL-Maintenance-
Tool/<apg[1..n]>/conf/mysql-root-mysql.xml -Q "GRANT ALL
PRIVILEGES ON *.* TO 'apg'@'<HostName>' IDENTIFIED BY
PASSWORD'*FA71926E39A02D4DA4843003DF34BEADE3920AF3'"
    The <HOST NAME> must be the DNS name resolved from the nslookup <CLIENT IP> command executed from the Additional Backend host.
  10. Find all of the XML files in the /opt/APG/Backends/APG-Backend/apg[1..n] folders that contains JDBS connection URLs.
    For example: …localhost:53306/apg
  11. Update the URLs to include the correct APG database numbers.
    For example: …localhost:53306/apg[1..n]
    To complete this step with a script (for Linux), run this command: 
    find /opt/APG/Backends/APG-Backend/apg[1..n] -name '*.xml' | xargs
sed -i "s|jdbc:mysql://localhost:53306/apg|\\0[1..n]|"
  12. Set the Telnet interface port for each new apg database.
    The Telnet interface port for each new apg database must be different. The default port is 2001. To change the port numbers, edit the following file and set the port numbers to 2[1..n]01: /opt/APG/Backends/APG-Backend/apg[1..n]/conf/telnetinterface.xml
    Refer to Telnet and Socket Interface Ports for guidelines.
  13. Set the socket interface port for each new apg database.
    The socket interface port for each new apg database must be different. The default port is 2000. To change the port numbers, edit the following files and set the port numbers to 2[1..n]00: /opt/APG/Backends/APG-Backend/apg[1..n]/conf/Negotiating-socket-interface.xml
  14. Point the MySQL maintenance tools to the new local databases.
    Edit the following files and replace "apg" with the correct name, for example, "apg1." /opt/APG/Tools/MySQL-Maintenance-Tool/apg[1..n]/conf/mysql.xml

    /opt/APG/Tools/MySQL-Maintenance-Tool/apg[1..n]/conf/mysql-root-apg.xml

    For example: 
    <url>jdbc:mysql://localhost:53306/apg1?autoReconnect=true</url>
<!-- The username for database access. -->
<username>apg</username>
<!-- The password for database access. -->
<password>watch4net</password>
    To complete this step with a script (for Linux), run the following command: find /opt/APG/Tools/MySQL-Maintenance-Tool/apg[1..n] -name '*.xml' | xargs sed -i "s|jdbc:mysql://localhost:53306/apg|\\0[1..n]|"
  15. Start the backend services:
    Option Description
    Linux manage-modules.sh service start all
    Windows manage-modules.cmd service start all
  16. Verify that all the services are running:
    Option Description
    Linux manage-modules.sh service status all
    Windows manage-modules.cmd service status all
  17. To complete the configuration of additional backends, reconfigure the Load Balancer Arbiter (LBA) as described in Configuring the load balancer arbiter and add an entry for each of the apg backends.
    After the installation, you can reconfigure the backends and ports from Centralized Management > SolutionPacks > Other Components.