From c845566c6d38b3b8f73822eb4168a23cf1689235 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 4 Apr 2022 19:36:49 -0400 Subject: [PATCH 01/12] Consolidated model for install topics --- .../13_upgrading_rpm_install.mdx | 2 +- .../55/05_installing_mtk/index.mdx | 11 +- .../01_mtk55_rhel8_x86.mdx | 118 ---- .../02_mtk55_other_linux8_x86.mdx | 118 ---- .../03_mtk55_rhel7_x86.mdx | 107 ---- .../04_mtk55_centos7_x86.mdx | 107 ---- .../05_mtk55_sles15_x86.mdx | 51 -- .../06_mtk55_sles12_x86.mdx | 63 -- .../07_mtk55_ubuntu20_deb10_x86.mdx | 56 -- .../08_mtk55_ubuntu18_deb9_x86.mdx | 56 -- .../09_mtk55_rhel8_ppcle.mdx | 63 -- .../10_mtk55_rhel7_ppcle.mdx | 77 --- .../11_mtk55_sles15_ppcle.mdx | 51 -- .../12_mtk55_sles12_ppcle.mdx | 55 -- .../ibm_power_ppc64le/index.mdx | 238 +++++++ .../install_on_linux_using_edb_repo/index.mdx | 3 + .../x86_amd64/index.mdx | 592 ++++++++++++++++++ 17 files changed, 839 insertions(+), 929 deletions(-) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => }/13_upgrading_rpm_install.mdx (93%) delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/13_upgrading_rpm_install.mdx similarity index 93% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/13_upgrading_rpm_install.mdx index 376519e4f44..aaefeca7f34 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/13_upgrading_rpm_install.mdx @@ -1,5 +1,5 @@ --- -title: Upgrading an RPM Installation +title: Upgrading an RPM installation --- If you have an existing 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: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx index f74858050ff..d495b9deb60 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx @@ -8,11 +8,10 @@ legacyRedirects: - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_sles.html" - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_centos_or_rhel.html" navigation: - - mtk_rel_notes - - 02_supported_operating_systems_and_database_versions - - 03_migration_methodology - - 04_functionality_overview - - 05_installing_mtk + - install_on_linux_using_edb_repo + - install_on_mac + - install_on_windows + - 13_upgrading_rpm_install --- @@ -21,7 +20,7 @@ Before installing Migration Toolkit, you must install Java (version 1.8.0 or lat You can install Migration Toolkit on: -- [Linux x86-64 (amd64) and IBM Power (ppc64le)](install_on_linux_using_edb_repo) +- [Linux x86-64 (amd64)](x86_amd64) and [IBM Power (ppc64le)](ibm_power_ppc64le) - [Windows x86-64](install_on_windows) - [Mac OS X](install_on_mac) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx deleted file mode 100644 index f0511868666..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: "RHEL 8/OL 8 on x86_64" ---- - - -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -## Creating a Repository Configuration File - -1. To create the repository configuration file, assume superuser privileges and invoke the following command - - ```text - dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-8.noarch.rpm - ``` - -4. Enable the codeready-builder repository to resolve dependencies: - - ```text - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for - -rhel-8-${ARCH}-rpms" - ``` - -## Installing Migration Toolkit - -```text -dnf -y install edb-migrationtoolkit -``` - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -## Using Migration Toolkit with IDENT Authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx deleted file mode 100644 index 0338dc2f0fe..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" ---- - - -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -## Creating a Repository Configuration File - -1. To create the repository configuration file, assume superuser privileges and invoke the following command - - ```text - dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-8.noarch.rpm - ``` - -4. Enable the codeready-builder repository to resolve dependencies: - - ```text - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for - -rhel-8-${ARCH}-rpms" - ``` - -## Installing Migration Toolkit - -```text -dnf -y install edb-migrationtoolkit -``` - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -## Using Migration Toolkit with IDENT Authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx deleted file mode 100644 index e0a0046df40..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: "RHEL 7/OL 7 on x86_64" ---- - - -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -## Creating a Repository Configuration File - -1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -## Installing Migration Toolkit - -```shell -yum -y install edb-migrationtoolkit -``` - - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -## Using Migration Toolkit with IDENT Authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx deleted file mode 100644 index 72c0ba3e43a..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: "CentOS 7 on x86_64" ---- - - -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -## Creating a Repository Configuration File - -1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -## Installing Migration Toolkit - -```shell -yum -y install edb-migrationtoolkit -``` - - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -## Using Migration Toolkit with IDENT Authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx deleted file mode 100644 index 8767d6da935..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "SLES 15 on x86_64" ---- - - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-migrationtoolkit -``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx deleted file mode 100644 index cbfaff50df8..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "SLES 12 on x86_64" ---- - - - - -You can use the zypper package manager to install a Migration toolkit on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. - -1. You must assume superuser privileges and stop any firewalls before installing Migration Toolkit. Then, use the following commands to add EnterpriseDB repositories to your system: - - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/ - edb-sles.repo - ``` - -2. The command creates the repository configuration files in the /etc/zypp/repos.d directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: - - ```text - zypper refresh - ``` - - When prompted, provide credentials for the repository; specify `a` to always trust the provided key and update the metadata to include the EnterpriseDB repository. - -3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: - - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - - SUSEConnect -p PackageHub/12.5/x86_64 - - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` - -4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: - - ```text - zypper addrepo https://download.opensuse.org/repositories/ - Apache:/Modules/SLE_12_SP4/Apache:Modules.repo - ``` - -5. Use the following command to refresh the metadata: - - ```text - zypper refresh - ``` - -6. Install OpenJDK (version 1.8) for Java based components: - - ```text - zypper -n install java-1_8_0-openjdk - ``` - -7. Now you can use the zypper utility to install a Migration Toolkit: - - ```text - zypper -n install edb-migrationtoolkit - ``` - - For detailed information about registering a SUSE host, visit: - - - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx deleted file mode 100644 index fdf830574d5..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "Ubuntu 20.04/Debian 10 on x86_64" ---- - - - -To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. - -1. Assume superuser privileges: - - ```text - sudo su – - ``` - -2. Set up the EnterpriseDB repository: - - ```text - sh -c 'echo "deb [arch=amd64] https:// - apt.enterprisedb.com/ - $(lsb_release -cs)-edb/ $(lsb_release -cs) main" - > /etc/ - apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - -1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login - password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -1. Add support to your system for secure APT repositories: - - ```text - apt-get install apt-transport-https - ``` - -1. Add the EBD signing key: - - ```text - wget -q -O - https://username:password - @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - - ``` - -1. Update the repository metadata: - - ```text - apt-get update - ``` - -1. Install the `edb-migrationtoolkit` package: - - ```text - apt-get -y install edb-migrationtoolkit - ``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx deleted file mode 100644 index 89c2082f05b..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "Ubuntu 18.04/Debian 9 on x86_64" ---- - - - - -To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. - -1. Assume superuser privileges: - - ```text - sudo su – - ``` - -2. Configure the EnterpriseDB repository: - - ```text - sh -c 'echo "deb https://username:password@apt. - enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release - -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release - -cs).list' - ``` - -1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login - password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -1. Add support to your system for secure APT repositories: - - ```text - apt-get install apt-transport-https - ``` - -1. Add the EBD signing key: - - ```text - wget -q -O - https://username:password - @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - - ``` - -1. Update the repository metadata: - - ```text - apt-get update - ``` - -1. Install the `edb-migrationtoolkit` package: - - ```text - apt-get -y install edb-migrationtoolkit - ``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx deleted file mode 100644 index adab91ce0df..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "RHEL 8 on IBM Power (ppc64le)" ---- - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: - -```shell -sudo su - -``` - -## Setting up the Repository - -1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -1. Set up the EDB repository: - - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - This creates the /etc/yum.repos.d/edb.repo configuration file. - -1. Add your EDB credentials to the edb.repo file: - - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - - where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). - -1. Install the EPEL repository and refresh the cache: - - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` - -1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: - - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` - -1. Disable the built-in PostgreSQL module: - ```shell - dnf -qy module disable postgresql - ``` - -## Installing the Package - -```shell -dnf -y install edb-migrationtoolkit -``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx deleted file mode 100644 index 6ca7ac63eff..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: "RHEL 7 on IBM Power (ppc64le)" ---- - - - -You can use an RPM package to install Migration Toolkit on a RHEL ppc64le host. - -Before installing Migration toolkit: - -1. Create the Advance Toolchain repository configuration file; assume superuser privileges and invoke the following command: - - ```text - rpm --import https://public.dhe.ibm.com/software/server/POWER/ - Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b - ``` - -2. After creating the `advance-toolchain.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [advance-toolchain] - name=Advance Toolchain IBM FTP - baseurl=https://public.dhe.ibm.com/software/server/POWER/ - Linux/toolchain/at/redhat/RHEL7 - failovermethod=priority - enabled=1 - gpgcheck=1 - gpgkey=ftp://public.dhe.ibm.com/software/server/POWER/Linux/ - toolchain/at/redhat/RHELX/gpg-pubkey-6976a827-5164221b - ``` - -The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -## Creating a Repository Configuration File - -1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: - - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL package: - - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -4. Enable an additional repository to resolve dependencies: - - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" - --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* - -server-rpms" - ``` -## Installing the Package -To install Migration Toolkit, run the following command. - -```text -yum -y install edb-migrationtoolkit -``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx deleted file mode 100644 index 3b00332523c..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "SLES 15 on IBM Power (ppc64le)" ---- - - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the Repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` - -## Installing the Package - -```shell -zypper -n install edb-migrationtoolkit -``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx deleted file mode 100644 index 1a28617bb17..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: "SLES 12 on IBM Power (ppc64le)" ---- - - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the Repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh - -# Install OpenJDK (version 1.8) -zypper -n install java-1_8_0-openjdk -``` - -## Installing the Package - -```shell -zypper -n install edb-migrationtoolkit -``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx new file mode 100644 index 00000000000..812f02e978d --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx @@ -0,0 +1,238 @@ +--- +title: "Installing on Linux x86-64 (amd64)" +navTitle: "IBM Power (ppc64le)" +--- + +## RHEL 8 + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```shell +sudo su - +``` + +### Setting up the repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```shell + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```shell + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```shell + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```shell + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```shell + dnf -qy module disable postgresql + ``` + +### Installing the package + +```shell +dnf -y install edb-migrationtoolkit +``` + +## RHEL 7 + +You can use an RPM package to install Migration Toolkit on a RHEL ppc64le host. + +Before installing Migration toolkit: + +1. Create the Advance Toolchain repository configuration file; assume superuser privileges and invoke the following command: + + ```text + rpm --import https://public.dhe.ibm.com/software/server/POWER/ + Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + ``` + +2. After creating the `advance-toolchain.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [advance-toolchain] + name=Advance Toolchain IBM FTP + baseurl=https://public.dhe.ibm.com/software/server/POWER/ + Linux/toolchain/at/redhat/RHEL7 + failovermethod=priority + enabled=1 + gpgcheck=1 + gpgkey=ftp://public.dhe.ibm.com/software/server/POWER/Linux/ + toolchain/at/redhat/RHELX/gpg-pubkey-6976a827-5164221b + ``` + +The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +### Creating a repository configuration file + +1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: + + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL package: + + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +4. Enable an additional repository to resolve dependencies: + + ```text + subscription-manager repos --enable "rhel-*-optional-rpms" + --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* + -server-rpms" + ``` +### Installing the package +To install Migration Toolkit, run the following command. + +```text +yum -y install edb-migrationtoolkit +``` +## SLES 15 + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +### Setting up the repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/15.3/ppc64le + +# Refresh the metadata +zypper refresh +``` + +### Installing the package + +```shell +zypper -n install edb-migrationtoolkit +``` +## SLES 12 + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +### Setting up the repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/12.5/ppc64le +SUSEConnect -p sle-sdk/12.5/ppc64le + +# Refresh the metadata +zypper refresh + +# Install OpenJDK (version 1.8) +zypper -n install java-1_8_0-openjdk +``` + +### Installing the package + +```shell +zypper -n install edb-migrationtoolkit +``` + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx index 7e0ffdf1305..a654f54e23f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx @@ -1,5 +1,8 @@ --- title: "Installing on Linux using the EDB Repository" +navigation: +- x86_amd64 +- ibm_power_ppc64le --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx new file mode 100644 index 00000000000..4b8711116ab --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx @@ -0,0 +1,592 @@ +--- +title: "Installing on Linux x86-64 (amd64)" +navTitle: "Intel x86-64 (amd64)" +--- + +To install Migration Toolkit, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). + +## RHEL 8/OL 8 + +You can use an RPM package to install Migration Toolkit on a RHEL 8/OL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +### Creating a Repository Configuration File + +1. To create the repository configuration file, assume superuser privileges and invoke the following command + + ```text + dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + + ```text + dnf -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-8.noarch.rpm + ``` + +4. Enable the codeready-builder repository to resolve dependencies: + + ```text + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for + -rhel-8-${ARCH}-rpms" + ``` + +### Installing Migration Toolkit + +```text +dnf -y install edb-migrationtoolkit +``` + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +### Using Migration Toolkit with IDENT authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + +## Rocky Linux 8/AlmaLinux 8 + +You can use an RPM package to install Migration Toolkit on a Rocky Linux/AlmaLinux host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +### Creating a repository configuration file + +1. To create the repository configuration file, assume superuser privileges and invoke the following command + + ```text + dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + + ```text + dnf -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-8.noarch.rpm + ``` + +4. Enable the codeready-builder repository to resolve dependencies: + + ```text + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for + -rhel-8-${ARCH}-rpms" + ``` + +### Installing Migration Toolkit + +```text +dnf -y install edb-migrationtoolkit +``` + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +### Using Migration Toolkit with IDENT authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + +## RHEL 7/OL 7 + +You can use an RPM package to install Migration Toolkit on a RHEL 7/OL 7 host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +### Creating a repository configuration file + +1. To create the repository configuration file, assume superuser privileges and invoke the following command: + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +### Installing Migration Toolkit + +```shell +yum -y install edb-migrationtoolkit +``` + +## CentOS 7 + +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +### Creating a repository configuration file + +1. To create the repository configuration file, assume superuser privileges and invoke the following command: + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +### Installing Migration Toolkit + +```shell +yum -y install edb-migrationtoolkit +``` + + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +### Using Migration Toolkit with IDENT authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + +## SLES 15 + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +### Setting up the repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/15.3/x86_64 + +# Refresh the metadata +zypper refresh +``` + +### Installing the package + +```shell +zypper -n install edb-migrationtoolkit +``` +## SLES 12 + + + +You can use the zypper package manager to install a Migration toolkit on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. + +1. You must assume superuser privileges and stop any firewalls before installing Migration Toolkit. Then, use the following commands to add EnterpriseDB repositories to your system: + + ```text + zypper addrepo https://zypp.enterprisedb.com/suse/ + edb-sles.repo + ``` + +2. The command creates the repository configuration files in the /etc/zypp/repos.d directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: + + ```text + zypper refresh + ``` + + When prompted, provide credentials for the repository; specify `a` to always trust the provided key and update the metadata to include the EnterpriseDB repository. + +3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: + + ```text + SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + + SUSEConnect -p PackageHub/12.5/x86_64 + + SUSEConnect -p sle-sdk/12.5/x86_64 + ``` + +4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: + + ```text + zypper addrepo https://download.opensuse.org/repositories/ + Apache:/Modules/SLE_12_SP4/Apache:Modules.repo + ``` + +5. Use the following command to refresh the metadata: + + ```text + zypper refresh + ``` + +6. Install OpenJDK (version 1.8) for Java based components: + + ```text + zypper -n install java-1_8_0-openjdk + ``` + +7. Now you can use the zypper utility to install a Migration Toolkit: + + ```text + zypper -n install edb-migrationtoolkit + ``` + + For detailed information about registering a SUSE host, visit: + + + +## Ubuntu 20.04/Debian 10 + + + +To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. + +1. Assume superuser privileges: + + ```text + sudo su – + ``` + +2. Set up the EnterpriseDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https:// + apt.enterprisedb.com/ + $(lsb_release -cs)-edb/ $(lsb_release -cs) main" + > /etc/ + apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + +1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login + password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + + ```text + apt-get install apt-transport-https + ``` + +1. Add the EBD signing key: + + ```text + wget -q -O - https://username:password + @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - + ``` + +1. Update the repository metadata: + + ```text + apt-get update + ``` + +1. Install the `edb-migrationtoolkit` package: + + ```text + apt-get -y install edb-migrationtoolkit + ``` +## Ubuntu 18.04/Debian 9 + + + +To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. + +1. Assume superuser privileges: + + ```text + sudo su – + ``` + +2. Configure the EnterpriseDB repository: + + ```text + sh -c 'echo "deb https://username:password@apt. + enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release + -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release + -cs).list' + ``` + +1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login + password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + + ```text + apt-get install apt-transport-https + ``` + +1. Add the EBD signing key: + + ```text + wget -q -O - https://username:password + @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - + ``` + +1. Update the repository metadata: + + ```text + apt-get update + ``` + +1. Install the `edb-migrationtoolkit` package: + + ```text + apt-get -y install edb-migrationtoolkit + ``` + + + From f4fa1c53a8d3462e40430788b9df65c7ddd6d051 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 5 Apr 2022 08:38:13 -0400 Subject: [PATCH 02/12] alternative approach shown in EFM --- .../09_efm4_rhel8_ppcle.mdx | 1 + .../10_efm4_rhel7_ppcle.mdx | 1 + .../11_efm4_sles15_ppcle.mdx | 1 + .../12_efm4_sles12_ppcle.mdx | 1 + .../ibm_power_pcc64le/index.mdx | 17 ++++++++++++++ .../docs/efm/4/03_installing_efm/index.mdx | 9 +++++++- .../{ => x86_amd64}/01_efm4_rhel_8_x86.mdx | 1 + .../02_efm4_other_linux8_x86.mdx | 1 + .../{ => x86_amd64}/03_efm4_rhel7_x86.mdx | 1 + .../{ => x86_amd64}/04_efm4_centos7_x86.mdx | 1 + .../{ => x86_amd64}/05_efm4_sles15_x86.mdx | 1 + .../{ => x86_amd64}/06_efm4_sles12_x86.mdx | 1 + .../07_efm4_ubuntu20_deb10_x8.mdx | 1 + .../08_efm4_ubuntu18_deb9_x86.mdx | 1 + .../4/03_installing_efm/x86_amd64/index.mdx | 23 +++++++++++++++++++ .../install_on_linux_using_edb_repo/index.mdx | 3 ++- .../55/05_installing_mtk/install_on_mac.mdx | 1 + .../05_installing_mtk/install_on_windows.mdx | 1 + .../13_upgrading_rpm_install.mdx | 0 .../docs/migration_toolkit/55/index.mdx | 1 + 20 files changed, 65 insertions(+), 2 deletions(-) rename product_docs/docs/efm/4/03_installing_efm/{ => ibm_power_pcc64le}/09_efm4_rhel8_ppcle.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => ibm_power_pcc64le}/10_efm4_rhel7_ppcle.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => ibm_power_pcc64le}/11_efm4_sles15_ppcle.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => ibm_power_pcc64le}/12_efm4_sles12_ppcle.mdx (98%) create mode 100644 product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/01_efm4_rhel_8_x86.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/02_efm4_other_linux8_x86.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/03_efm4_rhel7_x86.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/04_efm4_centos7_x86.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/05_efm4_sles15_x86.mdx (98%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/06_efm4_sles12_x86.mdx (99%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/07_efm4_ubuntu20_deb10_x8.mdx (97%) rename product_docs/docs/efm/4/03_installing_efm/{ => x86_amd64}/08_efm4_ubuntu18_deb9_x86.mdx (97%) create mode 100644 product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx rename product_docs/docs/migration_toolkit/55/{05_installing_mtk => }/13_upgrading_rpm_install.mdx (100%) diff --git a/product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index bb653cd71fd..b3c5ecd9667 100644 --- a/product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -1,5 +1,6 @@ --- title: "RHEL 8 on IBM Power (ppc64le)" +navTitle: "RHEL 8 " --- There are two steps to completing an installation: diff --git a/product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index 5ee3ee75545..f92ce86e57f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -1,5 +1,6 @@ --- title: "RHEL 7 on IBM Power (ppc64le)" +navTitle: "RHEL 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). diff --git a/product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index 8cbc08eebe6..21df01afbef 100644 --- a/product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -1,5 +1,6 @@ --- title: "SLES 15 on IBM Power (ppc64le)" +navTitle: "SLES 15" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index 1fe443d8172..509b50eb1b0 100644 --- a/product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -1,5 +1,6 @@ --- title: "SLES 12 on IBM Power (ppc64le)" +navTitle: "SLES 12" --- There are two steps to completing an installation: diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx new file mode 100644 index 00000000000..a5d475daa1e --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx @@ -0,0 +1,17 @@ +--- +title: "IBM Power (ppc64le)" +--- + + + + + +For platform-specific install instructions, including accessing the repo, see: + + - [RHEL 8](09_efm4_rhel8_ppcle) + + - [RHEL 7](10_efm4_rhel7_ppcle) + - [SLES 15](11_efm4_sles15_ppcle) + - [SLES 12](12_efm4_sles12_ppcle) + +After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/index.mdx b/product_docs/docs/efm/4/03_installing_efm/index.mdx index a7083a78216..fabd6e73aaf 100644 --- a/product_docs/docs/efm/4/03_installing_efm/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/index.mdx @@ -1,17 +1,24 @@ --- -title: "Installing Failover Manager" +title: "Installing on Linux" redirects: - ../efm_user/03_installing_efm legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.0/installing_efm.html" - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.1/installing_efm.html" +navigation: +- x86_amd64 +- ibm_power_pcc64le +- 13_initial_config +- 14_install_details --- +Native packages for Linux are available in the EDB repository. + For information about the platforms and versions supported by Failover Manager, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#efm). !!! Note diff --git a/product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index f4f3dc1127b..d9340b2eaa9 100644 --- a/product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -1,5 +1,6 @@ --- title: "RHEL 8/OL 8 on x86_64" +navTitle: "RHEL 8/OL 8" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). diff --git a/product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index 05966eb3b0f..4512772820b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -1,5 +1,6 @@ --- title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +navTitle: "Rocky Linux 8/AlmaLinux 8" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). diff --git a/product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index bac5e349397..8839735d3b7 100644 --- a/product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -1,5 +1,6 @@ --- title: "RHEL 7/OL 7 on x86_64" +navTitle: "RHEL 7/OL 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). diff --git a/product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 51f4798abd7..1aadd24c45f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -1,5 +1,6 @@ --- title: "CentOS 7 on x86_64" +navTitle: "CentOS 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). diff --git a/product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx similarity index 98% rename from product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index 0d279cc59eb..c593b77a6b9 100644 --- a/product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -1,5 +1,6 @@ --- title: "SLES 15 on x86_64" +navTitle: "SLES 15" --- There are three steps to completing an installation: diff --git a/product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx similarity index 99% rename from product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index 3dc035cd446..032aae62574 100644 --- a/product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,5 +1,6 @@ --- title: "SLES 12 on x86_64" +title: "SLES 12" --- To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the instructions to [access EDB software repositories](https://www.enterprisedb.com/repository-access-request). diff --git a/product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx similarity index 97% rename from product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index e8d3e25b0b6..3594fc4d6ad 100644 --- a/product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -1,5 +1,6 @@ --- title: "Ubuntu 20.04/Debian 10 on x86_64" +navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx similarity index 97% rename from product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index 457aceb2a28..214e46e8a1b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -1,5 +1,6 @@ --- title: "Ubuntu 18.04/Debian 9 on x86_64" +navTitle: "Ubuntu 18.04/Debian 9" --- To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the [EnterpriseDB website](https://www.enterprisedb.com/user/login). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx new file mode 100644 index 00000000000..b8caaa56458 --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx @@ -0,0 +1,23 @@ +--- +title: "x86_64 (amd64)" +--- + + + + + +For platform-specific install instructions, including accessing the repo, see: + +- Linux x86-64 (amd64): + - [RHEL 8/OL 8](01_efm4_rhel_8_x86) + + - [Rocky Linux 8/AlmaLinux 8](02_efm4_other_linux8_x86) + - [RHEL 7/OL 7](03_efm4_rhel7_x86) + - [CentOS 7](04_efm4_centos7_x86) + - [SLES 15](05_efm4_sles15_x86) + - [SLES 12](06_efm4_sles12_x86) + - [Ubuntu 20.04/Debian 10](07_efm4_ubuntu20_deb10_x8) + - [Ubuntu 18.04/Debian 9](08_efm4_ubuntu18_deb9_x86) + + +After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx index a654f54e23f..6c9d54d7b6a 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx @@ -1,5 +1,6 @@ --- -title: "Installing on Linux using the EDB Repository" +title: "Installing on Linux" +navTitle: "Linux" navigation: - x86_amd64 - ibm_power_ppc64le diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx index 414f9507f7b..b4854b1e00d 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx @@ -1,5 +1,6 @@ --- title: "Installing on Mac OS X" +navTitle: "Mac OS X" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx index 715ccbb189f..7b44f1f29de 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx @@ -1,5 +1,6 @@ --- title: "Installing on Windows" +navTitle: "Windows" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/13_upgrading_rpm_install.mdx b/product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/13_upgrading_rpm_install.mdx rename to product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx diff --git a/product_docs/docs/migration_toolkit/55/index.mdx b/product_docs/docs/migration_toolkit/55/index.mdx index 1952af45ab9..a683cc5e966 100644 --- a/product_docs/docs/migration_toolkit/55/index.mdx +++ b/product_docs/docs/migration_toolkit/55/index.mdx @@ -8,6 +8,7 @@ navigation: - 03_migration_methodology - 04_functionality_overview - 05_installing_mtk + - 13_upgrading_rpm_install --- From a67633b7b213b360743665c87bc688a6137a68a8 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 5 Apr 2022 09:37:46 -0400 Subject: [PATCH 03/12] fixed dup title element --- .../efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index 032aae62574..4c3fc60a4f6 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,6 +1,6 @@ --- title: "SLES 12 on x86_64" -title: "SLES 12" +navTitle: "SLES 12" --- To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the instructions to [access EDB software repositories](https://www.enterprisedb.com/repository-access-request). From 0fd9616b23797906c3a6bc59f880a785ae294192 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 5 Apr 2022 17:26:13 -0400 Subject: [PATCH 04/12] tweaks --- .../4/03_installing_efm/13_initial_config.mdx | 16 ---------------- .../ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx | 14 +++++++++++++- .../ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx | 10 ++++++++++ .../ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx | 10 ++++++++++ .../ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx | 11 +++++++++++ .../x86_amd64/01_efm4_rhel_8_x86.mdx | 9 +++++++++ .../x86_amd64/02_efm4_other_linux8_x86.mdx | 9 +++++++++ .../x86_amd64/03_efm4_rhel7_x86.mdx | 10 ++++++++++ .../x86_amd64/04_efm4_centos7_x86.mdx | 10 ++++++++++ .../x86_amd64/05_efm4_sles15_x86.mdx | 10 ++++++++++ .../x86_amd64/06_efm4_sles12_x86.mdx | 10 ++++++++++ .../x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx | 9 +++++++++ .../x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx | 10 ++++++++++ .../14_install_details.mdx | 0 product_docs/docs/efm/4/index.mdx | 1 + 15 files changed, 122 insertions(+), 17 deletions(-) delete mode 100644 product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx rename product_docs/docs/efm/4/{03_installing_efm => }/14_install_details.mdx (100%) diff --git a/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx b/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx deleted file mode 100644 index d63337f8b3a..00000000000 --- a/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Initial configuration" ---- - - - -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). - -After installing on each node of the cluster: - -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. -3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). - - diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index b3c5ecd9667..fc4bb25605d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -3,10 +3,11 @@ title: "RHEL 8 on IBM Power (ppc64le)" navTitle: "RHEL 8 " --- -There are two steps to completing an installation: +There are three steps to completing an installation: - Setting up the repository - Installing the package +- Initial configuration For each step, you must be logged in as superuser. @@ -63,3 +64,14 @@ dnf -y install edb-efm ``` where `` is the version number of Failover Manager. +## "Initial configuration" + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). + diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index f92ce86e57f..9fb6b05d2ba 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -55,3 +55,13 @@ To request credentials that allow you to access an EnterpriseDB repository, see ```text yum -y install edb-efm42 ``` +## "Initial configuration" + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index 21df01afbef..c65dbfdb866 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -52,3 +52,13 @@ zypper -n install edb-efmedb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index 509b50eb1b0..3ef9b4d30e9 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -7,6 +7,7 @@ There are two steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) +- [Initial configuration] For each step, you must be logged in as superuser. @@ -52,3 +53,13 @@ zypper -n install edb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index d9340b2eaa9..c37c7c7a1c3 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -48,4 +48,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` +## "Initial configuration" +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index 4512772820b..8f9dcb253c4 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -47,4 +47,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` +## "Initial configuration" +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index 8839735d3b7..097390aa2ee 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -46,3 +46,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` +## "Initial configuration" + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 1aadd24c45f..312bfdfaac2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -40,3 +40,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` +## "Initial configuration" + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index c593b77a6b9..4f20bd5efbc 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -52,3 +52,13 @@ zypper -n install edb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index 4c3fc60a4f6..debc97606cf 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -52,3 +52,13 @@ You can use the `zypper` package manager to install a Failover Manager agent on Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index 3594fc4d6ad..3965ae27b2f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -38,4 +38,13 @@ Use the EnterpriseDB APT repository to install Failover Manager. ```text apt-get -y install edb-efm42 ``` +## "Initial configuration" +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index 214e46e8a1b..0554bb748b4 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -33,3 +33,13 @@ Use the EnterpriseDB APT repository to install Failover Manager. ```text apt-get -y install edb-efm42 ``` +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/14_install_details.mdx b/product_docs/docs/efm/4/14_install_details.mdx similarity index 100% rename from product_docs/docs/efm/4/03_installing_efm/14_install_details.mdx rename to product_docs/docs/efm/4/14_install_details.mdx diff --git a/product_docs/docs/efm/4/index.mdx b/product_docs/docs/efm/4/index.mdx index 19de386b4f8..8191e637aac 100644 --- a/product_docs/docs/efm/4/index.mdx +++ b/product_docs/docs/efm/4/index.mdx @@ -12,6 +12,7 @@ navigation: - "#Installing" - 01_prerequisites - 03_installing_efm + - 14_install_details - 12_upgrading_existing_cluster - "#Configuring" - 14_configuring_streaming_replication From d282e5881c4b8d051fca205c6160fe47632ffcd3 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 06:16:28 -0400 Subject: [PATCH 05/12] cleanup and shortening x86_64 to x86 --- .../ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx | 2 +- .../ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx | 2 +- .../ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx | 2 +- .../ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx | 2 +- .../efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx | 6 ++---- product_docs/docs/efm/4/03_installing_efm/index.mdx | 2 +- .../4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx | 2 +- .../x86_amd64/02_efm4_other_linux8_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx | 2 +- .../x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx | 2 +- .../x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx | 2 +- .../docs/efm/4/03_installing_efm/x86_amd64/index.mdx | 8 +++----- 15 files changed, 18 insertions(+), 22 deletions(-) diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index fc4bb25605d..67fd187b278 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "RHEL 8 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 8 on IBM Power (ppc64le)" navTitle: "RHEL 8 " --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index 9fb6b05d2ba..ecc2ad546a2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "RHEL 7 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 7 on IBM Power (ppc64le)" navTitle: "RHEL 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index c65dbfdb866..9ad0025e6de 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 15 on IBM Power (ppc64le)" navTitle: "SLES 15" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index 3ef9b4d30e9..a180d92867c 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "SLES 12 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 12 on IBM Power (ppc64le)" navTitle: "SLES 12" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx index a5d475daa1e..e78956b4934 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx @@ -1,17 +1,15 @@ --- -title: "IBM Power (ppc64le)" +title: "Installing Failover Manager on IBM Power (ppc64le)" --- -For platform-specific install instructions, including accessing the repo, see: +For operating system-specific install instructions, including accessing the repo, see: - [RHEL 8](09_efm4_rhel8_ppcle) - [RHEL 7](10_efm4_rhel7_ppcle) - [SLES 15](11_efm4_sles15_ppcle) - [SLES 12](12_efm4_sles12_ppcle) - -After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/index.mdx b/product_docs/docs/efm/4/03_installing_efm/index.mdx index fabd6e73aaf..9b5de2e611d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing on Linux" +title: "Installing Failover Manager on Linux" redirects: - ../efm_user/03_installing_efm legacyRedirectsGenerated: diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index c37c7c7a1c3..b00b2b23da4 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "RHEL 8/OL 8 on x86_64" +title: "Installing Failover Manager on RHEL 8/OL 8 on x86" navTitle: "RHEL 8/OL 8" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index 8f9dcb253c4..505c352ac5d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +title: "Installing Failover Manager on Rocky Linux 8/AlmaLinux 8 on x86" navTitle: "Rocky Linux 8/AlmaLinux 8" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index 097390aa2ee..b00d4f9416f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "RHEL 7/OL 7 on x86_64" +title: "Installing Failover Manager on RHEL 7/OL 7 on x86" navTitle: "RHEL 7/OL 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 312bfdfaac2..7e58afb1256 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "CentOS 7 on x86_64" +title: "Installing Failover Manager on CentOS 7 on x86" navTitle: "CentOS 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index 4f20bd5efbc..d5e033bc346 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -1,5 +1,5 @@ --- -title: "SLES 15 on x86_64" +title: "Installing Failover Manager on SLES 15 on x86" navTitle: "SLES 15" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index debc97606cf..bb9e0573e32 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,5 +1,5 @@ --- -title: "SLES 12 on x86_64" +title: "Installing Failover Manager on SLES 12 on x86" navTitle: "SLES 12" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index 3965ae27b2f..b7d8cda694a 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -1,5 +1,5 @@ --- -title: "Ubuntu 20.04/Debian 10 on x86_64" +title: "Installing Failover Manager on Ubuntu 20.04/Debian 10 on x86" navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index 0554bb748b4..d919c05768a 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Ubuntu 18.04/Debian 9 on x86_64" +title: "Installing Failover Manager on Ubuntu 18.04/Debian 9 on x86" navTitle: "Ubuntu 18.04/Debian 9" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx index b8caaa56458..8144d15c0e2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx @@ -1,14 +1,14 @@ --- -title: "x86_64 (amd64)" +title: "Installing Failover Manager on x86 (amd64)" +navTitle: "86 (amd64)" --- -For platform-specific install instructions, including accessing the repo, see: +For operating system-specific install instructions, including accessing the repo, see: -- Linux x86-64 (amd64): - [RHEL 8/OL 8](01_efm4_rhel_8_x86) - [Rocky Linux 8/AlmaLinux 8](02_efm4_other_linux8_x86) @@ -19,5 +19,3 @@ For platform-specific install instructions, including accessing the repo, see: - [Ubuntu 20.04/Debian 10](07_efm4_ubuntu20_deb10_x8) - [Ubuntu 18.04/Debian 9](08_efm4_ubuntu18_deb9_x86) - -After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file From e4ad7a8ad95964627ec86854029c3da664399d06 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 07:11:04 -0400 Subject: [PATCH 06/12] cleanup --- .../03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx | 2 +- .../03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx | 2 +- .../ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx | 2 +- .../ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx | 2 +- .../docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx | 1 + product_docs/docs/efm/4/03_installing_efm/index.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx | 2 +- .../4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx | 2 +- product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx | 2 +- 15 files changed, 15 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index 67fd187b278..0434589491e 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on RHEL 8 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 8 IBM Power (ppc64le)" navTitle: "RHEL 8 " --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index ecc2ad546a2..101ed186612 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on RHEL 7 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 7 IBM Power (ppc64le)" navTitle: "RHEL 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index 9ad0025e6de..71a2a1e2c6a 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on SLES 15 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 15 IBM Power (ppc64le)" navTitle: "SLES 15" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index a180d92867c..749202f6037 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on SLES 12 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 12 IBM Power (ppc64le)" navTitle: "SLES 12" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx index e78956b4934..b87affd70fc 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx @@ -1,5 +1,6 @@ --- title: "Installing Failover Manager on IBM Power (ppc64le)" +navTitle: "IBM Power (ppc64le)" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/index.mdx b/product_docs/docs/efm/4/03_installing_efm/index.mdx index 9b5de2e611d..b1ae25b73d7 100644 --- a/product_docs/docs/efm/4/03_installing_efm/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/index.mdx @@ -1,5 +1,6 @@ --- title: "Installing Failover Manager on Linux" +navTitle: "Installing on Linux" redirects: - ../efm_user/03_installing_efm legacyRedirectsGenerated: @@ -45,4 +46,3 @@ For platform-specific install instructions, including accessing the repo, see: - [SLES 15](11_efm4_sles15_ppcle) - [SLES 12](12_efm4_sles12_ppcle) -After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index b00b2b23da4..e333417b5fc 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on RHEL 8/OL 8 on x86" +title: "Installing Failover Manager on RHEL 8/OL 8 x86" navTitle: "RHEL 8/OL 8" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index 505c352ac5d..b1016129be2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on Rocky Linux 8/AlmaLinux 8 on x86" +title: "Installing Failover Manager on Rocky Linux 8/AlmaLinux 8 x86" navTitle: "Rocky Linux 8/AlmaLinux 8" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index b00d4f9416f..010917bad20 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on RHEL 7/OL 7 on x86" +title: "Installing Failover Manager on RHEL 7/OL 7 x86" navTitle: "RHEL 7/OL 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 7e58afb1256..c06fafe78a1 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on CentOS 7 on x86" +title: "Installing Failover Manager on CentOS 7 x86" navTitle: "CentOS 7" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index d5e033bc346..5d08639f3db 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on SLES 15 on x86" +title: "Installing Failover Manager on SLES 15 x86" navTitle: "SLES 15" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index bb9e0573e32..3e85654e93f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on SLES 12 on x86" +title: "Installing Failover Manager on SLES 12 x86" navTitle: "SLES 12" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index b7d8cda694a..c35a48eb336 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on Ubuntu 20.04/Debian 10 on x86" +title: "Installing Failover Manager on Ubuntu 20.04/Debian 10 x86" navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index d919c05768a..ab609acf44d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Failover Manager on Ubuntu 18.04/Debian 9 on x86" +title: "Installing Failover Manager on Ubuntu 18.04/Debian 9 x86" navTitle: "Ubuntu 18.04/Debian 9" --- diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx index 8144d15c0e2..1041a5811bd 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx @@ -1,6 +1,6 @@ --- title: "Installing Failover Manager on x86 (amd64)" -navTitle: "86 (amd64)" +navTitle: "x86 (amd64)" --- From 3008f84724e2ec5d142b3d7e17fc662d825e9cbb Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 07:54:02 -0400 Subject: [PATCH 07/12] restoring individual topics structure --- .../09_mtk55_rhel8_ppcle.mdx | 63 ++++++++++ .../10_mtk55_rhel7_ppcle.mdx | 77 ++++++++++++ .../11_mtk55_sles15_ppcle.mdx | 51 ++++++++ .../12_mtk55_sles12_ppcle.mdx | 55 ++++++++ .../13_upgrading_rpm_install.mdx | 15 +++ .../x86_amd64/01_mtk55_rhel8_x86.mdx | 118 ++++++++++++++++++ .../x86_amd64/02_mtk55_other_linux8_x86.mdx | 118 ++++++++++++++++++ .../x86_amd64/03_mtk55_rhel7_x86.mdx | 107 ++++++++++++++++ .../x86_amd64/04_mtk55_centos7_x86.mdx | 107 ++++++++++++++++ .../x86_amd64/05_mtk55_sles15_x86.mdx | 51 ++++++++ .../x86_amd64/06_mtk55_sles12_x86.mdx | 63 ++++++++++ .../x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx | 56 +++++++++ .../x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx | 56 +++++++++ 13 files changed, 937 insertions(+) create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx create mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx new file mode 100644 index 00000000000..adab91ce0df --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx @@ -0,0 +1,63 @@ +--- +title: "RHEL 8 on IBM Power (ppc64le)" +--- + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```shell +sudo su - +``` + +## Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```shell + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```shell + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```shell + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```shell + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```shell + dnf -qy module disable postgresql + ``` + +## Installing the Package + +```shell +dnf -y install edb-migrationtoolkit +``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx new file mode 100644 index 00000000000..6ca7ac63eff --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx @@ -0,0 +1,77 @@ +--- +title: "RHEL 7 on IBM Power (ppc64le)" +--- + + + +You can use an RPM package to install Migration Toolkit on a RHEL ppc64le host. + +Before installing Migration toolkit: + +1. Create the Advance Toolchain repository configuration file; assume superuser privileges and invoke the following command: + + ```text + rpm --import https://public.dhe.ibm.com/software/server/POWER/ + Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + ``` + +2. After creating the `advance-toolchain.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [advance-toolchain] + name=Advance Toolchain IBM FTP + baseurl=https://public.dhe.ibm.com/software/server/POWER/ + Linux/toolchain/at/redhat/RHEL7 + failovermethod=priority + enabled=1 + gpgcheck=1 + gpgkey=ftp://public.dhe.ibm.com/software/server/POWER/Linux/ + toolchain/at/redhat/RHELX/gpg-pubkey-6976a827-5164221b + ``` + +The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +## Creating a Repository Configuration File + +1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: + + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL package: + + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +4. Enable an additional repository to resolve dependencies: + + ```text + subscription-manager repos --enable "rhel-*-optional-rpms" + --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* + -server-rpms" + ``` +## Installing the Package +To install Migration Toolkit, run the following command. + +```text +yum -y install edb-migrationtoolkit +``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx new file mode 100644 index 00000000000..3b00332523c --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx @@ -0,0 +1,51 @@ +--- +title: "SLES 15 on IBM Power (ppc64le)" +--- + + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +## Setting up the Repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/15.3/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Installing the Package + +```shell +zypper -n install edb-migrationtoolkit +``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx new file mode 100644 index 00000000000..1a28617bb17 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx @@ -0,0 +1,55 @@ +--- +title: "SLES 12 on IBM Power (ppc64le)" +--- + + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +## Setting up the Repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/12.5/ppc64le +SUSEConnect -p sle-sdk/12.5/ppc64le + +# Refresh the metadata +zypper refresh + +# Install OpenJDK (version 1.8) +zypper -n install java-1_8_0-openjdk +``` + +## Installing the Package + +```shell +zypper -n install edb-migrationtoolkit +``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx new file mode 100644 index 00000000000..376519e4f44 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx @@ -0,0 +1,15 @@ +--- +title: Upgrading an RPM Installation +--- + +If you have an existing 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: + +```text +yum upgrade edb-repo +``` + +yum will update the edb.repo file to enable access to the current EnterpriseDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum to upgrade Migration toolkit: + +```text +yum upgrade edb-migrationtoolkit +``` diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx new file mode 100644 index 00000000000..f0511868666 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx @@ -0,0 +1,118 @@ +--- +title: "RHEL 8/OL 8 on x86_64" +--- + + +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +## Creating a Repository Configuration File + +1. To create the repository configuration file, assume superuser privileges and invoke the following command + + ```text + dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + + ```text + dnf -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-8.noarch.rpm + ``` + +4. Enable the codeready-builder repository to resolve dependencies: + + ```text + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for + -rhel-8-${ARCH}-rpms" + ``` + +## Installing Migration Toolkit + +```text +dnf -y install edb-migrationtoolkit +``` + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +## Using Migration Toolkit with IDENT Authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx new file mode 100644 index 00000000000..0338dc2f0fe --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx @@ -0,0 +1,118 @@ +--- +title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +--- + + +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +## Creating a Repository Configuration File + +1. To create the repository configuration file, assume superuser privileges and invoke the following command + + ```text + dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + ``` + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + + ```text + dnf -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-8.noarch.rpm + ``` + +4. Enable the codeready-builder repository to resolve dependencies: + + ```text + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for + -rhel-8-${ARCH}-rpms" + ``` + +## Installing Migration Toolkit + +```text +dnf -y install edb-migrationtoolkit +``` + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +## Using Migration Toolkit with IDENT Authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx new file mode 100644 index 00000000000..e0a0046df40 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx @@ -0,0 +1,107 @@ +--- +title: "RHEL 7/OL 7 on x86_64" +--- + + +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +## Creating a Repository Configuration File + +1. To create the repository configuration file, assume superuser privileges and invoke the following command: + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +## Installing Migration Toolkit + +```shell +yum -y install edb-migrationtoolkit +``` + + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +## Using Migration Toolkit with IDENT Authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx new file mode 100644 index 00000000000..72c0ba3e43a --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx @@ -0,0 +1,107 @@ +--- +title: "CentOS 7 on x86_64" +--- + + +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. + +## Creating a Repository Configuration File + +1. To create the repository configuration file, assume superuser privileges and invoke the following command: + ```text + yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ + edb-repo-latest.noarch.rpm + + The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. + + ```text + [edb] + name=EnterpriseDB RPMs $releasever - $basearch + baseurl=https://:@yum.enterprisedb.com/ + edb/ + redhat/rhel-$releasever-$basearch + enabled=1 + gpgcheck=1 + gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + ``` + +3. After saving your changes to the configuration file, install the EPEL repository: + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/ + epel-release-latest-7.noarch.rpm + ``` + +## Installing Migration Toolkit + +```shell +yum -y install edb-migrationtoolkit +``` + + +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. + +After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. + +## Using Migration Toolkit with IDENT Authentication + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: + + `yum install xinetd authd` + + The command should create a file named `/etc/xinetd.d/auth` that contains: + + ```text + service auth + { + disable = yes + socket_type = stream + wait = no + user = ident + cps = 4096 10 + instances = UNLIMITED + server = /usr/sbin/in.authd + server_args = -t60 --xerror --os + } + ``` + + !!! Note + If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. + + Then, to start the `identd` server, invoke the commands: + + ```text + systemctl enable xinetd + systemctl start xinetd + ``` + +2. Open the `pg_ident.conf` file and create a user mapping: + + ```text + # map_name system_username postgres_username + edbas enterprisedb enterprisedb + ``` + + Where: + + - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. + - The name specified in the `system_username` column is enterprisedb. + - The name specified in the `postgres_username` column is enterprisedb. + +3. Open the `pg_hba.conf` file and modify the `IDENT` entries. + + On an IPv4 host: + + `host all all 127.0.0.0/0 ident map=edbas` + + On an IPv6 host: + + `host all all ::1/128 ident map=edbas` + +4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx new file mode 100644 index 00000000000..8767d6da935 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx @@ -0,0 +1,51 @@ +--- +title: "SLES 15 on x86_64" +--- + + +There are three steps to completing an installation: + +- [Setting up the repository](#setting-up-the-repository) +- [Installing the package](#installing-the-package) +- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) + +For each step, you must be logged in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +## Setting up the repository + +Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access to +# SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration +# information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module +SUSEConnect -p PackageHub/15.3/x86_64 + +# Refresh the metadata +zypper refresh +``` + +## Installing the package + +```shell +zypper -n install edb-migrationtoolkit +``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx new file mode 100644 index 00000000000..cbfaff50df8 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx @@ -0,0 +1,63 @@ +--- +title: "SLES 12 on x86_64" +--- + + + + +You can use the zypper package manager to install a Migration toolkit on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. + +1. You must assume superuser privileges and stop any firewalls before installing Migration Toolkit. Then, use the following commands to add EnterpriseDB repositories to your system: + + ```text + zypper addrepo https://zypp.enterprisedb.com/suse/ + edb-sles.repo + ``` + +2. The command creates the repository configuration files in the /etc/zypp/repos.d directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: + + ```text + zypper refresh + ``` + + When prompted, provide credentials for the repository; specify `a` to always trust the provided key and update the metadata to include the EnterpriseDB repository. + +3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: + + ```text + SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + + SUSEConnect -p PackageHub/12.5/x86_64 + + SUSEConnect -p sle-sdk/12.5/x86_64 + ``` + +4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: + + ```text + zypper addrepo https://download.opensuse.org/repositories/ + Apache:/Modules/SLE_12_SP4/Apache:Modules.repo + ``` + +5. Use the following command to refresh the metadata: + + ```text + zypper refresh + ``` + +6. Install OpenJDK (version 1.8) for Java based components: + + ```text + zypper -n install java-1_8_0-openjdk + ``` + +7. Now you can use the zypper utility to install a Migration Toolkit: + + ```text + zypper -n install edb-migrationtoolkit + ``` + + For detailed information about registering a SUSE host, visit: + + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx new file mode 100644 index 00000000000..fdf830574d5 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx @@ -0,0 +1,56 @@ +--- +title: "Ubuntu 20.04/Debian 10 on x86_64" +--- + + + +To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. + +1. Assume superuser privileges: + + ```text + sudo su – + ``` + +2. Set up the EnterpriseDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https:// + apt.enterprisedb.com/ + $(lsb_release -cs)-edb/ $(lsb_release -cs) main" + > /etc/ + apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + +1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login + password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + + ```text + apt-get install apt-transport-https + ``` + +1. Add the EBD signing key: + + ```text + wget -q -O - https://username:password + @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - + ``` + +1. Update the repository metadata: + + ```text + apt-get update + ``` + +1. Install the `edb-migrationtoolkit` package: + + ```text + apt-get -y install edb-migrationtoolkit + ``` + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx new file mode 100644 index 00000000000..89c2082f05b --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx @@ -0,0 +1,56 @@ +--- +title: "Ubuntu 18.04/Debian 9 on x86_64" +--- + + + + +To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. + +1. Assume superuser privileges: + + ```text + sudo su – + ``` + +2. Configure the EnterpriseDB repository: + + ```text + sh -c 'echo "deb https://username:password@apt. + enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release + -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release + -cs).list' + ``` + +1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login + password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + + ```text + apt-get install apt-transport-https + ``` + +1. Add the EBD signing key: + + ```text + wget -q -O - https://username:password + @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - + ``` + +1. Update the repository metadata: + + ```text + apt-get update + ``` + +1. Install the `edb-migrationtoolkit` package: + + ```text + apt-get -y install edb-migrationtoolkit + ``` + From 46b2fc421bb94bbd2a73dd29f920c14c9d15e950 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 08:47:54 -0400 Subject: [PATCH 08/12] more cleanup --- .../55/03_migration_methodology.mdx | 101 --- .../55/05_installing_mtk/index.mdx | 4 +- .../09_mtk55_rhel8_ppcle.mdx | 8 +- .../10_mtk55_rhel7_ppcle.mdx | 7 +- .../11_mtk55_sles15_ppcle.mdx | 7 +- .../12_mtk55_sles12_ppcle.mdx | 7 +- .../13_upgrading_rpm_install.mdx | 15 - .../ibm_power_ppc64le/index.mdx | 235 +------ .../install_on_linux_using_edb_repo/index.mdx | 26 +- .../x86_amd64/01_mtk55_rhel8_x86.mdx | 7 +- .../x86_amd64/02_mtk55_other_linux8_x86.mdx | 7 +- .../x86_amd64/03_mtk55_rhel7_x86.mdx | 7 +- .../x86_amd64/04_mtk55_centos7_x86.mdx | 7 +- .../x86_amd64/05_mtk55_sles15_x86.mdx | 3 +- .../x86_amd64/06_mtk55_sles12_x86.mdx | 3 +- .../x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx | 3 +- .../x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx | 3 +- .../x86_amd64/index.mdx | 598 +----------------- 18 files changed, 74 insertions(+), 974 deletions(-) delete mode 100644 product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx delete mode 100644 product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx diff --git a/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx b/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx deleted file mode 100644 index 48d46570678..00000000000 --- a/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: "Migration methodology" - ---- - - - -You might consider migrating from one database to another for many reasons. Migration can allow you to take advantage of new or better technology. If your current database doesn't offer the right set of capabilities to allow you to scale the system, moving to a database that offers the functionality you need is the best move for your company. - -Migration can also be cost effective. Migrating systems with significant maintenance costs can save money spent on system upkeep. By consolidating the number of databases in use, you can also reduce in-house administrative costs. By using fewer database platforms (or possibly taking advantage of database compatibility), you can do more with your IT budget. - -Using more than one database platform can offer you a graceful migration path if a vendor raises their pricing or changes their company directive. EnterpriseDB has, for years, helped companies migrate their existing database systems to Postgres. - - - -## The migration process - -The migration path to Postgres that we recommend includes the following main steps: - -1. Start the migration process by determining the database objects and data to include in the migration. Form a migration team that includes someone with solid knowledge of the architecture and implementation of the source system. - -2. Identify potential migration problems. If it is an Oracle-to-EDB Postgres Advanced Server migration, consult the [EnterpriseDB Postgres Advanced Server documentation](/epas/latest/) for complete details about the compatibility features supported in EDB Postgres Advanced Server. Consider using the EnterpriseDB migration assessment service to help with this review. - -3. Prepare the migration environment. Obtain and install the needed software, and establish connectivity between the servers. - -4. If the migration involves a large body of data, consider migrating the schema definition before moving the data. Verify the results of the DDL migration and resolve any problems reported in the migration summary. [Migration errors](09_mtk_errors/#mtk_errors) includes information about resolving migration problems. - -5. Migrate the data. For small data sets, use Migration Toolkit. If it's an Oracle migration into EDB Postgres Advanced Server, and the data set is large or if you notice slow data transfer, take advantage of one of the other data movement methods available: - - - Use the EDB Postgres Advanced Server database link feature compatible with Oracle databases. - - If your data has BLOB or CLOB data, use the dblink_ora style database links instead of the Oracle style database links. - - Both of these methods use the Oracle Call Interface (OCI) to connect to Oracle. After connecting, use an SQL statement to select the data from the 'linked' Oracle database and insert the data into the EDB Postgres Advanced Server database. - -6. Confirm the results of the data migration, and resolve any problems reported in the migration summary. - -7. Convert applications to work with the newly migrated Postgres database. Applications that use open standard connectivity such as JDBC or ODBC normally require changes only to the database connection strings and selection of the EnterpriseDB driver. See [Connecting an application to Postgres](#connecting_application_postgres) for more information. - -8. Test the system performance, and tune the new server. If you're migrating into an EDB Postgres Advanced Server database, take advantage of EDB Postgres Advanced Server's performance tuning utilities: - - - Use Dynatune to dynamically adjust database configuration resources. - - Use Optimizer Hints to direct the query path. - - Use the `ANALYZE` command to retrieve database statistics. - - See [EDB Postgres Advanced Server](../../epas/latest) and [Database Compatibility for Oracle Developers](../../epas/latest/epas_compat_tools_guide/) for information about the performance tuning tools available with EDB Postgres Advanced Server. - - - -## Connecting an application to Postgres - -To convert a client application to use a Postgres database, you must modify the connection properties to specify the new target database. In the case of a Java application, change the JDBC driver name (`Class.forName`) and JDBC URL. - -A Java application running on Oracle might have the following connection properties: - -```text -Class.forName("oracle.jdbc.driver.OracleDriver"); -Connection con = -DriverManager.getConnection -("jdbc:oracle:thin:@localhost:1521:xe", - "user", - "password") -``` - -Modify the connection string to connect to a Postgres server: - -```text -Class.forName("com.edb.Driver") -Connection con = DriverManager.getConnection -("jdbc:edb://localhost:5444/edb", - "user", - "password"); -``` - -Converting an ODBC application to connect to an instance of Postgres is a two-step process. - -1. To connect an ODBC application, use an ODBC data source administrator to create a data source that defines the connection properties for the new target database. - - Most Linux and Windows systems include graphical tools that allow you to create and edit ODBC data sources. After installing ODBC, check the **Administrative Tools** menu for a link to the ODBC Data Source Administrator. Select **Add** to start the Create New Data Source wizard. Then, complete the dialogs to define the new target data source. - -2. Change the application to use the new data source. - - The application contains a call to `SQLConnect` or `SQLDriverConnect`. Edit the invocation to change the data source name. In the following example, the data source is named `OracleDSN`: - - ```text - result = SQLConnect(conHandle, // Connection handle - (returned) - "OracleDSN", SQL_NTS, // Data source name - username, SQL_NTS, // User name - password, SQL_NTS); // Password - ``` - -To connect to an instance of Postgres defined in a data source named `PostgresDSN`, change the data source name: - -```text -result = SQLConnect(conHandle, // Connection handle (returned) - "PostgresDSN", SQL_NTS, // Data source name - username, SQL_NTS, // User name - password, SQL_NTS); // Password -``` - -After establishing a connection between the application and the server, test the application to find any compatibility problems between the application and the migrated schema. In most cases, a simple change resolves any incompatibility that the application encounters. When a feature is not supported, use a workaround or third-party tool to provide the functionality required by the application. See [Migration errors](09_mtk_errors/#mtk_errors), for information about some common problems and their workarounds. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx index d495b9deb60..2782e810f87 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx @@ -27,8 +27,8 @@ You can install Migration Toolkit on: -## Installing Source-Specific Drivers +## Installing source-specific drivers -Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, see the [Third Party JDBC Drivers](https://www.enterprisedb.com/software-downloads-postgres#third-party-jdbc-drivers) on the Downloads page. +Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, see [Third Party JDBC Drivers](https://www.enterprisedb.com/software-downloads-postgres#third-party-jdbc-drivers) on the Downloads page. After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx index adab91ce0df..5deef52379e 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 8 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on RHEL 8 IBM Power (ppc64le)" +navTitle: "RHEL 8" --- There are two steps to completing an installation: @@ -15,7 +16,7 @@ To log in as a superuser: sudo su - ``` -## Setting up the Repository +## Setting up the repository 1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). @@ -55,9 +56,8 @@ sudo su - dnf -qy module disable postgresql ``` -## Installing the Package +## Installing the package ```shell dnf -y install edb-migrationtoolkit ``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx index 6ca7ac63eff..0759e040d20 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 7 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on RHEL 7 IBM Power (ppc64le)" +navTitle: "RHEL 7" --- @@ -31,7 +32,7 @@ Before installing Migration toolkit: The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: @@ -68,7 +69,7 @@ The following steps provide detailed information about accessing the EnterpriseD --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* -server-rpms" ``` -## Installing the Package +## Installing the package To install Migration Toolkit, run the following command. ```text diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx index 3b00332523c..40012bec8b1 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on SLES 15 IBM Power (ppc64le)" +navTitle: "SLES 15 " --- @@ -18,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -43,7 +44,7 @@ SUSEConnect -p PackageHub/15.3/ppc64le zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-migrationtoolkit diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx index 1a28617bb17..18c008ea2be 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on SLES 12 IBM Power (ppc64le)" +navTitle: "SLES 12 " --- @@ -18,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -47,7 +48,7 @@ zypper refresh zypper -n install java-1_8_0-openjdk ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-migrationtoolkit diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx deleted file mode 100644 index 376519e4f44..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/13_upgrading_rpm_install.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Upgrading an RPM Installation ---- - -If you have an existing 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: - -```text -yum upgrade edb-repo -``` - -yum will update the edb.repo file to enable access to the current EnterpriseDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum to upgrade Migration toolkit: - -```text -yum upgrade edb-migrationtoolkit -``` diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx index 812f02e978d..cbc6623544c 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx @@ -1,238 +1,17 @@ --- -title: "Installing on Linux x86-64 (amd64)" +title: "Installing Migration Toolkit on IBM Power (ppc64le)" navTitle: "IBM Power (ppc64le)" --- -## RHEL 8 +For operating system-specific install instructions, see: -There are two steps to completing an installation: -- Setting up the repository -- Installing the package + - [RHEL 8](09_mtk55_rhel8_ppcle) -For each step, you must be logged in as superuser. + - [RHEL 7](10_mtk55_rhel7_ppcle) + - [SLES 15](11_mtk55_sles15_ppcle) + - [SLES 12](12_mtk55_sles12_ppcle) -To log in as a superuser: - -```shell -sudo su - -``` - -### Setting up the repository - -1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -1. Set up the EDB repository: - - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - This creates the /etc/yum.repos.d/edb.repo configuration file. - -1. Add your EDB credentials to the edb.repo file: - - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - - where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). - -1. Install the EPEL repository and refresh the cache: - - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` - -1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: - - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` - -1. Disable the built-in PostgreSQL module: - ```shell - dnf -qy module disable postgresql - ``` - -### Installing the package - -```shell -dnf -y install edb-migrationtoolkit -``` - -## RHEL 7 - -You can use an RPM package to install Migration Toolkit on a RHEL ppc64le host. - -Before installing Migration toolkit: - -1. Create the Advance Toolchain repository configuration file; assume superuser privileges and invoke the following command: - - ```text - rpm --import https://public.dhe.ibm.com/software/server/POWER/ - Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b - ``` - -2. After creating the `advance-toolchain.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [advance-toolchain] - name=Advance Toolchain IBM FTP - baseurl=https://public.dhe.ibm.com/software/server/POWER/ - Linux/toolchain/at/redhat/RHEL7 - failovermethod=priority - enabled=1 - gpgcheck=1 - gpgkey=ftp://public.dhe.ibm.com/software/server/POWER/Linux/ - toolchain/at/redhat/RHELX/gpg-pubkey-6976a827-5164221b - ``` - -The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -### Creating a repository configuration file - -1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: - - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL package: - - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -4. Enable an additional repository to resolve dependencies: - - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" - --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* - -server-rpms" - ``` -### Installing the package -To install Migration Toolkit, run the following command. - -```text -yum -y install edb-migrationtoolkit -``` -## SLES 15 - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -### Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` - -### Installing the package - -```shell -zypper -n install edb-migrationtoolkit -``` -## SLES 12 - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -### Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh - -# Install OpenJDK (version 1.8) -zypper -n install java-1_8_0-openjdk -``` - -### Installing the package - -```shell -zypper -n install edb-migrationtoolkit -``` +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../../#installing_drivers) for more information. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx index 6c9d54d7b6a..6145e785acf 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx @@ -12,23 +12,23 @@ To install Migration Toolkit, you must have credentials that allow access to the For platform-specific install instructions, see: - Linux x86-64 (amd64): - - [RHEL 8/OL 8](01_mtk55_rhel8_x86) + - [RHEL 8/OL 8](x86_amd64/01_mtk55_rhel8_x86) - - [Rocky Linux 8/AlmaLinux 8](02_mtk55_other_linux8_x86) - - [RHEL 7/OL 7](03_mtk55_rhel7_x86) - - [CentOS 7](04_mtk55_centos7_x86) - - [SLES 15](05_mtk55_sles15_x86) - - [SLES 12](06_mtk55_sles12_x86) - - [Ubuntu 20.04/Debian 10](07_mtk55_ubuntu20_deb10_x86) - - [Ubuntu 18.04/Debian 9](08_mtk55_ubuntu18_deb9_x86) + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/02_mtk55_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/03_mtk55_rhel7_x86) + - [CentOS 7](x86_amd64/04_mtk55_centos7_x86) + - [SLES 15](x86_amd64/05_mtk55_sles15_x86) + - [SLES 12](x86_amd64/06_mtk55_sles12_x86) + - [Ubuntu 20.04/Debian 10](x86_amd64/07_mtk55_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](x86_amd64/08_mtk55_ubuntu18_deb9_x86) - Linux on IBM Power (ppc64le): - - [RHEL 8](09_mtk55_rhel8_ppcle) + - [RHEL 8](ibm_power_ppc64le/09_mtk55_rhel8_ppcle) - - [RHEL 7](10_mtk55_rhel7_ppcle) - - [SLES 15](11_mtk55_sles15_ppcle) - - [SLES 12](12_mtk55_sles12_ppcle) + - [RHEL 7](ibm_power_ppc64le/10_mtk55_rhel7_ppcle) + - [SLES 15](ibm_power_ppc64le/11_mtk55_sles15_ppcle) + - [SLES 12](ibm_power_ppc64le/12_mtk55_sles12_ppcle) -After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing Source-Specific Drivers](../#installing_drivers) for more information. +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../#installing_drivers) for more information. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx index f0511868666..ceb8bb20498 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx @@ -1,11 +1,12 @@ --- -title: "RHEL 8/OL 8 on x86_64" +title: "Installing Migration Toolkit on RHEL 8/OL 8 x86" +navTitle: "RHEL 8/OL 8" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command @@ -56,7 +57,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx index 0338dc2f0fe..e1db7cd2d2f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx @@ -1,11 +1,12 @@ --- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +title: "Installing Migration Toolkit on Rocky Linux 8/AlmaLinux 8 x86" +navTitle: "Rocky Linux 8/AlmaLinux 8" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command @@ -56,7 +57,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx index e0a0046df40..9a9c04e3b3b 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx @@ -1,11 +1,12 @@ --- -title: "RHEL 7/OL 7 on x86_64" +title: "Installing Migration Toolkit on RHEL 7/OL 7 x86" +navTitle: "RHEL 7/OL 7 " --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -46,7 +47,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx index 72c0ba3e43a..a4c05916546 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx @@ -1,11 +1,12 @@ --- -title: "CentOS 7 on x86_64" +title: "Installing Migration Toolkit on CentOS 7 x86" +title: "CentOS 7" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -46,7 +47,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx index 8767d6da935..705ca7532b9 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on x86_64" +title: "Installing Migration Toolkit on SLES 15 x86" +navTitle: "SLES 15" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx index cbfaff50df8..c3cf5ba2478 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on x86_64" +title: "Installing Migration Toolkit on SLES 12 x86" +title: "SLES 12" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx index fdf830574d5..f6093923a18 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 20.04/Debian 10 on x86_64" +title: "Installing Migration Toolkit on Ubuntu 20.04/Debian 10 x86" +navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx index 89c2082f05b..ec2fa554a5a 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 18.04/Debian 9 on x86_64" +title: "Installing Migration Toolkit on Ubuntu 18.04/Debian 9 x86" +navTitle: "Ubuntu 18.04/Debian 9" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx index 4b8711116ab..46020334941 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx @@ -1,592 +1,18 @@ --- -title: "Installing on Linux x86-64 (amd64)" -navTitle: "Intel x86-64 (amd64)" +title: "Installing Migration Toolkit on Linux x86 (amd64)" +navTitle: "Intel x86 (amd64)" --- -To install Migration Toolkit, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). - -## RHEL 8/OL 8 - -You can use an RPM package to install Migration Toolkit on a RHEL 8/OL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -### Creating a Repository Configuration File - -1. To create the repository configuration file, assume superuser privileges and invoke the following command - - ```text - dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-8.noarch.rpm - ``` - -4. Enable the codeready-builder repository to resolve dependencies: - - ```text - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for - -rhel-8-${ARCH}-rpms" - ``` - -### Installing Migration Toolkit - -```text -dnf -y install edb-migrationtoolkit -``` - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -### Using Migration Toolkit with IDENT authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - -## Rocky Linux 8/AlmaLinux 8 - -You can use an RPM package to install Migration Toolkit on a Rocky Linux/AlmaLinux host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -### Creating a repository configuration file - -1. To create the repository configuration file, assume superuser privileges and invoke the following command - - ```text - dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-8.noarch.rpm - ``` - -4. Enable the codeready-builder repository to resolve dependencies: - - ```text - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for - -rhel-8-${ARCH}-rpms" - ``` - -### Installing Migration Toolkit - -```text -dnf -y install edb-migrationtoolkit -``` - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -### Using Migration Toolkit with IDENT authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - -## RHEL 7/OL 7 - -You can use an RPM package to install Migration Toolkit on a RHEL 7/OL 7 host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -### Creating a repository configuration file - -1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -### Installing Migration Toolkit - -```shell -yum -y install edb-migrationtoolkit -``` - -## CentOS 7 - -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. - -### Creating a repository configuration file - -1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ - edb-repo-latest.noarch.rpm - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -2. After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EnterpriseDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/ - edb/ - redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -3. After saving your changes to the configuration file, install the EPEL repository: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/ - epel-release-latest-7.noarch.rpm - ``` - -### Installing Migration Toolkit - -```shell -yum -y install edb-migrationtoolkit -``` - - -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. - -After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. - -### Using Migration Toolkit with IDENT authentication - -By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: - -1. Confirm that an `identd` server is installed and running. You can use the yum package manager to install an `identd` server by invoking the command: - - `yum install xinetd authd` - - The command should create a file named `/etc/xinetd.d/auth` that contains: - - ```text - service auth - { - disable = yes - socket_type = stream - wait = no - user = ident - cps = 4096 10 - instances = UNLIMITED - server = /usr/sbin/in.authd - server_args = -t60 --xerror --os - } - ``` - - !!! Note - If the file includes a `-E` argument at the end of `server_args`, please erase the `-E`. - - Then, to start the `identd` server, invoke the commands: - - ```text - systemctl enable xinetd - systemctl start xinetd - ``` - -2. Open the `pg_ident.conf` file and create a user mapping: - - ```text - # map_name system_username postgres_username - edbas enterprisedb enterprisedb - ``` - - Where: - - - The name specified in the `map_name` column is a user-defined name that will identify the mapping in the pg_hba.conf file. - - The name specified in the `system_username` column is enterprisedb. - - The name specified in the `postgres_username` column is enterprisedb. - -3. Open the `pg_hba.conf` file and modify the `IDENT` entries. - - On an IPv4 host: - - `host all all 127.0.0.0/0 ident map=edbas` - - On an IPv6 host: - - `host all all ::1/128 ident map=edbas` - -4. Restart the EDB Postgres Advanced Server service before invoking Migration Toolkit. - -## SLES 15 - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -### Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 - -# Refresh the metadata -zypper refresh -``` - -### Installing the package - -```shell -zypper -n install edb-migrationtoolkit -``` -## SLES 12 - - - -You can use the zypper package manager to install a Migration toolkit on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. - -1. You must assume superuser privileges and stop any firewalls before installing Migration Toolkit. Then, use the following commands to add EnterpriseDB repositories to your system: - - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/ - edb-sles.repo - ``` - -2. The command creates the repository configuration files in the /etc/zypp/repos.d directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: - - ```text - zypper refresh - ``` - - When prompted, provide credentials for the repository; specify `a` to always trust the provided key and update the metadata to include the EnterpriseDB repository. - -3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: - - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - - SUSEConnect -p PackageHub/12.5/x86_64 - - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` - -4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: - - ```text - zypper addrepo https://download.opensuse.org/repositories/ - Apache:/Modules/SLE_12_SP4/Apache:Modules.repo - ``` - -5. Use the following command to refresh the metadata: - - ```text - zypper refresh - ``` - -6. Install OpenJDK (version 1.8) for Java based components: - - ```text - zypper -n install java-1_8_0-openjdk - ``` - -7. Now you can use the zypper utility to install a Migration Toolkit: - - ```text - zypper -n install edb-migrationtoolkit - ``` - - For detailed information about registering a SUSE host, visit: - - - -## Ubuntu 20.04/Debian 10 - - - -To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. - -1. Assume superuser privileges: - - ```text - sudo su – - ``` - -2. Set up the EnterpriseDB repository: - - ```text - sh -c 'echo "deb [arch=amd64] https:// - apt.enterprisedb.com/ - $(lsb_release -cs)-edb/ $(lsb_release -cs) main" - > /etc/ - apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - -1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login - password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -1. Add support to your system for secure APT repositories: - - ```text - apt-get install apt-transport-https - ``` - -1. Add the EBD signing key: - - ```text - wget -q -O - https://username:password - @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - - ``` - -1. Update the repository metadata: - - ```text - apt-get update - ``` - -1. Install the `edb-migrationtoolkit` package: - - ```text - apt-get -y install edb-migrationtoolkit - ``` -## Ubuntu 18.04/Debian 9 - - - -To install a package with apt, complete the following steps. When invoking the commands, replace the `username` and `password` with the user credentials provided by EnterpriseDB. - -1. Assume superuser privileges: - - ```text - sudo su – - ``` - -2. Configure the EnterpriseDB repository: - - ```text - sh -c 'echo "deb https://username:password@apt. - enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release - -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release - -cs).list' - ``` - -1. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login - password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -1. Add support to your system for secure APT repositories: - - ```text - apt-get install apt-transport-https - ``` - -1. Add the EBD signing key: - - ```text - wget -q -O - https://username:password - @apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - - ``` - -1. Update the repository metadata: - - ```text - apt-get update - ``` - -1. Install the `edb-migrationtoolkit` package: - - ```text - apt-get -y install edb-migrationtoolkit - ``` +For operating system-specific install instructions, see: + - [RHEL 8/OL 8](01_mtk55_rhel8_x86) + - [Rocky Linux 8/AlmaLinux 8](02_mtk55_other_linux8_x86) + - [RHEL 7/OL 7](03_mtk55_rhel7_x86) + - [CentOS 7](04_mtk55_centos7_x86) + - [SLES 15](05_mtk55_sles15_x86) + - [SLES 12](06_mtk55_sles12_x86) + - [Ubuntu 20.04/Debian 10](07_mtk55_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](08_mtk55_ubuntu18_deb9_x86) +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../../#installing_drivers) for more information. \ No newline at end of file From b10b56135568fdf4ad3f1008b26a71af1720ae04 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 09:46:12 -0400 Subject: [PATCH 09/12] even more cleanup --- .../03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx | 2 +- .../03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx | 2 +- .../efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx | 2 +- .../4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx | 2 +- .../x86_amd64/06_mtk55_sles12_x86.mdx | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index 0434589491e..5b1941b348d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -64,7 +64,7 @@ dnf -y install edb-efm ``` where `` is the version number of Failover Manager. -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index 101ed186612..b7ae49316fa 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -55,7 +55,7 @@ To request credentials that allow you to access an EnterpriseDB repository, see ```text yum -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index e333417b5fc..ab87c4b7491 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -48,7 +48,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index b1016129be2..fe78bb40ae1 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -47,7 +47,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index 010917bad20..7530393a1dc 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -46,7 +46,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index c06fafe78a1..9716f585537 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -40,7 +40,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index c35a48eb336..506a2f11374 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -38,7 +38,7 @@ Use the EnterpriseDB APT repository to install Failover Manager. ```text apt-get -y install edb-efm42 ``` -## "Initial configuration" +## Initial configuration If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx index c3cf5ba2478..431eb100c3f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx @@ -1,6 +1,6 @@ --- title: "Installing Migration Toolkit on SLES 12 x86" -title: "SLES 12" +navTitle: "SLES 12" --- From 1475260d82979ac608aff4b971b8b9f6bc0cedb8 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Apr 2022 10:37:05 -0400 Subject: [PATCH 10/12] another fix --- .../x86_amd64/04_mtk55_centos7_x86.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx index a4c05916546..0dce19a5033 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx @@ -1,6 +1,6 @@ --- title: "Installing Migration Toolkit on CentOS 7 x86" -title: "CentOS 7" +navTitle: "CentOS 7" --- From f6e35180d0a295179c57636c86a019bd45e010cd Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Apr 2022 06:39:47 -0400 Subject: [PATCH 11/12] final cleanup --- .../ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx | 12 +++++----- .../ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx | 8 +++---- .../11_efm4_sles15_ppcle.mdx | 12 +++++----- .../12_efm4_sles12_ppcle.mdx | 10 ++++---- .../docs/efm/4/03_installing_efm/index.mdx | 24 +++++++++---------- .../x86_amd64/01_efm4_rhel_8_x86.mdx | 8 +++---- .../x86_amd64/02_efm4_other_linux8_x86.mdx | 8 +++---- .../x86_amd64/03_efm4_rhel7_x86.mdx | 8 +++---- .../x86_amd64/04_efm4_centos7_x86.mdx | 6 ++--- .../x86_amd64/05_efm4_sles15_x86.mdx | 14 +++++------ .../x86_amd64/06_efm4_sles12_x86.mdx | 8 +++---- .../x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx | 8 +++---- .../x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx | 8 +++---- .../55/05_installing_mtk/index.mdx | 2 +- .../09_mtk55_rhel8_ppcle.mdx | 0 .../10_mtk55_rhel7_ppcle.mdx | 0 .../11_mtk55_sles15_ppcle.mdx | 0 .../12_mtk55_sles12_ppcle.mdx | 0 .../ibm_power_ppc64le/index.mdx | 0 .../index.mdx | 0 .../x86_amd64/01_mtk55_rhel8_x86.mdx | 0 .../x86_amd64/02_mtk55_other_linux8_x86.mdx | 0 .../x86_amd64/03_mtk55_rhel7_x86.mdx | 0 .../x86_amd64/04_mtk55_centos7_x86.mdx | 0 .../x86_amd64/05_mtk55_sles15_x86.mdx | 0 .../x86_amd64/06_mtk55_sles12_x86.mdx | 0 .../x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx | 0 .../x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx | 0 .../x86_amd64/index.mdx | 0 29 files changed, 68 insertions(+), 68 deletions(-) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/ibm_power_ppc64le/index.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/index.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/01_mtk55_rhel8_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/02_mtk55_other_linux8_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/03_mtk55_rhel7_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/04_mtk55_centos7_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/05_mtk55_sles15_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/06_mtk55_sles12_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx (100%) rename product_docs/docs/migration_toolkit/55/05_installing_mtk/{install_on_linux_using_edb_repo => install_on_linux}/x86_amd64/index.mdx (100%) diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index 5b1941b348d..5374ce64157 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -17,7 +17,7 @@ To log in as a superuser: sudo su - ``` -#### Setting up the Repository +## Setting up the repository 1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). @@ -57,7 +57,7 @@ sudo su - dnf -qy module disable postgresql ``` -#### Installing the Package +## Installing the package ```shell dnf -y install edb-efm @@ -66,12 +66,12 @@ where `` is the version number of Failover Manager. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index b7ae49316fa..19e3c681e3b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -57,11 +57,11 @@ To request credentials that allow you to access an EnterpriseDB repository, see ``` ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index 71a2a1e2c6a..b47d1c114b5 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -8,7 +8,7 @@ There are three steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) -- [Performing the initial configuration](12_initial_config) +- [Performing the initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -19,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -44,7 +44,7 @@ SUSEConnect -p PackageHub/15.3/ppc64le zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-efmedb-efm<4x> @@ -58,7 +58,7 @@ If you are using Failover Manager to monitor a cluster owned by a user other tha After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index 749202f6037..efa0caa80a0 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -7,7 +7,7 @@ There are two steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) -- [Initial configuration] +- [Initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -55,11 +55,11 @@ Where <4x> is the version of Failover Manager you are installing. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/index.mdx b/product_docs/docs/efm/4/03_installing_efm/index.mdx index b1ae25b73d7..02260a9419b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/index.mdx @@ -29,20 +29,20 @@ For information about the platforms and versions supported by Failover Manager, For platform-specific install instructions, including accessing the repo, see: - Linux x86-64 (amd64): - - [RHEL 8/OL 8](01_efm4_rhel_8_x86) + - [RHEL 8/OL 8](x86_amd64/01_efm4_rhel_8_x86) - - [Rocky Linux 8/AlmaLinux 8](02_efm4_other_linux8_x86) - - [RHEL 7/OL 7](03_efm4_rhel7_x86) - - [CentOS 7](04_efm4_centos7_x86) - - [SLES 15](05_efm4_sles15_x86) - - [SLES 12](06_efm4_sles12_x86) - - [Ubuntu 20.04/Debian 10](07_efm4_ubuntu20_deb10_x8) - - [Ubuntu 18.04/Debian 9](08_efm4_ubuntu18_deb9_x86) + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/02_efm4_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/03_efm4_rhel7_x86) + - [CentOS 7](x86_amd64/04_efm4_centos7_x86) + - [SLES 15](x86_amd64/05_efm4_sles15_x86) + - [SLES 12](x86_amd64/06_efm4_sles12_x86) + - [Ubuntu 20.04/Debian 10](x86_amd64/07_efm4_ubuntu20_deb10_x8) + - [Ubuntu 18.04/Debian 9](x86_amd64/08_efm4_ubuntu18_deb9_x86) - Linux on IBM Power (ppc64le): - - [RHEL 8](09_efm4_rhel8_ppcle) + - [RHEL 8](ibm_power_pcc64le/09_efm4_rhel8_ppcle) - - [RHEL 7](10_efm4_rhel7_ppcle) - - [SLES 15](11_efm4_sles15_ppcle) - - [SLES 12](12_efm4_sles12_ppcle) + - [RHEL 7](ibm_power_pcc64le/10_efm4_rhel7_ppcle) + - [SLES 15](ibm_power_pcc64le/11_efm4_sles15_ppcle) + - [SLES 12](ibm_power_pcc64le/12_efm4_sles12_ppcle) diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index ab87c4b7491..bbd7434491c 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -50,11 +50,11 @@ After receiving your credentials, you must create the EnterpriseDB repository co ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index fe78bb40ae1..c198cbaa6c2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -49,11 +49,11 @@ After receiving your credentials, you must create the EnterpriseDB repository co ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index 7530393a1dc..e0ec497e10c 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -48,11 +48,11 @@ After receiving your credentials, you must create the EnterpriseDB repository co ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 9716f585537..42d569f931a 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -46,7 +46,7 @@ If you are using Failover Manager to monitor a cluster owned by a user other tha After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index 5d08639f3db..b0571570e73 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -7,7 +7,7 @@ There are three steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) -- [Performing the initial configuration](12_initial_config) +- [Performing the initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -18,7 +18,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -43,7 +43,7 @@ SUSEConnect -p PackageHub/15.3/x86_64 zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-efm<4x> @@ -54,11 +54,11 @@ Where <4x> is the version of Failover Manager you are installing. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index 3e85654e93f..c9fa3dbd81e 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -54,11 +54,11 @@ You can use the `zypper` package manager to install a Failover Manager agent on ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index 506a2f11374..dc06e9c646f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -40,11 +40,11 @@ Use the EnterpriseDB APT repository to install Failover Manager. ``` ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index ab609acf44d..17e92960ce0 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -35,11 +35,11 @@ Use the EnterpriseDB APT repository to install Failover Manager. ``` ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx index 2782e810f87..11d8757749e 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx @@ -20,7 +20,7 @@ Before installing Migration Toolkit, you must install Java (version 1.8.0 or lat You can install Migration Toolkit on: -- [Linux x86-64 (amd64)](x86_amd64) and [IBM Power (ppc64le)](ibm_power_ppc64le) +- [Linux x86-64 (amd64)](install_on_linux/x86_amd64) and [IBM Power (ppc64le)](install_on_linux/ibm_power_ppc64le) - [Windows x86-64](install_on_windows) - [Mac OS X](install_on_mac) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/index.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/index.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/index.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/index.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/01_mtk55_rhel8_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/01_mtk55_rhel8_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/01_mtk55_rhel8_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/02_mtk55_other_linux8_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/02_mtk55_other_linux8_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/02_mtk55_other_linux8_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/03_mtk55_rhel7_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/03_mtk55_rhel7_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/03_mtk55_rhel7_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/04_mtk55_centos7_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/04_mtk55_centos7_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/04_mtk55_centos7_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/05_mtk55_sles15_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/06_mtk55_sles12_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/index.mdx similarity index 100% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/x86_amd64/index.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/index.mdx From 2fbb9cf9a6c52de1a54d4e4ff29069b72ff9e9b6 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Apr 2022 11:28:10 -0400 Subject: [PATCH 12/12] updated filename --- .../docs/migration_toolkit/55/05_installing_mtk/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx index 11d8757749e..a5f39c3e1c4 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx @@ -8,7 +8,7 @@ legacyRedirects: - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_sles.html" - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_centos_or_rhel.html" navigation: - - install_on_linux_using_edb_repo + - install_on_linux - install_on_mac - install_on_windows - 13_upgrading_rpm_install