Installing the Manager software in a Multi-Manager configuration
This topic describes how to install the BMC Database Automation Manager software in a mesh on several servers. BMC Database Automation 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/.
Before you begin
Ensure that the following prerequisites are met:
- 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 1.2 and 2.1). The following tools are required to compile Slony-I:
- GNU make version 3.76 and up
- An ISO/ANSI C compiler, such as GCC
- PostgreSQL source version 7.3.3 and up
To install the Manager software in a Multi-Manager configuration
Perform the following steps on every manager that will be in the mesh:
- Install the Manager software on the servers that will comprise the mesh using the steps in Installing-the-Manager-software-in-a-Standalone-configuration.
- To ensure that the changes made in this procedure are saved, make sure the dmanager, mtd and postgresql services are running.
- Download the Slony source file:
- Red Hat Enterprise Linux 5:
wget http://slony.info/downloads/1.2/source/slony1-1.2.14.tar.bz2 - Red Hat Enterprise Linux 6:
wget http://slony.info/downloads/2.1/source/slony1-2.1.1.tar.bz2
- Red Hat Enterprise Linux 5:
- To unpack, compile, and install Slony, type the following commands and press <Enter>:
- 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
- Copy the Slony initialization script into the /etc/init.d directory:
cp /app/clarity/manager_scripts/bin/slony.init /etc/init.d/slony Grant remote login privileges to the Multi-Manager postgres users for all managers in the mesh:
- If the manager is to be used as a Content manager:
- Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.
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 trusthost GridApp megamesh_config ::1/128 trust- Add the following lines under the lines in Step aii (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 - Save the /var/lib/pgsql/data/pg_hba.conf file.
- Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
- Add the following line at the beginning of the file:
listen_addresses = '*' - Save the /var/lib/pgsql/data/postgresql.conf file.
- Restart the postgresql service:
service postgresql restart
- If the manager is to be used as a Satellite manager:
- Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.
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 trusthost GridApp megamesh_config ::1/128 trust- Add the following lines immediately under the lines in Step bii:
host all megamesh <content manager IP> 255.255.255.255 password
host all megamesh_config <content manager IP> 255.255.255.255 password - Add the following lines immediately under the lines in Step biii (satellite IP is the IP address of the server in Step 6b (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 - Save the /var/lib/pgsql/data/pg_hba.conf file.
- Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
- Add the following line at the beginning of the file:
listen_addresses = '*' - Save the /var/lib/pgsql/data/postgresql.conf file.
- Restart the postgresql service:
service postgresql restart
- If the manager is to be used as a Content manager:
Where to go next
Configuring-a-Multi-Manager-mesh
Related topic