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 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. 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) 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..88a0fe39597 --- /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 later: + +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 + +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; +``` + + 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..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,3 +1,11 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% 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 + + 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 12656d73c50..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,3 +1,11 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "almalinux-9-or-rocky-linux-9" %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% 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 + + 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 e7bd911a54d..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,5 +1,9 @@ {% 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 %} {% block frontmatter %} {# @@ -17,38 +21,65 @@ redirects: {% endblock frontmatter %} -{% 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 %} +{% 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. - - To set up the EDB repository: +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 %} - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). +{% block product_prerequisites %} - 1. Select the button that provides access to the EDB repo. - - 1. Select the platform and software that you want to download. +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. - - To set up the PostgreSQL community repository, go to the [downloads page for PostgreSQL](https://www.postgresql.org/download/). + 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. - !!! Note +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. - The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. + 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 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, such as `host all superusername 127.0.0.1/32 scram-sha-256`. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). + !!! 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). + !!! -- Review [configuration and authentication requirements](../prerequisites/) for PEM. +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. + + ```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. + + ```shell + sudo {{packageManager}} install {{ssutilsExtendedFirstName}} {{ssutilsExtendedName}} + ``` + + {% 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: + + {% 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). + + ```shell + sudo {{packageManager}} {{upgradeCommand}} + ``` + {% endblock product_prerequisites %} {% block postinstall %} ## Initial configuration @@ -63,4 +94,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 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..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,9 +1,17 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "centos-7" %} +{% 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. - 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 5bc08e8f6b5..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 @@ -1,7 +1,17 @@ {% 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: `apt-cache search enterprisedb` {% 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 %} +{% 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 dbd8399aa1c..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 @@ -1,7 +1,16 @@ {% 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: `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 %} +{% 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 f7f097c678e..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 @@ -1,5 +1,8 @@ {% 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 %} @@ -7,3 +10,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 bfec7833e0d..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,9 +1,17 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} +{% 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. - 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 fa3995e8e8f..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,3 +1,11 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% 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 + + firewall-cmd --reload + ```{% endblock firewallCommand %} \ 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..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 +1,5 @@ + +{% 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 e57659be552..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,3 +1,11 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "rhel-9-or-ol-9" %} -{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file +{% 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 + + firewall-cmd --reload + ```{% endblock firewallCommand %} 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..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 +1,4 @@ {% extends "products/postgres-enterprise-manager-server/rhel-9-or-ol-9.njk" %} +{% 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 6ac27252c2d..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,5 +1,9 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set upgradeCommand = "update" %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} {% block introductory_notes %} !!! Note @@ -11,3 +15,10 @@ 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 %} +{% 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 37db62276f7..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,2 +1,7 @@ {% extends "products/postgres-enterprise-manager-server/sles-12.njk" %} {% set platformBaseTemplate = "sles-12" %} +{% set upgradeCommand = "update" %} +{% 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 cf71670d058..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,19 +1,31 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set upgradeCommand = "update" %} +{% 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 754a64c69fc..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,2 +1,6 @@ {% extends "products/postgres-enterprise-manager-server/sles-15.njk" %} {% set platformBaseTemplate = "sles-15" %} +{% set upgradeCommand = "update" %} +{% 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/ubuntu-20.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-20.04.njk index a9c715bd684..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 @@ -1,7 +1,17 @@ {% 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: `apt-cache search enterprisedb` {% endblock repocheck %} +{% 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 %} + 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..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 @@ -1,7 +1,17 @@ {% 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: `apt-cache search enterprisedb` {% endblock repocheck %} +{% 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 %} + 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 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. diff --git a/product_docs/docs/lasso/4/describe.mdx b/product_docs/docs/lasso/4/describe.mdx index bfe9b236273..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`) @@ -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:** @@ -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`) @@ -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. @@ -2542,10 +2542,10 @@ and write. **Depth:** Surface -**Security Impact:** Low — +**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:** 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -21,42 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/ppc64le - sudo SUSEConnect -p sle-sdk/12.5/ppc64le + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -76,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_15.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx index ba95246600f..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 @@ -21,47 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/ppc64le +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/ppc64le + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp - ``` + firewall-cmd --reload + ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -81,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_centos_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx index 122b9787359..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - Setting 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, such as `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..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 @@ -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 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. - Setting 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, such as `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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -21,42 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/x86_64 - sudo SUSEConnect -p sle-sdk/12.5/x86_64 + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -76,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_15.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx index 0a4e7d93301..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 @@ -21,47 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/x86_64 +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/x86_64 + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp - ``` + firewall-cmd --reload + ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -81,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_ubuntu_20.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx index 5c670254057..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 @@ -13,35 +13,70 @@ 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 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. - Setting 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, such as `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/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..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 @@ -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 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. - Setting 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, such as `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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -21,42 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/ppc64le - sudo SUSEConnect -p sle-sdk/12.5/ppc64le + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -76,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_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index d3e5f871a32..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 @@ -21,47 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/ppc64le +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/ppc64le + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp - ``` + firewall-cmd --reload + ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -81,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_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx index 5d43d0027cf..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - Setting 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, such as `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..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 @@ -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 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. - Setting 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, such as `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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -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 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. - `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, such as `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 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 + 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..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 @@ -21,42 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: - ```shell - sudo SUSEConnect -p PackageHub/12.5/x86_64 - sudo SUSEConnect -p sle-sdk/12.5/x86_64 + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -76,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_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index a48e898e967..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 @@ -21,47 +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 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. - 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, such as `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 + ``` -- Activate the required SUSE module: + - 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 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 + sudo zypper install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` - ```shell - # You can use SLES 15 SP3 for PEM 8.3 and later: - sudo SUSEConnect -p PackageHub/15.3/x86_64 +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: - # You can use SLES 15 SP4 for PEM 8.6 and later: - sudo SUSEConnect -p PackageHub/15.4/x86_64 + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp - ``` + firewall-cmd --reload + ``` -- Refresh the metadata: - ```shell - sudo zypper refresh - ``` +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 + ``` ## Install the package @@ -81,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_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index fa76f38198c..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 @@ -13,35 +13,70 @@ 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 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. - Setting 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, such as `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_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index de59993255f..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 @@ -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 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. - Setting 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, such as `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/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. diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx index 5a214fc7146..071ab90e6a8 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**. @@ -91,6 +91,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. @@ -99,6 +101,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. @@ -129,11 +133,37 @@ 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: sending notifications to Slack + +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 + +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'. + +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. + +``` +{"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 usual. Now, PEM will send all the alerts 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. 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/further_explore_replication.mdx b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx new file mode 100644 index 00000000000..074c8d02566 --- /dev/null +++ b/product_docs/docs/pgd/5/quickstart/further_explore_replication.mdx @@ -0,0 +1,208 @@ +--- +title: Exploring replication with PGD +navTitle: Exploring replication +deepToC: true +--- + +## Explore replication with PGD + +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 + * 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: + * 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 + * 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; + ``` + * Compare with the result from the 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 + +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 +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 + +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 +``` + +#### On kaboom, monitor performance + +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; +__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 `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 will be 100000. + +### Check data + +The second host is 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 the second node'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 third and last node is kaolin. In another window or session, log in to 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 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..28d2ebd0359 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 @@ -19,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). + +### 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: @@ -32,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 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 diff --git a/product_docs/docs/pgd/5/routing/readonly.mdx b/product_docs/docs/pgd/5/routing/readonly.mdx index 1245d1929e1..f62cd192224 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 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..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 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 may 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 may 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. !!! - - 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 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 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]; 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)),