diff --git a/install_template/config.yaml b/install_template/config.yaml index aa999e092fe..eb311d5a391 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -3,40 +3,40 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [42.x.x] + supported versions: [42] - name: RHEL 8 arch: ppc64le - supported versions: [42.x.x] + supported versions: [42] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [42.x.x] + supported versions: [42] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [42.x.x] + supported versions: [42] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [42.x.x] + supported versions: [42] - name: Debian 10 arch: x86_64 - supported versions: [42.3.3.1] + supported versions: [42] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [42.3.3.1] + supported versions: [42] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [42.3.3.1] + supported versions: [42] - name: SLES 12 arch: x86_64 - supported versions: [42.3.3.1] + supported versions: [42] - name: SLES 12 arch: ppc64le - supported versions: [42.3.3.1] + supported versions: [42] - name: SLES 15 arch: x86_64 - supported versions: [42.3.3.1] + supported versions: [42] - name: SLES 15 arch: ppc64le - supported versions: [42.3.3.1] + supported versions: [42] - name: Migration Toolkit platforms: - name: RHEL 8 or OL 8 @@ -269,51 +269,48 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [10, 11, 12, 13, 14] + supported versions: [14] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [10, 11, 12, 13, 14] + supported versions: [14] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: RHEL 8 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: Debian 10 arch: x86_64 - supported versions: [13, 14] + supported versions: [14] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [13, 14] + supported versions: [14] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: SLES 12 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: SLES 15 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: SLES 12 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: SLES 15 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [14] - name: EDB*Plus platforms: - name: CentOS 7 arch: x86_64 supported versions: [40] - - name: CentOS 7 - arch: ppc64le - supported versions: [40] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [40] @@ -322,7 +319,10 @@ products: supported versions: [40] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [9.6, 11, 12, 13, 14] + supported versions: [40] + - name: RHEL 8 + arch: ppc64le + supported versions: [40] - name: Ubuntu 18.04 arch: x86_64 supported versions: [40] @@ -351,43 +351,43 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: RHEL 8 arch: ppc64le - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: Debian 10 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: SLES 12 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: SLES 12 arch: ppc64le - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: SLES 15 arch: x86_64 - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: SLES 15 arch: ppc64le - supported versions: [3.10, 4.0, 4.1, 4.2, 4.3, 4.4] + supported versions: [4] - name: Hadoop Foreign Data Wrapper platforms: - name: CentOS 7 @@ -472,9 +472,6 @@ products: - name: CentOS 7 arch: x86_64 supported versions: [2] - - name: CentOS 7 - arch: ppc64le - supported versions: [2] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [2] @@ -483,7 +480,10 @@ products: supported versions: [2] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] + - name: RHEL 8 + arch: ppc64le + supported versions: [2] - name: Ubuntu 18.04 arch: x86_64 supported versions: [2] @@ -550,16 +550,16 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [8] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: RHEL 8 arch: ppc64le supported versions: [8] @@ -568,7 +568,7 @@ products: supported versions: [8] - name: Debian 9 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: Ubuntu 20.04 arch: x86_64 supported versions: [8] @@ -580,7 +580,7 @@ products: supported versions: [8] - name: SLES 12 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: SLES 15 arch: x86_64 supported versions: [8] @@ -663,6 +663,9 @@ products: - name: SLES 15 arch: x86_64 supported versions: [7] + - name: RHEL 8 + arch: ppc64le + supported versions: [7] - name: SLES 12 arch: ppc64le supported versions: [7] diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 3e7ae1cc2ac..e964f09c32f 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -152,6 +152,16 @@ const moveDoc = async (product, platform, version) => { (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB*Plus", version: 40}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "CentOS 7"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "RHEL 8"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/edbplus_RHEL8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Postgres Advanced Server"}, platform: {name: "CentOS 7"}}, (ctx) => `epas/14/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_centos7_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Postgres Advanced Server"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, @@ -172,25 +182,25 @@ const moveDoc = async (product, platform, version) => { (ctx) => `epas/14/epas_inst_linux/installing_epas_using_edb_repository//${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Postgres Advanced Server"}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `epas/14/epas_inst_linux/installing_epas_using_edb_repository//${fmtArchPath(ctx)}/epas_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "CentOS 7"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "CentOS 7"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_centos7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_other_linux8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "RHEL 7 or OL 7"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 7 or OL 7"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "RHEL 8 or OL 8"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8 or OL 8"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel_8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "RHEL 8"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "SLES 12"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 12"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "SLES 15"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 15"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "Debian 10"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 10"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb10_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "Ubuntu 18.04"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 18.04"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu18_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "Ubuntu 20.04"}}, + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu20_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "SLES 12"}}, (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_sles12_${fmtArchFilename(ctx)}.mdx`), @@ -212,17 +222,28 @@ const moveDoc = async (product, platform, version) => { (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 8"}}, (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "CentOS 7"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles12_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles15_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles15_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_deb10_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 18.04"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 12"}}, + (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + + when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 12"}}, (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 15"}}, (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles15_${fmtArchFilename(ctx)}.mdx`), @@ -262,6 +283,18 @@ const moveDoc = async (product, platform, version) => { (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "RHEL 8"}}, (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_rhel8_${fmtArchFilename(ctx)}.mdx`), + + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "CentOS 7"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 8"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 12"}}, (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 15"}}, @@ -272,6 +305,7 @@ const moveDoc = async (product, platform, version) => { (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, @@ -282,6 +316,26 @@ const moveDoc = async (product, platform, version) => { (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "CentOS 7"}}, + (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8"}}, + (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, + (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB ODBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8"}}, + (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 12"}}, (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 15"}}, @@ -292,16 +346,39 @@ const moveDoc = async (product, platform, version) => { (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "SLES 12"}}, - (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "SLES 15"}}, - (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "Debian 10"}}, - (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_deb10_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_ubuntu18_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "RHEL 8"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "CentOS 7"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "SLES 12"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "SLES 15"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "Debian 10"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "Ubuntu 18.04"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "Ubuntu 20.04"}}, + (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "RHEL 8"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "CentOS 7"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "SLES 12"}}, (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "SLES 15"}}, @@ -312,7 +389,18 @@ const moveDoc = async (product, platform, version) => { (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/pgpool_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "SLES 12"}}, + + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "RHEL 8"}}, + (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "CentOS 7"}}, + (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "SLES 12"}}, (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "SLES 15"}}, (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_sles15_${fmtArchFilename(ctx)}.mdx`), @@ -322,7 +410,8 @@ const moveDoc = async (product, platform, version) => { (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 8 or OL 8"}}, + + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 8 or OL 8"}}, (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 8"}}, (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_rhel8_${fmtArchFilename(ctx)}.mdx`), @@ -382,11 +471,28 @@ const moveDoc = async (product, platform, version) => { (ctx) => `postgis/3.2/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/postgis_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "PostGIS", version: 3.2}, platform: {name: "Debian 10"}}, (ctx) => `postgis/3.2/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/postgis_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "SLES 12"}}, (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Replication Server", version: 7}, platform: {name: "SLES 15"}}, (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_sles15_${fmtArchFilename(ctx)}.mdx`), - ); + when({product: {name: "Replication Server", version: 7}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "CentOS 7"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "Ubuntu 20.04"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "Ubuntu 18.04"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "Debian 10"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "RHEL 8"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/eprs_rhel8_${fmtArchFilename(ctx)}.mdx`), ); + function match(context, ...conditions) { for (let test of conditions) { diff --git a/install_template/templates/platformBase/_epasinstalldiffserver.njk b/install_template/templates/platformBase/_epasinstalldiffserver.njk new file mode 100644 index 00000000000..80a147d0ebb --- /dev/null +++ b/install_template/templates/platformBase/_epasinstalldiffserver.njk @@ -0,0 +1 @@ +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). \ No newline at end of file diff --git a/install_template/templates/platformBase/_epasinstallsameserver.njk b/install_template/templates/platformBase/_epasinstallsameserver.njk new file mode 100644 index 00000000000..5bdb0a6540a --- /dev/null +++ b/install_template/templates/platformBase/_epasinstallsameserver.njk @@ -0,0 +1 @@ +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). \ No newline at end of file diff --git a/install_template/templates/platformBase/_javainstall.njk b/install_template/templates/platformBase/_javainstall.njk new file mode 100644 index 00000000000..c75a940c4b5 --- /dev/null +++ b/install_template/templates/platformBase/_javainstall.njk @@ -0,0 +1,5 @@ +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo {{ packageManager }} -y install java + ``` \ No newline at end of file diff --git a/install_template/templates/platformBase/_login.njk b/install_template/templates/platformBase/_login.njk new file mode 100644 index 00000000000..8f109c5a717 --- /dev/null +++ b/install_template/templates/platformBase/_login.njk @@ -0,0 +1,5 @@ +- Log in as a superuser: + + ```shell + sudo su - + ``` \ No newline at end of file diff --git a/install_template/templates/platformBase/_shared.njk b/install_template/templates/platformBase/_shared.njk index e6159c634e5..b56307f3a28 100644 --- a/install_template/templates/platformBase/_shared.njk +++ b/install_template/templates/platformBase/_shared.njk @@ -3,7 +3,7 @@ DELETE THIS FILE WHEN WE'RE SURE IT IS NOT USED (pretty certain it is not used) {% macro redhatFamilyRepositoryConfiguration(packageManager, epelRepo) %} ```shell # Set up the EDB repository: -{{ packageManager }} -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +sudo {{ packageManager }} -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm # This creates the /etc/yum.repos.d/edb.repo configuration file. @@ -12,7 +12,7 @@ DELETE THIS FILE WHEN WE'RE SURE IT IS NOT USED (pretty certain it is not used) sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo # Install the EPEL repository: -{{ packageManager }} -y install {{ epelRepo }} +sudo {{ packageManager }} -y install {{ epelRepo }} {% block rhel_8_or_ol8 %}{% endblock rhel_8_or_ol8 %}{% block almalinux_8_or_rockylinux_8 %}{% endblock almalinux_8_or_rockylinux_8 %}{% block rhel_7 %}{% endblock rhel_7 %} {% endmacro %} diff --git a/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk index 492c4e5baf0..b45ba0cff1d 100644 --- a/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk @@ -2,7 +2,6 @@ {% set packageManager = "dnf" %} {% set epelRepo = "epel-release" %} {% block redhatConfig %}# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools - -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql{% endblock redhatConfig %} +sudo dnf config-manager --set-enabled PowerTools{% block mysqlfdw %} + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql{% endblock mysqlfdw %}{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/platformBase/base.njk b/install_template/templates/platformBase/base.njk index af919eea0be..e8025b80fea 100644 --- a/install_template/templates/platformBase/base.njk +++ b/install_template/templates/platformBase/base.njk @@ -1,21 +1,31 @@ --- navTitle: {{ platform.name }} title: Installing {{ product.name }} on {{ platform.name }} {{ platform.arch }} +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -{% block pemprereq %} -Before you begin the installation process, log in as superuser. -```shell -# To log in as a superuser: -sudo su - -``` -{% endblock pemprereq %} -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +## Prerequisites + +Before you begin the installation process: + +{% block prodprereq %}{% endblock prodprereq %} + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. {% block prerequisites %}{% endblock prerequisites %} ## Install the package -{% block installCommand %}{% endblock installCommand %} +{% block installCommand %} +```shell +sudo {{packageManager}} -y install {{ packageName }} +``` +{% endblock installCommand %} {% block postinstall %}{% endblock postinstall %} diff --git a/install_template/templates/platformBase/centos-7.njk b/install_template/templates/platformBase/centos-7.njk index bd3580d8f3c..e29c8f901f9 100644 --- a/install_template/templates/platformBase/centos-7.njk +++ b/install_template/templates/platformBase/centos-7.njk @@ -1,3 +1,4 @@ {% extends "platformBase/redhat-family.njk" %} {% set packageManager = "yum" %} -{% set epelRepo = "https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" %} \ No newline at end of file +{% set epelRepo = "https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" %} +{% block redhatConfig %}{% block mysqlfdw %}{% endblock mysqlfdw %}{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/platformBase/debian.njk b/install_template/templates/platformBase/debian.njk index cc3ad801744..4a7d13636d6 100644 --- a/install_template/templates/platformBase/debian.njk +++ b/install_template/templates/platformBase/debian.njk @@ -1,29 +1,8 @@ {% extends "platformBase/base.njk" %} {% set packageManager = "apt-get" %} -{% block prerequisites %} -{% block repoAuth %} -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf -{% endblock repoAuth %} -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - -{% block mysqlfdw %} -# Update the repository metadata: -apt-get update -``` -{% endblock mysqlfdw %}{% endblock prerequisites %} - +{% block prerequisites %}{% block mysqlfdw %}{% endblock mysqlfdw %}{% endblock prerequisites %} {% block installCommand %}{% block odbcconnector %} ```shell -apt-get install {{ packageName }} +sudo apt-get -y install {{ packageName }} ``` {% endblock odbcconnector %}{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/platformBase/redhat-family.njk b/install_template/templates/platformBase/redhat-family.njk index b990b7fb2b9..419cf9e1db9 100644 --- a/install_template/templates/platformBase/redhat-family.njk +++ b/install_template/templates/platformBase/redhat-family.njk @@ -1,24 +1,10 @@ {% extends "platformBase/base.njk" %} -{% block prerequisites %} -```shell -# Set up the EDB repository: -{{ packageManager }} -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -{% block pemsetuprepo %} -# Install the EPEL repository: -{{ packageManager }} -y install {{ epelRepo }} -{% if includePPC %} -# Refresh the cache: -dnf makecache -{% endif %} -{% block redhatConfig %}{% endblock redhatConfig %}{% endblock pemsetuprepo %} -``` -{% endblock prerequisites %} -{% block installCommand %} -```shell -{{packageManager}} -y install {{ packageName }} -``` -{% endblock installCommand %} \ No newline at end of file +{% block prerequisites %}{% block pemsetuprepo %} +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo {{ packageManager }} -y install {{ epelRepo }} + {% if includePPC %} + # Refresh the cache: + sudo dnf makecache{% endif %}{% block redhatConfig %}{% endblock redhatConfig %} + ```{% endblock pemsetuprepo %}{% endblock prerequisites %} diff --git a/install_template/templates/platformBase/rhel-7-or-ol-7.njk b/install_template/templates/platformBase/rhel-7-or-ol-7.njk index fa3b844dd38..5fc6071614d 100644 --- a/install_template/templates/platformBase/rhel-7-or-ol-7.njk +++ b/install_template/templates/platformBase/rhel-7-or-ol-7.njk @@ -2,4 +2,4 @@ {% set packageManager = "yum" %} {% set epelRepo = "https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" %} {% block redhatConfig %}# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms"{% endblock redhatConfig %} \ No newline at end of file +subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms"{% block mysqlfdw %}{% endblock mysqlfdw %}{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/platformBase/rhel-8-or-ol-8.njk b/install_template/templates/platformBase/rhel-8-or-ol-8.njk index 21ac9f1c861..365904bb8fb 100644 --- a/install_template/templates/platformBase/rhel-8-or-ol-8.njk +++ b/install_template/templates/platformBase/rhel-8-or-ol-8.njk @@ -1,8 +1,9 @@ {% extends "platformBase/redhat-family.njk" %} {% set packageManager = "dnf" %} {% set epelRepo = "https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm" %} -{% block redhatConfig %}# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql{% endblock redhatConfig %} \ No newline at end of file +{% block redhatConfig %} + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" +{% block mysqlfdw %} + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql{% endblock mysqlfdw %}{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/platformBase/sles-12.njk b/install_template/templates/platformBase/sles-12.njk index 0957e9a34c2..cd690cef0bf 100644 --- a/install_template/templates/platformBase/sles-12.njk +++ b/install_template/templates/platformBase/sles-12.njk @@ -1,30 +1,18 @@ {% extends "platformBase/base.njk" %} {% set packageManager = "zypper" %} {% block prerequisites %} -```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' -{% block mysqlfdw %}{% endblock mysqlfdw %} -# Activate the required SUSE module -{% block activateSUSEmodule %}SUSEConnect -p PackageHub/12.5/{{ platform.arch }} -SUSEConnect -p sle-sdk/12.5/{{ platform.arch }} -{% endblock activateSUSEmodule %} -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + ```shell{% block mysqlfdw %}{% endblock mysqlfdw %} + # Activate the required SUSE module + {% block activateSUSEmodule %}sudo SUSEConnect -p PackageHub/12.5/{{ platform.arch }} + sudo SUSEConnect -p sle-sdk/12.5/{{ platform.arch }} + {% endblock activateSUSEmodule %} + # Refresh the metadata + sudo zypper refresh + ``` {% endblock prerequisites %} {% block installCommand %} ```shell -zypper -n install {{ packageName }} +sudo zypper -n install {{ packageName }} ``` {% endblock installCommand %} diff --git a/install_template/templates/platformBase/sles-15.njk b/install_template/templates/platformBase/sles-15.njk index 19548e277d4..9f3534517e2 100644 --- a/install_template/templates/platformBase/sles-15.njk +++ b/install_template/templates/platformBase/sles-15.njk @@ -1,3 +1,3 @@ {% extends "platformBase/sles-12.njk" %} -{% block activateSUSEmodule %}SUSEConnect -p PackageHub/15.3/{{ platform.arch }} +{% block activateSUSEmodule %}sudo SUSEConnect -p PackageHub/15.3/{{ platform.arch }} {% endblock activateSUSEmodule %} diff --git a/install_template/templates/platformBase/ubuntu.njk b/install_template/templates/platformBase/ubuntu.njk index 34b058b83d2..a45f9f6ae5d 100644 --- a/install_template/templates/platformBase/ubuntu.njk +++ b/install_template/templates/platformBase/ubuntu.njk @@ -1,28 +1,8 @@ {% extends "platformBase/base.njk" %} {% set packageManager = "apt-get" %} -{% block prerequisites %} -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf - -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - -{% block mysqlfdw %} -# Update the repository metadata: -apt-get update -``` -{% endblock mysqlfdw %}{% endblock prerequisites %} - +{% block prerequisites %}{% block mysqlfdw %}{% endblock mysqlfdw %}{% endblock prerequisites %} {% block installCommand %}{% block odbcconnector %} ```shell -apt-get install {{ packageName }} +sudo apt-get -y install {{ packageName }} ``` {% endblock odbcconnector %}{% endblock installCommand %} diff --git a/install_template/templates/products/edb*plus/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb*plus/almalinux-8-or-rocky-linux-8.njk index b19364aa0f2..a7fa1a42812 100644 --- a/install_template/templates/products/edb*plus/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb*plus/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb*plus/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb*plus/base.njk b/install_template/templates/products/edb*plus/base.njk index d8664a8e950..a10ecc24976 100644 --- a/install_template/templates/products/edb*plus/base.njk +++ b/install_template/templates/products/edb*plus/base.njk @@ -1,5 +1,9 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as-edbplus{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% include "platformBase/_javainstall.njk" %} +{% endblock prodprereq %} {% block installCommand %} {{super()}} Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/install_template/templates/products/edb*plus/centos-7_ppc64le.njk b/install_template/templates/products/edb*plus/centos-7_ppc64le.njk deleted file mode 100644 index 1f84a3cf3b4..00000000000 --- a/install_template/templates/products/edb*plus/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb*plus/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb*plus/rhel-8_ppc64le.njk b/install_template/templates/products/edb*plus/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..e471e9b058f --- /dev/null +++ b/install_template/templates/products/edb*plus/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb*plus/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-jdbc-connector/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-jdbc-connector/almalinux-8-or-rocky-linux-8.njk index 6f483a059c9..adb6433a714 100644 --- a/install_template/templates/products/edb-jdbc-connector/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-jdbc-connector/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-jdbc-connector/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-jdbc-connector/base.njk b/install_template/templates/products/edb-jdbc-connector/base.njk index 5985d7803aa..024fdce47cc 100644 --- a/install_template/templates/products/edb-jdbc-connector/base.njk +++ b/install_template/templates/products/edb-jdbc-connector/base.njk @@ -1,3 +1,7 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-jdbc{% endset %} -{% block postinstallMenu %}- [Initial configuration](#initial-configuration){% endblock postinstallMenu %} \ No newline at end of file +{% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). + +{% endblock prodprereq %} +{% block postinstallMenu %}- [Initial configuration](#initial-configuration){% endblock postinstallMenu %} diff --git a/install_template/templates/products/edb-ocl-connector/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-ocl-connector/almalinux-8-or-rocky-linux-8.njk index 795fa4d65f8..826f057f4b0 100644 --- a/install_template/templates/products/edb-ocl-connector/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-ocl-connector/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-ocl-connector/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/base.njk b/install_template/templates/products/edb-ocl-connector/base.njk index fbaac082c2d..0c76b0c906a 100644 --- a/install_template/templates/products/edb-ocl-connector/base.njk +++ b/install_template/templates/products/edb-ocl-connector/base.njk @@ -1,2 +1,5 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-oci{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} + +{% endblock prodprereq %} diff --git a/install_template/templates/products/edb-ocl-connector/debian.njk b/install_template/templates/products/edb-ocl-connector/debian.njk index 9bd573413b7..c2e16a57374 100644 --- a/install_template/templates/products/edb-ocl-connector/debian.njk +++ b/install_template/templates/products/edb-ocl-connector/debian.njk @@ -1,7 +1,7 @@ {% extends "products/edb-ocl-connector/base.njk" %} {% block odbcconnector %} ```shell -apt-get install {{ packageName }} -apt-get install {{ packageName }}-dev +sudo apt-get install {{ packageName }} +sudo apt-get install {{ packageName }}-dev ``` {% endblock odbcconnector %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/ubuntu.njk b/install_template/templates/products/edb-ocl-connector/ubuntu.njk index 9bd573413b7..c2e16a57374 100644 --- a/install_template/templates/products/edb-ocl-connector/ubuntu.njk +++ b/install_template/templates/products/edb-ocl-connector/ubuntu.njk @@ -1,7 +1,7 @@ {% extends "products/edb-ocl-connector/base.njk" %} {% block odbcconnector %} ```shell -apt-get install {{ packageName }} -apt-get install {{ packageName }}-dev +sudo apt-get install {{ packageName }} +sudo apt-get install {{ packageName }}-dev ``` {% endblock odbcconnector %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-odbc-connector/almalinux-8-or-rocky-linux-8.njk index 434df4a6b4a..47dec5da57d 100644 --- a/install_template/templates/products/edb-odbc-connector/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-odbc-connector/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-odbc-connector/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/base.njk b/install_template/templates/products/edb-odbc-connector/base.njk index 533f6a9fa65..cefe59ea112 100644 --- a/install_template/templates/products/edb-odbc-connector/base.njk +++ b/install_template/templates/products/edb-odbc-connector/base.njk @@ -1,2 +1,5 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-odbc{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} + +{% endblock prodprereq %} diff --git a/install_template/templates/products/edb-odbc-connector/debian.njk b/install_template/templates/products/edb-odbc-connector/debian.njk index 118cddceb0d..a1fe7f20325 100644 --- a/install_template/templates/products/edb-odbc-connector/debian.njk +++ b/install_template/templates/products/edb-odbc-connector/debian.njk @@ -1,7 +1,7 @@ {% extends "products/edb-odbc-connector/base.njk" %} {% block odbcconnector %} ```shell -apt-get install {{ packageName }} -apt-get install {{ packageName }}-dev +sudo apt-get install {{ packageName }} +sudo apt-get install {{ packageName }}-dev ``` {% endblock odbcconnector %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/ubuntu.njk b/install_template/templates/products/edb-odbc-connector/ubuntu.njk index 118cddceb0d..a1fe7f20325 100644 --- a/install_template/templates/products/edb-odbc-connector/ubuntu.njk +++ b/install_template/templates/products/edb-odbc-connector/ubuntu.njk @@ -1,7 +1,7 @@ {% extends "products/edb-odbc-connector/base.njk" %} {% block odbcconnector %} ```shell -apt-get install {{ packageName }} -apt-get install {{ packageName }}-dev +sudo apt-get install {{ packageName }} +sudo apt-get install {{ packageName }}-dev ``` {% endblock odbcconnector %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgbouncer/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-pgbouncer/almalinux-8-or-rocky-linux-8.njk index 189f1f855d9..d6a049ca659 100644 --- a/install_template/templates/products/edb-pgbouncer/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-pgbouncer/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-pgbouncer/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgbouncer/base.njk b/install_template/templates/products/edb-pgbouncer/base.njk index 5b27ed60b2b..25990e8ac77 100644 --- a/install_template/templates/products/edb-pgbouncer/base.njk +++ b/install_template/templates/products/edb-pgbouncer/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pgbouncer{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{super()}} Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk index f7499477eab..f4f867de738 100644 --- a/install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-pgpool-ii/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/base.njk b/install_template/templates/products/edb-pgpool-ii-extensions/base.njk index 4a9cc79f127..43c8a74a013 100644 --- a/install_template/templates/products/edb-pgpool-ii-extensions/base.njk +++ b/install_template/templates/products/edb-pgpool-ii-extensions/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as--pgpool-extensions{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{super()}} Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk index f7499477eab..f4f867de738 100644 --- a/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/edb-pgpool-ii/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/base.njk b/install_template/templates/products/edb-pgpool-ii/base.njk index 3e5f03cd9d9..570186f0612 100644 --- a/install_template/templates/products/edb-pgpool-ii/base.njk +++ b/install_template/templates/products/edb-pgpool-ii/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pgpool{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{super()}} Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/install_template/templates/products/edb-postgres-advanced-server/base.njk b/install_template/templates/products/edb-postgres-advanced-server/base.njk index b48aed5ffa1..3cc25f7796b 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/base.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/base.njk @@ -1,16 +1,16 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as-server{% endset %} {% block installCommand %} -{{super()}} -Where `` is the version of the EDB Postgres Advanced server you are installing. +{{super()}}{% block slesoption %} +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -{{packageManager}} install +sudo {{packageManager}} -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). -{% endblock installCommand %} +{% endblock slesoption %}{% endblock installCommand %} {% block postinstall %} ## Initial configuration diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk index 722bbc51ef9..a5d1d6de8be 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk @@ -1,3 +1,13 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} -{% set packageManager = "zypper" %} \ No newline at end of file +{% set packageManager = "zypper" %} +{% block slesoption %} +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. + +To install an individual component: + +```shell +sudo {{packageManager}} -n install +``` +Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). +{% endblock slesoption %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk index afe322e1ac3..3c057f0bf16 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk @@ -1,3 +1,13 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} -{% set packageManager = "zypper" %} \ No newline at end of file +{% set packageManager = "zypper" %} +{% block slesoption %} +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. + +To install an individual component: + +```shell +sudo {{packageManager}} -n install +``` +Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). +{% endblock slesoption %} \ No newline at end of file diff --git a/install_template/templates/products/failover-manager/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/failover-manager/almalinux-8-or-rocky-linux-8.njk index 0adc2696a01..1fb73337463 100644 --- a/install_template/templates/products/failover-manager/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/failover-manager/almalinux-8-or-rocky-linux-8.njk @@ -1,2 +1,2 @@ {% extends "products/failover-manager/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/failover-manager/base.njk b/install_template/templates/products/failover-manager/base.njk index 54868df8d19..b7f056e6ebf 100644 --- a/install_template/templates/products/failover-manager/base.njk +++ b/install_template/templates/products/failover-manager/base.njk @@ -1,5 +1,7 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-efm<4x>{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} +{% endblock prodprereq %} {% block postinstall %} Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/install_template/templates/products/failover-manager/rhel-8_ppc64le.njk b/install_template/templates/products/failover-manager/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..88ed2496065 --- /dev/null +++ b/install_template/templates/products/failover-manager/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/failover-manager/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk index d6ebd0442f2..b9dfc888a0f 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as14-hdfs_fdw{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{ super() }} {% include "platformBase/_epasVersionInPackageName.njk" %} diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk index 813444b77e2..0fa5eea26d0 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk @@ -1,7 +1,7 @@ {% extends "products/hadoop-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} {% block redhatConfig %}# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + sudo dnf config-manager --set-enabled PowerTools -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql{% endblock redhatConfig %} \ No newline at end of file + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/products/migration-toolkit/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/migration-toolkit/almalinux-8-or-rocky-linux-8.njk index a93e5b4ef7f..46360e31e6e 100644 --- a/install_template/templates/products/migration-toolkit/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/migration-toolkit/almalinux-8-or-rocky-linux-8.njk @@ -2,18 +2,12 @@ {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} {% set packageManager = "dnf" %} {% block prerequisites %} -```shell -# Set up the EDB repository: -{{ packageManager }} -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo {{ packageManager }} -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Install the EPEL repository: -{{ packageManager }} -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - -{% block redhatConfig %}# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms"{% endblock redhatConfig %} -``` + {% block redhatConfig %}# Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms"{% endblock redhatConfig %} + ``` {% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/migration-toolkit/base.njk b/install_template/templates/products/migration-toolkit/base.njk index 4f566495040..f215ea5b0c4 100644 --- a/install_template/templates/products/migration-toolkit/base.njk +++ b/install_template/templates/products/migration-toolkit/base.njk @@ -1,5 +1,7 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-migrationtoolkit{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} +{% endblock prodprereq %} {% block postinstall %} ## Initial configuration 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. diff --git a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk b/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk index a8e8e3fac47..d99f462146f 100644 --- a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk @@ -1,3 +1,9 @@ {% extends "products/migration-toolkit/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} -{% block redhatConfig %}{% endblock redhatConfig %} \ No newline at end of file +{% block prerequisites %} +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo {{ packageManager }} -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ``` +{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk b/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk index eae29beb0aa..2be7c031afe 100644 --- a/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk +++ b/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk @@ -1,2 +1,8 @@ {% extends "products/migration-toolkit/rhel-8-or-ol-8.njk" %} -{% set includePPC = true %} \ No newline at end of file +{% set includePPC = true %} +{% block redhatConfig %} + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk index ad63a2a3a25..e1bfc9f1526 100644 --- a/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as14-mongo_fdw{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{ super() }} {% include "platformBase/_epasVersionInPackageName.njk" %} diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/mysql-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk index 6a52895a4e5..c2623a34f7b 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,3 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% block mysqlfdw %}{% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/base.njk b/install_template/templates/products/mysql-foreign-data-wrapper/base.njk index c8e586a4c34..643d29f160c 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/base.njk @@ -1,5 +1,8 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as-mysql-fdw{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} {{ super() }} Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk index 3b83c16d289..48beccc1847 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk @@ -1,2 +1,11 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file +{% set platformBaseTemplate = "centos-7" %} +{% block mysqlfdw %}# Download and install the MYSQL repo: + sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm + + # Enable the MYSQL repo: + # For MySQL 8: + sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw + + # For MySQL 5: + sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw{% endblock mysqlfdw %} diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7_ppc64le.njk b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7_ppc64le.njk deleted file mode 100644 index 13e9a41605d..00000000000 --- a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/mysql-foreign-data-wrapper/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk index 6823dc39dd5..75141fd2e3b 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk @@ -1,19 +1,16 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "debian-10" %} {% block mysqlfdw %} -# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command: -apt-get remove libmysqlclient-dev +- Address other prerequisites + ```shell + # If there is `libmysqlclient-dev` already installed on your system, + # remove it by using the following command: + sudo apt-get remove libmysqlclient-dev -# Enable the MySQL repo: -# For MySQL 8: -sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list -# For MySQL 5: -sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - -# Add the mysql repo key using the following commands: -sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5 - -# Update the repository metadata: -apt-get update -``` + #Enable the MySQL repo: + For MySQL 8: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list + For MySQL 5: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list + ``` {% endblock mysqlfdw %} diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk index 3e29f41d483..e9b8f0b5f6c 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk @@ -1,2 +1,12 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file +{% set platformBaseTemplate = "rhel-7-or-ol-7" %} +{% block mysqlfdw %} + # Download and install the MYSQL repo: + sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm + + # Enable the MYSQL repo: + # For MySQL 8: + sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw + + # For MySQL 5: + sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw{% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8-or-ol-8.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8-or-ol-8.njk index cd91fd8d8d3..73f23013808 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8-or-ol-8.njk @@ -1,2 +1,3 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file +{% set platformBaseTemplate = "rhel-8-or-ol-8" %} +{% block mysqlfdw %}{% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8_ppc64le.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..fba28435346 --- /dev/null +++ b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-8_ppc64le.njk @@ -0,0 +1,3 @@ +{% extends "products/mysql-foreign-data-wrapper/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} +{% block mysqlfdw %}{% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk b/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk index fc888add3ae..c5d7f3b97b1 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk @@ -1,11 +1,11 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "sles-12" %} {% block mysqlfdw %} -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community {% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk b/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk index d4154489ade..9b338048823 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk @@ -1,11 +1,11 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "sles-15" %} {% block mysqlfdw %} -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community {% endblock mysqlfdw %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk b/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk index 9d610f71751..3bf7b34bd1c 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk @@ -1,19 +1,16 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "ubuntu-18.04" %} {% block mysqlfdw %} -# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command: -apt-get remove libmysqlclient-dev +- Address other prerequisites + ```shell + # If there is `libmysqlclient-dev` already installed on your system, + # remove it by using the following command: + sudo apt-get remove libmysqlclient-dev -# Enable the MySQL repo: -# For MySQL 8: -echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list -# For MySQL 5: -echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - -# Add the mysql repo key using the following commands: -apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5 - -# Update the repository metadata: -apt-get update -``` + # Enable the MySQL repo: + # For MySQL 8: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list + # For MySQL 5: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list + ``` {% endblock mysqlfdw %} diff --git a/install_template/templates/products/postgis/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgis/almalinux-8-or-rocky-linux-8.njk index bd643913112..2a317fecfa4 100644 --- a/install_template/templates/products/postgis/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgis/almalinux-8-or-rocky-linux-8.njk @@ -4,13 +4,13 @@ ```shell # To install PostGIS 3.2: -dnf install edb-as-postgis32 +sudo dnf -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -dnf install edb-as-postgis3 +sudo dnf -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11: -dnf install edb-as11-postgis +sudo dnf -y install edb-as11-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgis/base.njk b/install_template/templates/products/postgis/base.njk index 4b3a8a48f3d..faa9147e940 100644 --- a/install_template/templates/products/postgis/base.njk +++ b/install_template/templates/products/postgis/base.njk @@ -1,12 +1,15 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as14-postgis32{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %} + +{% endblock prodprereq %} {% block installCommand %} ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +sudo zypper -n install edb-as-postgis32 # To install PostGIS 3.1: -zypper install edb-as-postgis3 +sudo zypper -n install edb-as-postgis3 ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgis/centos-7.njk b/install_template/templates/products/postgis/centos-7.njk index 8e6f7dfb2eb..b52225dd92c 100644 --- a/install_template/templates/products/postgis/centos-7.njk +++ b/install_template/templates/products/postgis/centos-7.njk @@ -3,13 +3,13 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -yum install edb-as-postgis32 +sudo yum -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -yum install edb-as-postgis3 +sudo yum -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 10-12: -yum install edb-as-postgis +sudo yum -y install edb-as-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/debian-10.njk b/install_template/templates/products/postgis/debian-10.njk index a38687d8f7e..1abc957f038 100644 --- a/install_template/templates/products/postgis/debian-10.njk +++ b/install_template/templates/products/postgis/debian-10.njk @@ -3,16 +3,16 @@ {% block installCommand %} ```shell # To install PostGIS 3.2 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis32 +sudo apt-get -y install edb-as-postgis32 -# To install PostGIS 3.2 using EDB Postgres Advanced Server 12: -apt-get install edb-as-postgis-3.2 +# To install PostGIS 3.2 using EDB Postgres Advanced Server 11-12: +sudo sudo apt-get -y install edb-as-postgis-3.2 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 12: -apt-get install edb-as12-postgis-3.1 +sudo apt-get -y install edb-as12-postgis-3.1 ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/rhel-7-or-ol-7.njk b/install_template/templates/products/postgis/rhel-7-or-ol-7.njk index 94883c65351..54b0e552e0c 100644 --- a/install_template/templates/products/postgis/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgis/rhel-7-or-ol-7.njk @@ -3,13 +3,13 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -yum install edb-as-postgis32 +sudo yum -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -yum install edb-as-postgis3 +sudo yum -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 10-11: -yum install edb-as-postgis +sudo yum -y install edb-as-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/rhel-8-or-ol-8.njk b/install_template/templates/products/postgis/rhel-8-or-ol-8.njk index dc4489fbd4f..225e579e5f4 100644 --- a/install_template/templates/products/postgis/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/postgis/rhel-8-or-ol-8.njk @@ -3,13 +3,13 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -dnf install edb-as-postgis32 +sudo dnf -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -dnf install edb-as-postgis3 +sudo dnf -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -dnf install edb-as-postgis +sudo dnf -y install edb-as-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/sles-12.njk b/install_template/templates/products/postgis/sles-12.njk index ce2c034f376..84d98667818 100644 --- a/install_template/templates/products/postgis/sles-12.njk +++ b/install_template/templates/products/postgis/sles-12.njk @@ -3,13 +3,13 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +sudo zypper -n install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -zypper install edb-as-postgis3 +sudo zypper -n install edb-as-postgis3 -# To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -zypper install edb-as12-postgis +# To install PostGIS 3.1 using EDB Postgres Advanced Server 12: +sudo zypper -n install edb-as12-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/sles-12_ppc64le.njk b/install_template/templates/products/postgis/sles-12_ppc64le.njk index 7eef4b8d80f..f239b0d1799 100644 --- a/install_template/templates/products/postgis/sles-12_ppc64le.njk +++ b/install_template/templates/products/postgis/sles-12_ppc64le.njk @@ -3,13 +3,13 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +zypper -n install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -zypper install edb-as-postgis3 +zypper -n install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 12: -zypper install edb-as12-postgis +zypper -n install edb-as12-postgis ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgis/ubuntu-18.04.njk b/install_template/templates/products/postgis/ubuntu-18.04.njk index f5caaf48d1d..fa9604cd2e4 100644 --- a/install_template/templates/products/postgis/ubuntu-18.04.njk +++ b/install_template/templates/products/postgis/ubuntu-18.04.njk @@ -3,16 +3,16 @@ {% block installCommand %} ```shell # To install PostGIS 3.2 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis32 +sudo apt-get -y install edb-as-postgis32 # To install PostGIS 3.2 using EDB Postgres Advanced Server 11-12: -apt-get install edb-as-postgis-3.2 +sudo apt-get -y install edb-as-postgis-3.2 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -apt-get install edb-as-postgis-3.1 +sudo apt-get -y install edb-as-postgis-3.1 ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgis/ubuntu-20.04.njk b/install_template/templates/products/postgis/ubuntu-20.04.njk index b558c733a0d..fbac58035b2 100644 --- a/install_template/templates/products/postgis/ubuntu-20.04.njk +++ b/install_template/templates/products/postgis/ubuntu-20.04.njk @@ -3,10 +3,10 @@ {% block installCommand %} ```shell # To install PostGIS 3.2: -apt-get install edb-as14-postgis32 +sudo apt-get -y install edb-as14-postgis32 # To install PostGIS 3.1: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 ``` {% include "platformBase/_epasVersionInPostGISPackageName.njk" %} {% endblock installCommand %} diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/base.njk b/install_template/templates/products/postgres-enterprise-manager-agent/base.njk index 18b387b4f00..ba278d9e918 100644 --- a/install_template/templates/products/postgres-enterprise-manager-agent/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-agent/base.njk @@ -1,5 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pem-agent{% endset %} +{% block prodprereq %}{% endblock prodprereq %} {% block pemsetuprepo %}{% endblock pemsetuprepo %} {% block installCommand %} {{super()}} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 2c5129d21c9..33886be6389 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -1,25 +1,20 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pem{% endset %} -{% block pemprereq %} -Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +{% block prodprereq %} +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -2. Log in as superuser: -```shell -sudo su - -``` -{% endblock pemprereq %} -{% block pemsetuprepo %}{% endblock pemsetuprepo %} +{% endblock prodprereq %}{% block pemsetuprepo %}{% endblock pemsetuprepo %} {% block postinstall %} ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note -- The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. {% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk index a4fd66e61c1..39612bb80b2 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk @@ -1,8 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "centos-7" %} {% block postinstall %} -{{ super() }}!!! Note: -- If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. +{{ super() }} + - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. -- If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. + - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. {% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk index ee661bbae09..7f546942da7 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk @@ -2,7 +2,7 @@ {% set platformBaseTemplate = "rhel-7-or-ol-7" %} {% block postinstall %} {{ super() }} -- If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. + - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. -- If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. + - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. {% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/replication-manager/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/replication-manager/almalinux-8-or-rocky-linux-8.njk index 38bf92e85b2..80d1d674463 100644 --- a/install_template/templates/products/replication-manager/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/replication-manager/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/replication-manager/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk index f1a29c47508..f2697da24bf 100644 --- a/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/replication-server/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/base.njk b/install_template/templates/products/replication-server/base.njk index 91cd996c178..4c560556dad 100644 --- a/install_template/templates/products/replication-server/base.njk +++ b/install_template/templates/products/replication-server/base.njk @@ -1,16 +1,20 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-xdb{% endset %} +{% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} + +{% include "platformBase/_javainstall.njk" %} +{% endblock prodprereq %} {% block installCommand %} You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. To install all Replication Server components: ```shell -zypper -n install {{ packageName }} +sudo {{ packageManager }} -y install {{ packageName }} ``` To install an individual component: ```shell -zypper install +sudo {{ packageManager }} -y install ``` Where `` is: diff --git a/install_template/templates/products/replication-server/rhel-8_ppc64le.njk b/install_template/templates/products/replication-server/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..6cb7a4ff759 --- /dev/null +++ b/install_template/templates/products/replication-server/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-12.njk b/install_template/templates/products/replication-server/sles-12.njk index 18823a2b02e..d2f2f58fefc 100644 --- a/install_template/templates/products/replication-server/sles-12.njk +++ b/install_template/templates/products/replication-server/sles-12.njk @@ -1,2 +1,24 @@ {% extends "products/replication-server/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file +{% set platformBaseTemplate = "sles-12" %} +{% block installCommand %} +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: +```shell +sudo {{ packageManager }} -n install {{ packageName }} +``` + +To install an individual component: +```shell +sudo {{ packageManager }} -n install +``` + +Where `` is: + +| Package name | Component | +| --------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | + +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-15.njk b/install_template/templates/products/replication-server/sles-15.njk index 62c5745d295..16746f197f6 100644 --- a/install_template/templates/products/replication-server/sles-15.njk +++ b/install_template/templates/products/replication-server/sles-15.njk @@ -1,2 +1,24 @@ {% extends "products/replication-server/base.njk" %} -{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file +{% set platformBaseTemplate = "sles-15" %} +{% block installCommand %} +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: +```shell +sudo {{ packageManager }} -n install {{ packageName }} +``` + +To install an individual component: +```shell +sudo {{ packageManager }} -n install +``` + +Where `` is: + +| Package name | Component | +| --------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | + +{% endblock installCommand %} \ No newline at end of file diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_rhel8_ppcle.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_rhel8_ppcle.mdx new file mode 100644 index 00000000000..8c945402487 --- /dev/null +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_rhel8_ppcle.mdx @@ -0,0 +1,57 @@ +--- +navTitle: RHEL 8 +title: Installing EDB*Plus on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo dnf -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as-edbplus +``` + +Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles12_ppcle.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles12_ppcle.mdx index 8061edac183..5febe3afd25 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles12_ppcle.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles12_ppcle.mdx @@ -1,45 +1,44 @@ --- navTitle: SLES 12 title: Installing EDB*Plus on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-edbplus +sudo zypper -n install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles15_ppcle.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles15_ppcle.mdx index 9ff9a64e835..bb9a170fe46 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles15_ppcle.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles15_ppcle.mdx @@ -1,44 +1,43 @@ --- navTitle: SLES 15 title: Installing EDB*Plus on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-edbplus +sudo zypper -n install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/index.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/index.mdx index 831e129023b..c18ce10ed12 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/index.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/index.mdx @@ -2,12 +2,15 @@ title: "Installing EDB*Plus on IBM Power (ppc64le)" navTitle: "IBM Power (ppc64le)" navigation: + - edbplus_rhel8_ppcle - edbplus_sles15_ppcle - edbplus_sles12_ppcle --- For operating system-specific install instructions, see: + - [RHEL 8](edbplus_rhel8_ppcle) + - [SLES 15](edbplus_sles15_ppcle) - [SLES 12](edbplus_sles12_ppcle) diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/index.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/index.mdx index 25545da6dcb..48b8242225b 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/index.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/index.mdx @@ -38,6 +38,9 @@ For platform-specific install instructions, see: - [Debian 10](x86_amd64/edbplus_deb10_x86) - Linux on IBM Power (ppc64le): + + - [RHEL 8](ibm_power_ppc64le/edbplus_rhel8_ppcle) + - [SLES 15](ibm_power_ppc64le/edbplus_sles15_ppcle) - [SLES 12](ibm_power_ppc64le/edbplus_sles12_ppcle) diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_centos7_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_centos7_x86.mdx index f01e2e35bac..ed574d5468f 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_centos7_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_centos7_x86.mdx @@ -1,34 +1,50 @@ --- -title: "Installing EDB*Plus on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing EDB*Plus on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -You can use an RPM package to install EDB\*Plus on a CentOS host. - -1. To install the repository configuration file, assume superuser privileges, and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -1. Before installing EDB\*Plus, install the `epel-release` package: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -1. After saving your changes to the configuration file, install EDB\*Plus: - ```text - yum -y install edb-asxx-edbplus - ``` - - Where, `xx` is the Advanced Server version. - -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 `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. +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo yum -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + + ``` + +## Install the package + +```shell +sudo yum -y install edb-as-edbplus +``` + +Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_deb10_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_deb10_x86.mdx index 2b4c9473051..b2293248a9f 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_deb10_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_deb10_x86.mdx @@ -1,42 +1,33 @@ --- navTitle: Debian 10 title: Installing EDB*Plus on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Set up the EDB repository -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 + ```shell + sudo apt-get -y install java + ``` -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-edbplus +sudo apt-get -y install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_other_linux8_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_other_linux8_x86.mdx index dd55a76a078..c06def47725 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_other_linux8_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_other_linux8_x86.mdx @@ -1,35 +1,52 @@ --- -title: "Installing EDB*Plus on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB*Plus on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -You can use an RPM package to install EDB\*Plus on a Rocky Linux/AlmaLinux host. - -1. To install the repository configuration file, assume superuser privileges, and invoke the following command: - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -1. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -1. Before installing EDB\*Plus, install the `epel-release` package: - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` - -1. Enable the PowerTools repository to satisfy package dependencies: - ```text - dnf config-manager --set-enabled PowerTools - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -1. After saving your changes to the configuration file, install EDB\*Plus: - ```text - dnf -y install edb-asxx-edbplus - ``` - - Where, `xx` is the Advanced Server version. \ No newline at end of file +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo dnf -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as-edbplus +``` + +Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel7_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel7_x86.mdx index 69d237b4a84..5f8c7b0d2ba 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel7_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel7_x86.mdx @@ -1,39 +1,50 @@ --- -title: "Installing EDB*Plus on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing EDB*Plus on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -You can use an RPM package to install EDB\*Plus on a RHEL host. - -1. To install the repository configuration file, assume superuser privileges and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` -1. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` -1. Before installing EDB\*Plus, install the `epel-release` package: - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` - -1. Enable the `codeready-builder-for-rhel-8-*-rpms` repository to satisfy package dependencies: - ```text - ARCH=$( /bin/arch ) - - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -1. After saving your changes to the configuration file, install EDB\*Plus: - ```text - yum -y install edb-asxx-edbplus - ``` - - Where, `xx` is the Advanced Server version. - -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 `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. +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo yum -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` + +## Install the package + +```shell +sudo yum -y install edb-as-edbplus +``` + +Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel8_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel8_x86.mdx index 565a49edac8..ff9edc45c7e 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel8_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel8_x86.mdx @@ -1,37 +1,55 @@ --- -title: "Installing EDB*Plus on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB*Plus on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -You can use an RPM package to install EDB\*Plus on a RHEL host. - -1. To install the repository configuration file, assume superuser privileges, and invoke the following command: - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -1. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -1. Before installing EDB\*Plus, install the `epel-release` package: - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` - -1. Enable the `codeready-builder-for-rhel-8-*-rpms` repository to satisfy package dependencies: - ```text - ARCH=$( /bin/arch ) - - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` - - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -1. After saving your changes to the configuration file, install EDB\*Plus: - ```text - dnf -y install edb-asxx-edbplus - ``` - - Where, `xx` is the Advanced Server version. +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo dnf -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as-edbplus +``` + +Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles12_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles12_x86.mdx index 838cd32bb64..04ab800ca7d 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles12_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles12_x86.mdx @@ -1,45 +1,44 @@ --- navTitle: SLES 12 title: Installing EDB*Plus on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-edbplus +sudo zypper -n install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles15_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles15_x86.mdx index 08b8c00037b..18ee9b187f7 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles15_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles15_x86.mdx @@ -1,44 +1,43 @@ --- navTitle: SLES 15 title: Installing EDB*Plus on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-edbplus +sudo zypper -n install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu18_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu18_x86.mdx index da84af21cf9..87cefed24f1 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu18_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu18_x86.mdx @@ -1,42 +1,33 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB*Plus on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Set up the EDB repository -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 + ```shell + sudo apt-get -y install java + ``` -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-edbplus +sudo apt-get -y install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu20_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu20_x86.mdx index 9bee0e0d5bf..7b283dc8c1d 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu20_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_ubuntu20_x86.mdx @@ -1,42 +1,33 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB*Plus on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Set up the EDB repository -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 + ```shell + sudo apt-get -y install java + ``` -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-edbplus +sudo apt-get -y install edb-as-edbplus ``` Where `` is the version of EDB Postgres Advanced Server. For example, if you are installing with version 14 of EDB Postgres Advanced Server, the package name would be `edb-as14-edbplus`. diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_rhel8_ppcle.mdx index 2c4afaf4c09..b06f29df145 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_rhel8_ppcle.mdx @@ -1,44 +1,42 @@ --- navTitle: RHEL 8 title: Installing Failover Manager on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Refresh the cache: -dnf makecache + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-efm<4x> +sudo dnf -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles12_ppcle.mdx index a9bdee35002..e8836f3e3d5 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Failover Manager on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-efm<4x> +sudo zypper -n install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles15_ppcle.mdx index ba594b44b8e..2d9bc0ebf10 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Failover Manager on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-efm<4x> +sudo zypper -n install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_centos7_x86.mdx index d426fc72d01..127a0ef48c9 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_centos7_x86.mdx @@ -1,37 +1,35 @@ --- navTitle: CentOS 7 title: Installing Failover Manager on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` + ``` ## Install the package ```shell -yum -y install edb-efm<4x> +sudo yum -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_deb10_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_deb10_x86.mdx index 063941a3787..230b428e0c3 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_deb10_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing Failover Manager on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-efm<4x> +sudo apt-get -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_other_linux8_x86.mdx index b8b1f593d6d..4bf6f672091 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_other_linux8_x86.mdx @@ -1,41 +1,37 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing Failover Manager on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Set up the repository -# Install the EPEL repository: -dnf -y install epel-release + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-efm<4x> +sudo dnf -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel7_x86.mdx index e9b98367b4e..6af5617defb 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel7_x86.mdx @@ -1,38 +1,35 @@ --- navTitle: RHEL 7 or OL 7 title: Installing Failover Manager on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - -# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` ## Install the package ```shell -yum -y install edb-efm<4x> +sudo yum -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel_8_x86.mdx index 874d81fdebd..2849fafe71d 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_rhel_8_x86.mdx @@ -1,41 +1,40 @@ --- navTitle: RHEL 8 or OL 8 title: Installing Failover Manager on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-efm<4x> +sudo dnf -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles12_x86.mdx index 0b993fc613d..84a24432fa6 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Failover Manager on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-efm<4x> +sudo zypper -n install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles15_x86.mdx index 24ff5d160ec..e550f5878e2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Failover Manager on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-efm<4x> +sudo zypper -n install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu18_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu18_x86.mdx index c9665204900..06a9866ba54 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu18_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing Failover Manager on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-efm<4x> +sudo apt-get -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu20_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu20_x86.mdx index 78d608fffd9..1c0815ca260 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu20_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/efm4_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing Failover Manager on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-efm<4x> +sudo apt-get -y install edb-efm<4x> ``` Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx index 7c6c7e0e75c..1ff9ebc71ec 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx @@ -1,52 +1,48 @@ --- navTitle: RHEL 8 title: Installing EDB Postgres Advanced Server on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Address other prerequisites -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Refresh the cache: -dnf makecache + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as-server +sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -dnf install +sudo dnf -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx index c00364985c7..e8422f5becb 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx @@ -1,53 +1,44 @@ --- navTitle: SLES 12 title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-server +sudo zypper -n install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx index 642a60b30d3..8a5079ac1dc 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx @@ -1,52 +1,43 @@ --- navTitle: SLES 15 title: Installing EDB Postgres Advanced Server on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-server +sudo zypper -n install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx index feb26a5a8a3..f3a867e37eb 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx @@ -1,45 +1,41 @@ --- navTitle: CentOS 7 title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Address other prerequisites -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - -``` + ``` ## Install the package ```shell -yum -y install edb-as-server +sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -yum install +sudo yum -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx index d519f151363..1e62fedb967 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx @@ -1,50 +1,33 @@ --- navTitle: Debian 10 title: Installing EDB Postgres Advanced Server on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-server +sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -apt-get install +sudo apt-get -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx index 1d4df34119a..fa64f899c9b 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx @@ -1,49 +1,43 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing EDB Postgres Advanced Server on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install epel-release - -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools - -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as-server +sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -dnf install +sudo dnf -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx index f3c3e52cdc4..3248c95c20b 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx @@ -1,46 +1,41 @@ --- navTitle: RHEL 7 or OL 7 title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` ## Install the package ```shell -yum -y install edb-as-server +sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -yum install +sudo yum -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx index 46aaa71d7a9..5eb5d8c1493 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx @@ -1,49 +1,46 @@ --- navTitle: RHEL 8 or OL 8 title: Installing EDB Postgres Advanced Server on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Address other prerequisites -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as-server +sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -dnf install +sudo dnf -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx index 26704b33c97..9cef1ebd28b 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx @@ -1,53 +1,44 @@ --- navTitle: SLES 12 title: Installing EDB Postgres Advanced Server on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-server +sudo zypper -n install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx index c1b29f3b42c..696d7a8e233 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx @@ -1,52 +1,43 @@ --- navTitle: SLES 15 title: Installing EDB Postgres Advanced Server on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-server +sudo zypper -n install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx index 33c9f490e4c..525cb03e126 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx @@ -1,50 +1,33 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB Postgres Advanced Server on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-server +sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -apt-get install +sudo apt-get -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx index aa055570136..d308ef50b9c 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx @@ -1,50 +1,33 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB Postgres Advanced Server on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-server +sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced server you are installing. +Where `` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. To install an individual component: ```shell -apt-get install +sudo apt-get -y install ``` Where `package_name` can be any of the available packages from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx index 5bd12d4e568..f887c22c77b 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx @@ -1,60 +1,43 @@ --- -title: "Installing Replication Server on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing Replication Server on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To log in as a superuser: +- Install Java (version 1.8 or later) on your server, if not present. -```shell -sudo su - -``` - -## Set 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 + sudo dnf -y install java + ``` - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -1. Install the EPEL repository and refresh the cache: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` +- Address other prerequisites -1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + 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 - ``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package @@ -63,19 +46,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -dnf -y install edb-xdb +sudo dnf -y install edb-xdb ``` To install an individual component: ```shell -dnf install package_name +sudo dnf -y install ``` -Where `package_name` is: +Where `` is: -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | \ No newline at end of file +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx index e51478cf18a..1098dc75a5d 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx @@ -1,40 +1,39 @@ --- navTitle: SLES 12 title: Installing Replication Server on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package @@ -43,13 +42,13 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -n install edb-xdb +sudo zypper -y install edb-xdb ``` To install an individual component: ```shell -zypper install +sudo zypper -y install ``` Where `` is: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx index 09bb414b918..707bc58d6f4 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx @@ -1,39 +1,38 @@ --- navTitle: SLES 15 title: Installing Replication Server on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package @@ -42,13 +41,13 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -n install edb-xdb +sudo zypper -y install edb-xdb ``` To install an individual component: ```shell -zypper install +sudo zypper -y install ``` Where `` is: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx index 5c13c8ee8ad..8f54131c74e 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx @@ -21,6 +21,9 @@ For platform-specific install instructions, see: - [CentOS 7](x86_amd64/eprs_centos7_x86) - [SLES 15](x86_amd64/eprs_sles15_x86) - [SLES 12](x86_amd64/eprs_sles12_x86) + - [Ubuntu 20.04](x86_amd64/eprs_ubuntu20_x86) + - [Ubuntu 18.04](x86_amd64/eprs_ubuntu18_x86) + - [Debian 10](x86_amd64/eprs_deb10_x86) - Linux on IBM Power (ppc64le): diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx index baf3a61c626..31f54178a51 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx @@ -1,63 +1,35 @@ --- -title: "Installing Replication Server on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing Replication Server on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -For each step, you must be logged in as superuser. +## Prerequisites -To log in as a superuser: +Before you begin the installation process: -```shell -sudo su - -``` - -In addition, you must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Follow the directions for your host operating system to install Java runtime. +- Install Java (version 1.8 or later) on your server, if not present. -!!! Note - For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. - -## Set up the repository + ```shell + sudo yum -y install java + ``` -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```shell - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - In the directory `/etc/yum.repos.d`, the repository configuration file `edb.repo` is created, which a text file is containing a list of EnterpriseDB repositories, each denoted by an entry starting with the text `[repository_name]`. +- Set up the repository - !!! Note - You may have to enable the \[extras] repository definition in the `CentOS-Base.repo file (located in /etc/yum.repos.d)`. + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -2. Enable access to the packages in any of these repositories: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - - Using your requested credentials for the EDB Yum Repository, substitute the user name and password for the `:` placeholders of the baseurl parameter. - - Change the setting of the enabled parameter to `enabled=1`. +- Address other prerequisites - For example, to access the server `libs` package from the repository for Advanced Server version 14, enable the following entry: + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ```ini - [edbas96] - name=EnterpriseDB Advanced Server 14 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/14/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - - When enabling one version, be sure the other entries are disabled (that is, the parameter setting is `enabled=0` for the non-selected entries). - - For example, to access Replication Server version 7.0, enable the following entry: - - ```ini - [enterprisedb-xdb70] - name=EnterpriseDB XDB 7.0 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/xdb70/redhat/rhel-$releasever-$basearch - enabled=0 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` ## Install the package @@ -67,151 +39,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -yum install edb-xdb +sudo yum -y install edb-xdb ``` To install an individual component: ```shell -yum install package_name +sudo yum -y install ``` -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | - -The following is an example: - -```shell -yum install edb-xdb -__OUTPUT__ -Loaded plugins: fastestmirror, langpacks -Loading mirror speeds from cached hostfile -* base: centos.excellmedia.net -* extras: centos.excellmedia.net -* updates: centos.excellmedia.net -base | 3.6 kB 00:00:00 -edb | 2.5 kB 00:00:00 -extras | 2.9 kB 00:00:00 -updates | 2.9 kB 00:00:00 -edb/7/x86_64/primary_db | 452 kB 00:00:03 -Resolving Dependencies ---> Running transaction check ----> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: edb-jdbc-driver >= 42.2.19.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64 -Loading mirror speeds from cached hostfile - * base: centos.excellmedia.net - * epel: ftp.iij.ad.jp - * extras: centos.excellmedia.net - * updates: centos.excellmedia.net ----> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: ppas-libs >= 13 for package: edb-xdb-console-7.0.0-1.rhel7.x86_64 ----> Package edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed ---> Running transaction check ----> Package edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 will be installed ----> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be installed ---> Finished Dependency Resolution - - - -Dependencies Resolved -========================================================================================================================================================================= -Package Arch Version Repository Size -========================================================================================================================================================================= -Installing: - edb-xdb x86_64 7.0.0-1.rhel7 /edb-xdb-7.0.0-1.rhel7.x86_64 0.0 - edb-xdb-console x86_64 7.0.0-1.rhel7 /edb-xdb-console-7.0.0-1.rhel7.x86_64 3.3 M - edb-xdb-debuginfo x86_64 7.0.0-1.rhel7 /edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 192 k - edb-xdb-libs x86_64 7.0.0-1.rhel7 /edb-xdb-libs-7.0.0-1.rhel7.x86_64 15 M - edb-xdb-publisher x86_64 7.0.0-1.rhel7 /edb-xdb-publisher-7.0.0-1.rhel7.x86_64 131 k - edb-xdb-subscriber x86_64 7.0.0-1.rhel7 /edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5.2 k -Installing for dependencies: - edb-as13-server-libs x86_64 13.4.8-1.rhel7 edb 619 k - edb-jdbc x86_64 42.2.19.1-1.rhel7 edb 1.0 M - -Transaction Summary -========================================================================================================================================================================== -Install 6 Packages (+2 Dependent packages) - -Total size: 20 M -Total download size: 1.6 M -Installed size: 21 M -Downloading packages: -No Presto metadata available for edb -warning: /var/cache/yum/x86_64/7/edb/packages/edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 7e30651c: NOKEY ] 370 kB/s | 928 kB 00:00:01 ETA -Public key for edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm is not installed -(1/2): edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:03 -(2/2): edb-as13-server-libs-13.4.8-1.rhel7.x86_64.rpm | 619 kB 00:00:04 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ -Total 387 kB/s | 1.6 MB 00:00:04 -Retrieving key from file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Importing GPG key 0x7E30651C: - Userid : "EnterpriseDB Inc. (EnterpriseDB Yum Repositories) " - Fingerprint: ca40 9f7c 635f 2ae5 6c9e 8b34 e5ed e919 7e30 651c - Package : edb-repo-20-3.noarch (installed) - From : /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Running transaction check -Running transaction test -Transaction test succeeded -Running transaction - Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/8 - Installing : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 2/8 - Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/8 - Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 4/8 - Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5/8 - Installing : edb-jdbc-42.2.19.1-1.rhel7.x86_64 6/8 - Installing : edb-xdb-7.0.0-1.rhel7.x86_64 7/8 - Installing : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 8/8 - Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 1/8 - Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/8 - Verifying : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 3/8 - Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 4/8 - Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 5/8 - Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 6/8 - Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 7/8 - Verifying : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 8/8 - -Installed: - edb-xdb.x86_64 0:7.0.0-1.rhel7 edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 - edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 - -Dependency Installed: - edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 - -Complete! -``` - -The Replication Server is installed in directory location `/usr/edb/xdb` - -```shell -[root@localhost xdb]# pwd -/usr/edb/xdb -[root@localhost xdb]# ls -l -total 88 - -drwxr-xr-x. 2 root root 4096 Oct 7 12:50 bin --r--r--r--. 1 root root 15272 Jul 12 09:58 edb-xdb_license.txt -drwxr-xr-x. 3 root root 151 Oct 7 12:50 etc -drwxr-xr-x. 4 root root 4096 Oct 7 12:50 lib -drwx------. 2 enterprisedb enterprisedb 6 Oct 7 00:07 xdata --r--r--r--. 1 enterprisedb enterprisedb 61497 Jul 12 09:58 xdb_3rd_party_licenses.txt -``` - -Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details). - -!!! Note - Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). - - -## Initial configuration - -In the Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the Replication Configuration File](../../../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file/#encrypt_password_in_conf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [Replication Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for more information. +Where `` is: -The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information. See [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details) for the location of this file. +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx new file mode 100644 index 00000000000..25b44b6b466 --- /dev/null +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx @@ -0,0 +1,49 @@ +--- +navTitle: Debian 10 +title: Installing Replication Server on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo apt-get -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +## Install the package + +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: + +```shell +sudo apt-get -y install edb-xdb +``` + +To install an individual component: + +```shell +sudo apt-get -y install +``` + +Where `` is: + +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx index 34ae1691ab0..d098c64c7ef 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx @@ -1,63 +1,39 @@ --- -title: "Installing Replication Server on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing Replication Server on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -For each step, you must be logged in as superuser. +## Prerequisites -To log in as a superuser: +Before you begin the installation process: -```shell -sudo su - -``` - -In addition, you must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. - -Follow the directions for your host operating system to install Java runtime. - -!!! Note - For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. - -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - In the directory `/etc/yum.repos.d`, the repository configuration file `edb.repo` is created, which a text file is containing a list of EnterpriseDB repositories, each denoted by an entry starting with the text `[repository_name]`. +- Install Java (version 1.8 or later) on your server, if not present. -2. Enable access to the packages in any of these repositories: + ```shell + sudo dnf -y install java + ``` - - Using your requested credentials for the EDB Yum Repository, substitute the user name and password for the `:` placeholders of the baseurl parameter. - - Change the setting of the enabled parameter to `enabled=1`. +- Set up the repository - For example, to access the server `libs` package from the repository for Advanced Server version 14, enable the following entry: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - ```ini - [edbas96] - name=EnterpriseDB Advanced Server 14 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/14/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - When enabling one version, be sure the other entries are disabled (that is, the parameter setting is `enabled=0` for the non-selected entries). - - For example, to access Replication Server version 7.0, enable the following entry: - - ```ini - [enterprisedb-xdb70] - name=EnterpriseDB XDB 7.0 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/xdb70/redhat/rhel-$releasever-$basearch - enabled=0 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql ``` - ## Install the package You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. @@ -65,151 +41,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -dnf -y install edb-xdb +sudo dnf -y install edb-xdb ``` To install an individual component: ```shell -dnf install package_name +sudo dnf -y install ``` -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | - -The following is an example: - -```shell -dnf -y install edb-xdb -__OUTPUT__ -Loaded plugins: fastestmirror, langpacks -Loading mirror speeds from cached hostfile -* base: centos.excellmedia.net -* extras: centos.excellmedia.net -* updates: centos.excellmedia.net -base | 3.6 kB 00:00:00 -edb | 2.5 kB 00:00:00 -extras | 2.9 kB 00:00:00 -updates | 2.9 kB 00:00:00 -edb/7/x86_64/primary_db | 452 kB 00:00:03 -Resolving Dependencies ---> Running transaction check ----> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: edb-jdbc-driver >= 42.2.19.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64 -Loading mirror speeds from cached hostfile - * base: centos.excellmedia.net - * epel: ftp.iij.ad.jp - * extras: centos.excellmedia.net - * updates: centos.excellmedia.net ----> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: ppas-libs >= 13 for package: edb-xdb-console-7.0.0-1.rhel7.x86_64 ----> Package edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed ---> Running transaction check ----> Package edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 will be installed ----> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be installed ---> Finished Dependency Resolution - - - -Dependencies Resolved -========================================================================================================================================================================= -Package Arch Version Repository Size -========================================================================================================================================================================= -Installing: - edb-xdb x86_64 7.0.0-1.rhel7 /edb-xdb-7.0.0-1.rhel7.x86_64 0.0 - edb-xdb-console x86_64 7.0.0-1.rhel7 /edb-xdb-console-7.0.0-1.rhel7.x86_64 3.3 M - edb-xdb-debuginfo x86_64 7.0.0-1.rhel7 /edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 192 k - edb-xdb-libs x86_64 7.0.0-1.rhel7 /edb-xdb-libs-7.0.0-1.rhel7.x86_64 15 M - edb-xdb-publisher x86_64 7.0.0-1.rhel7 /edb-xdb-publisher-7.0.0-1.rhel7.x86_64 131 k - edb-xdb-subscriber x86_64 7.0.0-1.rhel7 /edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5.2 k -Installing for dependencies: - edb-as13-server-libs x86_64 13.4.8-1.rhel7 edb 619 k - edb-jdbc x86_64 42.2.19.1-1.rhel7 edb 1.0 M - -Transaction Summary -========================================================================================================================================================================== -Install 6 Packages (+2 Dependent packages) - -Total size: 20 M -Total download size: 1.6 M -Installed size: 21 M -Downloading packages: -No Presto metadata available for edb -warning: /var/cache/yum/x86_64/7/edb/packages/edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 7e30651c: NOKEY ] 370 kB/s | 928 kB 00:00:01 ETA -Public key for edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm is not installed -(1/2): edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:03 -(2/2): edb-as13-server-libs-13.4.8-1.rhel7.x86_64.rpm | 619 kB 00:00:04 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ -Total 387 kB/s | 1.6 MB 00:00:04 -Retrieving key from file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Importing GPG key 0x7E30651C: - Userid : "EnterpriseDB Inc. (EnterpriseDB Yum Repositories) " - Fingerprint: ca40 9f7c 635f 2ae5 6c9e 8b34 e5ed e919 7e30 651c - Package : edb-repo-20-3.noarch (installed) - From : /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Running transaction check -Running transaction test -Transaction test succeeded -Running transaction - Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/8 - Installing : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 2/8 - Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/8 - Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 4/8 - Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5/8 - Installing : edb-jdbc-42.2.19.1-1.rhel7.x86_64 6/8 - Installing : edb-xdb-7.0.0-1.rhel7.x86_64 7/8 - Installing : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 8/8 - Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 1/8 - Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/8 - Verifying : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 3/8 - Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 4/8 - Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 5/8 - Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 6/8 - Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 7/8 - Verifying : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 8/8 - -Installed: - edb-xdb.x86_64 0:7.0.0-1.rhel7 edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 - edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 - -Dependency Installed: - edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 - -Complete! -``` - -The Replication Server is installed in directory location `/usr/edb/xdb` - -```shell -[root@localhost xdb]# pwd -/usr/edb/xdb -[root@localhost xdb]# ls -l -total 88 - -drwxr-xr-x. 2 root root 4096 Oct 7 12:50 bin --r--r--r--. 1 root root 15272 Jul 12 09:58 edb-xdb_license.txt -drwxr-xr-x. 3 root root 151 Oct 7 12:50 etc -drwxr-xr-x. 4 root root 4096 Oct 7 12:50 lib -drwx------. 2 enterprisedb enterprisedb 6 Oct 7 00:07 xdata --r--r--r--. 1 enterprisedb enterprisedb 61497 Jul 12 09:58 xdb_3rd_party_licenses.txt -``` - -Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details). - -!!! Note - Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). - - -## Initial configuration - -In the Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the Replication Configuration File](../../../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file/#encrypt_password_in_conf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [Replication Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for more information. +Where `` is: -The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information. See [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details) for the location of this file. +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx index 15b21680af6..a1bdf773714 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx @@ -1,60 +1,35 @@ --- -title: "Installing Replication Server on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7 " +navTitle: RHEL 7 or OL 7 +title: Installing Replication Server on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -For each step, you must be logged in as superuser. +## Prerequisites -To log in as a superuser: +Before you begin the installation process: -```shell -sudo su - -``` - -In addition, you must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. - -Follow the directions for your host operating system to install Java runtime. - -!!! Note - For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. - -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```shell - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - In the directory `/etc/yum.repos.d`, the repository configuration file `edb.repo` is created, which a text file is containing a list of EnterpriseDB repositories, each denoted by an entry starting with the text `[repository_name]`. +- Install Java (version 1.8 or later) on your server, if not present. -2. Enable access to the packages in any of these repositories: + ```shell + sudo yum -y install java + ``` - - Using your requested credentials for the EDB Yum Repository, substitute the user name and password for the `:` placeholders of the baseurl parameter. - - Change the setting of the enabled parameter to `enabled=1`. +- Set up the repository - For example, to access the server `libs` package from the repository for Advanced Server version 14, enable the following entry: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - ```ini - [edbas96] - name=EnterpriseDB Advanced Server 14 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/14/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - When enabling one version, be sure the other entries are disabled (that is, the parameter setting is `enabled=0` for the non-selected entries). - - For example, to access Replication Server version 7.0, enable the following entry: - - ```ini - [enterprisedb-xdb70] - name=EnterpriseDB XDB 7.0 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/xdb70/redhat/rhel-$releasever-$basearch - enabled=0 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` ## Install the package @@ -64,151 +39,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -yum install edb-xdb +sudo yum -y install edb-xdb ``` To install an individual component: ```shell -yum install package_name -``` - -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | - -The following is an example: - -```shell -yum install edb-xdb -__OUTPUT__ -Loaded plugins: fastestmirror, langpacks -Loading mirror speeds from cached hostfile -* base: centos.excellmedia.net -* extras: centos.excellmedia.net -* updates: centos.excellmedia.net -base | 3.6 kB 00:00:00 -edb | 2.5 kB 00:00:00 -extras | 2.9 kB 00:00:00 -updates | 2.9 kB 00:00:00 -edb/7/x86_64/primary_db | 452 kB 00:00:03 -Resolving Dependencies ---> Running transaction check ----> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: edb-jdbc-driver >= 42.2.19.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64 -Loading mirror speeds from cached hostfile - * base: centos.excellmedia.net - * epel: ftp.iij.ad.jp - * extras: centos.excellmedia.net - * updates: centos.excellmedia.net ----> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: ppas-libs >= 13 for package: edb-xdb-console-7.0.0-1.rhel7.x86_64 ----> Package edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed ---> Running transaction check ----> Package edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 will be installed ----> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be installed ---> Finished Dependency Resolution - - - -Dependencies Resolved -========================================================================================================================================================================= -Package Arch Version Repository Size -========================================================================================================================================================================= -Installing: - edb-xdb x86_64 7.0.0-1.rhel7 /edb-xdb-7.0.0-1.rhel7.x86_64 0.0 - edb-xdb-console x86_64 7.0.0-1.rhel7 /edb-xdb-console-7.0.0-1.rhel7.x86_64 3.3 M - edb-xdb-debuginfo x86_64 7.0.0-1.rhel7 /edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 192 k - edb-xdb-libs x86_64 7.0.0-1.rhel7 /edb-xdb-libs-7.0.0-1.rhel7.x86_64 15 M - edb-xdb-publisher x86_64 7.0.0-1.rhel7 /edb-xdb-publisher-7.0.0-1.rhel7.x86_64 131 k - edb-xdb-subscriber x86_64 7.0.0-1.rhel7 /edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5.2 k -Installing for dependencies: - edb-as13-server-libs x86_64 13.4.8-1.rhel7 edb 619 k - edb-jdbc x86_64 42.2.19.1-1.rhel7 edb 1.0 M - -Transaction Summary -========================================================================================================================================================================== -Install 6 Packages (+2 Dependent packages) - -Total size: 20 M -Total download size: 1.6 M -Installed size: 21 M -Downloading packages: -No Presto metadata available for edb -warning: /var/cache/yum/x86_64/7/edb/packages/edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 7e30651c: NOKEY ] 370 kB/s | 928 kB 00:00:01 ETA -Public key for edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm is not installed -(1/2): edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:03 -(2/2): edb-as13-server-libs-13.4.8-1.rhel7.x86_64.rpm | 619 kB 00:00:04 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ -Total 387 kB/s | 1.6 MB 00:00:04 -Retrieving key from file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Importing GPG key 0x7E30651C: - Userid : "EnterpriseDB Inc. (EnterpriseDB Yum Repositories) " - Fingerprint: ca40 9f7c 635f 2ae5 6c9e 8b34 e5ed e919 7e30 651c - Package : edb-repo-20-3.noarch (installed) - From : /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Running transaction check -Running transaction test -Transaction test succeeded -Running transaction - Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/8 - Installing : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 2/8 - Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/8 - Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 4/8 - Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5/8 - Installing : edb-jdbc-42.2.19.1-1.rhel7.x86_64 6/8 - Installing : edb-xdb-7.0.0-1.rhel7.x86_64 7/8 - Installing : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 8/8 - Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 1/8 - Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/8 - Verifying : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 3/8 - Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 4/8 - Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 5/8 - Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 6/8 - Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 7/8 - Verifying : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 8/8 - -Installed: - edb-xdb.x86_64 0:7.0.0-1.rhel7 edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 - edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 - -Dependency Installed: - edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 - -Complete! +sudo yum -y install ``` -The Replication Server is installed in directory location `/usr/edb/xdb` - -```shell -[root@localhost xdb]# pwd -/usr/edb/xdb -[root@localhost xdb]# ls -l -total 88 - -drwxr-xr-x. 2 root root 4096 Oct 7 12:50 bin --r--r--r--. 1 root root 15272 Jul 12 09:58 edb-xdb_license.txt -drwxr-xr-x. 3 root root 151 Oct 7 12:50 etc -drwxr-xr-x. 4 root root 4096 Oct 7 12:50 lib -drwx------. 2 enterprisedb enterprisedb 6 Oct 7 00:07 xdata --r--r--r--. 1 enterprisedb enterprisedb 61497 Jul 12 09:58 xdb_3rd_party_licenses.txt -``` - -Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details). - -!!! Note - Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). - - -## Initial configuration - -In the Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the Replication Configuration File](../../../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file/#encrypt_password_in_conf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [Replication Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for more information. +Where `` is: -The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information. See [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details) for the location of this file. +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx index c277574da1b..2014b664386 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx @@ -1,60 +1,40 @@ --- -title: "Installing Replication Server on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing Replication Server on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -For each step, you must be logged in as superuser. +## Prerequisites -To log in as a superuser: +Before you begin the installation process: -```shell -sudo su - -``` +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -In addition, you must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. +- Install Java (version 1.8 or later) on your server, if not present. -Follow the directions for your host operating system to install Java runtime. + ```shell + sudo dnf -y install java + ``` -!!! Note - For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. +- Set up the repository -## Set 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 this step. -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - In the directory `/etc/yum.repos.d`, the repository configuration file `edb.repo` is created, which a text file is containing a list of EnterpriseDB repositories, each denoted by an entry starting with the text `[repository_name]`. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -2. Enable access to the packages in any of these repositories: +- Address other prerequisites - - Using your requested credentials for the EDB Yum Repository, substitute the user name and password for the `:` placeholders of the baseurl parameter. - - Change the setting of the enabled parameter to `enabled=1`. - - For example, to access the server `libs` package from the repository for Advanced Server version 14, enable the following entry: + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ```ini - [edbas96] - name=EnterpriseDB Advanced Server 14 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/14/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - When enabling one version, be sure the other entries are disabled (that is, the parameter setting is `enabled=0` for the non-selected entries). - - For example, to access Replication Server version 7.0, enable the following entry: - - ```ini - [enterprisedb-xdb70] - name=EnterpriseDB XDB 7.0 $releasever - $basearch - baseurl=http://:@yum.enterprisedb.com/xdb70/redhat/rhel-$releasever-$basearch - enabled=0 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql ``` ## Install the package @@ -64,151 +44,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -dnf -y install edb-xdb +sudo dnf -y install edb-xdb ``` To install an individual component: ```shell -dnf install package_name -``` - -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | - -The following is an example: - -```shell -dnf -y install edb-xdb -__OUTPUT__ -Loaded plugins: fastestmirror, langpacks -Loading mirror speeds from cached hostfile -* base: centos.excellmedia.net -* extras: centos.excellmedia.net -* updates: centos.excellmedia.net -base | 3.6 kB 00:00:00 -edb | 2.5 kB 00:00:00 -extras | 2.9 kB 00:00:00 -updates | 2.9 kB 00:00:00 -edb/7/x86_64/primary_db | 452 kB 00:00:03 -Resolving Dependencies ---> Running transaction check ----> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: edb-jdbc-driver >= 42.2.19.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64 -Loading mirror speeds from cached hostfile - * base: centos.excellmedia.net - * epel: ftp.iij.ad.jp - * extras: centos.excellmedia.net - * updates: centos.excellmedia.net ----> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed ---> Processing Dependency: ppas-libs >= 13 for package: edb-xdb-console-7.0.0-1.rhel7.x86_64 ----> Package edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed ----> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed ---> Running transaction check ----> Package edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 will be installed ----> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be installed ---> Finished Dependency Resolution - - - -Dependencies Resolved -========================================================================================================================================================================= -Package Arch Version Repository Size -========================================================================================================================================================================= -Installing: - edb-xdb x86_64 7.0.0-1.rhel7 /edb-xdb-7.0.0-1.rhel7.x86_64 0.0 - edb-xdb-console x86_64 7.0.0-1.rhel7 /edb-xdb-console-7.0.0-1.rhel7.x86_64 3.3 M - edb-xdb-debuginfo x86_64 7.0.0-1.rhel7 /edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 192 k - edb-xdb-libs x86_64 7.0.0-1.rhel7 /edb-xdb-libs-7.0.0-1.rhel7.x86_64 15 M - edb-xdb-publisher x86_64 7.0.0-1.rhel7 /edb-xdb-publisher-7.0.0-1.rhel7.x86_64 131 k - edb-xdb-subscriber x86_64 7.0.0-1.rhel7 /edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5.2 k -Installing for dependencies: - edb-as13-server-libs x86_64 13.4.8-1.rhel7 edb 619 k - edb-jdbc x86_64 42.2.19.1-1.rhel7 edb 1.0 M - -Transaction Summary -========================================================================================================================================================================== -Install 6 Packages (+2 Dependent packages) - -Total size: 20 M -Total download size: 1.6 M -Installed size: 21 M -Downloading packages: -No Presto metadata available for edb -warning: /var/cache/yum/x86_64/7/edb/packages/edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 7e30651c: NOKEY ] 370 kB/s | 928 kB 00:00:01 ETA -Public key for edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm is not installed -(1/2): edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:03 -(2/2): edb-as13-server-libs-13.4.8-1.rhel7.x86_64.rpm | 619 kB 00:00:04 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ -Total 387 kB/s | 1.6 MB 00:00:04 -Retrieving key from file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Importing GPG key 0x7E30651C: - Userid : "EnterpriseDB Inc. (EnterpriseDB Yum Repositories) " - Fingerprint: ca40 9f7c 635f 2ae5 6c9e 8b34 e5ed e919 7e30 651c - Package : edb-repo-20-3.noarch (installed) - From : /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -Running transaction check -Running transaction test -Transaction test succeeded -Running transaction - Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/8 - Installing : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 2/8 - Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/8 - Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 4/8 - Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5/8 - Installing : edb-jdbc-42.2.19.1-1.rhel7.x86_64 6/8 - Installing : edb-xdb-7.0.0-1.rhel7.x86_64 7/8 - Installing : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 8/8 - Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 1/8 - Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/8 - Verifying : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 3/8 - Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 4/8 - Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 5/8 - Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 6/8 - Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 7/8 - Verifying : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 8/8 - -Installed: - edb-xdb.x86_64 0:7.0.0-1.rhel7 edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 - edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 - -Dependency Installed: - edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 - -Complete! -``` - -The Replication Server is installed in directory location `/usr/edb/xdb` - -```shell -[root@localhost xdb]# pwd -/usr/edb/xdb -[root@localhost xdb]# ls -l -total 88 - -drwxr-xr-x. 2 root root 4096 Oct 7 12:50 bin --r--r--r--. 1 root root 15272 Jul 12 09:58 edb-xdb_license.txt -drwxr-xr-x. 3 root root 151 Oct 7 12:50 etc -drwxr-xr-x. 4 root root 4096 Oct 7 12:50 lib -drwx------. 2 enterprisedb enterprisedb 6 Oct 7 00:07 xdata --r--r--r--. 1 enterprisedb enterprisedb 61497 Jul 12 09:58 xdb_3rd_party_licenses.txt +sudo dnf -y install ``` -Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details). - -!!! Note - Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). - - -## Initial configuration - -In the Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the Replication Configuration File](../../../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file/#encrypt_password_in_conf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [Replication Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for more information. +Where `` is: -The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information. [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details) for the location of this file. +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx index 92b1cd5bacf..3a5817e26d0 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx @@ -1,40 +1,39 @@ --- navTitle: SLES 12 title: Installing Replication Server on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package @@ -43,13 +42,13 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -n install edb-xdb +sudo zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `` is: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx index 49d3ac67e7e..f03340e9267 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx @@ -1,39 +1,38 @@ --- navTitle: SLES 15 title: Installing Replication Server on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install Java (version 1.8 or later) on your server, if not present. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + ```shell + sudo zypper -y install java + ``` -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Set up the repository -# 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' + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Refresh the metadata -zypper refresh -``` +- Address other prerequisites + + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 + + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package @@ -42,13 +41,13 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -n install edb-xdb +sudo zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install +sudo zypper -n install ``` Where `` is: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx new file mode 100644 index 00000000000..ac8df099104 --- /dev/null +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx @@ -0,0 +1,49 @@ +--- +navTitle: Ubuntu 18.04 +title: Installing Replication Server on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo apt-get -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +## Install the package + +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: + +```shell +sudo apt-get -y install edb-xdb +``` + +To install an individual component: + +```shell +sudo apt-get -y install +``` + +Where `` is: + +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx new file mode 100644 index 00000000000..b5684e00fe2 --- /dev/null +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx @@ -0,0 +1,49 @@ +--- +navTitle: Ubuntu 20.04 +title: Installing Replication Server on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Install Java (version 1.8 or later) on your server, if not present. + + ```shell + sudo apt-get -y install java + ``` + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +## Install the package + +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: + +```shell +sudo apt-get -y install edb-xdb +``` + +To install an individual component: + +```shell +sudo apt-get -y install +``` + +Where `` is: + +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx index 7a1108a18cb..f1364813d86 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx @@ -8,6 +8,9 @@ navigation: - eprs_centos7_x86 - eprs_sles15_x86 - eprs_sles12_x86 + - eprs_ubuntu20_x86 + - eprs_ubuntu18_x86 + - eprs_deb10_x86 --- For operating system-specific install instructions, see: @@ -19,3 +22,6 @@ For operating system-specific install instructions, see: - [CentOS 7](eprs_centos7_x86) - [SLES 15](eprs_sles15_x86) - [SLES 12](eprs_sles12_x86) + - [Ubuntu 20.04](eprs_ubuntu20_x86) + - [Ubuntu 18.04](eprs_ubuntu18_x86) + - [Debian 10](eprs_deb10_x86) diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx index 0f6af2cd5bb..8f2574bad06 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx @@ -1,44 +1,42 @@ --- navTitle: RHEL 8 title: Installing Hadoop Foreign Data Wrapper on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Refresh the cache: -dnf makecache + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-hdfs_fdw +sudo dnf -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles12_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles12_ppcle.mdx index 26edf0a052e..b68fee08402 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles12_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Hadoop Foreign Data Wrapper on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-hdfs_fdw +sudo zypper -n install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles15_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles15_ppcle.mdx index 1204fc5b83d..3d1135661c1 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles15_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Hadoop Foreign Data Wrapper on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-hdfs_fdw +sudo zypper -n install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx index dce6184082c..fa47bde021f 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx @@ -1,37 +1,35 @@ --- navTitle: CentOS 7 title: Installing Hadoop Foreign Data Wrapper on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` + ``` ## Install the package ```shell -yum -y install edb-as14-hdfs_fdw +sudo yum -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_deb10_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_deb10_x86.mdx index 4890f1a9562..5e8499ffd0a 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_deb10_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing Hadoop Foreign Data Wrapper on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-hdfs_fdw +sudo apt-get -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx index 4965f469783..a06408b9550 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx @@ -1,41 +1,37 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing Hadoop Foreign Data Wrapper on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Set up the repository -# Install the EPEL repository: -dnf -y install epel-release + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-hdfs_fdw +sudo dnf -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx index 37d6884a244..fd0e2070807 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx @@ -1,38 +1,35 @@ --- navTitle: RHEL 7 or OL 7 title: Installing Hadoop Foreign Data Wrapper on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - -# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` ## Install the package ```shell -yum -y install edb-as14-hdfs_fdw +sudo yum -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx index d9c29e9492d..cef0aa73d03 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx @@ -1,41 +1,39 @@ --- navTitle: RHEL 8 or OL 8 title: Installing Hadoop Foreign Data Wrapper on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-hdfs_fdw +sudo dnf -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles12_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles12_x86.mdx index 7421749d24f..03718e368de 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles12_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Hadoop Foreign Data Wrapper on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-hdfs_fdw +sudo zypper -n install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles15_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles15_x86.mdx index 4e96a2ac4ec..3413ec23ac0 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles15_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Hadoop Foreign Data Wrapper on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-hdfs_fdw +sudo zypper -n install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu18_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu18_x86.mdx index 0bdc8dc632f..e81dde1986f 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu18_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing Hadoop Foreign Data Wrapper on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-hdfs_fdw +sudo apt-get -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu20_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu20_x86.mdx index 7205777f450..44d7b0364be 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu20_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing Hadoop Foreign Data Wrapper on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-hdfs_fdw +sudo apt-get -y install edb-as14-hdfs_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx index f1031c6e251..8523eaeda10 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx @@ -1,64 +1,41 @@ --- -title: "Installing EDB JDBC Connector on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing EDB JDBC Connector on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -To log in as a superuser: +- Set up the repository -```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 - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - This creates the /etc/yum.repos.d/edb.repo configuration file. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Add your EDB credentials to the edb.repo file: +- Address other prerequisites - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -1. Install the EPEL repository and refresh the cache: + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - ```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 +## Install the package ```shell -dnf -y install edb-jdbc +sudo dnf -y install edb-jdbc ``` - diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx index 8f9a5bfccda..c047388f0c8 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx @@ -1,45 +1,39 @@ --- navTitle: SLES 12 title: Installing EDB JDBC Connector on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-jdbc +sudo zypper -n install edb-jdbc ``` ## Initial configuration diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx index 422e222c4d6..95b5ac3b6ba 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx @@ -1,44 +1,38 @@ --- navTitle: SLES 15 title: Installing EDB JDBC Connector on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-jdbc +sudo zypper -n install edb-jdbc ``` ## Initial configuration diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx index c15fb02655d..4a6ec503040 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx @@ -1,62 +1,34 @@ --- -title: "Installing EDB JDBC Connector on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing EDB JDBC Connector on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -!!! Note - You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). +- Set up the repository -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -After receiving your repository credentials you can: +- Address other prerequisites -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-jdbc`. + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -## Creating a repository configuration file + ``` -To create the repository configuration file, assume superuser privileges, and invoke the following command: +## Install the package -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +```shell +sudo yum -y install edb-jdbc ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -## Modifying the file, providing your user name and password - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -## Installing JDBC Connector - -After saving your changes to the configuration file, use the following command to install the JDBC Connector: - -```text -yum install edb-jdbc -``` - -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 `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. - diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx index d26a992fe35..bbcc7b909c6 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx @@ -1,40 +1,26 @@ --- navTitle: Debian 10 title: Installing EDB JDBC Connector on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-jdbc +sudo apt-get -y install edb-jdbc ``` diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx index 8dada8e9444..51b9e6535cd 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx @@ -1,64 +1,36 @@ --- -title: "Installing EDB JDBC Connector on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB JDBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `PowerTools` repository: - -```text -dnf config-manager --set-enabled PowerTools -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-jdbc`. +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -## Creating a repository configuration file +- Set up the repository -To create the repository configuration file, assume superuser privileges, and invoke the following command: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -```text -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -## Modifying the file, providing your user name and password - -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 EDB user. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -## Installing JDBC Connector +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -After saving your changes to the configuration file, use the following command to install the JDBC Connector: +## Install the package -```text -dnf install edb-jdbc +```shell +sudo dnf -y install edb-jdbc ``` - -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 `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. diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx index df80c40b96f..d0f31bed1f6 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx @@ -1,65 +1,34 @@ --- -title: "Installing EDB JDBC Connector on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7 " +navTitle: RHEL 7 or OL 7 +title: Installing EDB JDBC Connector on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -Enable the optional, extras, and HA repositories: - -```text -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - +- Set up the repository -After receiving your repository credentials you can: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-jdbc`. - -## Creating a repository configuration file - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` -## Modifying the file, providing your user name and password - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -## Installing JDBC Connector - -After saving your changes to the configuration file, use the following command to install the JDBC Connector: +## Install the package ```shell -yum install edb-jdbc +sudo yum -y install edb-jdbc ``` - -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 `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. - diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx index 11f5d4fe54e..66bda2d350f 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx @@ -1,65 +1,39 @@ --- -title: "Installing EDB JDBC Connector on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB JDBC Connector on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - -```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: +- Set 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 this step. -After receiving your repository credentials you can: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-jdbc`. +- Address other prerequisites -## Creating a repository configuration file - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -## Modifying the file, providing your user name and password + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo dnf -y install edb-jdbc ``` - -## Installing JDBC Connector - -After saving your changes to the configuration file, use the below command to install the JDBC Connector: - -```text -dnf install edb-jdbc -``` - -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 `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. diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx index 8c0b84498f7..32af347a815 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx @@ -1,45 +1,39 @@ --- navTitle: SLES 12 title: Installing EDB JDBC Connector on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-jdbc +sudo zypper -n install edb-jdbc ``` ## Initial configuration diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx index df883470dc1..09423bb8677 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx @@ -1,44 +1,38 @@ --- navTitle: SLES 15 title: Installing EDB JDBC Connector on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-jdbc +sudo zypper -n install edb-jdbc ``` ## Initial configuration diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx index 314c91ffb5b..621b75ed65d 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx @@ -1,40 +1,26 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB JDBC Connector on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-jdbc +sudo apt-get -y install edb-jdbc ``` diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx index 0947be08359..3486de4a032 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx @@ -1,40 +1,26 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB JDBC Connector on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-jdbc +sudo apt-get -y install edb-jdbc ``` diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_rhel8_ppcle.mdx index 4150497a233..9e1f19e6994 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_rhel8_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_rhel8_ppcle.mdx @@ -1,44 +1,42 @@ --- navTitle: RHEL 8 title: Installing Migration Toolkit on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Refresh the cache: -dnf makecache + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-migrationtoolkit +sudo dnf -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles12_ppcle.mdx index 18184e66514..1738a08004f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles12_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Migration Toolkit on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-migrationtoolkit +sudo zypper -n install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles15_ppcle.mdx index 4585cb579ae..3c5e54ed9bd 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles15_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Migration Toolkit on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-migrationtoolkit +sudo zypper -n install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_centos7_x86.mdx index c5e8cbedb1f..6c5a8163683 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_centos7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_centos7_x86.mdx @@ -1,37 +1,35 @@ --- navTitle: CentOS 7 title: Installing Migration Toolkit on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` + ``` ## Install the package ```shell -yum -y install edb-migrationtoolkit +sudo yum -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_deb10_x86.mdx index 5884cb638ae..acfc29a1f47 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_deb10_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing Migration Toolkit on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-migrationtoolkit +sudo apt-get -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_other_linux8_x86.mdx index 925d0109556..180da215147 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_other_linux8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_other_linux8_x86.mdx @@ -1,38 +1,37 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing Migration Toolkit on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` ## Install the package ```shell -dnf -y install edb-migrationtoolkit +sudo dnf -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel7_x86.mdx index 7cbff260e61..959330e1cfe 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel7_x86.mdx @@ -1,37 +1,33 @@ --- navTitle: RHEL 7 or OL 7 title: Installing Migration Toolkit on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Set up the repository -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ``` ## Install the package ```shell -yum -y install edb-migrationtoolkit +sudo yum -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel8_x86.mdx index a3c745fca90..83186f53a75 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel8_x86.mdx @@ -1,38 +1,35 @@ --- navTitle: RHEL 8 or OL 8 title: Installing Migration Toolkit on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` ## Install the package ```shell -dnf -y install edb-migrationtoolkit +sudo dnf -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles12_x86.mdx index 51b98ea487d..bbcf4199155 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles12_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing Migration Toolkit on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-migrationtoolkit +sudo zypper -n install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles15_x86.mdx index 7efa048ff34..09336c76b8b 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles15_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing Migration Toolkit on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-migrationtoolkit +sudo zypper -n install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu18_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu18_x86.mdx index 4fd709e0c68..64b96f960ce 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu18_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing Migration Toolkit on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-migrationtoolkit +sudo apt-get -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu20_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu20_x86.mdx index a00a6a9cf82..6e60c5c7ddc 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu20_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing Migration Toolkit on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-migrationtoolkit +sudo apt-get -y install edb-migrationtoolkit ``` ## Initial configuration diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx index f0473a7202c..f3ff437d44f 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx @@ -1,44 +1,42 @@ --- navTitle: RHEL 8 title: Installing MongoDB Foreign Data Wrapper on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Refresh the cache: -dnf makecache + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-mongo_fdw +sudo dnf -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles12_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles12_ppcle.mdx index 14e6dfe3c17..db87bfd9a5c 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles12_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing MongoDB Foreign Data Wrapper on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-mongo_fdw +sudo zypper -n install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles15_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles15_ppcle.mdx index 05cbf1045c8..a0bfb7b740e 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles15_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing MongoDB Foreign Data Wrapper on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-mongo_fdw +sudo zypper -n install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx index 1c42e21f74e..941afb32b1b 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx @@ -1,37 +1,35 @@ --- navTitle: CentOS 7 title: Installing MongoDB Foreign Data Wrapper on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` + ``` ## Install the package ```shell -yum -y install edb-as14-mongo_fdw +sudo yum -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_deb10_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_deb10_x86.mdx index 15d9b67716d..d6bea664918 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_deb10_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing MongoDB Foreign Data Wrapper on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-mongo_fdw +sudo apt-get -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx index 7f976b231da..67d745465db 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx @@ -1,41 +1,37 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing MongoDB Foreign Data Wrapper on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Set up the repository -# Install the EPEL repository: -dnf -y install epel-release + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-mongo_fdw +sudo dnf -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx index 2994671ceb8..04ea2e00313 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx @@ -1,38 +1,35 @@ --- navTitle: RHEL 7 or OL 7 title: Installing MongoDB Foreign Data Wrapper on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - -# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` ## Install the package ```shell -yum -y install edb-as14-mongo_fdw +sudo yum -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx index a214b6985a2..2b38d423883 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx @@ -1,41 +1,40 @@ --- navTitle: RHEL 8 or OL 8 title: Installing MongoDB Foreign Data Wrapper on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell -dnf -y install edb-as14-mongo_fdw +sudo dnf -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles12_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles12_x86.mdx index 103922f7824..8402a94c928 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles12_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing MongoDB Foreign Data Wrapper on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-mongo_fdw +sudo zypper -n install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles15_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles15_x86.mdx index 2d4178532d3..4ed91987d24 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles15_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing MongoDB Foreign Data Wrapper on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as14-mongo_fdw +sudo zypper -n install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu18_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu18_x86.mdx index 37c5ab701b1..12be8d0728c 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu18_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing MongoDB Foreign Data Wrapper on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-mongo_fdw +sudo apt-get -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu20_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu20_x86.mdx index 0ba6ad3b560..7da4d893367 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu20_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing MongoDB Foreign Data Wrapper on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as14-mongo_fdw +sudo apt-get -y install edb-as14-mongo_fdw ``` Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_rhel8_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_rhel8_ppcle.mdx index 1e737a1ce8f..2fa7156b205 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_rhel8_ppcle.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_rhel8_ppcle.mdx @@ -1,68 +1,40 @@ --- -title: "Installing MySQL Foreign Data Wrapper on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing MySQL Foreign Data Wrapper on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To log in as a superuser: +- Set up the repository -```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. + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -1. Add your EDB credentials to the edb.repo file: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Address other prerequisites - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -1. Install the EPEL repository and refresh the cache: + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ```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 +## Install the package ```shell -dnf -y install edb-as-mysql8_fdw +sudo dnf -y install edb-as-mysql-fdw ``` -where `xx` is the server version number. - - - +Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles12_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles12_ppcle.mdx index d69bb681e8c..e050573226d 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles12_ppcle.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles12_ppcle.mdx @@ -1,53 +1,46 @@ --- navTitle: SLES 12 title: Installing MySQL Foreign Data Wrapper on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + ```shell + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-mysql-fdw +sudo zypper -n install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles15_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles15_ppcle.mdx index 9508c84a292..b19c5f43fa2 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles15_ppcle.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles15_ppcle.mdx @@ -1,52 +1,45 @@ --- navTitle: SLES 15 title: Installing MySQL Foreign Data Wrapper on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + ```shell + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-mysql-fdw +sudo zypper -n install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_centos7_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_centos7_x86.mdx index 4c85d3b47dc..9527ac17e3e 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_centos7_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_centos7_x86.mdx @@ -1,72 +1,43 @@ --- -title: "Installing MySQL Foreign Data Wrapper on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing MySQL Foreign Data Wrapper on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -After receiving your repository credentials you can: +- Set up the repository -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -## Creating a repository configuration file + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -To create the repository configuration file, assume superuser privileges, and invoke the following command: +- Address other prerequisites -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Download and install the MYSQL repo: + sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + # Enable the MYSQL repo: + # For MySQL 8: + sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw -## Modifying the file, providing your user name and password + # For MySQL 5: + sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo yum -y install edb-as-mysql-fdw ``` -## Installing MySQL Foreign Data Wrapper - -1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: - - ```text - yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm - ``` - -2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: - - For MySQL 8: - ```text - yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw - ``` - - For MySQL 5: - ```text - yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw - ``` -Where `xx` is the server version number i.e. 13. - -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 `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. - - - +Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_deb10_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_deb10_x86.mdx index c41527769fb..33636441366 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_deb10_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_deb10_x86.mdx @@ -1,54 +1,41 @@ --- navTitle: Debian 10 title: Installing MySQL Foreign Data Wrapper on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - +- Address other prerequisites -# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command: -apt-get remove libmysqlclient-dev + ```shell + # If there is `libmysqlclient-dev` already installed on your system, + # remove it by using the following command: + sudo apt-get remove libmysqlclient-dev -# Enable the MySQL repo: -# For MySQL 8: -sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list -# For MySQL 5: -sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - -# Add the mysql repo key using the following commands: -sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5 - -# Update the repository metadata: -apt-get update -``` + #Enable the MySQL repo: + For MySQL 8: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list + For MySQL 5: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list + ``` ## Install the package ```shell -apt-get install edb-as-mysql-fdw +sudo apt-get -y install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_other_linux8_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_other_linux8_x86.mdx index 86d4ab1ae42..1864245b100 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_other_linux8_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_other_linux8_x86.mdx @@ -1,63 +1,35 @@ --- -title: "Installing MySQL Foreign Data Wrapper on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing MySQL Foreign Data Wrapper on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `PowerTools` repository: - -```text -dnf config-manager --set-enabled PowerTools -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -## Creating a repository configuration file +- Set up the repository -To create the repository configuration file, assume superuser privileges, and invoke the following command: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -## Modifying the file, providing your user name and password +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo dnf -y install edb-as-mysql-fdw ``` -## Installing MySQL Foreign Data Wrapper - -After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: - -```text -dnf install edb-as-mysql8_fdw -``` -Where `xx` is the server version number i.e. 13. - -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 `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. +Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel7_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel7_x86.mdx index 13a5698c7cf..0b255c650a3 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel7_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel7_x86.mdx @@ -1,76 +1,45 @@ --- -title: "Installing MySQL Foreign Data Wrapper on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing MySQL Foreign Data Wrapper on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -Enable the optional, extras, and HA repositories: +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```text -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Set up the repository -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -After receiving your repository credentials you can: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. +- Address other prerequisites -## Creating a repository configuration file + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + # Download and install the MYSQL repo: + sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm -To create the repository configuration file, assume superuser privileges, and invoke the following command: + # Enable the MYSQL repo: + # For MySQL 8: + sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + # For MySQL 5: + sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw + ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. +## Install the package -## Modifying the file, providing your user name and password - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo yum -y install edb-as-mysql-fdw ``` -## Installing MySQL Foreign Data Wrapper - -1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: - - ```text - yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm - ``` - -2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: - - For MySQL 8: - ```text - yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw - ``` - - For MySQL 5: - ```text - yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw - ``` -Where `xx` is the server version number i.e. 13. - -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 `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. - - - +Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel8_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel8_x86.mdx index 12ec03092a3..0c2affb6003 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel8_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel8_x86.mdx @@ -1,64 +1,38 @@ --- -title: "Installing MySQL Foreign Data Wrapper on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing MySQL Foreign Data Wrapper on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - -```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -After receiving your repository credentials you can: +- Set up the repository -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -## Creating a repository configuration file + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -To create the repository configuration file, assume superuser privileges, and invoke the following command: +- Address other prerequisites -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -## Modifying the file, providing your user name and password + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo dnf -y install edb-as-mysql-fdw ``` -## Installing MySQL Foreign Data Wrapper - -After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: - -```text -dnf install edb-as-mysql8_fdw -``` -Where `xx` is the server version number i.e. 13. - -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 `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. +Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles12_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles12_x86.mdx index 971e28546a0..0ded7d09e31 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles12_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles12_x86.mdx @@ -1,53 +1,46 @@ --- navTitle: SLES 12 title: Installing MySQL Foreign Data Wrapper on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + ```shell + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-mysql-fdw +sudo zypper -n install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles15_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles15_x86.mdx index 57515044ab0..20717f6a821 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles15_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles15_x86.mdx @@ -1,52 +1,45 @@ --- navTitle: SLES 15 title: Installing MySQL Foreign Data Wrapper on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Install the MySQL community repository -wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm -rpm --import /etc/RPM-GPG-KEY-mysql-2022 + ```shell + # Install the MySQL community repository + sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm + rpm --import /etc/RPM-GPG-KEY-mysql-2022 -# Enable the MySQL8 repository and disable the MySQL 5 repository -zypper modifyrepo -e mysql80-community -zypper modifyrepo -d mysql57-community + # Enable the MySQL8 repository and disable the MySQL 5 repository + sudo zypper modifyrepo -e mysql80-community + sudo zypper modifyrepo -d mysql57-community -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as-mysql-fdw +sudo zypper -n install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu18_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu18_x86.mdx index 17131ab88ba..cc10fbeedda 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu18_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu18_x86.mdx @@ -1,54 +1,41 @@ --- navTitle: Ubuntu 18.04 title: Installing MySQL Foreign Data Wrapper on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - +- Address other prerequisites -# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command: -apt-get remove libmysqlclient-dev + ```shell + # If there is `libmysqlclient-dev` already installed on your system, + # remove it by using the following command: + sudo apt-get remove libmysqlclient-dev -# Enable the MySQL repo: -# For MySQL 8: -echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list -# For MySQL 5: -echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - -# Add the mysql repo key using the following commands: -apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5 - -# Update the repository metadata: -apt-get update -``` + # Enable the MySQL repo: + # For MySQL 8: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list + # For MySQL 5: + sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list + ``` ## Install the package ```shell -apt-get install edb-as-mysql-fdw +sudo apt-get -y install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu20_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu20_x86.mdx index 343d04b42b2..d357c912fec 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu20_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing MySQL Foreign Data Wrapper on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as-mysql-fdw +sudo apt-get -y install edb-as-mysql-fdw ``` Where `` is the version of EDB Postgres Advanced server and `` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`. diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx index e8b92f17fc1..7f1d186cc3c 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx @@ -1,66 +1,40 @@ --- -title: "Installing EDB OCL Connector on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing EDB OCL Connector on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites -There are two steps to completing an installation: +Before you begin the installation process: -- Setting up the repository -- Installing the package +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -For each step, you must be logged in as superuser. +- Set up the repository -To log in as a superuser: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -```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. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Add your EDB credentials to the edb.repo file: +- Address other prerequisites - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -1. Install the EPEL repository and refresh the cache: + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - ```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 +## Install the package ```shell -dnf -y install edb-oci +sudo dnf -y install edb-oci ``` - - diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx index da01ec3c9cf..3a4bcd0c22b 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx @@ -1,43 +1,36 @@ --- navTitle: SLES 12 title: Installing EDB OCL Connector on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-oci +sudo zypper -n install edb-oci ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx index 3aaea5db420..147cd752478 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx @@ -1,42 +1,35 @@ --- navTitle: SLES 15 title: Installing EDB OCL Connector on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-oci +sudo zypper -n install edb-oci ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx index 4cd8eb64b6f..e8c57bcc5cd 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx @@ -11,9 +11,12 @@ To install EDB OCL Connector, you must have credentials that allow access to the For platform-specific install instructions, see: - Linux x86-64 (amd64): - - [Rocky Linux 8/AlmaLinux 8](x86_amd64/ocl_connector14_rhel_variants8_x86) + - [RHEL 8/OL 8](x86_amd64/ocl_connector14_rhel8_x86) - - [RHEL 7/OL 7](x86_amd64/ocl_connector14_rhel_variants7_x86) + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/ocl_connector14_other_linux8_x86) + + - [RHEL 7/OL 7](x86_amd64/ocl_connector14_rhel7_x86) + - [CentOS 7](x86_amd64/ocl_connector14_centos7_x86) - [SLES 15](x86_amd64/ocl_connector14_sles15_x86) - [SLES 12](x86_amd64/ocl_connector14_sles12_x86) - [Ubuntu 20.04](x86_amd64/ocl_connector14_ubuntu20_x86) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx index 3573b4979c3..84b92df34be 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx @@ -2,8 +2,10 @@ title: "Installing EDB OCL Connector on Linux x86 (amd64)" navTitle: "Intel x86 (amd64)" navigation: -- ocl_connector14_rhel_variants8_x86 -- ocl_connector14_rhel_variants7_x86 +- ocl_connector14_rhel8_x86 +- ocl_connector14_other_linux8_x86 +- ocl_connector14_rhel7_x86 +- ocl_connector14_centos7_x86 - ocl_connector14_sles15_x86 - ocl_connector14_sles12_x86 - ocl_connector14_ubuntu20_x86 @@ -13,9 +15,12 @@ navigation: For operating system-specific install instructions, see: - - [Rocky Linux 8/AlmaLinux 8](ocl_connector14_rhel_variants8_x86) + + - [RHEL 8/OL 8](ocl_connector14_rhel8_x86) - - [RHEL 7/OL 7](ocl_connector14_rhel_variants7_x86) + - [Rocky Linux 8/AlmaLinux 8](ocl_connector14_other_linux8_x86) + - [RHEL 7/OL 8](ocl_connector14_rhel7_x86) + - [RHEL CentOS 7](ocl_connector14_centos7_x86) - [SLES 15](ocl_connector14_sles15_x86) - [SLES 12](ocl_connector14_sles12_x86) - [Ubuntu 20.04](ocl_connector14_ubuntu20_x86) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx new file mode 100644 index 00000000000..c7610d1dbe2 --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx @@ -0,0 +1,33 @@ +--- +navTitle: CentOS 7 +title: Installing EDB OCL Connector on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + + ``` + +## Install the package + +```shell +sudo yum -y install edb-oci +``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx index 0d4777e594a..18b471cbb90 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Debian 10 title: Installing EDB OCL Connector on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-oci -apt-get install edb-oci-dev +sudo apt-get install edb-oci +sudo apt-get install edb-oci-dev ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx new file mode 100644 index 00000000000..d27a17b705a --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx @@ -0,0 +1,35 @@ +--- +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx new file mode 100644 index 00000000000..af622906526 --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx @@ -0,0 +1,33 @@ +--- +navTitle: RHEL 7 or OL 7 +title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` + +## Install the package + +```shell +sudo yum -y install edb-oci +``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx new file mode 100644 index 00000000000..62d6908994e --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx @@ -0,0 +1,38 @@ +--- +navTitle: RHEL 8 or OL 8 +title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants7_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants7_x86.mdx deleted file mode 100644 index 35a2b00075e..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants7_x86.mdx +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: "Installing EDB OCL Connector on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" ---- - - -Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: - -- Install the `epel-release` package: - -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -- The EPEL packages may depend on packages from other repositories. To download the packages, enable the platform-specific repositories: - - - For RHEL 7 - - Enable the optional, extras, and HA repositories: - - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` - - For CentOS 7 - - You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-oci`. - -**Creating a repository configuration file** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing OCL Connector** - -After saving your changes to the configuration file, use the following commands to install the OCL Connector: - -``` -yum install edb-oci - -yum install edb-oci-devel -``` - -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 `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. - diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants8_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants8_x86.mdx deleted file mode 100644 index 4b0af08492b..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel_variants8_x86.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: "Installing EDB OCL Connector on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" ---- - - - - - -Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - -```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-oci`. - -**Creating a repository configuration file** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing OCL Connector** - -After saving your changes to the configuration file, use the below command to install the OCL Connector: - -```text -dnf install edb-oci - -dnf install edb-oci-devel -``` - -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 `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. - diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx index abff489e83d..5be1265d749 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx @@ -1,43 +1,36 @@ --- navTitle: SLES 12 title: Installing EDB OCL Connector on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-oci +sudo zypper -n install edb-oci ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx index 28e2b664ca2..7bcd1294ed5 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx @@ -1,42 +1,35 @@ --- navTitle: SLES 15 title: Installing EDB OCL Connector on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-oci +sudo zypper -n install edb-oci ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx index 14cbb0eb660..3d68231f273 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB OCL Connector on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-oci -apt-get install edb-oci-dev +sudo apt-get install edb-oci +sudo apt-get install edb-oci-dev ``` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx index 9074f106842..4a155790034 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-oci -apt-get install edb-oci-dev +sudo apt-get install edb-oci +sudo apt-get install edb-oci-dev ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx index 7e185f59e33..c068927e330 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx @@ -11,5 +11,6 @@ For operating system-specific install instructions, see: - [RHEL 8](odbc13_rhel8_ppcle) - - [SLES 12](odbc13_sles12_ppcle) - [SLES 15](odbc13_sles15_ppcle) + - [SLES 12](odbc13_sles12_ppcle) + diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx index e1abc054063..bef0c5a20b2 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx @@ -1,65 +1,40 @@ --- -title: "Installing EDB ODBC Connector on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing EDB ODBC Connector on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To log in as a superuser: +- Set up the repository -```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 - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - This creates the /etc/yum.repos.d/edb.repo configuration file. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Add your EDB credentials to the edb.repo file: +- Address other prerequisites - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -1. Install the EPEL repository and refresh the cache: + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - ```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 +## Install the package ```shell -dnf -y install edb-odbc +sudo dnf -y install edb-odbc ``` - - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx index 11dcf318966..2552e11cc75 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx @@ -1,43 +1,36 @@ --- navTitle: SLES 12 title: Installing EDB ODBC Connector on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-odbc +sudo zypper -n install edb-odbc ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx index 07a91a51ff0..93de551134e 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx @@ -1,42 +1,35 @@ --- navTitle: SLES 15 title: Installing EDB ODBC Connector on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-odbc +sudo zypper -n install edb-odbc ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx index beb0d2a075d..99816d19041 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx @@ -1,63 +1,33 @@ --- -title: "Installing EDB ODBC Connector on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing EDB ODBC Connector on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -!!! Note - You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). +- Set up the repository -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -After receiving your repository credentials you can: +- Address other prerequisites -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-odbc`. + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -## Creating a repository configuration file + ``` -To create the repository configuration file, assume superuser privileges, and invoke the following command: +## Install the package -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +```shell +sudo yum -y install edb-odbc ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -## Modifying the file, providing your user name and password - -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -## Installing ODBC Connector - -After saving your changes to the configuration file, use the following command to install the ODBC Connector: - -```text -yum install edb-odbc - -yum install edb-odbc-devel -``` - -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 `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. diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx index 4e8485073b5..02421591633 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Debian 10 title: Installing EDB ODBC Connector on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-odbc -apt-get install edb-odbc-dev +sudo apt-get install edb-odbc +sudo apt-get install edb-odbc-dev ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx index 294c68c0282..6327fe9be39 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx @@ -1,67 +1,35 @@ --- -title: "Installing EDB ODBC Connector on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB ODBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `PowerTools` repository: - -```text -dnf config-manager --set-enabled PowerTools -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-odbc`. - -## Creating a repository configuration file +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To create the repository configuration file, assume superuser privileges, and invoke the following command: +- Set up the repository -```text -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -## Modifying the file, providing your user name and password +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo dnf -y install edb-odbc ``` - -## Installing ODBC Connector - -After saving your changes to the configuration file, use the following command to install the ODBC Connector: - -```text -dnf install edb-odbc - -dnf install edb-odbc-devel -``` - -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 `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. - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx index 4066b9ca010..3ed5633dcbb 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx @@ -1,68 +1,33 @@ --- -title: "Installing EDB ODBC Connector on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing EDB ODBC Connector on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -Enable the optional, extras, and HA repositories: - -```text -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). - +- Set up the repository -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-odbc`. - -## Creating a repository configuration file - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -## Modifying the file, providing your user name and password +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` -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 EDB user. +## Install the package -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +```shell +sudo yum -y install edb-odbc ``` - -## Installing ODBC Connector - -After saving your changes to the configuration file, use the following commands to install the ODBC Connector: - -``` -yum install edb-odbc - -yum install edb-odbc-devel -``` - -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 `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. - - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx index 8974f1627c5..7343c0e578f 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx @@ -1,67 +1,38 @@ --- -title: "Installing EDB ODBC Connector on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB ODBC Connector on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: +## Prerequisites -Install the `epel-release` package: +Before you begin the installation process: -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - -```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install `edb-odbc`. +- Set up the repository -## Creating a repository configuration file + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -To create the repository configuration file, assume superuser privileges, and invoke the following command: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. +- Address other prerequisites -## Modifying the file, providing your user name and password + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -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 EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -## Installing ODBC Connector + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -After saving your changes to the configuration file, use the below command to install the ODBC Connector: +## Install the package -```text -dnf install edb-odbc - -dnf install edb-odbc-devel +```shell +sudo dnf -y install edb-odbc ``` - -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 `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. diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx index cdadf0ebf8f..7bda3391ea0 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx @@ -1,43 +1,36 @@ --- navTitle: SLES 12 title: Installing EDB ODBC Connector on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-odbc +sudo zypper -n install edb-odbc ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx index 57a7771891d..0fe9e0be66b 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx @@ -1,42 +1,35 @@ --- navTitle: SLES 15 title: Installing EDB ODBC Connector on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-odbc +sudo zypper -n install edb-odbc ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx index afd510a4db1..9dff1e17a1e 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB ODBC Connector on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-odbc -apt-get install edb-odbc-dev +sudo apt-get install edb-odbc +sudo apt-get install edb-odbc-dev ``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx index 251c9e17e69..1262f656fd0 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx @@ -1,41 +1,26 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB ODBC Connector on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-odbc -apt-get install edb-odbc-dev +sudo apt-get install edb-odbc +sudo apt-get install edb-odbc-dev ``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx index 54e717eabe1..a1a11461529 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx @@ -1,33 +1,25 @@ --- navTitle: RHEL 8 title: Installing Postgres Enterprise Manager agent on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` +## Prerequisites +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem-agent +sudo dnf -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle.mdx index c8017ce2a8a..04013bec152 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle.mdx @@ -1,45 +1,36 @@ --- navTitle: SLES 12 title: Installing Postgres Enterprise Manager agent on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem-agent +sudo zypper -n install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles15_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles15_ppcle.mdx index e37d33ea226..a003a5d179e 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles15_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles15_ppcle.mdx @@ -1,44 +1,35 @@ --- navTitle: SLES 15 title: Installing Postgres Enterprise Manager agent on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem-agent +sudo zypper -n install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx index c945bf2df33..3cd92456428 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx @@ -1,32 +1,25 @@ --- navTitle: CentOS 7 title: Installing Postgres Enterprise Manager agent on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -yum -y install edb-pem-agent +sudo yum -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86.mdx index c5558adeba0..85251cfc635 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86.mdx @@ -1,42 +1,25 @@ --- navTitle: Debian 10 title: Installing Postgres Enterprise Manager agent on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem-agent +sudo apt-get -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx index 613e2b2f042..9ba8757bb05 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx @@ -1,33 +1,25 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing Postgres Enterprise Manager agent on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites -Before you begin the installation process, log in as superuser. +Before you begin the installation process: -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem-agent +sudo dnf -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx index 9f348185f2f..f6923a3af01 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx @@ -1,34 +1,25 @@ --- navTitle: RHEL 7 or OL 7 title: Installing Postgres Enterprise Manager agent on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites -Before you begin the installation process, log in as superuser. +Before you begin the installation process: -```shell -# To log in as a superuser: -sudo su - -``` +- Set up the repository -## Set 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 this step. -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -yum -y install edb-pem-agent +sudo yum -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). - diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx index b433f43ada0..cd3d8afe108 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx @@ -1,34 +1,25 @@ --- navTitle: RHEL 8 or OL 8 title: Installing Postgres Enterprise Manager agent on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites -Before you begin the installation process, log in as superuser. +Before you begin the installation process: -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem-agent +sudo dnf -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86.mdx index fc8de210fb2..3d0fffb851c 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86.mdx @@ -1,45 +1,36 @@ --- navTitle: SLES 12 title: Installing Postgres Enterprise Manager agent on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem-agent +sudo zypper -n install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles15_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles15_x86.mdx index 10c48d6ebd4..45d81e3d1f2 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles15_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles15_x86.mdx @@ -1,44 +1,35 @@ --- navTitle: SLES 15 title: Installing Postgres Enterprise Manager agent on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Set 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 this step. If you do need to set up the repository, you must 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 is a one-time task. If you have already set up your repository, you do not need to perform this step. -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect +- Address other prerequisites -# 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' + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 - -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem-agent +sudo zypper -n install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu18_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu18_x86.mdx index f9c8c968c5a..b6cd2206c44 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu18_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu18_x86.mdx @@ -1,42 +1,25 @@ --- navTitle: Ubuntu 18.04 title: Installing Postgres Enterprise Manager agent on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem-agent +sudo apt-get -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu20_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu20_x86.mdx index 24fb2df363b..126942cdc87 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu20_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_ubuntu20_x86.mdx @@ -1,42 +1,25 @@ --- navTitle: Ubuntu 20.04 title: Installing Postgres Enterprise Manager agent on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process: -```shell -# Set up the EDB repository -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 - -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Set up the repository -# Add support for secure APT repositories: -apt-get -y install apt-transport-https + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem-agent +sudo apt-get -y install edb-pem-agent ``` After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx index c2640ef4e89..1baea81e418 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx @@ -1,47 +1,38 @@ --- navTitle: RHEL 8 title: Installing Postgres Enterprise Manager server on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: - -```shell -sudo su - -``` +## Prerequisites +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem +sudo dnf -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note - - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx index 9a337d65d76..296d763a875 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx @@ -1,58 +1,49 @@ --- navTitle: SLES 12 title: Installing Postgres Enterprise Manager server on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem +sudo zypper -n install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx index dd996675ec7..979879920b1 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx @@ -1,57 +1,48 @@ --- navTitle: SLES 15 title: Installing Postgres Enterprise Manager server on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem +sudo zypper -n install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx index fbe1f476d4c..b06a0a90449 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx @@ -1,52 +1,42 @@ --- navTitle: CentOS 7 title: Installing Postgres Enterprise Manager server on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -2. Log in as superuser: +- Set up the repository -```shell -sudo su - -``` - -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -yum -y install edb-pem +sudo yum -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). - +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. - + - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. - - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. \ No newline at end of file + - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx index 340684683e2..3662f1c0fd7 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx @@ -1,55 +1,38 @@ --- navTitle: Debian 10 title: Installing Postgres Enterprise Manager server on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: - -```shell -sudo su - -``` +## Prerequisites -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +Before you begin the installation process: -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -# Add support for secure APT repositories: -apt-get -y install apt-transport-https +- Set up the repository -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem +sudo apt-get -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx index c301340b49f..8212cd6447a 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing Postgres Enterprise Manager server on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem +sudo dnf -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx index b3e0899624f..b15342dfecf 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx @@ -1,48 +1,40 @@ --- navTitle: RHEL 7 or OL 7 title: Installing Postgres Enterprise Manager server on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: - -```shell -sudo su - -``` +## Prerequisites -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -yum -y install edb-pem +sudo yum -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx index a0799d618bd..2b5b373e2a6 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx @@ -1,46 +1,38 @@ --- navTitle: RHEL 8 or OL 8 title: Installing Postgres Enterprise Manager server on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -dnf -y install edb-pem +sudo dnf -y install edb-pem ``` - ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx index b7337a9000c..1d503eb937f 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx @@ -1,58 +1,49 @@ --- navTitle: SLES 12 title: Installing Postgres Enterprise Manager server on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem +sudo zypper -n install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx index c5bc25a9a99..96d77f83f99 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx @@ -1,57 +1,48 @@ --- navTitle: SLES 15 title: Installing Postgres Enterprise Manager server on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: +## Prerequisites -```shell -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pem +sudo zypper -n install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx index c641149abf5..e69fbf5a0b3 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx @@ -1,55 +1,38 @@ --- navTitle: Ubuntu 18.04 title: Installing Postgres Enterprise Manager server on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: - -```shell -sudo su - -``` +## Prerequisites -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +Before you begin the installation process: -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -# Add support for secure APT repositories: -apt-get -y install apt-transport-https +- Set up the repository -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem +sudo apt-get -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx index d1d4dd7ce5d..dc2d5ceaefd 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx @@ -1,55 +1,38 @@ --- navTitle: Ubuntu 20.04 title: Installing Postgres Enterprise Manager server on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process: - -1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - -2. Log in as superuser: - -```shell -sudo su - -``` +## Prerequisites -## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +Before you begin the installation process: -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf +- Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -# Add support for secure APT repositories: -apt-get -y install apt-transport-https +- Set up the repository -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pem +sudo apt-get -y install edb-pem ``` ## Initial configuration ```shell # You can configure the PEM server using the following command: -/usr/edb/pem/bin/configure-pem-server.sh +sudo /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). !!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/prerequisites.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/prerequisites.mdx index c56d5b605c8..6fc1f88f3d8 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/prerequisites.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/prerequisites.mdx @@ -59,7 +59,7 @@ Postres Enterprise Manager requires a Postgres server running either [EDB Postgr 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: + For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: ```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp @@ -67,11 +67,12 @@ Postres Enterprise Manager requires a Postgres server running either [EDB Postgr firewall-cmd --reload ``` - For Debian/Ubuntu: + For Debian/Ubuntu: ```shell iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT ``` + Make sure the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: For RHEL/AlmaLinux/Rocky Linux 8: diff --git a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/using_sql_profiler.mdx b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/using_sql_profiler.mdx index 219477e7af6..92fcc793374 100644 --- a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/using_sql_profiler.mdx +++ b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/using_sql_profiler.mdx @@ -29,7 +29,7 @@ For each database monitored by SQL Profiler: 3. Stop and restart the server to make the changes to take effect. !!! Note - If you connected to the PEM server with the PEM client before configuring SQL Profiler, you must disconnect and reconnect with the server to enable SQL Profiler functionality. For detailed information about installing and configuring the SQL Profiler plugin, see [Installing SQL Profiler](installing_the_sql_profiler_plugin/). + If you connected to the PEM server with the PEM client before configuring SQL Profiler, you must disconnect and reconnect with the server to enable SQL Profiler functionality. For detailed information about installing and configuring the SQL Profiler plugin, see [Installing SQL Profiler](installing_the_sql_profiler_plugin/). ## Creating a new SQL trace diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel8_ppcle.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel8_ppcle.mdx index 909eb4abe91..478f4560c5c 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel8_ppcle.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_rhel8_ppcle.mdx @@ -1,64 +1,42 @@ --- -title: "Installing EDB PgBouncer on RHEL 8 ppc64le" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing EDB pgBouncer on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To log in as a superuser: +- Set up the repository -```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 - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - This creates the /etc/yum.repos.d/edb.repo configuration file. + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -1. Add your EDB credentials to the edb.repo file: +- Address other prerequisites - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - Where `USERNAME:PASSWORD` is the username and password available from your - [EDB account](https://www.enterprisedb.com/user). + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -1. Install the EPEL repository and refresh the cache: + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - ```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 +## Install the package ```shell -dnf -y install edb-pgbouncer +sudo dnf -y install edb-pgbouncer ``` -where `` is the EDB PgBouncer version you want to install. \ No newline at end of file + +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle.mdx index 798963f654c..ad2acacb237 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB pgBouncer on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgbouncer +sudo zypper -n install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles15_ppcle.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles15_ppcle.mdx index 9d9c4c2cf7f..35046d5460e 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles15_ppcle.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB pgBouncer on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgbouncer +sudo zypper -n install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86.mdx index 1279927a134..8f5d562b45a 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86.mdx @@ -1,35 +1,35 @@ --- -title: "Installing EDB PgBouncer on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing EDB pgBouncer on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Follow the steps given below to install EDB PgBouncer: +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges and invoke the following command: - ``` text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` in the following command with the username and password of a registered EnterpriseDB user: +- Set up the repository - ``` text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -3. Before installing EDB PgBouncer, install the Extra Packages for Enterprise Linux (EPEL) release package: - ``` text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -6. Install EDB PgBouncer: - ``` text - yum -y install edb-pgbouncer - ``` +- Address other prerequisites - Where <xx> is the EDB PgBouncer version you want to install. + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - 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 `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. EDB PgBouncer will be installed in the `/usr/edb/pgbouncer` directory. +## Install the package + +```shell +sudo yum -y install edb-pgbouncer +``` + +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86.mdx index 1af77e783c4..d14bd825ca2 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing EDB pgBouncer on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgbouncer +sudo apt-get -y install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux8_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux8_x86.mdx index 1344242ea80..bc393d3f8de 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux8_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_other_linux8_x86.mdx @@ -1,45 +1,37 @@ --- -title: "Installing EDB PgBouncer on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB pgBouncer on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites -Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +Before you begin the installation process: -Follow the steps given below to install EDB PgBouncer: +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -1. To install the repository configuration, assume superuser privileges and invoke the following command: - ``` text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Set up the repository -2. Replace the `USERNAME:PASSWORD` in the following command with the username and password of a registered EnterpriseDB user: - ``` text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -3. Before installing EDB PgBouncer, install the Extra Packages for Enterprise Linux (EPEL) release package: - ``` text - dnf -y install epel-release - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -4. Enable the PowerTools repository to satisfy EPEL package dependencies: - ``` text - dnf config-manager --set-enabled PowerTools - ``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -5. Disable the built-in PostgreSQL module: - ``` text - dnf -qy module disable postgresql - ``` +## Install the package -6. Install EDB PgBouncer: - ``` text - dnf -y install edb-pgbouncer - ``` +```shell +sudo dnf -y install edb-pgbouncer +``` - Where <xx> is the EDB PgBouncer version you want to install. - - 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 `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. EDB PgBouncer will be installed in the `/usr/edb/pgbouncer` directory. +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86.mdx index 251c543005e..026421632b3 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86.mdx @@ -1,41 +1,35 @@ --- -title: "Installing EDB PgBouncer on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing EDB pgBouncer on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Follow the steps given below to install EDB PgBouncer: +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges and invoke the following command: - ``` text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` in the following command with the username and password of a registered EnterpriseDB user: +- Set up the repository - ``` text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -3. Before installing EDB PgBouncer, install the Extra Packages for Enterprise Linux (EPEL) release package: - ``` text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -4. Enable the `optional, extras`, and `HA` repositories to satisfy EPEL package dependencies: +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` - ``` text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` - -5. Install EDB PgBouncer: - ``` text - yum -y install edb-pgbouncer - ``` +## Install the package - Where <xx> is the EDB PgBouncer version you want to install. - - 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 `y`, and press `Return` to continue. +```shell +sudo yum -y install edb-pgbouncer +``` - 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. EDB PgBouncer will be installed in the `/usr/edb/pgbouncer` directory. +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel8_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel8_x86.mdx index 5b146aa715f..d660cf1d7b6 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel8_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel8_x86.mdx @@ -1,53 +1,40 @@ --- -title: "Installing EDB PgBouncer on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB pgBouncer on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Follow the steps given below to install EDB PgBouncer: +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges and invoke the following command: - ``` text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` in the following command with the username and password of a registered EnterpriseDB user: +- Set up the repository - ``` text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -3. Before installing EDB PgBouncer, execute the following command to install the Extra Packages for Enterprise Linux (EPEL) release package: - ``` text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -4. Enable the the `codeready-builder-for-rhel-8-*-rpms` repository to satisfy EPEL packages dependency: - ``` text - ARCH=$( /bin/arch ) +- Address other prerequisites - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -5. Disable the built-in PostgreSQL module: - ``` text - dnf -qy module disable postgresql - ``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -6. Use the following platform-specific command to install EDB PgBouncer: - ``` text - dnf -y install edb-pgbouncer - ``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - Where <xx> is the EDB PgBouncer version you want to install. +## Install the package - To install EDB PgBouncer 1.16 on RHEL 8, the command is: +```shell +sudo dnf -y install edb-pgbouncer +``` - ``` text - dnf -y install edb-pgbouncer116 - ``` - - 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 `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. EDB PgBouncer will be installed in the `/usr/edb/pgbouncer` directory. \ No newline at end of file +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86.mdx index f202268efa5..6ac35dab415 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB pgBouncer on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgbouncer +sudo zypper -n install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles15_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles15_x86.mdx index 07914e80604..fbcc9f3a9e0 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles15_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB pgBouncer on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgbouncer +sudo zypper -n install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu18_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu18_x86.mdx index 699a6b17f4c..9fa9f1bbf3c 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu18_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB pgBouncer on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgbouncer +sudo apt-get -y install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu20_x86.mdx b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu20_x86.mdx index c4a25c04315..b3d53158493 100644 --- a/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu20_x86.mdx +++ b/product_docs/docs/pgbouncer/1.17/01_installation/install_on_linux/x86_amd64/pgbouncer_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB pgBouncer on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgbouncer +sudo apt-get -y install edb-pgbouncer ``` Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.16, the package name would be `edb-pgbouncer116`. diff --git a/product_docs/docs/pgd/3.6/bdr/index.mdx b/product_docs/docs/pgd/3.6/bdr/index.mdx deleted file mode 100644 index 8cbebe8249b..00000000000 --- a/product_docs/docs/pgd/3.6/bdr/index.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -navTitle: BDR -title: "BDR (Bi-Directional Replication)" -directoryDefaults: - description: "BDR (Bi-Directional Replication) is a ground-breaking multi-master replication capability for PostgreSQL clusters that has been in full production status since 2014." ---- - -**BDR (Bi-Directional Replication)** is a ground-breaking multi-master replication capability for PostgreSQL clusters that has been in full production status since 2014. In the complex environment of replication, this 3rd generation of BDR achieves efficiency and accuracy, enabling very high availability of all nodes in a geographically distributed cluster. This solution is for top-tier enterprise applications that require near-zero downtime and near-zero data loss. - -As a standard PostgreSQL extension BDR does this through logical replication of data and schema along with a robust set of features and tooling to manage conflicts and monitor performance. This means applications with the most stringent demands can be run with confidence on PostgreSQL. - -BDR was built from the start to allow for rolling upgrades and developed in conjunction with partners who were replacing costly legacy solutions. - -Available as two editions, BDR Standard provides essential multi-master replication capabilities for delivering row level consistency to address high availability and/or geographically distributed workloads. BDR Enterprise adds advanced conflict-handling and data-loss protection capabilities. - -## BDR Enterprise - -To provide very high availability, avoid data conflicts, and to cope with more advanced usage scenarios, the Enterprise edition provides the following extensive additional features: - -* Eager replication provides conflict free replication by synchronizing across cluster nodes before committing a transaction -* Commit at most once consistency guards application transactions even in the presence of node failures -* Conflict-free replicated data types (CRDTs) provide mathematically proven consistency in asynchronous multi-master update scenarios -* Column level conflict resolution enables per column last-update wins resolution to merge updates -* Transform triggers execute on incoming data for modifying or advanced programmatic filtering -* Conflict triggers provide custom resolution techniques when a conflict is detected - -BDR Enterprise requires EDB Postgres Extended v11 (formerly known as 2ndQuadrant Postgres) which is SQL and on-disk compatible with PostgreSQL. - -!!!note - The documentation for the latest stable 3.6 release is available here: - - [BDR 3.6 Enterprise Edition](https://documentation.enterprisedb.com/bdr3-enterprise/release/latest-3.6/) - - **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)** -!!! - -## BDR Standard - -The Standard edition provides loosely-coupled multi-master logical replication using a mesh topology. This means that you can write to any node and the changes will be sent directly, row-by-row to all the other nodes that are part of the EDB Postgres Distributed cluster. - -By default BDR uses asynchronous replication to provide row-level eventual consistency, applying changes on the peer nodes only after the local commit. - -The following are included to support very high availability and geographically distributed workloads: - -* Rolling application and database upgrades to address the largest source of downtime -* DDL replication supports changes to application schema, ideal for use in continuous release environments -* Sequence handling provides applications different options for generating unique surrogate ids that a multi-node aware -* Tools to assess applications, monitor operation, and verify data consistency - -BDR Standard requires PostgreSQL v10 or v11. - -!!!note - The documentation for the latest stable 3.6 release is available here: - - [BDR 3.6 Standard Edition](https://documentation.enterprisedb.com/bdr3/release/latest-3.6/) - - **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)** -!!! - - diff --git a/product_docs/docs/pgd/3.6/index.mdx b/product_docs/docs/pgd/3.6/index.mdx index cbb3984e3e5..b7b68172069 100644 --- a/product_docs/docs/pgd/3.6/index.mdx +++ b/product_docs/docs/pgd/3.6/index.mdx @@ -21,16 +21,70 @@ What Postgres distribution and version is right for you depends on the features See the feature matrix in [Choosing a Postgres distribution](/pgd/latest/choosing_server) for detailed comparison. -## [BDR](bdr) +## BDR -A Postgres server with the [BDR](bdr) extension installed is referred to as a BDR +A Postgres server with the BDR extension installed is referred to as a BDR node. BDR nodes can be either data nodes or witness nodes. Witness nodes don't participate in data replication and are only used as a tie-breaker for consensus. +Available as two editions, BDR Standard provides essential multi-master replication capabilities for delivering row level consistency to address high availability and/or geographically distributed workloads. BDR Enterprise adds advanced conflict-handling and data-loss protection capabilities. -## [pglogical 3](pglogical) +### BDR Enterprise -BDR depends on [pglogical 3](pglogical) to provide the replication +To provide very high availability, avoid data conflicts, and to cope with more advanced usage scenarios, the Enterprise edition provides the following extensive additional features: + +* Eager replication provides conflict free replication by synchronizing across cluster nodes before committing a transaction +* Commit at most once consistency guards application transactions even in the presence of node failures +* Conflict-free replicated data types (CRDTs) provide mathematically proven consistency in asynchronous multi-master update scenarios +* Column level conflict resolution enables per column last-update wins resolution to merge updates +* Transform triggers execute on incoming data for modifying or advanced programmatic filtering +* Conflict triggers provide custom resolution techniques when a conflict is detected + +BDR Enterprise requires EDB Postgres Extended v11 (formerly known as 2ndQuadrant Postgres) which is SQL and on-disk compatible with PostgreSQL. + +!!!note + The documentation for the latest stable 3.6 release is available here: + + [BDR 3.6 Enterprise Edition](https://documentation.enterprisedb.com/bdr3-enterprise/release/latest-3.6/) + + **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)** +!!! + +### BDR Standard + +The Standard edition provides loosely-coupled multi-master logical replication using a mesh topology. This means that you can write to any node and the changes will be sent directly, row-by-row to all the other nodes that are part of the EDB Postgres Distributed cluster. + +By default BDR uses asynchronous replication to provide row-level eventual consistency, applying changes on the peer nodes only after the local commit. + +The following are included to support very high availability and geographically distributed workloads: + +* Rolling application and database upgrades to address the largest source of downtime +* DDL replication supports changes to application schema, ideal for use in continuous release environments +* Sequence handling provides applications different options for generating unique surrogate ids that a multi-node aware +* Tools to assess applications, monitor operation, and verify data consistency + +BDR Standard requires PostgreSQL v10 or v11. + +!!!note + The documentation for the latest stable 3.6 release is available here: + + [BDR 3.6 Standard Edition](https://documentation.enterprisedb.com/bdr3/release/latest-3.6/) + + **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)** +!!! + +## pglogical 3.6 + +BDR depends on the pglogical 3 extension to provide the replication channel upon which BDR builds. + + +!!!note + The documentation for the latest stable 3.6 release is available here: + + [pglogical 3.6](https://documentation.enterprisedb.com/pglogical3/release/latest-3.6/) + + **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)** +!!! diff --git a/product_docs/docs/pgd/3.6/pglogical/configuration.mdx b/product_docs/docs/pgd/3.6/pglogical/configuration.mdx deleted file mode 100644 index 5b3f2027dc2..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/configuration.mdx +++ /dev/null @@ -1,314 +0,0 @@ ---- -navTitle: PostgreSQL Configuration -title: PostgreSQL settings which affect pglogical -originalFilePath: configuration.md - ---- - -Several PostgreSQL configuration options may need adjusting for pglogical -to work. - -PostgreSQL must be configured for logical replication: - -``` -wal_level = 'logical' -``` - -The pglogical library need to be loaded at server start, so the parameter -`shared_preload_libraries` must contain pglogical, e.g.: - -``` -shared_preload_libraries = 'pglogical' -``` - -As pglogical uses additional worker processes to maintain state and apply -the replicated changes, enough worker process slots need to be present: - -``` -max_worker_processes = 10 -``` - -The formula for computing the correct value of `max_worker_processes` is: -one for instance + one per database on the provider (upstream), one for instance - -- one per database + two per subscription on the subscriber (downstream). - -The replication slots and origins are used so enough slots for those need -to exist; both replication slots and origins are controlled by same -configuration option: - -``` -max_replication_slots = 10 -``` - -One per subscription on both provider and subscriber is needed. - -The replication data is sent using walsender (just like physical replication): - -``` -max_wal_senders = 10 -``` - -There is one walsender needed for every subscriber (on top of any standbys -or backup streaming connections). - -If you are using PostgreSQL 9.5+ (this won't work on 9.4) and want to handle -conflict resolution with last/first update wins (see [pglogical writer](pglogical-writer)), -you can add this additional option to postgresql.conf: - -``` -track_commit_timestamp = on -``` - -Also `pg_hba.conf` has to allow replication connections from the subscribers. - -## pglogical specific settings - -There are additional pglogical specific configuration options. Some generic -options are mentioned below, but most of the configuration options depend on -which [writer](subscriptions) is used and are documented as part of the -individual [writer](subscriptions) documentation. - -### `pglogical.synchronous_commit` - -This controls whether pglogical apply worker should use synchronous commit. By -default this is off. Turning it on has performance implications - the maximum -replication throughput will be much lower. However in low TPS environments which -use `synchronous_commit = remote_apply` on the provider, turning this option on -can improve the transaction latency. This guidance may change in later releases. - -The pglogical.synchronous_commit setting for a subscription determines what -happens to the things that the subscription's apply worker writes -locally. The subscription's apply worker operates much like a normal -client backend, and whatever it writes and commits is subject to its -current pglogical.synchronous_commit setting. - -In most cases, pglogical.synchronous_commit off is the best setting because it -avoids the flushing work at commit time, and it is safe because in case -of a crash the data can be re-obtained from the publishing server. - -But if you use synchronous replication on the publishing server, then -the publishing server will wait for the subscribing server to send -feedback messages when the sent data has been flushed to disk on the -subscribing server (depending on the particular setting). If the -subscriber has pglogical.synchronous_commit off, then the flushing happens at some -random later time, and then the upstream publisher has to wait for that -to happen. In order to speed that up, you need to make the subscriber -flush stuff faster, and the way to do that is to set pglogical.synchronous_commit -to a value other than off on the subscriber. - -Also if you have standbys connected to this subscriber server then you can set the -value of pglogical.synchronous_commit to wait for confirmation from its standbys. - -**NOTE** As per design, if on, this configuration will always wait for the local -flush confirmation, even if the `synchronous_standby_names` would point to any -physical standby/s. - -The default is off. - -### `pglogical.track_subscription_apply` - -This controls whether to track per subscription apply statistics. If this is on, the -`pglogical.stat_subscription` view will contain performance statistics for -each subscription which has received any data, otherwise the view is empty. - -Collecting statistics requires additional CPU resources on the subscriber. - -The default is on. - -### `pglogical.track_relation_apply` - -This controls whether to track per table apply statistics. If this is on, the -`pglogical.stat_relation` view will contain performance statistics for -each subscribed relation which has received any data, otherwise the view is -empty. - -Collecting statistics requires additional CPU resources on the subscriber. - -The default is off. - -### `pglogical.track_apply_lock_timing` - -This tracks lock timing when tracking statistics for relations. - -The default is off. - -### `pglogical.temp_directory` - -This defines system path for where to put temporary files needed for schema -synchronization. This path needs to exist and be writeable by users running -Postgres. - -The default is empty, which tells pglogical to use the default temporary -directory based on environment and operating system settings. - -### `pglogical.extra_connection_options` - -This option may be set to assign connection options that apply to all -connections made by pglogical. This can be a useful -place to set up custom keepalive options, etc. - -pglogical defaults to enabling TCP keepalives to ensure that it notices -when the upstream server disappears unexpectedly. To disable them, add -`keepalives = 0` to `pglogical.extra_connection_options`. - -### `pglogical.synchronize_failover_slot_names` - -This standby option allows setting which logical slots should be synchronized -to this physical standby. It's comma separated list of slot filters. - -Slot filter is defined as `key:value` pair (separated by colon) where `key` -can be one of: - -- `name` - specifies to match exact slot name -- `name_like` - specifies to match slot name against SQL `LIKE` expression -- `plugin` - specifies to match slot plugin name agains the value - -The `key` can be omitted and will default to `name` in that case. - -For example `'my_slot_name,plugin:pglogical_output,plugin:pglogical'` will -synchronize slot named "my_slot_name" and any pglogical slots. - -If this is set to empty string, no slots will be synchronized to this physical -standby. - -Default value is `'plugin:pglogical,plugin:pglogical_output'` meaning pglogical -slots will be synchronized. - -### `pglogical.synchronize_failover_slots_drop` - -This standby option controls what happens to extra slots on standby that are -not found on primary using pglogical.synchronize_failover_slot_names filter. -If it's set to true, they will be dropped, otherwise they will be kept. - -The default value is `true`. - -### `pglogical.synchronize_failover_slots_dsn` - -A standby option for specifying which connection string to use to connect to -primary when fetching slot information. - -If empty (and default) is to use same connection string as `primary_conninfo`. - -Note that `primary_conninfo` cannot be used if there is a `password` field in -the connection string because it gets obfuscated by PostgreSQL and pglogical -can't actually see the password. In this case the -`pglogical.synchronize_failover_slots_dsn` must be used. - -### `pglogical.standby_slot_names` - -This option is typically used in failover configurations to ensure that the -failover-candidate streaming physical replica(s) for this pglogical provider -have received and flushed all changes before they ever become visible to any -subscribers. That guarantees that a commit cannot vanish on failover to a -standby for the provider. - -Replication slots whose names are listed in the comma-separated -`pglogical.standby_slot_names` list are treated specially by the walsender -on a pglogical provider. - -pglogical's logical replication walsenders will ensure that all local changes -are sent and flushed to the replication slots in `pglogical.standby_slot_names` -before the provider sends those changes to any other pglogical replication -clients. Effectively it provides a synchronous replication barrier between the -named list of slots and all pglogical replication clients. - -Any replication slot may be listed in `pglogical.standby_slot_names`; both -logical and physical slots work, but it's generally used for physical slots. - -Without this safeguard, two anomalies are possible where a commit can be -received by a subscriber then vanish from the provider on failover because -the failover candidate hadn't received it yet: - -- For 1+ subscribers, the subscriber may have applied the change but the new - provider may execute new transactions that conflict with the received change, - as it never happened as far as the provider is concerned; - -and/or - -- For 2+ subscribers, at the time of failover, not all subscribers have applied - the change.The subscribers now have inconsistent and irreconcilable states - because the subscribers that didn't receive the commit have no way to get it - now. - -Setting `pglogical.standby_slot_names` will (by design) cause subscribers to -lag behind the provider if the provider's failover-candidate replica(s) are not -keeping up. Monitoring is thus essential. - -Note that this setting is generally not required for BDR3 nodes (which are -based on pglogical). Unlike base pglogical3, BDR3 is capable of reconciling -lost changes from surviving peer nodes. - -### `pglogical.standby_slots_min_confirmed` - -Controls how many of the `pglogical.standby_slot_names` have to confirm before -we send data to pglogical subscribers. - -### `pglogical.writer_input_queue_size` - -This option is used to specify the size of the shared memory queue used -by the receiver to send data to the writer process. If the writer process is -stalled or making slow progress, then the queue might get filled up, stalling -the receiver process too. So it's important to provide enough shared memory for -this queue. The default is 1MB and the maximum allowed size is 1GB. While any -storage size specifier can be used to set the GUC, the default is kB. - -### `pglogical.writer_output_queue_size` - -This option is used to specify the size of the shared memory queue used -by the receiver to receive data from the writer process. Since the writer is -not expected to send a large amount of data, a relatively smaller sized queue -should be enough. The default is 32kB and the maximum allowed size is 1MB. -While any storage size specifier can be used to set the GUC, the default is -kB. - -### `pglogical.min_worker_backoff_delay` and `pglogical.max_worker_backoff_delay` - -Rate limit pglogical background worker launches by preventing a given worker -from being relaunched more often than every -`pglogical.min_worker_backoff_delay` milliseconds. On repeated errors, the back-off -increases exponentially with added jitter up to maximum of -`pglogical.max_worker_backoff_delay`. - -Time-unit suffixes are supported. - -!!! Note - This setting currently only affects receiver worker, which means it - primarily affects how fast a subscription will try to reconnect on error - or connection failure. - -The default for `pglogical.min_worker_backoff_delay` is 1 second, for -`pglogical.max_worker_backoff_delay` it is 1 minute. - -If the backoff delay setting is changed and the PostgreSQL configuration is -reloaded then all current backoff waits will be reset. Additionally, the -`pglogical.worker_task_reset_backoff_all()` function is provided to allow the -administrator to force all backoff intervals to immediately expire. - -A tracking table in shared memory is maintained to remember the last launch -time of each type of worker. This tracking table is not persistent; it is -cleared by PostgreSQL restarts, including soft-restarts during crash recovery -after an unclean backend exit. - -The view [`pglogical.worker_tasks`](troubleshooting#pglogical.worker_tasks) -may be used to inspect this state so the administrator can see any backoff -rate-limiting currently in effect. - -For rate limiting purposes, workers are classified by "task". This key consists -of the worker role, database oid, subscription id, subscription writer id, -extension library name and function name, extension-supplied worker name, and -the remote relation id for sync writers. `NULL` is used where a given -classifier does not apply, e.g. manager workers don't have a subscription ID -and receivers don't have a writer id. - -### `pglogical.max_writers_per_subscription` - -Specifies the maximum number of parallel writers that a subscription may use. -Values between 1 and 64 are allowed, with the default being 8. When set to 1, -parallel apply is effectively disabled. - -### `pglogical.writers_per_subscription` - -Sets the default number of parallel writers for subscriptions without an -explicitly set value. Values between 1 and 64 are allowed, with the default -being 4. diff --git a/product_docs/docs/pgd/3.6/pglogical/ddl.mdx b/product_docs/docs/pgd/3.6/pglogical/ddl.mdx deleted file mode 100644 index 4d20c0682bf..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/ddl.mdx +++ /dev/null @@ -1,263 +0,0 @@ ---- -title: DDL Replication -originalFilePath: ddl.md - ---- - -pglogical3 supports *transparent DDL replication*, where schema change commands -run on provider node(s) are automatically captured and replicated to subscriber -node(s) without the need for wrapper functions like -`pglogical.replicate_ddl_command` or external schema management tools. - -The main difference from normal replication of table rows ("table replication") -is that DDL replication replicates statements themselves rather than the -effects of those statements. Normal data replication replicates the changes -made by a statement, e.g. it sends the rows that got `UPDATE`d by an `UPDATE` -command rather than replicating and executing the `UPDATE` statement itself. -pglogical's DDL replication captures, replicates and executes *the text of the -DDL statement itself*. - -## Minimal example - -Enabling DDL replication on a pglogical provider can be as simple as: - -```sql -SELECT * FROM pglogical.replication_set_add_ddl('ddl_sql', 'all', NULL, NULL); -``` - -to replicate any captureable DDL statements executed by any user on the -provider database to any subscriber(s) that subscribe to the enabled-by-default -`ddl_sql` replication set. - -However it's generally *recommended* to enable replication of a targeted subset -of DDL instead. - -There are also caveats relating to replication of changes to "global objects" -like roles, the handling of some `ALTER TABLE` modes, etc that are important to -understand. See ["Restrictions"](#Restrictions) below. - -## How to use DDL replication - -Transparent DDL replication in pglogical builds on the same [Replication -Sets](replication-sets) model that's used by replication of table contents. -The same replication set(s) may be used for both replicating table contents -and for DDL. - -To replicate future DDL commands on a provider, a DDL replication filter must -be added to the replication set(s) used by subscribers that should receive -and apply the DDL. - -The DDL filter can specify a `command_tag` and `role_name` to allow -replication of only some DDL statements. The `command_tag` is same as those -used by [EVENT TRIGGERs](https://www.postgresql.org/docs/current/static/event-trigger-matrix.html). -The `role_name` is used for matching against the current role which is executing the -command. Both `command_tag` and `role_name` are evaluated as regular expressions -which are case sensitive. - -## Functions for managing DDL replication filters - -The following functions are provided for managing DDL replication filters using -replication sets: - -### pglogical.replication_set_add_ddl - -Adds a DDL replication filter to a replication set. - -#### Synopsis - -```sql -pglogical.replication_set_add_ddl ( - set_name name, - ddl_filter_name text, - command_tag text, - role_name text -) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `ddl_filter_name` - name of the new DDL replication filter -- `command_tag` - regular expression for matching command tags -- `role_name` - regular expression for matching role name - -The `command_tag` and `role_name` parameters can be set to `NULL` in which case -they will match any command tag or role respectively. They are both regular -expressions, so you can use patterns like `'CREATE.*'` or `'(CREATE|DROP).*'`. - -The target object identity (oid, name, etc) are not exposed, so you cannot -filter on them. - -### pglogical.replication_set_remove_ddl - -Remove a DDL replication filter from replication set. - -#### Synopsis - -```sql -pglogical.replication_set_remove_ddl(set_name name, ddl_filter_name text) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `ddl_filter_name` - name of the DDL replication filter to be removed from the set - -## Additional functions and views - -## `pglogical.ddl_replication` - -This view lists ddl replication configuration as set up by current ddl_filters. - -### `pglogical.ddl_replication` Columns - -| Name | Type | Description | -| ------------ | ---- | ------------------------------------------------------------ | -| set_ddl_name | name | Name of DDL filter | -| set_ddl_tag | text | Which command tags it applies to (regular expression) | -| set_ddl_role | text | Which roles it applies to (regular expression) | -| set_name | name | Name of the replication set for which this filter is defined | - -## `pglogical.ddl_replication` - -This view lists ddl replication configuration as set up by current ddl_filters. - -### `pglogical.ddl_replication` Columns - -| Name | Type | Description | -| ------------ | ---- | ------------------------------------------------------------ | -| set_ddl_name | name | Name of DDL filter | -| set_ddl_tag | text | Which command tags it applies to (regular expression) | -| set_ddl_role | text | Which roles it applies to (regular expression) | -| set_name | name | Name of the replication set for which this filter is defined | - -### pglogical.replicate_ddl_command - -This function can be used to explicitly replicate a command as-is using the -specified set of replication sets. The command will also be executed locally. - -In most cases `pglogical.replicate_ddl_command` is rendered obsolete by -pglogical's support for DDL replication filters. - -#### Synopsis - -```sql -pglogical.replicate_ddl_command(command text, replication_sets text[])` -``` - -#### Parameters - -- `command` - DDL query to execute -- `replication_sets` - array of replication sets which this command should be - associated with; default "{ddl_sql}" - -## Restrictions - -When the DDL replication filter matches a DDL command it will modify the -`search_path` configuration parameter used to execute the DDL on both provider -and subscriber(s) to include only `pg_catalog` i.e. the system catalogs. This -means that all the user objects referenced in the query must be fully schema -qualified. For example `CREATE TABLE foo...` will raise an error when -executed and has to be rewritten as `CREATE TABLE public.foo...`. - -DDL that matches the DDL replication filter and does not comply with this -requirement will fail with an error like this: - -```sql -ERROR: no schema has been selected to create in -STATEMENT: CREATE TABLE foo (id integer); -``` - -or will raise an `ERROR` message complaining that data types, tables, etc -referenced by the DDL statement do not exist even when they can be queried -normally, are shown by `psql`, etc. - -For example, attempting to drop some table `public.a` will fail: - -```sql -ERROR: table "a" does not exist -STATEMENT: DROP TABLE a; -``` - -and must be reframed as: - -```sql -DROP TABLE public.a; -``` - -The same restriction applies to any command executed using the -`pglogical.replicate_ddl_command` function. The function call has the -additional restriction that it cannot execute special commands which need to be -run outside of a transaction. Most notably `CREATE INDEX CONCURRENTLY` will -fail if run using `pglogical.replicate_ddl_command` but will work via DDL -replication sets. - -For testing purposes it can be useful to simulate the behaviour of -DDL replication capture manually in psql. To do so, set the `search_path` to -the empty string, e.g. - -```sql -BEGIN; -SET LOCAL search_path = ''; -CREATE TABLE mytable(id integer); -COMMIT; -``` - -will fail with `ERROR: no schema selected to create in`. - -## Considerations with global objects - -Because PostgreSQL has objects that exist within one database, objects shared -by all databases, and objects that exist outside the catalogs, some care is -required when you may potentially replicate a subset of DDL or replicate DDL -from more than one database: - -- pglogical can capture and replicate DDL that affects global objects like - roles, users, groups, etc, but only if the commands are run in a database - with pglogical ddl replication enabled. So it's easy to get into inconsistent - states if you do something like `CREATE ROLE` in the `postgres` db then - `ALTER ROLE` in the `my_pglogical_enabled`. The resulting captured DDL may - not apply on the downstream, requiring a transaction to be skipped over or - non-replicated DDL to be run on the downstream to create the object that's - targeted by the replicated DDL. - -- pglogical can also capture and replicate DDL that references global objects - that may not exist on the other node(s), such as tablespaces and users/roles. - So an `ALTER TABLE ... OWNER TO ...` can fail to apply if the role, a global - object, does not exist on the downstream. You may have to create a dummy - global object on the downstream or if absolutely necessary, skip some changes - from the stream. - -- DDL that references local paths like tablespaces may fail to apply on the other - end if paths differ. - -In general you should run all your DDL via your pglogical-enabled database, and -ensure that all global objects *exist* on the provider and all subscribers. This -may require the creation of dummy roles, dummy tablespaces, etc. - -## `pglogical.tables` - -This view lists information about table membership in replication sets. -If a table exists in multiple replication sets it will appear multiple times -in this table. - -### `pglogical.tables` Columns - -| Name | Type | Description | -| ----------- | ------- | ---------------------------------------------------- | -| relid | oid | The OID of the relation | -| nspname | name | Name of the schema relation is in | -| relname | name | Name of the relation | -| set_name | name | Name of the replication set | -| set_ops | text\[] | List of replicated operations | -| rel_columns | text\[] | List of replicated columns (NULL = all columns) (\*) | -| row_filter | text | Row filtering expression | - -## `pglogical.queue` - -DDL can also be queued up with a message to state the replication information. -This can be seen in ascending order, on this view. - -## `pglogical.queue_truncate` - -A function that erase's all the logging information of the view. diff --git a/product_docs/docs/pgd/3.6/pglogical/failover.mdx b/product_docs/docs/pgd/3.6/pglogical/failover.mdx deleted file mode 100644 index d70b9898cbb..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/failover.mdx +++ /dev/null @@ -1,214 +0,0 @@ ---- -navTitle: Failover -title: Failover with pglogical3 -originalFilePath: failover.md - ---- - -pglogical has support for following failover of both the provider (logical -master) and subscriber (logical replica) if the conditions described in the -following sections are met. - -Only failover to streaming physical replicas is supported. pglogical subscribers -cannot switch from replication from the provider to replicating from another -peer subscriber. - -## Provider failover setup - -*With appropriate configuration of the provider and the provider's physical -standby(s)*, pglogical subscriber(s) can follow failover of the provider to a -promoted physical streaming replica of the provider. - -Given a topology like this: - -``` -[Provider1] -------------> [Provider2] - | ^ - | | physical - | |-streaming - | replication - | (specific configuration - | required) - | - | - | <- logical - | replication - | - | -[Subscriber1] -``` - -On failure of Provider1 and promotion of Provider2 to replace it, pglogical on -Subscriber1 can consistently follow the failover and promotion if: - -- Provider1 and Provider2 run PostgreSQL 10 or newer -- The connection between Provider1 and Provider2 uses streaming replication - with hot standby feedback and a physical replication slot. It's OK if WAL - archiving and a `restore_command` is configured as a fallback. -- Provider2 has: - - `recovery.conf`: - - `primary_conninfo` pointing to Provider1 - - `primary_slot_name` naming a physical replication slot on Provider1 to be - used only by Provider2 - - `postgresql.conf`: - - `pglogical` in its `shared_preload_libraries` - - `hot_standby = on` - - `hot_standby_feedback = on` - - [`pglogical.synchronize_failover_slot_names`](configuration#pglogical-synchronize-failover-slot-names) - can be modified to specify which slots should be synchronized (default is all pglogical/bdr slots) -- Provider1 has: - - `postgresql.conf`: - - [`pglogical.standby_slot_names`](configuration#pglogical-standby-slot-names) - lists the physical replication slot used for Provider2's `primary_slot_name`. - Promotion will still work if this is not set, but subscribers may be inconsistent - per the linked documentation on the setting. -- Provider2 has had time to sync and has created a copy of Subscriber1's - logical replication slot. pglogical3 creates master slots on replicas - automatically once the replica's resource reservations can satisfy the master - slot's requirements, so just check that all pglogical slots on the master exist - on the standby, and have `confirmed_flush_lsn` set. -- Provider2 takes over Provider1's IP address or hostname *or* Subscriber1's - existing subscription is reconfigured to connect to Provider2 using - `pglogical.alter_node_add_interface` and `pglogical.alter_subscription_interface`. - -It is not necessary for Subscriber1 to be aware of or able to connect to -Provider2 until it is promoted. - -The post-failover topology is: - -``` -XXXXXXXXXXX -xProvider1x [Provider2] -XXXXXXXXXXX ^ - | - | - | - | - |------------------------------ - | - | <- logical - | replication - | - | -[Subscriber1] -``` - -The reason pglogical must run on the provider's replica, and the provider's -replica must use a physical replication slot, is due to limitations in -PostgreSQL itself. - -Normally when a PostgreSQL instance is replaced by a promoted physical replica -of the same instance, any replication slots on that node are lost. Replication -slot status is not itself replicated along physical replication connections and -does not appear in WAL. So if the failed-and-replaced node was the upstream -provider of any logical subscribers, those subscribers stop being able to -receive data and cannot recover. Physical failover breaks logical replication -connections. - -To work around this, pglogical3 running on the failover-candidate replica syncs -the state of the master provider's logical replication slot(s) to the replica. -It also sends information back to the master to ensure that those slots -guarantees' (like `catalog_xmin`) are respected by the master. That -synchronization requires a physical replication slot to avoid creating -excessive master bloat and to ensure the reservation is respected by the master -even if the replication connection is broken. - -## Subscriber failover setup - -pglogical automatically follows failover of a subscriber to a streaming physical -replica of the subscriber. No additional configuration is required. - -**WARNING**: At present it's possible for the promoted subscriber to lose some -transactions that were committed on the failed subscriber and confirmed-flushed -to the provider, but not yet replicated to the new subscriber at the time of -promotion. That's because the provider will silently start replication at the -greater of the position the subscriber sends from its replication origin and -the position the master has recorded in its slot's `confirmed_flush_lsn`. - -Where possible you should execute a planned failover by stopping the -subscription on Subscriber1 and waiting until Subscriber2 is caught up to -Subscriber1 before failing over. - -Given the server topology: - -``` -[Provider1] - | - | - | <- logical - | replication - | - | - | -[Subscriber1]------------> [Subscriber2] - ^ - | physical - |-streaming - replication -``` - -Upon promotion of Subscriber2 to replace a failed Subscriber1, logical -replication will resume normally. It doesn't matter whether Subscriber2 has the -same IP address or not. - -For replication to resume promptly it may be necessary to explicitly terminate -the walsender for Subscriber1 on Provider1 if the connection failure is not -detected promptly by Provider1. pglogical enables TCP keepalives by default so -in the absence of manual action it should exit and release the slot -automatically in a few minutes. - -It is important that Subscriber1 be fenced or otherwise conclusively terminated -before Subscriber2 is promoted. Otherwise Subscriber1 can interfere with -Subscriber2's replication progress tracking on Provider1 and create gaps in the -replication stream. - -After failover the topology is: - -``` -[Provider1] - | - | - | <- logical - | replication - | - |------------------------------- - | - | -XXXXXXXXXXXXXXX | -X[Subscriber1]X [Subscriber2] -XXXXXXXXXXXXXXX -``` - -Note: at this time it is possible that there can be a small window of -replicated data loss around the window of failover. pglogical on Subscriber1 -may send confirmation of receipt of data to Provider1 before ensuring that -Subscriber2 has received and flushed that data. - -## Additional functions - -### pglogical.sync_failover_slots() - -Signal the supervisor to restart the mecanism to synchronize the failover -slots specifyed in the [`pglogical.synchronize_failover_slot_names`](configuration#pglogical-synchronize-failover-slot-names) - -#### Synopsis - - pglogical.syncfailover_slots(); - -This function should be run on the subscriber. - -## Legacy: Provider failover with pglogical2 using failover slots - -An earlier effort to support failover of logical replication used the "failover -slots" patch to PostgreSQL 9.6. This patch is carried in 2ndQPostgres 9.6 -(only), but did not get merged into any community PostgreSQL version. pglogical2 -supports using 2ndQPostgres and failover slots to follow provider failover. - -The failover slots patch is neither required nor supported by pglogical3. -pglogical3 only supports provider failover on PostgreSQL 10 or newer, since -that is the first PostgreSQL version that contains support for sending -`catalog_xmin` in hot standby feedback and for logical decoding to follow -timeline switches. - -This section is retained to explain the change in failover models and reduce -any confusion that may arise when updating from pglogical2 to pglogical3. diff --git a/product_docs/docs/pgd/3.6/pglogical/index.mdx b/product_docs/docs/pgd/3.6/pglogical/index.mdx deleted file mode 100644 index f812eeb3e08..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/index.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -navigation: - - index - - release-notes - - nodes - - replication-sets - - ddl - - subscriptions - - configuration - - failover - - restrictions - - troubleshooting -navTitle: pglogical 3 -title: pglogical 3 -originalFilePath: index.md - ---- - -The pglogical 3 extension provides logical streaming replication for PostgreSQL, -using a publish/subscribe model. It is based on technology developed as part -of the BDR3 project. - -We use the following terms to describe data streams between nodes: - -- Nodes - PostgreSQL database instances -- Providers and Subscribers - roles taken by Nodes -- Replication Set - a collection of tables - -These terms have been deliberately reused from the earlier Slony technology. - -pglogical is new technology utilizing the latest in-core features, so we -require both provider and subscriber nodes to run PostgreSQL 10 or newer. - -Use cases supported are: - -- Upgrades between major versions (given the above restrictions) -- Full database replication -- Selective replication of sets of tables using replication sets -- Selective replication of table rows at either provider or subscriber side (row_filter) -- Selective replication of table columns at provider side -- Data gather/merge from multiple upstream servers - -Architectural details: - -- pglogical works on a per-database level, not whole server level like - physical streaming replication -- One Provider may feed multiple Subscribers without incurring additional disk - write overhead -- One Subscriber can merge changes from several origins and detect conflict - between changes with automatic and configurable conflict resolution (some, - but not all aspects required for multi-master). -- Cascading replication is implemented in the form of changeset forwarding. diff --git a/product_docs/docs/pgd/3.6/pglogical/nodes.mdx b/product_docs/docs/pgd/3.6/pglogical/nodes.mdx deleted file mode 100644 index 1abbe0301de..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/nodes.mdx +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Nodes -originalFilePath: nodes.md - ---- - -Each database that participates in pglogical replication must be represented -by its own node. Each node must have a name that is unique amongst all nodes -that will interact with and communicate with each other. - -A pglogical node associates an operator-supplied node name with a connection -string that pglogical subscriber nodes may use to communicate with the node. -It also serves to mark a database as pglogical-enabled and as something with -which to associate other pglogical state like replication sets or -subscriptions. - -Creating a pglogical node in an existing PostgreSQL databse using the -[`pglogical.create_node`](#pglogical_create_node) function causes pglogical to -launch a manager process for the node but doesn't cause any sort of replication -to begin. - -A node can be set up as a pglogical provider by having replication sets created -and/or tables and DDL filters added to the default replication set. A node can -be set up as a pglogical subscriber by having a subscription created on it -after the node is created. Any given node can be a provider, a subscriber, or -both; nothing in node creation marks the node as one or the other. - -## Setting up a node as a provider - -Newly created pglogical nodes have empty replication sets and do not have any -DDL replication filters enabled. - -[Replication sets](replication-sets) specify what data from which tables and -sequences should be sent to any subscriptions that use this node as a provider. - -[DDL replication filters](ddl) capture and replicate schema changes to -subscribers so that subscribers' definitions of tables, types, etc remain in -sync with the provider. - -The simplest way to set up a new node as a provider is to re-create the -'default' replication set with all existing and future tables and sequences -auto-added to it. Then add a DDL replication filter to it to enable automatic -schema replication. For example: - -```sql -SELECT pglogical.create_node('mynode'); -SELECT pglogical.drop_replication_set('default'); -SELECT pglogical.create_replication_set('default', autoadd_tables := true, autoadd_sequences := true, autoadd_existing := true); -SELECT pglogical.replication_set_add_ddl('default', 'all_ddl', '.*', NULL); -``` - -A replication set drop and create is used here because -`pglogical.alter_replication_set` cannot autoadd existing tables. - -## Setting up a node as a subscriber - -Newly created nodes do not have any subscriptions so they won't receive -changes from anywhere. Use -[`pglogical.create_subscription(...)`](subscriptions#pglogical_create_subscription) -to populate a node with initial data and start receiving streams of changes. Or use -the separate [`pglogical_create_subscriber`](subscriptions#pglogical_create_subscriber) -to create a node and subscription from a basebackup or physical streaming replica. - -Creating subscriber nodes is discussed in detail in ["Subscriptions"](subscriptions). - -## Node information - -### pglogical.local_node - -A view containing node information but only for the -local node. - -## `pglogical.node` - -This table lists all PGL nodes. - -### `pglogical.node` Columns - -| Name | Type | Description | -| --------- | ---- | ---------------- | -| node_id | oid | Id of the node | -| node_name | name | Name of the node | - -### `pglogical.node_interface` - -This is a view that elaborates the information in `pglogical.node`, -showing the DSN and node interface information. - -### `pglogical.node_interface` Columns - -| Name | Type | Description | -| --------- | ---- | ------------------------------------- | -| if_id | oid | Node Interface ID | -| if_name | name | Name of the node the interface is for | -| if_nodeid | oid | ID of the node | -| if_dsn | text | DSN of the node | - -## Node management - -Nodes can be added and removed dynamically using SQL calls to functions -provided by pglogical. - -### pglogical.create_node - -Creates a pglogical node. Only one pglogical node may exist on a given -PostgreSQL database. There's nothing special to mark a node as a provider -or subscriber - one node may be either, or both. - -#### Synopsis - -```sql -pglogical.create_node(node_name name, dsn text) -``` - -#### Parameters - -- `node_name` - name of the new node; only one node is allowed per database -- `dsn` - connection string to the node. For nodes that are supposed to be - providers; this should be reachable from outside - -### pglogical.drop_node - -Removes the node. - -#### Synopsis - -```sql -pglogical.drop_node(node_name name, ifexists bool) -``` - -#### Parameters - -- `node_name` - name of an existing node -- `ifexists` - if true, error is not thrown when subscription does not exist; - default is false - -### pglogical.alter_node_add_interface - -Adds an interface to a node. - -When a node is created, the interface for it is also created with the `dsn` -specified in the `create_node` and with the same name as the node. - -If the address or connection options required for a subscriber to connect to a -provider change, create a new interface *for* the provider *on* the subscriber, -then associate it with the subscription so that the subscriber switches to the -new connection string. For example: - -```sql -SELECT pglogical.alter_node_add_interface('providername', 'providername_newconnname', 'connstr'); -SELECT pglogical.alter_subscription_interface('subscription_name', 'providername_newconnname'); -``` - -At this time creating a new interface on the provider side has no effect on any -subscribers. Subscribers use the connection string specified at subscription -creation time, not the connection string declared for a node. - -#### Synopsis - -```sql -pglogical.alter_node_add_interface ( - node_name name, - interface_name name, - dsn text -) -``` - -When a node is created, the interface for it is also created with the `dsn` -specified in the `create_node` and with the same name as the node. This -interface allows adding alternative interfaces with different connection -strings to an existing node. - -#### Parameters - -- `node_name` - name of an existing node -- `interface_name` - name of a new interface to be added -- `dsn` - connection string to the node used for the new interface - -### pglogical.alter_node_drop_interface - -Remove an existing named interface from a node. - -#### Synopsis - -```sql -pglogical.alter_node_drop_interface(node_name name, interface_name name) -``` - -#### Parameters - -- `node_name` - name of an existing node -- `interface_name` - name of an existing interface diff --git a/product_docs/docs/pgd/3.6/pglogical/release-notes.mdx b/product_docs/docs/pgd/3.6/pglogical/release-notes.mdx deleted file mode 100644 index 05cce8d7044..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/release-notes.mdx +++ /dev/null @@ -1,1237 +0,0 @@ ---- -navTitle: Release Notes -title: Release Notes for pglogical3 -originalFilePath: release-notes.md - ---- - -## pglogical 3.7.16 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Resolved Issues - -- Keep the `lock_timeout` as configured on non-CAMO-partner BDR nodes (BDR-1916) - A CAMO partner uses a low `lock_timeout` when applying transactions - from its origin node. This was inadvertently done for all BDR nodes - rather than just the CAMO partner, which may have led to spurious - `lock_timeout` errors on pglogical writer processes on normal BDR - nodes. - -- Prevent walsender processes spinning when facing lagging standby slots (RT80295, RT78290) - Correct signaling to reset a latch so that a walsender process does - consume 100% of a CPU in case one of the standby slots is lagging - behind. - -- Provide a proper error when attempting to use `pglogical.use_spi` (RT76368) - -- Reduce log information when switching between writer processes (BDR-2196) - -- Eliminate a memory leak when replicating partitioned tables (RT80981, BDR-2194) - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.29 and higher -- 2.4.0 and 2.4.1 - -## pglogical 3.7.15 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Add `pglogical.max_worker_backoff_delay` (BDR-1767) - This changes the handling of the backoff delay to exponentially - increase from `pglogical.min_worker_backoff_delay` to - `pglogical.max_worker_backoff_delay` in presence of repeated errors. This - reduces log spam and in some cases also prevents unnecessary - connection attempts. - -### Resolved Issues - -- For the view `pglogical.subscriptions`, ensure the correct value is displayed - in the `provider_dsn` column (BDR-1859) - Previously the subscriber node's DSN was being displayed. - -- Fix handling of `wal_receiver_timeout` (BDR-1848) - The `wal_receiver_timeout` has not been triggered correctly due to a regression - in BDR 3.7 and 4.0. - -- Limit the `pglogical.standby_slot_names` check when reporting flush position only to - physical slots (RT77985, RT78290) - Otherwise flush progress is not reported in presence of disconnected nodes when - using `pglogical.standby_slot_names`. - -- Confirm LSN of LCR slot progress records when recovering LCR segments (BDR-1264) - -- Fix replication of data types created during bootstrap (BDR-1784) - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.29 and higher -- 2.4.0 and 2.4.1 - -## pglogical 3.7.14 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Implement buffered read for LCR segment file (BDR-1422) - This should reduce both I/O operations done by decoding worker as well as the - amount of signalling between the decoding worker and wal senders which results - in improved performance when decoding worker is used. - -### Resolved Issues - -- Invalidate output plugin's replication set cache when published replication sets - change (BDR-1715) - This ensures that published replicated sets are always up to date when user - changes what should be published on node level. Before this fix, the old - settings would have been applied until downstream has reconnected. - This primarily affects BDR in situations where the `bdr.alter_node_replication_sets` - was called on multiple nodes in quick succession. - -- Don't try to retry transaction replication when writer receives SIGTERM or SIGINT - This would unnecessarily hold back the shutdown of postgres when parallel apply - is enabled. - -- Log correct error message during initial schema synchronization error (BDR-1598) - Previously we'd always log ERROR with message "Success" which is not helpful for - troubleshooting. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.29 and higher -- 2.4.0 -- 2.4.1 - -## pglogical 3.7.13 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Allow the BDR consensus process to use a (sub) replorigin (BDR-1613) - For parallel apply, multiple writers could use invididual origins - that would be merged, thus act kind of as child origins for a main - or parent origin. - Extend this mechanism to allow the BDR consensus process to also - register an origin participating in the group. - -### Resolved Issues - -- Fix the replication protocol handling of some strings (RT74123) - Certain strings like e.g. relation schema, relation name, attribute - name, and message prefix were mistakenly changed to not include a - terminating NULL character. This led to a protocol incompatibility - when interoperating with PGLogical 3.5.3 and older or when WAL - messages are used (e.g. due to the use of BDR features CAMO or Eager - All Node Replication). - -- Fix segfault when creating a subscription with the RabbitMQ writer plugin (BDR-1482, RT72434) - -- Don't wait on own replication slot when waiting for `standby_slot_names` (RT74036) - The walsenders that use slots named in `standby_slot_names` should not - wait for anything, otherwise it might wait forever. - -- Reduce logging when WAL decoder is not available (BDR-1041) - `pgl_xact_fully_decoded()` will log a message when it finds that - the WAL decoder is not running. WAL decoder may not start for long - duration and thus this log line will repeat and increase the log file - size. There are other ways to know whether WAL decoder is running. So - this line is not required. - -- Handle deprecated `update_differing` and `update_recently_deleted` (BDR-1610, RT74973) - While upgrading to 3.7, take care of the deprecated conflict types - otherwise, as they would be unknown to the new version, it would - not know how to handle them and break the upgrade process. - -- Enable async conflict resolution for explicit 2PC (BDR-1609, RT71298) - Continue applying the transaction using the async conflict resolution - for explicit two phase commit. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.28 -- 2.4.0 -- 2.4.1 - -## pglogical 3.7.12 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Add replication status monitoring (BDR-865) - Track the connection establishment and drops, the number of - transactions committed as well as the restart LSN to detect repeated - restarts and diagnose stalled replication. - -- Improve performance when used in combination with synchronous replication (BDR-1398) - Override `synchronous_commit` to `local'` for all PGLogical - processes performing only bookkeeping transactions which do not need - to be replicated. Only the PGLogical writer processes applying user - transactions need to follow the `synchronous_commit` mode configured - for synchronous replication. - -- Internal improvements and additional hooks to better support BDR - -### Resolved Issues - -- Performance improvements for Decoding Worker (BDR-1311, BDR-1357) - Speed up lookups of the WAL decoder worker, reduce delays after - reaching up to the LSN proviously known to be decoded by the - Decoding Worker, and reduce number of system calls when writing one - LCR chunk to an LCR segment file. - -- Improve compatibility with Postgres 13 (BDR-1396) - Adjust to an API change in ReplicationSlotAcquire that may have led - to unintended blocking when non-blocking was requestend and vice - versa. This version of PGLogical eliminates this potential problem, - which has not been observed on production systems so far. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.27 -- 2.4.0 - -## pglogical 3.7.11 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Resolved Issues - -- Add protection against malformed parameter values in pgl output plugin - This fixes potential crash when some parameters sent to the output plugin - were malformed. - -- Get copy of slot tuple when logging conflict (BDR-734) - Otherwise we could materialize the row early causing wrong update in presence - of additional columns on the downstream. - -- Use a separate memory context for processing LCRs (BDR-1237, RT72165) - This fixes memory leak when using the decoding worker feature of BDR. - -- Truncate LCR segment file after recovery (BDR-1236, BDR-1259) - This fixes memory errors reported by the decoding worker after crash. - -- Ensure `pg_read_and_filter_lcr` will exit when postmaster dies - (BDR-1226, BDR-1209, RT72083) - Solves issues with hanging decoder worker on shutdown. - -- Fix memory leak in the pglogical COPY handler (BDR-1219, RT72091) - This fixes memory leak when synchronizing large tables. - -- Allow binary and internal protocol on more hardware combinations. This - currently only affects internal testing. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.27 -- 2.4.0 - -## pglogical 3.7.10 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Windows support improvements (BDR-976, BDR-1083) - -### Resolved Issues - -- Fix potential crash during cleanup of bulk copy replication (BDR-1168) - -- Fix issues in generic WAL message handling when the WAL message was produced - by something other than pglogical (BDR-670) - -- Redefine `werr_age` of `pglogical.worker_error_summary` to report correct age - -- Only use key attributes of covering unique index when used as replica identity - This only affects what is being sent over network, no logic change. - -## pglogical 3.7.9 - -This is a maintenance release for pglogical 3.7 which includes minor -improvements as well as fixes for issues identified previously. - -### Improvements - -- Support two-phase commit transaction with Decoding Worker (BDR-811) - - A two-phase commit transaction is completely decoded and sent downstream when - processing its PREPARE WAL record. COMMIT/ROLLBACK PREPARED is replicated - separately when processing the corresponding WAL record. - -- Reduce writes to `pg_replication_origin` when using parallel apply (RT71077) - Previously, especially on EPAS pglogical could produce thousands of dead rows - in `pg_replication_origin` system catalog if it had connection problems to - upstream. - -## Resolved Issues - -- Fix flush queue truncation (BDR-890) - During queue compaction flush to correct LSN instead of always truncating - whole flush queue. - -- Fix the pglogical.worker_error columns `werr_worker_index` and `werr_time` - Used to report wrong values. - -- Fix snapshot handling in internal executor usage (BDR-904) - Row filtering didn't correctly pushed snapshot in some situations. - - Caught thanks to upcoming change in PostgreSQL that double checks for this. - -- Fix handling of domains over arrays and composite types (BDR-29) - The replication protocol previously could not always handle columns using - domains over arrays and domains over composite types. - -## pglogical 3.7.8 - -This is a first stable release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -Upgrades are supported from pglogical 3.6.25 and 3.7.7 in this release. - -### Improvements - -- Allow parallel apply on EDB Advanced Server (EE) - -### Resolved Issues - -- Fix divergence after physical failover (BDR-365, RT68894 and RM19886) - Make sure that we don't report back LSN on subscriber that - hasn't been received by named standbys (pglogical.standby_slot_names). - - This will ensure provider side keeps slot position behind - far enough so that if subscriber is replaced by one of said - named standbys, the standby will be able to fetch any missing - replication stream from the original provider. - -- Fix crash when ERROR happened during fast shutdown of pglogical writer - -- Don't re-enter worker error handling loop recursively (BDR-667) - This should help make what happens clearer in any cases where we do - encounter errors during error processing. - -- Assign collation to the index scan key (BDR-561) - When doing lookups for INSERT/UPDATE/DELETE, either to find conflicts - or key for the operation to be applied, we should use correct collation. - - This fixes index lookups for index on textual fields on Postgres 12+. - -- Use `name` data type for known fixed length fields (BDR-561) - This solves potential index collation issues with pglogical catalogs. - -- Progress WAL sender's slot based on WAL decoder input (BDR-567) - Without slot progression the server will eventually stop working. - -- Fix begin of transaction write when LCR file does not have enough space (BDR-606) - -- Restart decoding a transaction that was not completed in single decoding worker (BDR-247) - If we crashed during a long transaction that spawns on more then one lcr file - we start decoding again from the lsn of the beginning of the transaction and - find the last lcr file where we can write into. - -- Generate temp slot with correct length in subscription sync - Otherwise the name of the slot might be shortened by Postgres leading to - confusion on the slot cleanup. - -- Improve detection of mixing temporary and nontemporary objects in DDLs (BDR-485) - These can break replication so it's important to not allow them. - -- Fix pre-commit message handling in Eager replication (BDR-492) - -- Override GUCs in all pglogical workers, not just in writers. - -## pglogical 3.7.7 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -Upgrades are supported from pglogical 3.6.25 and 3.7.6 in this release. - -### Improvements - -- Use parallel apply during initial sync during logical join - -- Add worker process index to the worker_error catalog (BDR-229) - The column `werr_worker_index` in worker_error table keeps track - of the writers for the same subscription. - -- Various improvements for WAL decoder/sender coordination (BDR-232, BDR-335) - -- Name LCR segment similar to XLOG segments (BDR-236, BDR-253, BDR-321, BDR-322) - An LCR segment file is identified by five 8-digit hex numbers. - Timeline first group, XLOG the next two groups and file number the last - two groups. - -### Resolved Issues - -- Restrict adding queue table to the replication set. (EDBAS, EBD-45) - -- Fix deadlock between receiver and writer during queue flush (BDR-483) - -- Force and wait for all writers to exit when one writer dies (BDR-229) - -- Name LCR directory after the replication slot (BDR-60) - Logical output plugin may be used by multiple replication slots. Store - the LCRs from a given replication slot in a directory named after that - replication slot to avoid mixing LCRs for different slots. - -- Fix EXPLAIN...INTO TABLE replication issue (EBC-46) - -## pglogical 3.7.6 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -Upgrades are supported from pglogical 3.6.25 in this release. - -### Improvements - -- Enable parallel apply for CAMO and Eager (RM17858) - -- Improve error handling in Eager/CAMO, especially with parallel apply - (BDR-106) - -- Reduce severity of Eager/CAMO feedback errors - -- Add infrastructure necessary for allowing separation of WAL decoding from - WalSender process in BDR (RM18868, BDR-51, BDR-60) - -### Resolved Issues - -- Improve relcache invalidation handling in heap writer - This should solve missed invalidations after opening table for DML apply. - -- Wait for the writer that has XID assigned rather then one that doesn't - (BDR-137) - This fixes deadlock in parallel apply when there is a mix of empty and - non-empty transactions where the non-empty ones conflict. - -- Correct writer state tracking for Eager/CAMO (BDR-107) - -- Correct and improve CAMO misconfiguration handling (BDR-105) - Properly abort the transaction in case of sync CAMO, so the internal - state of the PGL writer is cleared - -- Fix transaction state tracking for CAMO/Eager - Do not abort the transaction at pre-commit time for non-CAMO nodes, but - keep it open until the final commit. Adjust the transaction state - tracking accordingly - -- Fix MERGE handling in 2ndQPostgres 12 and 13 - We'd before allow the MERGE command on replicated tables without appropriate - REPLICA IDENTITY which could result in broken replication. - -- Fix CAMO feedback sending (RM17858) - Fixes stalls in CAMO feedback, improving performance compared to previous - 3.7 beta releases. This is especially visible with parallel apply enabled. - -## pglogical 3.7.5 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -### Improvements - -- Optimize utility command processing (RT69617) - For commands that won't affect any DB objects and don't affect - pglogical we can skip the processing early without reading any - pglogical or system catalogs or calling to DDL replication plugin - interfaces. This is optimization for systems with large number of - such utility command calls (that is primarily applications that - do explicit transaction management). - -- Add upgrade path from pglogical 2. - -### Resolved Issues - -- Ensure that `pglogical.standby_slot_names` takes effect when - `pglogical.standby_slots_min_confirmed` is at the default value - of -1. - - On 3.6.21 and older `pglogical.standby_slot_names` was ignored - if `pglogical.standby_slot_names` is set to zero (RM19042). - - Clusters satisfying the following conditions may experience inter-node - data consistency issues after a provider failover: - - - Running pglogical 3.0.0 through to 3.6.21 inclusive; - - Using pglogical subscriptions/or providers directly (BDR3-managed - subscriptions between pairs of BDR3 nodes are unaffected); - - Have a physical standby (streaming replica) of a pglogical provider - intended as a failover candidate; - - Have `pglogical.standby_slot_names` on the provider configured to list that - physical standby; - - Have left `pglogical.standby_slots_min_confirmed` unconfigured or set it - explicitly to zero; - - This issue can cause inconsistencies between pglogical provider and subscriber - and/or between multiple subscribers when a provider is replaced using - physical replication based failover. It's possible for the subscriber(s) to - receive transactions committed to the pre-promotion original provider - that will not exist on the post-promotion replacement provider. This - causes provider/subscriber divergence. If multiple subscribers are - connected to the provider, each subscriber could also receive a different - subset of transactions from the pre-promotion provider, leading to - inter-subscriber divergence as well. - - The `pglogical.standby_slots_min_confirmed` now defaults to the newly - permitted value `-1`, meaning "all slots listed in - `pglogical.standby_slot_names`". The default of 0 on previous releases - was intended to have that effect, but instead effectively disabled - physical-before-logical replication. - - To work around the issue on older versions the operator is advised to - set `pglogical.standby_slots_min_confirmed = 100` in `postgresql.conf`. - This has no effect unless `pglogical.standby_slot_names` is also set. - - No action is generally required for this issue on BDR3 clusters. - BDR3 has its own separate protections to ensure consistency during - promotion of replicas. - -- Fix pglogical_create_subscriber when "-v" is passed. - It will make pg_ctl emit meaningful information, making it easier to - debug issues where pg_ctl fails - -## pglogical 3.7.4 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -### Improvements - -- Support PostgreSQL 13 - -- Add `pglogical.replication_origin_status` view (RM17074) - Same as `pg_replication_origin_status` but does not require superuser - permissions to access it. - -- Beta support of upgrades from 3.6 (currently from 3.6.22) - -- Improved SystemTAP support - -### Resolved Issues - -- Fix race condition in replication table filtering which could cause - crash (RM18839) - The cached info about table might get invalidated while used which would - crash the backend during one of the following operations: - - - reading the pglogical.tables view - - new subcription creation - - table resynchronization - -- Don't do transparent DDL replication on commands that affect temporary objects (RM19491, RT69170) - These are likely to not exist on the subscription. - -- Only run pgl specific code in deadlock detector when inside writer (RM18402) - It's not relevant in user backends and would cause ERRORs there. - -## pglogical 3.7.3 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -### Improvements - -- Parallel Apply (RM6503) - Allows configuring number of writers per subscriptions. By default this is - still 1, which mean parallel apply is off by default but can be enabled - both globally (`pglogical.writers_per_subscription`) and per subscription - (`num_writers` option in `pglogical.create_subscription()` and - `pglogical.alter_subscription_num_writers()`). - -- Split "replicating" subscription status into two statuses - One is still "replicating" and is reported only if something was actually - replicated by the subcription since last worker start. The other is "started" - and just means that the worker for the subscription is running at the time - the status query was executed. - This should reduce confusion where subscription would report "replicating" - status but worker is in restart loop due to an apply error. - -- Substantial test and testing framework improvements - -- Improve 2ndQPostgres and BDR version dependency handling (RM17024) - -- Add PostgreSQL 12 support to `pglogical_create_subscriber` - -- Rework table resynchronization to use separate receiver process from the - main one - This improves performance of both main apply (primarily latency) and the - resynchronization itself. - It also fixes potential issue where table could be considered synchronized - before the catchup finished completely. - -### Resolved Issues - -- Fix crash on resynchronization of large partitioned tables (RM18154, RM15733, - RT68455, RT68352) - The resync process would keep crashing due to cache invalidation race - condition if the `COPY` took very long or if there was DDL activity on the - copied table during the `COPY`. - -- Prohibit MERGE and UPSERT on a table without replica identity (RM17323, RT68146) - These commands can end up doing `UPDATE` which will break replication if - the table has no replica identity as the downstream has no way to find the - matching row for updating. - -- Resolve relcache reference leak reports (RM16956) - Close the relation correctly in `pglogical.show_repset_tables_info()` - -- Resolve rare crash in HeapWriter row cleanup code (RM16956) - -- Resolve rare crash on worker exit (RM11686) - If a pglogical worker exited before it finished initialization it could - crash instead of exiting cleanly. - -- Fix apply errors parallel index rebuild afrer `TRUNCATE` (RM17602) - -## pglogical 3.7.2 - -This is a beta release of the pglogical 3.7. - -pglogical 3.7 is a major release of pglogical. This release includes -major new features as well as smaller enhancements. - -pglogical 3.7 introduces several major new features as well as -architectural changes some of which affect backward compatibility with -existing applications. - -### Important Notes - -- Beta software is not supported in production - for application test only - -- Upgrade from 3.6 is not supported in this release, yet. - -### Improvements - -- Add support for Postgres 12, deprecate support for older versions - pglogical 3.7 now requires at least Postgres 10 and supports up to - Postgres 12. - -### Resolved Issues - -- Keep open the connection until pglogical_create_subscriber finishes (RM13649) - Set idle_in_transaction_session_timeout to 0 so we avoid any user setting - that could close the connection and invalidate the snapshot. - -## pglogical 3.6.19 - -This is a security and maintenance release for pglogical 3.6 which includes -minor features as well as fixes for issues identified previously. - -### Resolved Issues - -- SECURITY: Set search_path to empty for internal PGLogical SQL statements (RM15373) - Also, fully qualify all operators used internally. PGLogical is now - protected from attack risks identified in CVE-2018-1058, when the - user application avoids the insecure coding practices identified there. - -- Correct parsing of direct WAL messages (RT67762) - Custom WAL messages emitted by PGLogical (or plugins building on top - of it) can be broadcast or direct types. Decoding of the latter was - incorrect and could in rare cases (depending on the node name) lead - to "insufficient data left in message" or memory allocation errors. - Decoding of such direct WAL messages has been corrected. - -- Add pglogical.sync_failover_slots() function (RM14318) - Signal the supervisor process to restart the mechanism to synchronize the - failover slots specifyed in the "pglogical.synchronize_failover_slot_name". - -- Fix the `--extra-basebackup-args` argument passed to pg_basebackup (RM14808) - Corrects how the `pglogical_create_subscriber` tool passes on such - extra arguments to pg_backbackup. - -### Improvements - -- Add more diagnostic information to pglogical.queue message (RM15292) - A new key `info` has been added to `pglogical.queue` providing - additional information about a queued DDL operation. - -## pglogical 3.6.18 - -This is a maintenance release for pglogical 3.6 which includes minor features -as well as fixes for issues identified previously. - -### Improvements - -- Warn about failover issues if standby_slot_names is not set (RT66767, RM12973) - If pglogical.standby_slot_names is not set and a physical standby is - configured; failover to this standby will have data consistency issues as - per our documentation. However, the replica could just be a simple read - replica. In any case, we now warn on the replica about the potential data - corruption/divergence that could result if failover is desired to such a - standby. - -- Check repsets in create_subscription for pgl2 upstreams also. - -- Various improvements to systemtap integration. - -### Resolved Issues - -- Prevent a hang in case of an early error in the PGL writer (RT67433, RM14678) - -- Allow postgres to start with pglogical library loaded but activity suspended - Add start_workers commandline-only GUC to facilitate this. - -## pglogical 3.6.17 - -This is a maintenance release for pglogical 3.6 which includes minor features -as well as fixes for issues identified previously. - -### Improvements - -- Make the slot synchronization to standby more configurable (RM13111) - Added several new configuration parameters which tune the behavior of the - synchronization of logical replication slots from a primary to a standby - PostgreSQL servers. This allows for better filtering, inclusion of - non-pglogical replication sets and also using different connection string - than physical replication uses (useful when different user or database - should be used to collect information about slots). - -### Resolved Issues - -- Fix issue with UPDATEs on partitions with different physical row - representation than partition root (RM13539, RT67045) - The partitions must have same logical row as partition root they can have - different physical representation (primarily due to dropped columns). UPDATEs - on such partitions need to do special handling to remap everything correctly - otherwise constraints and not-updated TOAST columns will refer to wrong - incoming data. - -- Fix truncation of `\_tmp` slot names in sync slots - Long slot names could previously cause the temporary slot to be suffixed - by `\_tm` rather than the expected `\_tmp` suffix. - -### Support, Diagnostic and Logging Changes - -These changes don't directly change existing behaviour or add new user-facing -features. They are primarily of interest to technical support operations and -for advanced diagnostic analysis. - -- Expand non-invasive tracing (SystemTap, linux-perf, DTrace, etc) - support to cover inspection of the pglogical receiver's input protocol - stream, walsender output plugin protocol stream, and other useful events. - (RM13517) - -- Add a test and debug utility that decodes captured pglogical protocol streams - into human-readable form (RM13538) - -- Improve error context logging in the pglogical writer to show more - information about the transaction being applied and its origin. - -- Fix incorrectly reported commit lsn in errcontext messages from the pglogical - heap writer (RM13796). This fix only affects logging output. The writer would - report the lsn of the original forwarded transaction not the lsn of the - immediate source transaction. - -- Add subscription, local node and peer node names to heap writer errcontext - log output. - -## pglogical 3.6.16 - -This is the sixteenth minor release of the Pglogical 3.6 series. This release -includes mostly just enables BDR 3.6.16 without any significant changes to -pglogical. - -## pglogical 3.6.15 - -This is the fifteenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Fix backwards-compatibility to PGLogical 2 (RM13333, RT66919) - Recent releases performed additional checks during - `create_subscription`, which are fine against other PGLogical 3 - installations, but not backwards-compatible. This release corrects - the check to account for backwards-compatibility. - -- Correct a warning about GUC nest level not being reset (EE) (RM13375) - The addition of the `lock_timeout` in 3.6.14 led to a warning being - issued for CAMO and Eager All Node transaction ("GUC nest level = 1 - at transaction start"). With this release, GUC nest levels are - properly managed and the warning no longer occurs. - -### Improvements - -- Add a new `pglogical.worker_tasks` view that tracks and records pglogical's - background worker use. The view exposes information about the number of times - a given type of worker has been restarted, how long it has been running, - whether it accomplished any useful work, and more. This offers administrators - more insight into pglogical's internal activity when diagnosing problems, - especially when joined against the `pglogical.worker_error` table. - -- Add support for rate-limiting pglogical background worker (re)launches. The - new `pglogical.min_worker_backoff_delay` configuration option sets a minimum - delay between launches of all types of pglogical background workers so that - rapid respawning of workers cannot fill the log files and or excessive load - on the system that affects other operations. - - For example, if configured with `pglogical.min_worker_backoff_delay = - '500ms'`, pglogical will not retry any given background worker startup more - often than twice per second (`1000/500 = 2`). - - A simple fixed-rate factor was deemed to be the most predictable and - production-safe initial approach. Future enhancements may add a heuristic - delay factor based on worker type, time from start to exit, number of recent - launches, etc. - - The launch backoff delay defaults to 0 (off) to prevent surprises for - upgrading users. - - A setting of `pglogical.min_worker_backoff_delay = '5s'` or similar is a - reasonable starting point, and may become the default in a future release. - -### Upgrades - -The PostgreSQL Global Development Group has phased out support for -PostgreSQL 9.4 on all Debian based distributions. Following that, -this release covers only PostgreSQL 9.5 and newer. We advise to -upgrade to a newer version. - -For RedHat based distributions, this release is still available for -PostgreSQL 9.4. - -## pglogical 3.6.14 - -This is the fourteenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Resolve deadlocked CAMO or Eager transactions (RM12903, RM12910) - Add a `lock_timeout` as well as an abort feedback to the origin node - to resolve distributed deadlocking due to conflicting primary key - updates. This also prevents frequent restarts and retries of the - PGL writer process for Eager All Node and sync CAMO transactions. - -## pglogical 3.6.12 - -This is the twelveth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Add infrastructure for `check_full_row` in DELETE operations used by - BDR 3.6.12 (RT66493) - -- Validate requested replication sets at subscribe time (RM12020, RT66310) - `pglogical.create_subscription()` now checks that all requested replication - sets actually exist on the provider node before returning. If any are - missing it will raise an ERROR like: - `ERROR: replication set(s) "nonexistent_repset" requested by subscription are missing on provider` - with a DETAIL message listing the full sets requested, etc. - On prior releases subscriptions with missing repsets would fail after - `pglogical.create_subscription(...)` returned, during initial sync. The - failure would only be visible in the logs where it is much less obvious to - the user. Or if schema sync was not enable they could appear to succeed but - not populate the initial table contents. - - -### Resolved Issues - -- Fix a potential deadlock at CAMO partner startup. (RM12187) - After a restart, the CAMO partner resends all confirmations for - recent CAMO protected transactions. In case these fill the internal - queue between the receiver and writer processes, a deadlock was - possible. This release ensures the receiver consumes pending - feedback messages allowing the writer to make progress. - -## pglogical 3.6.11 - -This is the eleventh minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Implement remote_commit_flush for CAMO. (RM11564) - Additional level of robustness for CAMO, only replying when xact - is known committed and flushed on partner node. - -- Make receiver-writer shared queues of configurable size. (RM11779) - Two new GUCs are introduced: - pglogical.writer_input_queue_size (default 1MB) - pglogical.writer_output_queue_size (default 1MB) - -- Add a warning when user tries to set update_origin_change to skip - -- Add callback to request replay progress update. (RM6747) - -### Resolved Issues - -- Send TimeZone GUC when replicating DDL (RT66019) - To ensure that timezone dependent expressions in DDL get evaluated to - same value on all nodes. - -- Only use isvalid indexes when searching for conflicts (RT66036) - Indexes currently being created or failed index creations - will be ignored, to prevent concurrency issues with change apply - and `CREATE INDEX CONCURRENTLY`. - -- Fix crash when replication invalidations arrive outside a transaction (RM11159) - -- Make the receiver apply the queue before shutting down (RM11778) - Upon smart shutdown, the PGL writer no longer terminates - immediately, requiring queued transactions to be resent, but applies - already received transactions prior to shutting down. - -## pglogical 3.6.10 - -This is the tenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Add support for a CAMO remote_write mode (RM6749) - -### Resolved Issues - -- COMMIT after initial sync of a table. This avoids treating the first - catchup xact as if it was part of the initial COPY, which could lead to - strange errors or false conflicts. (RM11284). - -- Remove the 4 billion row limit during the initial subscription - synchronization (RT66050). - -- Cleanup table replication cache when replication set configuration changes. - Previously we could use stale cache on multiple calls for table replication - info on same connection if user changed the configuration in meantime. - This could result in initial sync missing replicated table if the - configuration was changed while the subscription was being created. - -- Remember repsets when caching table replication info. - If the client calls the table replication info with different parameters, - we need to remember them otherwise we might return cached value for wrong - replication sets. - This could result in initial sync copying data from table which were - not supposed to be replicated. - -## pglogical 3.6.9 - -This is the ninth minor release of the Pglogical 3.6 series. This release -includes minor improvements. - -### Improvements - -- Add support for local, remote_apply and remote_write. (RM11069, RT65801) - We now accept the use of all the values that PostgreSQL accepts when configuring - the "pglogical.synchronous_commit". - -- Immediately forward all messages from the PGL receiver back to origin (BDR CAMO) - Confirmations for CAMO protected transactions flow - from the PGL writer applying the transaction back to origin node via - the PGL receiver. This process used to consume only one - confirmation message per iteration. It now consumes all pending - confirmations from the PGL writer and immediately sends them back to - the origin. It also decreases latency for BDR CAMO transactions in case - confirmations queue up. - -## pglogical 3.6.8 - -This is the eigth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Use RelationGetIndexAttrBitmap to get pkey columns. (RT65676, RT65797) - No need to try to fetch pkey columns from index itself, we have - relcache interface that does exactly what we need and does so - in more performant way. - -## pglogical 3.6.7.1 - -This is a hot-fix release on top of 3.6.7. - -### Resolved Issues - -- Fix a protocol violation after removal of an origin. (RT65671, RM10605) - Removal of a replication subscription may lead to a walsender trying - to forward data for unknown origins. Prevent emission of an invalid - message in that case. - -## pglogical 3.6.7 - -pglogical 3.6.7 is the seventh minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified earlier. - -### Improvements - -- Replicate TRUNCATE on a partition if only parent table is published in - replication set (RT65335) - Previously, we'd skip such TRUNCATE unless the partition was also published. -- Generate `target_table_missing` for TRUNCATE which is executed against - non-existing table (RT10291) - Allows for user-configured decision if it should be a replication-stopping - issue or not. -- Improve performance of repeated UPDATEs and DELETEs executed on origin node - by caching the replication configuration of tables in a user session. -- Reduce CPU usage of receiver worker when writer queue is full (RM10370). - -### Resolved Issues - -- Fix partition replication set membership detection for multi-level - partitioned tables - Replicate changes correctly for multi-level partitioned tables, where only - the intermediate partition is part of replication set (not root or leaf - partitions). -- Support replication `TRUNCATE CASCADE` on tables referenced by - `FOREIGN KEY` (RT65518) - Previously this would throw error on the subscriber. This will only work if - all tables on subscriber which have `FOREIGN KEY` on the table being - `TRUNCATEd` are replicated tables. Also it's only supported on - PostgreSQL 11 and higher. -- Flush writer between data copy and constraint restore - Otherwise there could in some rare cases still be unapplied changes when - creating constraints during initial synchronization of a subscription, - potentially causing deadlocks. -- Fix potential writer queue corruption on very wide (1000+ columns) tables - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -## pglogical 3.6.6 - -pglogical 3.6.6 is the sixth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified earlier. - -### Improvements - -- New conflict type `update_pkey_exists` (RM9976) - Allows resolving conflicts when a `PRIMARY KEY` was updated to one which - already exists on the node which is applying the change. - -- Add `pglogical.apply_log_summary` (RM6596) - View over `pglogical.apply_log` which shows the human-readable conflict - type and resolver string instead of internal id. - -- Improve logging during both the initial data synchronization of a - subscription and the individual table resynchronization. - -### Resolved Issues - -- Make sure writer flushes changes after initial data copy (RT65185) - Otherwise depending on timing and I/O load the subscription might not - update positioning info and get data both via initial copy and replication - stream catchup that follows. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -## pglogical 3.6.5 - -pglogical 3.6.5 is the fifth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.4. - -### Improvements - -- Improve tuple lock waits during apply for deletes (RM9569) - This should improve performance of replication of deletes and updates in - contentious situation. - -### Resolved Issues - -- Use consistent table list in initial data copy (RM9651/RT64809) - To prevent issues during initial data copy and concurrent table drop. -- Cleanup worker_dsm_handle on worker detach (internal) - Otherwise we could leave dangling DSM segment handle for a worker after a - crash, which could confuse plugins using this API. -- Fix handling of empty eager transactions (RM9550) - In case no relevant change remains to be applied on a replica node, - the prepare of such an empty transaction now works just fine. -- Fix the replication sets output in `pglogical.pglogical_node_info()` - Previously it could be garbled. -- Reduce log level for messages when resolving - ERRCODE_T_R_SERIALIZATION_FAILUREs (RM9439) - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -Note that upgrades from 2.2.x are only supported on systems with -`pglogical.conflict_resolution` set to `last_update_wins`. - -## pglogical 3.6.4 - -pglogical 3.6.4 is the fourth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.3. - -### New Features - -- Apply statistics tracking (RM9063) - We now track statistics about replication and resource use for individual - subscriptions and relations and make them available in - `pglogical.stat_subscription` and `pglogical.stat_relation` views. - The tracking can be configured via `pglogical.stat_track_subscription` and - `pglogical.stat_track_relation` configuration parameters. -- The `replicate_inserts` option now affects initial COPY - We now do initial copy of data only if the table replicates inserts. - -### Resolved Issues - -- Fix initial data copy of multi-level partitioned tables (RT64809) - The initial data copy used to support only single level partitioning, - multiple levels of partitioning are now supported. -- Don't try to copy initial data twice for partitions in some situations (RT64809) - The initial data copy used to try to copy data from all tables that are in - replication sets without proper regard to partitioning. This could result in - partition data to be copied twice if both root partition and individual - partitions were published via replication set. This is now solved, we only - do the initial copy on the root partition if it's published. -- Fix handling of indexes when replicating INSERT to a partition (RT64809) - Close the indexes correctly in all situations. -- Improve partitioning test coverage (RM9311) - In light of the partitioning related issues, increase the amount of - automated testing done against partitioned tables. -- Fix a leak in usage of the relation cache (RT64935) -- Fix a potential queue deadlock between writer and receiver (RT64935, RT64714) - -## pglogical 3.6.3 - -pglogical 3.6.3 is the third minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.2. - -### New Features - -- Support `DoNotReplicateId` special origin - This allows correct handling of "do not replicate" origin which allows skipping replication of some changes. Primarily needed internally for other features. -- Persist the last_xact_replay_timestamp (RT63881) - So that it's visible even if the subscription connection is down. -- Rework documentation build procedure for better consistency between HTML and PDF documentation - This mainly changes the way docs are structured into chapters so that there is single source of chapter list and ordering for both PDF and HTML docs. - -### Resolved Issues - -- Invalidate local cache when adding new invalidation - Fixes visibility of changes in the catalog cache view of the transaction which did those changes. Not triggered yet by any code but will be in the future releases. -- Open indexes after partition routing - Otherwise we might be opening indexes of the root table rather than the partition, causing issues with handling conflicts for `INSERT` operation replication. - -## pglogical 3.6.2 - -pglogical 3.6.2 is the second minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.1. - -### New Features - -- Support DEFERRED UNIQUE indexes - They used to work only in limited cases before this release. -- Support covering UNIQUE indexes (RT64650) - The use of covering UNIQUE indexes could result in ambiguous error messages in some cases before. -- Add `--log-file` option to `pglogical_create_subscriber` (RT64129) - So that log can be saved somewhere other than the current working directory - -### Resolved Issues - -- Fix error message when the database name in the connection string in `pglogical_create_subscriber` is missing (RT64129) - The previous message was ambiguous. -- Raise error when unknown parameter was specified for `pglogical_create_subscriber` (RT64129) - Otherwise mistakes in command line arguments could be silently ignored. -- Solve timing issue with workers exiting while another one tries to start using same worker slot - Before, we could corrupt the worker information causing the newly starting worker to crash (and having to start again later), this will no longer happen. -- Set statement time on start of every transaction in pglogical workers (RT64572) - Fixes reporting of `xact_start` in `pg_stat_activity` - -## pglogical 3.6.1 - -pglogical 3.6.1 is the first minor release of the pglogical 3.6 series. This release includes minor new features and fixes including all the fixes from 3.6.0.1. - -### New Features - -- Add slot failover documentation -- Add `pglogical.get_sub_progress_timestamp` for retrieving origin timestamp of the last committed change by the subscription - -### Resolved Issues - -- Stop retrying subscription synchronization after unrecoverable error (RT64463) - If the schema synchronization failed (which is an unrecoverable error) don't keep retrying forever. Instead mark the subscription synchronization as failed and disable the subscription. -- Improve handling and messaging with missing replication sets in output plugin (RT64451) - Report all missing and found sets and make sure the sets are looked up using current snapshot. - -## pglogical 3.6.0.1 - -The pglogical 3.6.0.1 is the first bug-fix release in the pglogical 3.6 series. - -### Resolved Issues - -- Improve synchronous `remote_write` replication performance (RT64397) -- Re-add support for binary protocol - -## pglogical 3.6.0 - -The version 3.6 of pglogical is a major update which brings performance improvements, better conflict handling, bug fixes and infrastructure necessary for BDR 3.6. - -### New Features - -- Significant replication performance improvement - - Cache table synchronization state - - Only send keepalives when necessary - - Only do flush when necessary - - Serialize transactions in fewer cases in walsender (2ndQPostgres) -- Improved replication position reporting which is more in line with how physical streaming replication reports it -- Conflict detection and resolution improvements - - Add new types of conflicts (like `target_table_missing`) - - Add new types of conflict resolvers - - Make conflict resolution configurable by subscription and conflict type - - Improve conflict detection for updates - -### Resolved Issues - -- Don't try to replicate REINDEX on temporary indexes - -### Other Improvements - -- Fix potential message parsing error for two-phase commits -- Make initial COPY of data interruptible diff --git a/product_docs/docs/pgd/3.6/pglogical/replication-sets.mdx b/product_docs/docs/pgd/3.6/pglogical/replication-sets.mdx deleted file mode 100644 index ef64beacdd0..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/replication-sets.mdx +++ /dev/null @@ -1,466 +0,0 @@ ---- -navTitle: Replication Sets -title: Replication sets -originalFilePath: replication-sets.md - ---- - -Replication sets provide a mechanism to control which tables in the database -will be replicated and which actions on those tables will be replicated. - -Each replicated set can specify individually if `INSERTs`, `UPDATEs`, -`DELETEs` and `TRUNCATEs` on the set are replicated. Every table can be in -multiple replication sets and every subscriber can subscribe to multiple -replication sets as well. The resulting set of tables and actions replicated -is the union of the sets the table is in. The tables are not replicated until -they are added into a replication set. - -There are three preexisting replication sets, named "default", -"default_insert_only" and "ddl_sql". The "default" replication set is defined -to replicate all changes to tables in it. The "default_insert_only" replication -set only replicates INSERTs and is meant for tables that don't have primary key -(see [Restrictions](restrictions) section for details). The "ddl_sql" replication -set is defined to replicate schema changes specified by the -`pglogical.replicate_ddl_command`. - -*Note: Table are **not** added automatically to the "default" replication set, -the name "default" just means it exists by default. This behavior can be -changed using `pglogical.alter_replication_set`.* - -## Behavior of partitioned tables - -From PostgreSQL 11 onwards, pglogical supports partitioned tables -transparently. This means that a partitioned table can be added to a replication -set and changes to any of the partitions will be replicated downstream. - -The partitioning definition on the subscription side can be set up differently to the -one on the provider. This means that one can also replicate a partitioned table to a -single table, or a single table to a partitioned table, or a partitioned tabled to a -differently'partitioned table (repartitioning). - -It's also possible to add individual partitions to the replication set, in -which case they will be replicated like regular tables (to the table of the -same name as the partition on the downstream). This has some performance -advantages in case the partitioning definition is same on both provider and -subscriber, as the partitioning logic does not have to be executed. - -**Note: If the root-partitioned table is part of any replication set, memberships -of individual partitions are ignored and only the membership of said root -table will be taken into account.** - -### Older versions of PostgreSQL - -In PostgreSQL 10 and older, pglogical only allows the replication of partitions -directly to other partitions. Which means the partitioned table itself cannot be -added to a replication set and can't be target of replication on the subscriber -either (one can't replicate a normal table to a partitioned table). - -## Replication set manipulation interfaces - -The following functions are provided for managing the replication sets: - -### pglogical.create_replication_set - - This function creates a new replication set. - -#### Synopsis - -```sql -pglogical.create_replication_set ( - set_name name, - replicate_insert boolean, - replicate_update boolean, - replicate_delete boolean, - replicate_truncate boolean, - autoadd_tables boolean, - autoadd_sequences boolean, - autoadd_existing boolean -) -``` - -#### Parameters - -- `set_name` - name of the set, must be unique -- `replicate_insert` - specifies if `INSERT` is replicated; default true -- `replicate_update` - specifies if `UPDATE` is replicated; default true -- `replicate_delete` - specifies if `DELETE` is replicated; default true -- `replicate_truncate` - specifies if `TRUNCATE` is replicated; default true -- `autoadd_tables` - specifies if newly created tables should be automatically - added to the new replication set; default false -- `autoadd_sequences` - specifies if newly created sequences should be automatically - added to the new replication set; default false -- `autoadd_existing` - this in combination with `autoadd_tables` or `autoadd_sequences` - specifies if any existing tables and sequences should be added as well - -The autoadd options will ignore tables that are in -`information_schema` or `pg_catalog` schemas or are part of an extension. - -The autoadd options will also allow automatic removal of tables from the -replication set. So there will be no dependency check on replication membership -when the table which is part of the autoadd replication set is being dropped. - -If you want to replicate tables which are part of some extension, you still -have to add them manually. - -### pglogical.alter_replication_set - -This function changes the parameters of the existing replication set. - -#### Synopsis - -```sql -pglogical.alter_replication_set ( - set_name name, - replicate_insert boolean, - replicate_update boolean, - replicate_delete boolean, - replicate_truncate boolean, - autoadd_tables boolean, - autoadd_sequences boolean -) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `replicate_insert` - specifies if `INSERT` is replicated -- `replicate_update` - specifies if `UPDATE` is replicated -- `replicate_delete` - specifies if `DELETE` is replicated -- `replicate_truncate` - specifies if `TRUNCATE` is replicated -- `autoadd_tables` - specifies if newly created tables should be automatically - added to the new replication set -- `autoadd_sequences` - specifies if newly created sequences should be automatically - added to the new replication set - -If any of these replication set parameters is NULL (which is the default -value if nothing else is specified), the current setting for that parameter will -remain unchanged. - -### pglogical.drop_replication_set - -Removes the replication set. - -#### Synopsis - -```sql -pglogical.drop_replication_set(set_name text) -``` - -#### Parameters - -- `set_name` - name of the existing replication set - -### pglogical.replication_set_add_table - -Adds a table to a specified existing replication set, optionally requesting -resynchronization by subscribers. - -#### Synopsis - -```sql -pglogical.replication_set_add_table ( - set_name name, - relation regclass, - synchronize_data boolean, - columns text[], - row_filter text -) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `relation` - name or OID of the table to be added to the set -- `synchronize_data` - if true, the table data is synchronized on all - subscribers which are subscribed to given replication set; default false -- `columns` - list of columns to replicate. Normally when all columns - should be replicated, this will be set to NULL which is the - default. -- `row_filter` - row filtering expression; default NULL (no filtering). - See [Row Filtering On Provider](#row-filtering-on-provider) for more info. - -**WARNING: Use caution when synchronizing data with a valid row filter.** -Using `synchronize_data=true` with a valid `row_filter` is like a one-time operation for a table. -Executing it again with a modified `row_filter` won't synchronize data to subscriber. Subscribers -may need to call `pglogical.alter_subscription_resynchronize_table()` to fix it. - -Also, note that if `synchronize_data` is enabled, a synchronization request is -scheduled on each subscriber and actioned asynchronously. Adding to the -replication set *does not wait for synchronization to complete*. - -To wait until the resync has completed, first, on the provider, run: - -```sql -SELECT pglogical.wait_slot_confirm_lsn(NULL, NULL); -``` - -To ensure each subscriber has received the request, then on each subscriber -run: - -```sql -SELECT pglogical.wait_for_subscription_sync_complete('sub_name'); -``` - -**NOTE**: There is currently no function to alter the row filter or columns of -a table's replication set membership (RM#5960). However, you can use a *single -transaction* to remove the table from the replication set and then re-add it with -the desired row filter and column filter. Make sure to set `synchronize_data := -false`. This provides a seamless transition from the old to the new membership -and will not skip or lose any rows from concurrent transactions. - -### pglogical.replication_set_add_all_tables - -Adds all tables in given schemas. - -#### Synopsis - -```sql -pglogical.replication_set_add_all_tables ( - set_name name, - schema_names text[], - synchronize_data boolean -) -``` - -Only existing tables are added; any tables created later will not -be added automatically. To see how to automatically add tables -to the correct replication set at creation time, see -[Automatic assignment of replication sets for new tables](#automatic-assignment-of-replication-sets-for-new-tables). - -#### Parameters - -- `set_name` - name of the existing replication set -- `schema_names` - array of names name of existing schemas from which tables - should be added -- `synchronize_data` - if true, the table data is synchronized on all - subscribers which are subscribed to the given replication set; default false - -### pglogical.replication_set_remove_table - -Removes a table from a specified existing replication set. - -#### Synopsis - -```sql -pglogical.replication_set_remove_table(set_name name, relation regclass) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `relation` - name or OID of the table to be removed from the set - -### pglogical.replication_set_add_sequence - -Adds a sequence to a replication set. - -#### Synopsis - -```sql -pglogical.replication_set_add_sequence ( - set_name name, - relation regclass, - synchronize_data boolean -) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `relation` - name or OID of the sequence to be added to the set -- `synchronize_data` - if true, the sequence value will be synchronized immediately; default false - -### pglogical.replication_set_add_all_sequences - -Adds all sequences from the given schemas. - -#### Synopsis - -```sql -pglogical.replication_set_add_all_sequences ( - set_name name, - schema_names text[], - synchronize_data boolean -) -``` - -Only existing sequences are added; any sequences created later will not -be added automatically. - -#### Parameters - -- `set_name` - name of the existing replication set -- `schema_names` - array of names of existing schemas from which tables - should be added -- `synchronize_data` - if true, the sequence value will be synchronized - immediately; default false - -### pglogical.replication_set_remove_sequence - -Remove a sequence from a replication set. - -#### Synopsis - -```sql -pglogical.replication_set_remove_sequence(set_name name, relation regclass) -``` - -#### Parameters - -- `set_name` - name of the existing replication set -- `relation` - name or OID of the sequence to be removed from the set - -You can view the information about which table is in which set by querying the -`pglogical.tables` view. - -## Automatic assignment of replication sets for new tables - -The event trigger facility can be used for describing rules which define -replication sets for newly created tables. - -Example: - -```sql -CREATE OR REPLACE FUNCTION pglogical_assign_repset() -RETURNS event_trigger AS $$ -DECLARE obj record; -BEGIN - FOR obj IN SELECT * FROM pg_event_trigger_ddl_commands() - LOOP - IF obj.object_type = 'table' THEN - IF obj.schema_name = 'config' THEN - PERFORM pglogical.replication_set_add_table('configuration', obj.objid); - ELSIF NOT obj.in_extension THEN - PERFORM pglogical.replication_set_add_table('default', obj.objid); - END IF; - END IF; - END LOOP; -END; -$$ LANGUAGE plpgsql; - -CREATE EVENT TRIGGER pglogical_assign_repset_trg - ON ddl_command_end - WHEN TAG IN ('CREATE TABLE', 'CREATE TABLE AS') - EXECUTE PROCEDURE pglogical_assign_repset(); -``` - -The above example will put all new tables created in schema `config` into -replication set `configuration` and all other new tables which are not created -by extensions will go to the `default` replication set. - -## Additional functions - -### pglogical.synchronize_sequence - -Push sequence state to all subscribers. - -#### Synopsis - -```sql -pglogical.synchronize_sequence(relation regclass) -``` - -Unlike the subscription and table -synchronization function, this function should be run on the provider. It forces -an update of the tracked sequence state which will be consumed by all -subscribers (replication set filtering still applies) once they replicate the -transaction in which this function has been executed. - -#### Parameters - -- `relation` - name of existing sequence, optionally qualified - -## Row Filtering on Provider - -On the provider side, row filtering can be done by specifying the `row_filter` -parameter for the `pglogical.replication_set_add_table` function. The -`row_filter` is a normal PostgreSQL expression with the same limitations as a -[`CHECK` constraint](https://www.postgresql.org/docs/current/static/ddl-constraints.html#DDL-CONSTRAINTS-CHECK-CONSTRAINTS). - -You can see which row filters are active in the `pglogical.tables` view. - -The table's column(s) are exposed to the row filter as simple identifiers; -there's no qualifier or namespace. - -Unlike a CHECK constraint's body, the row-filter is passed as a string which is -parsed and checked by pglogical. So to avoid quoting issues you should use -PostgreSQL's dollar-quoting, like this: - -```sql -SELECT pglogical.replication_set_add_table( -'setname', 'tblname'::regclass, -synchronize_data := false, -row_filter := $FILTER$ id > 0 $FILTER$ -); -``` - -A simple `row_filter` would look something like `row_filter := 'id > 0'` which -would replicate only those rows where values of column `id` are greater than zero. -This *will not affect any already-committed rows pending -replication, or any already-replicated rows*. - -**Important**: Caveats apply when re-synchronizing tables with row filters -using `replication_set_add_table`. See `pglogical.replication_set_add_table`. - -### Writing safer row filters - -Be very cautious when writing row filter expressions, and keep them as simple -as possible. If a row-filter expression raises an error during replication, it -is generally necessary to drop and re-create the subscription, resynchronizing -*all* tables, not just the table with the problem row-filter. So row filters -should be simple and defensively written. A non-exhaustive list of rules for -writing filters is that they: - -- *Should* be simple expressions wherever possible. Try to use only - built-in PostgreSQL operators and `IMMUTABLE` functions if you can. - -- *Must* avoid using any expression that could raise an `ERROR` at runtime, - such as casting from `text` to a more strictly validated data type. They - must tolerate any value that the table's constraints permit to appear in - the table. - -- *May* use `VOLATILE` or `STABLE` functions, but any functions must obey the - same constraints as the filter expression itself. - - E.g. you can call `random()` but not `txid_current()` or - `my_audit_log_function()`. - -- *May* call user-defined functions written in SQL, Pl/PgSQL, or (with care) C. - Use of other languages is untested and not recommended. PL/PgSQL functions - *must not* use `EXCEPTION` blocks, and may have other as-yet-undiscovered - issues so their use is not recommended. Stick to SQL where possible. - -- *Should not* attempt to access any tables. Only the column values should - be used. - - Direct use of subqueries in the row-filter expression is blocked. - - It's possible to call a user-defined function within the filter, and that - *can* access table contents. This is *not recommended* and may be subject to - surprising behaviour. The function *must* only access tables in - `pg_catalog.*` or tables marked with the `user_catalog_table=true` attribute. - Accessing other tables will not raise an error, but may cause undefined - behaviour, errors, or crashes. - -- *Must never* attempt any write operation or anything that assigns a - transaction-id. Similar to queries on a read-replica. Attempting writes - will break replication. - -- *May* safely use columns of the filtered table that are not part of the - replication set's column list. Filtering happens on the provider side - so non-replicated columns will have their values accessible. This lets - you do things like pre-compute complex filter criteria in triggers. - -- *Should not* rely on session state, since the `row_filter` is running inside - the replication session. Session specific expressions such as - `CURRENT_USER` will have values of the replication session and not the session - which did the writes. The same is true for GUCs etc. - -### Changing row filters - -To change a row-filter expression on a table, use a single transaction to remove the -table from the replication set, then add it again with the new row filter expression. -Do not specify data sync and make sure to explicitly repeat the set of replicated -columns. You can check the `pglogical.tables` view for the old column set and row filter. - -See `pglogical.replication_set_add_table`. diff --git a/product_docs/docs/pgd/3.6/pglogical/restrictions.mdx b/product_docs/docs/pgd/3.6/pglogical/restrictions.mdx deleted file mode 100644 index 204f46d5070..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/restrictions.mdx +++ /dev/null @@ -1,114 +0,0 @@ ---- -title: Restrictions -originalFilePath: restrictions.md - ---- - -pglogical currently has the following restrictions or missing functionality. -These might be addressed in future releases. - -## Superuser is required - -Currently pglogical replication and administration requires superuser -privileges. It may be later extended to more granular privileges. - -## UNLOGGED and TEMPORARY not replicated - -`UNLOGGED` and `TEMPORARY` tables will not and cannot be replicated, similar to -physical streaming replication. - -## One database at a time - -To replicate multiple databases you must set up individual provider/subscriber -relationships for each. There is no way to configure replication for all databases -in a PostgreSQL install at once. - -## PRIMARY KEY or REPLICA IDENTITY required - -When replicating `UPDATE`s and `DELETE`s for tables that lack a `PRIMARY -KEY`, the `REPLICA IDENTITY` must be set to `FULL`. However it's important -to note that without `PRIMARY KEY` every `UPDATE` or `DELETE` will produce a -sequential scan on a table which will have severe detrimental effect on -performance of replication and subsequently the replication lag. - -Note: On regular PostgreSQL nodes it's only possible to set the -`REPLICA IDENTITY` to `FULL` via `ALTER TABLE`, however on pglogical nodes -tables can be created with `REPLICA IDENTITY FULL` directly using the following -syntax: - -```sql -CREATE TABLE name (column_a int) WITH (replica_identity = full); -``` - -See for details on replica identity. - -## DDL - -There are several limitations of DDL replication in pglogical, for details -check the [DDL Replication](ddl) chapter. - -## Sequences - -The state of sequences added to replication sets is replicated periodically -and not in real-time. A dynamic buffer is used for the value being replicated so -that the subscribers actually receive the future state of the sequence. This -minimizes the chance of the subscriber's notion of the sequence's last_value -falling behind but does not completely eliminate the possibility. - -It might be desirable to call `synchronize_sequence` to ensure all subscribers -have up to date information about a given sequence after "big events" in the -database such as data loading or during the online upgrade. - -The types bigserial and bigint are recommended for sequences on multi-node -systems as smaller sequences might reach the end of the sequence space fast. - -Users who want to have independent sequences on the provider and subscriber can -avoid adding sequences to replication sets and create sequences with a step -interval equal to or greater than the number of nodes, and then set a different -offset on each node. Use the `INCREMENT BY` option for `CREATE SEQUENCE` or -`ALTER SEQUENCE`, and use `setval(...)` to set the start point. - -## PostgreSQL Version differences - -PGLogical can replicate across PostgreSQL major versions. Despite that, long -term cross-version replication is not considered a design target, though it may -often work. Issues where changes are valid on the provider but not on the -subscriber are more likely to arise when replicating across versions. - -It is safer to replicate from an old version to a newer version since PostgreSQL -maintains solid backward compatibility but only limited forward compatibility. -Initial schema synchronization is only supported when replicating between the -same version of PostgreSQL or from lower version to a higher version. - -Replicating between different minor versions makes no difference at all. - -### pglogical.pglogical_version - -This function retrieves the textual representation of the PGL version that is currently in use. - -```sql -SELECT pglogical.pglogical_version(); -``` - -### pglogical.pglogical_version_num - -This function retrieves a numerical representation of the PGL version that is currently in use. -Version numbers are monotonically increasing, allowing this value to be used for less-than and greater-than comparisons. - -## Database encoding differences - -PGLogical does not support replication between databases with different -encoding. We recommend using `UTF-8` encoding in all replicated databases. - -## Large objects - -PostgreSQL's logical decoding facility does not support decoding changes -to large objects, so pglogical cannot replicate Large Objects. This does -not restrict the use of large values in normal columns. - -## Additional restrictions - -Please node that additional restrictions may apply depending on which -writer is being used and which version of PostgreSQL is being -used. These additional restrictions are documented in their respective -sections (ie., every writer documents it's own additional restrictions). diff --git a/product_docs/docs/pgd/3.6/pglogical/subscriptions/index.mdx b/product_docs/docs/pgd/3.6/pglogical/subscriptions/index.mdx deleted file mode 100644 index 3d929cbcf73..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/subscriptions/index.mdx +++ /dev/null @@ -1,957 +0,0 @@ ---- -navigation: - - subscriptions - - pglogical-writer -navTitle: Subscriptions -title: Subscription Overview -originalFilePath: subscriptions.md - ---- - -A subscription is the receiving side (or downstream) of the pglogical -replication setup. Just like on the upstream, the subscription first needs -local node to be created (see [#Nodes](nodes)). - -## Subscription information - -## pglogical.stat_subscription - -Apply statistics for each subscription. Only contains data if the tracking -is enabled. - -## `pglogical.stat_subscription` Columns - -| Column | Type | Description | -| -------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------- | -| sub_name | name | Name of the subscription | -| subid | oid | Oid of the subscription | -| nconnect | bigint | Number of times this subscription has connected upstream | -| ncommit | bigint | Number of commits this subscription did | -| nabort | bigint | Number of aborts writer did for this subscription | -| nerror | bigint | Number of errors writer has hit for this subscription | -| nskippedtx | bigint | Number of transactions skipped by writer for this subscription (currently normally 0 for pgl subscription) | -| ninsert | bigint | Number of inserts this subscription did | -| nupdate | bigint | Number of updates this subscription did | -| ndelete | bigint | Number of deletes this subscription did | -| ntruncate | bigint | Number of truncates this subscription did | -| nddl | bigint | Number of DDL operations this subscription has executed | -| ndeadlocks | bigint | Number of errors that were caused by deadlocks | -| nretries | bigint | Number of retries the writer did (without going for full restart/reconnect) | -| shared_blks_hit | bigint | Total number of shared block cache hits by the subscription | -| shared_blks_read | bigint | Total number of shared blocks read by the subscription | -| shared_blks_dirtied | bigint | Total number of shared blocks dirtied by the subscription | -| shared_blks_written | bigint | Total number of shared blocks written by the subscription | -| blk_read_time | double precision | Total time the subscription spent reading blocks, in milliseconds (if `track_io_timing` is enabled, otherwise zero) | -| blk_write_time | double precision | Total time the subscription spent writing blocks, in milliseconds (if `track_io_timing` is enabled, otherwise zero) | -| connect_time | timestamp with time zone | Time when the current upstream connection was established, NULL if not connected | -| last_disconnect_time | timestamp with time zone | Time when the last upstream connection was dropped | -| start_lsn | pg_lsn | LSN from which this subscription requested to start replication from the upstream | -| retries_at_same_lsn | bigint | Number of attempts the subscription was restarted from the same LSN value | -| curr_ncommit | bigint | Number of commits this subscription did after the current connection was established | - -## `pglogical.stat_relation` - -Apply statistics for each relation. Only contains data if the tracking -is enabled and something was replicated for a given relation. - -## `pglogical.stat_relation` Columns - -| Column | Type | Description | -| ------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------- | -| nspname | name | Name of the relation's schema | -| relname | name | Name of the relation | -| relid | oid | OID of the relation | -| total_time | double precision | Total time spent processing replication for the relation | -| ninsert | bigint | Number of inserts replicated for the relation | -| nupdate | bigint | Number of updates replicated for the relation | -| ndelete | bigint | Number of deletes replicated for the relation | -| ntruncate | bigint | Number of truncates replicated for the relation | -| shared_blks_hit | bigint | Total number of shared block cache hits for the relation | -| shared_blks_read | bigint | Total number of shared blocks read for the relation | -| shared_blks_dirtied | bigint | Total number of shared blocks dirtied for the relation | -| shared_blks_written | bigint | Total number of shared blocks written for the relation | -| blk_read_time | double precision | Total time spent reading blocks for the relation, in milliseconds (if `track_io_timing` is enabled, otherwise zero) | -| blk_write_time | double precision | Total time spent writing blocks for the relation, in milliseconds (if `track_io_timing` is enabled, otherwise zero) | -| lock_acquire_time | double precision | Total time spent acquiring locks on the relation (if `pglogical.track_apply_lock_timing` is enabled, otherwise zero) | - -## `pglogical.replication_status` - -Replication status view for each subscription. We consider replication -to be blocked when the subscription has restarted from the same LSN at -least twice and not a single transaction is yet applied after the -current upstream connection was established. If the very first -transaction after restart is very big and still being applied, the -`replication_blocked` result maybe wrong. - -## `pglogical.replication_status` Columns - -| Column | Type | Description | -| ------------------- | ------------------------ | ------------------------------------------------ | -| sub_name | name | Name of the subscription | -| connected | boolean | Is the subscription connected to the upstream? | -| replication_blocked | boolean | Is the replication currently blocked? | -| connect_time | timestamp with time zone | Time when the current connection was established | -| disconnect_time | timestamp with time zone | Time when the last connection was dropped | -| uptime | interval | Duration since the current connection is active | - -## pglogical.local_sync_status - -An updated view of the synchronization locally. Columns include subscription ID, sync status and kind. - -## pglogical.show_workers - -A function to bring the user information of the worker PID, role and subscription ID. - -## SQL interfaces - -### pglogical.create_subscription - -Creates a subscription from the current node to the provider node. Command -does not block, just initiates the action. - -#### Synopsis - -```sql -pglogical.create_subscription ( - subscription_name name, - provider_dsn text, - replication_sets text[], - synchronize_structure boolean, - synchronize_data boolean, - create_slot boolean, - slot_name text, - forward_origins text[], - strip_origins boolean, - num_writers int, - apply_delay interval, - writer name, - writer_options text[] -) -``` - -The `subscription_name` is used as `application_name` by the replication -connection. This means that it's visible in the `pg_stat_replication` -monitoring view. It can also be used in `synchronous_standby_names` when -pglogical is used as part of the synchronous replication setup. - -Subscription setup is asynchronous. `pglogical.create_subscription` returns -after creating the replication slot (unless `create_slot` is false) but -before the subscription is synchronized and streaming. Use -`pglogical.wait_for_subscription_sync_complete` to wait until the subscription -is up and has completed any requested schema and/or data sync. - -`synchronize_structure` internally uses `pg_dump` and `pg_restore` to copy schema -definitions. If more than one upstream is being subscribed to, only use -`synchronize_data` on the first one, because it cannot de-duplicate schema -definitions. - -`synchronize_data` internally uses `COPY` to unload and load the data -from the provider. - -If both `synchronize_structure` and `synchronize_data` are used, take care to -create table definitions, then copy data, and only create indexes etc. at the end. - -**Note**: An alternative to `pglogical.create_subscription` is the -`pglogical_create_subscriber` tool, which takes a `pg_basebackup` or uses a -pre-existing streaming replica of the provider node and converts it into a new -logical replica. It's often much faster where network bandwidth is sufficient, -but cannot filter the initial dump to exclude some databases/tables/etc. - -**Note**: `pglogical.create_subscription` will appear to hang (it will wait -indefinitely without returning) if the database pointed to by `provider_dsn` is -on the same PostgreSQL instance as the subscriber and `create_slot` is true. -This happens because the replication slot creation command on the provider -waits for all transactions that were in-progress at the time it started to -commit, but the transaction running `pglogical.create_subscription` cannot -commit until after the create replication slot command returns, so the two -deadlock. The PostgreSQL deadlock detector does not identify this condition as -it is not a deadlock on heavyweight locks, and is not visible in the `pg_locks` -view. To make this fairly uncommon use case work, manually create a logical -replication slot for the pglogical subscription on the provider using the -`'pglogical_output'` output plugin, e.g. - -```sql -SELECT pg_catalog.create_logical_replication_slot( -pglogical.gen_slot_name( -'SUBSCRIBER_DBNAME', -'PROVIDER_NODE_NAME', -'SUBSCRIPTION_NAME' -), 'pglogical_output'); -``` - -then specify `create_slot := false` to `pglogical.create_subscription()`. You may -alternately choose your own replication slot name instead of using -`gen_slot_name` then pass it as the `slot_name` parameter to -`create_subscription`. - -#### Parameters - -- `subscription_name` - name of the subscription; must be unique -- `provider_dsn` - connection string to a provider -- `replication_sets` - array of replication sets to subscribe to, these must - already exist, default is "{default,ddl_sql}" -- `synchronize_structure` - specifies if to synchronize structure from - provider to the subscriber; default false -- `synchronize_data` - specifies if to synchronize data from provider to - the subscriber; default true -- `create_slot` - set to false to suppress automatic creation of a logical - replication slot on the provider in order to use a pre-created one; default true -- `slot_name` - override the autogenerated replication slot name pglogical - generates in order to supply your own; default is same as that generated by - `pglogical.pglogical_gen_slot_name()` -- `forward_origins` - array of replication origin names to forward. Currently the only - supported values are: an empty array meaning don't forward any changes - that didn't originate on provider node (this is useful for two-way - replication between the nodes); or "{all}" which means replicate all - changes no matter what is their origin. The default is "{all}" -- `apply_delay` - how much to delay replication; default is 0 seconds. - Mainly used for application testing, but also useful for delayed - standbys. -- `forward_origins` - array of origin names to forward; currently only - supported values are empty array meaning don't forward any changes - that didn't originate on provider node (this is useful for two-way - replication between the nodes), or "{all}" which means replicate all - changes no matter what is their origin; default is "{all}" -- `apply_delay` - how much to delay replication; default is 0 seconds -- `strip_origins` - determines whether to remove origin names from - forwarded data, making it look like the data originate from local node, - and allowing to forward the data to a subscription in the same instance - (default is "false" which keeps origin info). The negative effect is - it makes it impossible to redirect the subscription to the first node. -- `num_writers` - number of parallel writers for this subscription, -1 - means the subscription will use the default as specified by the GUC - pglogical.writers_per_subscription. Valid values are either -1 or a - positive integer. -- `writer` - which writer to use for writing the data from the replication - stream. Only `HeapWriter` is supported in this version of PGLogical. - `local` is an alias for backwards compatibility. -- `writer_options` - writer-specific options as an array of keys and values - -### `pglogical_create_subscriber` - -`pglogical_create_subscriber` isn't a SQL function, it's a standalone command -that provides an alternative way to create a subscriber. By default it will -take a `pg_basebackup` of the provider node and convert that into a `pglogical` -subscriber. - -This can be a lot faster than `pglogical.create_subscription` where network and -disk bandwidth is sufficient. However, it cannot filter out individual tables -or table subsets, and it copies all databases whether or not they are intended -for use with pglogical. It does not respect replication sets for the initial -data copy. Unlike `pglogical.create_subscription`, it copies indexes rather -than rebuilding them on the subscriber side. - -It may be necessary to specify a customized `postgresql.conf` and/or `pg_hba.conf` -for the copied node. In particular, you *must* copy the provider's `postgresql.conf` -and edit it to change the `port` if you plan on creating a subscriber on the same -host, where the port number would otherwise conflict. - -`pglogical_create_subscriber` may also be used to convert an existing, running -streaming replica of the provider into a subscriber. This lets the user clone -the provider using alternative methods like `pg_start_backup()`, `rsync`, and -`pg_stop_backup()`, or from a SAN snapshot. This conversion is done -automatically when the target data directory is non-empty and instead contains -a suitable PostgreSQL streaming replica. - -#### Synopsis - -```sql -pglogical_create_subscriber [OPTION]... -``` - -#### Options - -##### General Options - -- `-D, --pgdata=DIRECTORY` - data directory to be used for new node; - can be either empty/non-existing directory, - or directory populated using - pg_basebackup -X stream command -- `--databases` - optional list of databases to replicate -- `-n, --subscriber-name=NAME` - name of the newly created subscriber -- `--subscriber-dsn=CONNSTR` - connection string to the newly created subscriber -- `--provider-dsn=CONNSTR` - connection string to the provider -- `--replication-sets=SETS` - comma separated list of replication set names -- `--apply-delay=DELAY` - apply delay in seconds (by default 0) -- `--drop-slot-if-exists` - drop replication slot of conflicting name -- `-s, --stop` - stop the server once the initialization is done -- `-v` - increase logging verbosity -- `--extra-basebackup-args` - additional arguments to pass to pg_basebackup. - Safe options: `-T, -c, --xlogdir/--waldir` - -##### Configuration Files Override - -- `--hba-conf` - path to the new pg_hba.conf -- `--postgresql-conf` - path to the new postgresql.conf - -**WARNING: pglogical will always overwrite the `recovery.conf`, this behavior -will be fixed in the next release.** - -### pglogical.drop_subscription - -Disconnects the subscription and removes it from the catalog. - -#### Synopsis - -```sql -pglogical.drop_subscription ( - subscription_name name, - ifexists bool -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `ifexists` - if true, error is not thrown when subscription does not exist; - default is false - -### pglogical.alter_subscription_disable - - Disables a subscription and disconnects it from the provider. - -#### Synopsis - -```sql -pglogical.alter_subscription_disable ( - subscription_name name, - immediate bool -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `immediate` - if true, the subscription is stopped immediately, otherwise - it will be only stopped at the end of the current transaction; default is false - -### pglogical.alter_subscription_enable - -Enables disabled subscription. - -```sql -pglogical.alter_subscription_enable(subscription_name name, immediate bool) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `immediate` - if true, the subscription is started immediately, otherwise - it will be only started at the end of current transaction; default is false - -### pglogical.alter_subscription_num_writers - -Changes the number of writers for a subscription. - -```postgresql -pglogical.alter_subscription_num_writers(subscription_name name, num_writers int, immediate bool) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `num_writers` - number of writers for this subscription, -1 means the - subscription will use value set by pglogical.writers_per_subscription GUC -- `immediate` - if true, the subscription is started immediately, otherwise - it will be only started at the end of current transaction, default is false - -### pglogical.alter_subscription_interface - -Switch the subscription to use a different interface to connect to the provider node. -This is how you change the address, port etc that a subscription uses when connecting -to a provider. - -See [`pglogical.alter_node_create_interface()`](nodes#pglogical_alter_node_add_interface) -for usage. - -#### Synopsis - -```sql -pglogical.alter_subscription_interface ( - subscription_name name, - interface_name name -) -``` - -#### Parameters - -- `subscription_name` - name of an existing subscription -- `interface_name` - name of an existing interface of the current provider - node - -### pglogical.alter_subscription_synchronize - -All unsynchronized tables in all sets are synchronized in a single operation. - -#### Synopsis - -```sql -pglogical.alter_subscription_synchronize ( - subscription_name name, - truncate bool -) -``` - -Tables are copied and synchronized one by one. Command does not block, just -initiates the action. - -Use `pglogical.wait_for_subscription_sync_complete('sub_name')` to wait for -the resynchronization to complete. - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `truncate` - if true, tables will be truncated before copy; default false - -### pglogical.alter_subscription_resynchronize_table - -Asynchronously resynchronize one existing table. - -**WARNING: This function will truncate the table first.** The table will be -visibly empty to transactions between when the resync is scheduled and -when it completes. - -Use `pglogical.wait_for_subscription_sync_complete('sub_name')` to wait for all -pending resynchronizations to complete, or -`pglogical.wait_for_table_sync_complete` for just the named table. - -#### Synopsis - -```sql -pglogical.alter_subscription_resynchronize_table ( - subscription_name name, - relation regclass -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `relation` - name of existing table, optionally qualified - -### pglogical.show_subscription_status - -Shows status and basic information about a subscription. - -```sql -pglogical.show_subscription_status (subscription_name name) -``` - -#### Parameters - -- `subscription_name` - optional name of the existing subscription, when no - name was provided, the function will show status for all subscriptions on - local node - -### pglogical.show_subscription_table - -Shows the synchronization status of a table. - -#### Synopsis - -```sql -pglogical.show_subscription_table ( - subscription_name name, - relation regclass -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `relation` - name of existing table, optionally qualified - -### pglogical.show_subscription_clock_drift - -Shows clock drift between provider and subscriber. - -On the subscriber at apply time, we track the commit timestamp -received from the provider and the current local timestamp. When -the above function is invoked, we generate a diff (interval) of -these values. A negative value will indicate clock drift. - -```sql -pglogical.show_subscription_clock_drift (subscription_name name) -``` - -#### Parameters - -- `subscription_name` - optional name of the existing subscription; when no - name is provided, the function will show clock drift information for all - subscriptions on the local node - -### pglogical.alter_subscription_add_replication_set - -Adds one replication set into a subscriber. Does not synchronize, only -activates consumption of events. - -#### Synopsis - -```sql -pglogical.alter_subscription_add_replication_set ( - subscription_name name, - replication_set name -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `replication_set` - name of replication set to add - -### pglogical.alter_subscription_remove_replication_set - -Removes one replication set from a subscriber. - -#### Synopsis - -```sql - pglogical.alter_subscription_remove_replication_set ( - subscription_name name, - replication_set name -) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription -- `replication_set` - name of replication set to remove - -### pglogical.wait_for_subscription_sync_complete - -Wait on the subscriber side until the named subscription is fully synchronized. -The function waits for both the initial schema and data syncs (if any) and any -currently outstanding individual table resyncs. - -To ensure that this function sees and waits for pending resynchronizations -triggered by provider-side replication set changes, make sure to -`pglogical.wait_slot_confirm_lsn(NULL, NULL)` on the provider after any -replication set changes. - -#### Synopsis - -```sql - pglogical.wait_for_subscription_sync_complete( - subscription_name name - ) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription to wait for - -### pglogical.wait_for_table_sync_complete - -Same as `pglogical.wait_for_subscription_sync_complete`, except that -it waits for the subscription to be synced and for exactly one named table, -which must exist on the downstream. You can use this variant to wait for -a specific table resync to complete while ignoring other pending resyncs. - -#### Synopsis - -```sql - pglogical.wait_for_table_sync_complete( - subscription_name name, - relid regclass - ) -``` - -#### Parameters - -- `subscription_name` - name of the existing subscription to wait for -- `relid` - possibly schema-qualified relation name (cast to regclass if needed) - for the relation to wait for sync completion of. - -### `pglogical.wait_slot_confirm_lsn(name, pg_lsn)` - -On a pglogical provider, wait for the specified replication slot(s) to pass -all the requested WAL position. - -Note that to wait for a subscriber this function should be called on the -*provider*, not the subscriber. - -Waits for one specified slot if named explicitly, or all logical slots that use -the pglogical output plugin if the slot name is null. - -If no position is supplied the current WAL write position on the Pg instance -this function is called on is used. - -No timeout is offered, use a `statement_timeout`. - -This function can only wait for physical slots and for logical slots with -output plugins other than 'pglogical' if specified as a single named slot -argument. - -For physical slots the LSN waited for is the `restart_lsn`, because -physical slots don't have the same two-phase advance as logical slots -and they have a NULL `confirmed_flush_lsn`. Because physical standbys -guarantee durability (flush) before visibility (replay), if you want -to ensure transactions are actually visible you should call -`pglogical.standby_wait_replay_upstream_lsn` on the standby instead. - -Waiting with default (null) position can cause delays on idle systems -because the slot position may not advance until the next standby status -update if there are no further txns to replay. If you can ensure there will -be are no concurrent transactions you can instead capture -`pg_current_wal_insert_lsn()` after the writes you are interested in but -before you commit the transaction, then wait for that. Ideally commit would -report the commit lsn, and you could wait for that, but Pg doesn't do that -yet. Doing this may lead to waits ending prematurely if there are concurrent -txns, so only do it on test harness setups that do only one thing at a time. - -#### Synopsis - -```sql - SELECT pglogical.wait_slot_confirm_lsn( - slotname name, - target_lsn pg_lsn - ); -``` - -Typically it's sufficient to use: - -```sql -SELECT pglogical.wait_slot_confirm_lsn(NULL, NULL); -``` - -to wait until all pglogical (and bdr3) subscriber replication slots' -`confirmed_flush_lsn`s have confirmed a successful flush to disk of all WAL -that was written on the provider as of the start of the -`pglogical.wait_slot_confirm_lsn` call. - -#### Parameters - -- `slotname` - name of the replication slot to wait for, or NULL for all - pglogical slots -- `target_lsn` - xlog position to wait for slots to confirm, or NULL for current - xlog insert location. - -### `pglogical.standby_wait_replay_upstream_lsn(pg_lsn)` - -On a physical streaming replica (hot standby), wait for the -standby to replay WAL from the upstream up to or past the -specified lsn before returning. - -Does not support an explicit timeout. Use a `statement_timeout`. - -ERRORs if called on a non-standby, or when a standby is promoted -while waiting. - -Use this where you need to guarantee that changes are replayed and -visible on a replica, not just safe on disk. The sender-side function -`pglogical.wait_slot_confirm_lsn()` only ensures durability, not -visibility, when applied to physical replicas, because there's -no guarantee the flushed WAL is replayed and commits become visible -before the flush position is reported to the upstream. - -This is effectively a convenience function for a loop over -`pg_last_wal_replay_lsn()` for use in testing. - -### pglogical.alter_subscription_skip_changes_upto - -Because logical replication can replicate across versions, doesn't replicate -global changes like roles, and can replicate selectively, sometimes the logical -replication apply process can encounter an error and stop applying changes. - -Wherever possible such problems should be fixed by making changes to the -subscriber side. `CREATE`ing any missing table that's blocking replication, -`CREATE` a needed role, `GRANT` a necessary permission, etc. But occasionally a -problem can't be fixed that way and it may be necessary to skip entirely over a -transaction. - -There's no support in pglogical for skipping over only parts of a transaction, -i.e. subscriber-side filtering. Changes are skipped as entire transactions, -all or nothing. To decide where to skip to, use log output to find the commit -LSN, per the example below, or peek the change stream with the logical decoding -functions. - -Unless a transaction only made one change, it's often necessary to manually -apply the transaction's effects on the downstream side, so it's important to -save the problem transaction whenever possible. See the example below. - -It's possible to skip over changes without -`pglogical.alter_subscription_skip_changes_upto` by using -`pg_catalog.pg_logical_slot_get_binary_changes` to skip to the LSN of interest, -so this is really a convenience function. It does do a faster skip; however, it -may bypass some kinds of errors in logical decoding. - -This function only works on disabled subscriptions. - -The usual sequence of steps is: - -- identify the problem subscription and LSN of the problem commit -- disable the subscription -- save a copy of the transaction(s) using `pg_catalog.pg_logical_slot_peek_changes` *on the provider* (if possible) -- `pglogical.alter_subscription_skip_changes_upto` on the subscriber -- apply repaired or equivalent changes on the subscriber manually if necessary -- re-enable the subscription - -**WARNING**: It's easy to make problems worse when using this function. Don't -do anything unless you're really, really sure it's the only option. - -#### Synopsis - -```sql - pglogical.alter_subscription_skip_changes_upto( - subname text, - skip_upto_and_including pg_lsn - ); -``` - -#### Example - -Apply of a transaction is failing with an ERROR, and you've determined that -lower-impact fixes such as changes to the subscriber side will not resolve this -issue. You determine that you must skip the transaction. - -In the error logs, find the commit record LSN to skip to, as in this -artificial example: - -```shell - ERROR: 55000: pglogical target relation "public.break_me" does not exist - CONTEXT: during apply of INSERT in commit before 0/1B28848, xid 670 committed - ^^^^^^^^^^^^^^^^^^^^^^^^^^ - this LSN - at 2018-07-03 14:28:48.58659+08 (action #2) from node replorigin 1 -``` - -and if needed use the `pglogical.subscriptions` view to map the origin back to -a subscription name, e.g.: - -```sql -SELECT subscription_name, slot_name -FROM pglogical.subscriptions s -WHERE replication_origin_id = 1 -``` - -Next, disable the subscription so the apply worker doesn't try to connect to the replication slot: - -```sql -SELECT pglogical.alter_subscription_disable('the_subscription'); -``` - -Note that you cannot skip only parts of the transaction, it's all or nothing. So -it's strongly recommended that you save a record of it by `COPY`ing it out on the -provider side first, using the subscription's slot name (as obtained above). - -```sql - \copy (SELECT * FROM pg_catalog.pg_logical_slot_peek_changes('the_slot_name', - 'the_target_lsn', NULL, 'min_proto_version', '1', 'max_proto_version', '1', - 'startup_params_format', '1', 'proto_format', 'json') - TO 'transaction_to_drop.csv' WITH (FORMAT csv); -``` - -*(Note that the example is broken into multiple lines for readability, -but it should be issued in a single line because `\copy` does not -support multi-line commands)* - -Now you can skip the change by changing "peek" to "get" above, but -`pglogical.skip_changes_upto` does a faster skip that avoids decoding -and outputting all the data: - -```sql -SELECT pglogical.alter_subscription_skip_changes_upto('subscription_name', -'the_target_lsn'); -``` - -If necessary or desired, apply the same changes (or repaired versions of them) -manually to the subscriber, using the dumped transaction contents as a guide. - -Finally, re-enable the subscription: - -```sql -SELECT pglogical.alter_subscription_enable('the_subscription'); -``` - -### pglogical.alter_subscription_writer_options - -Change the writer options first addressed when `writer_name` and `writer_options` -are clarified with pglogical.create_subscription. - -#### Synopsis - -```sql - pglogical.alter_subscription_writer_options( - subscription_name name, - writer_name name, - writer_options text[] = '{}' - - ); -``` - -#### Example - -Find the subscription you want to alter and use that as the `subscription_name` and -possibly the `writer_name` if chosen (shown first). Then the DML with the `writer_options` -text array. - -```sql -SELECT pglogical.alter_subscription_writer_options(sub_name, sub_name, '{}') FROM pglogical.subscription; -``` - -Grant all writer options to `writer_name` super; array has to be an even number of elements. - -```sql -SELECT pglogical.alter_subscription_writer_options(sub_name, 'super', '{UPDATE,INSERT,DELETE,''}') FROM pglogical.subscription; -``` - -### pglogical.alter_subscription_set_conflict_resolver - -Change the conflict resolver of given conflict type for the given subscription. - -#### Synopsis - -```sql -pglogical.alter_subscription_set_conflict_resolver( - sub_name text, - conflict_type text, - conflict_resolver text - ) -``` - -#### Parameters - -- `sub_name` - name of subscription to change -- `conflict_type` - type of conflict to configure (see bellow) -- `conflict_resolver` - which resolver to use for the given conflict type (see bellow) - -Conflict type can be one of: - -- `insert_exists` - the row being inserted exists locally -- `update_missing` - the row being updated does not exist locally -- `delete_missing` - the row being deleted does not exist locally -- `update_origin_change` - the row being updated was updated on a different - origin -- `target_table_missing` - the table corresponding to the change does not - exist locally -- `target_column_missing` - the column being updated or inserted to does not - exist locally -- `source_column_missing` - a column that exists locally is not available in - the updated or inserted row - replicated -- `delete_recently_updated` - the row being deleted was updated locally - recently -- `update_pkey_exists` - the updated primary key exists locally -- `apply_error` - an error occured while applying the change locally -- `apply_error_trigger` - an error occured while firing a trigger locally - after applying the change -- `apply_error_ddl` - an error occured during applying a DDL that was - replicated -- `apply_error_dml` - an error occured while applying a DML that was - - Note that `apply_error`, `apply_error_trigger`, `apply_error_ddl` and - `apply_error_dml` are never raised right now. They may be used in future. - -Conflict resolver can be one of: - -- `error` - the replication will stop on error if conflict is detected; manual - action is then required for resolution. -- `skip` - keep the local version of the data and ignore the - conflicting change that is coming from the remote node. This is same as - `keep_local` which is now deprecated. -- `update` - always apply the upstream change that's conflicting with local data. - This is same as `apply_remote`, which is now deprecated. -- `update_if_newer` - the version of data with the newest commit timestamp - will be kept (this can be either the local or the remote version). This is same - as `last_update_wins` which is now deprecated. -- `update_if_older` - the version of the data with the oldest timestamp will - be kept (this can be either the local or the remote version). This is same - as `first_update_wins` which is now deprecated. -- `insert_or_skip` - if the row being updated is missing and the downstream - can verify that the updated row was none of the ones that exist the new row - will be inserted. Otherwise the change will be skipped. -- `insert_or_error` - if the row being updated is missing and the downstream - can verify that the updated row was none of the ones that exist the new row - will be inserted. Otherwise the replication will stop on error. -- `ignore` - if the updated or inserted column is missing, it will be ignored - while applying the upstream change -- `ignore_or_error` - if the updated or inserted column is missing, it will be ignored - if it the new value is NULL. Otherwise replication will stop on error -- `use_default_value` - if a column is present locally but is not available on - the source, a default value will be used for that column. - -The available settings and defaults depend on the version of PostgreSQL and -other settings. - -The `skip`, `update_if_newer` and `first_update_wins` settings require the -`track_commit_timestamp` PostgreSQL setting to be enabled. Those can not be -used with PostgreSQL 9.4 as `track_commit_timestamp` is not available in there. - -Some conflict resolvers can not be used with some conflict types e.g. resolver -`update_if_newer` can not be used with conflict type `target_table_missing`. -`error` is the only resolved available to handle conflict types `apply_error`, -`apply_error_trigger`, `apply_error_ddl`, or `apply_error_dml`. The function -throws an error when an incompatible resolver is used. - -#### Example - -Find the subscription you want to change the conflict resolver for and use that as the `sub_name`. - -```sql -SELECT pglogical.alter_subscription_set_conflict_resolver(`sub_name`, 'insert_exists', 'update_if_newer') -``` - -Changes the conflict resolver of conflict type `insert_exists` for subscription -`sub_name` to `update_if_newer`. If the row specified by INSERT change on -subscription `sub_name` already exists locally, out of the two rows, the one -with the newest commit will be kept. - -#### Listing Conflict Resolution Configurations - -The catalog `pglogical.sub_cfl_res` show non-default conflict resolution -configuration settings for each subscription. - -### pglogical.alter_subscription_add_log - -Add conflict logging configuration for a subscription. - -This can primarily be used to log conflicts into the `pglogical.apply_log` -table. - -#### Synopsis - -```postgresql -pglogical.alter_subscription_add_log( - sub_name text, - log_name text, - log_to_file bool DEFAULT true, - log_to_table regclass DEFAULT NULL, - conflict_type text[] DEFAULT NULL, - conflict_resolution text[] DEFAULT NULL -) -``` - -#### Listing Conflict Logging Configurations - -The catalog `pglogical.sub_log` shows all the logging configurations. -It lists the name of the logging configuration, where it logs and which -conflicts type and resolution it logs. - -#### Parameters - -- `sub_name` - name of the subscription that is being changed -- `log_name` - name of the logging configuration -- `log_to_file` - whether to log to the server log file -- `log_to_table` - whether to log to a table, and which table should be the - target; NULL (the default) means do not log to a table -- `conflict_type` - which conflict types to log; NULL (the default) means all -- `conflict_resolution` - which conflict resolutions to log; NULL - (the default) means all - -### pglogical.alter_subscription_remove_log - -Remove existing conflict logging configuration for a subscription. - -#### Synopsis - -```postgresql -pglogical.alter_subscription_remove_log( - sub_name text, - log_name text -) -``` - -#### Parameters - -- `node_name` - name of the subscription that is being changed -- `log_name` - name of the logging configuration to be removed diff --git a/product_docs/docs/pgd/3.6/pglogical/subscriptions/pglogical-writer.mdx b/product_docs/docs/pgd/3.6/pglogical/subscriptions/pglogical-writer.mdx deleted file mode 100644 index 47db829ef82..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/subscriptions/pglogical-writer.mdx +++ /dev/null @@ -1,186 +0,0 @@ ---- -redirects: - - ../../pglogical-writer -navTitle: pglogical Writer -title: pglogical writer -originalFilePath: pglogical-writer.md - ---- - -The pglogical writer (or HeapWriter) is the standard way of writing into a local -PostgreSQL instance when using pglogical subscription. This is the default -writer used when no writer is specified in `pglogical.create_subscription()`. - -The pglogical writer is using low-level APIs to write the data into local -tables and sequences. It supports conflict detection and resolution, -has full support for `REPLICA IDENTITY`, invokes constraints with the exception -of foreign keys (see [Foreign Keys](#foreign-keys) for details) and row triggers -marked as `REPLICA` (see [Triggers](#triggers)). - -Changes are applied as the table owning-user, thus security concerns are similar -to the use of triggers by table owners. - -## Conflict handling - -In case the node is subscribed to multiple providers, or when local writes -happen on a subscriber, conflicts can arise for the incoming changes. These -are automatically detected and can be acted on depending on the configuration. - -The configuration of the conflicts resolver is done using -pglogical.alter_subscription_set_conflict_resolver(). - -### Row versioning - -To ease reasoning about different versions of a row, it can be helpful for it -to carry a row version. PGLogical provides the helper trigger -`pglogical.inc_row_version` to simplify this task. It requires a user -provided integer column of any bitwidth (usually, `SMALLINT` is enough) and -needs to be added to a table as follows (assuming a table `my_table` with -an integer column `row_version`): - -```sql -CREATE TRIGGER my_row_version_trigger -BEFORE UPDATE ON my_table -FOR EACH ROW -EXECUTE PROCEDURE pglogical.inc_row_version('row_version'); -``` - -This approach resembles Lamport timestamps and - in combination with -`REPLICA IDENTITY FULL` and `check_full_tuple` (see below) - fully prevents -the ABA problem for conflict detection. - -## Configuration options - -Some aspects of pglogical can be configured using configuration options that -can be either set in `postgresql.conf` or via `ALTER SYSTEM SET`. - -### pglogical.conflict_log_level - -Sets the log level for reporting detected conflicts. - -Main use for this setting is to suppress logging of conflicts. - -Possible values are the same as for PostgreSQL `log_min_messages` parameter. - -The default is `LOG`. - -### pglogical.conflict_ignore_redundant_updates - -In case the subscriber retrieves an INSERT or UPDATE to a locally -pre-existing and equivalent tuple, it is simply ignored without invoking any -conflict handler or logging on the subscriber side, if this option is turned -on. - -To be used in combination with `REPLICA IDENTITY FULL`. - -The default is `false`. - -### pglogical.conflict_check_full_tuple - -This option controls the detection of UPDATE-UPDATE conflicts. By default, -the origin of the existing tuple is compared to the expected origin - -every mismatch is considered a conflict and initiates conflict handling. -This is a low-overhead conflict detection mechanism and is therefore the -default. However, it can lead to false positives and invoke conflict -handlers inadvertently. - -With this option turned on, the expected tuple, as it was before the update on -the provider, is compared to the existing tuple on the subscriber. This -allows for a better conflict detection mechanism and (in combination with -a row version column) can mitigate all false positives. - -Due to the requirement to know the full old tuple, this option only ever -affects relations that are set to `REPLICA IDENTITY FULL`. - -The default is `false`. - -### pglogical.batch_inserts - -This tells pglogical writer to use the batch insert mechanism if possible. The -Batch mechanism uses PostgreSQL internal batch insert mode which is also used -by `COPY` command. - -The batch inserts will improve replication performance of transactions that -perform many inserts into one table. pglogical will switch to batch mode when -the transaction performed than 5 INSERTs, or 5 rows within a COPY. - -It's only possible to switch to batch mode when there are no -`INSTEAD OF INSERT` and `BEFORE INSERT` triggers on the table and when -there are no defaults with volatile expressions for columns of the table. - -The default is `true`. - -### config.session_replication_role - -This tells pglogical writer what `session_replication_role` to use. This can be -useful mainly in case when it's desirable to enforce `FOREIGN KEY` constraints. - -The default is `replica` which ignores foreign keys when writing changes -to the database. - -**WARNING: Use with caution.** -This option changes trigger execution behavior as documented in -[PostgreSQL documentation](https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-SESSION-REPLICATION-ROLE). -If set to `origin` or `local` this will fire **normal** triggers in the -database which can leadi to the trigger being executed both on the upstream and on -the downstream! - -## Restrictions - -There are some additional restrictions imposed by pglogical writer over the -standard set of [restrictions](restrictions). - -### Only one unique index/constraint/PK - -If more than one upstream is configured, or the downstream accepts local writes, -then only one `UNIQUE` index should be present on downstream replicated tables. -Conflict resolution can only use one index at a time, so conflicting rows may -`ERROR` if a row satisfies the `PRIMARY KEY` but violates a `UNIQUE` constraint -on the downstream side. This will stop replication until the downstream table -is modified to remove the violation. - -It's fine to have extra unique constraints on an upstream if the downstream only -gets writes from that upstream and nowhere else. The rule is that the downstream -constraints must *not be more restrictive* than those on the upstream(s). - -### Deferrable unique indexes - -Deferrable unique indexes are supported; however initially deferred unique -indexes might result in apply retries, as the conflicts might not be detected -on first try due to the deferred uniqueness check. - -Note that deferred `PRIMARY KEY` cannot be used as `REPLICA IDENTITY` - PostgreSQL -will throw an error if this is attempted. As a result a table withi a deferred -`PRIMARY KEY` does not have `REPLICA IDENTITY` unless another `REPLICA IDENTITY` -is explicitly set. Replicated tables without `REPLICA IDENTITY` cannot receive -`UPDATEs` or `DELETEs`. - -### Foreign Keys - -By default foreign key constraints are not enforced for the replication -process - what succeeds on the provider side gets applied to the subscriber -even if the `FOREIGN KEY` would be violated. - -This behavior can be changed using `config.session_replication_role` writer -option. - -### TRUNCATE - -Using `TRUNCATE ... CASCADE` will only apply the `CASCADE` option on the -provider side. - -(Properly handling this would probably require the addition of `ON TRUNCATE CASCADE` -support for foreign keys in PostgreSQL). - -`TRUNCATE ... RESTART IDENTITY` is not supported. The identity restart step is -not replicated to the replica. - -### Triggers - -Trigger behavior depends on the `config.session_replication_role` setting of -the writer. By default it's set to `replica`, which means that `ENABLE REPLICA` -and `ENABLE ALWAYS` triggers will be fired. When it's set to `origin` or -`local`, it will trigger normal triggers. - -Only row triggers are fired. Statement triggers are ignored as there are no -statements executed by the writer. Per-column UPDATE triggers are ignored. diff --git a/product_docs/docs/pgd/3.6/pglogical/troubleshooting.mdx b/product_docs/docs/pgd/3.6/pglogical/troubleshooting.mdx deleted file mode 100644 index 52a16fc291f..00000000000 --- a/product_docs/docs/pgd/3.6/pglogical/troubleshooting.mdx +++ /dev/null @@ -1,216 +0,0 @@ ---- -navTitle: Troubleshooting -title: Error handling in pglogical -originalFilePath: troubleshooting.md - ---- - -The main tool for troubleshooting is the PostgreSQL log file. - -On the upstream side, monitoring uses the views: - -```sql -pg_catalog.pg_replication_slots -pg_catalog.pg_stat_replication -``` - -On the subscriber side there are numerous helper functions and views that may -be consulted to gain insight into pglogical's configuration and behaviour. - -Start with the configuration and status summary views: - -Configuration can be fetched from: - -```sql -SELECT * FROM pglogical.subscriptions; -SELECT * FROM pglogical.TABLES; -SELECT * FROM pglogical.SEQUENCES; -SELECT * FROM pglogical.DDL_REPLICATION; -``` - -Observe worker activity with: - -```sql -SELECT * FROM pglogical.workers; -SELECT * FROM pglogical.worker_error_summary; -SELECT * FROM pglogical.apply_log; -SELECT * FROM pglogical.apply_log_summary; -SELECT * FROM pglogical.worker_locks; -``` - -Statistics are reported by: - -```sql -SELECT * FROM pglogical.stat_relation; -SELECT * FROM pglogical.stat_subscription; -``` - -Other views provide logs and details: - -```sql -SELECT * FROM pglogical.local_sync_status; -SELECT * FROM pglogical.show_subscription_status(); -SELECT * FROM pglogical.sub_history; -SELECT * FROM pglogical.worker_error; -SELECT * FROM pglogical.show_workers(); -SELECT * FROM pglogical.worker_tasks; - -SELECT * FROM pg_catalog.pg_stat_activity; -SELECT * FROM pg_catalog.pg_locks; -SELECT * FROM pg_catalog.pg_replication_origin_status; -``` - -The relation `pglogical.worker_error_summary` is particularly important for -getting a quick overview of recent problems, though the logs should generally -be your main reference. - -## `pglogical.worker_error` and `pglogical.worker_error_summary` - -These relations show the last error reported by each kind of pglogical worker. -Only the most recent error is retained for each distinct worker task. Receiver -workers are tracked separately to their writer(s), as are any writer(s) used -for table (re)sync purposes. - -walsender workers cannot record errors in `pglogical.worker_error`. Their -errors are only available in the log files. - -`pglogical.worker_error_summary` is a convenience view over -`pglogical.worker_error` available in 3.7 and above. - -## `pglogical.worker_tasks` - -The `pglogical.worker_tasks` view shows pglogical's current worker launch rate -limiting state as well as some basic statistics on background worker launch -and registration activity. - -Unlike the other views listed here, it is not specific to the current database -and pglogical node; state for all pglogical nodes on the current PostgreSQL -instance is shown. Join on the current database to filter it. - -`pglogical.worker_tasks` does not track walsenders and output plugins. - -See the configuration option -[`pglogical.min_worker_backoff_delay`](configuration#pglogical.min_worker_backoff_delay) for -rate limit settings and overrides. - -## `pglogical.apply_log` and `pglogical.apply_log_summary` - -The `pglogical.apply_log_summary` view summarizes the record of apply worker -events kept in `pglogical.apply_log`. This records human-readable information -about conflicts and errors that arose during apply. - -## `pglogical.sub_log` - -The `pglogical.sub_log` table contains *conflict log filter definitions* that -are applied when recording entries in `pglogical.apply_log`, controlling -whether conflicts are recorded to a log table and/or postgres log, or silently -dropped. It's managed by `pglogical.alter_subscription_add_log(...)` and -`pglogical.alter_subscription_remove_log()`. - -If you aren't seeing expected conflict information when debugging an issue, check -to make sure you have not filtered it out. - -When pglogical workers encounter an error condition during operation they -report the error to the PostgreSQL log file, record the error to the -`pglogical.worker_error` table if possible, and exit. - -Unlike normal PostgreSQL user backends they do not attempt to recover from most -errors and resume normal operation. Instead the worker in question will be -relaunched soon and will resume operations at the last recoverable point. -In the case of apply workers and walsenders that generally means restarting the -last uncommitted transaction from the beginning. - -This is an intentional design choice to make error handling and recovery -simpler and more robust. - -For example, if an apply worker tries to apply an `UPDATE` and the new row -violates a secondary unique constraint on the target table, the apply worker -will report the unique violation error and exit. The error information will be -visible in `pglogical.worker_error_summary` (3.7+, `pglogical.worker_error` on 3.6). -The walsender worker on the peer end will exit automatically as well. The apply -worker will be relaunched by the manager worker for the database in a few -seconds and will retry the failed transaction from the beginning. If the -conflicting row has since been removed the transaction will apply normally and -replication will resume. If not, the worker will error again and the cycle will -repeat until the cause of the error is fixed. In this case the fix would -typically be for another subscription or a local application write to replicate -a change that clears the unhandled conflict condition or for the administrator -to intervene to change the conflicting row. - -## Diagnosing and fixing errors - -It's important to first check that your schema and deployment don't violate any -of the [restrictions](restrictions) imposed by pglogical. Also check the -additional writer-specific restrictions from the pglogical writer you are using, -most likely the [HeapWriter](pglogical-writer#Restrictions). - -### Common problems - -Some issues that arise when operating pglogical include: - -- Incorrect or changed provider address or hostname. Update the interface definition - for the subscription. - - Use `pglogical.alter_node_add_interface(...)` and - `pglogical.alter_subscription_interface(...)` to change the subscriber's - recorded address for the provider. - -- Incorrect `pg_hba.conf` on provider disallowing subscriber from connecting. - The subscriber must be able to connect in both replication and ordinary - non-replication mode. - - Correct the `pg_hba.conf` on the provider and `SELECT pg_reload_conf();` on - the provider. - -- Incompatible schema definitions on provider and subscriber caused by schema changes - being made without [DDL replication](ddl) enabled and without use of - `pglogical.replicate_ddl_command`. For example, missing columns on subscriber - that haven't been excluded by a column filter, differing data types for columns - between provider and subscriber, etc. - - (Some data type differences are actually permitted, but care must be taken - that the text representations are compatible. Do not use differing data types - for PostgreSQL built-in data types. See [restrictions](restrictions).) - -- Incorrectly defined `ENABLE REPLICA` or `ENABLE ALWAYS` triggers firing on - apply on the subscriber and causing errors. - -- Heap writers configured to fire normal triggers and foreign key validation - triggers (using writer option `config.session_replication_role`). Problems - arise when not all triggers have been checked to ensure they'll work - correctly with row-replication and without statement triggers being fired as - well. Or when FK violations or check constraint violations are created by - replication set configuration such as row and column filters or by referenced - tables not being replicated along with the referencing tables. - -- Inconsistent versions of PostgreSQL or extensions between provider and subscriber - where the version difference affects the behaviour or limits of a data type being - replicated. - - pglogical explicitly supports replicating between different versions of - PostgreSQL, so a version difference alone is not a problem. But the data - being replicated must be valid on the subscriber's PostgreSQL version. - - For example, apply errors may occur when replicating data from PostGIS 3.0 to - PostGIS 2.5 where not all the 3.0 data is understood by 2.5. Similarly, - replicating from a PostgreSQL configured without integer datetimes to one - with integer datetimes may result in errors if there are non-integer - datetimes with values outside the somewhat narrower range permitted by - integer datetimes support. - -### Multiple data source issues - -Additional classes of error tend to arise with any sort of multiple-data-source -configuration, i.e. multiple subscriptions to different providers for the same -tables and/or local writes to tables that are also part of a subscription. Some of -these affect BDR3 as well. - -These include: - -- Tables with multiple unique constraints may cause unique violation errors - during apply if the table receives writes from multiple sources. - -- Updating the PRIMARY KEY value for rows, or deleting a key then inserting the same - key again soon afterwards. This may cause unique violation errors during apply - if the table receives writes from more than one source, i.e. multiple providers - and/or local writes. diff --git a/product_docs/docs/pgd/3.7/bdr/index.mdx b/product_docs/docs/pgd/3.7/bdr/index.mdx index d4539a607d7..efbae52874d 100644 --- a/product_docs/docs/pgd/3.7/bdr/index.mdx +++ b/product_docs/docs/pgd/3.7/bdr/index.mdx @@ -44,10 +44,10 @@ provides a solution for building multi-master clusters with mesh topology. This means that you can write to any server and the changes will be sent row-by-row to all the other servers that are part of the same BDR group. -BDR version 3 ("BDR3") is built on the [pglogical3](https://www.enterprisedb.com/docs/pglogical/latest/) +BDR 3 ("BDR3") is built on the [pglogical 3.7](https://www.enterprisedb.com/docs/pglogical/latest/) extension. However, everything you need to know about BDR3 is included here and it is unnecessary, as well as potentially -confusing, to refer to pglogical docs. +confusing, to refer to pglogical 3.7 docs. This documentation refers only to BDR3, not to earlier architectures, referred to as BDR1 and BDR2. There are significant and important differences in BDR3 diff --git a/product_docs/docs/pgd/3.7/index.mdx b/product_docs/docs/pgd/3.7/index.mdx index 908223e6a7a..6be6dee0c10 100644 --- a/product_docs/docs/pgd/3.7/index.mdx +++ b/product_docs/docs/pgd/3.7/index.mdx @@ -22,7 +22,7 @@ What Postgres distribution and version is right for you depends on the features See the feature matrix in [Choosing a Postgres distribution](/pgd/latest/choosing_server) for detailed comparison. -## [BDR](bdr) +## BDR A Postgres server with the [BDR](bdr) extension installed is referred to as a BDR node. BDR nodes can be either data nodes or witness nodes. @@ -31,7 +31,7 @@ Witness nodes don't participate in data replication and are only used as a tie-breaker for consensus. -## [HARP](harp) +## HARP [HARP](harp) is connection management tool for a EDB Postgres Distributed cluster. @@ -39,7 +39,7 @@ It leverages consensus-driven quorum to determine the correct connection end-poi in a semi-exclusive manner to prevent unintended multi-node writes from an application. This reduces the potential for data conflicts. -## [pglogical 3](pglogical) +## pglogical 3.7 -BDR depends on [pglogical 3](pglogical) to provide the replication +BDR depends on [pglogical 3.7](pglogical) to provide the replication channel upon which BDR builds. diff --git a/product_docs/docs/pgd/3.7/pglogical/index.mdx b/product_docs/docs/pgd/3.7/pglogical/index.mdx index f812eeb3e08..0ca5cfbdfb5 100644 --- a/product_docs/docs/pgd/3.7/pglogical/index.mdx +++ b/product_docs/docs/pgd/3.7/pglogical/index.mdx @@ -10,13 +10,13 @@ navigation: - failover - restrictions - troubleshooting -navTitle: pglogical 3 -title: pglogical 3 +navTitle: pglogical 3.7 +title: pglogical 3.7 originalFilePath: index.md --- -The pglogical 3 extension provides logical streaming replication for PostgreSQL, +The pglogical 3.7 extension provides logical streaming replication for PostgreSQL, using a publish/subscribe model. It is based on technology developed as part of the BDR3 project. diff --git a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx index 89aecc9d57b..0ee0bcad2e4 100644 --- a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx +++ b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx @@ -1,6 +1,6 @@ --- navTitle: Release Notes -title: Release Notes for pglogical3 +title: Release Notes for pglogical 3.7 originalFilePath: release-notes.md --- @@ -316,7 +316,7 @@ improvements as well as fixes for issues identified previously. in `pg_replication_origin` system catalog if it had connection problems to upstream. -## Resolved Issues +### Resolved Issues - Fix flush queue truncation (BDR-890) During queue compaction flush to correct LSN instead of always truncating @@ -678,582 +678,3 @@ existing applications. Set idle_in_transaction_session_timeout to 0 so we avoid any user setting that could close the connection and invalidate the snapshot. -## pglogical 3.6.19 - -This is a security and maintenance release for pglogical 3.6 which includes -minor features as well as fixes for issues identified previously. - -### Resolved Issues - -- SECURITY: Set search_path to empty for internal PGLogical SQL statements (RM15373) - Also, fully qualify all operators used internally. PGLogical is now - protected from attack risks identified in CVE-2018-1058, when the - user application avoids the insecure coding practices identified there. - -- Correct parsing of direct WAL messages (RT67762) - Custom WAL messages emitted by PGLogical (or plugins building on top - of it) can be broadcast or direct types. Decoding of the latter was - incorrect and could in rare cases (depending on the node name) lead - to "insufficient data left in message" or memory allocation errors. - Decoding of such direct WAL messages has been corrected. - -- Add pglogical.sync_failover_slots() function (RM14318) - Signal the supervisor process to restart the mechanism to synchronize the - failover slots specifyed in the "pglogical.synchronize_failover_slot_name". - -- Fix the `--extra-basebackup-args` argument passed to pg_basebackup (RM14808) - Corrects how the `pglogical_create_subscriber` tool passes on such - extra arguments to pg_backbackup. - -### Improvements - -- Add more diagnostic information to pglogical.queue message (RM15292) - A new key `info` has been added to `pglogical.queue` providing - additional information about a queued DDL operation. - -## pglogical 3.6.18 - -This is a maintenance release for pglogical 3.6 which includes minor features -as well as fixes for issues identified previously. - -### Improvements - -- Warn about failover issues if standby_slot_names is not set (RT66767, RM12973) - If pglogical.standby_slot_names is not set and a physical standby is - configured; failover to this standby will have data consistency issues as - per our documentation. However, the replica could just be a simple read - replica. In any case, we now warn on the replica about the potential data - corruption/divergence that could result if failover is desired to such a - standby. - -- Check repsets in create_subscription for pgl2 upstreams also. - -- Various improvements to systemtap integration. - -### Resolved Issues - -- Prevent a hang in case of an early error in the PGL writer (RT67433, RM14678) - -- Allow postgres to start with pglogical library loaded but activity suspended - Add start_workers commandline-only GUC to facilitate this. - -## pglogical 3.6.17 - -This is a maintenance release for pglogical 3.6 which includes minor features -as well as fixes for issues identified previously. - -### Improvements - -- Make the slot synchronization to standby more configurable (RM13111) - Added several new configuration parameters which tune the behavior of the - synchronization of logical replication slots from a primary to a standby - PostgreSQL servers. This allows for better filtering, inclusion of - non-pglogical replication sets and also using different connection string - than physical replication uses (useful when different user or database - should be used to collect information about slots). - -### Resolved Issues - -- Fix issue with UPDATEs on partitions with different physical row - representation than partition root (RM13539, RT67045) - The partitions must have same logical row as partition root they can have - different physical representation (primarily due to dropped columns). UPDATEs - on such partitions need to do special handling to remap everything correctly - otherwise constraints and not-updated TOAST columns will refer to wrong - incoming data. - -- Fix truncation of `\_tmp` slot names in sync slots - Long slot names could previously cause the temporary slot to be suffixed - by `\_tm` rather than the expected `\_tmp` suffix. - -### Support, Diagnostic and Logging Changes - -These changes don't directly change existing behaviour or add new user-facing -features. They are primarily of interest to technical support operations and -for advanced diagnostic analysis. - -- Expand non-invasive tracing (SystemTap, linux-perf, DTrace, etc) - support to cover inspection of the pglogical receiver's input protocol - stream, walsender output plugin protocol stream, and other useful events. - (RM13517) - -- Add a test and debug utility that decodes captured pglogical protocol streams - into human-readable form (RM13538) - -- Improve error context logging in the pglogical writer to show more - information about the transaction being applied and its origin. - -- Fix incorrectly reported commit lsn in errcontext messages from the pglogical - heap writer (RM13796). This fix only affects logging output. The writer would - report the lsn of the original forwarded transaction not the lsn of the - immediate source transaction. - -- Add subscription, local node and peer node names to heap writer errcontext - log output. - -## pglogical 3.6.16 - -This is the sixteenth minor release of the Pglogical 3.6 series. This release -includes mostly just enables BDR 3.6.16 without any significant changes to -pglogical. - -## pglogical 3.6.15 - -This is the fifteenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Fix backwards-compatibility to PGLogical 2 (RM13333, RT66919) - Recent releases performed additional checks during - `create_subscription`, which are fine against other PGLogical 3 - installations, but not backwards-compatible. This release corrects - the check to account for backwards-compatibility. - -- Correct a warning about GUC nest level not being reset (EE) (RM13375) - The addition of the `lock_timeout` in 3.6.14 led to a warning being - issued for CAMO and Eager All Node transaction ("GUC nest level = 1 - at transaction start"). With this release, GUC nest levels are - properly managed and the warning no longer occurs. - -### Improvements - -- Add a new `pglogical.worker_tasks` view that tracks and records pglogical's - background worker use. The view exposes information about the number of times - a given type of worker has been restarted, how long it has been running, - whether it accomplished any useful work, and more. This offers administrators - more insight into pglogical's internal activity when diagnosing problems, - especially when joined against the `pglogical.worker_error` table. - -- Add support for rate-limiting pglogical background worker (re)launches. The - new `pglogical.min_worker_backoff_delay` configuration option sets a minimum - delay between launches of all types of pglogical background workers so that - rapid respawning of workers cannot fill the log files and or excessive load - on the system that affects other operations. - - For example, if configured with `pglogical.min_worker_backoff_delay = - '500ms'`, pglogical will not retry any given background worker startup more - often than twice per second (`1000/500 = 2`). - - A simple fixed-rate factor was deemed to be the most predictable and - production-safe initial approach. Future enhancements may add a heuristic - delay factor based on worker type, time from start to exit, number of recent - launches, etc. - - The launch backoff delay defaults to 0 (off) to prevent surprises for - upgrading users. - - A setting of `pglogical.min_worker_backoff_delay = '5s'` or similar is a - reasonable starting point, and may become the default in a future release. - -### Upgrades - -The PostgreSQL Global Development Group has phased out support for -PostgreSQL 9.4 on all Debian based distributions. Following that, -this release covers only PostgreSQL 9.5 and newer. We advise to -upgrade to a newer version. - -For RedHat based distributions, this release is still available for -PostgreSQL 9.4. - -## pglogical 3.6.14 - -This is the fourteenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Resolve deadlocked CAMO or Eager transactions (RM12903, RM12910) - Add a `lock_timeout` as well as an abort feedback to the origin node - to resolve distributed deadlocking due to conflicting primary key - updates. This also prevents frequent restarts and retries of the - PGL writer process for Eager All Node and sync CAMO transactions. - -## pglogical 3.6.12 - -This is the twelveth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Add infrastructure for `check_full_row` in DELETE operations used by - BDR 3.6.12 (RT66493) - -- Validate requested replication sets at subscribe time (RM12020, RT66310) - `pglogical.create_subscription()` now checks that all requested replication - sets actually exist on the provider node before returning. If any are - missing it will raise an ERROR like: - `ERROR: replication set(s) "nonexistent_repset" requested by subscription are missing on provider` - with a DETAIL message listing the full sets requested, etc. - On prior releases subscriptions with missing repsets would fail after - `pglogical.create_subscription(...)` returned, during initial sync. The - failure would only be visible in the logs where it is much less obvious to - the user. Or if schema sync was not enable they could appear to succeed but - not populate the initial table contents. - - -### Resolved Issues - -- Fix a potential deadlock at CAMO partner startup. (RM12187) - After a restart, the CAMO partner resends all confirmations for - recent CAMO protected transactions. In case these fill the internal - queue between the receiver and writer processes, a deadlock was - possible. This release ensures the receiver consumes pending - feedback messages allowing the writer to make progress. - -## pglogical 3.6.11 - -This is the eleventh minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Implement remote_commit_flush for CAMO. (RM11564) - Additional level of robustness for CAMO, only replying when xact - is known committed and flushed on partner node. - -- Make receiver-writer shared queues of configurable size. (RM11779) - Two new GUCs are introduced: - pglogical.writer_input_queue_size (default 1MB) - pglogical.writer_output_queue_size (default 1MB) - -- Add a warning when user tries to set update_origin_change to skip - -- Add callback to request replay progress update. (RM6747) - -### Resolved Issues - -- Send TimeZone GUC when replicating DDL (RT66019) - To ensure that timezone dependent expressions in DDL get evaluated to - same value on all nodes. - -- Only use isvalid indexes when searching for conflicts (RT66036) - Indexes currently being created or failed index creations - will be ignored, to prevent concurrency issues with change apply - and `CREATE INDEX CONCURRENTLY`. - -- Fix crash when replication invalidations arrive outside a transaction (RM11159) - -- Make the receiver apply the queue before shutting down (RM11778) - Upon smart shutdown, the PGL writer no longer terminates - immediately, requiring queued transactions to be resent, but applies - already received transactions prior to shutting down. - -## pglogical 3.6.10 - -This is the tenth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Improvements - -- Add support for a CAMO remote_write mode (RM6749) - -### Resolved Issues - -- COMMIT after initial sync of a table. This avoids treating the first - catchup xact as if it was part of the initial COPY, which could lead to - strange errors or false conflicts. (RM11284). - -- Remove the 4 billion row limit during the initial subscription - synchronization (RT66050). - -- Cleanup table replication cache when replication set configuration changes. - Previously we could use stale cache on multiple calls for table replication - info on same connection if user changed the configuration in meantime. - This could result in initial sync missing replicated table if the - configuration was changed while the subscription was being created. - -- Remember repsets when caching table replication info. - If the client calls the table replication info with different parameters, - we need to remember them otherwise we might return cached value for wrong - replication sets. - This could result in initial sync copying data from table which were - not supposed to be replicated. - -## pglogical 3.6.9 - -This is the ninth minor release of the Pglogical 3.6 series. This release -includes minor improvements. - -### Improvements - -- Add support for local, remote_apply and remote_write. (RM11069, RT65801) - We now accept the use of all the values that PostgreSQL accepts when configuring - the "pglogical.synchronous_commit". - -- Immediately forward all messages from the PGL receiver back to origin (BDR CAMO) - Confirmations for CAMO protected transactions flow - from the PGL writer applying the transaction back to origin node via - the PGL receiver. This process used to consume only one - confirmation message per iteration. It now consumes all pending - confirmations from the PGL writer and immediately sends them back to - the origin. It also decreases latency for BDR CAMO transactions in case - confirmations queue up. - -## pglogical 3.6.8 - -This is the eigth minor release of the Pglogical 3.6 series. This release -includes fixes for issues identified previously. - -### Resolved Issues - -- Use RelationGetIndexAttrBitmap to get pkey columns. (RT65676, RT65797) - No need to try to fetch pkey columns from index itself, we have - relcache interface that does exactly what we need and does so - in more performant way. - -## pglogical 3.6.7.1 - -This is a hot-fix release on top of 3.6.7. - -### Resolved Issues - -- Fix a protocol violation after removal of an origin. (RT65671, RM10605) - Removal of a replication subscription may lead to a walsender trying - to forward data for unknown origins. Prevent emission of an invalid - message in that case. - -## pglogical 3.6.7 - -pglogical 3.6.7 is the seventh minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified earlier. - -### Improvements - -- Replicate TRUNCATE on a partition if only parent table is published in - replication set (RT65335) - Previously, we'd skip such TRUNCATE unless the partition was also published. -- Generate `target_table_missing` for TRUNCATE which is executed against - non-existing table (RT10291) - Allows for user-configured decision if it should be a replication-stopping - issue or not. -- Improve performance of repeated UPDATEs and DELETEs executed on origin node - by caching the replication configuration of tables in a user session. -- Reduce CPU usage of receiver worker when writer queue is full (RM10370). - -### Resolved Issues - -- Fix partition replication set membership detection for multi-level - partitioned tables - Replicate changes correctly for multi-level partitioned tables, where only - the intermediate partition is part of replication set (not root or leaf - partitions). -- Support replication `TRUNCATE CASCADE` on tables referenced by - `FOREIGN KEY` (RT65518) - Previously this would throw error on the subscriber. This will only work if - all tables on subscriber which have `FOREIGN KEY` on the table being - `TRUNCATEd` are replicated tables. Also it's only supported on - PostgreSQL 11 and higher. -- Flush writer between data copy and constraint restore - Otherwise there could in some rare cases still be unapplied changes when - creating constraints during initial synchronization of a subscription, - potentially causing deadlocks. -- Fix potential writer queue corruption on very wide (1000+ columns) tables - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -## pglogical 3.6.6 - -pglogical 3.6.6 is the sixth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified earlier. - -### Improvements - -- New conflict type `update_pkey_exists` (RM9976) - Allows resolving conflicts when a `PRIMARY KEY` was updated to one which - already exists on the node which is applying the change. - -- Add `pglogical.apply_log_summary` (RM6596) - View over `pglogical.apply_log` which shows the human-readable conflict - type and resolver string instead of internal id. - -- Improve logging during both the initial data synchronization of a - subscription and the individual table resynchronization. - -### Resolved Issues - -- Make sure writer flushes changes after initial data copy (RT65185) - Otherwise depending on timing and I/O load the subscription might not - update positioning info and get data both via initial copy and replication - stream catchup that follows. - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -## pglogical 3.6.5 - -pglogical 3.6.5 is the fifth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.4. - -### Improvements - -- Improve tuple lock waits during apply for deletes (RM9569) - This should improve performance of replication of deletes and updates in - contentious situation. - -### Resolved Issues - -- Use consistent table list in initial data copy (RM9651/RT64809) - To prevent issues during initial data copy and concurrent table drop. -- Cleanup worker_dsm_handle on worker detach (internal) - Otherwise we could leave dangling DSM segment handle for a worker after a - crash, which could confuse plugins using this API. -- Fix handling of empty eager transactions (RM9550) - In case no relevant change remains to be applied on a replica node, - the prepare of such an empty transaction now works just fine. -- Fix the replication sets output in `pglogical.pglogical_node_info()` - Previously it could be garbled. -- Reduce log level for messages when resolving - ERRCODE_T_R_SERIALIZATION_FAILUREs (RM9439) - -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 2.2.0 -- 2.2.1 -- 2.2.2 -- 3.2.0 and higher - -Note that upgrades from 2.2.x are only supported on systems with -`pglogical.conflict_resolution` set to `last_update_wins`. - -## pglogical 3.6.4 - -pglogical 3.6.4 is the fourth minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.3. - -### New Features - -- Apply statistics tracking (RM9063) - We now track statistics about replication and resource use for individual - subscriptions and relations and make them available in - `pglogical.stat_subscription` and `pglogical.stat_relation` views. - The tracking can be configured via `pglogical.stat_track_subscription` and - `pglogical.stat_track_relation` configuration parameters. -- The `replicate_inserts` option now affects initial COPY - We now do initial copy of data only if the table replicates inserts. - -### Resolved Issues - -- Fix initial data copy of multi-level partitioned tables (RT64809) - The initial data copy used to support only single level partitioning, - multiple levels of partitioning are now supported. -- Don't try to copy initial data twice for partitions in some situations (RT64809) - The initial data copy used to try to copy data from all tables that are in - replication sets without proper regard to partitioning. This could result in - partition data to be copied twice if both root partition and individual - partitions were published via replication set. This is now solved, we only - do the initial copy on the root partition if it's published. -- Fix handling of indexes when replicating INSERT to a partition (RT64809) - Close the indexes correctly in all situations. -- Improve partitioning test coverage (RM9311) - In light of the partitioning related issues, increase the amount of - automated testing done against partitioned tables. -- Fix a leak in usage of the relation cache (RT64935) -- Fix a potential queue deadlock between writer and receiver (RT64935, RT64714) - -## pglogical 3.6.3 - -pglogical 3.6.3 is the third minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.2. - -### New Features - -- Support `DoNotReplicateId` special origin - This allows correct handling of "do not replicate" origin which allows skipping replication of some changes. Primarily needed internally for other features. -- Persist the last_xact_replay_timestamp (RT63881) - So that it's visible even if the subscription connection is down. -- Rework documentation build procedure for better consistency between HTML and PDF documentation - This mainly changes the way docs are structured into chapters so that there is single source of chapter list and ordering for both PDF and HTML docs. - -### Resolved Issues - -- Invalidate local cache when adding new invalidation - Fixes visibility of changes in the catalog cache view of the transaction which did those changes. Not triggered yet by any code but will be in the future releases. -- Open indexes after partition routing - Otherwise we might be opening indexes of the root table rather than the partition, causing issues with handling conflicts for `INSERT` operation replication. - -## pglogical 3.6.2 - -pglogical 3.6.2 is the second minor release of the pglogical 3.6 series. This release includes minor new features as well as fixes for issues identified in 3.6.1. - -### New Features - -- Support DEFERRED UNIQUE indexes - They used to work only in limited cases before this release. -- Support covering UNIQUE indexes (RT64650) - The use of covering UNIQUE indexes could result in ambiguous error messages in some cases before. -- Add `--log-file` option to `pglogical_create_subscriber` (RT64129) - So that log can be saved somewhere other than the current working directory - -### Resolved Issues - -- Fix error message when the database name in the connection string in `pglogical_create_subscriber` is missing (RT64129) - The previous message was ambiguous. -- Raise error when unknown parameter was specified for `pglogical_create_subscriber` (RT64129) - Otherwise mistakes in command line arguments could be silently ignored. -- Solve timing issue with workers exiting while another one tries to start using same worker slot - Before, we could corrupt the worker information causing the newly starting worker to crash (and having to start again later), this will no longer happen. -- Set statement time on start of every transaction in pglogical workers (RT64572) - Fixes reporting of `xact_start` in `pg_stat_activity` - -## pglogical 3.6.1 - -pglogical 3.6.1 is the first minor release of the pglogical 3.6 series. This release includes minor new features and fixes including all the fixes from 3.6.0.1. - -### New Features - -- Add slot failover documentation -- Add `pglogical.get_sub_progress_timestamp` for retrieving origin timestamp of the last committed change by the subscription - -### Resolved Issues - -- Stop retrying subscription synchronization after unrecoverable error (RT64463) - If the schema synchronization failed (which is an unrecoverable error) don't keep retrying forever. Instead mark the subscription synchronization as failed and disable the subscription. -- Improve handling and messaging with missing replication sets in output plugin (RT64451) - Report all missing and found sets and make sure the sets are looked up using current snapshot. - -## pglogical 3.6.0.1 - -The pglogical 3.6.0.1 is the first bug-fix release in the pglogical 3.6 series. - -### Resolved Issues - -- Improve synchronous `remote_write` replication performance (RT64397) -- Re-add support for binary protocol - -## pglogical 3.6.0 - -The version 3.6 of pglogical is a major update which brings performance improvements, better conflict handling, bug fixes and infrastructure necessary for BDR 3.6. - -### New Features - -- Significant replication performance improvement - - Cache table synchronization state - - Only send keepalives when necessary - - Only do flush when necessary - - Serialize transactions in fewer cases in walsender (2ndQPostgres) -- Improved replication position reporting which is more in line with how physical streaming replication reports it -- Conflict detection and resolution improvements - - Add new types of conflicts (like `target_table_missing`) - - Add new types of conflict resolvers - - Make conflict resolution configurable by subscription and conflict type - - Improve conflict detection for updates - -### Resolved Issues - -- Don't try to replicate REINDEX on temporary indexes - -### Other Improvements - -- Fix potential message parsing error for two-phase commits -- Make initial COPY of data interruptible diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_rhel8_ppcle.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_rhel8_ppcle.mdx index 5562a1eb135..5d25cd632d8 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_rhel8_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_rhel8_ppcle.mdx @@ -1,65 +1,42 @@ --- -title: "Installing EDB Pgpool-II on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing EDB Pgpool-II on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -There are two steps to completing an installation: +## Prerequisites -- Setting up the repository -- Installing the package +Before you begin the installation process: -For each step, you must be logged in as superuser. +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -To log in as a superuser: +- Set up the repository -```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). + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -1. Install the EPEL repository and refresh the cache: + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` +- Address other prerequisites -1. Enable the `codeready-builder-for-rhel-8-\*-rpms` repository because EPEL packages may depend on packages from it: + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + 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 - ``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -## Installing the package +## Install the package ```shell -dnf -y install edb-pgpool +sudo dnf -y install edb-pgpool ``` -where <xx> is the EDB Pgpool-II version you want to install. +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles12_ppcle.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles12_ppcle.mdx index 405aedcf760..9fd6974cc4a 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles12_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB Pgpool-II on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgpool +sudo zypper -n install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles15_ppcle.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles15_ppcle.mdx index 9b0ff11b8e1..ce4c9899167 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles15_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB Pgpool-II on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgpool +sudo zypper -n install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/index.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/index.mdx index 3c86eb294e3..05029a23318 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/index.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/index.mdx @@ -22,6 +22,7 @@ For platform-specific install instructions, see: - [Rocky Linux 8/AlmaLinux 8](x86_amd64/pgpool_other_linux8_x86) - [RHEL 7/OL 7](x86_amd64/pgpool_rhel7_x86) + - [CentOS 7](x86_amd64/pgpool_centos7_x86) - [SLES 15](x86_amd64/pgpool_sles15_x86) - [SLES 12](x86_amd64/pgpool_sles12_x86) - [Ubuntu 20.04](x86_amd64/pgpool_ubuntu20_x86) diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/index.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/index.mdx index e16585f2fe8..4a1c587fc72 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/index.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/index.mdx @@ -8,6 +8,7 @@ navigation: - pgpool_rhel8_x86 - pgpool_other_linux8_x86 - pgpool_rhel7_x86 + - pgpool_centos7_x86 - pgpool_sles15_x86 - pgpool_sles12_x86 - pgpool_ubuntu20_x86 @@ -21,6 +22,7 @@ For operating system-specific install instructions, see: - [Rocky Linux 8/AlmaLinux 8](pgpool_other_linux8_x86) - [RHEL 7/OL 7](pgpool_rhel7_x86) + - [CentOS 7](pgpool_centos7_x86) - [SLES 15](pgpool_sles15_x86) - [SLES 12](pgpool_sles12_x86) - [Ubuntu 20.04](pgpool_ubuntu20_x86) diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_centos7_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_centos7_x86.mdx new file mode 100644 index 00000000000..418a6f6270d --- /dev/null +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_centos7_x86.mdx @@ -0,0 +1,35 @@ +--- +navTitle: CentOS 7 +title: Installing EDB Pgpool-II on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + + ``` + +## Install the package + +```shell +sudo yum -y install edb-pgpool +``` + +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_deb10_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_deb10_x86.mdx index bb48a7b4071..be05fae2dd4 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_deb10_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing EDB Pgpool-II on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgpool +sudo apt-get -y install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_other_linux8_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_other_linux8_x86.mdx index 410f04dc673..52e44e40aed 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_other_linux8_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_other_linux8_x86.mdx @@ -1,48 +1,37 @@ --- -title: "Installing EDB Pgpool-II on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB Pgpool-II on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- +## Prerequisites +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges, and invoke the platform-specific command: - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Invoke the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```text - dnf -y install epel-release - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -4. Enable the PowerTools repository to satisfy additional package dependencies: - ```text - dnf config-manager --set-enabled PowerTools - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -5. Disable the built-in PostgreSQL module: - ```text - dnf -qy module disable postgresql - ``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` -5. Install EDB Pgpool-II: - ```text - dnf install edb-pgpool - ``` - - where `` is the EDB Pgpool release version. +## Install the package - For example, to install EDB Pgpool 4.3, invoke the following command: - ```text - dnf install edb-pgpool43 - ``` +```shell +sudo dnf -y install edb-pgpool +``` - When you install an RPM package signed by a source that is not recognized by your system, your permission to import the key to your local server may be asked. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y` and press `Return` to continue. - - EDB Pgpool-II is installed in the `/usr/edb/pgpool/` directory, where <x.y> is the installed EDB Pgpool-II version number. - \ No newline at end of file +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel7_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel7_x86.mdx index f5e92f92248..e8ad3a541e4 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel7_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel7_x86.mdx @@ -1,45 +1,35 @@ --- -title: "Installing EDB PgPool-II on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing EDB Pgpool-II on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before creating the repository configuration file, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Perform the following steps to install EDB Pgpool-II: +Before you begin the installation process: -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Invoke the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -4. Enable the `optional`, `extras`, and `HA` repositories to satisfy additional package dependencies: - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -6. Install EDB Pgpool-II: - ```text - yum install edb-pgpool - ``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` - where <xx> is the EDB Pgpool release version. +## Install the package - For example, to install EDB Pgpool 4.3, invoke the following command: - ```text - yum install edb-pgpool43 - ``` +```shell +sudo yum -y install edb-pgpool +``` - When you install an RPM package that is signed by a source that is not recognized by your system, your permission to import the key to your local server may be asked for. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - - EDB Pgpool-II will be installed in the `/usr/edb/pgpool/` directory, where <x.y> is the installed EDB Pgpool-II version number. - \ No newline at end of file +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel8_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel8_x86.mdx index 8987d7fbae3..1db796f9ab1 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel8_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel8_x86.mdx @@ -1,52 +1,40 @@ --- -title: "Installing EDB Pgpool-II on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB Pgpool-II on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before creating the repository configuration file, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Perform the following steps to install EDB Pgpool-II: +Before you begin the installation process: -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Install the Extra Packages for Enterprise Linux (EPEL): - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -4. Enable the `codeready-builder-for-rhel-8-*-rpms` repository to satisfy additional package dependencies: - ```text - ARCH=$( /bin/arch ) + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` +- Address other prerequisites -5. Disable the built-in PostgreSQL module: - ```text - dnf -qy module disable postgresql - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -6. Install EDB Pgpool-II: - ```text - dnf install edb-pgpool - ``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - where <xx> is the EDB Pgpool release version. + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` - For example, to install EDB Pgpool 4.3, invoke the following command: - ```text - dnf install edb-pgpool43 - ``` +## Install the package - When you install an RPM package that is signed by a source that is not recognized by your system, your permission to import the key to your local server may be asked for. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. +```shell +sudo dnf -y install edb-pgpool +``` - EDB Pgpool-II will be installed in the `/usr/edb/pgpool/` directory, where <x.y> is the installed EDB Pgpool-II version number. - \ No newline at end of file +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles12_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles12_x86.mdx index ec378ddd183..461d45a242e 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles12_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB Pgpool-II on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgpool +sudo zypper -n install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles15_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles15_x86.mdx index f18a4a68e05..3fdf69e149b 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles15_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB Pgpool-II on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-pgpool +sudo zypper -n install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu18_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu18_x86.mdx index 51058ecd083..0b4099b4b55 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu18_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB Pgpool-II on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgpool +sudo apt-get -y install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu20_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu20_x86.mdx index e759096f489..10ab9de37cd 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu20_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB Pgpool-II on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-pgpool +sudo apt-get -y install edb-pgpool ``` Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/index.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/index.mdx index c9408257a38..fe8651957a3 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/index.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/index.mdx @@ -2,11 +2,14 @@ title: "Installing Pgpool extensions on IBM Power (ppc64le)" navTitle: "IBM Power (ppc64le)" navigation: + - pgpoolext_rhel8_ppcle - pgpoolext_sles15_ppcle - pgpoolext_sles12_ppcle --- For operating system-specific install instructions, see: + - [RHEL 8](pgpoolext_rhel8_ppcle) + - [SLES 15](pgpoolext_sles15_ppcle) - [SLES 12](pgpoolext_sles12_ppcle) diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_rhel8_ppcle.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_rhel8_ppcle.mdx new file mode 100644 index 00000000000..b8f3c4c86ab --- /dev/null +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_rhel8_ppcle.mdx @@ -0,0 +1,42 @@ +--- +navTitle: RHEL 8 +title: Installing EDB Pgpool-II Extensions on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +--- + +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as--pgpool-extensions +``` + +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles12_ppcle.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles12_ppcle.mdx index d9294049825..d995352b162 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles12_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles12_ppcle.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB Pgpool-II Extensions on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as--pgpool-extensions +sudo zypper -n install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles15_ppcle.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles15_ppcle.mdx index f39e1ea731d..60f0b93af83 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles15_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/pgpoolext_sles15_ppcle.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB Pgpool-II Extensions on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as--pgpool-extensions +sudo zypper -n install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/index.mdx b/product_docs/docs/pgpool/4.3/02_extensions/index.mdx index ff7d235b247..db62788912b 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/index.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/index.mdx @@ -32,6 +32,8 @@ For platform-specific install instructions for PgPool-II extensions, see: - [Debian 10](x86_amd64/pgpoolext_deb10_x86) - Linux on IBM Power (ppc64le): + - [RHEL 8](ibm_power_ppc64le/pgpoolext_rhel8_ppcle) + - [SLES 15](ibm_power_ppc64le/pgpoolext_sles15_ppcle) - [SLES 12](ibm_power_ppc64le/pgpoolext_sles12_ppcle) diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_centos7_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_centos7_x86.mdx index 52daa583480..1a9035be7eb 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_centos7_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_centos7_x86.mdx @@ -1,35 +1,35 @@ --- -title: "Installing Pgpool extensions on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing EDB Pgpool-II Extensions on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Assume superuser privileges and perform the following steps to install EDB Pgpool-II extensions on a CentOS host: +## Prerequisites -1. To install the repository configuration, assume superuser privileges, and invoke the following command: - ```shell - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +Before you begin the installation process: -2. Replace the `USERNAME:PASSWORD` variable with the username and password of a registered EDB user: +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Before installing EDB Pgpool-II, execute the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```shell - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -5. Install EDB Pgpool-II extensions: - ```shell - yum -y install edb-as-pgpool-extensions - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - In the above command, `` is the EDB Postgres Advanced Server version, and `` is the EDB Pgpool-II extension version. For example, to install Pgpool43 extensions for EDB Postgres Advanced Server 14, execute the following command: +- Address other prerequisites + + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + + ``` + +## Install the package ```shell -yum -y install edb-as14-pgpool43-extensions +sudo yum -y install edb-as--pgpool-extensions ``` -The extensions will be available in the `/usr/edb/as/share/extension` directory. +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_deb10_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_deb10_x86.mdx index acff1c56c6f..e767315122a 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_deb10_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_deb10_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Debian 10 title: Installing EDB Pgpool-II Extensions on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as--pgpool-extensions +sudo apt-get -y install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_other_linux8_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_other_linux8_x86.mdx index 7064355d77b..855ec371116 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_other_linux8_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_other_linux8_x86.mdx @@ -1,35 +1,37 @@ --- -title: "Installing Pgpool extensions on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB Pgpool-II Extensions on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Assume superuser privileges and perform the following steps to install EDB Pgpool-II extensions on a CentOS host: - -1. To install the repository configuration, assume superuser privileges, and invoke the following command: - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -2. Replace the `USERNAME:PASSWORD` variable with the username and password of a registered EDB user: - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -3. Before installing EDB Pgpool-II, execute the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```shell - dnf -y install epel-release - ``` - -4. Enable the PowerTools repository to satisfy EPEL package dependencies: - ```shell - dnf config-manager --set-enabled PowerTools - ``` - -5. Install EDB Pgpool-II extensions: - ```shell - dnf install edb-as-pgpool-extensions - ``` - - In the above command, `` is the EDB Postgres Advanced Server version, and `` is the EDB Pgpool-II extension version. - - The extensions will be available in the `/usr/edb/as/share/extension` directory. +## Prerequisites + +Before you begin the installation process: + +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). + +- Set 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 this step. + + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. + +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-pgpool +``` + +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel7_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel7_x86.mdx index ec1a13c57e8..1e2ba430ad9 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel7_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel7_x86.mdx @@ -1,41 +1,35 @@ --- -title: "Installing Pgpool extensions on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing EDB Pgpool-II Extensions on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the repository configuration, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Perform the following steps to install EDB Pgpool-II extensions on an RHEL host: +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges, and invoke the platform-specific command: - ```shell - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Before installing EDB Pgpool-II, execute the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```shell - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -4. Enable the `optional`, `extras`, and `HA` repositories to satisfy EPEL package dependencies: - ```shell - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -5. Install EDB Pgpool-II extensions: - ```shell - yum -y install edb-as-pgpool-extensions - ``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` - For example, to install Pgpool43 extensions for EDB Postgres Advanced Server 14, execute the following command: +## Install the package - ```shell - yum -y install edb-as13-pgpool43-extensions - ``` +```shell +sudo yum -y install edb-as--pgpool-extensions +``` -In the above command, `` is the EDB Postgres Advanced Server version, and `` is the EDB Pgpool-II extension version. The extensions will be available in the `/usr/edb/as/share/extension` directory. +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel8_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel8_x86.mdx index 97430fd39da..fc989e4152d 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel8_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_rhel8_x86.mdx @@ -1,37 +1,40 @@ --- -title: "Installing Pgpool extensions on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing EDB Pgpool-II Extensions on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before installing the repository configuration, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). +## Prerequisites -Perform the following steps to install EDB Pgpool-II extensions on an RHEL host: +Before you begin the installation process: -1. To install the repository configuration, assume superuser privileges, and invoke the following command: - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -2. Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +- Set up the repository -3. Before installing EDB Pgpool-II, execute the following command to install the Extra Packages for Enterprise Linux (EPEL): - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -4. Enable the `codeready-builder-for-rhel-8-*-rpms` repository to satisfy EPEL packages dependency: - ```shell - ARCH=$( /bin/arch ) + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` +- Address other prerequisites -5. Install EDB Pgpool-II extensions: - ```shell - dnf install edb-as-pgpool-extensions - ``` + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -In the above command, `` is the EDB Postgres Advanced Server version, and `` is the EDB Pgpool-II extension version. The extensions will be available in the `/usr/edb/as/share/extension` directory. + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as--pgpool-extensions +``` + +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles12_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles12_x86.mdx index 06cc8882672..b0050b54647 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles12_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles12_x86.mdx @@ -1,45 +1,38 @@ --- navTitle: SLES 12 title: Installing EDB Pgpool-II Extensions on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as--pgpool-extensions +sudo zypper -n install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles15_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles15_x86.mdx index 712367e3cb4..72f687272f7 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles15_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_sles15_x86.mdx @@ -1,44 +1,37 @@ --- navTitle: SLES 15 title: Installing EDB Pgpool-II Extensions on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell -zypper -n install edb-as--pgpool-extensions +sudo zypper -n install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu18_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu18_x86.mdx index c27a441e351..e7a25502e5d 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu18_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu18_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB Pgpool-II Extensions on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as--pgpool-extensions +sudo apt-get -y install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu20_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu20_x86.mdx index 7e83ff5d3fc..94d3284eb69 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu20_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/pgpoolext_ubuntu20_x86.mdx @@ -1,42 +1,27 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB Pgpool-II Extensions on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell -apt-get install edb-as--pgpool-extensions +sudo apt-get -y install edb-as--pgpool-extensions ``` Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.3 and EDB Postgres Advanced Server version 14, the package name would be `edb-as-14-pgpool43-extensions`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_rhel8_ppcle.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_rhel8_ppcle.mdx index 4ebd576481a..d621809b331 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_rhel8_ppcle.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_rhel8_ppcle.mdx @@ -1,51 +1,49 @@ --- navTitle: RHEL 8 title: Installing PostGIS on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Refresh the cache: -dnf makecache + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + # Refresh the cache: + sudo dnf makecache + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell # To install PostGIS 3.2: -dnf install edb-as-postgis32 +sudo dnf -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -dnf install edb-as-postgis3 +sudo dnf -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -dnf install edb-as-postgis +sudo dnf -y install edb-as-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles12_ppcle.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles12_ppcle.mdx index 31e4a814d29..52d79e509c6 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles12_ppcle.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles12_ppcle.mdx @@ -1,52 +1,45 @@ --- navTitle: SLES 12 title: Installing PostGIS on SLES 12 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/ppc64le + sudo SUSEConnect -p sle-sdk/12.5/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +zypper -n install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -zypper install edb-as-postgis3 +zypper -n install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 12: -zypper install edb-as12-postgis +zypper -n install edb-as12-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles15_ppcle.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles15_ppcle.mdx index cc62a68738c..b774d59a214 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles15_ppcle.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles15_ppcle.mdx @@ -1,48 +1,41 @@ --- navTitle: SLES 15 title: Installing PostGIS on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/ppc64le -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +sudo zypper -n install edb-as-postgis32 # To install PostGIS 3.1: -zypper install edb-as-postgis3 +sudo zypper -n install edb-as-postgis3 ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_centos7_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_centos7_x86.mdx index 99b83056646..61a1231b42e 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_centos7_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_centos7_x86.mdx @@ -1,44 +1,42 @@ --- navTitle: CentOS 7 title: Installing PostGIS on CentOS 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` + ``` ## Install the package ```shell # To install PostGIS 3.2: -yum install edb-as-postgis32 +sudo yum -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -yum install edb-as-postgis3 +sudo yum -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 10-12: -yum install edb-as-postgis +sudo yum -y install edb-as-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_deb10_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_deb10_x86.mdx index 45297a67b2a..fd8ed5ac6c2 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_deb10_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_deb10_x86.mdx @@ -1,52 +1,37 @@ --- navTitle: Debian 10 title: Installing PostGIS on Debian 10 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell # To install PostGIS 3.2 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis32 +sudo apt-get -y install edb-as-postgis32 -# To install PostGIS 3.2 using EDB Postgres Advanced Server 12: -apt-get install edb-as-postgis-3.2 +# To install PostGIS 3.2 using EDB Postgres Advanced Server 11-12: +sudo sudo apt-get -y install edb-as-postgis-3.2 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 12: -apt-get install edb-as12-postgis-3.1 +sudo apt-get -y install edb-as12-postgis-3.1 ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_other_linux8_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_other_linux8_x86.mdx index ddb37306098..cfc83b3729f 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_other_linux8_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_other_linux8_x86.mdx @@ -1,48 +1,44 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing PostGIS on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` - -## Set up the repository +Before you begin the installation process: -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +- Set up the repository -# Install the EPEL repository: -dnf -y install epel-release + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Enable additional repositories to resolve dependencies: -dnf config-manager --set-enabled PowerTools + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo dnf -y install epel-release + # Enable additional repositories to resolve dependencies: + sudo dnf config-manager --set-enabled PowerTools + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell # To install PostGIS 3.2: -dnf install edb-as-postgis32 +sudo dnf -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -dnf install edb-as-postgis3 +sudo dnf -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11: -dnf install edb-as11-postgis +sudo dnf -y install edb-as11-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel7_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel7_x86.mdx index 0cebd63c3e8..9aab4141976 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel7_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel7_x86.mdx @@ -1,45 +1,42 @@ --- navTitle: RHEL 7 or OL 7 title: Installing PostGIS on RHEL 7 or OL 7 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - -# Enable additional repositories to resolve dependencies: -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` +- Address other prerequisites + ```shell + # Install the EPEL repository: + sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + # Enable additional repositories to resolve dependencies: + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` ## Install the package ```shell # To install PostGIS 3.2: -yum install edb-as-postgis32 +sudo yum -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -yum install edb-as-postgis3 +sudo yum -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 10-11: -yum install edb-as-postgis +sudo yum -y install edb-as-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel_8_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel_8_x86.mdx index 8afdd351084..9360ff50e28 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel_8_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel_8_x86.mdx @@ -1,48 +1,47 @@ --- navTitle: RHEL 8 or OL 8 title: Installing PostGIS on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Set up the EDB repository: -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Replace '' and '' below with -# your username and password for the EDB repository: -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# Install the EPEL repository: -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +- Address other prerequisites -# Enable additional repositories to resolve dependencies: -ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ```shell + # Install the EPEL repository: + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -# Disable the built-in PostgreSQL module: -dnf -qy module disable postgresql -``` + # Enable additional repositories to resolve dependencies: + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + + # Disable the built-in PostgreSQL module: + sudo dnf -qy module disable postgresql + ``` ## Install the package ```shell # To install PostGIS 3.2: -dnf install edb-as-postgis32 +sudo dnf -y install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -dnf install edb-as-postgis3 +sudo dnf -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -dnf install edb-as-postgis +sudo dnf -y install edb-as-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles12_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles12_x86.mdx index 3de2fb56d5c..0a0b7ae6c21 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles12_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles12_x86.mdx @@ -1,52 +1,45 @@ --- navTitle: SLES 12 title: Installing PostGIS on SLES 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/12.5/x86_64 + sudo SUSEConnect -p sle-sdk/12.5/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +sudo zypper -n install edb-as-postgis32 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -zypper install edb-as-postgis3 +sudo zypper -n install edb-as-postgis3 -# To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -zypper install edb-as12-postgis +# To install PostGIS 3.1 using EDB Postgres Advanced Server 12: +sudo zypper -n install edb-as12-postgis ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles15_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles15_x86.mdx index a31a551b33c..585435f1b85 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles15_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles15_x86.mdx @@ -1,48 +1,41 @@ --- navTitle: SLES 15 title: Installing PostGIS on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +- Set up the repository -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Install SUSEConnect to register the host with SUSE, allowing access -# to SUSE repositories -zypper install SUSEConnect + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. -# 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' +- Address other prerequisites -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/x86_64 + ```shell + # Activate the required SUSE module + sudo SUSEConnect -p PackageHub/15.3/x86_64 -# Refresh the metadata -zypper refresh -``` + # Refresh the metadata + sudo zypper refresh + ``` ## Install the package ```shell # To install PostGIS 3.2: -zypper install edb-as-postgis32 +sudo zypper -n install edb-as-postgis32 # To install PostGIS 3.1: -zypper install edb-as-postgis3 +sudo zypper -n install edb-as-postgis3 ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu18_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu18_x86.mdx index fb6aa706d2b..c039fc920a0 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu18_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu18_x86.mdx @@ -1,52 +1,37 @@ --- navTitle: Ubuntu 18.04 title: Installing PostGIS on Ubuntu 18.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell # To install PostGIS 3.2 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis32 +sudo apt-get -y install edb-as-postgis32 # To install PostGIS 3.2 using EDB Postgres Advanced Server 11-12: -apt-get install edb-as-postgis-3.2 +sudo apt-get -y install edb-as-postgis-3.2 # To install PostGIS 3.1 using EDB Postgres Advanced Server 13-14: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 # To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: -apt-get install edb-as-postgis-3.1 +sudo apt-get -y install edb-as-postgis-3.1 ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu20_x86.mdx b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu20_x86.mdx index 24b17a20c00..634eab786cf 100644 --- a/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu20_x86.mdx +++ b/product_docs/docs/postgis/3.2/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_ubuntu20_x86.mdx @@ -1,46 +1,31 @@ --- navTitle: Ubuntu 20.04 title: Installing PostGIS on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. --- -Before you begin the installation process, log in as superuser. +## Prerequisites -```shell -# To log in as a superuser: -sudo su - -``` +Before you begin the installation process: -## Set up the repository +- Install EDB Postgres Advanced Server on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). -Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -```shell -# Set up the EDB repository -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 +- Set up the repository -# Replace '' and '' below with -# your username and password for the EDB repositories: -echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf + Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. -# Add support for secure APT repositories: -apt-get -y install apt-transport-https - -# Add the EDB signing key. Substitute your EnterpriseDB credentials -# for the '' and '' placeholders. -wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - - -# Update the repository metadata: -apt-get update -``` + To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there. ## Install the package ```shell # To install PostGIS 3.2: -apt-get install edb-as14-postgis32 +sudo apt-get -y install edb-as14-postgis32 # To install PostGIS 3.1: -apt-get install edb-as-postgis3 +sudo apt-get -y install edb-as-postgis3 ``` Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as14-postgis32`. diff --git a/scripts/source/pglogical2.js b/scripts/source/pglogical2.js index 7e3dafd38cc..f3596fdc620 100644 --- a/scripts/source/pglogical2.js +++ b/scripts/source/pglogical2.js @@ -104,6 +104,7 @@ function pglogicalTransformer() { metadata: { title: title, product: "pglogical 2", + generatedBy: `${process.argv[1]} - re-run to regenerate from originalFilePath`, }, data: { type: "root", @@ -146,7 +147,10 @@ function pglogicalTransformer() { path.basename(f.path, ".mdx"), ); files[0].metadata.indexCards = "simple"; - files[0].metadata.directoryDefaults = { iconName: "EdbReplicate" }; + files[0].metadata.directoryDefaults = { + iconName: "EdbReplicate", + editTarget: "originalFilePath", + }; tree.children = files; }; } diff --git a/src/pages/index.js b/src/pages/index.js index b84d5dc0f26..16e0d2ee191 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -216,7 +216,7 @@ const Page = () => ( Slony (Deprecated) - pgLogical 2 + pglogical 2 diff --git a/static/_redirects b/static/_redirects index 05b49d48b26..496ae820b55 100644 --- a/static/_redirects +++ b/static/_redirects @@ -39,7 +39,8 @@ /docs/bdr/latest/* /docs/pgd/latest/overview/bdr/:splat 302 /docs/bdr/4/* /docs/pgd/4/overview/bdr/:splat 301 /docs/bdr/3.7/* /docs/pgd/3.7/bdr/:splat 301 -/docs/bdr/3.6/* /docs/pgd/3.6/bdr/:splat 301 +/docs/bdr/3.6/* /docs/pgd/3.6/ 302 +/docs/pgd/3.6/pglogical/* /docs/pgd/3.6/ 302 /docs/harp/latest/* /docs/pgd/latest/overview/harp/:splat 302 /docs/harp/2/* /docs/pgd/4/overview/harp/:splat 301 /docs/pglogical/latest/* /docs/pgd/3.7/pglogical/:splat 302 @@ -146,6 +147,7 @@ /docs/hadoop_data_adapter/2.0/* /docs/hadoop_data_adapter/latest/ 301 /docs/hadoop_data_adapter/2.0.5/* /docs/hadoop_data_adapter/latest/ 301 /docs/jdbc_connector/42.2.12.1/* /docs/jdbc_connector/latest/ 301 +/docs/jdbc_connector/42.3.3.1/* /docs/jdbc_connector/latest/ 301 /docs/ocl_connector/13.1.4.1/* /docs/ocl_connector/latest/ 301 /docs/odbc_connector/12.0.0.1/* /docs/odbc_connector/latest/ 301 /docs/odbc_connector/12.2.0.1/* /docs/odbc_connector/latest/ 301