-
Notifications
You must be signed in to change notification settings - Fork 248
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Generated file changes to support RHEL9 on ARM64 for PEM (agent and s…
…erver)
- Loading branch information
1 parent
1268b28
commit 4cb40fa
Showing
6 changed files
with
167 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
97 changes: 97 additions & 0 deletions
97
product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,97 @@ | ||
--- | ||
navTitle: RHEL 9 or OL 9 | ||
title: Installing Postgres Enterprise Manager server on RHEL 9 or OL 9 arm64 | ||
# This topic is generated from templates. If you have feedback on it, instead of | ||
# editing the page and creating a pull request, please enter a GitHub issue and | ||
# the documentation team will update the templates accordingly. | ||
|
||
redirects: | ||
- /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/arm64/pem_server_rhel9_arm | ||
- /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_rhel9_arm/ | ||
- /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_arm/ | ||
- /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_arm/ | ||
- /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_arm/ | ||
--- | ||
|
||
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: | ||
|
||
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](../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`. | ||
|
||
!!! 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 `<x>` is the EDB Postgres Advanced server version. | ||
|
||
```shell | ||
sudo dnf install edb-as<x>-server-sslutils | ||
``` | ||
|
||
- If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version. | ||
```shell | ||
sudo dnf install sslutils_<x> postgresql<x>-contrib | ||
``` | ||
- If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version. | ||
```shell | ||
sudo dnf install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib | ||
``` | ||
|
||
4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: | ||
|
||
```shell | ||
firewall-cmd --permanent --zone=public --add-port=8443/tcp | ||
|
||
firewall-cmd --reload | ||
``` | ||
|
||
5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. | ||
If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). | ||
|
||
```shell | ||
sudo dnf upgrade | ||
``` | ||
|
||
## Install the package | ||
|
||
```shell | ||
sudo dnf -y install edb-pem | ||
``` | ||
|
||
## Initial configuration | ||
|
||
```shell | ||
# You can configure the PEM server using the following command: | ||
sudo /usr/edb/pem/bin/configure-pem-server.sh | ||
``` | ||
|
||
For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/). | ||
|
||
!!! Note | ||
|
||
- The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. | ||
|
||
## 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
42 changes: 42 additions & 0 deletions
42
product_docs/docs/pem/9/installing_pem_agent/linux_arm64/pem_agent_rhel_9.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
navTitle: RHEL 9 or OL 9 | ||
title: Installing Postgres Enterprise Manager agent on RHEL 9 or OL 9 arm64 | ||
# This topic is generated from templates. If you have feedback on it, instead of | ||
# editing the page and creating a pull request, please enter a GitHub issue and | ||
# the documentation team will update the templates accordingly. | ||
|
||
redirects: | ||
- /pem/9/installing_pem_agent/installing_on_linux/arm64/pem_agent_rhel9_arm | ||
--- | ||
|
||
## Prerequisites | ||
|
||
Before you begin the installation process: | ||
|
||
- Set up the EDB repository. | ||
|
||
Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. | ||
|
||
To determine if your repository exists, enter this command: | ||
|
||
`dnf repolist | grep enterprisedb` | ||
|
||
If no output is generated, the repository isn't installed. | ||
|
||
To set up the EDB repository: | ||
|
||
1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). | ||
|
||
1. Select the button that provides access to the EDB repository. | ||
|
||
1. Select the platform and software that you want to download. | ||
|
||
1. Follow the instructions for setting up the EDB repository. | ||
|
||
## Install the package | ||
|
||
```shell | ||
sudo dnf -y install edb-pem-agent | ||
``` | ||
|
||
After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/). |