From 48230cb4dc5adea9f66a280d69cf7199d91be2fd Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 13 Feb 2024 11:45:50 -0500 Subject: [PATCH 01/50] draft of using webhooks --- .../monitoring_performance/notifications.mdx | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index f8c131552fc..cd28bd0ac77 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -135,6 +135,31 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: - Set **All alerts** to **Yes** to enable all alert levels to send notifications. - To send a notification when a specific alert level is reached, set the slider next to an alert level to **Yes**. You must set **All alerts** to **No** to configure an individual alert level. +### Using a webhook + +Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. + +Here are the steps to configure a Slack `Incoming Webhook` using PEM: + +- Configure the Slack application, if it's not already configured. +- Activate `Incoming Webhooks` from Slack. +- Add new webhooks to the Slack workspace. You must add the channel and authorize the application for the incoming webhooks so the pemAgent can notify the alert using Slack. +- Get the unique URL used in PEM to configure the webhook configurations. You can configure PEM to send notifications (low, medium, high) to Slack via a POST request. +- The pemAgent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. + +Here is an example of a POST request from the pemAgent: + +```shell +POST https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXX/ +Content-type: application/json +{ + "text": "Alert from PEM: [%AlertID%], [%AlertName%]" +} +``` + +!!! Note + To configure Slack, see + ### Deleting a webhook To mark a webhook for deletion, in the Webhooks table, select the webhook name and select **Delete** to the left of the name. The alert remains in the list but in strike-through font. From 74abdd48e3000da7018d223c052a066118bc1885 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 19 Feb 2024 09:14:39 -0500 Subject: [PATCH 02/50] Update product_docs/docs/pem/9/monitoring_performance/notifications.mdx Added reference to Slack documentation Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index cd28bd0ac77..83827a17ef4 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -137,7 +137,7 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: ### Using a webhook -Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. +Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks`](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. Here are the steps to configure a Slack `Incoming Webhook` using PEM: From 14458dde264c04aea2c59deecfddcf181c25b7b1 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 19 Feb 2024 09:17:36 -0500 Subject: [PATCH 03/50] Removed stub to reference information because a link was inserted earlier --- .../docs/pem/9/monitoring_performance/notifications.mdx | 3 --- 1 file changed, 3 deletions(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 83827a17ef4..4af68e04d0d 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -157,9 +157,6 @@ Content-type: application/json } ``` -!!! Note - To configure Slack, see - ### Deleting a webhook To mark a webhook for deletion, in the Webhooks table, select the webhook name and select **Delete** to the left of the name. The alert remains in the list but in strike-through font. From b488b4b592f8168b3a2a67581d1776fa45c28a52 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 20 Feb 2024 08:16:01 -0500 Subject: [PATCH 04/50] corrected typo Co-authored-by: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 4af68e04d0d..797d3bb53b1 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -137,7 +137,7 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: ### Using a webhook -Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks`](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. +Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. Here are the steps to configure a Slack `Incoming Webhook` using PEM: From 39bd5436e6777da29a6774bb834b07edf3d2da1a Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 21 Feb 2024 09:37:05 -0500 Subject: [PATCH 05/50] Fixed capitalization --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 797d3bb53b1..6ec57a4d14f 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -135,7 +135,7 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: - Set **All alerts** to **Yes** to enable all alert levels to send notifications. - To send a notification when a specific alert level is reached, set the slider next to an alert level to **Yes**. You must set **All alerts** to **No** to configure an individual alert level. -### Using a webhook +#### Example of configuring a webhook using Slack Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. From 7904ccd2f5f837d8cae4deef9f140e55642a8c8e Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 26 Feb 2024 09:31:58 -0500 Subject: [PATCH 06/50] Changed header levels based on Simon's input --- .../docs/pem/9/monitoring_performance/notifications.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 6ec57a4d14f..cc3e2296a0b 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -92,6 +92,8 @@ You can define the webhook SSL parameters in the respective agent configuration ![Example - Webhook SSL Parameters in windows registry](../images/webhook_ssl_config_windows.png) +### Defining webhook headers + Use the **HTTP Headers** tab to define the header parameters to pass while calling the webhook endpoints: - Specify all the values as a key and value pair. @@ -100,6 +102,8 @@ Use the **HTTP Headers** tab to define the header parameters to pass while calli - To delete HTTP headers, select **Delete** to the left of **Key**. The header remains in the list but in strike-through font. Select **Save** to permanently delete the headers. - To edit the HTTP headers, select **Edit** to the left of **Key**. +### Defining webhook payloads + Use the **Payload** tab to define the JSON data to send to the endpoint when an alert is triggered: - **Type** specifies data to send in the format type, that is, JSON. @@ -130,12 +134,14 @@ Use the **Payload** tab to define the JSON data to send to the endpoint when an - Select **Test Connection** to test notification delivery to the mentioned endpoint. +### Defining webhook alert levels + Use the **Notifications** tab to specify an alert level for webhook endpoints: - Set **All alerts** to **Yes** to enable all alert levels to send notifications. - To send a notification when a specific alert level is reached, set the slider next to an alert level to **Yes**. You must set **All alerts** to **No** to configure an individual alert level. -#### Example of configuring a webhook using Slack +### Example of configuring a webhook using Slack Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. From 34523cda757c745204109a70008d9aba06f9b99d Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 26 Feb 2024 11:47:04 -0500 Subject: [PATCH 07/50] Update product_docs/docs/pem/9/monitoring_performance/notifications.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index cc3e2296a0b..c3ded04d1c9 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -149,7 +149,7 @@ Here are the steps to configure a Slack `Incoming Webhook` using PEM: - Configure the Slack application, if it's not already configured. - Activate `Incoming Webhooks` from Slack. -- Add new webhooks to the Slack workspace. You must add the channel and authorize the application for the incoming webhooks so the pemAgent can notify the alert using Slack. +- Add new webhooks to the Slack workspace. You must add the channel and authorize the application for the incoming webhooks so the PEM Agent can notify the alert using Slack. - Get the unique URL used in PEM to configure the webhook configurations. You can configure PEM to send notifications (low, medium, high) to Slack via a POST request. - The pemAgent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. From 7a01a6f15a4ec1e606e6df32ca897754e5b1a4a5 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 26 Feb 2024 11:47:19 -0500 Subject: [PATCH 08/50] Update product_docs/docs/pem/9/monitoring_performance/notifications.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index c3ded04d1c9..6380a72af62 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -151,7 +151,7 @@ Here are the steps to configure a Slack `Incoming Webhook` using PEM: - Activate `Incoming Webhooks` from Slack. - Add new webhooks to the Slack workspace. You must add the channel and authorize the application for the incoming webhooks so the PEM Agent can notify the alert using Slack. - Get the unique URL used in PEM to configure the webhook configurations. You can configure PEM to send notifications (low, medium, high) to Slack via a POST request. -- The pemAgent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. +- The PEM Agent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. Here is an example of a POST request from the pemAgent: From 2c9e3f3b7e50b01e07b1e250aea2e4793a7a2e9f Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 26 Feb 2024 11:47:27 -0500 Subject: [PATCH 09/50] Update product_docs/docs/pem/9/monitoring_performance/notifications.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 6380a72af62..cf1442d536c 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -143,7 +143,7 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: ### Example of configuring a webhook using Slack -Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the pemAgent can send a JSON payload with the message text and other options to Slack webhooks. +Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the PEM Agent can send a JSON payload with the message text and other options to Slack webhooks. Here are the steps to configure a Slack `Incoming Webhook` using PEM: From 9bd07ae2a78f3670903352170808856de120379c Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 26 Feb 2024 11:47:59 -0500 Subject: [PATCH 10/50] Update product_docs/docs/pem/9/monitoring_performance/notifications.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index cf1442d536c..00316880311 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -153,7 +153,7 @@ Here are the steps to configure a Slack `Incoming Webhook` using PEM: - Get the unique URL used in PEM to configure the webhook configurations. You can configure PEM to send notifications (low, medium, high) to Slack via a POST request. - The PEM Agent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. -Here is an example of a POST request from the pemAgent: +Here is an example of a POST request from the PEM Agent: ```shell POST https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXX/ From 8f56fe87ff9ed2e21d1271b57b9290e48067033c Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 13 May 2024 11:54:40 -0400 Subject: [PATCH 11/50] test attempt to combine prereqs topic with install template --- .../base.njk | 112 ++++++++++++++---- 1 file changed, 91 insertions(+), 21 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index e7bd911a54d..3bf14c0f7d7 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -17,38 +17,108 @@ redirects: {% endblock frontmatter %} +{% block introductory_notes %}You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers.{% endblock introductory_notes %} + {% block product_prerequisites %} -- Set up the repository. - - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - {%- filter indent(2) -%} - {% block repocheck %} - To determine if your repository exists, enter this command: - - `dnf repolist | grep enterprisedb` - {% endblock repocheck %} - {%- endfilter %} - - To set up the EDB repository: +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - 1. Select the button that provides access to the EDB repo. +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! + +3. Verify that the `sslutils` extension is installed on your Postgres server. + + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. + + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. + + ```shell + sudo {{packageManager}} install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + + For all platforms except Debian/Ubuntu: + + ```shell + sudo {{packageManager}} install sslutils_ postgresql-contrib + ``` + + For Debian/Ubuntu: + + ```shell + sudo {{packageManager}} postgresql--sslutils + ``` + + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + + For all platforms except Debian/Ubuntu: + + ```shell + sudo {{packageManager}} install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + + For Debian/Ubuntu: + + ```shell + sudo {{packageManager}} edb-postgresextended-sslutils- + ``` + + !!! Note For Debian and Ubuntu users + Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. + + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + + For Debian/Ubuntu: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). - !!! Note + For RHEL/AlmaLinux/Rocky Linux 8 and For RHEL/OL/CentOS 7: - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo {{packageManager}} upgrade + ``` - !!! + For Debian/Ubuntu and SLES: + + ```shell + sudo {{packageManager}} update + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +## Supported locales -- Review [configuration and authentication requirements](../prerequisites/) for PEM. - +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. {% endblock product_prerequisites %} {% block postinstall %} ## Initial configuration From e765d0cac57c8ef4c58d096b6d82182d414d2a0f Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 14 May 2024 10:38:33 -0400 Subject: [PATCH 12/50] fixed spacing issues --- .../base.njk | 89 ++++++++++--------- 1 file changed, 45 insertions(+), 44 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 3bf14c0f7d7..5bc9848c421 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -25,41 +25,41 @@ After fulfilling the prerequisites and completing the installation procedure des 1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. 2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - !!! Note - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - !!! + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. -3. Verify that the `sslutils` extension is installed on your Postgres server. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. +3. Verify that the `sslutils` extension is installed on your Postgres server. + + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. + + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - ```shell - sudo {{packageManager}} install edb-as-server-sslutils - ``` + ```shell + sudo {{packageManager}} install edb-as-server-sslutils + ``` - - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. - For all platforms except Debian/Ubuntu: + For all platforms except Debian/Ubuntu: ```shell sudo {{packageManager}} install sslutils_ postgresql-contrib ``` - For Debian/Ubuntu: + For Debian/Ubuntu: ```shell sudo {{packageManager}} postgresql--sslutils @@ -79,46 +79,43 @@ After fulfilling the prerequisites and completing the installation procedure des sudo {{packageManager}} edb-postgresextended-sslutils- ``` - !!! Note For Debian and Ubuntu users + !!! Note For Debian and Ubuntu users Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. - - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: + For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp - firewall-cmd --reload - ``` + firewall-cmd --reload + ``` - For Debian/Ubuntu: + For Debian/Ubuntu: - ```shell - iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT - ``` + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). - For RHEL/AlmaLinux/Rocky Linux 8 and For RHEL/OL/CentOS 7: + For RHEL/AlmaLinux/Rocky Linux 8 and For RHEL/OL/CentOS 7: - ```shell - sudo {{packageManager}} upgrade - ``` + ```shell + sudo {{packageManager}} upgrade + ``` - For Debian/Ubuntu and SLES: + For Debian/Ubuntu and SLES: - ```shell - sudo {{packageManager}} update - ``` - -## Supported locales + ```shell + sudo {{packageManager}} update + ``` -Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. {% endblock product_prerequisites %} {% block postinstall %} ## Initial configuration @@ -133,4 +130,8 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. {% endblock postinstall %} \ No newline at end of file From 370ee30a337469588c5b619550ffe2832a3c0512 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 14 May 2024 11:39:48 -0400 Subject: [PATCH 13/50] Interim checkin templatizing various install commands --- .../almalinux-8-or-rocky-linux-8.njk | 2 ++ .../almalinux-9-or-rocky-linux-9.njk | 2 ++ .../base.njk | 32 ++++++------------- .../centos-7.njk | 2 ++ .../ppc64le_index.njk | 2 ++ .../rhel-7-or-ol-7.njk | 2 ++ .../rhel-8-or-ol-8.njk | 2 ++ .../rhel-8_ppc64le.njk | 3 ++ .../rhel-9-or-ol-9.njk | 2 ++ .../rhel-9_ppc64le.njk | 2 ++ .../sles-12.njk | 2 ++ .../sles-12_ppc64le.njk | 2 ++ .../sles-15.njk | 2 ++ .../sles-15_ppc64le.njk | 2 ++ 14 files changed, 36 insertions(+), 23 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk index d587e822be4..7cc07207cb7 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk @@ -1,3 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk index 12656d73c50..83d47df9633 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk @@ -1,3 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-9-or-rocky-linux-9" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 5bc9848c421..8360f671ccd 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -1,5 +1,7 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pem{% endset %} +{% set ssutilsName = ssutilsName or 'postgresql--sslutils' %} +{% set ssutilsExtendedName = ssutilsExtendedName or '' %} {% import "platformBase/_deploymentConstants.njk" as deploy %} {% block frontmatter %} {# @@ -52,32 +54,16 @@ After fulfilling the prerequisites and completing the installation procedure des ``` - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. - - For all platforms except Debian/Ubuntu: - - ```shell - sudo {{packageManager}} install sslutils_ postgresql-contrib - ``` - - For Debian/Ubuntu: - ```shell - sudo {{packageManager}} postgresql--sslutils - ``` - + ```shell + sudo {{packageManager}} install {{ssutilsName}} + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - - For all platforms except Debian/Ubuntu: - - ```shell - sudo {{packageManager}} install edb-postgresextended-sslutils edb-postgresextended-contrib - ``` - - For Debian/Ubuntu: - ```shell - sudo {{packageManager}} edb-postgresextended-sslutils- - ``` + ```shell + sudo {{packageManager}} install edb-postgresextended-sslutils {{ssutilsExtendedName}} + ``` !!! Note For Debian and Ubuntu users Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk index 1224759bfd2..244b1dd2deb 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk @@ -1,5 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "centos-7" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block postinstall %} {{ super() }} - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk index f7f097c678e..f89c72e6fdc 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk @@ -1,5 +1,7 @@ {% extends "platformBase/ppc64le_index.njk" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% set productShortname="pem" %} {% block frontmatter %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk index bfec7833e0d..a22646e4d6d 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk @@ -1,5 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block postinstall %} {{ super() }} - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk index fa3995e8e8f..5012d31defe 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk @@ -1,3 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk index 473f252a37b..5a8f181a04b 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk @@ -1 +1,4 @@ + +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% extends "products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk" %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk index e57659be552..15b297e5d55 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk @@ -1,3 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk index 36f3cd2f819..ba079ef183f 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk @@ -1 +1,3 @@ {% extends "products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk index 6ac27252c2d..51bf4a2da02 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk @@ -1,5 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block introductory_notes %} !!! Note diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk index 37db62276f7..d3140da4208 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk @@ -1,2 +1,4 @@ {% extends "products/postgres-enterprise-manager-server/sles-12.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk index cf71670d058..2c7640ce9e9 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk @@ -1,5 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block introductory_notes %} !!! Note diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk index 754a64c69fc..c64bfb82433 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk @@ -1,2 +1,4 @@ {% extends "products/postgres-enterprise-manager-server/sles-15.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} From 2eb34859aae839ee365f40ee50eac5a1d92dafb4 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 15 May 2024 09:33:13 -0400 Subject: [PATCH 14/50] Block for Debian Ubuntu note --- .../products/postgres-enterprise-manager-server/base.njk | 8 ++------ .../postgres-enterprise-manager-server/debian-10.njk | 7 +++++++ .../postgres-enterprise-manager-server/debian-11.njk | 6 ++++++ .../postgres-enterprise-manager-server/ubuntu-20.04.njk | 6 ++++++ .../postgres-enterprise-manager-server/ubuntu-22.04.njk | 7 +++++++ 5 files changed, 28 insertions(+), 6 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 8360f671ccd..7745a80231a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -65,12 +65,8 @@ After fulfilling the prerequisites and completing the installation procedure des sudo {{packageManager}} install edb-postgresextended-sslutils {{ssutilsExtendedName}} ``` - !!! Note For Debian and Ubuntu users - Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. - - - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." - + {% block debianUbuntuNote %}{% endblock debianUbuntuNote %} + 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk index 5bc08e8f6b5..6a6045f37f4 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk @@ -5,3 +5,10 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} +{% block debianUbuntuNote %}!!! Note For Debian users + Debian 10 changed the requirements for accepting certificates. + + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk index dbd8399aa1c..f77df55eb6a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk @@ -5,3 +5,9 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} +{% block debianUbuntuNote %}!!! Note For Debian users + Debian 10 changed the requirements for accepting certificates. + + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk index a9c715bd684..cfbdd8a9339 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk @@ -5,3 +5,9 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} +{% block debianUbuntuNote %}!!! Note For Ubuntu users + Ubuntu 20 changed the requirements for accepting certificates. + + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk index 09981deeda4..3ed80f0a4f4 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk @@ -5,3 +5,10 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} +{% block debianUbuntuNote %}!!! Note For Ubuntu users + Ubuntu 20 changed the requirements for accepting certificates. + + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + + From be2ced925d36835d282059f4df544cff51d669e2 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 20 May 2024 11:44:56 -0400 Subject: [PATCH 15/50] Added variables for step 5 --- .../postgres-enterprise-manager-server/base.njk | 11 ++--------- .../postgres-enterprise-manager-server/debian-10.njk | 1 + .../postgres-enterprise-manager-server/debian-11.njk | 1 + .../postgres-enterprise-manager-server/sles-12.njk | 1 + .../sles-12_ppc64le.njk | 1 + .../postgres-enterprise-manager-server/sles-15.njk | 1 + .../sles-15_ppc64le.njk | 1 + .../ubuntu-20.04.njk | 1 + .../ubuntu-22.04.njk | 1 + 9 files changed, 10 insertions(+), 9 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 7745a80231a..c39cf191d8a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -2,6 +2,7 @@ {% set packageName %}edb-pem{% endset %} {% set ssutilsName = ssutilsName or 'postgresql--sslutils' %} {% set ssutilsExtendedName = ssutilsExtendedName or '' %} +{% set upgradeCommand = upgradeCommand or 'upgrade' %} {% import "platformBase/_deploymentConstants.njk" as deploy %} {% block frontmatter %} {# @@ -86,16 +87,8 @@ After fulfilling the prerequisites and completing the installation procedure des 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). - For RHEL/AlmaLinux/Rocky Linux 8 and For RHEL/OL/CentOS 7: - - ```shell - sudo {{packageManager}} upgrade - ``` - - For Debian/Ubuntu and SLES: - ```shell - sudo {{packageManager}} update + sudo {{packageManager}} {{upgradeCommand}} ``` {% endblock product_prerequisites %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk index 6a6045f37f4..804c7bc85f5 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "debian-10" %} +{% set upgradeCommand = "update" %} {% block repocheck %} To determine if your repository exists, enter this command: diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk index f77df55eb6a..b79fb666535 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "debian-11" %} +{% set upgradeCommand = "update" %} {% block repocheck %} To determine if your repository exists, enter this command: diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk index 51bf4a2da02..a820276e1d6 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set upgradeCommand = "update" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block introductory_notes %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk index d3140da4208..99bb871a980 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk @@ -1,4 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/sles-12.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set upgradeCommand = "update" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk index 2c7640ce9e9..cb3403f05f7 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set upgradeCommand = "update" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} {% block introductory_notes %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk index c64bfb82433..edc1991a352 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk @@ -1,4 +1,5 @@ {% extends "products/postgres-enterprise-manager-server/sles-15.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set upgradeCommand = "update" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk index cfbdd8a9339..94e33789c83 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "ubuntu-20.04" %} +{% set upgradeCommand = "update" %} {% block repocheck %} To determine if your repository exists, enter this command: diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk index 3ed80f0a4f4..7c65fade810 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk @@ -1,5 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "ubuntu-22.04" %} +{% set upgradeCommand = "update" %} {% block repocheck %} To determine if your repository exists, enter this command: From b3188761392c95881d1906b96129caff28e98286 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 20 May 2024 11:55:35 -0400 Subject: [PATCH 16/50] first step of templatizing step 4 --- .../products/postgres-enterprise-manager-server/base.njk | 4 ++-- .../postgres-enterprise-manager-server/rhel-9-or-ol-9.njk | 7 ++++++- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index c39cf191d8a..17afd00c837 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -69,8 +69,8 @@ After fulfilling the prerequisites and completing the installation procedure des {% block debianUbuntuNote %}{% endblock debianUbuntuNote %} 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - - For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: + + {% block firewallCommand %}{% endblock firewallCommand %}{% block firewallDebianCommand %}{% endblock firewallDebianCommand %} ```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk index 15b297e5d55..9d523ce4e3a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk @@ -2,4 +2,9 @@ {% set platformBaseTemplate = "rhel-9-or-ol-9" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} From 5c1da91d0db849d6708eabb7ee65cd7193d75702 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 21 May 2024 10:22:04 -0400 Subject: [PATCH 17/50] Final set of template changes --- .../almalinux-8-or-rocky-linux-8.njk | 7 ++++++- .../almalinux-9-or-rocky-linux-9.njk | 7 ++++++- .../postgres-enterprise-manager-server/base.njk | 12 ------------ .../postgres-enterprise-manager-server/centos-7.njk | 7 ++++++- .../postgres-enterprise-manager-server/debian-10.njk | 6 ++++-- .../postgres-enterprise-manager-server/debian-11.njk | 6 ++++-- .../ppc64le_index.njk | 5 +++++ .../rhel-7-or-ol-7.njk | 7 ++++++- .../rhel-8-or-ol-8.njk | 7 ++++++- .../postgres-enterprise-manager-server/sles-12.njk | 5 +++++ .../postgres-enterprise-manager-server/sles-15.njk | 5 +++++ .../sles-15_ppc64le.njk | 5 +++++ .../ubuntu-20.04.njk | 2 +- .../ubuntu-22.04.njk | 6 ++++-- 14 files changed, 63 insertions(+), 24 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk index 7cc07207cb7..156261dab2e 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk @@ -2,4 +2,9 @@ {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk index 83d47df9633..2a37ad6a77a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk @@ -2,4 +2,9 @@ {% set platformBaseTemplate = "almalinux-9-or-rocky-linux-9" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 17afd00c837..e30ae06c6e5 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -72,18 +72,6 @@ After fulfilling the prerequisites and completing the installation procedure des {% block firewallCommand %}{% endblock firewallCommand %}{% block firewallDebianCommand %}{% endblock firewallDebianCommand %} - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ``` - - For Debian/Ubuntu: - - ```shell - iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT - ``` - 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk index 244b1dd2deb..94cda62e221 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk @@ -8,4 +8,9 @@ - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. {% endblock postinstall %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk index 804c7bc85f5..4f69aa2e7ad 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk @@ -6,10 +6,12 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} -{% block debianUbuntuNote %}!!! Note For Debian users +{% block debianUbuntuNote %}!!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} - +{% block firewallDebianCommand %}```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ```{% endblock firewallDebianCommand %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk index b79fb666535..80010edf2c0 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk @@ -6,9 +6,11 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} -{% block debianUbuntuNote %}!!! Note For Debian users +{% block debianUbuntuNote %}!!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} - +{% block firewallDebianCommand %}```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ```{% endblock firewallDebianCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk index f89c72e6fdc..ca40801f7a1 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk @@ -9,3 +9,8 @@ redirects: - /pem/{{ product.version if product.version < 9 else "latest" }}/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/ {% endblock frontmatter %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk index a22646e4d6d..30f2bb7c9e9 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk @@ -8,4 +8,9 @@ - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. {% endblock postinstall %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk index 5012d31defe..adb33b892f7 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk @@ -2,4 +2,9 @@ {% set platformBaseTemplate = "rhel-8-or-ol-8" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk index a820276e1d6..91f2f4cafb1 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk @@ -14,3 +14,8 @@ To determine if your repository exists, enter this command: `zypper lr -E | grep enterprisedb` {% endblock repocheck %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk index cb3403f05f7..57dc7b85854 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk @@ -20,3 +20,8 @@ To determine if your repository exists, enter this command: `zypper lr -E | grep enterprisedb` {% endblock repocheck %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk index edc1991a352..884af550858 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk @@ -3,3 +3,8 @@ {% set upgradeCommand = "update" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk index 94e33789c83..a903ded797d 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk @@ -6,7 +6,7 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} -{% block debianUbuntuNote %}!!! Note For Ubuntu users +{% block debianUbuntuNote %}!!! Note Ubuntu 20 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk index 7c65fade810..e2564bc10f6 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-22.04.njk @@ -6,10 +6,12 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` {% endblock repocheck %} -{% block debianUbuntuNote %}!!! Note For Ubuntu users +{% block debianUbuntuNote %}!!! Note Ubuntu 20 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} - +{% block firewallDebianCommand %}```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ```{% endblock firewallDebianCommand %} From d25113f27e5da87c947de601298079a31ae96ff3 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 21 May 2024 11:46:16 -0400 Subject: [PATCH 18/50] Removed prerequisites topic and fixed broken links --- .../base.njk | 2 +- .../docs/pem/9/installing/prerequisites.mdx | 163 ------------------ 2 files changed, 1 insertion(+), 164 deletions(-) delete mode 100644 product_docs/docs/pem/9/installing/prerequisites.mdx diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index e30ae06c6e5..342c4320fff 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -73,7 +73,7 @@ After fulfilling the prerequisites and completing the installation procedure des {% block firewallCommand %}{% endblock firewallCommand %}{% block firewallDebianCommand %}{% endblock firewallDebianCommand %} 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. - If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). ```shell sudo {{packageManager}} {{upgradeCommand}} diff --git a/product_docs/docs/pem/9/installing/prerequisites.mdx b/product_docs/docs/pem/9/installing/prerequisites.mdx deleted file mode 100644 index 1e0a0e0d7a8..00000000000 --- a/product_docs/docs/pem/9/installing/prerequisites.mdx +++ /dev/null @@ -1,163 +0,0 @@ ---- -title: "Prerequisites to install the PEM server on Linux" -navTitle: "Linux prerequisites" -redirects: -- /pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/ ---- - -You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. - -After completing the prerequisites, [install](/pem/9/installing/linux_x86_64/) and [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. - -To install a PEM server on Linux, perform this preliminary configuration: - -1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - You can install this instance on the same server as you will use for the PEM web application or a separate server. - You can also use an existing Postgres instance providing it is configured as detailed in steps 2 and 3 below. - -2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - You must make the following changes manually, prior to configuration. (Additional changes are made to this file during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - !!! Note - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - !!! - -3. Verify that the `sslutils` extension is installed on your Postgres server. - If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - - For RHEL/AlmaLinux/Rocky Linux 8/9: - - ```shell - dnf install edb-as-server-sslutils - ``` - - For RHEL/OL/CentOS 7: - - ```shell - yum install edb-as-server-sslutils - ``` - - For Debian/Ubuntu: - - ```shell - apt install edb-as-server-sslutils - ``` - - For SLES: - - ```shell - zypper install edb-as-server-sslutils - ``` - - - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. - - For RHEL/AlmaLinux/Rocky Linux 8/9: - - ```shell - dnf install sslutils_ postgresql-contrib - ``` - - For RHEL/OL/CentOS 7: - - ```shell - yum install sslutils_ postgresql-contrib - ``` - - For Debian/Ubuntu: - - ```shell - apt install postgresql--sslutils - ``` - - For SLES: - - ```shell - zypper install sslutils_ postgresql-contrib - - - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - - For RHEL/AlmaLinux/Rocky Linux 8/9: - - ```shell - dnf install edb-postgresextended-sslutils edb-postgresextended-contrib - ``` - - For RHEL/OL/CentOS 7: - - ```shell - yum install edb-postgresextended-sslutils edb-postgresextended-contrib - ``` - - For Debian/Ubuntu: - - ```shell - apt install edb-postgresextended-sslutils- - ``` - - For SLES: - - ```shell - zypper install edb-postgresextended-sslutils edb-postgresextended-contrib - ``` - - !!! Note For Debian and Ubuntu users - Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. - - - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." - -4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - - For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ``` - - For Debian/Ubuntu: - - ```shell - iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT - ``` - -5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. - If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](dependencies.md). - - For RHEL/AlmaLinux/Rocky Linux 8: - - ```shell - dnf upgrade - ``` - - For RHEL/OL/CentOS 7: - - ```shell - yum upgrade - ``` - - For Debian/Ubuntu: - - ```shell - apt-get update - ``` - - For SLES: - - ```shell - zypper update - ``` - -## Supported locales - -Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. From b3b205f4ae08a90a5a328ed9016280171649b7f3 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 21 May 2024 11:47:07 -0400 Subject: [PATCH 19/50] Generated install files from template --- .../8/installing/linux_ppc64le/pem_rhel_8.mdx | 62 +++++++++++++---- .../8/installing/linux_ppc64le/pem_rhel_9.mdx | 62 +++++++++++++---- .../installing/linux_ppc64le/pem_sles_12.mdx | 58 ++++++++++++---- .../installing/linux_ppc64le/pem_sles_15.mdx | 58 ++++++++++++---- .../installing/linux_x86_64/pem_centos_7.mdx | 62 +++++++++++++---- .../installing/linux_x86_64/pem_debian_10.mdx | 67 +++++++++++++++---- .../installing/linux_x86_64/pem_debian_11.mdx | 67 +++++++++++++++---- .../linux_x86_64/pem_other_linux_8.mdx | 62 +++++++++++++---- .../linux_x86_64/pem_other_linux_9.mdx | 62 +++++++++++++---- .../8/installing/linux_x86_64/pem_rhel_7.mdx | 62 +++++++++++++---- .../8/installing/linux_x86_64/pem_rhel_8.mdx | 62 +++++++++++++---- .../8/installing/linux_x86_64/pem_rhel_9.mdx | 62 +++++++++++++---- .../8/installing/linux_x86_64/pem_sles_12.mdx | 58 ++++++++++++---- .../8/installing/linux_x86_64/pem_sles_15.mdx | 58 ++++++++++++---- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 63 +++++++++++++---- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 67 +++++++++++++++---- .../9/installing/linux_ppc64le/pem_rhel_8.mdx | 62 +++++++++++++---- .../9/installing/linux_ppc64le/pem_rhel_9.mdx | 62 +++++++++++++---- .../installing/linux_ppc64le/pem_sles_12.mdx | 58 ++++++++++++---- .../installing/linux_ppc64le/pem_sles_15.mdx | 58 ++++++++++++---- .../installing/linux_x86_64/pem_centos_7.mdx | 62 +++++++++++++---- .../installing/linux_x86_64/pem_debian_10.mdx | 67 +++++++++++++++---- .../installing/linux_x86_64/pem_debian_11.mdx | 67 +++++++++++++++---- .../linux_x86_64/pem_other_linux_8.mdx | 62 +++++++++++++---- .../linux_x86_64/pem_other_linux_9.mdx | 62 +++++++++++++---- .../9/installing/linux_x86_64/pem_rhel_7.mdx | 62 +++++++++++++---- .../9/installing/linux_x86_64/pem_rhel_8.mdx | 62 +++++++++++++---- .../9/installing/linux_x86_64/pem_rhel_9.mdx | 62 +++++++++++++---- .../9/installing/linux_x86_64/pem_sles_12.mdx | 58 ++++++++++++---- .../9/installing/linux_x86_64/pem_sles_15.mdx | 58 ++++++++++++---- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 63 +++++++++++++---- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 67 +++++++++++++++---- 32 files changed, 1536 insertions(+), 448 deletions(-) diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx index e2ab0a7970f..237b1617551 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_ppcle/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx index 0fcde925d21..421263913e2 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_ppcle/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx index fbf01e2e7b9..1b219165e47 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: ```shell @@ -76,3 +102,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx index ba95246600f..98fafd53ab5 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: @@ -81,3 +107,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx index 122b9787359..bfd11d36f87 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_centos7_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo yum install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo yum install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo yum install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo yum upgrade + ``` ## Install the package @@ -62,6 +92,10 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. + - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx index d1bb9157864..f00939d5423 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx @@ -13,35 +13,70 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Debian 10 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx index 564d24fc91a..d3571c17126 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx @@ -13,35 +13,70 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb11_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Debian 10 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx index a5f4e739e17..b61691f0184 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx @@ -14,35 +14,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux8_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -62,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx index fe5d95f23ee..9a128e159a2 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx @@ -14,35 +14,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux9_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -62,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx index 8f95c1bf895..6caf61ffc82 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel7_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo yum install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo yum install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo yum install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo yum upgrade + ``` ## Install the package @@ -62,6 +92,10 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. + - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx index e6fb9e8b466..6042a16dd61 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx index f710e83e0ba..c5f864a1185 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx @@ -13,35 +13,65 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx index 57c0e6e61af..8e492c8ec92 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: ```shell @@ -76,3 +102,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx index 0a4e7d93301..a0b3c246084 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: @@ -81,3 +107,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx index 5c670254057..960b4be8414 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -13,35 +13,66 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Ubuntu 20 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx index ae02e77b48d..a5f0efb0760 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -13,35 +13,70 @@ redirects: - /pem/8/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu22_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Ubuntu 20 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx index 315b3b8664a..586e24fb18d 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_ppcle/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx index 2e4a8a42744..810b897fdd0 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_ppcle/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx index c00aad01555..2e83f4393a5 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: ```shell @@ -76,3 +102,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index d3e5f871a32..0bf32d885aa 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: @@ -81,3 +107,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx index 5d43d0027cf..c2183cbd54b 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_centos7_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo yum install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo yum install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo yum install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo yum upgrade + ``` ## Install the package @@ -62,6 +92,10 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. + - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx index e13aac87871..e02be33bfc4 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx @@ -13,35 +13,70 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Debian 10 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx index 43e0b3be356..f805dec48da 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx @@ -13,35 +13,70 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb11_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Debian 10 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx index ab13bea481a..5c2284196d4 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx @@ -14,35 +14,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux8_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -62,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx index 7bff34ee84e..5855463c0c6 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx @@ -14,35 +14,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_other_linux9_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -62,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx index 70ff797e8c7..46a1ee5989a 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel7_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo yum install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo yum install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo yum install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo yum upgrade + ``` ## Install the package @@ -62,6 +92,10 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. + - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx index 910bf6737ca..3119df92ad8 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel8_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx index ea4536237bd..607d817339d 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx @@ -13,35 +13,65 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - `dnf repolist | grep enterprisedb` + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the EDB repository: + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. +3. Verify that the `sslutils` extension is installed on your Postgres server. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - !!! Note + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + ```shell + sudo dnf install edb-as-server-sslutils + ``` - !!! + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` ## Install the package @@ -61,3 +91,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx index d717efe08a2..f71dd3dba86 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: ```shell @@ -76,3 +102,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index a48e898e967..7120b3f023f 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx @@ -21,31 +21,57 @@ redirects: Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. - `zypper lr -E | grep enterprisedb` +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - - To set up the EDB repository: + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - !!! Note + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. +3. Verify that the `sslutils` extension is installed on your Postgres server. - !!! + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo zypper install edb-as-server-sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo zypper update + ``` - Activate the required SUSE module: @@ -81,3 +107,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index fa76f38198c..30182413caa 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -13,35 +13,66 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu20_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Ubuntu 20 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +92,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index de59993255f..066a9ba685c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -13,35 +13,70 @@ redirects: - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_ubuntu22_x86/ --- +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + ## Prerequisites Before you begin the installation process: -- Set up the repository. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. - Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. - To determine if your repository exists, enter this command: + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. - `apt-cache search enterprisedb` + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - To set up the EDB repository: + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +3. Verify that the `sslutils` extension is installed on your Postgres server. - 1. Select the button that provides access to the EDB repo. - 1. Select the platform and software that you want to download. + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. - !!! Note + ```shell + sudo apt-get install edb-as-server-sslutils + ``` - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo apt-get install postgresql--sslutils + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. - !!! + ```shell + sudo apt-get install edb-postgresextended-sslutils + ``` -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! Note + Ubuntu 20 changed the requirements for accepting certificates. -- Review [configuration and authentication requirements](../prerequisites/) for PEM. + - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo apt-get update + ``` ## Install the package @@ -61,3 +96,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p !!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. From a7c5c9a34773117c141a5be14706b642cbb6a539 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 22 May 2024 12:19:26 -0400 Subject: [PATCH 20/50] Many small changes to clean up templates --- .../almalinux-8-or-rocky-linux-8.njk | 3 ++- .../almalinux-9-or-rocky-linux-9.njk | 3 ++- .../base.njk | 7 +++--- .../centos-7.njk | 3 ++- .../debian-10.njk | 2 +- .../debian-11.njk | 4 ++-- .../ppc64le_index.njk | 1 + .../rhel-7-or-ol-7.njk | 3 ++- .../rhel-8-or-ol-8.njk | 3 ++- .../rhel-8_ppc64le.njk | 3 ++- .../rhel-9-or-ol-9.njk | 3 ++- .../rhel-9_ppc64le.njk | 3 ++- .../sles-12.njk | 7 ++++-- .../sles-12_ppc64le.njk | 4 +++- .../sles-15.njk | 22 +++++++++++-------- .../sles-15_ppc64le.njk | 8 ++----- .../ubuntu-20.04.njk | 3 +++ 17 files changed, 50 insertions(+), 32 deletions(-) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk index 156261dab2e..cc33f1f1472 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block prerequisites %}{% endblock prerequisites %} {% block firewallCommand %}```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk index 2a37ad6a77a..aa9fb4ab370 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-9-or-rocky-linux-9.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-9-or-rocky-linux-9" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block prerequisites %}{% endblock prerequisites %} {% block firewallCommand %}```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 342c4320fff..769ea8040c4 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -1,6 +1,7 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pem{% endset %} {% set ssutilsName = ssutilsName or 'postgresql--sslutils' %} +{% set ssutilsExtendedFirstName = ssutilsExtendedFirstName or 'edb-postgresextended-sslutils-'%} {% set ssutilsExtendedName = ssutilsExtendedName or '' %} {% set upgradeCommand = upgradeCommand or 'upgrade' %} {% import "platformBase/_deploymentConstants.njk" as deploy %} @@ -34,9 +35,9 @@ After fulfilling the prerequisites and completing the installation procedure des Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -63,7 +64,7 @@ After fulfilling the prerequisites and completing the installation procedure des - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo {{packageManager}} install edb-postgresextended-sslutils {{ssutilsExtendedName}} + sudo {{packageManager}} install {{ssutilsExtendedFirstName}} {{ssutilsExtendedName}} ``` {% block debianUbuntuNote %}{% endblock debianUbuntuNote %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk index 94cda62e221..da8e815b82d 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "centos-7" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block postinstall %} {{ super() }} - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk index 4f69aa2e7ad..d42fc18a4d2 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk @@ -10,7 +10,7 @@ To determine if your repository exists, enter this command: Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak"{% endblock debianUbuntuNote %} {% block firewallDebianCommand %}```shell iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT ```{% endblock firewallDebianCommand %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk index 80010edf2c0..1a4ae008448 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/debian-11.njk @@ -5,12 +5,12 @@ To determine if your repository exists, enter this command: `apt-cache search enterprisedb` -{% endblock repocheck %} +{% endblock repocheck %} {% block debianUbuntuNote %}!!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak"{% endblock debianUbuntuNote %} {% block firewallDebianCommand %}```shell iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT ```{% endblock firewallDebianCommand %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk index ca40801f7a1..bb9c90e3d83 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ppc64le_index.njk @@ -2,6 +2,7 @@ {% extends "platformBase/ppc64le_index.njk" %} {% set ssutilsName %}edb-as-server-sslutils{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% set productShortname="pem" %} {% block frontmatter %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk index 30f2bb7c9e9..61f8562e2c9 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block postinstall %} {{ super() }} - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk index adb33b892f7..2c2193a4f0a 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block prerequisites %}{% endblock prerequisites %} {% block firewallCommand %}```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk index 5a8f181a04b..8659ed31160 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-8_ppc64le.njk @@ -1,4 +1,5 @@ -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% extends "products/postgres-enterprise-manager-server/rhel-8-or-ol-8.njk" %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk index 9d523ce4e3a..61856ff934e 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk @@ -1,7 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-9-or-ol-9" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block prerequisites %}{% endblock prerequisites %} {% block firewallCommand %}```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk index ba079ef183f..1e28bcbcee6 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_ppc64le.njk @@ -1,3 +1,4 @@ {% extends "products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk index 91f2f4cafb1..883445754c5 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk @@ -1,8 +1,9 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} {% set upgradeCommand = "update" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block introductory_notes %} !!! Note @@ -18,4 +19,6 @@ To determine if your repository exists, enter this command: firewall-cmd --permanent --zone=public --add-port=8443/tcp firewall-cmd --reload - ```{% endblock firewallCommand %} \ No newline at end of file + ```{% endblock firewallCommand %} +{% block prerequisites %}{% endblock prerequisites %} + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk index 99bb871a980..cf53ae658dc 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk @@ -1,5 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/sles-12.njk" %} {% set platformBaseTemplate = "sles-12" %} {% set upgradeCommand = "update" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk index 57dc7b85854..6606c7a221b 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15.njk @@ -1,27 +1,31 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} {% set upgradeCommand = "update" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block introductory_notes %} !!! Note Postgres Enterprise Manager 8.3 and later is supported on SLES. {% endblock introductory_notes %} -{% block activateSUSEmodule %} +# {% block activateSUSEmodule %} # You can use SLES 15 SP3 for PEM 8.3 and later: -sudo SUSEConnect -p PackageHub/15.3/{{ platform.arch }} +# sudo SUSEConnect -p PackageHub/15.3/{{ platform.arch }} # You can use SLES 15 SP4 for PEM 8.6 and later: -sudo SUSEConnect -p PackageHub/15.4/{{ platform.arch }} -{% endblock activateSUSEmodule %} -{% block repocheck %} -To determine if your repository exists, enter this command: +# sudo SUSEConnect -p PackageHub/15.4/{{ platform.arch }} +# {% endblock activateSUSEmodule %} +# {% block repocheck %} +# To determine if your repository exists, enter this command: -`zypper lr -E | grep enterprisedb` -{% endblock repocheck %} +# `zypper lr -E | grep enterprisedb` +# {% endblock repocheck %} {% block firewallCommand %}```shell firewall-cmd --permanent --zone=public --add-port=8443/tcp firewall-cmd --reload ```{% endblock firewallCommand %} +{% block prerequisites %}{% endblock prerequisites %} + + diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk index 884af550858..0abf30b3b45 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-15_ppc64le.njk @@ -1,10 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/sles-15.njk" %} {% set platformBaseTemplate = "sles-15" %} {% set upgradeCommand = "update" %} -{% set ssutilsName %}edb-as-server-sslutils{% endset %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} {% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} -{% block firewallCommand %}```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ```{% endblock firewallCommand %} \ No newline at end of file +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk index a903ded797d..32da5b84881 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk @@ -11,4 +11,7 @@ To determine if your repository exists, enter this command: - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak."{% endblock debianUbuntuNote %} +{% block firewallDebianCommand %}```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ```{% endblock firewallDebianCommand %} From 2c36b683c1ca8b20bc829d69b0adf0e43c6ff613 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 22 May 2024 12:20:13 -0400 Subject: [PATCH 21/50] Generated files based on latest templates --- .../8/installing/linux_ppc64le/pem_rhel_8.mdx | 6 ++--- .../8/installing/linux_ppc64le/pem_rhel_9.mdx | 6 ++--- .../installing/linux_ppc64le/pem_sles_12.mdx | 17 +++----------- .../installing/linux_ppc64le/pem_sles_15.mdx | 22 +++---------------- .../installing/linux_x86_64/pem_centos_7.mdx | 6 ++--- .../installing/linux_x86_64/pem_debian_10.mdx | 8 +++---- .../installing/linux_x86_64/pem_debian_11.mdx | 8 +++---- .../linux_x86_64/pem_other_linux_8.mdx | 6 ++--- .../linux_x86_64/pem_other_linux_9.mdx | 6 ++--- .../8/installing/linux_x86_64/pem_rhel_7.mdx | 6 ++--- .../8/installing/linux_x86_64/pem_rhel_8.mdx | 6 ++--- .../8/installing/linux_x86_64/pem_rhel_9.mdx | 6 ++--- .../8/installing/linux_x86_64/pem_sles_12.mdx | 17 +++----------- .../8/installing/linux_x86_64/pem_sles_15.mdx | 22 +++---------------- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 10 ++++++--- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 6 ++--- .../9/installing/linux_ppc64le/pem_rhel_8.mdx | 6 ++--- .../9/installing/linux_ppc64le/pem_rhel_9.mdx | 6 ++--- .../installing/linux_ppc64le/pem_sles_12.mdx | 17 +++----------- .../installing/linux_ppc64le/pem_sles_15.mdx | 22 +++---------------- .../installing/linux_x86_64/pem_centos_7.mdx | 6 ++--- .../installing/linux_x86_64/pem_debian_10.mdx | 8 +++---- .../installing/linux_x86_64/pem_debian_11.mdx | 8 +++---- .../linux_x86_64/pem_other_linux_8.mdx | 6 ++--- .../linux_x86_64/pem_other_linux_9.mdx | 6 ++--- .../9/installing/linux_x86_64/pem_rhel_7.mdx | 6 ++--- .../9/installing/linux_x86_64/pem_rhel_8.mdx | 6 ++--- .../9/installing/linux_x86_64/pem_rhel_9.mdx | 6 ++--- .../9/installing/linux_x86_64/pem_sles_12.mdx | 17 +++----------- .../9/installing/linux_x86_64/pem_sles_15.mdx | 22 +++---------------- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 10 ++++++--- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 6 ++--- 32 files changed, 108 insertions(+), 208 deletions(-) diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx index 237b1617551..c23c09c09a7 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx index 421263913e2..e83728d34d3 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx index 1b219165e47..e7f9fec8722 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,17 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/ppc64le - sudo SUSEConnect -p sle-sdk/12.5/ppc64le - - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx index 98fafd53ab5..8267bb22f2c 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,22 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/ppc64le - - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/ppc64le - - ``` - -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx index bfd11d36f87..ee5b942c896 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo yum install edb-as-server-sslutils + sudo yum install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx index f00939d5423..1f7a5c6ed54 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,14 +56,14 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak" 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx index d3571c17126..60ee7563380 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,14 +56,14 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak" 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx index b61691f0184..0a70d25bcb9 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx @@ -30,9 +30,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -52,7 +52,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx index 9a128e159a2..aa893aea3fd 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx @@ -30,9 +30,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -52,7 +52,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx index 6caf61ffc82..9408f3cae82 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo yum install edb-as-server-sslutils + sudo yum install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx index 6042a16dd61..4306297c444 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx index c5f864a1185..dad2af14801 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx index 8e492c8ec92..e0cc3063c40 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,17 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/x86_64 - sudo SUSEConnect -p sle-sdk/12.5/x86_64 - - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx index a0b3c246084..c3a196916a1 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,22 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/x86_64 - - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/x86_64 - - ``` - -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx index 960b4be8414..dd3424ba47c 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,7 +56,7 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note @@ -67,6 +67,10 @@ Before you begin the installation process: 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx index a5f0efb0760..f9e48789da9 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,7 +56,7 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx index 586e24fb18d..4ef21d2427d 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx index 810b897fdd0..a27ac7c4e93 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx index 2e83f4393a5..bf1021cf9ed 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,17 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/ppc64le - sudo SUSEConnect -p sle-sdk/12.5/ppc64le - - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index 0bf32d885aa..2e6eb9f4224 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,22 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/ppc64le - - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/ppc64le - - ``` - -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx index c2183cbd54b..76642163e81 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo yum install edb-as-server-sslutils + sudo yum install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx index e02be33bfc4..65eb2600435 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,14 +56,14 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak" 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx index f805dec48da..596e4600be5 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,14 +56,14 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note Debian 10 changed the requirements for accepting certificates. - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it. - - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak." + - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak" 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx index 5c2284196d4..c844c0fd4d6 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx @@ -30,9 +30,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -52,7 +52,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx index 5855463c0c6..d8fb53e3c9c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx @@ -30,9 +30,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -52,7 +52,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx index 46a1ee5989a..dc1d2793526 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo yum install edb-as-server-sslutils + sudo yum install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx index 3119df92ad8..42b8507dee7 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx index 607d817339d..b9e8eec5bea 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo dnf install edb-as-server-sslutils + sudo dnf install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx index f71dd3dba86..cad96c6ef54 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,17 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/x86_64 - sudo SUSEConnect -p sle-sdk/12.5/x86_64 - - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index 7120b3f023f..033a39261da 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -51,7 +51,7 @@ Before you begin the installation process: - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. ```shell - sudo zypper install edb-as-server-sslutils + sudo zypper install sslutils_ postgresql-contrib ``` - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell @@ -73,22 +73,6 @@ Before you begin the installation process: sudo zypper update ``` -- Activate the required SUSE module: - - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/x86_64 - - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/x86_64 - - ``` - -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` - ## Install the package ```shell diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index 30182413caa..182bcfc93f5 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,7 +56,7 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note @@ -67,6 +67,10 @@ Before you begin the installation process: 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + ```shell + iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT + ``` + 5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index 066a9ba685c..52346dc11a6 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -29,9 +29,9 @@ Before you begin the installation process: Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).) - - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location in which you run the configuration script. In practice, this means the server on which the backend database is located and the server on which the PEM web application is to be installed, if they're different. + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. - - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, for example, `host all superusername 127.0.0.1/32 scram-sha-256`. + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. !!! Note If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). @@ -56,7 +56,7 @@ Before you begin the installation process: - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. ```shell - sudo apt-get install edb-postgresextended-sslutils + sudo apt-get install edb-postgresextended-sslutils- ``` !!! Note From 40978f0bc46d05825499b2349aed0639c73b8d93 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=ADn=20Marqu=C3=A9s?= Date: Fri, 31 May 2024 12:40:05 -0300 Subject: [PATCH 22/50] Update readonly.mdx --- product_docs/docs/pgd/5/routing/readonly.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/routing/readonly.mdx b/product_docs/docs/pgd/5/routing/readonly.mdx index 1245d1929e1..77a9d3bc022 100644 --- a/product_docs/docs/pgd/5/routing/readonly.mdx +++ b/product_docs/docs/pgd/5/routing/readonly.mdx @@ -34,7 +34,7 @@ Only data nodes that aren't the write leader are valid as read-only nodes. For r ## Creating a proxy configuration -Proxy creation functions in PGD take an optional `proxy-mode` parameter. This parameter can be set to one of the following values: +Proxy creation functions in PGD take an optional `proxy_mode` parameter. This parameter can be set to one of the following values: * `default`: This is the default value. It creates a proxy that can handles traffic that follows the write leader on port 6432. * `read-only`: This option creates a read-only proxy that routes traffic to nodes that aren't the write leader. It handles this read-only traffic only on port 6433. * `any`: This option creates create a proxy that can handle both read-only and write-leader-following traffic on separate ports: 6432 for write-leader-following traffic and 6433 for read-only traffic. From 03ffde3ba8c0f6ad0982082f391b3f88a5339267 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 31 May 2024 16:50:40 +0100 Subject: [PATCH 23/50] Further updates readonly.mdx --- product_docs/docs/pgd/5/routing/readonly.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/routing/readonly.mdx b/product_docs/docs/pgd/5/routing/readonly.mdx index 77a9d3bc022..c6b2da42ddc 100644 --- a/product_docs/docs/pgd/5/routing/readonly.mdx +++ b/product_docs/docs/pgd/5/routing/readonly.mdx @@ -34,11 +34,13 @@ Only data nodes that aren't the write leader are valid as read-only nodes. For r ## Creating a proxy configuration -Proxy creation functions in PGD take an optional `proxy_mode` parameter. This parameter can be set to one of the following values: +SQL Proxy creation functions in PGD take an optional `proxy_mode` parameter. This parameter can be set to one of the following values: * `default`: This is the default value. It creates a proxy that can handles traffic that follows the write leader on port 6432. * `read-only`: This option creates a read-only proxy that routes traffic to nodes that aren't the write leader. It handles this read-only traffic only on port 6433. * `any`: This option creates create a proxy that can handle both read-only and write-leader-following traffic on separate ports: 6432 for write-leader-following traffic and 6433 for read-only traffic. +PGD CLI proxy creation passes the `proxy_mode` value using the `-proxy-mode` flag. + ### Creating a Read-Only Proxy #### Using SQL @@ -53,7 +55,7 @@ This command creates a read-only proxy named `proxy-ro1` in group `group-a`. By #### Using PGD CLI -To create a new read-only proxy, use the `pgd create-proxy` command with the optional `--proxy_mode` flag set to `read-only`. +To create a new read-only proxy, use the `pgd create-proxy` command with the optional `--proxy-mode` flag set to `read-only`. ```sh pgd create-proxy --proxy-name proxy-ro1 --node-group group-a --proxy-mode read-only From 29dc2a3b9720eb998e9b3422ecfcc0c58705c810 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 31 May 2024 16:52:10 +0100 Subject: [PATCH 24/50] Fixed -- typo --- product_docs/docs/pgd/5/routing/readonly.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/routing/readonly.mdx b/product_docs/docs/pgd/5/routing/readonly.mdx index c6b2da42ddc..f62cd192224 100644 --- a/product_docs/docs/pgd/5/routing/readonly.mdx +++ b/product_docs/docs/pgd/5/routing/readonly.mdx @@ -39,7 +39,7 @@ SQL Proxy creation functions in PGD take an optional `proxy_mode` parameter. Thi * `read-only`: This option creates a read-only proxy that routes traffic to nodes that aren't the write leader. It handles this read-only traffic only on port 6433. * `any`: This option creates create a proxy that can handle both read-only and write-leader-following traffic on separate ports: 6432 for write-leader-following traffic and 6433 for read-only traffic. -PGD CLI proxy creation passes the `proxy_mode` value using the `-proxy-mode` flag. +PGD CLI proxy creation passes the `proxy_mode` value using the `--proxy-mode` flag. ### Creating a Read-Only Proxy From 8032ecd77d1d8b2967a720b5b4881d3b72c0be1d Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 5 Jun 2024 08:48:00 +0100 Subject: [PATCH 25/50] passthrough metadata implemented for import Signed-off-by: Dj Walker-Morgan --- scripts/source/tpa.js | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/scripts/source/tpa.js b/scripts/source/tpa.js index 17287a256f8..9b593fd2e69 100644 --- a/scripts/source/tpa.js +++ b/scripts/source/tpa.js @@ -6,12 +6,12 @@ import * as path from "path"; import fs from "fs/promises"; -import pkg from 'to-vfile'; -const {write, read} = pkg; +import pkg from "to-vfile"; +const { write, read } = pkg; import remarkParse from "remark-parse"; -import mdx from "remark-mdx"; +import mdx from "remark-mdx"; import unified from "unified"; import remarkFrontmatter from "remark-frontmatter"; import remarkStringify from "remark-stringify"; @@ -185,8 +185,15 @@ function stripEmptyComments(rawMarkdown) { function transformer() { return (tree, file) => { const filename = path.relative(basePath, file.path); - const metadata = fileToMetadata[filename]; - if (!metadata) console.warn(`No metadata for ${filename}`); + var metadata = fileToMetadata[filename]; + for (let i = 0; i < tree.children.length; ++i) { + const node = tree.children[i]; + if (node.type === "yaml") { + metadata = Object.assign({}, metadata || {}, yaml.load(node.value)); + tree.children.splice(i--, 1); + break; + } + } let title = ""; for (let i = 0; i < tree.children.length; ++i) { const node = tree.children[i]; From aa887a463695ab249a7de79879d5ef4cd44c7349 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 5 Jun 2024 08:48:20 +0100 Subject: [PATCH 26/50] add missing topic to nav index Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/index.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/tpa/23/index.mdx b/product_docs/docs/tpa/23/index.mdx index 58e630134c9..00ba8eca7ac 100644 --- a/product_docs/docs/tpa/23/index.mdx +++ b/product_docs/docs/tpa/23/index.mdx @@ -34,6 +34,7 @@ navigation: - ansible-and-sudo - misc-configure-putty - misc-troubleshooting + - task-selection - reference title: Trusted Postgres Architect originalFilePath: index.md From 26c1ac2e4940ae90031820a3fe1928f696ff98f5 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 5 Jun 2024 14:34:00 +0100 Subject: [PATCH 27/50] Added new explore replication section Signed-off-by: Dj Walker-Morgan --- .../further_explore_replication.mdx | 211 ++++++++++++++++++ product_docs/docs/pgd/5/quickstart/index.mdx | 1 + .../docs/pgd/5/quickstart/quick_start_aws.mdx | 1 + .../pgd/5/quickstart/quick_start_docker.mdx | 1 + .../pgd/5/quickstart/quick_start_linux.mdx | 1 + 5 files changed, 215 insertions(+) create mode 100644 product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx new file mode 100644 index 00000000000..b8b301c8880 --- /dev/null +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -0,0 +1,211 @@ +--- +title: Exploring replication with PGD +navTitle: Exploring replication +deepToC: true +--- + +## Explore replication with PGD + +With the cluster up and running, it's worthwhile to run some basic checks to see how effectively it's replicating. + +The following example shows one quick way to do this, but you must ensure that any testing you perform is appropriate for your use case. + +* **Preparation** + * Ensure the cluster is ready: + * Log in to the database on first host. + * Run `select bdr.wait_slot_confirm_lsn(NULL, NULL);`. + * When the query returns, the cluster is ready. + +* **Create data** + The simplest way to test that the cluster is replicating is to log in to a node, create a table, and populate it. On the first node, + * Create a table: + ```sql + CREATE TABLE quicktest ( id SERIAL PRIMARY KEY, value INT ); + ``` + * Populate the table: + ```sql + INSERT INTO quicktest (value) SELECT random()*10000 + FROM generate_series(1,10000); + ``` + * Monitor replication performance: + ```sql + select * from bdr.node_replication_rates; + ``` + * Get a sum of the value column (for checking): + ```sql + select COUNT(*),SUM(value) from quicktest; + ``` + +* **Check data** + * Log in to a second node. + * Get a sum of the value column (for checking): + ```sql + select COUNT(*),SUM(value) from quicktest; + ``` + * Compare with the result from first node. + * Log in to a third node. + * get a sum of the value column (for checking): + ```sql + select COUNT(*),SUM(value) from quicktest; + ``` + * Compare with the result from the first and second nodes. + +## Worked example + +### Preparation + +Our cluster has three data nodes, kaboom, kaftan and kaolin. We will use kaboom as our first node. Log in to kaboom and then into kaboom's Postgres server. + +``` +cd democluster +ssh -F ssh_config kaboom +sudo -iu enterprisedb psql bdrdb +``` + +#### Ensure the cluster is ready + +To ensure that the cluster is ready to go, run: + +``` +select bdr.wait_slot_confirm_lsn(NULL, NULL); +__OUTPUT__ + wait_slot_confirm_lsn +----------------------- + +(1 row) +``` + +This query waits if the cluster is busy initializing and returns when the cluster is ready. + +### Create data + +#### On the first node (kaboom), create a table + +Run: + +```sql +CREATE TABLE quicktest ( id SERIAL PRIMARY KEY, value INT ); +__OUTPUT__ +CREATE TABLE +``` + +#### On kaboom, populate the table + +``` +INSERT INTO quicktest (value) SELECT random()*10000 FROM generate_series(1,10000); +__OUTPUT__ +INSERT 0 10000 +``` + +This command generates a table of 10000 rows of random values. + +#### On kaboom, monitor performance + +As soon as possible, run: + +```sql +select * from bdr.node_replication_rates; +__OUTPUT__ + peer_node_id | target_name | sent_lsn | replay_lsn | replay_lag | replay_lag_bytes | replay_lag_size | apply_rate | catchup_interval +--------------+-------------+-----------+------------+------------+------------------+-----------------+------------+------------------ + 3490219809 | kaftan | 0/F57D120 | 0/F57D120 | 00:00:00 | 0 | 0 bytes | 9158 | 00:00:00 + 2111777360 | kaolin | 0/F57D120 | 0/F57D120 | 00:00:00 | 0 | 0 bytes | 9293 | 00:00:00 +(2 rows) +``` + +The command shows statistics about how quickly that data was replicated to the other two nodes: + + +Note that the replay_lag values are 0, showing no lag, and the LSN values are in sync, meaning the data is already replicated. + +#### On kaboom get a checksum + +Run: + +```sql +select COUNT(*),SUM(value) from quicktest; +``` + +This command calculates a sum of the values from the generated data: + +```sql +bdrdb=# select COUNT(*),SUM(value) from quicktest; +__OUTPUT__ + count | sum +--------+----------- + 100000 | 498884606 +(1 row) +``` + +Your sum will be different because the values in the table are random numbers, but the count should be 100000. + +### Check data + +Our second host will be "kaftan". In another window (or session), log in to kaftan's Postgres server: + +``` +cd democluster +ssh -F ssh_config kaftan +sudo -iu enterprisedb psql bdrdb +``` + +#### On the second node (kaftan), get a checksum + +Run: + +```sql +select COUNT(*),SUM(value) from quicktest; +``` + +This command gets node-two's values for the generated data: + +```sql +bdrdb=# select COUNT(*),SUM(value) from quicktest; +__OUTPUT__ + count | sum +--------+----------- + 100000 | 498884606 +(1 row) +``` + +#### Compare with the result from the first node (kaboom) + +The values are identical. + +You can repeat the process with the third node (kaolin), or generate new data on any node and see it replicate to the other nodes. + +#### Log in to the third node (kaolin) + +The last node is kaolin, our third node. In another window(or session), log in to the kaolin and then into kaolin's Postgres server: + +``` +cd democluster +ssh -F ssh_config kaolin +sudo -iu enterprisedb psql bdrdb +``` + +#### On kaolin, get a checksum + +Run: + +```sql +select COUNT(*),SUM(value) from quicktest; +``` + +This command gets kaolin's values for the generated data: + +```sql +bdrdb=# select COUNT(*),SUM(value) from quicktest; +__OUTPUT__ + count | sum +--------+----------- + 100000 | 498884606 +(1 row) +``` + +#### Compare the results. + +Compare the the result from the first and second nodes (kaboom and kaftan) with the result from kaolin. The values will be identical on all three nodes. + +## Next steps + diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 6d600035864..778b0f79325 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -10,6 +10,7 @@ navigation: - quick_start_aws - quick_start_cloud - connecting_applications +- further_explore_replication - further_explore_failover - further_explore_conflicts - next_steps diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx index 079211cebdc..e6a2aa70631 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx @@ -319,6 +319,7 @@ bdrdb=# ## Explore your cluster * [Connect your database](connecting_applications) to applications +* [Explore replication](further_explore_replication) with hands-on exercises * [Explore failover](further_explore_failover) with hands-on exercises * [Understand conflicts](further_explore_conflicts) by creating and monitoring them * [Next steps](next_steps) in working with your cluster diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx index 2d3d9f01230..0ec807e46c8 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx @@ -310,6 +310,7 @@ bdrdb=# ## Explore your cluster * [Connect to your database](connecting_applications) to applications +* [Explore replication](further_explore_replication) with hands-on exercises * [Explore failover](further_explore_failover) with hands-on exercises * [Understand conflicts](further_explore_conflicts) by creating and monitoring them * [Next steps](next_steps) in working with your cluster diff --git a/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx b/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx index acf40655704..8fb9d2e5538 100644 --- a/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx +++ b/product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx @@ -367,6 +367,7 @@ bdrdb=# ## Explore your cluster * [Connect to your database](connecting_applications) to applications +* [Explore replication](further_explore_replication) with hands-on exercises * [Explore failover](further_explore_failover) with hands-on exercises * [Understand conflicts](further_explore_conflicts) by creating and monitoring them * [Next steps](next_steps) in working with your cluster From 6e6a173040fdc304f6de7e2e8c35b11ad1d24083 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 6 Jun 2024 14:07:10 +0100 Subject: [PATCH 28/50] Update product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx Co-authored-by: Phil Eaton --- .../docs/pgd/5/quickstart/further_explore_replication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx index b8b301c8880..6f7bda3c092 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -17,7 +17,7 @@ The following example shows one quick way to do this, but you must ensure that a * When the query returns, the cluster is ready. * **Create data** - The simplest way to test that the cluster is replicating is to log in to a node, create a table, and populate it. On the first node, + The simplest way to test that the cluster is replicating is to log in to a node, create a table, populate it, and see the data you populated appear on a second node. On the first node, * Create a table: ```sql CREATE TABLE quicktest ( id SERIAL PRIMARY KEY, value INT ); From 96114cc4afab507710a7635efb868edd0f077ce6 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 6 Jun 2024 14:07:32 +0100 Subject: [PATCH 29/50] Update product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx Co-authored-by: Phil Eaton --- .../docs/pgd/5/quickstart/further_explore_replication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx index 6f7bda3c092..959fafe907f 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -37,7 +37,7 @@ The following example shows one quick way to do this, but you must ensure that a ``` * **Check data** - * Log in to a second node. + * To confirm the data was successfully replicated, log in to a second node. * Get a sum of the value column (for checking): ```sql select COUNT(*),SUM(value) from quicktest; From 9192290293faee5c15c4b0023c170bdffb234f80 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 6 Jun 2024 14:39:33 +0100 Subject: [PATCH 30/50] Update product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx --- .../docs/pgd/5/quickstart/further_explore_replication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx index 959fafe907f..23484aa097f 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -11,7 +11,7 @@ With the cluster up and running, it's worthwhile to run some basic checks to see The following example shows one quick way to do this, but you must ensure that any testing you perform is appropriate for your use case. * **Preparation** - * Ensure the cluster is ready: + * Ensure your cluster is ready to perform replication. If you have not installed a cluster yet, use one of the [quickstart](.) guides to get going: * Log in to the database on first host. * Run `select bdr.wait_slot_confirm_lsn(NULL, NULL);`. * When the query returns, the cluster is ready. From 21d5cbaceb984c17240fe8bfba705881d6dfe698 Mon Sep 17 00:00:00 2001 From: Frank Touserkani <94471063+ftouserkani-edb@users.noreply.github.com> Date: Thu, 6 Jun 2024 11:39:26 -0400 Subject: [PATCH 31/50] Update 02_vpc_peering.mdx Cluster VPC name needs to match in the example. --- .../02_connecting_from_aws/02_vpc_peering.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 f80ffd39c6b..c7e30779114 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 @@ -35,7 +35,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. - A Postgresql client, such as [psql](https://www.postgresql.org/download/), installed on your client VM. -You need to add two peering links: one from the client VPC `vpc-client` and the other from your cluster's VPC `vnet-japaneast`. +You need to add two peering links: one from the client VPC `vpc-client` and the other from your cluster's VPC `vpc-cluster`. ### VPC peering connection with a VPC in another AWS account From fa31a420c104ab18e2099727f48fc406c5de58a1 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 6 Jun 2024 15:32:00 -0400 Subject: [PATCH 32/50] Edits to Lasso release 4.16.0 #5733 --- product_docs/docs/lasso/4/describe.mdx | 36 +++++++++++++------------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/lasso/4/describe.mdx b/product_docs/docs/lasso/4/describe.mdx index bfe9b236273..29217445cfe 100644 --- a/product_docs/docs/lasso/4/describe.mdx +++ b/product_docs/docs/lasso/4/describe.mdx @@ -333,7 +333,7 @@ Dynamic linker configuration (overloads). **Depth:** Deep -**Security Impact:** Low — +**Security impact:** Low — No known security impact. ### Configured locale (`linux_locale`) @@ -349,7 +349,7 @@ Information about the system locale. **Depth:** Surface -**Security Impact:** Low — +**Security impact:** Low — No known security impact. ### Processor usage statistics (`linux_mpstat`) @@ -410,7 +410,7 @@ Information about the packages origins. **Depth:** Surface -**Security Impact:** *Low* — +**Security impact:** *Low* — No known security impact. ### PostgreSQL disk layout (`linux_postgresql_disk_layout`) @@ -443,7 +443,7 @@ No known security impact. ### OpenSSL version and configuration (`linux_ssl`) -Collects OpenSSL version, enabled engines, ciphers/configurations. +Collect OpenSSL version, enabled engines, and ciphers/configurations. **Report output:** @@ -456,7 +456,7 @@ Collects OpenSSL version, enabled engines, ciphers/configurations. **Depth:** Surface -**Security Impact:** Low — +**Security impact:** Low — No known security impact. ### System identification (`linux_system_identity`) @@ -1195,9 +1195,9 @@ List of database/role settings in the PostgreSQL node. **Security impact:** Low — No known security impact. -### EPAS resource group active use information (`postgresql_epas_edb_all_resource_groups`) +### EDB Postgres Advanced Server resource group active use information (`postgresql_epas_edb_all_resource_groups`) -Live view of the system at the moment of the collection showing how +Live view of the system at the moment of the collection, showing how many active backends are being constrained by the resource groups. **Report output:** @@ -1209,7 +1209,7 @@ many active backends are being constrained by the resource groups. **Security impact:** Low — No known security impact. -### EPAS user profile policies (`postgresql_epas_edb_profile`) +### EDB Postgres Advanced Server user profile policies (`postgresql_epas_edb_profile`) Contains user profiles and password policies. @@ -1222,9 +1222,9 @@ Contains user profiles and password policies. **Security impact:** Low — No known security impact. -### EPAS resource group information (`postgresql_epas_edb_resource_group`) +### EDB Postgres Advanced Server resource group information (`postgresql_epas_edb_resource_group`) -EPAS resource group names and limits. +EDB Postgres Advanced Server resource group names and limits. **Report output:** @@ -1622,7 +1622,7 @@ No known security impact. ### BDR get_decoding_worker_stat (`postgresql_db_decoding_worker_stats`) -Single Decoding Worker status. +Single decoding worker status. **Report output:** @@ -2308,7 +2308,7 @@ No known security impact. ### BDR wal_sender_stats (`postgresql_db_wal_sender_stats`) -WAL Sender processes status. +WAL sender processes status. **Report output:** @@ -2531,7 +2531,7 @@ Current EDB Postgres Advanced Server dblink information from `edb_dblink`. **Security impact:** Low — No known security impact. -### EPAS directories (`postgresql_epas_edb_dir`) +### EDB Postgres Advanced Server directories (`postgresql_epas_edb_dir`) Oracle-compatible directories used as destination for packages to read and write. @@ -2545,7 +2545,7 @@ and write. **Security Impact:** Low — No known security impact. -### EPAS security policies (`postgresql_epas_edb_policy`) +### EDB Postgres Advanced Server security policies (`postgresql_epas_edb_policy`) Contains the security policies (Oracle-style RLS). @@ -2558,7 +2558,7 @@ Contains the security policies (Oracle-style RLS). **Security impact:** Low — No known security impact. -### EPAS redaction policies per column (`postgresql_epas_edb_redaction_column`) +### EDB Postgres Advanced Server redaction policies per column (`postgresql_epas_edb_redaction_column`) Contains the redaction policies per column. @@ -2571,7 +2571,7 @@ Contains the redaction policies per column. **Security impact:** Low — No known security impact. -### EPAS redaction policies (`postgresql_epas_edb_redaction_policy`) +### EDB Postgres Advanced Server redaction policies (`postgresql_epas_edb_redaction_policy`) Contains the redaction policies of each table. @@ -2584,9 +2584,9 @@ Contains the redaction policies of each table. **Security impact:** Low — No known security impact. -### EPAS-extended pg_namespace view (`postgresql_epas_pg_namespace`) +### EDB Postgres Advanced Server extended pg_namespace view (`postgresql_epas_pg_namespace`) -EPAS has extended pg_namespace which provides additional information. +EDB Postgres Advanced Server has extended pg_namespace, which provides additional information. **Report output:** From cbfc93841babb7b6f4330c2df4c947d31ec55087 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 6 Jun 2024 15:47:36 -0400 Subject: [PATCH 33/50] More edits to lasso content --- product_docs/docs/lasso/4/describe.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/lasso/4/describe.mdx b/product_docs/docs/lasso/4/describe.mdx index 29217445cfe..7ca3286f272 100644 --- a/product_docs/docs/lasso/4/describe.mdx +++ b/product_docs/docs/lasso/4/describe.mdx @@ -270,7 +270,7 @@ downloads. Passwords are redacted. **Depth:** Surface -**Security Impact:** *Low* — +**Security impact:** *Low* — No known security impact. ### Hypervisor (`linux_hypervisor_collector`) @@ -1630,7 +1630,7 @@ Single decoding worker status. **Depth:** Surface -**Security Impact:** Low — +**Security impact:** Low — No known security impact. ### edb_wait_states database settings (`postgresql_db_edb_wait_states_database_settings`) @@ -2542,7 +2542,7 @@ and write. **Depth:** Surface -**Security Impact:** Low — +**Security impact:** Low — No known security impact. ### EDB Postgres Advanced Server security policies (`postgresql_epas_edb_policy`) From 8d770dbe23dec150d97cf555ead3ecca23f84e95 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 6 Jun 2024 20:11:38 +0000 Subject: [PATCH 34/50] DOCS-691: fix conversion of inline code --- tools/automation/actions/jira-sync/jira.js | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tools/automation/actions/jira-sync/jira.js b/tools/automation/actions/jira-sync/jira.js index 22ac9744681..2195b953052 100644 --- a/tools/automation/actions/jira-sync/jira.js +++ b/tools/automation/actions/jira-sync/jira.js @@ -288,7 +288,11 @@ function convertNodes(node, root, activeMarks = [], allowedTypes = allTypes) { html: NIblock, image: NI, imageReference: NI, - inlineCode: (node) => addMark("code"), + inlineCode: (node) => + map("text", { + marks: [{ type: "code" }, ...activeMarks], + text: node.value, + }), link: (node) => addMark("link", { href: node.url, title: node.title || undefined }), linkReference: (node) => typeConverter["link"](makeLinkForReference(node)), From caabb3584f0a7e0fc1d5f0229f4c95ad8a375e3c Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Fri, 7 Jun 2024 12:33:30 +0530 Subject: [PATCH 35/50] JDBC connector - 42.2.19.1 release notes Fixed a note in the release notes of version 42.2.19.1 as per [EC-3089](https://enterprisedb.atlassian.net/browse/EC-3089) --- .../42.5.4.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx index f95747e3d97..ae8ba1ac472 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx @@ -15,4 +15,4 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect | Enhancement | EDB JDBC Connector now supports GSSAPI encrypted connection. See [Support for GSSAPI Encrypted Connection](../09_security_and_encryption/03_support_for_gssapi_encrypted_connection). | !!! Note - EDB JDBC Connector v42.2.19.1 does not support Java 1.6 and 1.7. Previous versions of EDB JDBC Connector continue to support Java 1.6 and 1.7. + EDB JDBC Connector v42.2.19.1 does not support Java 1.6 and 1.7. Previous versions of EDB JDBC Connector support Java 1.6 and 1.7 but will not get any future updates, enhancements or bug fixes. From 764143cd62b3c8c4015147604b0fa4ce2f645ec2 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 7 Jun 2024 08:11:09 +0100 Subject: [PATCH 36/50] Apply suggestions from code review Co-authored-by: Betsy Gitelman --- .../further_explore_replication.mdx | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx index 23484aa097f..892d8dccd48 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -11,13 +11,13 @@ With the cluster up and running, it's worthwhile to run some basic checks to see The following example shows one quick way to do this, but you must ensure that any testing you perform is appropriate for your use case. * **Preparation** - * Ensure your cluster is ready to perform replication. If you have not installed a cluster yet, use one of the [quickstart](.) guides to get going: - * Log in to the database on first host. + * Ensure your cluster is ready to perform replication. If you haven't installed a cluster yet, use one of the [quick start](.) guides to get going: + * Log in to the database on the first host. * Run `select bdr.wait_slot_confirm_lsn(NULL, NULL);`. * When the query returns, the cluster is ready. * **Create data** - The simplest way to test that the cluster is replicating is to log in to a node, create a table, populate it, and see the data you populated appear on a second node. On the first node, + The simplest way to test that the cluster is replicating is to log in to a node, create a table, populate it, and see the data you populated appear on a second node. On the first node: * Create a table: ```sql CREATE TABLE quicktest ( id SERIAL PRIMARY KEY, value INT ); @@ -42,9 +42,9 @@ The following example shows one quick way to do this, but you must ensure that a ```sql select COUNT(*),SUM(value) from quicktest; ``` - * Compare with the result from first node. + * Compare with the result from the first node. * Log in to a third node. - * get a sum of the value column (for checking): + * Get a sum of the value column (for checking): ```sql select COUNT(*),SUM(value) from quicktest; ``` @@ -54,7 +54,7 @@ The following example shows one quick way to do this, but you must ensure that a ### Preparation -Our cluster has three data nodes, kaboom, kaftan and kaolin. We will use kaboom as our first node. Log in to kaboom and then into kaboom's Postgres server. +The cluster in this example has three data nodes: kaboom, kaftan, and kaolin. The example uses kaboom as the first node. Log in to kaboom and then into kaboom's Postgres server: ``` cd democluster @@ -116,7 +116,7 @@ __OUTPUT__ The command shows statistics about how quickly that data was replicated to the other two nodes: -Note that the replay_lag values are 0, showing no lag, and the LSN values are in sync, meaning the data is already replicated. +The `replay_lag` values are 0, showing no lag, and the LSN values are in sync, meaning the data is already replicated. #### On kaboom get a checksum @@ -137,11 +137,11 @@ __OUTPUT__ (1 row) ``` -Your sum will be different because the values in the table are random numbers, but the count should be 100000. +Your sum will be different because the values in the table are random numbers, but the count will be 100000. ### Check data -Our second host will be "kaftan". In another window (or session), log in to kaftan's Postgres server: +The second host is kaftan. In another window or session, log in to kaftan's Postgres server: ``` cd democluster @@ -157,7 +157,7 @@ Run: select COUNT(*),SUM(value) from quicktest; ``` -This command gets node-two's values for the generated data: +This command gets the second node's values for the generated data: ```sql bdrdb=# select COUNT(*),SUM(value) from quicktest; @@ -176,7 +176,7 @@ You can repeat the process with the third node (kaolin), or generate new data on #### Log in to the third node (kaolin) -The last node is kaolin, our third node. In another window(or session), log in to the kaolin and then into kaolin's Postgres server: +The third and last node is kaolin. In another window or session, log in to kaolin and then into kaolin's Postgres server: ``` cd democluster @@ -205,7 +205,7 @@ __OUTPUT__ #### Compare the results. -Compare the the result from the first and second nodes (kaboom and kaftan) with the result from kaolin. The values will be identical on all three nodes. +Compare the result from the first and second nodes (kaboom and kaftan) with the result from kaolin. The values will be identical on all three nodes. ## Next steps From 29c52e37e964fe14ad7b051961a14f0826b670a6 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 7 Jun 2024 08:14:20 +0100 Subject: [PATCH 37/50] Other review changes further_explore_replication.mdx More reorg --- .../quickstart/further_explore_replication.mdx | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx index 892d8dccd48..074c8d02566 100644 --- a/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -6,17 +6,17 @@ deepToC: true ## Explore replication with PGD -With the cluster up and running, it's worthwhile to run some basic checks to see how effectively it's replicating. +With the cluster up and running, it's useful to run some basic checks to see how effectively it's replicating. The following example shows one quick way to do this, but you must ensure that any testing you perform is appropriate for your use case. -* **Preparation** +### Preparation * Ensure your cluster is ready to perform replication. If you haven't installed a cluster yet, use one of the [quick start](.) guides to get going: * Log in to the database on the first host. * Run `select bdr.wait_slot_confirm_lsn(NULL, NULL);`. * When the query returns, the cluster is ready. -* **Create data** +### Create data The simplest way to test that the cluster is replicating is to log in to a node, create a table, populate it, and see the data you populated appear on a second node. On the first node: * Create a table: ```sql @@ -36,7 +36,7 @@ The following example shows one quick way to do this, but you must ensure that a select COUNT(*),SUM(value) from quicktest; ``` -* **Check data** +### Check data * To confirm the data was successfully replicated, log in to a second node. * Get a sum of the value column (for checking): ```sql @@ -91,17 +91,17 @@ CREATE TABLE #### On kaboom, populate the table +This command generates a table of 10000 rows of random values. + ``` INSERT INTO quicktest (value) SELECT random()*10000 FROM generate_series(1,10000); __OUTPUT__ INSERT 0 10000 ``` -This command generates a table of 10000 rows of random values. - #### On kaboom, monitor performance -As soon as possible, run: +As soon as possible, run the following command. It will shows statistics about how quickly that data was replicated to the other two nodes. ```sql select * from bdr.node_replication_rates; @@ -113,9 +113,6 @@ __OUTPUT__ (2 rows) ``` -The command shows statistics about how quickly that data was replicated to the other two nodes: - - The `replay_lag` values are 0, showing no lag, and the LSN values are in sync, meaning the data is already replicated. #### On kaboom get a checksum From 51c6f3786118a0ae55110655ab9d8872809371bd Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Fri, 7 Jun 2024 09:26:41 +0100 Subject: [PATCH 38/50] Added complete tested instructions for Slack example --- .../monitoring_performance/notifications.mdx | 34 ++++++++++--------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 00316880311..c9892f4c5c0 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -73,7 +73,7 @@ The **Webhooks** tab displays a list of the currently defined recipient applicat To define a new webhook, select the plus sign (+) in the upper-right corner of the table. You can then use the **General** tab to define the basic details of the webhook: - Provide a name for the webhook in the **Name** field. -- Specify a webhook URL to delever all the notifications to in the **URL** field. +- Specify a webhook URL to deliver all the notifications to in the **URL** field. - Set the request method type used to make the call in the **Request Method** field: **POST** or **PUT**. - By default, webhooks are enabled. To disable a webhook, set **Enable?** to **No**. @@ -141,28 +141,30 @@ Use the **Notifications** tab to specify an alert level for webhook endpoints: - Set **All alerts** to **Yes** to enable all alert levels to send notifications. - To send a notification when a specific alert level is reached, set the slider next to an alert level to **Yes**. You must set **All alerts** to **No** to configure an individual alert level. -### Example of configuring a webhook using Slack +### Example: sending notifications to Slack -Slack provides a way to post messages via `Incoming Webhooks`. To send an alert from PEM to Slack, users must create an `Incoming Webook`. Refer to Slack's guide [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks). The `Incoming Webhook` gives a unique URL to which the PEM Agent can send a JSON payload with the message text and other options to Slack webhooks. +In Slack, follow the instructions in [Getting started with incoming webhooks](https://api.slack.com/messaging/webhooks) to: +- Create a Slack app +- Activate incoming webhooks for that app +- Add a webhook that posts to a channel or user of your choice -Here are the steps to configure a Slack `Incoming Webhook` using PEM: +The newly created webhook will have a unique URL something like https://hooks.slack.com/services/x/y/z we can now configure PEM to send notifications to this URL. -- Configure the Slack application, if it's not already configured. -- Activate `Incoming Webhooks` from Slack. -- Add new webhooks to the Slack workspace. You must add the channel and authorize the application for the incoming webhooks so the PEM Agent can notify the alert using Slack. -- Get the unique URL used in PEM to configure the webhook configurations. You can configure PEM to send notifications (low, medium, high) to Slack via a POST request. -- The PEM Agent uses the URL to send alert notifications from PEM to Slack using an HTTP POST request, as configured in the webhook. +In PEM, [create a new webhook](#creating-a-webhook), give it a descriptive name and copy the URL you obtained above to the 'URL' field. +Ensure that 'Request method' is set to 'POST' and 'Enable?' is set to 'Yes'. Set all the sliders under 'Alert Notifications' to 'Yes'. -Here is an example of a POST request from the PEM Agent: +Under HTTP headers, add a header with the key `Content-Type` and the value `application/json`. -```shell -POST https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXX/ -Content-type: application/json -{ - "text": "Alert from PEM: [%AlertID%], [%AlertName%]" -} +Under Payload, delete the default template and specify a template with `text` as the top-level key as in the example below. + +``` +{"text": "%AlertName% on %ObjectType% %ObjectName% is now %CurrentState%"} ``` +You can now test the connection. If it succeeds, you will get a notification in PEM and the template above will appear in your Slack channel as a message. + +Save the webhook and continue using PEM as normal. All alerts will now be sent to your Slack channel! + ### Deleting a webhook To mark a webhook for deletion, in the Webhooks table, select the webhook name and select **Delete** to the left of the name. The alert remains in the list but in strike-through font. From e4a481156305ee9cf46cbd4d662519fea8cfea96 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 30 May 2024 12:06:05 +0100 Subject: [PATCH 39/50] Fix links and arrange glossary Signed-off-by: Dj Walker-Morgan --- .../pgbackrest/10-non-superuser.mdx | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx diff --git a/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx b/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx new file mode 100644 index 00000000000..7a3888771f4 --- /dev/null +++ b/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx @@ -0,0 +1,35 @@ +--- +title: 'Non-superuser support with pgBackRest' +description: "How to configure a non-superuser as the pgBackRest user" +--- + +pgBackRest supports non-superuser backups and restores. This feature is useful when you want to delegate backup and restore tasks to non-superusers. To configure non-superuser support, you need to grant the necessary permissions to the non-superuser. + +For example, to allow the `pgbackrest` user to perform backups and restores, you can grant the following permissions: + +```sql +grant pg_read_all_settings to pgbackrest ; +``` + +For EDB Postgres Advanced Server 14 and later: + +```sql +GRANT EXECUTE on FUNCTION pg_switch_wal to pgbackrest; +GRANT EXECUTE ON FUNCTION pg_start_backup(text, boolean, boolean) to pgbackrest; +GRANT EXECUTE ON FUNCTION pg_stop_backup(boolean, boolean) TO pgbackrest; +GRANT EXECUTE ON FUNCTION pg_catalog.pg_create_restore_point(text) TO pgbackrest; +``` + +For EDB Postgres 15 and earlier: + +In EDB Postgres 15 onwards, `pg_start_backup` and `pg_stop_backup` functions are changed to `pg_backup_start` and `pg_backup_stop`. + +```sql + +GRANT EXECUTE on FUNCTION pg_switch_wal to pgbackrest ; +GRANT EXECUTE ON FUNCTION pg_backup_start(label text, fast boolean) TO pgbackrest; +GRANT EXECUTE ON FUNCTION pg_backup_stop(wait_for_archive boolean) TO pgbackrest; +GRANT EXECUTE ON FUNCTION pg_catalog.pg_create_restore_point(text) TO pgbackrest; +``` + + From c259d5362039b0769b556e02070ff085fd00bd24 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 30 May 2024 12:07:05 +0100 Subject: [PATCH 40/50] Fix links and arrange glossary Signed-off-by: Dj Walker-Morgan --- .../pgbackrest/04-recommended_settings.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/advocacy_docs/supported-open-source/pgbackrest/04-recommended_settings.mdx b/advocacy_docs/supported-open-source/pgbackrest/04-recommended_settings.mdx index d6b98303ced..e2886a03c90 100644 --- a/advocacy_docs/supported-open-source/pgbackrest/04-recommended_settings.mdx +++ b/advocacy_docs/supported-open-source/pgbackrest/04-recommended_settings.mdx @@ -98,12 +98,12 @@ The `page-header-check` option has been introduced in the [2.46](https://github. #### pgBackRest -[`archive-header-check`](https://pgbackrest.org/configuration.html#section-archive/option-archive-header-check) -[`checksum-page`](https://pgbackrest.org/configuration.html#section-backup/option-checksum-page) -[`delta`](https://pgbackrest.org/configuration.html#section-general/option-delta) -[`log-level-console`](https://pgbackrest.org/configuration.html#section-log/option-log-level-console) -[`log-level-file`](https://pgbackrest.org/configuration.html#section-log/option-log-level-file) -[`page-header-check`](https://pgbackrest.org/configuration.html#section-backup/option-page-header-check) -[`process-max`](https://pgbackrest.org/configuration.html#section-general/option-process-max) -[`repo-cipher-pass`](https://pgbackrest.org/configuration.html#section-repository/option-repo-cipher-pass) -[`repo-cipher-type`](https://pgbackrest.org/configuration.html#section-repository/option-repo-cipher-type) +* [`archive-header-check`](https://pgbackrest.org/configuration.html#section-maintainer/option-archive-header-check) +* [`checksum-page`](https://pgbackrest.org/configuration.html#section-backup/option-checksum-page) +* [`delta`](https://pgbackrest.org/configuration.html#section-general/option-delta) +* [`log-level-console`](https://pgbackrest.org/configuration.html#section-log/option-log-level-console) +* [`log-level-file`](https://pgbackrest.org/configuration.html#section-log/option-log-level-file) +* [`page-header-check`](https://pgbackrest.org/configuration.html#section-maintainer/option-page-header-check) +* [`process-max`](https://pgbackrest.org/configuration.html#section-general/option-process-max) +* [`repo-cipher-pass`](https://pgbackrest.org/configuration.html#section-repository/option-repo-cipher-pass) +* [`repo-cipher-type`](https://pgbackrest.org/configuration.html#section-repository/option-repo-cipher-type) From c9a805e2bf723a3b82c91ba2a1cdab0cd04be4ab Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 6 Jun 2024 16:37:39 -0400 Subject: [PATCH 41/50] Edits to Tidy up roles pages #5657 --- .../docs/pgd/5/security/pgd-predefined-roles.mdx | 10 ++++------ product_docs/docs/pgd/5/security/roles.mdx | 10 ++++------ 2 files changed, 8 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx index a54e64e97e8..f27513c4016 100644 --- a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx +++ b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx @@ -18,7 +18,7 @@ This is a role for an admin user that can manage anything PGD related. It allows ### bdr_read_all_stats -This role provides read access to most of the tables, views and functions that may be needed by users or applications which wish to observe the statistics and state of the PGD cluster. +This role provides read access to most of the tables, views, and functions that users or applications need to observe the statistics and state of the PGD cluster. #### Privileges @@ -92,7 +92,7 @@ EXECUTE privilege on: ### bdr_monitor -This role provides read access to any tables, views and functions that may be needed by users or applications which monitor the PGD cluster. It includes all the privileges of the [`bdr_read_all_stats`](#bdr_read_all_stats) role. +This role provides read access to any tables, views, and functions that users or applications need to monitor the PGD cluster. It includes all the privileges of the [`bdr_read_all_stats`](#bdr_read_all_stats) role. #### Privileges @@ -106,7 +106,7 @@ All privileges from [`bdr_read_all_stats`](#bdr_read_all_stats) plus the followi - [`bdr.group_versions_details`](/pgd/latest/reference/catalogs-visible#bdrgroup_versions_details) - `bdr.raft_instances` -Also, EXECUTE privilege on: +`EXECUTE` privilege on: - `bdr.get_raft_instance_by_nodegroup` - `bdr.monitor_camo_on_all_nodes` @@ -122,7 +122,7 @@ Also, EXECUTE privilege on: ### bdr_application -This role is designed for applications which require access to PGD features, objects and functions such as sequences, CRDT datatypes, CAMO status functions or trigger management functions. +This role is designed for applications that require access to PGD features, objects, and functions such as sequences, CRDT datatypes, CAMO status functions, or trigger management functions. #### Privileges @@ -170,5 +170,3 @@ you can optionally grant the role `bdr_read_all_conflicts` to that user. #### Privileges An explicit policy is set on [`bdr.conflict_history`](/pgd/latest/reference/catalogs-visible#bdrconflict_history) that allows this role to read the `bdr.conflict_history` table. - - diff --git a/product_docs/docs/pgd/5/security/roles.mdx b/product_docs/docs/pgd/5/security/roles.mdx index f3f60b2da45..b387a5dd67d 100644 --- a/product_docs/docs/pgd/5/security/roles.mdx +++ b/product_docs/docs/pgd/5/security/roles.mdx @@ -3,8 +3,8 @@ title: Roles --- Configuring and managing PGD doesn't require superuser access. We recommend that -you do not use superuser access. Instead, the privileges required to administer -PGD are split across the following predefined roles: +you don't use superuser access. Instead, the privileges required to administer +PGD are split across the following predefined roles. | Role | Description | |----------------------------|------------------------------------------------------------------------------------------------------------------| @@ -15,11 +15,11 @@ PGD are split across the following predefined roles: | [**bdr_read_all_conflicts**](pgd-predefined-roles/#bdr_read_all_conflicts) | Can view all conflicts in [`bdr.conflict_history`](/pgd/latest/reference/catalogs-visible#bdrconflict_history). | -These roles are named to be analagous to to PostgreSQL's `pg_` [predefined +These roles are named to be analogous to PostgreSQL's `pg_` [predefined roles](https://www.postgresql.org/docs/current/predefined-roles.html): The PGD `bdr_` roles are created when the BDR extension is installed. See [PGD -predefined roles](pgd-predefined-roles) for more details of what priviliges each +predefined roles](pgd-predefined-roles) for more details of the privileges each one has. Managing PGD doesn't require that administrators have access to user data. @@ -35,5 +35,3 @@ management of PGD's underlying BDR extension. Only superusers can create the BDR extension. However, if you want, you can set up the `pgextwlist` extension and configure it to allow a non-superuser to create a BDR extension. !!! - - From 8cebabb7c4221981251ccee71eceadbbdbf7b475 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 6 Jun 2024 16:40:25 -0400 Subject: [PATCH 42/50] Update product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx --- product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx index f27513c4016..88e9f767947 100644 --- a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx +++ b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx @@ -92,7 +92,7 @@ EXECUTE privilege on: ### bdr_monitor -This role provides read access to any tables, views, and functions that users or applications need to monitor the PGD cluster. It includes all the privileges of the [`bdr_read_all_stats`](#bdr_read_all_stats) role. +This role provides read access to any tables, views, and functions that users or applications may need to monitor the PGD cluster. It includes all the privileges of the [`bdr_read_all_stats`](#bdr_read_all_stats) role. #### Privileges From c12e0466d460db53e8c8f933ac280f36325f044e Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 6 Jun 2024 16:40:35 -0400 Subject: [PATCH 43/50] Update product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx --- product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx index 88e9f767947..4e392e700fe 100644 --- a/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx +++ b/product_docs/docs/pgd/5/security/pgd-predefined-roles.mdx @@ -18,7 +18,7 @@ This is a role for an admin user that can manage anything PGD related. It allows ### bdr_read_all_stats -This role provides read access to most of the tables, views, and functions that users or applications need to observe the statistics and state of the PGD cluster. +This role provides read access to most of the tables, views, and functions that users or applications may need to observe the statistics and state of the PGD cluster. #### Privileges From dd7e927293731c6333d141f08257c809a5f2f798 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 7 Jun 2024 14:54:09 +0200 Subject: [PATCH 44/50] changed "earlier" to "later" --- .../supported-open-source/pgbackrest/10-non-superuser.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx b/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx index 7a3888771f4..88a0fe39597 100644 --- a/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx +++ b/advocacy_docs/supported-open-source/pgbackrest/10-non-superuser.mdx @@ -20,9 +20,9 @@ GRANT EXECUTE ON FUNCTION pg_stop_backup(boolean, boolean) TO pgbackrest; GRANT EXECUTE ON FUNCTION pg_catalog.pg_create_restore_point(text) TO pgbackrest; ``` -For EDB Postgres 15 and earlier: +For EDB Postgres 15 and later: -In EDB Postgres 15 onwards, `pg_start_backup` and `pg_stop_backup` functions are changed to `pg_backup_start` and `pg_backup_stop`. +In EDB Postgres 15 and later versions, `pg_start_backup` and `pg_stop_backup` functions are changed to `pg_backup_start` and `pg_backup_stop`. ```sql From f8bdc6431b69d599dfb666702b35556e87b59a15 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Mon, 10 Jun 2024 09:14:32 +0100 Subject: [PATCH 45/50] Apply suggestions from code review Co-authored-by: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> --- .../docs/pem/9/monitoring_performance/notifications.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index c9892f4c5c0..9274285f3f8 100644 --- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx +++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx @@ -148,12 +148,12 @@ In Slack, follow the instructions in [Getting started with incoming webhooks](ht - Activate incoming webhooks for that app - Add a webhook that posts to a channel or user of your choice -The newly created webhook will have a unique URL something like https://hooks.slack.com/services/x/y/z we can now configure PEM to send notifications to this URL. +The newly created webhook will have a unique URL something like https://hooks.slack.com/services/x/y/z . We can now configure PEM to send notifications to this URL. In PEM, [create a new webhook](#creating-a-webhook), give it a descriptive name and copy the URL you obtained above to the 'URL' field. Ensure that 'Request method' is set to 'POST' and 'Enable?' is set to 'Yes'. Set all the sliders under 'Alert Notifications' to 'Yes'. -Under HTTP headers, add a header with the key `Content-Type` and the value `application/json`. +Add a header under HTTP headers with the key `Content-Type` and the value `application/json`. Under Payload, delete the default template and specify a template with `text` as the top-level key as in the example below. @@ -161,9 +161,9 @@ Under Payload, delete the default template and specify a template with `text` as {"text": "%AlertName% on %ObjectType% %ObjectName% is now %CurrentState%"} ``` -You can now test the connection. If it succeeds, you will get a notification in PEM and the template above will appear in your Slack channel as a message. +You can now test the connection. If it succeeds, you will get a notification in PEM, and the template above will appear in your Slack channel as a message. -Save the webhook and continue using PEM as normal. All alerts will now be sent to your Slack channel! +Save the webhook and continue using PEM as usual. Now, PEM will send all the alerts to your Slack channel. ### Deleting a webhook From 61c6b1591166fe9fc9e4cbf784561ebc44554045 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 10 Jun 2024 11:09:49 -0400 Subject: [PATCH 46/50] Advocacy docs/edb postgres ai/console/estate - docs-596 (#5732) * Small tense change. * Started new file. * Additional steps. * Finish first draft. * Small change. * Small change. * Change some wording. * Change subtitle. * Added admonition regarding snippet in the wizard vs snippet in docs. * Fix on monitor_aws.mdx tagged the HTML element out as code * Fixed numbering. * Fixed a typo. * Small changes. * fixed formatting for project-id * Small change. * Small word change. * Word change. * Small word changes. * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Small change. * Log in to Go * Incorporated feedback keeping the UI's clear. * More alignment with review suggestions. * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Fixed some indentation. * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx Co-authored-by: gvasquezvargas --------- Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Co-authored-by: gvasquezvargas --- .../edb-postgres-ai/console/agent/index.mdx | 2 +- .../console/{estate.mdx => estate/index.mdx} | 0 .../console/estate/monitor_aws.mdx | 121 ++++++++++++++++++ 3 files changed, 122 insertions(+), 1 deletion(-) rename advocacy_docs/edb-postgres-ai/console/{estate.mdx => estate/index.mdx} (100%) create mode 100644 advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx diff --git a/advocacy_docs/edb-postgres-ai/console/agent/index.mdx b/advocacy_docs/edb-postgres-ai/console/agent/index.mdx index 07648d0197b..92515b37ca2 100644 --- a/advocacy_docs/edb-postgres-ai/console/agent/index.mdx +++ b/advocacy_docs/edb-postgres-ai/console/agent/index.mdx @@ -12,7 +12,7 @@ navigation: To monitor your self-managed Postgres database with Beacon Agent, you will need to: -* [Create a machine user](create-machine-user) in the EDB Postgres® AI Console. This will provide an access key for the agent. +* [Create a machine user](create-machine-user) in the EDB Postgres® AI Console. This provides an access key for the agent. * [Install Beacon Agent](install-agent) on the server where your Postgres instance is running. You will use the access key to enable the agent to communicate with the EDB Postgres AI Estate service. * [Run Beacon Agent as a service](agent-as-a-service) to have it start automatically on system startup and restart after errors. diff --git a/advocacy_docs/edb-postgres-ai/console/estate.mdx b/advocacy_docs/edb-postgres-ai/console/estate/index.mdx similarity index 100% rename from advocacy_docs/edb-postgres-ai/console/estate.mdx rename to advocacy_docs/edb-postgres-ai/console/estate/index.mdx diff --git a/advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx b/advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx new file mode 100644 index 00000000000..b5b360e0976 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/console/estate/monitor_aws.mdx @@ -0,0 +1,121 @@ +--- +title: Monitoring AWS resources in EDB Postgres AI +navTitle: Cloud Hosted Databases - AWS resources +description: How to monitor AWS resources in EDB Postgres AI Estate. +deepToC: true +--- + +## Overview + +Setting up the EDB Postgres® AI Console to monitor your RDS instances and S3 buckets on AWS involves adding a specific policiy and role in AWS. Once these are configured, you need to enter the role ARN of the newly created role into the **Cloud Hosted Databases** UI, accessible via the **Estate** page in the EDB Postgres AI Console. + +Using this role ARN and a custom policy, the EDB Postgres AI server will have access to the RDS and S3 information in your AWS account. + +After providing the role ARN in the Cloud Hosted Databases UI, you will see the selected AWS resources (RDS instances and/or S3 buckets) in the chosen AWS regions on your **Estate** page in the **Cloud Hosted Databases** section. + +## Setting up monitoring of AWS resources in EDB Postgres AI Estate + +### Starting the Cloud Hosted Databases UI + +1. Go to **EDB Postgres AI Console**. + +2. Scroll down to the **Cloud Hosted Databases** section, select the **Manage Access** button, and choose your project. + +3. The **Cloud Hosted Databases** UI shows **Step 1 - Create custom policy**. + +### Creating the AWS custom policy + +4. Go to the console of your AWS account with the RDS instances and S3 buckets you want to monitor. + +5. Navigate to IAM, and in the navigation pane on the left side of the AWS console, select **Policies**. + +6. On the **Policies** dashboard page, select the **Create policy** button. + +7. In the **Policy editor** section, choose the JSON option. + +8. Type or paste the following JSON policy document into the JSON editor: + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Sid": "VisualEditor0", + "Effect": "Allow", + "Action": [ + "rds:DescribeDBInstances", + "s3:ListAllMyBuckets", + "rds:DescribeDBClusters" + ], + "Resource": "*" + } + ] + } + ``` + +9. Select **Next**, give the policy a name, for example, `edb-postgres-ai-addon-policy` and select **Create Policy**. This policy allows EDB Postgres AI server to query metadata of your AWS RDS and S3 services. + + +### Creating the AWS role + +10. Next, in the Cloud Hosted Databases UI, select the **Next: Create a Role** button. The Cloud Hosted Databases UI should now show **Step 2 - Create a Role**. + +11. Go to the AWS console UI, and in the left-hand navigation pane, choose **Roles** and then select the **Create role** button. + +12. Select **Custom trust policy** role type. + +13. In the **Custom trust policy** section, paste the trust policy you obtained from **Step 2** in the Cloud Hosted Databases UI. It looks similar to this: + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "AWS": "arn:aws:iam::292478331082:root" + }, + "Action": "sts:AssumeRole", + "Condition": { + "StringEquals": { + "sts:ExternalId": "" + } + } + } + ] + } + ``` + + !!! Note + The EDB Postgres AI Cloud Hosted Databases UI shows a snippet like the one above but with the `` already specified. + !!! + +14. Select the **Next** button. + +15. Select the policy you created earlier. In this example, we used `edb-postgres-ai-addon-policy`. + +16. Select the **Next** button. + +17. Give the role a name. Note that you must give the role a name that starts with `biganimal-role`, such as `biganimal-role-beacon`. + +18. Select the **Create role** button. + +### Entering the role ARN into the EDB Postgres AI UI + +19. Still in the AWS console, select the **View role** button in the green banner at the top of the **Roles** dashboard in the AWS console. + +20. Copy the role ARN from the Summary section of the Role page in AWS console and paste it into the form at the bottom of the Cloud Hosted Databases UI labeled **Role ARN**. + +21. Select the **Next: Regions and Services** button in the Cloud Hosted Databases UI to move to the next step. + +### Selecting the scope of regions and services + +22. For **Step 3 - Regions and Services**, select the regions that you want to monitor and the services you want to monitor in those regions. + +23. Select the **Next: Review and submit** button. + +24. Review your regions and services selections, then select the **Submit** button. If you notice a mistake, you can always use the **Prev: Regions and Services** button and go back a step. + +25. Upon success, you will see a notification at the top of the Estate page saying, "The configuration has been submitted successfully." + +26. Within a moment, you should start to see the **Cloud Hosted Databases** section of your **Estate** page populate with the available S3 buckets and RDS instances. From 4d0fe511ceb2ca1f466cd4812af682ad920da863 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 10 Jun 2024 11:34:03 -0400 Subject: [PATCH 47/50] Add how-to of happy path for Lakehouse sync DOCS-604 (#5740) * First draft with happy path complete. * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> * Small spacing issue. * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: gvasquezvargas * Update advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> * Typo * Add trademark. * Change some wording in alignment with review feedback. * Fixing in line with review suggestions. Added screenshot of MSLs. * remove extraneous trademark. * Add admonition about infrastructure provisioning. --------- Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Co-authored-by: gvasquezvargas --- .../analytics/how_to_lakehouse_sync.mdx | 56 +++++++++++++++++++ .../analytics/images/msl_list.png | 3 + 2 files changed, 59 insertions(+) create mode 100644 advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx create mode 100644 advocacy_docs/edb-postgres-ai/analytics/images/msl_list.png diff --git a/advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx b/advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx new file mode 100644 index 00000000000..84ac90bf56e --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx @@ -0,0 +1,56 @@ +--- +title: Lakehouse Sync +navTitle: Lakehouse Sync +description: How to perform a Lakehouse Sync. +deepToC: true +--- + +## Overview + +Performing a Lakehouse Sync is a way to capture information from a transactional database at a point in time and sync that information to a Managed Store Location (MSL). + +The Lakehouse sync process organizes the transactional database data into Lakehouse tables stored in the MSL. This process allows the data to be queried by a Lakehouse node, which is optimized for higher-performance queries using a vectorized query engine designed for Lakehouse tables. + +## Performing a Lakehouse Sync + +### Prerequisites + +- a Postgres cluster hosted and managed by EDB Postgres AI® Cloud Service + +### Navigate to Lakehouse Sync + +1. Go to the [EDB Postgres AI Console](). + +2. From the landing page, select the project with the database instance you want to sync. If it is not shown on the landing page, select the **View Projects** link in the **Projects** section and select your project from there. + +3. Select the **Migrate** dropdown in the left navigation bar and then select **Migrations**. + +4. Select the **Create New Migration** button. + +### Define Lakehouse Sync + +5. Give the sync a **Name**, then select a **Source Cluster** and the **Database** you want to sync. + +6. If you have already created an MSL you want to use, select that MSL from the list of available MSLs and move on to [Selecting Tables](#selecting-tables) below. If not, select the **Create New Managed Storage Location** button to open the **Add Managed Storage Location** dialog. + +7. Select the AWS region for the new MSL. + +8. Set a location prefix in the form near the bottom of the **Add Managed Storage Location** dialog to complete the definition of the MSL. A location prefix is a unique name used to identify any resources and assets associated with the MSL. + +![List of MSLs](./images/msl_list.png) + +9. Select the **Create Managed Storage Location** button. + +### Selecting Tables + +10. Select the **Tables** tab next to the **Get Started** tab near the top of the page and select which tables and columns you wish to be included in the migration. + +### Start Lakehouse Sync + +11. Select the **Start Lakehouse Sync** button. + +12. If successful, you will see your Lakehouse sync with the 'Creating' status under 'MOST RECENT' migrations on the Migrations page. The time taken to perform a sync can depend upon how much data is being synchronized and may take several hours. + +!!! Warning +The first sync in a project will take a couple hours due to the provisioning of required infrastructure. +!!! \ No newline at end of file diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/msl_list.png b/advocacy_docs/edb-postgres-ai/analytics/images/msl_list.png new file mode 100644 index 00000000000..e78da2336c2 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/analytics/images/msl_list.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23879b9cdafff432ce39d8211f089e26b3be962bd4167330646e6dfd70944d6f +size 204050 From 2bcb5ba1fb4c6ca891d239b642b4af3690089ad5 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 10 Jun 2024 18:52:17 +0100 Subject: [PATCH 48/50] DOCS-734 edits Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 2 +- product_docs/docs/pgd/5/planning/deployments.mdx | 2 +- product_docs/docs/pgd/5/quickstart/index.mdx | 11 ++++++++--- 3 files changed, 10 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index d1147559b2f..183b53e02d9 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -76,7 +76,7 @@ The example uses the IP address because the configuration is from a Docker TPA i ### For a cluster deployed with EDB PGD for Kubernetes -As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple ways to obtain a connection string. It depends, in large part, on how the [services](/postgres_distributed_for_kubernetes/latest/connectivity/#services) were configured for the deployment: +As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple ways to obtain a connection string. It depends, in large part, on the configuration of the deployment's [services](/postgres_distributed_for_kubernetes/latest/connectivity/#services): - If you use the Node Service Template, direct connectivity to each node and proxy service is available. - If you use the Group Service Template, there's a gateway service to each group. diff --git a/product_docs/docs/pgd/5/planning/deployments.mdx b/product_docs/docs/pgd/5/planning/deployments.mdx index 17efb93254e..0726039d595 100644 --- a/product_docs/docs/pgd/5/planning/deployments.mdx +++ b/product_docs/docs/pgd/5/planning/deployments.mdx @@ -9,7 +9,7 @@ You can deploy and install EDB Postgres Distributed products using the following -- [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. TPA's flexibility allows deployments to virtual machines, AWS cloud instances or Linux host hardware. See [Deploying with TPA](../deploy-config/deploy-tpa/deploying/) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always-on clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by EDB's Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always-on clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information. - [EDB Postgres Distributed for Kubernetes](/postgres_distributed_for_kubernetes/latest/) is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 778b0f79325..ec1b8b71759 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,9 +20,13 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. -!!! Note Other deployment options - * If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/distributed_highavailability/). - * If you prefer to deploy PGD on Kubernetes, you can use the EDB PGD Operator for Kubernetes. Read more about [EDB PGD Operator for Kubernetes](/postgres_distributed_for_kubernetes/latest/quickstart). +### Other deployment options + +* If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/distributed_highavailability/). + +* If you prefer to deploy PGD on Kubernetes, you can use the EDB PGD Operator for Kubernetes. Read more about [EDB PGD Operator for Kubernetes](/postgres_distributed_for_kubernetes/latest/quickstart). + +### Whats in this quick start PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: @@ -33,6 +37,7 @@ PGD is very configurable. To quickly evaluate and deploy PGD, use this quick sta * The AWS quick start * Connecting applications to your cluster * Further explorations with your cluster including + * Replication * Conflicts * Failover From 2fbbd30fe49b286afbe25309cdfd4221c384db4b Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 10 Jun 2024 14:14:14 +0000 Subject: [PATCH 49/50] Update PDF logo --- scripts/pdf/cover.html | 124 ++++++++++++++++++++--------------------- 1 file changed, 59 insertions(+), 65 deletions(-) diff --git a/scripts/pdf/cover.html b/scripts/pdf/cover.html index 461ef3d10f8..c538450d9cf 100644 --- a/scripts/pdf/cover.html +++ b/scripts/pdf/cover.html @@ -1,67 +1,61 @@ - - - - - +
[PRODUCT]
+
Version [VERSION]
+ + + \ No newline at end of file From 638c18017022af7b57ed40d2b41b4da2417fe198 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 10 Jun 2024 19:34:10 +0100 Subject: [PATCH 50/50] Missed a postrephe Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index ec1b8b71759..28d2ebd0359 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -26,7 +26,7 @@ EDB Postgres Distributed (PGD) is a multi-master replicating implementation of P * If you prefer to deploy PGD on Kubernetes, you can use the EDB PGD Operator for Kubernetes. Read more about [EDB PGD Operator for Kubernetes](/postgres_distributed_for_kubernetes/latest/quickstart). -### Whats in this quick start +### What's in this quick start PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: