After receiving your credentials, you must create the EnterpriseDB repository configuration file on each node of the cluster, and then modify the file to enable access. The following steps provide detailed information about accessing the EnterpriseDB repository; the steps must be performed on each node of the cluster:
1. Use the edb-repo package to create the repository configuration file. You can download and invoke the edb-repo file, or use rpm or yum to create the repository. Assume superuser privileges and use either rpm or yum to create the EnterpriseDB repository configuration file. :The repository configuration file is named edb.repo; it resides in /etc/yum.repos.d.
2. Use your choice of editor to modify the repository configuration file, enabling the [enterprisedb-tools] and the [enterprisedb-dependencies] entries. To enable a repository, change the value of the enabled parameter to 1 and replace the user name and password placeholders in the baseurl specification with your user name and the repository password.baseurl=http://<username>:<password>@yum.enterprisedb.com/dependencies/redhat/rhel-$releasever-$basearch
3. Then, you can use the yum install command to install Failover Manager. For example, to install Failover Manager version 3.2, use the command:When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter a y, and press Return to continue.During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve.Failover Manager must be installed by root. During the installation process, the installer will also create a user named efm that has sufficient privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see Section 3.4, Extending Failover Manager Permissions.
4. 3.1.1 Installation Locations