You must install xterm, konsole, or gnome-terminal before executing any console-based program installed by EnterpriseDB installers.Before using an RPM to install Migration Toolkit or EDB*Plus, you must first install Java version 1.7 or later for Migration Toolkit and Java version 1.8 or later for EDB*Plus. On a Linux system, you can use the yum package manager to install Java. Open a terminal window, assume superuser privileges, and enter:You must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit:To create the repository configuration file, assume superuser privileges and invoke the following command:The repository configuration file is named edb.repo. The file resides in /etc/yum.repos.d.After creating the edb.repo file, use your choice of editor to set the value of the enabled parameter to 1, and replace the username and password placeholders in the baseurl specification with the name and password of a registered EnterpriseDB user.baseurl=https://<username>:<password>@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearchAfter saving your changes to the configuration file, you must download and install the repository keys:Then, you can use yum install command to install Advanced Server. For example, to install the server and its core components, 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.After installing Advanced Server, you must configure the installation; see Section 3.3, Configuring a Package Installation, for details.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.The tables that follow list the RPM packages that are available from EnterpriseDB. You can also use the yum search command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:yum search packageWhere package is the search term that specifies the name (or partial name) of a package.
This package contains the pgPool-II installer. The pgpool-II utility package acts as a middleman between client applications and Server database servers. pgpool-II functionality is transparent to client applications; client applications connect to pgpool-II instead of directly to Advanced Server, and pgpool-II manages the connection. EnterpriseDB supports the following pgpool-II features: The edb-jdbc package includes the .jar files needed for Java programs to access an Advanced Server database. The edb-migrationtoolkit package installs Migration Toolkit, facilitating migration to an Advanced Server database from Oracle, PostgreSQL, MySQL, Sybase and SQL Server. The edb-oci package installs the EnterpriseDB Open Client library, allowing applications that use the Oracle Call Interface API to connect to an Advanced Server database. The edb-pem package installs Management Tool that efficiently manages, monitor, and tune large Postgres deployments from a single remote GUI console. If you have an existing Advanced Server RPM installation, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the edb.repo file, assume superuser privileges and enter:yum will update the edb.repo file to enable access to the current EDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum to upgrade all packages whose names include the expression edb:yum upgrade edb*Please note that the yum upgrade command will only perform an update between minor releases; to update between major releases, you must use pg_upgrade.For more information about using yum commands and options, enter yum --help on your command line, or visit: