Skip to Content

Installing the Manager software in a Multi-Manager configuration

This topic describes how to install the BMC Database Automation (BDA) Manager software in a mesh on several servers. BDA uses the Slony-I enterprise-level replication system to provide the mesh for the Multi-Manager configuration. For more information on Slony-I, see http://www.slony.info/.

Related topics

Performing-the-installation

Archiving-restoring-jobs-and-creating-backup-files

Before you begin

Make sure that the following prerequisites are met:

  • You can perform a new installation of BDA Manager only on RHEL 7 or later. Apache version 2.4.6 or later is required.
  • You have satisfied the OS-requirements for Multi-Manager environments.
  • You must have root user privileges to perform this installation.
  • Slony-I must be compiled at your site (supported versions are 2.2.7 and 2.2.8). The following tools are required to compile Slony-I:
    • GNU make version 3.76 and later
    • An ISO/ANSI C compiler, such as GCC
    • PostgreSQL source version 11 and later
Warning

Note

For additional information on system requirements for Slony-I, see http://www.slony.info/documentation/1.2/requirements.html.


To install the Manager software in a Multi-Manager configuration

Perform the following steps on every manager that will be in the mesh:

  1. Install the Manager software on the servers that will comprise the mesh using the steps in Installing-the-Manager-software-in-a-stand-alone-configuration.
  2. To make sure that the changes made in this procedure are saved, make sure the dmanager, mtd and postgresql services are running.

  3. Download the Slony source file:

    RHEL version

    Source file

    RHEL 9 or RHEL 8 with PostgreSQL 15

    wget http://main.slony.info/downloads/2.2/source/slony1-2.2.11.tar.bz2

    RHEL 7 with PostgreSQL 12.4

    wget http://main.slony.info/downloads/2.2/source/slony1-2.2.8.tar.bz2

    RHEL 7 with PostgreSQL server 11.x

    wget http://main.slony.info/downloads/2.2/source/slony1-2.2.7.tar.bz2

  4. For the installations mentioned below, do the following:

    Installation scenario

    Procedure

    If you are installing on RHEL 9 or RHEL 8 with PostgreSQL 15.x

    1. Use the command PATH=$PATH:/usr/pgsql-15/bin/ to set the path variable for PostgreSQL 15.x.
    2. Make sure that gcc is installed. If it isn't, then install gcc-4.8.x or later.
    3. Link the PostgreSQL files from the /usr/pgsql-15/bin directory:
      ln -snf /usr/pgsql-15/bin/* /usr/bin/

    If you are installing on RHEL 7 with PostgreSQL server 11.x

    1. Use the command PATH=$PATH:/usr/pgsql-11/bin/ to set the path variable for PostgreSQL 11.x.
    2. Make sure that gcc is installed. If it isn't, then install gcc-4.8.x or later.
    3. Link the PostgreSQL files from the /usr/pgsql-11/bin directory:
      ln -snf /usr/pgsql-11/bin/* /usr/bin/

    If you are installing on or RHEL 7 with PostgreSQL server 12.4

    1. Use the command PATH=$PATH:/usr/pgsql-12/bin/ to set the path variable for PostgreSQL 12.
    2. Make sure that gcc is installed. If it isn't, then install gcc-4.8.x or later.
    3. Link the PostgreSQL files from the /usr/pgsql-12/bin directory:
      ln -snf /usr/pgsql-12/bin/* /usr/bin/
    (% class="nolink" %)

  5. To unpack, compile, and install Slony, type the following commands and press <Enter> after each command:

    tar xvjf <downloaded file from previous step>


    cd <extracted directory>

    ./configure --with-pgconfigdir=`which pg_config` --with-perltools=/var/lib/pgsql/data/slony

    make

    make install


    Warning

    Note

    The Slony-I build requires the pg_config tool to run correctly. This tool is installed with the postgres-devel RPM. For example, the full name of the postgresql-devel tools RPM for RHEL version 8 is postgresql12-devel-12.4-1PGDG.rhel7.x86_64.rpm. If you find that the pg_config tool is missing, you must download and install the postgres-devel RPM. See http://www.postgresql.org/ for download information for the RPM.

  6. Link the Slony initialization script from the /etc/init.d directory:
    ln -s /app/clarity/manager_scripts/bin/slony.init /etc/init.d/slony

  7. Grant remote login privileges to the Multi-Manager postgres users for all managers in the mesh:

    Warning

    Note

    The following changes should be added in addition to the BDA default entries (for example, tcrimi) that are already present in the postgres configuration files.

    1. If the Manager is to be used as a Content manager:
      1. Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.

      2. Add the the following lines at the beginning of the file:local   GridApp     megamesh_config                      trust

        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines under the lines that you added in the previous step (two-line entries for each Satellite manager in the mesh):
        host all megamesh <satellite1 IP> 255.255.255.255 password
        host all megamesh_config <satellite1 IP> 255.255.255.255 password
      4. Save the /var/lib/pgsql/data/pg_hba.conf file.
      5. Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
      6. Add the following line at the beginning of the file:
        listen_addresses = '*'
      7. Save the /var/lib/pgsql/data/postgresql.conf file.
      8. Restart the postgresql service:
        service postgresql restart
        For restarting the postgresql-15 service:
        service postgresql-15 restartFor restarting the postgresql-12 service:service postgresql-12 restartFor restarting the postgresql-11 service:service postgresql-11 restart
      9. Restart the middle tier service:
        service mtd restart
    2. If the Manager is to be used as a Satellite manager:
      1. Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.

      2. Add the the following lines at the beginning of the file:local   GridApp     megamesh_config                      trust

        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines immediately under the lines that you added in the previous step:
        host all megamesh <content manager IP> 255.255.255.255 password
        host all megamesh_config <content manager IP> 255.255.255.255 password

      4. Add the following lines immediately under the lines that you added in the previous step:

        Warning

        Note

        satellite IP is the IP address of the server that you selected in step 7b (in other words, the server itself).

        host all megamesh <satellite IP> 255.255.255.255 password

        host all megamesh_config <satellite IP> 255.255.255.255 password

      5. Save the /var/lib/pgsql/data/pg_hba.conf file.
      6. Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
      7. Add the following line at the beginning of the file:
        listen_addresses = '*'
      8. Save the /var/lib/pgsql/data/postgresql.conf file.
      9. Restart the postgresql service:
        {{code language="none"}}
        service postgresql restart

        {{/code}}        For restarting the postgresql-15 service:
        service postgresql-15 restart
        For restarting the postgresql-12 service:
        service postgresql-11 restart
        For restarting the postgresql-11 service:
        service postgresql-11 restart
      10. Restart the middle tier service:
        service mtd restart

  8. Copy the following files from the Manager specified as the Content Manager to the specified location on the Satellite Manager:

    Content Manager

    Satellite Manager

    Source file location

    /app/clarity/dmanager/etc

    Target file location

    /app/clarity/dmanager/etc

    Source file names

    server.pem, dummy.pem

    Target file names

    server.pem, dummy.pem

    On the Satellite Managers, replace the existing server.pem and dummy.pem with the files from the Content Manager.

  9. To access the GUI by using the https protocol, install the Apache mod_ssl package on all servers where you have installed the Manager software, and run the following command: 
    {{code language="none"}}
    /app/clarity/var/www/mgmt/bin/enable_ssl.sh
    {{/code}}

    Warning

    Note

    Running the enable_ssl script results in the use of the test Secure Sockets Layer (SSL) certificate that ships with the Apache server that comes with Red Hat Enterprise Linux. For more information about how to replace this certificate with your own SSL certificate, refer to the Red Hat User documentation.

The software is now installed in the /app/clarity/dmanager directory and by default, GUI is available on port 80 (http protocol) and port 443 (https protocol) of the Manager server. For instructions to access the GUI, see Accessing-the-interface.


To install the Manager software in a Multi-Manager configuration (Red Hat PostgreSQL)

Perform the following steps on every manager that will be in the mesh:

  1. Install the Manager software on the servers that will comprise the mesh using the steps in Installing-the-Manager-software-in-a-stand-alone-configuration.
  2. To make sure that the changes made in this procedure are saved, make sure the dmanager, mtd and postgresql services are running.
  3. Download the Slony source file:
  4. (Only if you are installing on RHEL 7 with RH-PostgreSQL12)
    1. Use the command PATH=$PATH:/opt/rh/rh-postgresql12/root/usr/bin/ to set the path variable for RH-PostgreSQL12
    2. Make sure that gcc is installed. If it isn't, then install gcc-4.8.x or later versions
    3. Link the PostgreSQL files from the /opt/rh/rh-postgresql12/root/usr/bin directory:
      ln -snf /opt/rh/rh-postgresql12/root/usr/bin/* /usr/bin

  5. To unpack, compile, and install Slony, type the following commands and press <Enter> after each command:
    tar xvjf <downloaded file from previous step>cd <extracted directory>./configure --with-pgconfigdir=`which pg_config` --with-perltools=/var/opt/rh/rh-postgresql12/lib/pgsql/data/slonymakemake install

    Warning

    Note

    The Slony-I build requires the pg_config tool to run correctly. This tool is installed with the postgres-devel RPM. For example, the full name of the postgresql12-devel tools RPM for RHEL 7 is postgresql12-devel-12.4-1PGDG.rhel7.x86_64.rpm. If you find that the pg_config tool is missing, you must download and install the postgres-devel RPM. See http://www.postgresql.org/ for download information for the RPM.

  6. Link the Slony initialization script from the /etc/init.d directory:
    ln -s /app/clarity/manager_scripts/bin/slony.init /etc/init.d/slony

  7. Grant remote login privileges to the Multi-Manager postgres users for all managers in the mesh:

    Warning

    Note

    The following changes should be added in addition to the BDA default entries (for example, tcrimi) that are already present in the postgres configuration files.

    1. If the Manager is to be used as a Content manager:
      1. Open the /var/opt/rh/rh-postgresql12/lib/pgsql/data/pg_hba.conf file in a text editor.
      2. Add the the following lines at the beginning of the file:
        local   GridApp     megamesh_config                      trust
        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines under the lines that you added in the previous step (two-line entries for each Satellite manager in the mesh):
        host all megamesh <satellite1 IP> 255.255.255.255 password
        host all megamesh_config <satellite1 IP> 255.255.255.255 password
      4. Save the /var/opt/rh/rh-postgresql12/lib/pgsql/data/pg_hba.conf file.
      5. Open the /var/opt/rh/rh-postgresql12/lib/pgsql/data/postgresql.conf file in a text editor.
      6. Add the following line at the beginning of the file:
        listen_addresses = '*'
      7. Save the /var/opt/rh/rh-postgresql12/lib/pgsql/data/postgresql.conf file.
      8. Restart the postgresql service:
        service postgresql restart
      9. Restart the middle tier service:
        service mtd restart
    2. If the Manager is to be used as a Satellite manager:
      1. Open the /var/opt/rh/rh-postgresql12/lib/pgsql/data/pg_hba.conf file in a text editor.
      2. Add the the following lines at the beginning of the file:
        local   GridApp     megamesh_config                      trust
        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines immediately under the lines that you added in the previous step:
        host all megamesh <content manager IP> 255.255.255.255 password
        host all megamesh_config <content manager IP> 255.255.255.255 password

      4. Add the following lines immediately under the lines that you added in the previous step:

        Warning

        Note

        satellite IP is the IP address of the server that you selected in step 7b (in other words, the server itself).

        host all megamesh <satellite IP> 255.255.255.255 password

        host all megamesh_config <satellite IP> 255.255.255.255 password

      5. Save the /var/opt/rh/rh-postgresql12/lib/pgsql/data/pg_hba.conf file.
      6. Open the /var/opt/rh/rh-postgresql12/lib/pgsql/data/postgresql.conf file in a text editor.
      7. Add the following line at the beginning of the file:
        listen_addresses = '*'
      8. Save the /var/opt/rh/rh-postgresql12/lib/pgsql/data/postgresql.conf file.
      9. Restart the postgresql service:
        service postgresql restart
      10. Restart the middle tier service:
        service mtd restart

  8. To access the GUI by using the https protocol, install the Apache mod_ssl package on all servers where you have installed the Manager software, and run the following command: 
    /app/clarity/var/www/mgmt/bin/enable_ssl.sh

    Warning

    Note

    Running the enable_ssl script results in the use of the test Secure Sockets Layer (SSL) certificate that ships with the Apache server that came with Red Hat Enterprise Linux. For more information about how to replace this certificate with your own SSL certificate, refer to the Red Hat User documentation.

Where to go from here

See Configuring-a-Multi-Manager-mesh.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Database Automation 20.23