diff --git a/advocacy_docs/supported-open-source/pgbackrest/02-installation.mdx b/advocacy_docs/supported-open-source/pgbackrest/02-installation.mdx index 240784d3d5c..4cd4ff776f7 100644 --- a/advocacy_docs/supported-open-source/pgbackrest/02-installation.mdx +++ b/advocacy_docs/supported-open-source/pgbackrest/02-installation.mdx @@ -34,9 +34,9 @@ Once you configured the repositories, run the following command to install pgBac $ sudo yum install pgbackrest ``` -The following additional packages will be installed: +The following additional packages may be installed to satisfy the dependencies: -* `postgresql-libs` +* `libpq5` * `libzstd` ### EDB Postgres Advanced Server diff --git a/install_template/config.yaml b/install_template/config.yaml index 7dafc8fa689..a177b3e89b0 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -189,7 +189,7 @@ products: - name: SLES 15 arch: ppc64le supported versions: [1.16] - - name: EDB PgpoolII + - name: EDB Pgpool-II platforms: - name: CentOS 7 arch: x86_64 @@ -227,7 +227,7 @@ products: - name: SLES 15 arch: ppc64le supported versions: [4.3] - - name: EDB PgpoolII Extensions + - name: EDB Pgpool-II Extensions platforms: - name: CentOS 7 arch: x86_64 @@ -337,16 +337,16 @@ products: supported versions: [9.6, 11, 12, 13, 14] - name: SLES 12 arch: x86_64 - supported versions: [14] + supported versions: [40] - name: SLES 12 arch: ppc64le - supported versions: [14] + supported versions: [40] - name: SLES 15 arch: x86_64 - supported versions: [14] + supported versions: [40] - name: SLES 15 arch: ppc64le - supported versions: [14] + supported versions: [40] - name: Failover Manager platforms: - name: CentOS 7 @@ -427,116 +427,116 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: CentOS 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: RHEL 7 or OL 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: Ubuntu 18.04 or Debian 9 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: Ubuntu 20.04 or Debian 10 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [5] - name: SLES 12 arch: x86_64 - supported versions: [14] + supported versions: [5] - name: SLES 12 arch: ppc64le - supported versions: [14] + supported versions: [5] - name: SLES 15 arch: x86_64 - supported versions: [14] + supported versions: [5] - name: SLES 15 arch: ppc64le - supported versions: [14] + supported versions: [5] - name: MySQL Foreign Data Wrapper platforms: - name: CentOS 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: CentOS 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: RHEL 7 or OL 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: Ubuntu 18.04 or Debian 9 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: Ubuntu 20.04 or Debian 10 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [2] - name: SLES 12 arch: x86_64 - supported versions: [14] + supported versions: [2] - name: SLES 12 arch: ppc64le - supported versions: [14] + supported versions: [2] - name: SLES 15 arch: x86_64 - supported versions: [14] + supported versions: [2] - name: SLES 15 arch: ppc64le - supported versions: [14] + supported versions: [2] - name: PostGIS platforms: - name: CentOS 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: CentOS 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: RHEL 7 or OL 7 arch: ppc64le - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: Ubuntu 18.04 or Debian 9 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: Ubuntu 20.04 or Debian 10 arch: x86_64 - supported versions: [11, 12, 13, 14] + supported versions: [3.1] - name: SLES 12 arch: x86_64 - supported versions: [14] + supported versions: [3.1] - name: SLES 12 arch: ppc64le - supported versions: [14] + supported versions: [3.1] - name: SLES 15 arch: x86_64 - supported versions: [14] + supported versions: [3.1] - name: SLES 15 arch: ppc64le - supported versions: [14] + supported versions: [3.1] - name: Postgres Enterprise Manager platforms: - name: CentOS 7 diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 13aedc19376..ebecc543f8c 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -124,8 +124,8 @@ const moveDoc = async (product, platform, version) => { "hadoop-foreign-data-wrapper": "05", "mongodb-foreign-data-wrapper": "04", "mysql-foreign-data-wrapper": "04", - "edb-pgpoolii": "01", - "edb-pgpoolii-extensions": "pgpoolext", + "edb-pgpool-ii": "01", + "edb-pgpool-ii-extensions": "pgpoolext", postgis: "01a", "edb-jdbc-connector": "04", "edb-ocl-connector": "04", @@ -138,6 +138,10 @@ const moveDoc = async (product, platform, version) => { // prettier-ignore const destFilename = match(context, + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "SLES 12"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_edbplus_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB*Plus", version: 40}, platform: {name: "SLES 15"}}, + (ctx) => `edb_plus/40/03_installing_edb_plus/install_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_dbplus_sles15_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "SLES 12"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/${prefix[plat]}_efm4_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "SLES 15"}}, @@ -154,14 +158,14 @@ const moveDoc = async (product, platform, version) => { (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_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)}/${prefix[plat]}_mtk55_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "MongoDB Foreign Data Wrapper", version: 14}, platform: {name: "SLES 12"}}, - (ctx) => `mongo_data_adapter/14/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mongo_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "MongoDB Foreign Data Wrapper", version: 14}, platform: {name: "SLES 15"}}, - (ctx) => `mongo_data_adapter/14/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mongo_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "MySQL Foreign Data Wrapper", version: 14}, platform: {name: "SLES 12"}}, - (ctx) => `mysql_data_adapter/14/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "MySQL Foreign Data Wrapper", version: 14}, platform: {name: "SLES 15"}}, - (ctx) => `mysql_data_adapter/14/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "SLES 12"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mongo_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "SLES 15"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mongo_sles15_${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)}/${prefix[plat]}_mysql_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 15"}}, + (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_sles15_${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)}/${prefix[plat]}_ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, @@ -170,18 +174,22 @@ const moveDoc = async (product, platform, version) => { (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/${prefix[plat]}_odbc13_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 15"}}, (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/${prefix[plat]}_odbc13_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB PgpoolII", version: 4.3}, platform: {name: "SLES 12"}}, + when({product: {name: "EDB pgBouncer", version: 1.16}, platform: {name: "SLES 12"}}, + (ctx) => `pgbouncer/1.16/01_installation/install_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_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)}/${prefix[plat]}_pgbouncer_sles15_${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)}/${prefix[plat]}_pgpool_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB PgpoolII", version: 4.3}, platform: {name: "SLES 15"}}, - (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/${prefix[plat]}_pgpool_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB PgpoolII Extensions", version: 4.3}, platform: {name: "SLES 12"}}, + when({product: {name: "EDB Pgpool-II", version: 4.3}, platform: {name: "SLES 15"}}, + (ctx) => `pgpool/4.3/01_installing_and_configuring_the_pgpool-II/${fmtArchPath(ctx)}/${prefix[plat]}_pgpool_sles15_${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)}/${prefix[plat]}_pgpoolext_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB PgpoolII Extensions", version: 4.3}, platform: {name: "SLES 15"}}, + when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "SLES 15"}}, (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/${prefix[plat]}_pgpoolext_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "PostGIS", version: 14}, platform: {name: "SLES 12"}}, - (ctx) => `postgis/14/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "PostGIS", version: 14}, platform: {name: "SLES 15"}}, - (ctx) => `postgis/14/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "PostGIS", version: 3.1}, platform: {name: "SLES 12"}}, + (ctx) => `postgis/3.1/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "PostGIS", version: 3.1}, platform: {name: "SLES 15"}}, + (ctx) => `postgis/3.1/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles15_${fmtArchFilename(ctx)}.mdx`), ); function match(context, ...conditions) { diff --git a/install_template/templates/platformBase/_epasVersionInPackageName.njk b/install_template/templates/platformBase/_epasVersionInPackageName.njk new file mode 100644 index 00000000000..8bbb3730ee9 --- /dev/null +++ b/install_template/templates/platformBase/_epasVersionInPackageName.njk @@ -0,0 +1 @@ +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. \ No newline at end of file diff --git a/install_template/templates/platformBase/_shared.njk b/install_template/templates/platformBase/_shared.njk index 37dd7939640..70ed1c6590f 100644 --- a/install_template/templates/platformBase/_shared.njk +++ b/install_template/templates/platformBase/_shared.njk @@ -15,4 +15,6 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` {% endmacro %} -{% macro centosInstallCommand(packageManager, packageName) %}{{packageManager}} -y install {{ packageName }}{% endmacro %} \ No newline at end of file +{% macro centosInstallCommand(packageManager, packageName) %}{{packageManager}} -y install {{ packageName }}{% endmacro %} + + diff --git a/install_template/templates/platformBase/base.njk b/install_template/templates/platformBase/base.njk index dcb98421468..7cb313d4c7b 100644 --- a/install_template/templates/platformBase/base.njk +++ b/install_template/templates/platformBase/base.njk @@ -1,5 +1,5 @@ --- -navTitle: {{ platform.name }} on {{ platform.arch }} +navTitle: {{ platform.name }} title: Installing {{ product.name }} on {{ platform.name }} {{ platform.arch }} --- diff --git a/install_template/templates/platformBase/centos-7.njk b/install_template/templates/platformBase/centos-7.njk index 1ffd4be8d33..90804a5c626 100644 --- a/install_template/templates/platformBase/centos-7.njk +++ b/install_template/templates/platformBase/centos-7.njk @@ -28,7 +28,6 @@ EOF ```shell {{ centosInstallCommand("yum", packageName) }} ``` - !!! Note Once the edb repository is set up, you can install any of the EDB products by using the relevant package name at this step. You can use `yum list available` command to check the available packages. 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 efa92edea7d..69ee9d1be9a 100644 --- a/install_template/templates/platformBase/rhel-8-or-ol-8.njk +++ b/install_template/templates/platformBase/rhel-8-or-ol-8.njk @@ -16,7 +16,6 @@ dnf -qy module disable postgresql ```shell {{ centosInstallCommand("dnf", packageName) }} ``` - !!! Note Once the edb repository is set up, you can install any of the EDB products by using the relevant package name at this step. You can use `dnf list available` command to check the available packages. {% endblock installCommand %} diff --git a/install_template/templates/products/edb-pgpoolii-extensions/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk similarity index 82% rename from install_template/templates/products/edb-pgpoolii-extensions/almalinux-8-or-rocky-linux-8.njk rename to install_template/templates/products/edb-pgpool-ii-extensions/almalinux-8-or-rocky-linux-8.njk index 73204b7cbc9..f7499477eab 100644 --- a/install_template/templates/products/edb-pgpoolii-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,4 +1,4 @@ -{% extends "products/edb-pgpoolii/base.njk" %} +{% extends "products/edb-pgpool-ii/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} {% block prerequisites %} {{ super() }} diff --git a/install_template/templates/products/edb-pgpoolii-extensions/base.njk b/install_template/templates/products/edb-pgpool-ii-extensions/base.njk similarity index 100% rename from install_template/templates/products/edb-pgpoolii-extensions/base.njk rename to install_template/templates/products/edb-pgpool-ii-extensions/base.njk diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk new file mode 100644 index 00000000000..b8fc8288891 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk new file mode 100644 index 00000000000..ce9a0cf72d1 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/centos-7.njk" %} +{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk b/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk new file mode 100644 index 00000000000..65626c6f7ff --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "debian-10" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/debian-9.njk b/install_template/templates/products/edb-pgpool-ii-extensions/debian-9.njk new file mode 100644 index 00000000000..ea4b9141c9d --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/debian-9.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk new file mode 100644 index 00000000000..1b0bcbe374c --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk new file mode 100644 index 00000000000..1ddbea0fcd6 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8-or-ol-8.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8-or-ol-8.njk new file mode 100644 index 00000000000..d8a473077ad --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8-or-ol-8.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/sles-12.njk b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12.njk new file mode 100644 index 00000000000..1f1d8e42297 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk new file mode 100644 index 00000000000..1f1d8e42297 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/sles-15.njk b/install_template/templates/products/edb-pgpool-ii-extensions/sles-15.njk new file mode 100644 index 00000000000..5d2c73ddd91 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/sles-15.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/sles-15_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/sles-15_ppc64le.njk similarity index 54% rename from install_template/templates/products/edb-pgpoolii-extensions/sles-15_ppc64le.njk rename to install_template/templates/products/edb-pgpool-ii-extensions/sles-15_ppc64le.njk index 6550ff3a389..39e562d78cb 100644 --- a/install_template/templates/products/edb-pgpoolii-extensions/sles-15_ppc64le.njk +++ b/install_template/templates/products/edb-pgpool-ii-extensions/sles-15_ppc64le.njk @@ -1,3 +1,3 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} {% set platformBaseTemplate = "sles-15" %} {% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk new file mode 100644 index 00000000000..33530af0112 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk @@ -0,0 +1 @@ +{% extends "products/edb-pgpool-ii-extensions/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-20.04.njk b/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-20.04.njk new file mode 100644 index 00000000000..33530af0112 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-20.04.njk @@ -0,0 +1 @@ +{% extends "products/edb-pgpool-ii-extensions/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpoolii/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk similarity index 82% rename from install_template/templates/products/edb-pgpoolii/almalinux-8-or-rocky-linux-8.njk rename to install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk index 73204b7cbc9..f7499477eab 100644 --- a/install_template/templates/products/edb-pgpoolii/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-pgpool-ii/almalinux-8-or-rocky-linux-8.njk @@ -1,4 +1,4 @@ -{% extends "products/edb-pgpoolii/base.njk" %} +{% extends "products/edb-pgpool-ii/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} {% block prerequisites %} {{ super() }} diff --git a/install_template/templates/products/edb-pgpoolii/base.njk b/install_template/templates/products/edb-pgpool-ii/base.njk similarity index 77% rename from install_template/templates/products/edb-pgpoolii/base.njk rename to install_template/templates/products/edb-pgpool-ii/base.njk index 9dbc78954e0..d1628fb8515 100644 --- a/install_template/templates/products/edb-pgpoolii/base.njk +++ b/install_template/templates/products/edb-pgpool-ii/base.njk @@ -4,5 +4,5 @@ ```shell zypper -n install {{ packageName }} ``` -Where `` is the version of EDB PbPool-II you are installing. +Where `` is the version of EDB PgPool-II you are installing. {% endblock installCommand %} diff --git a/install_template/templates/products/edb-pgpool-ii/centos-7.njk b/install_template/templates/products/edb-pgpool-ii/centos-7.njk new file mode 100644 index 00000000000..f177dd38d1c --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/centos-7.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk new file mode 100644 index 00000000000..81a8da6e3b0 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/centos-7.njk" %} +{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpool-ii/debian-10.njk b/install_template/templates/products/edb-pgpool-ii/debian-10.njk new file mode 100644 index 00000000000..662aad77f95 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/debian-10.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "debian-10" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/debian-9.njk b/install_template/templates/products/edb-pgpool-ii/debian-9.njk new file mode 100644 index 00000000000..35fbac250da --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/debian-9.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk similarity index 50% rename from install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7.njk rename to install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk index 51c924f89e9..4ec372bc95c 100644 --- a/install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk @@ -1,2 +1,2 @@ -{% extends "products/edb-pgpoolii/base.njk" %} +{% extends "products/edb-pgpool-ii/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk new file mode 100644 index 00000000000..1e23d7a8481 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/rhel-7-or-ol-7.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/rhel-8-or-ol-8.njk b/install_template/templates/products/edb-pgpool-ii/rhel-8-or-ol-8.njk similarity index 50% rename from install_template/templates/products/edb-pgpoolii/rhel-8-or-ol-8.njk rename to install_template/templates/products/edb-pgpool-ii/rhel-8-or-ol-8.njk index eaae22b3e1c..e3de9d8ed61 100644 --- a/install_template/templates/products/edb-pgpoolii/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/edb-pgpool-ii/rhel-8-or-ol-8.njk @@ -1,2 +1,2 @@ -{% extends "products/edb-pgpoolii/base.njk" %} +{% extends "products/edb-pgpool-ii/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/sles-12.njk b/install_template/templates/products/edb-pgpool-ii/sles-12.njk new file mode 100644 index 00000000000..4ac98e225cf --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/sles-12.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk new file mode 100644 index 00000000000..4ac98e225cf --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/sles-15.njk b/install_template/templates/products/edb-pgpool-ii/sles-15.njk new file mode 100644 index 00000000000..447bd6f53f1 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/sles-15.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/sles-15_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/sles-15_ppc64le.njk similarity index 59% rename from install_template/templates/products/edb-pgpoolii/sles-15_ppc64le.njk rename to install_template/templates/products/edb-pgpool-ii/sles-15_ppc64le.njk index f6950412ea1..5e712c15ace 100644 --- a/install_template/templates/products/edb-pgpoolii/sles-15_ppc64le.njk +++ b/install_template/templates/products/edb-pgpool-ii/sles-15_ppc64le.njk @@ -1,3 +1,3 @@ -{% extends "products/edb-pgpoolii/base.njk" %} +{% extends "products/edb-pgpool-ii/base.njk" %} {% set platformBaseTemplate = "sles-15" %} {% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk new file mode 100644 index 00000000000..1e18e0443aa --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk @@ -0,0 +1 @@ +{% extends "products/edb-pgpool-ii/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpool-ii/ubuntu-20.04.njk b/install_template/templates/products/edb-pgpool-ii/ubuntu-20.04.njk new file mode 100644 index 00000000000..1e18e0443aa --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/ubuntu-20.04.njk @@ -0,0 +1 @@ +{% extends "products/edb-pgpool-ii/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpoolii-extensions/centos-7.njk b/install_template/templates/products/edb-pgpoolii-extensions/centos-7.njk deleted file mode 100644 index 9fd14588299..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/centos-7.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpoolii-extensions/centos-7_ppc64le.njk deleted file mode 100644 index 64df7efa1f6..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpoolii-extensions/debian-10.njk b/install_template/templates/products/edb-pgpoolii-extensions/debian-10.njk deleted file mode 100644 index 2683b56783c..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/debian-10.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "debian-10" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/debian-9.njk b/install_template/templates/products/edb-pgpoolii-extensions/debian-9.njk deleted file mode 100644 index d9a545ef822..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/debian-9.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7.njk deleted file mode 100644 index 27a7a010b8b..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index fe0a6ae2694..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/rhel-8-or-ol-8.njk b/install_template/templates/products/edb-pgpoolii-extensions/rhel-8-or-ol-8.njk deleted file mode 100644 index 4f4a6e0124e..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/rhel-8-or-ol-8.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/sles-12.njk b/install_template/templates/products/edb-pgpoolii-extensions/sles-12.njk deleted file mode 100644 index d69e0701519..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/sles-12.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpoolii-extensions/sles-12_ppc64le.njk deleted file mode 100644 index d69e0701519..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/sles-12_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/sles-15.njk b/install_template/templates/products/edb-pgpoolii-extensions/sles-15.njk deleted file mode 100644 index da132b4e3ce..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/sles-15.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/base.njk" %} -{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-18.04.njk deleted file mode 100644 index 9548753acca..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-18.04.njk +++ /dev/null @@ -1 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-20.04.njk b/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-20.04.njk deleted file mode 100644 index 9548753acca..00000000000 --- a/install_template/templates/products/edb-pgpoolii-extensions/ubuntu-20.04.njk +++ /dev/null @@ -1 +0,0 @@ -{% extends "products/edb-pgpoolii-extensions/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpoolii/centos-7.njk b/install_template/templates/products/edb-pgpoolii/centos-7.njk deleted file mode 100644 index 0ced08dfc2f..00000000000 --- a/install_template/templates/products/edb-pgpoolii/centos-7.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpoolii/centos-7_ppc64le.njk deleted file mode 100644 index 93c76f789ec..00000000000 --- a/install_template/templates/products/edb-pgpoolii/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpoolii/debian-10.njk b/install_template/templates/products/edb-pgpoolii/debian-10.njk deleted file mode 100644 index 72372bfb8d2..00000000000 --- a/install_template/templates/products/edb-pgpoolii/debian-10.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "debian-10" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/debian-9.njk b/install_template/templates/products/edb-pgpoolii/debian-9.njk deleted file mode 100644 index 995623c5fea..00000000000 --- a/install_template/templates/products/edb-pgpoolii/debian-9.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index 0428d5bdcc4..00000000000 --- a/install_template/templates/products/edb-pgpoolii/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/sles-12.njk b/install_template/templates/products/edb-pgpoolii/sles-12.njk deleted file mode 100644 index df59d96575d..00000000000 --- a/install_template/templates/products/edb-pgpoolii/sles-12.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpoolii/sles-12_ppc64le.njk deleted file mode 100644 index df59d96575d..00000000000 --- a/install_template/templates/products/edb-pgpoolii/sles-12_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/sles-15.njk b/install_template/templates/products/edb-pgpoolii/sles-15.njk deleted file mode 100644 index a43f3e923d4..00000000000 --- a/install_template/templates/products/edb-pgpoolii/sles-15.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpoolii/base.njk" %} -{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpoolii/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpoolii/ubuntu-18.04.njk deleted file mode 100644 index 4050a963575..00000000000 --- a/install_template/templates/products/edb-pgpoolii/ubuntu-18.04.njk +++ /dev/null @@ -1 +0,0 @@ -{% extends "products/edb-pgpoolii/debian-10.njk" %} diff --git a/install_template/templates/products/edb-pgpoolii/ubuntu-20.04.njk b/install_template/templates/products/edb-pgpoolii/ubuntu-20.04.njk deleted file mode 100644 index 4050a963575..00000000000 --- a/install_template/templates/products/edb-pgpoolii/ubuntu-20.04.njk +++ /dev/null @@ -1 +0,0 @@ -{% extends "products/edb-pgpoolii/debian-10.njk" %} 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 49db2d2c787..d6ebd0442f2 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/base.njk @@ -1,2 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} -{% set packageName %}edb-as{{ product.version | replace(".", "") }}-hdfs_fdw{% endset %} +{% set packageName %}edb-as14-hdfs_fdw{% endset %} +{% block installCommand %} +{{ super() }} +{% include "platformBase/_epasVersionInPackageName.njk" %} +{% endblock installCommand %} \ 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 62e9a57152d..ad63a2a3a25 100644 --- a/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/mongodb-foreign-data-wrapper/base.njk @@ -1,2 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} -{% set packageName %}edb-as{{ product.version | replace(".", "") }}-mongo_fdw{% endset %} +{% set packageName %}edb-as14-mongo_fdw{% endset %} +{% block installCommand %} +{{ super() }} +{% include "platformBase/_epasVersionInPackageName.njk" %} +{% endblock installCommand %} \ 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 c8cd9977bdd..777f0b98d2c 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/base.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/base.njk @@ -1,2 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} -{% set packageName %}edb-as{{ product.version | replace(".", "") }}-mysql8_fdw{% endset %} +{% set packageName %}edb-as14-mysql8_fdw{% endset %} +{% block installCommand %} +{{ super() }} +{% include "platformBase/_epasVersionInPackageName.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 6f7d1badffd..e150494ce76 100644 --- a/install_template/templates/products/postgis/base.njk +++ b/install_template/templates/products/postgis/base.njk @@ -1,8 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} -{% set packageName %}edb-as-postgis3{% endset %} +{% set packageName %}edb-as14-postgis3{% endset %} {% block installCommand %} -```shell -zypper -n install {{ packageName }} -``` -Where `` is the version of PostGIS 3 you are installing. -{% endblock installCommand %} +{{ super() }} +{% include "platformBase/_epasVersionInPackageName.njk" %} +{% endblock installCommand %} \ No newline at end of file diff --git a/product_docs/docs/biganimal/release/free_trial/quickstart.mdx b/product_docs/docs/biganimal/release/free_trial/quickstart.mdx index c6f5f9d557a..be074b85e5d 100644 --- a/product_docs/docs/biganimal/release/free_trial/quickstart.mdx +++ b/product_docs/docs/biganimal/release/free_trial/quickstart.mdx @@ -48,7 +48,7 @@ Once your first cluster is fully provisioned, your 14-day free trial officially 1. Select your cluster to get an overview of how it has been configured. Select the **Connect** tab to see more information about how to connect to your cluster. 2. Select the **Overview** tab and copy the **Quick Connect** command. Paste it into a terminal where psql is installed. It will prompt for your password and put you on a SQL command line. - ``` + ```text $ psql -W "postgres://edb_admin@[HOST]:5432/edb_admin?sslmode=require" Password: psql (13.5 (Ubuntu 13.5-2.pgdg20.04+1), server 14.2.1 (Debian 14.2.1-1+deb10)) @@ -72,25 +72,25 @@ We're going to create some sample math data, so we're going to create a database 1. Create a new role called `math`. - ``` + ```sql create user math with password 'math_password'; ``` 2. Grant the `math` role to `edb_admin`. - ``` + ```sql grant math to edb_admin; ``` 3. Create a new `math` database. - ``` + ```sql create database math with owner math; ``` 4. Connect to the `math` database. You're prompted for the `edb_admin` password you provided in Step 2 above. - ``` + ```sql \connect math ``` @@ -150,7 +150,7 @@ We're going to use temporary tables to calculate prime numbers using a [Sieve of 3. Select the largest prime number less than 1000. - ``` + ```sql SELECT max(num) FROM primes WHERE num < 1000; diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud.mdx index f29f7b75870..de917a4441d 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud.mdx @@ -41,13 +41,13 @@ Perform the following steps: 1. Log in to BigAnimal as a user with either the owner or the contributor role. - ``` + ```shell biganimal create-credential --name --address portal.biganimal.com --port 443 ``` 1. Run the `setup-csp` command to set up your cloud provider. The synatx is: - ``` + ```shell setup-csp --provider {--account-id | --subscription-id} --region @@ -57,23 +57,23 @@ Perform the following steps: Here is an example of setting up an AWS account: - ``` + ```shell biganimal setup-csp --provider aws --account-id 123456789102 --region us-east-1 --instance-type aws:r5.large --high-availability --networking private --run ``` Here is an example if setting up an Azure account: - ``` + ```shell biganimal setup-csp --provider azure --subscription-id abc12345-1234-1234-abcd-12345678901 --region eastus --instance-type azure:Standard_E4s_v3 --high-availability --networking private --run ``` For more information on the command arguments, run the following command: - ``` + ```shell biganimal setup-csp --help ``` Alternatively, you can enable the CLI interactive mode to have the CLI guide you through the process: - ``` + ```shell biganimal config set interactive_mode on biganimal setup-csp ``` @@ -91,7 +91,7 @@ Perform the following steps: You need to configure your cloud, if any of the readiness checks are not met, see [Configure your Azure subscription](/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure#configure-your-azure-subscription) or [Configure your AWS account](/biganimal/release/getting_started/preparing_cloud_account/02_preparing_aws/#configure-your-aws-account). 1. If the cloud readiness checks pass, your cloud account is successfully set up. Connect your cloud account to BigAnimal with following command. - ``` + ```shell biganimal connect-csp --provider ``` diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/02_azure_market_setup.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/02_azure_market_setup.mdx index 269b743ef92..c163bdac6e7 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/02_azure_market_setup.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/02_azure_market_setup.mdx @@ -47,7 +47,7 @@ Alternatively, you can run the script in [Azure Cloud Shell](https://azure.micro The syntax of the command is: -``` +```shell curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/create-spn.sh | bash -s -- \ --display-name \ --subscription \ @@ -103,7 +103,7 @@ Add Azure AD Service Principal Owners... If you receive the following error message, you need to request admin consent for your cloud account. Only users with the Azure AD Global Administrator or Privileged Role Administrator role can grant admin consent. -``` +```text ... Error: Please request Azure AD Global Administrator or Privileged Role Administrator to grant admin consent permissions for Service Principal hello-s(77bbxxxx-xxxx-xxxx-xxxx-xxxxxxxx7c54) ``` diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx index 640519ff23a..572e71ead90 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx @@ -124,7 +124,7 @@ You can manually check the requirements instead of using the `biganimal-prefligh To check if an Azure resource provider is registered, use the following command. -``` +```shell az provider show -n Microsoft.ContainerService Namespace RegistrationPolicy RegistrationState diff --git a/product_docs/docs/biganimal/release/migration/cold_migration.mdx b/product_docs/docs/biganimal/release/migration/cold_migration.mdx index 33605668c83..affb28d0a4b 100644 --- a/product_docs/docs/biganimal/release/migration/cold_migration.mdx +++ b/product_docs/docs/biganimal/release/migration/cold_migration.mdx @@ -63,13 +63,13 @@ Access requirements: #### Verify your access 1. Connect to the source database using `psql`. For example: - ``` + ```shell psql -d "host=pg-source user=postgres dbname=postgres" ``` Replace `pg-source` with the actual hostname or IP address of the source database and the `user` and `dbname` values as appropriate. If the connection doesn't work, contact your system and database administrators to make sure that you can access the source database. This might require changes to your `pg_hba.conf` and network settings. If `pg_hba.conf` changes, reload the configuration with either `SELECT pg_reload_conf();` via a psql connection or `pg_ctl reload` in a shell connection to the database host. 2. Connect to the target database using the `edb_admin` user. For example: - ``` + ```shell psql -d "host=pg-target user=edb_admin dbname=edb_admin" ``` Replace `pg-target` with the actual hostname of your BigAnimal cluster. @@ -78,13 +78,13 @@ Access requirements: Export the existing roles from your source Postgres instance by running the following command on the migration host: -``` +```shell pg_dumpall -r -d "host=pg-source user=postgres dbname=postgres" > roles.sql ``` The generated SQL file looks like this: -``` +```sql -- -- PostgreSQL database cluster dump -- @@ -115,17 +115,17 @@ SET standard_conforming_strings = on; As a result, you need to modify the `roles.sql` file to: 1. Remove the lines involving the `postgres` user. For example, remove lines like these: - ``` + ```sql CREATE ROLE postgres; ALTER ROLE postgres WITH SUPERUSER ….; ``` 2. Remove any role with superuser or replication privileges. For example, remove lines like these: - ``` + ```sql CREATE ROLE admin; ALTER ROLE admin WITH SUPERUSER ….; ``` 3. For every role that is created, grant the new role to the `edb_admin` user immediately after creating the user. For example: - ``` + ```sql CREATE ROLE my_role; GRANT my_role TO edb_admin; ``` @@ -133,14 +133,14 @@ SET standard_conforming_strings = on; The role section in the modified file, then, looks similar to: - ``` + ```sql CREATE ROLE my_role; GRANT my_role TO edb_admin; ALTER ROLE my_role WITH INHERIT LOGIN PASSWORD 'SCRAM-SHA-256$4096:my-Scrambled-Password'; ``` 5. From the migration host, execute: - ``` + ```shell psql -1 -f roles.sql -d "postgres://edb_admin@pg-target:5432/edb_admin?sslmode=verify-full" ``` @@ -152,7 +152,7 @@ SET standard_conforming_strings = on; From the migration host, use the `pg_dump` command to export the source database into the target database in BigAnimal. For example: -``` +```shell pg_dump -Fc -d "host=pg-source user=postgres dbname=app" -f app.dump ``` @@ -172,7 +172,7 @@ For further information, see the [`pg_restore` documentation](https://www.postgr Use the `pg_restore` command and the .dump file you created when exporting the source database to import the database into BigAnimal. For example: -``` +```shell pg_restore -C -d "postgres://edb_admin@pg-target:5432/edb_admin?sslmode=verify-full" app.dump ``` @@ -180,7 +180,7 @@ This process might take some time depending on the size of the database and the In case of error, repeat the restore operation once you have deleted the database using the following command: -``` +```shell psql -d "postgres://edb_admin@pg-target:5432/edb_admin?sslmode=verify-full" \ -c ‘DROP DATABASE app’ ``` diff --git a/product_docs/docs/biganimal/release/reference/api.mdx b/product_docs/docs/biganimal/release/reference/api.mdx index 56386e1f1a0..4aed4ba8eeb 100644 --- a/product_docs/docs/biganimal/release/reference/api.mdx +++ b/product_docs/docs/biganimal/release/reference/api.mdx @@ -45,7 +45,7 @@ The response returns the `clientId`, `freetrialClientId`, `issuerUri`, `scope`, EDB recommends that you store the output in environment variables so that including them in the following calls is easier. For example: -``` +```ini CLIENT_ID=pM8PRguGtW9yVnrsvrvpaPyyeS9fVvFh ISSUER_URL=https://auth.biganimal.com SCOPE="openid profile email offline_access" @@ -99,7 +99,7 @@ For example: Store the device code in an environment variable for future use. For example: -``` +```ini DEVICE_CODE=KEOY2_5YjuVsRuIrrR-aq5gs ``` diff --git a/product_docs/docs/biganimal/release/reference/cli.mdx b/product_docs/docs/biganimal/release/reference/cli.mdx index 317efa48f44..d76612da2f5 100644 --- a/product_docs/docs/biganimal/release/reference/cli.mdx +++ b/product_docs/docs/biganimal/release/reference/cli.mdx @@ -11,7 +11,7 @@ The CLI is available for Linux, MacOS, and Windows operating systems. ### Download the binary executable - For Linux operating systems, use the following command to get the latest version of the binary executable: - ``` + ```shell curl -LO "https://cli.biganimal.com/download/$(uname -s)/$(uname -m)/latest/biganimal" ``` @@ -22,20 +22,20 @@ The CLI is available for Linux, MacOS, and Windows operating systems. - For Linux users: 1. Copy the SHA256 checksum code for Linux distribution from the [BigAnimal CLI](https://cli.biganimal.com) page and store it as a local file such as `biganimal_linux_amd64.sha256`. Alternatively, click on the SHA256 code to download it as a file directly and verify the content of the downloaded file is identical to the checksum code showed on the page. 2. From your local shell, validate the binary executable file against the checksum file: - ``` + ```shell echo "$( - password: ************ # - postgresType: epas # - postgresVersion: "13" # + clusterArchitecture: ha # provider: azure # - region: francecentral # - instanceType: azure:Standard_E2s_v3 # + clusterName: my-biganimal-cluster # + password: ************ # + postgresType: epas # + postgresVersion: "14" # + region: eastus # + instanceType: azure:Standard_D4s_v4 # volumeType: azurepremiumstorage # volumeProperties: P1 # - volumePropertySize: "4Gi" # networking: public # - highAvailability: true # - allowIpRangeMap: [[192.168.1.1/16, Sample Description]] # - pgConfigMap: [["application_name","test_app"],["array_nulls","true"]] # + allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # + pgConfigMap: # + application_name: test_app # + array_nulls: true # --- ``` +!!! Note +For backward compatibility, `allowIpRangeMap` and `pgConfigMap` properties also support embedded JSON format. + ``` + allowIpRangeMap: [["9.9.9.9/28", "Allow traffic from App A"],["10.10.10.10/27", "Allow traffic from App B"]] + pgConfigMap: [["application_name","test_app"],["array_nulls","true"]] + ``` +!!! + To create the cluster using the sample configuration file `config_file.yaml`: ```shell biganimal create-cluster --clusterConfigFile ./config_file.yaml ``` +To query an enumeration of valid values for above BigAnimal and cloud service provider related properties, CLI provides you a series of subcommands, for example: you can use `show-cluster-architecture` to list all available cloud architecture to your current login account. + +```shell +biganimal show-cluster-architecture +┌──────────────────────────────────────────────┐ +│ Architecture │ +├────────┬───────────────────────────┬─────────┤ +│ ID │ Name │ Status │ +├────────┼───────────────────────────┼─────────┤ +│ eha │ Extreme High Availability │ enabled │ +│ ha │ High Availability │ enabled │ +│ single │ Single Node │ enabled │ +└────────┴───────────────────────────┴─────────┘ +``` + +!!!Note +"Extreme High Availability" architecture is not enabled by default, to get access to this offering, contact your sales representative or [Support](/biganimal/release/overview/support). +!!! + +For more information !!!Tip You can turn off the confirmation step with the `biganimal disable-confirm` command. !!! @@ -219,7 +252,7 @@ You can turn off the confirmation step with the `biganimal disable-confirm` comm To use your BigAnimal cluster, you first need to get your cluster's connection information. To get your cluster's connection information, use the `show-cluster-connection` command: ``` -$ biganimal show-cluster-connection --name my-biganimal-cluster --provider azure --region eastus (main|✚118) +$ biganimal show-cluster-connection --name my-biganimal-cluster --provider azure --region eastus ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Connection String ┃ ┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ @@ -230,7 +263,7 @@ $ biganimal show-cluster-connection --name my-biganimal-cluster --provider azure !!!tip You can query the complete connection information with other output formats, like JSON or YAML. For example: -``` +```shell biganimal show-cluster-connection --name my-biganimal-cluster --provider azure --region eastus --ouput json ``` !!! @@ -241,54 +274,68 @@ After the cluster is created, you can update attributes of the cluster including - Cluster name - Password of administrator account +- Cluster Architecture - Instance type of cluster - Instance volume properties - Networking - Allowed IP list -- High-availability - Postgres database configuration -For example, to enable high availability, use the `--high-availability` option: +For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: ```shell -$ biganimal update-cluster --name my-biganimal-cluster --provider azure --region eastus --high-availability true +$ biganimal update-cluster --name my-biganimal-cluster --provider azure --region eastus --cidr-blocks --cidr-blocks "9.9.9.9/28=Traffic from App A" ``` To check whether the setting took effect, use the `show-clusters` command and view the detailed cluster information output in JSON format. For example, ```shell -$ biganimal show-clusters --name my-biganimal-cluster --provider azure --region eastus --output json | grep zone - "zoneRedundantHa": true, +$ biganimal show-clusters --name my-biganimal-cluster --provider azure --region eastus --output json | jq '.[0].allowIpRangeMap' +[ + [ + "9.9.9.9/28", + "Traffic from App A" + ] +] ``` ### Update the Postgres configuration of a cluster To update the Postgres configuration of a BigAnimal cluster directly from the CLI: -``` +```shell biganimal update-cluster --id p-gxhkfww1fe --pg-config "application_name=ba_test_app,array_nulls=false" Update Cluster operation is started Cluster ID is "p-gxhkfww1fe" ``` To specify multiple configurations, you can use multiple `--pg-config` flags or include multiple configuration settings as a key-value array string separated by commas in one `--pg-config` flag. If a Postgres setting contains a comma, you need to specify it with a separate `--pg-config` flag. +!!! Note +You can update "Cluster Architecture" with the `--cluster-architecture` flag. The only supported scenario is to update a “Single Node” cluster to a “High Availability” cluster. +!!! + + ### Restore a cluster Biganimal continuously backs up your PostgrSQL clusters. Using CLI you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be a in another region and with different configurations, you can specify new configurations in restore command. For example: -``` -biganimal restore-cluster --name "my-biganimal-cluster" --provider "azure" --region "eastus" --password "mypassword@123" --new-name "my-biganimal-cluster-restored" --new-region="eastus2" --instance-type azure:Standard_E2s_v3 --volume-type azurepremiumstorage --volume-property P1 --networking public --cidr-blocks="10.0.0.1/16=app traffic" --high-availability=true --restore-point 2022-01-26T15:04:05+0800 +```shell +biganimal restore-cluster --name "my-biganimal-cluster" --provider "azure" --region "eastus" --password "mypassword@123" --new-name "my-biganimal-cluster-restored" --new-region="eastus2" --cluster-architecture "single" --instance-type "azure:Standard_E2s_v3" --volume-type "azurepremiumstorage" --volume-property "P1" --networking "public" --cidr-blocks="10.10.10.10/27=Traffic from App B" --restore-point "2022-01-26T15:04:05+0800" ``` The password for the restored cluster is a mandatory. The other parameters, if not specified, inherit the source database's settings. In interactive mode, the source database's settings appear as the default input, or appear as the first option in a selection list. To restore a deleted cluster, use `--from-deleted` flag in the command. +!!! Note +You can restore a cluster in a "Single" cluster to a "High Availability" cluster and vice versa. You can only restore an "Extreme High Availability" cluster to a cluster in using the same architecture. +!!! + ### Delete a cluster To delete a cluster you no longer need, use the `delete-cluster` command. For example: ```shell -$ biganimal delete-cluster --name my-biganimal-cluster --provider azure --region e\ +$ biganimal delete-cluster --name my-biganimal-cluster --provider azure --region eastus ``` You can list all deleted clusters with the `show-deleted-clusters` command and restore them from their history backups as needed. diff --git a/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx b/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx index 80841e4d423..ae008d67202 100644 --- a/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx @@ -6,7 +6,7 @@ Don't use the `edb_admin` database role and `edb_admin` database created when cr To create a new role and database, first connect using `psql`: -``` +```shell psql -W "postgres://edb_admin@xxxxxxxxx.xxxxx.biganimal.io:5432/edb_admin?sslmode=require" ``` diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx index f8873e69648..857894ba118 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx @@ -29,7 +29,7 @@ To walk through an example in your own environment, you need: - Your cluster URL. You can find the URL in the **Connect** tab of your cluster instance in the BigAnimal portal. - The IP address of your cluster. You can find the IP address of your cluster using the following command: - ``` + ```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.218 ``` @@ -41,7 +41,7 @@ To walk through an example in your own environment, you need: 1. Get the resource group details from the Azure CLI or the Azure portal and note the resource group name. For example, if the cluster's virtual network is `vnet-japaneast`, use the following command: - ``` + ```shell $ az network vnet list --query "[?name==\`vnet-japaneast\`].resourceGroup" -o json ``` @@ -66,7 +66,7 @@ To walk through an example in your own environment, you need: You can get the IP address of your cluster with the following command: - ``` + ```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.218 ``` @@ -83,7 +83,7 @@ To walk through an example in your own environment, you need: 5. After the private link service is created, note its alias. The alias is the unique ID for your private service, which you can share with the service consumers. Obtain the alias either from the Azure portal or by using the following CLI command: - ``` + ```shell $ az network private-link-service list --query "[?name=='p-c4j0jfcmp3af2ieok5eg-service-private-link'].alias" -o tsv p-c4j0jfcmp3af2ieok5eg-service-private-link.48f26b42-45dc-4e80-8e3d-307d58d7d274.japaneast.azure.privatelinkservice ``` @@ -134,7 +134,7 @@ To walk through an example in your own environment, you need: 11. You have successfully built a tunnel between your client VM's virtual network and the cluster. You can now access the cluster from the private endpoint in your client VM. The private endpoint's private IP address is associated with an independent virtual network NIC. Get the private endpoint's private IP address using the following commands: - ``` + ```shell $ NICID=$(az network private-endpoint show -n vnet-client-private-pg-service -g rg-client --query "networkInterfaces[0].id" -o tsv) $ az network nic show -n ${NICID##*/} -g rg-client --query "ipConfigurations[0].privateIpAddress" -o tsv 100.64.111.5 @@ -142,7 +142,7 @@ To walk through an example in your own environment, you need: 12. From the client VM `vm-client`, access the cluster by using the private IP address: - ``` + ```shell $ psql -h 100.64.111.5 -U edb_admin Password for user edb_admin : @@ -185,7 +185,7 @@ With a Private DNS Zone, you configure a DNS entry for your cluster's public hos 7. You can now access your cluster with this private domain name. - ``` + ```shell $ dig +short p-c4iabjleig40jngmac40.brcxzr08qr7rbei1.biganimal.io 10.240.1.123 @@ -203,6 +203,6 @@ With a Private DNS Zone, you configure a DNS entry for your cluster's public hos !!! Tip You might need to flush your local DNS cache to resolve your domain name to the new private IP address after adding the private endpoint. For example, on Ubuntu, run the following command: - ``` + ```shell $ sudo systemd-resolve --flush-caches ``` diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx index ed4f7a07ab6..44c82b1c981 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx @@ -31,7 +31,7 @@ To walk through an example in your own environment, you need: - Your cluster URL. You can find the URL in the **Connect** tab of your cluster instance in the BigAnimal portal. - The IP address of your cluster. You can find the IP address of your cluster using the following command: - ``` + ```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.218 ``` @@ -62,7 +62,7 @@ You need to add two peering links, one from the client VM's VNet `vnet-client` a Access the cluster with its domain name from your cluster's connection string. It's accessible from `vnet-client` after peering. -``` +```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.123 diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx index b886a274bbb..72724598765 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx @@ -33,7 +33,7 @@ To walk through an example in your own environment, you need: - Your cluster URL. You can find the URL in the **Connect** tab of your cluster instance in the BigAnimal portal. - The IP address of your cluster. You can find the IP address of your cluster using the following command: - ``` + ```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.218 ``` @@ -67,21 +67,21 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga **From the BigAnimal subscription**: - ``` + ```shell $ az network vnet-gateway show -n vpng-biganimal -g brCxzr08qr7RBEi1-rg-japaneast-management --query "[id]" -otsv subscriptions/.../vpng-biganimal ``` **From the client VM's subscription**: - ``` + ```shell $ az network vnet-gateway show -n vpng-client -g rg-client --query "[id]" -o tsv /subscriptions/.../vpng-client ``` 2. From the BigAnimal subscription, create a connection from `vpng-biganimal` to `vpng-client`. - ``` + ```shell $ az network vpn-connection create -n vpnc-biganimal-client -g brCxzr08qr7RBEi1-rg-japaneast-management --vnet-gateway1 /subscriptions/.../vpng-biganimal -l japaneast --shared-key "a_very_long_and_complex_psk" \--vnet-gateway2 /subscriptions/.../vpng-client ``` @@ -90,7 +90,7 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga 3. From the client VM's subscription, create another connection from `vpng-client` to `vpng-ebdcloud`. - ``` + ```shell $ az network vpn-connection create -n vpnc-client-biganimal -g rg-client --vnet-gateway1 /subscriptions/.../vpng-client -l japaneast --shared-key "a_very_long_and_complex_psk!" --vnet-gateway2 /subscriptions/.../vpng-biganimal ``` @@ -98,14 +98,14 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga 1. After a few minutes, verify the gateway connection status from either virtual networks with the following command: - ``` + ```shell $ az network vpn-connection show --name vpnc-client-biganimal -g rg-client --query "[connectionStatus]" -o tsv Connected ``` 2. Verify the connectivity to the cluster: - ``` + ```shell $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io 10.240.1.123 diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx index e02c3825db7..2c7e9665e58 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx @@ -98,7 +98,7 @@ Now that your endpoint service is created, you can connect it to the cluster VPC In your application's AWS account, select the **Load Balancers** service, search for the load balancer with cluster ID you want to access, and use the DNS name provided in the details section to access your cluster. - ``` + ```shell $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin Password for user edb_admin: diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx index a86dd41a13c..bef71dcec38 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx @@ -91,7 +91,7 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. -``` +```shell $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin Password for user edb_admin: @@ -132,7 +132,7 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. -``` +```shell $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin Password for user edb_admin: diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx index fce1b42ffce..4cce19cc550 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx @@ -40,7 +40,7 @@ Different clients can have different default TLS/SSL modes (sslmode). For exampl For public connections and in most environments, EDB recommends setting `sslmode` to `verify-full`. This setting ensures that you connect to the server you specified and that the connection is encrypted. BigAnimal generates certificates with LetsEncrypt, a widely trusted certificate authority. Your client machine might already have a bundled CA certificate for LetsEncrypt, for example, at `/etc/ssl/certs/ca-certificates.crt` or `/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem`. If it doesn't, your client machine needs a [CA certificate for Let's Encrypt](https://letsencrypt.org/certificates/). Once the CA certificate is in place on your client machine, configure the `sslrootcert` parameter to its location and set the `sslmode` parameter to `verify-full` to verify the certificate to fully validate the connection: -``` +```shell psql -W "postgres://edb_admin@xxxxxxxxx.xxxxx.biganimal.io:5432/edb_admin?sslmode=verify-full&sslrootcert=/usr/share/ca-certificates/isrgrootx1.pem" ``` diff --git a/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx b/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx index 228c3051c1f..32113ab2c4e 100644 --- a/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx @@ -66,7 +66,7 @@ chinook=> Let's take a look at the schema: -``` +```sql \dt __OUTPUT__ List of relations @@ -88,7 +88,7 @@ __OUTPUT__ There's an employee table, let's examine its definition: -``` +```sql \d+ employee __OUTPUT__ Table "public.employee" diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/11_dbplus_sles15_ppcle.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/11_dbplus_sles15_ppcle.mdx new file mode 100644 index 00000000000..8d389a23eac --- /dev/null +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/11_dbplus_sles15_ppcle.mdx @@ -0,0 +1,110 @@ +--- +navTitle: SLES 15 +title: Installing EDB*Plus on SLES 15 ppc64le +--- + +Before you begin the installation process, log in as superuser. + +```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). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as40-edbplus +``` + +## Initial configuration + +After performing an RPM installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation. Use the following commands to set variable values: + +```text +export JAVA_HOME= +export PATH=/bin:$PATH +``` + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication. Before invoking EDB\*Plus, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +You must confirm that an `identd` server is installed and running. You can use the package manager to install an `identd` server by invoking the command: + +```text +zypper -y install xinetd authd +``` + +The command should create a file named `/etc/xinetd.d/auth` that contains: + +```text +service auth +{ + disable = yes + socket_type = stream +wait =no +user = ident +cps = 4096 10 +instances = UNLIMITED +server = /usr/sbin/in.authd server_args = -t60 --xerror –os +} +``` + +!!! Note +If the file includes a `-E` argument at the end of the server arguments, please erase `-E`. + +Then, to start the `identd` server, invoke the following commands: + +```text +systemctl enable xinetd +systemctl start xinetd +``` + +Open the `pg_ident.conf` file and create a user mapping: + +```text +# map_name system_username postgres_username + edbas enterprisedb enterprisedb +``` + +Where: + +- The name specified in the `map_name` column is a user-defined name that will identify the mapping in the `pg_hba.conf` file. +- The name specified in the `system_username` column is `enterprisedb`. +- The name specified in the `postgres_username` column is `enterprisedb`. + +Then, open the `pg_hba.conf` file and modify the `IDENT` entries: + +- If you are using an IPv4 local connection, modify the file entry to read: + + `host all all 127.0.0.0/0 ident map=edbas` + +- If you are using an IPv6 local connection, modify the file entry to read: + + `host all all ::1/128 ident map=edbas` + +You must restart the Advanced Server service before invoking EDB\*Plus. For detailed information about controlling the Advanced Server service, see the online documentation for [EDB Postgres Advanced Server](/epas/latest/). diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/12_edbplus_sles12_ppcle.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/12_edbplus_sles12_ppcle.mdx index 9309b9fd68a..6dc847cee25 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/12_edbplus_sles12_ppcle.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/12_edbplus_sles12_ppcle.mdx @@ -1,50 +1,111 @@ --- -title: "Installing EDB*Plus on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB*Plus on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 # 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 +# 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 -# You can skip this step if already registered +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules on SUSE 12 +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le # Refresh the metadata zypper refresh - -# Install OpenJDK (version 1.8) for Java based components -zypper -n install java-1_8_0-openjdk ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as14-edbplus +zypper -n install edb-as40-edbplus +``` + +## Initial configuration + +After performing an RPM installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation. Use the following commands to set variable values: + +```text +export JAVA_HOME= +export PATH=/bin:$PATH +``` + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication. Before invoking EDB\*Plus, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +You must confirm that an `identd` server is installed and running. You can use the package manager to install an `identd` server by invoking the command: + +```text +zypper -y install xinetd authd +``` + +The command should create a file named `/etc/xinetd.d/auth` that contains: + +```text +service auth +{ + disable = yes + socket_type = stream +wait =no +user = ident +cps = 4096 10 +instances = UNLIMITED +server = /usr/sbin/in.authd server_args = -t60 --xerror –os +} ``` + +!!! Note +If the file includes a `-E` argument at the end of the server arguments, please erase `-E`. + +Then, to start the `identd` server, invoke the following commands: + +```text +systemctl enable xinetd +systemctl start xinetd +``` + +Open the `pg_ident.conf` file and create a user mapping: + +```text +# map_name system_username postgres_username + edbas enterprisedb enterprisedb +``` + +Where: + +- The name specified in the `map_name` column is a user-defined name that will identify the mapping in the `pg_hba.conf` file. +- The name specified in the `system_username` column is `enterprisedb`. +- The name specified in the `postgres_username` column is `enterprisedb`. + +Then, open the `pg_hba.conf` file and modify the `IDENT` entries: + +- If you are using an IPv4 local connection, modify the file entry to read: + + `host all all 127.0.0.0/0 ident map=edbas` + +- If you are using an IPv6 local connection, modify the file entry to read: + + `host all all ::1/128 ident map=edbas` + +You must restart the Advanced Server service before invoking EDB\*Plus. For detailed information about controlling the Advanced Server service, see the online documentation for [EDB Postgres Advanced Server](/epas/latest/). 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 097d487803d..14a3683136f 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 @@ -33,8 +33,10 @@ For platform-specific install instructions, see: - [CentOS 7](x86_amd64/04_edbplus_centos7_x86) - [SLES 15](x86_amd64/05_edbplus_sles15_x86) - [SLES 12](x86_amd64/06_edbplus_sles12_x86) - - [Ubuntu 20.04 or 18.04/Debian 10](x86_amd64/07_edbplus_ubuntu18_20_deb10_x86) - - [Debian 9](x86_amd64/08_edbplus_deb9_x86) + - [Ubuntu 20.04](x86_amd64/07_edbplus_ubuntu20_x86) + - [Ubuntu 18.04](x86_amd64/07a_edbplus_ubuntu18_x86) + - [Debian 10](x86_amd64/08_edbplus_deb10_x86) + - [Debian 9](x86_amd64/08a_edbplus_deb9_x86) - Linux on IBM Power (ppc64le): - [RHEL 7](ibm_power_ppc64le/10_edbplus_rhel7_ppcle) diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/05_dbplus_sles15_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/05_dbplus_sles15_x86.mdx new file mode 100644 index 00000000000..37be3be9b2f --- /dev/null +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/05_dbplus_sles15_x86.mdx @@ -0,0 +1,110 @@ +--- +navTitle: SLES 15 +title: Installing EDB*Plus on SLES 15 x86_64 +--- + +Before you begin the installation process, log in as superuser. + +```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). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/x86_64 + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as40-edbplus +``` + +## Initial configuration + +After performing an RPM installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation. Use the following commands to set variable values: + +```text +export JAVA_HOME= +export PATH=/bin:$PATH +``` + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication. Before invoking EDB\*Plus, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +You must confirm that an `identd` server is installed and running. You can use the package manager to install an `identd` server by invoking the command: + +```text +zypper -y install xinetd authd +``` + +The command should create a file named `/etc/xinetd.d/auth` that contains: + +```text +service auth +{ + disable = yes + socket_type = stream +wait =no +user = ident +cps = 4096 10 +instances = UNLIMITED +server = /usr/sbin/in.authd server_args = -t60 --xerror –os +} +``` + +!!! Note +If the file includes a `-E` argument at the end of the server arguments, please erase `-E`. + +Then, to start the `identd` server, invoke the following commands: + +```text +systemctl enable xinetd +systemctl start xinetd +``` + +Open the `pg_ident.conf` file and create a user mapping: + +```text +# map_name system_username postgres_username + edbas enterprisedb enterprisedb +``` + +Where: + +- The name specified in the `map_name` column is a user-defined name that will identify the mapping in the `pg_hba.conf` file. +- The name specified in the `system_username` column is `enterprisedb`. +- The name specified in the `postgres_username` column is `enterprisedb`. + +Then, open the `pg_hba.conf` file and modify the `IDENT` entries: + +- If you are using an IPv4 local connection, modify the file entry to read: + + `host all all 127.0.0.0/0 ident map=edbas` + +- If you are using an IPv6 local connection, modify the file entry to read: + + `host all all ::1/128 ident map=edbas` + +You must restart the Advanced Server service before invoking EDB\*Plus. For detailed information about controlling the Advanced Server service, see the online documentation for [EDB Postgres Advanced Server](/epas/latest/). diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/06_edbplus_sles12_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/06_edbplus_sles12_x86.mdx index b8ae4e76ac4..fe6106fe136 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/06_edbplus_sles12_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/06_edbplus_sles12_x86.mdx @@ -1,51 +1,111 @@ --- -title: "Installing EDB*Plus on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB*Plus on SLES 12 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 # 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 +# 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 -# You can skip this step if already registered -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules on SUSE 12 +# 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 - -# Install OpenJDK (version 1.8) for Java based components -zypper -n install java-1_8_0-openjdk ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as14-edbplus +zypper -n install edb-as40-edbplus +``` + +## Initial configuration + +After performing an RPM installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation. Use the following commands to set variable values: + +```text +export JAVA_HOME= +export PATH=/bin:$PATH +``` + +By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication. Before invoking EDB\*Plus, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: + +You must confirm that an `identd` server is installed and running. You can use the package manager to install an `identd` server by invoking the command: + +```text +zypper -y install xinetd authd +``` + +The command should create a file named `/etc/xinetd.d/auth` that contains: + +```text +service auth +{ + disable = yes + socket_type = stream +wait =no +user = ident +cps = 4096 10 +instances = UNLIMITED +server = /usr/sbin/in.authd server_args = -t60 --xerror –os +} ``` +!!! Note +If the file includes a `-E` argument at the end of the server arguments, please erase `-E`. + +Then, to start the `identd` server, invoke the following commands: + +```text +systemctl enable xinetd +systemctl start xinetd +``` + +Open the `pg_ident.conf` file and create a user mapping: + +```text +# map_name system_username postgres_username + edbas enterprisedb enterprisedb +``` + +Where: + +- The name specified in the `map_name` column is a user-defined name that will identify the mapping in the `pg_hba.conf` file. +- The name specified in the `system_username` column is `enterprisedb`. +- The name specified in the `postgres_username` column is `enterprisedb`. + +Then, open the `pg_hba.conf` file and modify the `IDENT` entries: + +- If you are using an IPv4 local connection, modify the file entry to read: + + `host all all 127.0.0.0/0 ident map=edbas` + +- If you are using an IPv6 local connection, modify the file entry to read: + + `host all all ::1/128 ident map=edbas` + +You must restart the Advanced Server service before invoking EDB\*Plus. For detailed information about controlling the Advanced Server service, see the online documentation for [EDB Postgres Advanced Server](/epas/latest/). diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu18_20_deb10_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu20_x86.mdx similarity index 93% rename from product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu18_20_deb10_x86.mdx rename to product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu20_x86.mdx index 3a09b444ffb..a16f3dab603 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu18_20_deb10_x86.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07_edbplus_ubuntu20_x86.mdx @@ -1,6 +1,6 @@ --- -title: "Installing EDB*Plus on Ubuntu 20.04 or 18.04/Debian 10 x86" -navTitle: "Ubuntu 20.04 or 18.04/Debian 10" +title: "Installing EDB*Plus on Ubuntu 20.04 x86" +navTitle: "Ubuntu 20.04" --- To install EDB\*Plus on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07a_edbplus_ubuntu18_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07a_edbplus_ubuntu18_x86.mdx new file mode 100644 index 00000000000..21f90cdc64f --- /dev/null +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/07a_edbplus_ubuntu18_x86.mdx @@ -0,0 +1,60 @@ +--- +title: "Installing EDB*Plus on Ubuntu 18.04 x86" +navTitle: "Ubuntu 18.04" +--- + +To install EDB\*Plus on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: + + + +The following steps will walk you through using the EDB apt repository to install a debian package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. + +1. Assume superuser privileges: + ```text + sudo su - + ``` + +1. Configure the EDB repository: + + On Ubuntu 20: + + ```text + sh -c 'echo "deb https://USERNAME:PASSWORD@apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + On Debian 10: + + a. Set up the EDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + ```text + apt-get -y install apt-transport-https + ``` + +1. Add the EDB signing key: + ```text + wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + ``` + +1. Update the repository metadata: + ```text + apt-get update + ``` + +1. Install the package: + ```text + apt-get -y install edb-asxx-edbplus + ``` + + Where, `xx` is the Advanced Server version. + diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08_edbplus_deb10_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08_edbplus_deb10_x86.mdx new file mode 100644 index 00000000000..5bbcf1782ab --- /dev/null +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08_edbplus_deb10_x86.mdx @@ -0,0 +1,60 @@ +--- +title: "Installing EDB*Plus on Debian 10 x86" +navTitle: "Debian 10" +--- + +To install EDB\*Plus on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: + + + +The following steps will walk you through using the EDB apt repository to install a debian package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. + +1. Assume superuser privileges: + ```text + sudo su - + ``` + +1. Configure the EDB repository: + + On Ubuntu 20: + + ```text + sh -c 'echo "deb https://USERNAME:PASSWORD@apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + On Debian 10: + + a. Set up the EDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +1. Add support to your system for secure APT repositories: + ```text + apt-get -y install apt-transport-https + ``` + +1. Add the EDB signing key: + ```text + wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + ``` + +1. Update the repository metadata: + ```text + apt-get update + ``` + +1. Install the package: + ```text + apt-get -y install edb-asxx-edbplus + ``` + + Where, `xx` is the Advanced Server version. + diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08_edbplus_deb9_x86.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08a_edbplus_deb9_x86.mdx similarity index 100% rename from product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08_edbplus_deb9_x86.mdx rename to product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/08a_edbplus_deb9_x86.mdx diff --git a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/index.mdx b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/index.mdx index 5971ead4dd5..38c30fba4f7 100644 --- a/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/index.mdx +++ b/product_docs/docs/edb_plus/40/03_installing_edb_plus/install_on_linux/x86_amd64/index.mdx @@ -12,5 +12,7 @@ For operating system-specific install instructions, see: - [CentOS 7](04_edbplus_centos7_x86) - [SLES 15](05_edbplus_sles15_x86) - [SLES 12](06_edbplus_sles12_x86) - - [Ubuntu 20.04 or 18.04/Debian 10](07_edbplus_ubuntu18_20_deb10_x86) - - [Debian 9](08_edbplus_deb9_x86) + - [Ubuntu 20.04](07_edbplus_ubuntu20_x86) + - [Ubuntu 18.04](07a_edbplus_ubuntu18_x86) + - [Debian 10](08_edbplus_deb10_x86) + - [Debian 9](08a_edbplus_deb9_x86) diff --git a/product_docs/docs/efm/4/01_prerequisites.mdx b/product_docs/docs/efm/4/01_prerequisites.mdx index 529727a2ef7..3b43123bee1 100644 --- a/product_docs/docs/efm/4/01_prerequisites.mdx +++ b/product_docs/docs/efm/4/01_prerequisites.mdx @@ -37,7 +37,7 @@ On database version 12 or later, the `primary_conninfo` and `restore_command` pr You must modify `pg_hba.conf` on the primary and standby nodes, adding entries that allow communication between all of the nodes in the cluster. The following example shows entries you might make to the `pg_hba.conf` file on the primary node: -```text +```shell # access for itself host fmdb efm 127.0.0.1/32 md5 # access for standby @@ -68,7 +68,7 @@ To prevent this condition, ensure that the Failover Manager agent auto starts be If a Linux firewall (that is, iptables) is enabled on the host of a Failover Manager node, you might need to add rules to the firewall configuration that allow tcp communication between the Failover Manager processes in the cluster. For example: -```text +``` # iptables -I INPUT -p tcp --dport 7800 -j ACCEPT /sbin/service iptables save ``` @@ -98,7 +98,7 @@ For detailed information about each of these functions, see the [PostgreSQL core The user must also have permissions to read the values of configuration variables. A database superuser can use the PostgreSQL `GRANT` command to provide the permissions needed: -```text +```sql GRANT pg_read_all_settings TO ; ``` diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx deleted file mode 100644 index bbc969299b4..00000000000 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: "Installing Failover Manager on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" ---- - - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Performing the initial configuration](#initial-configuration) - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE module -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-efmedb-efm<4x> -``` - -Where <4x> is the version of Failover Manager you are installing. - -## Initial configuration - -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). - -After installing on each node of the cluster: - -1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. -3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx deleted file mode 100644 index efa0caa80a0..00000000000 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: "Installing Failover Manager on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" ---- - -There are two steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Initial configuration](#initial-configuration) - - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the Repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE modules -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh -``` - -## Installing the Package - -```shell -zypper -n install edb-efm<4x> -``` - -Where <4x> is the version of Failover Manager you are installing. - -## Initial configuration - -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). - -After installing on each node of the cluster: - -1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. -3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/09_efm4_rhel8_ppcle.mdx similarity index 100% rename from product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/09_efm4_rhel8_ppcle.mdx diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/10_efm4_rhel7_ppcle.mdx similarity index 97% rename from product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/10_efm4_rhel7_ppcle.mdx index 19e3c681e3b..1533b39bdc5 100644 --- a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/10_efm4_rhel7_ppcle.mdx @@ -10,7 +10,7 @@ To request credentials that allow you to access an EnterpriseDB repository, see 1. Create a configuration file and install Advance Toolchain: - ```text + ```shell rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` 4. Install the EPEL repository: - ```text + ```shell yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` 5. On RHEL 7 ppc64le, enable the additional repositories to resolve EPEL dependencies: - ```text + ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` 6. Install the selected package: - ```text + ```shell yum -y install edb-efm42 ``` ## Initial configuration diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/11_efm4_sles15_ppcle.mdx new file mode 100644 index 00000000000..4794661d8c9 --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/11_efm4_sles15_ppcle.mdx @@ -0,0 +1,56 @@ +--- +navTitle: SLES 15 +title: Installing Failover Manager on SLES 15 ppc64le +--- + +Before you begin the installation process, log in as superuser. + +```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). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-efm<4x> +``` + +Where `<4x>` is the version of Failover Manager you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. + +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/12_efm4_sles12_ppcle.mdx new file mode 100644 index 00000000000..bd4733c0d17 --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/12_efm4_sles12_ppcle.mdx @@ -0,0 +1,57 @@ +--- +navTitle: SLES 12 +title: Installing Failover Manager on SLES 12 ppc64le +--- + +Before you begin the installation process, log in as superuser. + +```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). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/12.5/ppc64le +SUSEConnect -p sle-sdk/12.5/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-efm<4x> +``` + +Where `<4x>` is the version of Failover Manager you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. + +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/index.mdx similarity index 100% rename from product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/index.mdx diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index bbd7434491c..d89c04c7df9 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -16,35 +16,35 @@ After receiving your credentials, you must create the EnterpriseDB repository co ## Installing 1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text + ```shell dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` 2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: - ```text + ```shell sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` 3. Install the EPEL repository: - ```text + ```shell dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` 4. Enable the additional repositories to resolve dependencies: - ```text + ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` 5. Disable the built-in PostgreSQL module: - ```text + ```shell dnf -qy module disable postgresql ``` 6. Install the selected package: - ```text + ```shell dnf -y install edb-efm42 ``` diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index c198cbaa6c2..2da9faf6233 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -16,34 +16,34 @@ After receiving your credentials, you must create the EnterpriseDB repository co ## Installing 1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text + ```shell dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` 2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: - ```text + ```shell sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` 3. Install the EPEL repository: - ```text + ```shell dnf -y install epel-release ``` 4. Enable the additional repositories to resolve dependencies: - ```text + ```shell dnf config-manager --set-enabled PowerTools ``` 5. Disable the built-in PostgreSQL module: - ```text + ```shell dnf -qy module disable postgresql ``` 6. Install the selected package: - ```text + ```shell dnf -y install edb-efm42 ``` diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index e0ec497e10c..74077127aa6 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -18,31 +18,31 @@ After receiving your credentials, you must create the EnterpriseDB repository co 1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text + ```shell yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` 2. Replace ‘USERNAME:PASSWORD’ with your username and password for the EDB repositories: - ```text + ```shell sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` 3. Install the EPEL repository: - ```text + ```shell yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` 4. Enable the additional repositories to resolve dependencies: - ```text + ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` 5. Install the selected package: - ```text + ```shell yum -y install edb-efm42 ``` diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 578979eb65b..53da0304514 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -18,25 +18,25 @@ After receiving your credentials, you must create the EnterpriseDB repository co 1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text + ```shell yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` 2. Replace ‘USERNAME:PASSWORD’ with your username and password for the EDB repositories: - ```text + ```shell sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` 3. Install the EPEL repository: - ```text + ```shell yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` 5. Install the selected package: - ```text + ```shell yum -y install edb-efm42 ``` diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index b0571570e73..cf4fc36e920 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -1,64 +1,56 @@ --- -title: "Installing Failover Manager on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Failover Manager on SLES 15 x86_64 --- -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Performing the initial configuration](#initial-configuration) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-efm<4x> ``` -Where <4x> is the version of Failover Manager you are installing. - +Where `<4x>` is the version of Failover Manager you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index c9fa3dbd81e..b9c1a807545 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,64 +1,57 @@ --- -title: "Installing Failover Manager on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing Failover Manager on SLES 12 x86_64 --- -To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the instructions to [access EDB software repositories](https://www.enterprisedb.com/repository-access-request). +Before you begin the installation process, log in as superuser. -You can use the `zypper` package manager to install a Failover Manager agent on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package but requires access to specific repositories that are not hosted at EnterpriseDB. +```shell +# To log in as a superuser: +sudo su - +``` -## Installing +## Set up the repository -1. Assume superuser privileges and stop any firewalls before installing Failover Manager. Then, use the following commands to add EnterpriseDB repositories to your system: +Setting 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). - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -2. The commands create the repository configuration files in the `/etc/zypp/repos.d` directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - ```text - zypper refresh - ``` +# 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' - When prompted, provide credentials for the repository, specify to always trust the provided key, and update the metadata to include the EnterpriseDB repository. +# Activate the required SUSE module -3. Add SUSEConnect and the SUSE Package Hub extension to the SLES host and register the host with SUSE, allowing access to SUSE repositories: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ```text - zypper install SUSEConnect - SUSEConnect -r -e - SUSEConnect -p PackageHub/12.4/x86_64 - SUSEConnect -p sle-sdk/12.4/x86_64 - ``` +# Refresh the metadata +zypper refresh +``` -4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: +## Install the package - ```text - zypper addrepo https://download.opensuse.org/repositories/Apache:/Modules/SLE_12_SP4/Apache:Modules.repo - ``` +```shell +zypper -n install edb-efm<4x> +``` -5. Install OpenJDK (version 1.8) for Java-based components: - - ```text - zypper -n install java-1_8_0-openjdk - ``` - -6. Use the `zypper` utility to install a Failover Manager agent: - - ```text - zypper -n install edb-efm<4x> - ``` - - Where <4x> is the version of Failover Manager you are installing. +Where `<4x>` is the version of Failover Manager you are installing. For example, if you are installing version 4.0, the package name would be `edb-efm40`. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: -1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +1. Modify the [cluster properties file](../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../04_configuring_efm/03_cluster_members/#cluster_members) on each node. 3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_x86.mdx index a68b7baaadf..4fd2520c1a2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_x86.mdx @@ -11,31 +11,31 @@ Use the EnterpriseDB APT repository to install Failover Manager. ## Installing 1. Assume superuser privileges: - ```text + ```shell sudo su – ``` 2. Configure the EnterpriseDB repository by substituting your EnterpriseDB credentials for the username and password placeholders in the following commands: - ```text + ```shell sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' ``` 3. Add support to your system for secure APT repositories: - ```text + ```shell apt-get install apt-transport-https ``` 4. Add the EDB signing key: - ```text + ```shell wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - ``` 5. Update the repository meta data: - ```text + ```shell apt-get update ``` 6. Install Failover Manager: - ```text + ```shell apt-get -y install edb-efm42 ``` ## Initial configuration diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07a_efm4_ubuntu18_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07a_efm4_ubuntu18_x86.mdx index d2f7da5d98e..3adba940716 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07a_efm4_ubuntu18_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07a_efm4_ubuntu18_x86.mdx @@ -11,31 +11,31 @@ Use the EnterpriseDB APT repository to install Failover Manager. ## Installing 1. Assume superuser privileges: - ```text + ```shell sudo su – ``` 2. Configure the EnterpriseDB repository by substituting your EnterpriseDB credentials for the username and password placeholders in the following commands: - ```text + ```shell sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' ``` 3. Add support to your system for secure APT repositories: - ```text + ```shell apt-get install apt-transport-https ``` 4. Add the EDB signing key: - ```text + ```shell wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - ``` 5. Update the repository meta data: - ```text + ```shell apt-get update ``` 6. Install Failover Manager: - ```text + ```shell apt-get -y install edb-efm42 ``` ## Initial configuration diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07b_efm4_deb10_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07b_efm4_deb10_x86.mdx index db9b926d114..9da02cfb887 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07b_efm4_deb10_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07b_efm4_deb10_x86.mdx @@ -11,31 +11,31 @@ Use the EnterpriseDB APT repository to install Failover Manager. ## Installing 1. Assume superuser privileges: - ```text + ```shell sudo su – ``` 2. Configure the EnterpriseDB repository by substituting your EnterpriseDB credentials for the username and password placeholders in the following commands: - ```text + ```shell sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' ``` 3. Add support to your system for secure APT repositories: - ```text + ```shell apt-get install apt-transport-https ``` 4. Add the EDB signing key: - ```text + ```shell wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - ``` 5. Update the repository meta data: - ```text + ```shell apt-get update ``` 6. Install Failover Manager: - ```text + ```shell apt-get -y install edb-efm42 ``` ## Initial configuration diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86.mdx index 967c569dc3d..bd576e7f068 100644 --- a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_deb9_x86.mdx @@ -10,27 +10,27 @@ Use the EnterpriseDB APT repository to install Failover Manager. ### Installing 1. Assume superuser privileges: - ```text + ```shell sudo su – ``` 2. Configure the EnterpriseDB repository by substituting your EnterpriseDB credentials for the username and password placeholders in the following commands: - ```text + ```shell sh -c 'echo "deb https://@apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' ``` 3. Add support to your system for secure APT repositories: - ```text + ```shell apt-get install apt-transport-https ``` 4. Add the EDB signing key: - ```text + ```shell wget -q -O - https://:@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - ``` 5. Update the repository meta data: - ```text + ```shell apt-get update ``` 6. Install Failover Manager: - ```text + ```shell apt-get -y install edb-efm42 ``` ## Initial configuration diff --git a/product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx b/product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx index e0f4c217a0c..538badffb04 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx @@ -71,7 +71,7 @@ Use the properties in the `efm.properties` file to specify connection, administr | [user.email](#user_email) | | | | This value must be same for all the agents; can be left blank if using a notification script. | | [from.email](#from_email). | | | [efm@localhost](mailto:efm@localhost) | Leave blank to use the default [efm@localhost](mailto:efm@localhost). | | [notification.level](#notification_level) | Y | Y | INFO | See the [list of notifications](../10_notifications/#notifications). | -| [notification.text.prefix](#notification_text_prefix) | | | | | +| [notification.ini.prefix](#notification_text_prefix) | | | | | | [script.notification](#script_notification) | | | | Required if user.email property is not used; both parameters can be used together. | | [bind.address](#bind_address) | Y | Y | | Example: <ip_address>:<port> | | [external.address](#external_address) | | | | Example: <ip_address/hostname> | @@ -159,7 +159,7 @@ Use the properties in the `efm.properties` file to specify connection, administr Use the following properties to specify connection details for the Failover Manager cluster: -```text +```ini # The value for the password property should be the output from # 'efm encrypt' -- do not include a cleartext password here. To # prevent accidental sharing of passwords among clusters, the @@ -181,7 +181,7 @@ For information about encrypting the password for the database user, see [Encryp Use the `db.service.owner` property to specify the name of the operating system user that owns the cluster that is being managed by Failover Manager. This property isn't required on a dedicated witness node. -```text +```ini # This property tells EFM which OS user owns the $PGDATA dir for # the 'db.database'. By default, the owner is either 'postgres' # for PostgreSQL or 'enterprisedb' for EDB Postgres Advanced @@ -198,7 +198,7 @@ db.service.owner= Specify the name of the database service in the `db.service.name` property if you use the `service` or `systemctl` command when starting or stopping the service. -```text +```ini # Specify the proper service name in order to use service commands # rather than pg_ctl to start/stop/restart a database. For example, if # this property is set, then 'service restart' or 'systemctl @@ -213,7 +213,7 @@ db.service.name= Use the same service control mechanism (`pg_ctl`, `service`, or `systemctl`) each time you start or stop the database service. If you use the `pg_ctl` program to control the service, specify the location of the `pg_ctl` program in the `db.bin` property. -```text +```ini # Specify the directory containing the pg_controldata/pg_ctl commands, # for example: # /usr/edb/as12/bin. Unless the db.service.name property is used, the @@ -226,7 +226,7 @@ db.bin= Use the `db.data.dir` property to specify the location to write a recovery file on the primary node of the cluster during promotion. This property is required on primary and standby nodes. It isn't required on a dedicated witness node. -```text +```ini # For database version 12 and up, this is the directory where a # standby.signal file will exist for a standby node. For previous # versions, this is the location of the db recovery.conf file on @@ -247,7 +247,7 @@ db.data.dir= Use the `db.data.dir` property to specify the location to write a recovery file on the primary node of the cluster during promotion. This property is required on primary and standby nodes. It isn't required on a dedicated witness node. -```text +```ini # For database version 12 and up, this is the directory where a # standby.signal file will exist for a standby node. For previous # versions, this is the location of the db recovery.conf file on @@ -267,7 +267,7 @@ db.data.dir= Use the `db.config.dir` property to specify the location of database configuration files if they aren't stored in the same directory as the `recovery.conf` or `standby.signal` file. This is the value specified by the `config_file` parameter directory of your EDB Postgres Advanced Server or PostgreSQL installation. This value is used as the location of the EDB Postgres Advanced Server `data` directory when stopping, starting, or restarting the database. -```text +```ini # Specify the location of database configuration files if they are # not contained in the same location as the recovery.conf or # standby.signal file. This is most likely the case for Debian @@ -286,7 +286,7 @@ For more information about database configuration files, visit the [PostgreSQL w Use the `jdbc.sslmode` property to instruct Failover Manager to use SSL connections. By default, SSL is disabled. -```text +```ini # Use the jdbc.sslmode property to enable ssl for EFM # connections. Setting this property to anything but 'disable' # will force the agents to use 'ssl=true' for all JDBC database @@ -314,7 +314,7 @@ For information about configuring and using SSL, see [Secure TCP/IP Connections Use the `user.email` property to specify an email address (or multiple email addresses) to receive notifications sent by Failover Manager. -```text +```ini # Email address(es) for notifications. The value of this # property must be the same across all agents. Multiple email # addresses must be separated by space. If using a notification @@ -332,7 +332,7 @@ The `from.email` property specifies the value to use as the sender's address for For more information about notifications, see [Notifications](../10_notifications/#notifications). -```text +```ini # Use the from.email property to specify the from email address that # will be used for email notifications. Use the %h placeholder to # represent the name of the node host (e.g. example@%h). The @@ -346,7 +346,7 @@ from.email= Use the `notification.level` property to specify the minimum severity level at which Failover Manager sends user notifications or when a notification script is called. For a complete list of notifications, see [Notifications](../10_notifications/#notifications). -```text +```ini # Minimum severity level of notifications that will be sent by # the agent. The minimum level also applies to the notification # script (below). Valid values are INFO, WARNING, and SEVERE. @@ -357,25 +357,25 @@ notification.level=INFO
-Use the `notification.text.prefix` property to specify the text to add to the beginning of every notification. +Use the `notification.ini.prefix` property to specify the ini to add to the beginning of every notification. -```text +```ini # Text to add to the beginning of every notification. This could # be used to help identify what the cluster is used for, the role # of this node, etc. To use multiple lines, add a backslash \ to -# the end of a line of text. To include a newline use \n. +# the end of a line of ini. To include a newline use \n. # Example: -# notification.text.prefix=Development cluster for Example dept.\n\ +# notification.ini.prefix=Development cluster for Example dept.\n\ # Used by Dev and QA \ # See Example group for questions. -notification.text.prefix= +notification.ini.prefix= ``` Use the `script.notification` property to specify the path to a user-supplied script that acts as a notification service. The script is passed a message subject and a message body. The script is invoked each time Failover Manager generates a user notification. -```text +```ini # Absolute path to script run for user notifications. # # This is an optional user-supplied script that can be used for @@ -390,7 +390,7 @@ script.notification= The `bind.address` property specifies the IP address and port number of the agent on the current node of the Failover Manager cluster. -```text +```ini # This property specifies the ip address and port that jgroups # will bind to on this node. The value is of the form # :. @@ -406,7 +406,7 @@ bind.address= Use the `external.address` property to specify the IP address or hostname to use for communication with all other Failover Manager agents in a NAT environment. -```text +```ini # This is the ip address/hostname to be used for communication with all # other Failover Manager agents. All traffic towards this address # should be routed by the network to the bind.address of the node. @@ -420,7 +420,7 @@ external.address= Use the `admin.port` property to specify a port on which Failover Manager listens for administrative commands. -```text +```ini # This property controls the port binding of the administration # server which is used for some commands (ie cluster-status). The # default is 7809; you can modify this value if the port is @@ -432,7 +432,7 @@ admin.port=7809 Set the `is.witness` property to `true` to indicate that the current node is a witness node. If `is.witness` is `true`, the local agent doesn't check to see if a local database is running. -```text +```ini # Specifies whether or not this is a witness node. Witness nodes # do not have local databases running. is.witness= @@ -461,7 +461,7 @@ The following properties apply to the local server: For example, given the default values of these properties, a check of the local database happens once every 10 seconds. If an attempt to contact the local database doesn't come back positive within 60 seconds, Failover Manager makes a final attempt to contact the database. If a response isn't received within 10 seconds, Failover Manager declares database failure and notifies the administrator listed in the `user.email` property. These properties aren't required on a dedicated witness node. -```text +```ini # These properties apply to the connection(s) EFM uses to monitor # the local database. Every 'local.period' seconds, a database # check is made in a background thread. If the main monitoring @@ -483,7 +483,7 @@ If necessary, modify these values to suit your business model. Use the `remote.timeout` property to specify how many seconds an agent waits for a response from a remote database server (that is, how long a standby agent waits to verify that the primary database is down before performing failover). The `remote.timeout` property value specifies a timeout value for agent-to-agent communication. Other timeout properties in the cluster properties file specify values for agent-to-database communication. -```text +```ini # Timeout for a call to check if a remote database is responsive. # For example, this is how long a standby would wait for a # DB ping request from itself and the witness to the primary DB @@ -495,7 +495,7 @@ remote.timeout=10 Use the `node.timeout` property to specify the number of seconds for an agent to wait for a response from a node when determining if a node has failed. -```text +```ini # The total amount of time in seconds to wait before determining # that a node has failed or been disconnected from this node. # @@ -507,7 +507,7 @@ node.timeout=50 Use the `encrypt.agent.messages` property to specify whether to encrypt the messages sent between agents. -```text +```ini # Set to true to encrypt messages that are sent between agents. # This property must be the same on all agents or else the agents # will not be able to connect. @@ -518,7 +518,7 @@ encrypt.agent.messages=false Use the `enable.stop.cluster` property to enable or disable the `stop-cluster` command. The command is a convenience in some environments but can cause issues when unintentionally invoked. In Eager Failover mode, the command results in stopping EDB Postgres Advanced Server without failover. -```text +```ini # Whether or not the 'efm stop-cluster ' command is enabled. # Set to false to disable the command, in which case all Failover # Manager agents must be stopped individually. Note that stopping each @@ -532,7 +532,7 @@ enable.stop.cluster=true Use the `stop.isolated.primary` property to instruct Failover Manager to shut down the database if a primary agent detects that it's isolated. When `true` (the default), Failover Manager stops the database before invoking the script specified in the `script.primary.isolated` property. -```text +```ini # Shut down the database after a primary agent detects that it has # been isolated from the majority of the efm cluster. If set to # true, efm will stop the database before running the @@ -544,7 +544,7 @@ stop.isolated.primary=true Use the `stop.failed.primary` property to instruct Failover Manager to attempt to shut down a primary database if it can't reach the database. If `true`, Failover Manager runs the script specified in the `script.db.failure` property after attempting to shut down the database. -```text +```ini # Attempt to shut down a failed primary database after EFM can no # longer connect to it. This can be used for added safety in the # case a failover is caused by a failure of the network on the @@ -560,7 +560,7 @@ Use the `primary.shutdown.as.failure` property to treat any shutdown of the Fail - If the database is reached, a notification is sent informing you of the agent status. - If the database isn't reached, a failover occurs. -```text +```ini # Treat a primary agent shutdown as an agent failure. This can be set # to true to treat a primary agent shutdown as a failure situation. # Caution should be used when using this feature, as it could @@ -580,7 +580,7 @@ Use the `update.physical.slots.period` property to define the slot advance frequ Note: all slot names, including one set on the current primary if desired, must be unique. -```text +```ini # Period in seconds between having the primary agent update promotable # standbys with physical replication slot information so that # the cluster will continue to use replication slots after a failover. @@ -592,7 +592,7 @@ update.physical.slots.period=0 Use the `ping.server.ip` property to specify the IP address of a server that Failover Manager can use to confirm that network connectivity isn't a problem. -```text +```ini # This is the address of a well-known server that EFM can ping # in an effort to determine network reachability issues. It # might be the IP address of a nameserver within your corporate @@ -616,7 +616,7 @@ ping.server.ip=8.8.8.8 Use the `ping.server.command` property to specify the command used to test network connectivity. -```text +```ini # This command will be used to test the reachability of certain # nodes. # @@ -633,7 +633,7 @@ ping.server.command=/bin/ping -q -c3 -w5 Use the `auto.allow.hosts` property to instruct the server to use the addresses specified in the `.nodes` file of the first nostarts to update the allowed host list. Enabling this property by setting `auto.allow.hosts` to `true` can simplify cluster startup. -```text +```ini # Have the first nostarts automatically add the addresses # from its .nodes file to the allowed host list. This will make # it faster to start the cluster when the initial set of hosts @@ -645,7 +645,7 @@ auto.allow.hosts=false Use the `stable.nodes.file` property to instruct the server not to rewrite the nodes file when a node joins or leaves the cluster. This property is most useful in clusters with IP addresses that don't change. -```text +```ini # When set to true, EFM will not rewrite the .nodes file whenever # new nodes join or leave the cluster. This can help starting a # cluster in the cases where it is expected for member addresses @@ -658,7 +658,7 @@ stable.nodes.file=false The `db.reuse.connection.count` property allows the administrator to specify the number of times Failover Manager reuses the same database connection to check the database health. The default value is 0, indicating that Failover Manager creates a fresh connection each time. This property isn't required on a dedicated witness node. -```text +```ini # This property controls how many times a database connection is # reused before creating a new one. If set to zero, a new # connection will be created every time an agent pings its local @@ -670,7 +670,7 @@ db.reuse.connection.count=0 The `auto.failover` property enables automatic failover. By default, `auto.failover` is set to `true`. -```text +```ini # Whether or not failover will happen automatically when the primary # fails. Set to false if you want to receive the failover notifications # but not have EFM actually perform the failover steps. @@ -682,7 +682,7 @@ auto.failover=true Use the `auto.reconfigure` property to instruct Failover Manager to enable or disable automatic reconfiguration of remaining standby servers after the primary standby is promoted to primary. Set the property to `true` (the default) to enable automatic reconfiguration or `false` to disable automatic reconfiguration. This property isn't required on a dedicated witness node. If you're using EDB Postgres Advanced Server or PostgreSQL version 11 or earlier, the `recovery.conf` file is backed up during the reconfiguration process. -```text +```ini # After a standby is promoted, Failover Manager will attempt to # update the remaining standbys to use the new primary. For database # versions before 12, Failover Manager will back up recovery.conf. @@ -704,7 +704,7 @@ auto.reconfigure=true Use the `promotable` property to indicate not to promote a node. The `promotable` property is ignored when a primary agent starts. This simplifies switching back to the original primary after a switchover or failover. To override the setting, use the `efm set-priority` command at runtime. For more information about the `efm set-priority` command, see [Using the efm utility](../07_using_efm_utility/#using_efm_utility). -```text +```ini # A standby with this set to false will not be added to the # failover priority list, and so will not be available for # promotion. The property will be used whenever an agent starts @@ -719,7 +719,7 @@ promotable=true If the same amount of data was written to more than one standby node and a failover occurs, the `use.replay.tiebreaker` value determines how Failover Manager selects a replacement primary. Set the `use.replay.tiebreaker` property to `true` to instruct Failover Manager to failover to the node that will come out of recovery faster, as determined by the log sequence number. To ignore the log sequence number and promote a node based on user preference, set `use.replay.tiebreaker` to `false`. -```text +```ini # Use replay LSN value for tiebreaker when choosing a standby to # promote before using failover priority. Set this property to true to # consider replay location as more important than failover priority @@ -732,7 +732,7 @@ use.replay.tiebreaker=true Use the `standby.restart.delay` property to specify the time in seconds for the standby to wait before it gets reconfigured (stoppstarts) to follow the new primary after a promotion. -```text +```ini # Time in seconds for this standby to delay restarting to follow the # primary after a promotion. This can be used to have standbys restart # at different times to increase availability. Caution should be used @@ -747,7 +747,7 @@ standby.restart.delay=0 You can use the `application.name` property to provide the name of an application to copy to the `primary_conninfo` parameter before restarting an old primary node as a standby. -```text +```ini # During a switchover, recovery settings are copied from a standby # to the original primary. If the application.name property is set, # Failover Manager will replace the application_name portion of the @@ -767,7 +767,7 @@ Use the `restore.command` property to instruct Failover Manager to update the `r See the PostgreSQL documentation for more information about using a [restore_command](https://www.postgresql.org/docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-ARCHIVE-RECOVERY). -```text +```ini # If the restore_command on a standby restores directly from the # primary node, use this property to have Failover Manager change # the command when a new primary is promoted. @@ -788,7 +788,7 @@ restore.command= The database parameter `synchronous_standby_names` on the primary node specifies the names and count of the synchronous standby servers that confirm receipt of data to ensure that the primary nodes can accept write transactions. When the `reconfigure.num.sync` property is set to `true`, Failover Manager reduces the number of synchronous standby servers and reloads the configuration of the primary node to reflect the current value. -```text +```ini # Reduce num_sync when the number of synchronous standbys drops below # the value required by the primary database. If set to true, Failover # Manager will reduce the number of standbys needed in the primary's @@ -810,7 +810,7 @@ reconfigure.num.sync=false Use the `reconfigure.num.sync.max` property to specify the maximum number to which num-sync can be raised when a standby is added to the cluster. -```text +```ini # If reconfigure.num.sync is set to true and this property is set, # Failover Manager will check if num_sync can be raised when a standby # is added to the cluster. @@ -826,7 +826,7 @@ reconfigure.num.sync.max= Set the `reconfigure.sync.primary` property to `true` to take the primary database out of synchronous replication mode if the number of standby nodes drops below the level required. Set `reconfigure.sync.primary` to `false` to send a notification if the standby count drops without interrupting synchronous replication. -```text +```ini # Take the primary database out of synchronous replication mode when # needed. If set to true, Failover Manager will clear the # synchronous_standby_names configuration parameter on the primary @@ -851,7 +851,7 @@ reconfigure.sync.primary=false Use the `minimum.standbys` property to specify the minimum number of standby nodes to retain on a cluster. If the standby count drops to the specified minimum, a replica node isn't promoted if a failure of the primary node occurs. -```text +```ini # Instead of setting specific standbys as being unavailable for # promotion, this property can be used to set a minimum number # of standbys that will not be promoted. Set to one, for @@ -865,7 +865,7 @@ minimum.standbys=0 Use the `priority.standbys` property to specify the priority of standbys after this node is promoted. -```text +```ini # Space-separated list of standby addresses that are high priority for # promotion when this node is the primary. If set, when this node is # promoted, addresses in this list will be added to the front of the @@ -878,7 +878,7 @@ priority.standbys= Use the `recovery.check.period` property to specify the number of seconds for Failover Manager to wait before it checks to see if a database is out of recovery. -```text +```ini # Time in seconds between checks to see if a promoting database # is out of recovery. recovery.check.period=1 @@ -888,7 +888,7 @@ recovery.check.period=1 Use the `restart.connection.timeout` property to specify the number of seconds for Failover Manager to attempt to connect to a newly reconfigured primary or standby node while the database on that node prepares to accept connections. -```text +```ini # Time in seconds to keep trying to connect to a database after a # start or restart command returns successfully but the database # is not ready to accept connections yet (a rare occurance). This @@ -904,7 +904,7 @@ restart.connection.timeout=60 Use the `auto.resume.period` property to specify the number of seconds for an agent to attempt to resume monitoring that database. This property applies after a monitored database fails and an agent has assumed an idle state or when starting in IDLE mode. -```text +```ini # Period in seconds for IDLE agents to try to resume monitoring # after a database failure or when starting in IDLE mode. Set to # 0 for agents to not try to resume (in which case the @@ -923,7 +923,7 @@ The specified virtual IP address is assigned only to the primary node of the clu For information about using a virtual IP address, see [Using Failover Manager with virtual IP addresses](05_using_vip_addresses/#using_vip_addresses). -```text +```ini # These properties specify the IP and prefix length that will be # remapped during failover. If you do not use a VIP as part of # your failover solution, leave the virtual.ip property blank to @@ -958,7 +958,7 @@ virtual.ip.single=true Set the `check.vip.before.promotion` property to `false` to prevent Failover Manager from checking to see if a VIP is in use before assigning it to a new primary in case of a failure. This might result in multiple nodes broadcasting on the same VIP address. Unless the primary node is isolated or can be shut down via another process, set this property `to true`. -```text +```ini # Whether to check if the VIP (when used) is still in use before # promoting after a primary failure. Turning this off may allow # the new primary to have the VIP even though another node is also @@ -973,7 +973,7 @@ check.vip.before.promotion=true Use the `pgpool.enable` property to specify if you want to enable the Failover Manager and Pgpool integration for high availability. If you want to enable Pgpool integration in a non-sudo mode (running as the DB owner), the PCPPASS file must be owned by the DB owner operating system user and you must set the file permissions to 600. -```text +```ini # A boolean property to enable Failover Manager managed Pgpool HA. # If enabled, Failover Manager would natively update the joining # and leaving status of database nodes to active pgpool instance. @@ -987,7 +987,7 @@ pgpool.enable=false Use the following parameters to specify the values to use for Pgpool integration. -```text +```ini # Configurations required for pgpool integration. # 'pcp.user' - User that would be invoking PCP commands # 'pcp.host' - Virtual IP that would be used by pgpool. Same as @@ -1012,7 +1012,7 @@ You don't need to set the following properties if you are using Pgpool as the lo Provide a script named after the `script.load.balancer.attach` property to identify a script to invoke when you want to attach a node to the load balancer. Use the `script.load.balancer.detach` property to specify the name of a script to invoke when you want to detach node from the load balancer. Include the `%h` placeholder to represent the IP address of the node that's being attached or removed from the cluster. Include the `%t` placeholder to instruct Failover Manager to include a p (for a primary node) or an s (for a standby node) in the string. -```text +```ini # Absolute path to load balancer scripts # The attach script is called when a node should be attached to # the load balancer, for example after a promotion. The detach @@ -1033,7 +1033,7 @@ script.load.balancer.detach= Use the `detach.on.agent.failure` property to indicate that you don't want to detach a node from the load balancer in a scenario where the primary agent fails but the database is still reachable. The default value is `true.` -```text +```ini # If set to true, Failover Manager will detach the node from load # balancer if the primary agent fails but the database is still # reachable. In most scenarios this is NOT the desired situation. In @@ -1049,7 +1049,7 @@ detach.on.agent.failure= The `script.fence` property specifies the path to an optional user-supplied script to invoke during the promotion of a standby node to primary node. -```text +```ini # absolute path to fencing script run during promotion # # This is an optional user-supplied script that will be run @@ -1074,7 +1074,7 @@ script.fence= Use the `script.post.promotion` property to specify the path to an optional user-supplied script to invoke after a standby node is promoted to primary. -```text +```ini # Absolute path to fencing script run after promotion # # This is an optional user-supplied script that will be run after @@ -1097,7 +1097,7 @@ script.post.promotion= Use the `script.resumed` property to specify an optional path to a user-supplied script to invoke when an agent resumes monitoring a database. -```text +```ini # Absolute path to resume script # # This script is run before an IDLE agent resumes @@ -1109,7 +1109,7 @@ script.resumed= Use the `script.db.failure` property to specify the complete path to an optional user-supplied script that Failover Manager invokes if an agent detects that the database that it monitors has failed. -```text +```ini # Absolute path to script run after database failure # This is an optional user-supplied script that will be run after # an agent detects that its local database has failed. @@ -1120,7 +1120,7 @@ script.db.failure= Use the `script.primary.isolated` property to specify the complete path to an optional user-supplied script that Failover Manager invokes if the agent monitoring the primary database detects that the primary is isolated from the majority of the Failover Manager cluster. This script is called immediately after the VIP is released (if a VIP is in use). -```text +```ini # Absolute path to script run on isolated primary # This is an optional user-supplied script that will be run after # a primary agent detects that it has been isolated from the @@ -1134,7 +1134,7 @@ Use the `script.remote.pre.promotion` property to specify the path and name of a Include the %p placeholder to identify the address of the new primary node. -```text +```ini # Absolute path to script invoked on non-promoting agent nodes # before a promotion. # @@ -1158,7 +1158,7 @@ Use the `script.remote.post.promotion` property to specify the path and name of Include the %p placeholder to identify the address of the new primary node. -```text +```ini # Absolute path to script invoked on non-primary agent nodes # after a promotion. # @@ -1183,7 +1183,7 @@ Use `custom.monitor.timeout` to specify the maximum time for the script to run. Set `custom.monitor.safe.mode` to `true` to instruct Failover Manager to report nonzero exit codes from the script but not promote a standby as a result of an exit code. -```text +```ini # Absolute path to a custom monitoring script. # # Use script.custom.monitor to specify the location and name of @@ -1222,7 +1222,7 @@ Use the `sudo.command` property to specify a command for Failover Manager to inv Use the `sudo.user.command` property to specify a command for Failover Manager to invoke when executing commands performed by the database owner. -```text +```ini # Command to use in place of 'sudo' if desired when efm runs # the efm_db_functions or efm_root_functions, or efm_address # scripts. @@ -1244,7 +1244,7 @@ sudo.user.command=sudo -u %u Use the `lock.dir` property to specify an alternative location for the Failover Manager lock file. The file prevents Failover Manager from starting multiple, potentially orphaned, agents for a single cluster on the node. -```text +```ini # Specify the directory of lock file on the node. Failover # Manager creates a file named .lock at this location to # avoid starting multiple agents for same cluster. If the path @@ -1257,7 +1257,7 @@ lock.dir= Use the `log.dir` property to specify the location to write agent log files. Failover Manager attempts to create the directory if the directory doesn't exist. -```text +```ini # Specify the directory of agent logs on the node. If the path # does not exist, Failover Manager will attempt to create it. If # not specified defaults to '/var/log/efm-'. (To store @@ -1273,7 +1273,7 @@ log.dir= After enabling the UDP or TCP protocol on a Failover Manager host, you can enable logging to syslog. Use the `syslog.protocol` parameter to specify the protocol type (UDP or TCP) and the `syslog.port` parameter to specify the listener port of the syslog host. You can use the `syslog.facility` value as an identifier for the process that created the entry. Use a value between LOCAL0 and LOCAL7. -```text +```ini # Syslog information. The syslog service must be listening on # the port for the given protocol, which can be UDP or TCP. # The facilities supported are LOCAL0 through LOCAL7. @@ -1287,7 +1287,7 @@ syslog.facility=LOCAL1 Use the `file.log.enabled` and `syslog.enabled` properties to specify the type of logging that you want to implement. Set `file.log.enabled` to `true` to enable logging to a file. Enable the UDP protocol or TCP protocol and set `syslog.enabled` to `true` to enable logging to syslog. You can enable logging to both a file and syslog. -```text +```ini # Which logging is enabled. file.log.enabled=true syslog.enabled=false @@ -1299,7 +1299,7 @@ For more information about configuring syslog logging, see [Enabling syslog log Use the `jgroups.loglevel` and `efm.loglevel` parameters to specify the level of detail logged by Failover Manager. The default value is `INFO`. For more information about logging, see [Controlling logging](../09_controlling_logging/#controlling_logging). -```text +```ini # Logging levels for JGroups and EFM. # Valid values are: TRACE, DEBUG, INFO, WARN, ERROR # Default value: INFO @@ -1316,7 +1316,7 @@ efm.loglevel=INFO Use the `jvm.options` property to pass JVM-related configuration information. The default setting specifies the amount of memory that the Failover Manager agent can use. -```text +```ini # Extra information that will be passed to the JVM when starting # the agent. jvm.options=-Xmx128m diff --git a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx index a169c7894ac..42dd338364c 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx @@ -20,7 +20,7 @@ Where `` specifies the name of the Failover Manager cluster. If you include the `--from-env` option, you must export the value you want to encrypt before invoking the encryption utility. For example: -```text +```shell export EFMPASS=password ``` @@ -31,7 +31,7 @@ If you don't include the `--from-env` option, Failover Manager prompts you to en This example shows using the `encrypt` utility to encrypt a password for the `acctg` cluster: -```text +```ini # efm encrypt acctg This utility will generate an encrypted password for you to place in your Failover Manager cluster property file: @@ -57,7 +57,7 @@ If you receive this message when starting the Failover Manager service, see the If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, startup information is also available with the following command: -```text +```shell systemctl status edb-efm-4.4 ``` @@ -67,13 +67,13 @@ To prevent a cluster from inadvertently connecting to the database of another cl This example shows using the `--from-env` environment variable when encrypting a password. Before invoking the `efm encrypt` command, set the value of `EFMPASS` to the password `1safepassword`: -```text +``` # export EFMPASS=1safepassword ``` Then, invoke `efm encrypt`, specifying the `--from-env` option: -```text +``` # efm encrypt acctg --from-env # 7ceecd8965fa7a5c330eaa9e43696f83 ``` diff --git a/product_docs/docs/efm/4/04_configuring_efm/03_cluster_members.mdx b/product_docs/docs/efm/4/04_configuring_efm/03_cluster_members.mdx index fd660f54957..9948c81a5b2 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/03_cluster_members.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/03_cluster_members.mdx @@ -14,13 +14,13 @@ Each node in a Failover Manager cluster has a cluster members file (by default n After completing the Failover Manager installation, make a working copy of the template: -```text +```shell cp /etc/edb/efm-4.4/efm.nodes.in /etc/edb/efm-4.4/efm.nodes ``` After copying the template file, change the owner of the file to efm: -```text +```shell chown efm:efm efm.nodes ``` diff --git a/product_docs/docs/efm/4/04_configuring_efm/04_extending_efm_permissions.mdx b/product_docs/docs/efm/4/04_configuring_efm/04_extending_efm_permissions.mdx index 59028afda7f..b4b81c97bd3 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/04_extending_efm_permissions.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/04_extending_efm_permissions.mdx @@ -76,7 +76,7 @@ To run Failover Manager without sudo, you must select a database process owner w 1. Use the following command to add the user to the `efm` group: - ```text + ```shell usermod -a -G efm enterprisedb ``` @@ -86,7 +86,7 @@ To run Failover Manager without sudo, you must select a database process owner w 3. Copy the cluster properties template file and the nodes template file: - ```text + ```shell su - enterprisedb cp /etc/edb/efm-4.4/efm.properties.in .properties @@ -98,7 +98,7 @@ Then, modify the cluster properties file, providing the name of the user in the After modifying the configuration, the new user can control Failover Manager with the following command: -```text +```shell /usr/edb/efm-4.4/bin/runefm.sh start|stop .properties ``` diff --git a/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx b/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx index 11668b4c72f..58ec314cacf 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx @@ -60,7 +60,7 @@ When using a virtual IP (VIP) address with Failover Manager, it's important to t The following steps test the actions that Failover Manager takes. The example uses the following property values: -```text +```ini virtual.ip=172.24.38.239 virtual.ip.interface=eth0 virtual.ip.prefix=24 diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index a1a35f635df..108cbb41657 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -15,7 +15,7 @@ You can set up Eager Failover by performing the following steps. The example us ## Enabling Eager Failover - Since the database server stops as soon as the Failover Manager agent stops or fails, you must set the following property for all the agents before starting Failover Manager: - ```text + ```ini primary.shutdown.as.failure=true ``` @@ -23,7 +23,7 @@ You can set up Eager Failover by performing the following steps. The example us - With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid thihs scenario, you can disable the command using the `enable.stop.cluster` property. - ```text + ```ini enable.stop.cluster=false ``` @@ -31,7 +31,7 @@ You can set up Eager Failover by performing the following steps. The example us - As root, create `/etc/systemd/system/edb-as-12.service` file and include: - ```text + ```ini .include /lib/systemd/system/edb-as-12.service [Unit] BindsTo=edb-efm-4.2.service @@ -39,7 +39,7 @@ You can set up Eager Failover by performing the following steps. The example us - Run the following command to reload the configuration files: - ```text + ```shell systemctl daemon-reload ``` @@ -50,11 +50,11 @@ With these changes, when the Failover Manager agent is stopped or ended, the res ## Disabling Eager Failover - If you want to stop Failover Manager without stopping the database, comment out the following line in `/etc/systemd/system/edb-as-12.service`: - ```text + ```ini BindsTo=edb-efm-4.2.service ``` - Run the following command to reload the configuration files: - ```text + ```shell systemctl daemon-reload ``` diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index 70d4736c782..b16339f352c 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -83,7 +83,7 @@ If your Failover Manager cluster includes more than one standby server, you can For example, the following command instructs Failover Manager that the `acctg` cluster member that is monitoring `10.0.1.9` is the primary standby `(1)`: -```text +```shell efm set-priority acctg 10.0.1.9 1 ``` @@ -91,7 +91,7 @@ You can set the priority of a standby to `0` to make the standby nonpromotable. For example, if the properties file on node `10.0.1.10` includes a setting of `promotable=false` and you use `efm set-priority` to set the promotion priority of `10.0.1.10` to be the standby used in the event of a failover. The value designated by the `efm set-priority` command overrides the value in the property file: -```text +```shell efm set-priority acctg 10.0.1.10 1 ``` @@ -281,7 +281,7 @@ Environment=CLUSTER=acctg Also update the value of the `PIDfile` parameter to specify the new cluster name. For example: -```text +```ini PIDFile=/var/run/efm-4.4/acctg.pid ``` diff --git a/product_docs/docs/efm/4/09_controlling_logging.mdx b/product_docs/docs/efm/4/09_controlling_logging.mdx index 67fb44a8984..e485d578fec 100644 --- a/product_docs/docs/efm/4/09_controlling_logging.mdx +++ b/product_docs/docs/efm/4/09_controlling_logging.mdx @@ -14,7 +14,7 @@ Failover Manager writes and stores one log file per agent and one startup log pe You can control the level of detail written to the agent log by modifying the `jgroups.loglevel` and `efm.loglevel` parameters in the [cluster properties file](04_configuring_efm/01_cluster_properties/#loglevel): -```text +```ini # Logging levels for JGroups and EFM. # Valid values are: TRACE, DEBUG, INFO, WARN, ERROR # Default value: INFO @@ -39,7 +39,7 @@ For example, if you set the `efm.loglevel` parameter to `WARN`, Failover Manager By default, Failover Manager log files are rotated daily, compressed, and stored for a week. You can modify the file rotation schedule by changing settings in the log rotation file (`/etc/logrotate.d/efm-4.`). For more information about modifying the log rotation schedule, consult the logrotate man page: -``` +```shell $ man logrotate ``` @@ -51,7 +51,7 @@ Failover Manager supports syslog logging. To implement syslog logging, you must To allow a connection to syslog, edit the `/etc/rsyslog.conf` file and uncomment the protocol you want to use. Also make sure that the `UDPServerRun` or `TCPServerRun` entry associated with the protocol includes the port number to which log entries are sent. For example, the following configuration file entries enable UDP connections to port 514: -```text +```shell # Provides UDP syslog reception $ModLoad imudp $UDPServerRun 514 @@ -59,7 +59,7 @@ $UDPServerRun 514 The following configuration file entries enable TCP connections to port 514: -```text +```shell # Provides TCP syslog reception $ModLoad imtcp $InputTCPServerRun 514 @@ -71,7 +71,7 @@ After modifying the syslog configuration file, restart the `rsyslog` service to After modifying the `rsyslog.conf` file on the Failover Manager host, modify the Failover Manager properties to enable logging. Use your choice of editor to [modify the properties file](04_configuring_efm/01_cluster_properties/#logtype_enabled) `/etc/edb/efm-4./efm.properties.in`, specifying the type of logging that you want to implement: -```text +```ini # Which logging is enabled. file.log.enabled=true syslog.enabled=false @@ -79,7 +79,7 @@ syslog.enabled=false You must also [specify syslog details](04_configuring_efm/01_cluster_properties/#syslog_logging) for your system. Use the `syslog.protocol` parameter to specify the protocol type (UDP or TCP) and the `syslog.port` parameter to specify the listener port of the syslog host. You can use the `syslog.facility` value as an identifier for the process that created the entry. Use a value between `LOCAL0` and `LOCAL7`. -```text +```ini # Syslog information. The syslog service must be listening # on the port for the given protocol, which can be UDP or # TCP. The facilities supported are LOCAL0 through LOCAL7. diff --git a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx index 757ca1198bf..2569a252e69 100644 --- a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx +++ b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx @@ -16,7 +16,7 @@ Failover Manager provides a utility to assist you when upgrading a cluster manag 2. After installing Failover Manager, invoke the `efm upgrade-conf` utility to create the `.properties` and `.nodes` files for Failover Manager 4.4. The Failover Manager installer installs the upgrade utility ([efm upgrade-conf](07_using_efm_utility/#efm_upgrade_conf)) to the `/usr/edb/efm-4.4/bin directory`. To invoke the utility, assume root privileges, and invoke the command: -```text +```shell efm upgrade-conf ``` @@ -31,7 +31,7 @@ The efm `upgrade-conf` utility locates the `.properties` and `.nodes` files of p 5. Use a version-specific command to stop the old Failover Manager cluster. For example, you can use the following command to stop a version 4.1 cluster: -```text +```shell /usr/efm-4.1/bin/efm stop-cluster efm ``` @@ -69,25 +69,25 @@ After upgrading to Failover Manager 4.4, you can use your native package manager - On RHEL or CentOS 7.x: -```text +```shell yum remove edb-efm41 ``` - On RHEL or Rocky Linux or AlmaLinux 8.x: -```text +```shell dnf remove edb-efm41 ``` - On Debian or Ubuntu: -```text +```shell apt-get remove edb-efm41 ``` - On SLES: -```text +```shell zypper remove edb-efm41 ``` diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 530b2fd7451..62749d37f2e 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -41,7 +41,7 @@ If you're running with less than 128 megabytes allocated, increase the value and Failover Manager is tested with OpenJDK. We strongly recommend using OpenJDK. You can use the following command to check the type of your Java installation: -```text +```shell # java -version openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) diff --git a/product_docs/docs/efm/4/14_configuring_streaming_replication.mdx b/product_docs/docs/efm/4/14_configuring_streaming_replication.mdx index 092aa2aaf59..f7e722ea2ac 100644 --- a/product_docs/docs/efm/4/14_configuring_streaming_replication.mdx +++ b/product_docs/docs/efm/4/14_configuring_streaming_replication.mdx @@ -27,7 +27,7 @@ For detailed information about configuring cascading replication, see the [Postg To use Failover Manager in a cascading replication scenario, modify the cluster properties file, setting the following property values on standby node #2: -```text +```ini promotable=false auto.reconfigure=false ``` diff --git a/product_docs/docs/efm/4/15_configuring_ssl_authentication.mdx b/product_docs/docs/efm/4/15_configuring_ssl_authentication.mdx index bc7338a2aa3..d18022e4da7 100644 --- a/product_docs/docs/efm/4/15_configuring_ssl_authentication.mdx +++ b/product_docs/docs/efm/4/15_configuring_ssl_authentication.mdx @@ -18,7 +18,7 @@ To enable SSL on a Failover Manager cluster: 2. Modify the `postgresql.conf` file on each database in the Failover Manager cluster, enabling SSL: - ```text + ```ini ssl=on ``` @@ -26,7 +26,7 @@ To enable SSL on a Failover Manager cluster: 1. Modify the `pg_hba.conf` file on each node of the Failover Manager cluster, adding the following line to the beginning of the file: - ```text + ```shell hostnossl all all all reject ``` @@ -34,7 +34,7 @@ To enable SSL on a Failover Manager cluster: 1. After placing the `server.crt` and `server.key` files in the data directory, convert the certificate to a form that Java understands; you can use the command: - ```text + ```shell openssl x509 -in server.crt -out server.crt.der -outform der ``` @@ -42,7 +42,7 @@ To enable SSL on a Failover Manager cluster: 1. Add the certificate to the Java trusted certificates file: - ```text + ```shell keytool -keystore $JAVA_HOME/lib/security/cacerts -alias -import -file server.crt.der ``` @@ -54,7 +54,7 @@ To enable SSL on a Failover Manager cluster: You can use the `keytool` command to review a list of the available certificates or retrieve information about a specific certificate. For more information about using the `keytool` command, enter: - ```text + ```shell man keytool ``` diff --git a/product_docs/docs/efm/4/efm_deploy_arch/05_efm_pgbouncer.mdx b/product_docs/docs/efm/4/efm_deploy_arch/05_efm_pgbouncer.mdx index a316325c040..3bf196785da 100644 --- a/product_docs/docs/efm/4/efm_deploy_arch/05_efm_pgbouncer.mdx +++ b/product_docs/docs/efm/4/efm_deploy_arch/05_efm_pgbouncer.mdx @@ -113,7 +113,7 @@ to configure EDB PgBouncer. Perform the following steps in addition to those ins %include /etc/edb/pgbouncer1.15/edb-pgbouncer-databases.ini ``` 2. In the `edb-pgbouncer-1.15.ini` file, set the value of `listen_addr` to *: -``` text +```ini listen_addr = * ``` @@ -122,7 +122,7 @@ to configure EDB PgBouncer. Perform the following steps in addition to those ins The following is an example of the bash commands to create the file: -``` text +```shell echo "[databases]" > /etc/edb/pgbouncer1.15/edb-pgbouncer-databases.ini echo "edb= host=srv1" >> /etc/edb/pgbouncer1.15/edb-pgbouncer-databases.ini @@ -166,7 +166,7 @@ The user efm user must be able to ssh as the user running PgBouncer; for example 2. Make sure that passwordless `ssh` is enabled. You can check with the following command: - ``` text + ```shell grep ^PasswordAuthentication /etc/ssh/sshd_config ``` @@ -177,16 +177,16 @@ The user efm user must be able to ssh as the user running PgBouncer; for example On every Failover Manager/postgres host, as the efm user: 1. Run the following command: - ``` text + ```shell ssh-keygen -P "" -f ~/.ssh/id_rsa ``` 2. For every EDB PgBouncer host, copy the `ssh` key with the following command: - ``` text + ```shell ssh-copy-id enterprisedb@ ``` The default home directory for the `enterprisedb` user is `/var/lib/edb`. If this directory is not already present, create it manually. As a sudo user, run the following commands on each EDB PgBouncer host: - ``` text + ```shell mkdir -p /var/lib/edb chown -R enterprisedb:enterprisedb /var/lib/edb ``` @@ -195,7 +195,7 @@ On every Failover Manager/postgres host, as the efm user: You can reset the temporary password for the enterprisedb user on every EDB PgBouncer host by running the following command as root: -``` text +```shell passwd -d enterprisedb ``` ### Configuring the network load balancer diff --git a/product_docs/docs/efm/4/efm_deploy_arch/06_efm_pgpool.mdx b/product_docs/docs/efm/4/efm_deploy_arch/06_efm_pgpool.mdx index 9833de46427..99b206ea4ad 100644 --- a/product_docs/docs/efm/4/efm_deploy_arch/06_efm_pgpool.mdx +++ b/product_docs/docs/efm/4/efm_deploy_arch/06_efm_pgpool.mdx @@ -65,7 +65,7 @@ when returned to the Failover Manager cluster. To configure Failover Manager for high availability using EDB Pgpool-II, you must set the following properties in the cluster properties file: -``` text +```ini pgpool.enable = true pcp.user = User invoking PCP commands @@ -78,6 +78,7 @@ properties in the cluster properties file: pgpool.bin = Absolute path of pgpool bin directory ``` + ### Configuring EDB Pgpool-II You can configure some important parameters in the @@ -90,7 +91,7 @@ nodes. Configure using backend_* configuration parameters in `pgpool.conf`, and use the equal backend weights for all nodes. This makes the read queries distributed equally among all nodes. -``` text +```ini backend_hostname0 = 'server1_IP' @@ -115,7 +116,6 @@ makes the read queries distributed equally among all nodes. backend_weight2 = 1 backend_flag2 = 'ALLOW_TO_FAILOVER' - ``` #### Enabling load balancing and streaming replication mode @@ -124,7 +124,7 @@ Set the following configuration parameter in the `pgpool.conf` file to enable lo - For EDB Pgpool-II version 4.2: - ``` text + ```ini backend_clustering_mode = 'streaming_replication' load_balance_mode = on @@ -132,20 +132,21 @@ Set the following configuration parameter in the `pgpool.conf` file to enable lo - For EDB Pgpool-II versions prior to 4.2: - ``` text + ```ini master_slave_mode = on master_slave_sub_mode = 'stream' load_balance_mode = on ``` + #### Disabling health checking and failover Health checking and failover are handled by Failover Manager, so disable them on the EDB Pgpool-II side. To disable the health check and failover on EDB Pgpool-II side, assign the following values: -``` text +```ini health_check_period = 0 @@ -156,7 +157,6 @@ values: failover_command = '' failback_command = '' - ``` Ensure the following while setting up the values in the pgpool.conf diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx index a338ce6b9f6..2d939c0aac4 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx @@ -21,7 +21,9 @@ For platform-specific install instructions, including accessing the repo, see: - [CentOS 7](x86/epas_centos7_x86) - [SLES 15](x86/epas_sles15_x86) - [SLES 12](x86/epas_sles12_x86) - - [Ubuntu 18.04 or 20.04/Debian 10](x86/epas_ubuntu18_20_deb10_x86) + - [Ubuntu 20.04](x86/epas_ubuntu20_x86) + - [Ubuntu 18.04](x86/epas_ubuntu18_x86) + - [Debian 10](x86/epas_deb10_x86) - [Debian 9](x86/epas_deb9_x86) - Linux on IBM Power (ppc64le): - [RHEL 8](ppc64le/epas_rhel8_ppcle) diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86.mdx new file mode 100644 index 00000000000..ea3e609f28e --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86.mdx @@ -0,0 +1,83 @@ +--- +title: "Installing EDB Postgres Advanced Server on Debian 10 x86" +navTitle: "Debian 10" +redirects: +- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-debian-or-ubuntu +--- + +To install EDB Postgres Advanced Server on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: + + + +The following steps walk you through using the EDB apt repository to install a debian package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. + +- Assume superuser privileges: + + ```text + sudo su – + ``` + +- Configure the EDB repository and replace the `username` and `password` placeholders in the following command: + + a. Set up the EDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +- Add support to your system for secure APT repositories: + + ```text + apt-get -y install apt-transport-https + ``` + +- Add the EDB signing key: + + ```text + wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + ``` + +- Update the repository metadata: + + ```text + apt-get update + ``` + +- Install the package: + + ```text + apt-get -y install edb-as14-server + ``` + +!!! Note + Some EDB Postgres Advanced Server supporting components require a Java installation. Before using a native package to add Migration Toolkit or EDB\*Plus to your system, make sure that Java version 8 is installed on your EDB Postgres Advanced Server host. + +## Initial configuration +This section steps you through connecting to your cluster, and creating the user password. See [Managing an EDB Postgres Advanced Server installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. + +```shell +# To work in your cluster, login as `enterprisedb` user: +su - enterprisedb +# Connect to the database server using psql command line client: +psql edb +# Assign a password to the database superuser `enterprisedb`: +ALTER ROLE enterprisedb IDENTIFIED BY password; +# Creating a database (named hr): +CREATE DATABASE hr; +# Connect to the new database and create a table (named dept): +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, +dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); +# Add data to the table: +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table. +SELECT * FROM dept; +``` \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_20_deb10_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_x86.mdx similarity index 97% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_20_deb10_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_x86.mdx index 0ab1b6456c5..b578b1a4ac0 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_20_deb10_x86.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_x86.mdx @@ -1,6 +1,6 @@ --- -title: "Installing EDB Postgres Advanced Server on Ubuntu 18.04 or 20.04/Debian 10 x86" -navTitle: "Ubuntu 18.04 or 20.04/Debian 10" +title: "Installing EDB Postgres Advanced Server on Ubuntu 18.04 x86" +navTitle: "Ubuntu 18.04" redirects: - /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-debian-or-ubuntu --- diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86.mdx new file mode 100644 index 00000000000..f021d87ed4a --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86.mdx @@ -0,0 +1,83 @@ +--- +title: "Installing EDB Postgres Advanced Server on Ubuntu 20.04 x86" +navTitle: "Ubuntu 20.04" +redirects: +- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-debian-or-ubuntu +--- + +To install EDB Postgres Advanced Server on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: + + + +The following steps walk you through using the EDB apt repository to install a debian package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. + +- Assume superuser privileges: + + ```text + sudo su – + ``` + +- Configure the EDB repository and replace the `username` and `password` placeholders in the following command: + + a. Set up the EDB repository: + + ```text + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EDB credentials for the `username` and `password` placeholders in the following command: + + ```text + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +- Add support to your system for secure APT repositories: + + ```text + apt-get -y install apt-transport-https + ``` + +- Add the EDB signing key: + + ```text + wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - + ``` + +- Update the repository metadata: + + ```text + apt-get update + ``` + +- Install the package: + + ```text + apt-get -y install edb-as14-server + ``` + +!!! Note + Some EDB Postgres Advanced Server supporting components require a Java installation. Before using a native package to add Migration Toolkit or EDB\*Plus to your system, make sure that Java version 8 is installed on your EDB Postgres Advanced Server host. + +## Initial configuration +This section steps you through connecting to your cluster, and creating the user password. See [Managing an EDB Postgres Advanced Server installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. + +```shell +# To work in your cluster, login as `enterprisedb` user: +su - enterprisedb +# Connect to the database server using psql command line client: +psql edb +# Assign a password to the database superuser `enterprisedb`: +ALTER ROLE enterprisedb IDENTIFIED BY password; +# Creating a database (named hr): +CREATE DATABASE hr; +# Connect to the new database and create a table (named dept): +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, +dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); +# Add data to the table: +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table. +SELECT * FROM dept; +``` \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx index 74c3ca2bcb0..89cf297ef04 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx @@ -11,7 +11,9 @@ navigation: - epas_centos7_x86 - epas_sles15_x86 - epas_sles12_x86 -- epas_ubuntu18_20_deb10_x86 +- epas_ubuntu20_x86 +- epas_ubuntu18_x86 +- epas_deb10_x86 - epas_deb9_x86 --- @@ -25,5 +27,7 @@ For x86_64 (amd64) OS-specific install instructions, including accessing the rep - [CentOS 7](epas_centos7_x86) - [SLES 15](epas_sles15_x86) - [SLES 12](epas_sles12_x86) -- [Ubuntu 20.04 or 18.04/Debian 10](epas_ubuntu18_20_deb10_x86) +- [Ubuntu 20.04](epas_ubuntu20_x86) +- [Ubuntu 18.04](epas_ubuntu18_x86) +- [Debian 10](epas_deb10_x86) - [Debian 9](epas_deb9_x86) diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_4_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_4_0_rel_notes.mdx index 78171c5578f..9315fb9687a 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/epas14_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_4_0_rel_notes.mdx @@ -8,6 +8,6 @@ EDB Postgres Advanced Server 14.4.0 includes the following bug fixes: | -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | --------------------- | | Upstream merge | Merged with community PostgreSQL 14.4. See the community [Release Notes](https://www.postgresql.org/docs/release/14.4/) for details. | | | | Bug fix | Fix server crash while executing the function which returns TABLE and requires casting on attributes. [Support Ticket: #81924] | DB-1778 | | -| Bug fix | Fix \dn command query. | DB-1777 | psql | +| Bug fix | Fix \dn command query. [Support Ticket: #83263] | DB-1777 | psql | diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/17_hadoop_sles15_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/17_hadoop_sles15_ppcle.mdx index c07a57937ca..d5c75fed281 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/17_hadoop_sles15_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/17_hadoop_sles15_ppcle.mdx @@ -1,50 +1,45 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15 " +navTitle: SLES 15 +title: Installing Hadoop Foreign Data Wrapper on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell 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/19_hadoop_sles12_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/19_hadoop_sles12_ppcle.mdx index d883b312b2d..7128e66e10c 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/19_hadoop_sles12_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/19_hadoop_sles12_ppcle.mdx @@ -1,53 +1,46 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12 " +navTitle: SLES 12 +title: Installing Hadoop Foreign Data Wrapper on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le # Refresh the metadata zypper refresh - -# Install OpenJDK (version 11) -zypper -n install java-11-openjdk ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-hdfs_fdw -``` \ No newline at end of file +``` + +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/05_hadoop_sles15_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/05_hadoop_sles15_x86.mdx index e96f248ba84..680ec578c86 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/05_hadoop_sles15_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/05_hadoop_sles15_x86.mdx @@ -1,49 +1,45 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Hadoop Foreign Data Wrapper on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-hdfs_fdw -``` \ No newline at end of file +``` + +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/07_hadoop_sles12_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/07_hadoop_sles12_x86.mdx index b2333e27268..c3636dc9df8 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/07_hadoop_sles12_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/07_hadoop_sles12_x86.mdx @@ -1,42 +1,35 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing Hadoop Foreign Data Wrapper on SLES 12 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/x86_64 SUSEConnect -p sle-sdk/12.5/x86_64 @@ -44,9 +37,10 @@ SUSEConnect -p sle-sdk/12.5/x86_64 zypper refresh ``` -## Installing the package +## Install the package ```shell 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/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx index c39d53eafbb..b618f11ce3d 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx @@ -1,49 +1,51 @@ --- -title: "Installing EDB JDBC Connector on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB JDBC Connector on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-jdbc -``` \ No newline at end of file +``` + +## Initial configuration + +To make the JDBC driver available to Java, you must either copy the appropriate java `.jar` file for the JDBC version that you are using to your `$java_home/jre/lib/ext` directory or append the location of the `.jar` file to the `CLASSPATH` environment variable. + +Note that if you choose to append the location of the `jar` file to the `CLASSPATH` environment variable, you must include the complete pathname: + +`/usr/edb/jdbc/edb-jdbc18.jar` diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx index b2f8ec0488f..4924d6e60a6 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx @@ -1,53 +1,52 @@ --- -title: "Installing EDB JDBC Connector on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB JDBC Connector on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le # Refresh the metadata zypper refresh - -# Install OpenJDK (version 1.8) -zypper -n install java-1_8_0-openjdk ``` -## Installing the package +## Install the package ```shell zypper -n install edb-jdbc -``` \ No newline at end of file +``` + +## Initial configuration + +To make the JDBC driver available to Java, you must either copy the appropriate java `.jar` file for the JDBC version that you are using to your `$java_home/jre/lib/ext` directory or append the location of the `.jar` file to the `CLASSPATH` environment variable. + +Note that if you choose to append the location of the `jar` file to the `CLASSPATH` environment variable, you must include the complete pathname: + +`/usr/edb/jdbc/edb-jdbc18.jar` diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx index 0ed4265da50..56489c1f25d 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx @@ -1,49 +1,51 @@ --- -title: "Installing EDB JDBC Connector on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB JDBC Connector on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-jdbc -``` \ No newline at end of file +``` + +## Initial configuration + +To make the JDBC driver available to Java, you must either copy the appropriate java `.jar` file for the JDBC version that you are using to your `$java_home/jre/lib/ext` directory or append the location of the `.jar` file to the `CLASSPATH` environment variable. + +Note that if you choose to append the location of the `jar` file to the `CLASSPATH` environment variable, you must include the complete pathname: + +`/usr/edb/jdbc/edb-jdbc18.jar` diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx index c6fde3929a0..a43d822aaf5 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx @@ -1,56 +1,52 @@ --- -title: "Installing EDB JDBC Connector on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB JDBC Connector on SLES 12 x86_64 --- -To install the connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit the EnterpriseDB website at: +Before you begin the installation process, log in as superuser. - +```shell +# To log in as a superuser: +sudo su - +``` -You can use the zypper package manager to install a connector on an SLES 12 host. zypper will attempt to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. +## Set up the repository -1. You must assume superuser privileges and stop any firewalls before installing connector. Then, use the following commands to add EnterpriseDB repositories to your system: +Setting 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). - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -2. The commands create the repository configuration files in the `/etc/zypp/repos.d` directory. Then, use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - ```text - zypper refresh - ``` +# 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' - When prompted, provide credentials for the repository, and specify a to always trust the provided key, and update the metadata to include the EnterpriseDB repository. +# Activate the required SUSE module -3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information. Use the commands: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ```text - zypper install SUSEConnect - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - SUSEConnect -p PackageHub/12.4/x86_64 - SUSEConnect -p sle-sdk/12.4/x86_64 - ``` +# Refresh the metadata +zypper refresh +``` -4. Install the following repository for resolving the dependencies: +## Install the package - ```text - zypper addrepo https://download.opensuse.org/repositories/Apache:/Modules/SLE_12_SP4/Apache:Modules.repo - ``` +```shell +zypper -n install edb-jdbc +``` -5. Refresh the metadata on your SLES host: - ```text - zypper refresh - ``` +## Initial configuration -6. Install OpenJDK (version 1.8): +To make the JDBC driver available to Java, you must either copy the appropriate java `.jar` file for the JDBC version that you are using to your `$java_home/jre/lib/ext` directory or append the location of the `.jar` file to the `CLASSPATH` environment variable. - ```text - zypper -n install java-1_8_0-openjdk - ``` +Note that if you choose to append the location of the `jar` file to the `CLASSPATH` environment variable, you must include the complete pathname: -7. Now you can use the zypper utility to install the connector: - - ```text - zypper install edb-jdbc - ``` +`/usr/edb/jdbc/edb-jdbc18.jar` diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx index 996a2a08215..32a7f019ad1 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx @@ -1,52 +1,49 @@ --- -title: "Installing Migration Toolkit on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Migration Toolkit on SLES 15 ppc64le --- - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-migrationtoolkit ``` +## 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. + +After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx index 28db7141963..ef6957e1180 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx @@ -1,56 +1,50 @@ --- -title: "Installing Migration Toolkit on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing Migration Toolkit on SLES 12 ppc64le --- - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le # Refresh the metadata zypper refresh - -# Install OpenJDK (version 1.8) -zypper -n install java-1_8_0-openjdk ``` -## Installing the package +## Install the package ```shell zypper -n install edb-migrationtoolkit ``` +## 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. + +After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx index 705ca7532b9..f17804e8365 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx @@ -1,52 +1,49 @@ --- -title: "Installing Migration Toolkit on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Migration Toolkit on SLES 15 x86_64 --- - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) -- [Installing source-specific drivers](../../05_installing_mtk/#installing-source-specific-drivers) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-migrationtoolkit ``` +## 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. + +After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx index 431eb100c3f..d98a8d81c67 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx @@ -1,64 +1,50 @@ --- -title: "Installing Migration Toolkit on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing Migration Toolkit on SLES 12 x86_64 --- +Before you begin the installation process, log in as superuser. - +```shell +# To log in as a superuser: +sudo su - +``` -You can use the zypper package manager to install a Migration toolkit on an SLES 12 host. `zypper` attempts to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB. +## Set up the repository -1. You must assume superuser privileges and stop any firewalls before installing Migration Toolkit. Then, use the following commands to add EnterpriseDB repositories to your system: +Setting 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). - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/ - edb-sles.repo - ``` +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -2. The command creates the repository configuration files in the /etc/zypp/repos.d directory. Use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository: +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - ```text - zypper refresh - ``` +# 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' - When prompted, provide credentials for the repository; specify `a` to always trust the provided key and update the metadata to include the EnterpriseDB repository. +# Activate the required SUSE module -3. You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' +# Refresh the metadata +zypper refresh +``` - SUSEConnect -p PackageHub/12.5/x86_64 +## Install the package - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` +```shell +zypper -n install edb-migrationtoolkit +``` -4. Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories: +## Initial configuration - ```text - zypper addrepo https://download.opensuse.org/repositories/ - Apache:/Modules/SLE_12_SP4/Apache:Modules.repo - ``` - -5. Use the following command to refresh the metadata: - - ```text - zypper refresh - ``` - -6. Install OpenJDK (version 1.8) for Java based components: - - ```text - zypper -n install java-1_8_0-openjdk - ``` - -7. Now you can use the zypper utility to install a Migration Toolkit: - - ```text - zypper -n install edb-migrationtoolkit - ``` - - For detailed information about registering a SUSE host, visit: - - +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. +After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/17_mongo_sles15_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/17_mongo_sles15_ppcle.mdx index 670dc7f07a0..aeaa031e39e 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/17_mongo_sles15_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/17_mongo_sles15_ppcle.mdx @@ -1,50 +1,45 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15 " +navTitle: SLES 15 +title: Installing MongoDB Foreign Data Wrapper on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell 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/19_mongo_sles12_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/19_mongo_sles12_ppcle.mdx index bbc087dba6c..bd6bb5b830b 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/19_mongo_sles12_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/19_mongo_sles12_ppcle.mdx @@ -1,40 +1,35 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12 " +navTitle: SLES 12 +title: Installing MongoDB Foreign Data Wrapper on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -42,8 +37,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell 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/05_mongo_sles15_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/05_mongo_sles15_x86.mdx index cb7b5201e1c..43b2f1218c8 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/05_mongo_sles15_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/05_mongo_sles15_x86.mdx @@ -1,48 +1,45 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing MongoDB Foreign Data Wrapper on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh - ``` -## Installing the package +## Install the package ```shell 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/07_mongo_sles12_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/07_mongo_sles12_x86.mdx index 53b20aaea2f..b72a529c2dc 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/07_mongo_sles12_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/07_mongo_sles12_x86.mdx @@ -1,41 +1,35 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing MongoDB Foreign Data Wrapper on SLES 12 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/x86_64 SUSEConnect -p sle-sdk/12.5/x86_64 @@ -43,8 +37,10 @@ SUSEConnect -p sle-sdk/12.5/x86_64 zypper refresh ``` -## Installing the package +## Install the package ```shell 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/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/17_mysql_sles15_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/17_mysql_sles15_ppcle.mdx index e01a37e5504..38a2edc4f85 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/17_mysql_sles15_ppcle.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/17_mysql_sles15_ppcle.mdx @@ -1,38 +1,33 @@ --- -title: "Installing MySQL Foreign Data Wrapper on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing MySQL Foreign Data Wrapper on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 these steps. ```shell -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module @@ -46,8 +41,10 @@ rpm --import /etc/RPM-GPG-KEY-mysql-2022 zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as13-mysql8_fdw +zypper -n install edb-as14-mysql8_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/19_mysql_sles12_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/19_mysql_sles12_ppcle.mdx index fe6a7edd762..884086083dc 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/19_mysql_sles12_ppcle.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/19_mysql_sles12_ppcle.mdx @@ -1,38 +1,33 @@ --- -title: "Installing MySQL Foreign Data Wrapper on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing MySQL Foreign Data Wrapper on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 these steps. ```shell -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE modules @@ -43,9 +38,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-mysql8_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/x86_amd64/05_mysql_sles15_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/05_mysql_sles15_x86.mdx index 14cc2d5f893..0339a33796a 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/05_mysql_sles15_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/05_mysql_sles15_x86.mdx @@ -1,38 +1,33 @@ --- -title: "Installing MySQL Foreign Data Wrapper on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing MySQL Foreign Data Wrapper on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 these steps. ```shell -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module @@ -46,8 +41,10 @@ rpm --import /etc/RPM-GPG-KEY-mysql-2022 zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as13-mysql8_fdw -``` \ No newline at end of file +zypper -n install edb-as14-mysql8_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/x86_amd64/07_mysql_sles12_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/07_mysql_sles12_x86.mdx index 984df982089..9730740fefd 100644 --- a/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/07_mysql_sles12_x86.mdx +++ b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/07_mysql_sles12_x86.mdx @@ -1,37 +1,32 @@ --- -title: "Installing MySQL Foreign Data Wrapper on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing MySQL Foreign Data Wrapper on SLES 12 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform 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 these steps. ```shell -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration # information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' @@ -51,9 +46,10 @@ SUSEConnect -p sle-sdk/12.5/x86_64 zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-mysql8_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/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/09_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/09_ocl_connector14_sles15_ppcle.mdx index 434879e0ed1..e45d1ec97b2 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/09_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/09_ocl_connector14_sles15_ppcle.mdx @@ -1,49 +1,42 @@ --- -title: "Installing EDB OCL Connector on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB OCL Connector on SLES 15 ppc64le --- - -There are two steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modul +# Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell 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/10_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/10_ocl_connector14_sles12_ppcle.mdx index f4deca8c87b..4c1587bd1f9 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/10_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/10_ocl_connector14_sles12_ppcle.mdx @@ -1,41 +1,35 @@ --- -title: "Installing EDB OCL Connector on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB OCL Connector on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -43,9 +37,8 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell 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/03_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/03_ocl_connector14_sles15_x86.mdx index 62b97246070..61d55fdd5aa 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/03_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/03_ocl_connector14_sles15_x86.mdx @@ -1,51 +1,43 @@ --- -title: "Installing EDB OCL Connector on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB OCL Connector on SLES 15 x86_64 --- - -There are three steps to completing an installation: - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modul +# Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell 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/04_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/04_ocl_connector14_sles12_x86.mdx index f1324cde262..ec06186ab86 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/04_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/04_ocl_connector14_sles12_x86.mdx @@ -1,29 +1,44 @@ --- -title: "Installing EDB OCL Connector on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB OCL Connector on SLES 12 x86_64 --- +Before you begin the installation process, log in as superuser. -You can use the zypper package manager to install the connector on an SLES 12 host. zypper will attempt to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EDB. Before installing the connector, use the following commands to add EDB repository configuration files to your SLES host: +```shell +# To log in as a superuser: +sudo su - +``` - `zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo` +## Set up the repository -After creating the repository configuration files, use the `zypper refresh` command to refresh the metadata on your SLES host to include the EDB repositories. +Setting 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). -When prompted for a `User Name` and `Password`, provide your connection credentials for the EDB repository. To request credentials for the repository, visit [the EDB website](https://www.enterprisedb.com/repository-access-request). +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -Before installing EDB Postgres Advanced Server or supporting components, you must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - `zypper install SUSEConnect` - `SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'` - `SUSEConnect -p PackageHub/12.4/x86_64` - `SUSEConnect -p sle-sdk/12.4/x86_64` +# 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' -For detailed information about registering a SUSE host, visit the [SUSE website](https://www.suse.com/support/kb/doc/?id=7016626). +# Activate the required SUSE module -Then, you can use the zypper utility to install the connector: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - `zypper install edb-oci` +# Refresh the metadata +zypper refresh +``` - `zypper install edb-oci-devel` +## Install the package +```shell +zypper -n install edb-oci +``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/11_odbc13_sles15_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/11_odbc13_sles15_ppcle.mdx index f74794de902..e8b357773b7 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/11_odbc13_sles15_ppcle.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/11_odbc13_sles15_ppcle.mdx @@ -1,47 +1,42 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +navTitle: SLES 15 +title: Installing EDB ODBC Connector on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the Repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the Package +## Install the package ```shell zypper -n install edb-odbc diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle.mdx index 9a1bccbf013..c22f141e3e6 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle.mdx @@ -1,42 +1,35 @@ --- -title: "Installing EDB ODBC Connector on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB ODBC Connector on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -44,7 +37,7 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-odbc diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/05_odbc13_sles15_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/05_odbc13_sles15_x86.mdx index 89084f3290b..565dd04a503 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/05_odbc13_sles15_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/05_odbc13_sles15_x86.mdx @@ -1,49 +1,43 @@ --- -title: "Installing EDB ODBC Connector on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB ODBC Connector on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-odbc -``` \ No newline at end of file +``` diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/06_odbc13_sles12_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/06_odbc13_sles12_x86.mdx index 76431e1afbf..21ac34aa29e 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/06_odbc13_sles12_x86.mdx +++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/06_odbc13_sles12_x86.mdx @@ -1,27 +1,44 @@ --- -title: "Installing EDB ODBC Connector on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB ODBC Connector on SLES 12 x86_64 --- -You can use the zypper package manager to install the connector on an SLES 12 host. zypper will attempt to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EDB. Before installing the connector, use the following commands to add EDB repository configuration files to your SLES host: +Before you begin the installation process, log in as superuser. - `zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo` +```shell +# To log in as a superuser: +sudo su - +``` -After creating the repository configuration files, use the `zypper refresh` command to refresh the metadata on your SLES host to include the EDB repositories. +## Set up the repository -When prompted for a `User Name` and `Password`, provide your connection credentials for the EDB repository. To request credentials for the repository, visit [the EDB website](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. 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 installing EDB Postgres Advanced Server or supporting components, you must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands: +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - `zypper install SUSEConnect` - `SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'` - `SUSEConnect -p PackageHub/12.4/x86_64` - `SUSEConnect -p sle-sdk/12.4/x86_64` +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect -For detailed information about registering a SUSE host, visit the [SUSE website](https://www.suse.com/support/kb/doc/?id=7016626). +# 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' -Then, you can use the zypper utility to install the connector: +# Activate the required SUSE module -`zypper install edb-odbc` +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 -`zypper install edb-odbc-devel` \ No newline at end of file +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-odbc +``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/index.mdx index 923dc7229f3..8394614fc45 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/index.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/index.mdx @@ -9,7 +9,9 @@ navigation: - pem_agent_centos7_x86 - pem_agent_sles15_x86 - pem_agent_sles12_x86 -- pem_agent_ubuntu18_20_deb10_x86 +- pem_agent_ubuntu20_x86 +- pem_agent_ubuntu18_x86 +- pem_agent_deb10_x86 - pem_agent_deb9_x86 --- @@ -21,5 +23,7 @@ For Linux x86-64 (amd64) see: - [CentOS 7](pem_agent_centos7_x86) - [SLES 15](pem_agent_sles15_x86) - [SLES 12](pem_agent_sles12_x86) - - [Ubuntu 20.04 or 18.04/Debian 10](pem_agent_ubuntu18_20_deb10_x86) + - [Ubuntu 20.04](pem_agent_ubuntu20_x86) + - [Ubuntu 18.04](pem_agent_ubuntu18_x86) + - [Debian 10](pem_agent_deb10_x86) - [Debian 9](pem_agent_deb9_x86) diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_20_deb10_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb10_x86.mdx similarity index 93% rename from product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_20_deb10_x86.mdx rename to product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb10_x86.mdx index d9dd67ffea0..c770da1993d 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_20_deb10_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb10_x86.mdx @@ -1,6 +1,6 @@ --- -title: "Installing the PEM agent on Ubuntu 20.04 or 18.04/Debian 10 x86" -navTitle: "Ubuntu 20.04 or 18.04/Debian 10" +title: "Installing the PEM agent on Debian 10 x86" +navTitle: "Debian 10" --- @@ -16,7 +16,6 @@ The following steps will walk you through using the EDB apt repository to instal 2. Configure the EDB repository: - a. Set up the EnterpriseDB repository: ```shell diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb9_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb9_x86.mdx index 125e1767821..b2b33dc43a9 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb9_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_deb9_x86.mdx @@ -15,12 +15,11 @@ The following steps will walk you through using the EDB apt repository to instal 2. Configure the EDB repository: - ```shell sh -c 'echo "deb https://username:password@apt.enterprisedb.com $(lsb_release - cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' ``` -Where `username:password` is to be replaced by the credentials provided by EDB. + Where `username:password` is to be replaced by the credentials provided by EDB. 3. Add support to your system for secure APT repositories: diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_x86.mdx new file mode 100644 index 00000000000..1eb8d933cfe --- /dev/null +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu18_x86.mdx @@ -0,0 +1,56 @@ +--- +title: "Installing the PEM agent on Ubuntu 18.04 x86" +navTitle: "Ubuntu 18.04" +--- + + +To install PEM on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, [contact EDB](https://www.enterprisedb.com/repository-access-request) . + +The following steps will walk you through using the EDB apt repository to install a Debian package. When using the commands, replace the username and password with the credentials provided by EDB. + +1. Log in as root: + + ```shell + sudo su - + ``` + +2. Configure the EDB repository: + + a. Set up the EnterpriseDB repository: + + ```shell + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```shell + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +3. Add support to your system for secure APT repositories: + + ```shell + apt-get install apt-transport-https + ``` + +4. Add the EBD signing key: + + ```shell + wget -q -O -https://username:password@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add – + ``` + +5. Update the repository metadata: + + ```shell + apt-get update + ``` + +6. Use the following command to install the Debian package for the PEM Agent: + + ```shell + apt-get install edb-pem-agent + ``` + +After installing PEM Agent using `apt-get`, you need to register the PEM Agent. For more detailed information see [Registering an agent](../../../registering_agent). + diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu20_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu20_x86.mdx new file mode 100644 index 00000000000..97b841b47fe --- /dev/null +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86/pem_agent_ubuntu20_x86.mdx @@ -0,0 +1,56 @@ +--- +title: "Installing the PEM agent on Ubuntu 20.04 x86" +navTitle: "Ubuntu 20.04" +--- + + +To install PEM on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, [contact EDB](https://www.enterprisedb.com/repository-access-request) . + +The following steps will walk you through using the EDB apt repository to install a Debian package. When using the commands, replace the username and password with the credentials provided by EDB. + +1. Log in as root: + + ```shell + sudo su - + ``` + +2. Configure the EDB repository: + + a. Set up the EnterpriseDB repository: + + ```shell + sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' + ``` + + b. Substitute your EnterpriseDB credentials for the `username` and `password` placeholders in the following command: + + ```shell + sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' + ``` + +3. Add support to your system for secure APT repositories: + + ```shell + apt-get install apt-transport-https + ``` + +4. Add the EBD signing key: + + ```shell + wget -q -O -https://username:password@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add – + ``` + +5. Update the repository metadata: + + ```shell + apt-get update + ``` + +6. Use the following command to install the Debian package for the PEM Agent: + + ```shell + apt-get install edb-pem-agent + ``` + +After installing PEM Agent using `apt-get`, you need to register the PEM Agent. For more detailed information see [Registering an agent](../../../registering_agent). + diff --git a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/index.mdx b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/index.mdx index 187cd8dc8ad..fadefa02226 100644 --- a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/index.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/index.mdx @@ -9,7 +9,9 @@ navigation: - pem_server_centos7_x86 - pem_server_sles15_x86 - pem_server_sles12_x86 -- pem_server_ubuntu18_20_deb10_x86 +- pem_server_ubuntu20_x86 +- pem_server_ubuntu18_x86 +- pem_server_deb10_x86 - pem_server_deb9_x86 --- @@ -21,5 +23,7 @@ For Linux x86-64 (amd64), see: - [CentOS 7](pem_server_centos7_x86) - [SLES 15](pem_server_sles15_x86) - [SLES 12](pem_server_sles12_x86) - - [Ubuntu 20.04 or 18.04/Debian 10](pem_server_ubuntu18_20_deb10_x86) + - [Ubuntu 20.04](pem_server_ubuntu20_x86) + - [Ubuntu 18.04](pem_server_ubuntu18_x86) + - [Debian 10](pem_server_deb10_x86) - [Debian 9](pem_server_deb9_x86) diff --git a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_20_deb10_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86.mdx similarity index 97% rename from product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_20_deb10_x86.mdx rename to product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86.mdx index 3c8f99dae07..b79b502efed 100644 --- a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_20_deb10_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86.mdx @@ -1,6 +1,6 @@ --- -title: "Installing the PEM server on Ubuntu 20.04 or 18.04/Debian 10 x86" -navTitle: "Ubuntu 20.04 or 18.04/Debian 10" +title: "Installing the PEM server on Debian 10 x86" +navTitle: "Debian 10" --- The following steps will walk you through using the EDB `apt` repository to install a Debian package. diff --git a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_x86.mdx new file mode 100644 index 00000000000..eaea0597f93 --- /dev/null +++ b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu18_x86.mdx @@ -0,0 +1,102 @@ +--- +title: "Installing the PEM server on Ubuntu 18.04 x86" +navTitle: "Ubuntu 18.04" +--- + +The following steps will walk you through using the EDB `apt` repository to install a Debian package. + +!!! Note + You can also visit and select the platform and product to view the steps for installation. + +1. Log in as root on your Debian or Ubuntu host: + + ```shell + sudo su - + ``` + +## Prerequisites + +- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. + + 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). + + 2. Configure authentication on the Postgres server by updating the pg_hba.conf file. The pg_hba.conf file manages connections. You must ensure that the pg_hba.conf file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. + + - If you are using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + + - If you are using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + + 3. Ensure that the `sslutils` extension and `hstore` contrib module are installed on your Postgres server. + + - If you are using EDB Postgres Advanced Server, the `sslutils` extension and `hstore` contrib module are installed by default. + + - If you are PostgreSQL, ensure you have access to the PostgreSQL community repository, and then install the `sslutils` extension and the `hstore` contrib module: + + ```shell + apt install postgresql-_sslutils postgresql-contrib + ``` + + Where, `x` is the Postgres server version. + + !!! Note + Debian 10 and Ubuntu 20 has increased the requirements to accept the certificates due to security reason. + + - If a user wants to install the PEM agent on any of the machines, they must upgrade ssltuils to 1.3 where 4096 bit RSA key and sha256 signature algorithm support has added. + - If a user does not upgrade sslutils to 1.3, then PEM agent may fail to connect to the PEM backend database server, and it might log the error ca md too weak. + + 4. If you are using a firewall, allow access to port `8443` on the Postgres server: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +- Ensure the components Postgres Enterprise Manager depends on such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl are up to date, using the following command: + + ```shell + apt-get update + ``` + +## Configure the EDB repository + +a. Set up the EnterpriseDB repository: + +```shell +sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs)main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' +``` + +b. Substitute your EnterpriseDB credentials for the `` and `` placeholders in the following command: + +```shell +sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' +``` + +To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). + +## Add support to your system for secure APT repositories + +```shell +apt-get install apt-transport-https +``` + +## Add the EBD signing key + +```shell +wget -q -O -https://username:password@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add – +``` + +## Update the repository metadata + +```shell +apt-get update +``` + +## Install the PEM server + +```shell +apt-get install edb-pem +``` + +!!! Note + The operating system user `pem` gets 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 gets saved to this user's home directory. + +When the installation completes, you must configure the PEM Server. For detailed information see [Configuring the PEM Server on Linux Platforms](../../configuring_the_pem_server_on_linux/). diff --git a/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86.mdx new file mode 100644 index 00000000000..b1daf1e7761 --- /dev/null +++ b/product_docs/docs/pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86.mdx @@ -0,0 +1,102 @@ +--- +title: "Installing the PEM server on Ubuntu 20.04 x86" +navTitle: "Ubuntu 20.04" +--- + +The following steps will walk you through using the EDB `apt` repository to install a Debian package. + +!!! Note + You can also visit and select the platform and product to view the steps for installation. + +1. Log in as root on your Debian or Ubuntu host: + + ```shell + sudo su - + ``` + +## Prerequisites + +- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. + + 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). + + 2. Configure authentication on the Postgres server by updating the pg_hba.conf file. The pg_hba.conf file manages connections. You must ensure that the pg_hba.conf file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. + + - If you are using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + + - If you are using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + + 3. Ensure that the `sslutils` extension and `hstore` contrib module are installed on your Postgres server. + + - If you are using EDB Postgres Advanced Server, the `sslutils` extension and `hstore` contrib module are installed by default. + + - If you are PostgreSQL, ensure you have access to the PostgreSQL community repository, and then install the `sslutils` extension and the `hstore` contrib module: + + ```shell + apt install postgresql-_sslutils postgresql-contrib + ``` + + Where, `x` is the Postgres server version. + + !!! Note + Debian 10 and Ubuntu 20 has increased the requirements to accept the certificates due to security reason. + + - If a user wants to install the PEM agent on any of the machines, they must upgrade ssltuils to 1.3 where 4096 bit RSA key and sha256 signature algorithm support has added. + - If a user does not upgrade sslutils to 1.3, then PEM agent may fail to connect to the PEM backend database server, and it might log the error ca md too weak. + + 4. If you are using a firewall, allow access to port `8443` on the Postgres server: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +- Ensure the components Postgres Enterprise Manager depends on such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl are up to date, using the following command: + + ```shell + apt-get update + ``` + +## Configure the EDB repository + +a. Set up the EnterpriseDB repository: + +```shell +sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs)main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' +``` + +b. Substitute your EnterpriseDB credentials for the `` and `` placeholders in the following command: + +```shell +sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' +``` + +To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). + +## Add support to your system for secure APT repositories + +```shell +apt-get install apt-transport-https +``` + +## Add the EBD signing key + +```shell +wget -q -O -https://username:password@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add – +``` + +## Update the repository metadata + +```shell +apt-get update +``` + +## Install the PEM server + +```shell +apt-get install edb-pem +``` + +!!! Note + The operating system user `pem` gets 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 gets saved to this user's home directory. + +When the installation completes, you must configure the PEM Server. For detailed information see [Configuring the PEM Server on Linux Platforms](../../configuring_the_pem_server_on_linux/). diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/11_pgbouncer_sles15_ppcle.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/11_pgbouncer_sles15_ppcle.mdx index 69cd509980a..822db12d627 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/11_pgbouncer_sles15_ppcle.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/11_pgbouncer_sles15_ppcle.mdx @@ -1,55 +1,45 @@ --- -title: "Installing EDB PgBouncer on SLES 15 ppc64le" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB pgBouncer on SLES 15 ppc64le --- -!!! note - Supported on EDB PgBouncer 1.16 and later. - -There are two steps to completing an installation: - -- Setting up the Repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-pgbouncer ``` -Where <xx> is the EDB PgBouncer version you have installed. - +Where `` is the version of EDB PgBouncer you are installing. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/12_pgbouncer_sles12_ppcle.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/12_pgbouncer_sles12_ppcle.mdx index 3a456d46634..02e93a49a08 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/12_pgbouncer_sles12_ppcle.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/ibm_power_ppc64le/12_pgbouncer_sles12_ppcle.mdx @@ -1,44 +1,35 @@ --- -title: "Installing EDB PgBouncer on SLES 12 ppc64le" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB pgBouncer on SLES 12 ppc64le --- -!!! note - Supported on EDB PgBouncer 1.16 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -46,10 +37,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-pgbouncer ``` -Where <xx> is the EDB PgBouncer version you have installed. \ No newline at end of file +Where `` is the version of EDB PgBouncer you are installing. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/05_pgbouncer_sles15_x86.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/05_pgbouncer_sles15_x86.mdx index 4a1a42d704e..a69b87c627f 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/05_pgbouncer_sles15_x86.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/05_pgbouncer_sles15_x86.mdx @@ -1,55 +1,45 @@ --- -title: "Installing EDB PgBouncer on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB pgBouncer on SLES 15 x86_64 --- -!!! note - Supported on EDB PgBouncer 1.16 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-pgbouncer +zypper -n install edb-pgbouncer ``` -Where <xx> is the EDB PgBouncer version you have installed. \ No newline at end of file +Where `` is the version of EDB PgBouncer you are installing. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/06_pgbouncer_sles12_x86.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/06_pgbouncer_sles12_x86.mdx index 6e8dd32ff4a..55bfe2c15b4 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/06_pgbouncer_sles12_x86.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/install_on_linux/x86_amd64/06_pgbouncer_sles12_x86.mdx @@ -1,44 +1,46 @@ --- -title: "Installing EDB PgBouncer on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB pgBouncer on SLES 12 x86_64 --- -Perform the following steps to install EDB PgBouncer on an SLES 12 SP5 host using the zypper package manager. +Before you begin the installation process, log in as superuser. -1. Assume superuser privileges and use the following command to add the EnterpriseDB repository configuration file to your SLES host: +```shell +# To log in as a superuser: +sudo su - +``` - ``` text - zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` +## Set up the repository - This command creates a repository configuration file named `edb.repo` in the `/etc/zypp/repos.d` directory. +Setting 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). -3. Install `SUSEConnect` to register the host with SUSE to allow access to SUSE repositories: +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` text - zypper install SUSEConnect - ``` +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect -4. Register the host with SUSE to allow access to SUSE repositories and replace `'REGISTRATION_CODE'` and `'EMAIL'` with your SUSE registration information: +# 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' - ``` text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - SUSEConnect -p PackageHub/12.5/x86_64 - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` +# Activate the required SUSE module -5. Refresh the metadata: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ``` text - zypper refresh - ``` +# Refresh the metadata +zypper refresh +``` -6. Use the zypper utility to install EDB PgBouncer. +## Install the package - ``` text - zypper -n install edb-pgbouncer - ``` +```shell +zypper -n install edb-pgbouncer +``` - Where <xx> is the EDB PgBouncer version you have installed. - -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. diff --git a/product_docs/docs/pgd/4/upgrades/index.mdx b/product_docs/docs/pgd/4/upgrades/index.mdx index c3ca8c5c9a1..70c2accecf3 100644 --- a/product_docs/docs/pgd/4/upgrades/index.mdx +++ b/product_docs/docs/pgd/4/upgrades/index.mdx @@ -5,7 +5,7 @@ title: "Upgrading" Because EDB Postgres Distributed consists in multiple software components, the upgrade strategy depends partially on which components are being upgraded. -In general it's possible to upgrade the cluster with almost zero upgrade, by +In general it's possible to upgrade the cluster with almost zero downtime, by using an approach called Rolling Upgrade where nodes are upgraded one by one, and the application connections are switched over to already upgraded nodes. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/11_pgpool_sles15_ppcle.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/11_pgpool_sles15_ppcle.mdx index a5f02e60131..9f16a3b00be 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/11_pgpool_sles15_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/11_pgpool_sles15_ppcle.mdx @@ -1,55 +1,45 @@ --- -title: "Installing EDB Pgpool-II on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB Pgpool-II on SLES 15 ppc64le --- -!!! note - Supported on EDB Pgpool-II 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n 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. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/12_pgpool_sles12_ppcle.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/12_pgpool_sles12_ppcle.mdx index 815912cc51b..06cfa5a9cf9 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/12_pgpool_sles12_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/12_pgpool_sles12_ppcle.mdx @@ -1,45 +1,35 @@ --- -title: "Installing EDB PgPool-II on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB Pgpool-II on SLES 12 ppc64le --- -!!! note - Supported on EDB Pgpool-II 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -47,9 +37,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n 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. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/05_pgpool_sles15_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/05_pgpool_sles15_x86.mdx index f0d06f1b83c..588399b5cc2 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/05_pgpool_sles15_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/05_pgpool_sles15_x86.mdx @@ -1,53 +1,45 @@ --- -title: "Installing EDB Pgpool-II on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB Pgpool-II on SLES 15 x86_64 --- -!!! note - Supported on EDB Pgpool-II 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-pgpool ``` -where <xx> is the EDB Pgpool-II version you want to install. \ No newline at end of file + +Where `` is the version of EDB PgPool-II you are installing. diff --git a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/06_pgpool_sles12_x86.mdx b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/06_pgpool_sles12_x86.mdx index 52516dd8628..e77a82f678c 100644 --- a/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/06_pgpool_sles12_x86.mdx +++ b/product_docs/docs/pgpool/4.3/01_installing_and_configuring_the_pgpool-II/x86_amd64/06_pgpool_sles12_x86.mdx @@ -1,49 +1,46 @@ --- -title: "Installing EDB Pgpool-II on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB Pgpool-II on SLES 12 x86_64 --- -You can use the Zypper package manager to install EDB Pgpool-II on an SLES 12 host. Zypper will attempt to satisfy package dependencies but requires access to specific repositories that EDB does not host. +Before you begin the installation process, log in as superuser. -1. Assume superuser privileges. +```shell +# To log in as a superuser: +sudo su - +``` - ```text - sudo su - - ``` +## Set up the repository -2. Invoke the following command to add the EDB repository to your SLES host: +Setting 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). - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -4. Install `SUSEConnect` to register the host with SUSE to allow access to SUSE repositories: +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - ```text - 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' -5. Register the host with SUSE to allow access to SUSE repositories and replace `'REGISTRATION_CODE'` and `'EMAIL'` with your SUSE registration information: +# Activate the required SUSE module - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - SUSEConnect -p PackageHub/12.5/x86_64 - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 +# Refresh the metadata +zypper refresh +``` -6. Refresh the metadata: +## Install the package - ```text - zypper refresh - ``` - - -7. Use the Zypper utility to install EDB Pgpool-II: - - ```text - zypper install -n edb-pgpool - ``` - - where <xx> is the EDB Pgpool II version you wish to install. +```shell +zypper -n install edb-pgpool +``` +Where `` is the version of EDB PgPool-II you are installing. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/11_pgpoolext_sles15_ppcle.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/11_pgpoolext_sles15_ppcle.mdx index be071c18f6d..c71db52c2d1 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/11_pgpoolext_sles15_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/11_pgpoolext_sles15_ppcle.mdx @@ -1,54 +1,45 @@ --- -title: "Installing Pgpool extensions on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB Pgpool-II Extensions on SLES 15 ppc64le --- -!!! note - Supported on EDB Pgpool-II 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as-pgpool-extensions +zypper -n install edb-as--pgpool-extensions ``` -Where <xx> is the EDB Postgres Advanced Server version and <yy> is the EDB Pgpool-II version you wish to install. +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/12_pgpoolext_sles12_ppcle.mdx b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/12_pgpoolext_sles12_ppcle.mdx index 80d67f3af78..bb83a985878 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/12_pgpoolext_sles12_ppcle.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/ibm_power_ppc64le/12_pgpoolext_sles12_ppcle.mdx @@ -1,45 +1,35 @@ --- -title: "Installing Pgpool extensions on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB Pgpool-II Extensions on SLES 12 ppc64le --- -!!! note - Supported on EDB Pgpool-II Extension 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository +## 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 these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -47,10 +37,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as-pgpool-extensions +zypper -n install edb-as--pgpool-extensions ``` -Where <xx> is the EDB Postgres Advanced Server version and <yy> is the EDB Pgpool-II version you wish to install. +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/05_pgpoolext_sles15_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/05_pgpoolext_sles15_x86.mdx index 4410ec13a0d..9f0963f4108 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/05_pgpoolext_sles15_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/05_pgpoolext_sles15_x86.mdx @@ -1,55 +1,45 @@ --- -title: "Installing Pgpool extensions on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing EDB Pgpool-II Extensions on SLES 15 x86_64 --- -!!! note - Supported on EDB Pgpool-II 4.3 and later. - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell -zypper -n install edb-as-pgpool-extensions +zypper -n install edb-as--pgpool-extensions ``` -Where <xx> is the EDB Postgres Advanced Server version and <yy> is the EDB Pgpool-II version you wish to install. - +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. diff --git a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/06_pgpoolext_sles12_x86.mdx b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/06_pgpoolext_sles12_x86.mdx index a7f56b415c9..5652a1f8a75 100644 --- a/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/06_pgpoolext_sles12_x86.mdx +++ b/product_docs/docs/pgpool/4.3/02_extensions/x86_amd64/06_pgpoolext_sles12_x86.mdx @@ -1,40 +1,46 @@ --- -title: "Installing Pgpool extensions on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing EDB Pgpool-II Extensions on SLES 12 x86_64 --- -You can use the Zypper package manager to install the EDB Pgpool-II extension on an SLES 12 host. Zypper will attempt to satisfy package dependencies as it installs a package but requires access to specific repositories that are not hosted at EDB. - -1. Assume superuser privileges. - ```text - sudo su - - ``` - -2. Use the following command to add the EDB repository to your SLES host: - ```text - zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ``` - -4. Install `SUSEConnect` to register the host with SUSE to allow access to SUSE repositories: - ```text - zypper install SUSEConnect - ``` - -5. Register the host with SUSE to allow access to SUSE repositories and replace `'REGISTRATION_CODE'` and `'EMAIL'` with your SUSE registration information: - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - SUSEConnect -p PackageHub/12.5/x86_64 - SUSEConnect -p sle-sdk/12.5/x86_64 - ``` - -6. Refresh the metadata: - ```text - zypper refresh - ``` - -7. Use the Zypper utility to install EDB Pgpool-II extension: - ```text - zypper -n install edb-as-pgpool-extensions - ``` - - Where <xx> is the EDB Postgres Advanced Server version and <yy> is the EDB Pgpool-II version you wish to install. +Before you begin the installation process, log in as superuser. + +```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). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +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. diff --git a/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/11_postgis_sles15_ppcle.mdx b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/11_postgis_sles15_ppcle.mdx index ca7d4837f98..df25e41cc59 100644 --- a/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/11_postgis_sles15_ppcle.mdx +++ b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/11_postgis_sles15_ppcle.mdx @@ -1,52 +1,45 @@ --- -title: "Installing PostGIS on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing PostGIS on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules -SUSEConnect -p sle-module-desktop-applications/15.3/ppc64le -SUSEConnect -d -p sle-module-development-tools/15.3/ppc64le +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-postgis3 ``` +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/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/12_postgis_sles12_ppcle.mdx b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/12_postgis_sles12_ppcle.mdx index 4e766a24365..35d9b22119b 100644 --- a/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/12_postgis_sles12_ppcle.mdx +++ b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/12_postgis_sles12_ppcle.mdx @@ -1,42 +1,35 @@ --- -title: "Installing PostGIS on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing PostGIS on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le @@ -44,9 +37,10 @@ SUSEConnect -p sle-sdk/12.5/ppc64le zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-postgis3 ``` +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/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/05_postgis_sles15_x86.mdx b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/05_postgis_sles15_x86.mdx index c277240b9fd..e793e2bd968 100644 --- a/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/05_postgis_sles15_x86.mdx +++ b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/05_postgis_sles15_x86.mdx @@ -1,51 +1,45 @@ --- -title: "Installing PostGIS on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing PostGIS on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. +Before you begin the installation process, log in as superuser. ```shell # To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +## Set up the repository -## Setting up the repository - -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting 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 -# Install the repository configuration and enter your EDB repository +# 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 +# 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 +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules -SUSEConnect -p sle-module-desktop-applications/15.3/x86_64 -SUSEConnect -p sle-module-development-tools/15.3/x86_64 +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata zypper refresh ``` -## Installing the package +## Install the package ```shell zypper -n install edb-as14-postgis3 ``` +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/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/06_postgis_sles12_x86.mdx b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/06_postgis_sles12_x86.mdx index 6d912eab237..b28414dacd6 100644 --- a/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/06_postgis_sles12_x86.mdx +++ b/product_docs/docs/postgis/3.1/01a_installing_postgis/installing_on_linux/x86_amd64/06_postgis_sles12_x86.mdx @@ -1,52 +1,46 @@ --- -title: "Installing PostGIS on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing PostGIS on SLES 12 x86_64 --- -Perform the following steps to install PostGIS on an SLES Host using the Zypper package manager: +Before you begin the installation process, log in as superuser. -Zypper will attempt to satisfy package dependencies as it installs a package but requires access to specific repositories not hosted at EDB. +```shell +# To log in as a superuser: +sudo su - +``` -1. Assume superuser privileges. +## Set up the repository - ```text - sudo su - - ``` +Setting 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). -2. Use the following command to add the EDB repository to your SLES host: +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ```text - 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 -3. Invoke the following command to refresh the metadata: +# 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' - ```text - zypper refresh - ``` +# Activate the required SUSE module -4. Install `SUSEConnect` to register the host with SUSE to allow access to SUSE repositories: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ```text - zypper install SUSEConnect - ``` +# Refresh the metadata +zypper refresh +``` -5. Register the host with SUSE to allow access to SUSE repositories and replace `'REGISTRATION_CODE'` and `'EMAIL'` with your SUSE registration information: +## Install the package - ```text - SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - SUSEConnect -p PackageHub/12.4/x86_64 - SUSEConnect -p sle-sdk/12.4/x86_64 - ``` - -7. Refresh the metadata: +```shell +zypper -n install edb-as14-postgis3 +``` - ```text - zypper refresh - ``` - -9. Use the zypper utility to install PostGIS: - - ```text - zypper -n install edb-as14f-postgis - ``` +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/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index ad78e201f66..f865f1b7f23 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -3,11 +3,14 @@ title: "EDB Postgres for Kubernetes" navigation: - rel_notes - cloudnativepg +- "#Getting Started" - installation_upgrade - quickstart - interactive_demo +- "#Configuration" - operator_conf - logging +- "#Enhanced" - cnp-plugin - openshift - evaluation