diff --git a/install_template/config.yaml b/install_template/config.yaml index a177b3e89b0..a4d3ad44d5c 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -575,3 +575,41 @@ products: - name: SLES 15 arch: ppc64le supported versions: [8] + - name: Replication Server + platforms: + - name: CentOS 7 + arch: x86_64 + supported versions: [7] + - name: CentOS 7 + arch: ppc64le + supported versions: [7] + - name: AlmaLinux 8 or Rocky Linux 8 + arch: x86_64 + supported versions: [7] + - name: RHEL 7 or OL 7 + arch: x86_64 + supported versions: [7] + - name: RHEL 7 or OL 7 + arch: ppc64le + supported versions: [7] + - name: RHEL 8 or OL 8 + arch: x86_64 + supported versions: [7] + - name: Ubuntu 18.04 or Debian 9 + arch: x86_64 + supported versions: [7] + - name: Ubuntu 20.04 or Debian 10 + arch: x86_64 + supported versions: [7] + - name: SLES 12 + arch: x86_64 + supported versions: [7] + - name: SLES 15 + arch: x86_64 + supported versions: [7] + - name: SLES 12 + arch: ppc64le + supported versions: [7] + - name: SLES 15 + arch: ppc64le + supported versions: [7] \ No newline at end of file diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index ebecc543f8c..cbfd4685b93 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -146,6 +146,10 @@ const moveDoc = async (product, platform, version) => { (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/${prefix[plat]}_efm4_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Failover Manager", version: 4.4}, platform: {name: "SLES 15"}}, (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/${prefix[plat]}_efm4_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Postgres Advanced Server"}, platform: {name: "SLES 12"}}, + (ctx) => `epas/14/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "EDB Postgres Advanced Server"}, platform: {name: "SLES 15"}}, + (ctx) => `epas/14/epas_inst_linux/installing_epas_using_edb_repository//${fmtArchPath(ctx)}/epas_sles15_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Hadoop Foreign Data Wrapper"}, platform: {name: "SLES 12"}}, (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_hadoop_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Hadoop Foreign Data Wrapper"}, platform: {name: "SLES 15"}}, @@ -190,6 +194,10 @@ const moveDoc = async (product, platform, version) => { (ctx) => `postgis/3.1/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "PostGIS", version: 3.1}, platform: {name: "SLES 15"}}, (ctx) => `postgis/3.1/01a_installing_postgis/installing_on_linux/${fmtArchPath(ctx)}/${prefix[plat]}_postgis_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "SLES 12"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/${prefix[plat]}_eprs_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Replication Server", version: 7}, platform: {name: "SLES 15"}}, + (ctx) => `eprs/7/03_installation/03_installing_rpm_package/${fmtArchPath(ctx)}/${prefix[plat]}_eprs_sles15_${fmtArchFilename(ctx)}.mdx`), ); function match(context, ...conditions) { diff --git a/install_template/templates/platformBase/_shared.njk b/install_template/templates/platformBase/_shared.njk index 70ed1c6590f..4c513d9c283 100644 --- a/install_template/templates/platformBase/_shared.njk +++ b/install_template/templates/platformBase/_shared.njk @@ -12,6 +12,7 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo # Install EPEL repository and refresh the cache: {{ packageManager }} -y install {{ epelRepo }} {{ packageManager }} makecache +{% block rhel_8_or_ol8 %}{% endblock rhel_8_or_ol8 %} ``` {% endmacro %} diff --git a/install_template/templates/platformBase/rhel-8-or-ol-8.njk b/install_template/templates/platformBase/rhel-8-or-ol-8.njk index 69ee9d1be9a..851bbe372e8 100644 --- a/install_template/templates/platformBase/rhel-8-or-ol-8.njk +++ b/install_template/templates/platformBase/rhel-8-or-ol-8.njk @@ -4,12 +4,14 @@ {% block prerequisites %} {{ centosRepositoryConfiguration("dnf", "https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm") }} ```shell +{% block rhel_8_or_ol8 %} # Enable the codeready-builder-for-rhel-8-*-rpms repository since EPEL packages may depend on packages from it ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" # Disable the built-in PostgreSQL module: dnf -qy module disable postgresql +{% endblock rhel_8_or_ol8 %} ``` {% endblock prerequisites %} {% block installCommand %} diff --git a/install_template/templates/platformBase/sles-15.njk b/install_template/templates/platformBase/sles-15.njk index 198b9583ee0..f264864d1cf 100644 --- a/install_template/templates/platformBase/sles-15.njk +++ b/install_template/templates/platformBase/sles-15.njk @@ -1,4 +1,3 @@ - {% extends "platformBase/sles-12.njk" %} {% block activateSUSEmodule %} SUSEConnect -p PackageHub/15.3/{{ platform.arch }} diff --git a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-connectdatabasecluster.njk b/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-connectdatabasecluster.njk deleted file mode 100644 index 48f885404e2..00000000000 --- a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-connectdatabasecluster.njk +++ /dev/null @@ -1,6 +0,0 @@ -1. To ensure the installation and initial configuration was successful, check the status of your cluster: - - ```sh - /usr/edb/as{{ product.version }}/bin/pg_ctl status -D /var/lib/edb/as{{ product.version }}/data - ``` - See [Managing Cluster > Managing Services] for more information. \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk b/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk deleted file mode 100644 index 19d7f24d014..00000000000 --- a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk +++ /dev/null @@ -1,11 +0,0 @@ -1. Initialize the database cluster: - - ```sh - PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as{{ product.version }}/bin/edb-as-{{ product.version | replace(".", "") }}-setup initdb - ``` - -1. Start the database cluster: - - ```sh - systemctl start edb-as-{{ product.version }} - ``` diff --git a/install_template/templates/products/edb-postgres-advanced-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/edb-postgres-advanced-server/almalinux-8-or-rocky-linux-8.njk index 7570fb82e1f..634fb34f8f2 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/almalinux-8-or-rocky-linux-8.njk @@ -2,21 +2,12 @@ {% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} {% block prerequisites %} {{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` +```shell +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` {% endblock prerequisites %} {% block installCommand %} {{ super() }} {% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %} -{% endblock installCommand %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} -{% block connectdatabasecluster %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-connectdatabasecluster.njk" %} -{{ super() }} -{% endblock connectdatabasecluster %} +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/base.njk b/install_template/templates/products/edb-postgres-advanced-server/base.njk index 37ef64a7617..b732e54d5ae 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/base.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/base.njk @@ -1,72 +1,52 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-as-server{% endset %} -{% block installCommand %} -```shell -zypper -n install {{ packageName }} -``` -Where xx is the version of EDB Postgres Advanced Server you are installing. -{% endblock installCommand %} - {% block postinstall %} -## Connecting to Your Database cluster - -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. - -{% block connectdatabasecluster %}{% endblock connectdatabasecluster %} -1. To work in your cluster, login as `enterprisedb` user: - - ```sh - su - enterprisedb - ``` - See [Managing Your Cluster > Managing Services], for more information. - -1. Connect to the database server using psql command line client: - - ```sh - psql edb - ``` - See [Managing Your Cluster > Connecting to Your Cluster], for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface. - -1. Then, assign a password to the database superuser `enterprisedb`: +Where `` is the version of the EDB Postgres Advanced server you are installing. - ```sh - ALTER ROLE enterprisedb IDENTIFIED BY password; - ``` +{% block individual_component %}{% endblock individual_component %} -## Creating a Database +## Initial configuration -This section steps you through creating and adding data to a simple database. - -1. Create a database (named hr): - - ```sh - CREATE DATABASE hr; - ``` - -1. Connect to the new database and create a table (named dept): - - ```sh - \c hr - CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk - PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc - varchar(13)); - ``` - -1. Add data to the table: - - ```sh - INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); - INSERT into dept VALUES (20,'RESEARCH','DALLAS'); - ``` - -1. You can use simple SQL commands to query the database and retrieve information about the data you have added to the table: +{% block debian_ubuntu %} +This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. - ```sh - SELECT * FROM dept; - deptno | dname | loc - --------+------------+---------- - 10 | ACCOUNTING | NEW YORK - 20 | RESEARCH | DALLAS - (2 rows) - ``` +```shell +# Initialize the database cluster +PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as{{ product.version }}/bin/edb-as-{{ product.version | replace(".", "") }}-setup initdb + +# Start the database cluster +systemctl start edb-as-{{ product.version }} +{% endblock debian_ubuntu %} + +# To work in your cluster, login as the enterprisedb user +su - enterprisedb + +# Connect to the database server using the psql command line client +psql edb + +# Assign a password to the database superuser the enterprisedb +ALTER ROLE enterprisedb IDENTIFIED BY password; + +# Create a database (named hr) +CREATE DATABASE hr; + +# Connect to the new database and create a table (named dept) +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); + +# Add data to the table +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); + +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table +SELECT * FROM dept; +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` {% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk b/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk index 82c31735212..b5554bfdafa 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk @@ -3,12 +3,4 @@ {% block installCommand %} {{ super() }} {% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %} -{% endblock installCommand %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} -{% block connectdatabasecluster %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-connectdatabasecluster.njk" %} -{{ super() }} -{% endblock connectdatabasecluster %} +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk b/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk index 2088e274ad2..b92d37451d0 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk @@ -1,6 +1,5 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "debian-10" %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_debian-initialconfiguration.njk" %} -{{ super() }} -{% endblock postinstall %} \ No newline at end of file +{% block debian_ubuntu %} +For Debian/Ubuntu platforms, initializing and starting of the database cluster is done along with the package installation. +{% endblock debian_ubuntu %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/debian-9.njk b/install_template/templates/products/edb-postgres-advanced-server/debian-9.njk index 876f9e82bbe..c9558571464 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/debian-9.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/debian-9.njk @@ -1,6 +1,5 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "debian-9" %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_debian-initialconfiguration.njk" %} -{{ super() }} -{% endblock postinstall %} +{% block debian_ubuntu %} +For Debian/Ubuntu platforms, initializing and starting of the database cluster is done along with the package installation. +{% endblock debian_ubuntu %} diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk index 989c8c5b739..49d9eebf2bd 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk @@ -3,8 +3,4 @@ {% block installCommand %} {{ super() }} {% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %} -{% endblock installCommand %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-centos-8-or-ol-8.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-centos-8-or-ol-8.njk deleted file mode 100644 index 54997b7ac49..00000000000 --- a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-centos-8-or-ol-8.njk +++ /dev/null @@ -1,10 +0,0 @@ -{% extends "products/edb-postgres-advanced-server/base.njk" %} -{% set platformBaseTemplate = "rhel-8-or-ol-8" %} -{% block installCommand %} -{{ super() }} -{% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %} -{% endblock installCommand %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk index 54997b7ac49..5c6a256b0f8 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk @@ -3,8 +3,4 @@ {% block installCommand %} {{ super() }} {% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %} -{% endblock installCommand %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk index 64ac8240b95..095f157017e 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk @@ -1,6 +1,11 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "sles-12" %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} +{% block individual_component %} +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). +{% endblock individual_component %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk index 64ac8240b95..b147a5556c5 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk @@ -1,6 +1,2 @@ -{% extends "products/edb-postgres-advanced-server/base.njk" %} -{% set platformBaseTemplate = "sles-12" %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} +{% extends "products/edb-postgres-advanced-server/sles-12.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk index c57a843fa73..9a67b555e5c 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-15.njk @@ -1,6 +1,11 @@ {% extends "products/edb-postgres-advanced-server/base.njk" %} {% set platformBaseTemplate = "sles-15" %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} +{% block individual_component %} +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). +{% endblock individual_component %} \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-15_ppc64le.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-15_ppc64le.njk index a4113efd4f6..994ebffa821 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/sles-15_ppc64le.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/sles-15_ppc64le.njk @@ -1,7 +1,2 @@ -{% extends "products/edb-postgres-advanced-server/base.njk" %} -{% set platformBaseTemplate = "sles-15" %} +{% extends "products/edb-postgres-advanced-server/sles-15.njk" %} {% set includePPC = true %} -{% block postinstall %} -{% include "products/edb-postgres-advanced-server/_centos-rhel-postinstall.njk" %} -{{ super() }} -{% endblock postinstall %} diff --git a/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk new file mode 100644 index 00000000000..f1a29c47508 --- /dev/null +++ b/install_template/templates/products/replication-server/almalinux-8-or-rocky-linux-8.njk @@ -0,0 +1,10 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} +{% block prerequisites %} +{{ super() }} +1. Disable the built-in PostgreSQL module: + + ```sh + dnf -qy module disable postgresql + ``` +{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/base.njk b/install_template/templates/products/replication-server/base.njk new file mode 100644 index 00000000000..91cd996c178 --- /dev/null +++ b/install_template/templates/products/replication-server/base.njk @@ -0,0 +1,24 @@ +{% extends "platformBase/" + platformBaseTemplate + '.njk' %} +{% set packageName %}edb-xdb{% endset %} +{% block installCommand %} +You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. + +To install all Replication Server components: +```shell +zypper -n install {{ packageName }} +``` + +To install an individual component: +```shell +zypper install +``` + +Where `` is: + +| Package name | Component | +| --------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | + +{% endblock installCommand %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/centos-7.njk b/install_template/templates/products/replication-server/centos-7.njk new file mode 100644 index 00000000000..643abd8ea9f --- /dev/null +++ b/install_template/templates/products/replication-server/centos-7.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/centos-7_ppc64le.njk b/install_template/templates/products/replication-server/centos-7_ppc64le.njk new file mode 100644 index 00000000000..f3661e147f2 --- /dev/null +++ b/install_template/templates/products/replication-server/centos-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/centos-7.njk" %} +{% set includePPC = true %} diff --git a/install_template/templates/products/replication-server/debian-10.njk b/install_template/templates/products/replication-server/debian-10.njk new file mode 100644 index 00000000000..90abb59daa4 --- /dev/null +++ b/install_template/templates/products/replication-server/debian-10.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "debian-10" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/debian-9.njk b/install_template/templates/products/replication-server/debian-9.njk new file mode 100644 index 00000000000..380ae26a7bf --- /dev/null +++ b/install_template/templates/products/replication-server/debian-9.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk b/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk new file mode 100644 index 00000000000..e24ab1bfe1c --- /dev/null +++ b/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk new file mode 100644 index 00000000000..0f69f26d3a8 --- /dev/null +++ b/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/rhel-7-or-ol-7.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/rhel-8-or-ol-8.njk b/install_template/templates/products/replication-server/rhel-8-or-ol-8.njk new file mode 100644 index 00000000000..aee35351bf9 --- /dev/null +++ b/install_template/templates/products/replication-server/rhel-8-or-ol-8.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-12.njk b/install_template/templates/products/replication-server/sles-12.njk new file mode 100644 index 00000000000..18823a2b02e --- /dev/null +++ b/install_template/templates/products/replication-server/sles-12.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-12_ppc64le.njk b/install_template/templates/products/replication-server/sles-12_ppc64le.njk new file mode 100644 index 00000000000..18823a2b02e --- /dev/null +++ b/install_template/templates/products/replication-server/sles-12_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "sles-12" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-15.njk b/install_template/templates/products/replication-server/sles-15.njk new file mode 100644 index 00000000000..62c5745d295 --- /dev/null +++ b/install_template/templates/products/replication-server/sles-15.njk @@ -0,0 +1,2 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "sles-15" %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/sles-15_ppc64le.njk b/install_template/templates/products/replication-server/sles-15_ppc64le.njk new file mode 100644 index 00000000000..c75f4039ced --- /dev/null +++ b/install_template/templates/products/replication-server/sles-15_ppc64le.njk @@ -0,0 +1,3 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "sles-15" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/replication-server/ubuntu-18.04.njk b/install_template/templates/products/replication-server/ubuntu-18.04.njk new file mode 100644 index 00000000000..e77281fa687 --- /dev/null +++ b/install_template/templates/products/replication-server/ubuntu-18.04.njk @@ -0,0 +1 @@ +{% extends "products/replication-server/debian-10.njk" %} diff --git a/install_template/templates/products/replication-server/ubuntu-20.04.njk b/install_template/templates/products/replication-server/ubuntu-20.04.njk new file mode 100644 index 00000000000..e77281fa687 --- /dev/null +++ b/install_template/templates/products/replication-server/ubuntu-20.04.njk @@ -0,0 +1 @@ +{% extends "products/replication-server/debian-10.njk" %} diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx index 4cce19cc550..c776b0cbb6a 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx @@ -9,7 +9,7 @@ redirects: You can connect to your cluster using [`psql`](http://postgresguide.com/utilities/psql.html), the terminal-based client for Postgres, or another client. For additional security measures see: -- [Recommendations for Settings for SSL Mode](#recommended-settings-for-ssl-mode) +- [Recommendations for settings for SSL mode](#recommended-settings-for-ssl-mode) - [Using a private network to connect to your cluster](#setting-up-cloud-infrastructure-to-connect-to-a-private-network-cluster) ## Connect to your cluster using `psql` @@ -32,17 +32,42 @@ You can connect to your cluster using [`psql`](http://postgresguide.com/utilitie 3. Select the name of your cluster. -4. Select the **Connect** tab. You can review and copy all the relevant information you need from this screen except for the edb_admin user password. Consult the client driver documentation for the connection string format the driver uses. +4. Select the **Connect** tab. You can review and copy all the relevant information you need from this screen except for the edb_admin user password. Consult the client driver documentation for the connection string format or see [Recommended settings for SSL mode](#recommended-settings-for-ssl-mode) for sample connection strings of common drivers. ## Recommended settings for SSL mode -Different clients can have different default TLS/SSL modes (sslmode). For example, `psql` defaults to `prefer`, which means the client will attempt to establish a TLS connection but fall back to non-TLS if the server does not support it. In the `psql` example provided by EDB in the **Quick Connect** field, `sslmode` is explicitly set to `require`, which means the client will attempt a TLS connection and fail if the connection to the server can't be encrypted. +Different clients can have different default TLS/SSL modes (sslmode). For example, `psql` defaults to `prefer`, which means the client will attempt to establish a TLS connection but fall back to non-TLS if the server does not support it. In the `psql` example provided by EDB in the **Quick Connect** field, `sslmode` is explicitly set to `require`, which means the client will attempt a TLS connection and fail if the connection to the server can't be encrypted. -For public connections and in most environments, EDB recommends setting `sslmode` to `verify-full`. This setting ensures that you connect to the server you specified and that the connection is encrypted. BigAnimal generates certificates with LetsEncrypt, a widely trusted certificate authority. Your client machine might already have a bundled CA certificate for LetsEncrypt, for example, at `/etc/ssl/certs/ca-certificates.crt` or `/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem`. If it doesn't, your client machine needs a [CA certificate for Let's Encrypt](https://letsencrypt.org/certificates/). Once the CA certificate is in place on your client machine, configure the `sslrootcert` parameter to its location and set the `sslmode` parameter to `verify-full` to verify the certificate to fully validate the connection: +For public connections and in most environments, EDB recommends setting `sslmode` to `verify-full`. This setting ensures that you connect to the server you specified and that the connection is encrypted. + +BigAnimal generates certificates with LetsEncrypt, a widely trusted certificate authority. Your client machine might already have a bundled CA certificate for LetsEncrypt, for example, at `/etc/ssl/certs/ca-certificates.crt` or `/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem`. If it doesn't, your client machine needs a [CA certificate for Let's Encrypt](https://letsencrypt.org/certificates/). Once the CA certificate is in place on your client machine, configure the `sslrootcert` parameter to its location and set the `sslmode` parameter to `verify-full` to verify the certificate to fully validate the connection. + +Connection string examples for common database drivers: + +- libpq (psql) + + ``` + psql -W "postgres://edb_admin@xxxxxxxxx.xxxxx.biganimal.io:5432/edb_admin?sslmode=verify-full&sslrootcert=/usr/share/ca-certificates/ca-cert_name.pem" + ``` + +- JDBC for Java + + ``` + jdbc:postgresql://xxxxxxxxx.xxxxx.biganimal.io:5432/edb_admin?&sslrootcert=/usr/share/ca-certificates/ca-cert_name.pem&sslmode=verify-full?user=edb_admin&password=$PWD + ``` + +- Npgsql for DotNet Core + + ``` +Host=xxxxxxxxx.xxxxx.biganimal.io;Port=5432;Username=edb_admin;Password=$PWD;Database=edb_admin;SslRootCert=/usr/share/ca-certificates/ca-cert_name.pem;SslMode=verify-full + ``` + +- ODBC for Windows + + ``` +Driver={PostgreSQL};Server=xxxxxxxxx.xxxxx.biganimal.io;Port=5432;Database=myDataBase;Uid=edb_admin;Pwd=$PWD;sslrootcert=C:\\ssl\\ca-certificate.pem;sslmode=verify-full; + ``` -```shell -psql -W "postgres://edb_admin@xxxxxxxxx.xxxxx.biganimal.io:5432/edb_admin?sslmode=verify-full&sslrootcert=/usr/share/ca-certificates/isrgrootx1.pem" -``` Once connected to the cluster using `psql`, the `conninfo` meta-command shows the encryption protocol being used for communication. In the case of BigAnimal, TLS (v1.2+) is supported: @@ -52,11 +77,13 @@ You are connected to database "edb_admin" as user "edb_admin" on host "xxxxxxxxx SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off) ``` + + ## Setting up cloud infrastructure to connect to a private network cluster The Private Networking option offers a higher level of isolation and security by moving your cluster out of the public Internet. Clusters with Private Networking enabled are by default not accessible from outside of your cluster's resource network. You need to perform additional configuration steps to connect your applications in other parts of your cloud infrastructure to your clusters via private network links. -!!!note +!!!Note EDB strongly discourages provisioning additional resources in the cluster's resource virtual network. For examples to guide you through the different methods of connecting to your cluster, see diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index b16339f352c..4087ac5484e 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -105,7 +105,7 @@ In the event of a failover, Failover Manager first retrieves information from Po The promotion priority for nodes changes when a new primary is promoted. - If the `efm set-priority` command was used to change whether a standby is promotable, you can reset this to the value in the standby's properties file through promotion or cluster splits and rejoins. + If the `efm set-priority` command was used to change whether a standby is promotable, it may be reset to the value in the standby's properties file through promotion or cluster splits and rejoins. ### Promoting a Failover Manager node diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_rhel7_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_rhel7_ppcle.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_rhel8_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_rhel8_ppcle.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx new file mode 100644 index 00000000000..eda2e3be9c0 --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle.mdx @@ -0,0 +1,98 @@ +--- +navTitle: SLES 12 +title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le +--- + +Before you begin the installation process, log in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +## Set up the repository + +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/12.5/ppc64le +SUSEConnect -p sle-sdk/12.5/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced server you are installing. + +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +```shell +# Initialize the database cluster +PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb + +# Start the database cluster +systemctl start edb-as-14 + + +# To work in your cluster, login as the enterprisedb user +su - enterprisedb + +# Connect to the database server using the psql command line client +psql edb + +# Assign a password to the database superuser the enterprisedb +ALTER ROLE enterprisedb IDENTIFIED BY password; + +# Create a database (named hr) +CREATE DATABASE hr; + +# Connect to the new database and create a table (named dept) +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); + +# Add data to the table +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); + +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table +SELECT * FROM dept; +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx new file mode 100644 index 00000000000..036d1313931 --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle.mdx @@ -0,0 +1,97 @@ +--- +navTitle: SLES 15 +title: Installing EDB Postgres Advanced Server on SLES 15 ppc64le +--- + +Before you begin the installation process, log in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +## Set up the repository + +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/ppc64le + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced server you are installing. + +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +```shell +# Initialize the database cluster +PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb + +# Start the database cluster +systemctl start edb-as-14 + + +# To work in your cluster, login as the enterprisedb user +su - enterprisedb + +# Connect to the database server using the psql command line client +psql edb + +# Assign a password to the database superuser the enterprisedb +ALTER ROLE enterprisedb IDENTIFIED BY password; + +# Create a database (named hr) +CREATE DATABASE hr; + +# Connect to the new database and create a table (named dept) +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); + +# Add data to the table +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); + +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table +SELECT * FROM dept; +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/index.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/index.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/index.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/index.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx index 2d939c0aac4..52be564de14 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/index.mdx @@ -7,26 +7,26 @@ redirects: navigation: - - x86 - - ppc64le + - x86_amd64 + - ibm_power_ppc64le --- For platform-specific install instructions, including accessing the repo, see: - Linux x86-64 (amd64): - - [RHEL 8/OL 8](x86/epas_rhel8_x86) - - [Rocky Linux 8/AlmaLinux 8/](x86/epas_other_linux8_x86) - - [RHEL 7/OL 7](x86/epas_rhel7_x86) - - [CentOS 7](x86/epas_centos7_x86) - - [SLES 15](x86/epas_sles15_x86) - - [SLES 12](x86/epas_sles12_x86) - - [Ubuntu 20.04](x86/epas_ubuntu20_x86) - - [Ubuntu 18.04](x86/epas_ubuntu18_x86) - - [Debian 10](x86/epas_deb10_x86) - - [Debian 9](x86/epas_deb9_x86) + - [RHEL 8/OL 8](x86_amd64/epas_rhel8_x86) + - [Rocky Linux 8/AlmaLinux 8/](x86_amd64/epas_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/epas_rhel7_x86) + - [CentOS 7](x86_amd64/epas_centos7_x86) + - [SLES 15](x86_amd64/epas_sles15_x86) + - [SLES 12](x86_amd64/epas_sles12_x86) + - [Ubuntu 20.04](x86_amd64/epas_ubuntu20_x86) + - [Ubuntu 18.04](x86_amd64/epas_ubuntu18_x86) + - [Debian 10](x86_amd64/epas_deb10_x86) + - [Debian 9](x86_amd64/epas_deb9_x86) - Linux on IBM Power (ppc64le): - - [RHEL 8](ppc64le/epas_rhel8_ppcle) - - [RHEL 7](ppc64le/epas_rhel7_ppcle) - - [SLES 15](ppc64le/epas_sles15_ppcle) - - [SLES 12](ppc64le/epas_sles12_ppcle) \ No newline at end of file + - [RHEL 8](ibm_power_ppc64le/epas_rhel8_ppcle) + - [RHEL 7](ibm_power_ppc64le/epas_rhel7_ppcle) + - [SLES 15](ibm_power_ppc64le/epas_sles15_ppcle) + - [SLES 12](ibm_power_ppc64le/epas_sles12_ppcle) \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles12_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles12_ppcle.mdx deleted file mode 100644 index 1348e2f2e59..00000000000 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles12_ppcle.mdx +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: "Installing EDB Postgres Advanced Server on SLES 12 ppc64le" -navTitle: "SLES 12" ---- - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# You can skip this step if already registered -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE modules on SUSE 12 -SUSEConnect -p PackageHub/12.5/ppc64le -SUSEConnect -p sle-sdk/12.5/ppc64le - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-as14-server -``` - -To install an individual component: - -```shell -zypper install package_name -``` - -Where `package_name` can be any of the available package from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). - -## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. See [Managing an EDB Postgres Advanced Server installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. - -```shell -# Initialize the database cluster: -PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb - -# Start the database cluster: -systemctl start edb-as-14 -# To work in your cluster, login as `enterprisedb` user: -su - enterprisedb -# Connect to the database server using psql command line client: -psql edb -# Assign a password to the database superuser `enterprisedb`: -ALTER ROLE enterprisedb IDENTIFIED BY password; -# Creating a database (named hr): -CREATE DATABASE hr; -# Connect to the new database and create a table (named dept): -\c hr -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, -dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); -# Add data to the table: -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -# You can use simple SQL commands to query the database and retrieve -# information about the data you have added to the table. -SELECT * FROM dept; -``` - diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles15_ppcle.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles15_ppcle.mdx deleted file mode 100644 index 104b28ccbce..00000000000 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppc64le/epas_sles15_ppcle.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: "Installing EDB Postgres Advanced Server on SLES 15 ppc64le" -navTitle: "SLES 15" ---- - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# You can skip this step if already registered -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE modules on SUSE 15 -SUSEConnect -p PackageHub/15.3/ppc64le - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-as14-server -``` - -To install an individual component: - -```shell -zypper install package_name -``` - -Where `package_name` can be any of the available package from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). - -## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. See [Managing an installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. - -```shell -# Initialize the database cluster: -PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb - -# Start the database cluster: -systemctl start edb-as-14 -# To work in your cluster, login as `enterprisedb` user: -su - enterprisedb -# Connect to the database server using psql command line client: -psql edb -# Assign a password to the database superuser `enterprisedb`: -ALTER ROLE enterprisedb IDENTIFIED BY password; -# Creating a database (named hr): -CREATE DATABASE hr; -# Connect to the new database and create a table (named dept): -\c hr -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, -dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); -# Add data to the table: -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -# You can use simple SQL commands to query the database and retrieve -# information about the data you have added to the table. -SELECT * FROM dept; -``` diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86.mdx deleted file mode 100644 index c311a503cbe..00000000000 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86.mdx +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: "Installing EDB Postgres Advanced Server on SLES 12 x86" -navTitle: "SLES 12" ---- - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -```shell -# Install the repository configuration and enter your EDB repository -# credentials when prompted -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# You can skip this step if already registered -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE modules on SUSE 12 -SUSEConnect -p PackageHub/12.5/x86_64 -SUSEConnect -p sle-sdk/12.5/x86_64 - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-as14-server -``` - -To install an individual component: - -```shell -zypper install package_name -``` - -Where `package_name` can be any of the available package from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). - -## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. See [Managing an EDB Postgres Advanced Server installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. - -```shell -# Initialize the database cluster: -PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb - -# Start the database cluster: -systemctl start edb-as-14 -# To work in your cluster, login as `enterprisedb` user: -su - enterprisedb -# Connect to the database server using psql command line client: -psql edb -# Assign a password to the database superuser `enterprisedb`: -ALTER ROLE enterprisedb IDENTIFIED BY password; -# Creating a database (named hr): -CREATE DATABASE hr; -# Connect to the new database and create a table (named dept): -\c hr -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, -dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); -# Add data to the table: -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -# You can use simple SQL commands to query the database and retrieve -# information about the data you have added to the table. -SELECT * FROM dept; -``` - diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles15_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles15_x86.mdx deleted file mode 100644 index b981f5a5165..00000000000 --- a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles15_x86.mdx +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: "Installing EDB Postgres Advanced Server on SLES 15 x86" -navTitle: "SLES 15" -redirects: -- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-sles-x86_64 ---- - -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -```shell -# To log in as a superuser: -sudo su - -``` - -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Setting up the repository - -```shell -# Install the repository configuration -zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - -# Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories -zypper install SUSEConnect - -# Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration information -SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - -# Activate the required SUSE modules on SUSE 15 -SUSEConnect -p PackageHub/15.3/x86_64 - -# Refresh the metadata -zypper refresh -``` - -## Installing the package - -```shell -zypper -n install edb-as14-server -``` - -To install an individual component: - -```shell -zypper install package_name -``` - -Where `package_name` can be any of the available package from the [available package list](/epas/latest/epas_inst_linux/install_details/rpm_packages/). - -## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. See [Managing an EDB Postgres Advanced Server installation](/epas/latest/epas_inst_linux/managing_an_advanced_server_installation), for more information including how to use pgAdmin4 to connect to your cluster using its graphical interface instead of the command line option given below. - -```shell -# Initialize the database cluster: -PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb - -# Start the database cluster: -systemctl start edb-as-14 -# To work in your cluster, login as `enterprisedb` user: -su - enterprisedb -# Connect to the database server using psql command line client: -psql edb -# Assign a password to the database superuser `enterprisedb`: -ALTER ROLE enterprisedb IDENTIFIED BY password; -# Creating a database (named hr): -CREATE DATABASE hr; -# Connect to the new database and create a table (named dept): -\c hr -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY, -dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc varchar(13)); -# Add data to the table: -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -# You can use simple SQL commands to query the database and retrieve -# information about the data you have added to the table. -SELECT * FROM dept; -``` - diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb9_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb9_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb9_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb9_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux8_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux8_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel8_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel8_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx new file mode 100644 index 00000000000..a511c79276b --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86.mdx @@ -0,0 +1,98 @@ +--- +navTitle: SLES 12 +title: Installing EDB Postgres Advanced Server on SLES 12 x86_64 +--- + +Before you begin the installation process, log in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +## Set up the repository + +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced server you are installing. + +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +```shell +# Initialize the database cluster +PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb + +# Start the database cluster +systemctl start edb-as-14 + + +# To work in your cluster, login as the enterprisedb user +su - enterprisedb + +# Connect to the database server using the psql command line client +psql edb + +# Assign a password to the database superuser the enterprisedb +ALTER ROLE enterprisedb IDENTIFIED BY password; + +# Create a database (named hr) +CREATE DATABASE hr; + +# Connect to the new database and create a table (named dept) +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); + +# Add data to the table +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); + +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table +SELECT * FROM dept; +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx new file mode 100644 index 00000000000..10ab84d50c8 --- /dev/null +++ b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86.mdx @@ -0,0 +1,97 @@ +--- +navTitle: SLES 15 +title: Installing EDB Postgres Advanced Server on SLES 15 x86_64 +--- + +Before you begin the installation process, log in as superuser. + +```shell +# To log in as a superuser: +sudo su - +``` + +## Set up the repository + +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo + +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect + +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' + +# Activate the required SUSE module + +SUSEConnect -p PackageHub/15.3/x86_64 + +# Refresh the metadata +zypper refresh +``` + +## Install the package + +```shell +zypper -n install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced server you are installing. + +To install an individual component: + +```shell +zypper install +``` + +Where `package_name` can be any of the available package from the [available package list](https://www.enterprisedb.com/docs/epas/latest/epas_inst_linux/install_details/rpm_packages/). + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +```shell +# Initialize the database cluster +PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb + +# Start the database cluster +systemctl start edb-as-14 + + +# To work in your cluster, login as the enterprisedb user +su - enterprisedb + +# Connect to the database server using the psql command line client +psql edb + +# Assign a password to the database superuser the enterprisedb +ALTER ROLE enterprisedb IDENTIFIED BY password; + +# Create a database (named hr) +CREATE DATABASE hr; + +# Connect to the new database and create a table (named dept) +\c hr +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); + +# Add data to the table +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); + +# You can use simple SQL commands to query the database and retrieve +# information about the data you have added to the table +SELECT * FROM dept; +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu18_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu18_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86.mdx diff --git a/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx b/product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/index.mdx similarity index 100% rename from product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/index.mdx rename to product_docs/docs/epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/index.mdx diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx index 2bb83362ba2..32316168e86 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx @@ -6,7 +6,7 @@ title: "Synchronization Replication with the Trigger-Based Method" If a publication in a single-master replication system is created that will be used in synchronization replications with the trigger-based method, the publication server installs an insert trigger, an update trigger, and a delete trigger on each publication table. In a multi-master replication system, each replicated table in each primary node employing the trigger-based method has an insert trigger, an update trigger, and a delete trigger. -Oracle and SQL Server databases can only be used as a publication database with the trigger-based method. Additionally, Oracle and SQL Server databases can only be used as a subscription database with the WAL-based replication method. +Oracle and SQL Server databases can only be used as publication databases with the trigger-based method. Additionally, Oracle and SQL Server databases can be used as subscription databases with the WAL-based replication method. The publication server also creates a shadow table for each source table on which triggers have been created. A shadow table is a table used by xDB Replication Server to record the changes (inserts, updates, and deletions) made to a given source table. A shadow table records three types of record images: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx new file mode 100644 index 00000000000..2b477b99a6a --- /dev/null +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx @@ -0,0 +1,357 @@ +--- +title: "Installing the Replication Server RPM package" +--- + + + +Replication Server is supplied as an RPM package available in the EDB Yum Repository. Use the Yum package manager to install Replication Server from the RPM package. + +For information about using yum, see the [yum project website](http://yum.baseurl.org). + +For information about using the EDB yum repository, see the [EDB Postgres Advanced Server Linux Installation Guide](/epas/latest/epas_inst_linux). + +!!! Note + Although the following primarily describes the installation of Replication Server version 7.0, access to the RPM packages for prior Replication Server versions are also described in order to differentiate the installation of these different versions. + +Each Replication Server component is available as an individual RPM package. Thus, you can install all Replication Server components with a single yum install command, or you may choose to install selected, individual components by installing only those particular RPM packages. + +The following table lists the RPM packages and the Replication Server component it contains. + +**Table 3 1: Replication Server component RPM packages** + +| | | +| --------------------------------------------------- | ----------------------------------------------------------------------------- | +| **Package name** | **Replication Server Component** | +| `edb-xdb` | All components | +| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | +| `edb-xdb-libs` | Library files required by all components | + + +The Advanced Server server libs package must be available for access by Yum when installing any Replication Server RPM package component. The edb-asxx-server-libs package is a component of the Advanced Server repository package for version 10 or later. Step 3 shows how to enable access to the Advanced Server repository so Yum can access its server libs package. + +!!! Note + You might have to enable the \[extras] repository definition in the `CentOS-Base.repo file (located in /etc/yum.repos.d)`. + +To install any of the packages, invoke the following command as the root account: + +`yum install package_name` + +`package_name` is any of the packages listed under the Package Name column of the preceding table. + +For example to install all Replication Server components, invoke the following: + +`yum install edb-xdb` + +To install only the EPRS Replication Console and Replication Server Command Line Interface, invoke the following: + +`yum install edb-xdb-console` + +To install only the publication server, invoke the following: + +`yum install edb-xdb-publisher` + +!!! Note + Though all Replication Server components are dependent upon and thus require installation of the server libs package, by using Yum, the dependency on the server libs is recognized when any Replication Server component is installed. Yum automatically installs the server libs package from the enabled Advanced Server repository along with your selected Replication Server RPM package. + +## Installation steps for Linux on x86-64 (amd64) + +The following are the steps to perform a complete Replication Server installation with all Replication Server components. + +**Step 1:** You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. + +Follow the directions for your host operating system to install Java runtime. + +!!! Note + For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. + +**Step 2:** From the EDB Yum Repository, click on the following link to download the repository RPM for all the EnterpriseDB RPMs.: + +> + +As the `root` account, run the following command to install this repository configuration package: + +**On RHEL or CentOS 7:** + +> `yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` + +**On RHEL or Rocky Linux or AlmaLinux 8:** + +> `dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` + +**Step 3:** In the directory `/etc/yum.repos.d`, the repository configuration file `edb.repo` is created, which a text file is containing a list of EnterpriseDB repositories, each denoted by an entry starting with the text `[repository_name]`. + +Access to the packages in any of these repositories is accomplished by enabling the repository by editing the following in the repository entry: + +- Using your requested credentials for the EDB Yum Repository, substitute the user name and password for the `:` placeholders of the baseurl parameter. +- Change the setting of the enabled parameter to `enabled=1`. + +For example, to access the server `libs` package from the repository for Advanced Server version 14, enable the following entry: + +```text +[edbas96] +name=EnterpriseDB Advanced Server 14 $releasever - $basearch +baseurl=http://:@yum.enterprisedb.com/14/redhat/rhel-$releasever-$basearch +enabled=1 +gpgcheck=1 +gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +``` + +To enable the appropriate repository for installing the desired version of Replication Server, enable one of the following entries: + +- To install version 7.0, enable the entry for \[`enterprisedb-xdb70`]. +- To install a prior version, enable the entry for \[`enterprisedb-tools`]. + +Whichever version is chosen, be sure the other entries are disabled (that is, the parameter setting is enabled=0 for the non-selected entries). + +For example, to access Replication Server version 7.0, enable the following entry: + +```text +[enterprisedb-xdb70] +name=EnterpriseDB XDB 7.0 $releasever - $basearch +baseurl=http://:@yum.enterprisedb.com/xdb70/redhat/rhel-$releasever-$basearch +enabled=0 +gpgcheck=1 +gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +``` + +**Step 4:** Install the Replication Server RPM package. + +The following syntax installs the Replication Server RPM package: + +`yum install edb-xdb` + +The following is an example: + +```text +yum install edb-xdb +Loaded plugins: fastestmirror, langpacks +Loading mirror speeds from cached hostfile +* base: centos.excellmedia.net +* extras: centos.excellmedia.net +* updates: centos.excellmedia.net +base | 3.6 kB 00:00:00 +edb | 2.5 kB 00:00:00 +extras | 2.9 kB 00:00:00 +updates | 2.9 kB 00:00:00 +edb/7/x86_64/primary_db | 452 kB 00:00:03 +Resolving Dependencies +--> Running transaction check +---> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be installed +--> Processing Dependency: edb-jdbc-driver >= 42.2.19.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64 +Loading mirror speeds from cached hostfile + * base: centos.excellmedia.net + * epel: ftp.iij.ad.jp + * extras: centos.excellmedia.net + * updates: centos.excellmedia.net +---> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed +--> Processing Dependency: ppas-libs >= 13 for package: edb-xdb-console-7.0.0-1.rhel7.x86_64 +---> Package edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 will be installed +---> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed +---> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed +---> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed +--> Running transaction check +---> Package edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 will be installed +---> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be installed +--> Finished Dependency Resolution + + + +Dependencies Resolved +========================================================================================================================================================================= +Package Arch Version Repository Size +========================================================================================================================================================================= +Installing: + edb-xdb x86_64 7.0.0-1.rhel7 /edb-xdb-7.0.0-1.rhel7.x86_64 0.0 + edb-xdb-console x86_64 7.0.0-1.rhel7 /edb-xdb-console-7.0.0-1.rhel7.x86_64 3.3 M + edb-xdb-debuginfo x86_64 7.0.0-1.rhel7 /edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 192 k + edb-xdb-libs x86_64 7.0.0-1.rhel7 /edb-xdb-libs-7.0.0-1.rhel7.x86_64 15 M + edb-xdb-publisher x86_64 7.0.0-1.rhel7 /edb-xdb-publisher-7.0.0-1.rhel7.x86_64 131 k + edb-xdb-subscriber x86_64 7.0.0-1.rhel7 /edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5.2 k +Installing for dependencies: + edb-as13-server-libs x86_64 13.4.8-1.rhel7 edb 619 k + edb-jdbc x86_64 42.2.19.1-1.rhel7 edb 1.0 M + +Transaction Summary +========================================================================================================================================================================== +Install 6 Packages (+2 Dependent packages) + +Total size: 20 M +Total download size: 1.6 M +Installed size: 21 M +Downloading packages: +No Presto metadata available for edb +warning: /var/cache/yum/x86_64/7/edb/packages/edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 7e30651c: NOKEY ] 370 kB/s | 928 kB 00:00:01 ETA +Public key for edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm is not installed +(1/2): edb-jdbc-42.2.19.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:03 +(2/2): edb-as13-server-libs-13.4.8-1.rhel7.x86_64.rpm | 619 kB 00:00:04 +----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- +Total 387 kB/s | 1.6 MB 00:00:04 +Retrieving key from file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +Importing GPG key 0x7E30651C: + Userid : "EnterpriseDB Inc. (EnterpriseDB Yum Repositories) " + Fingerprint: ca40 9f7c 635f 2ae5 6c9e 8b34 e5ed e919 7e30 651c + Package : edb-repo-20-3.noarch (installed) + From : /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +Running transaction check +Running transaction test +Transaction test succeeded +Running transaction + Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/8 + Installing : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 2/8 + Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/8 + Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 4/8 + Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 5/8 + Installing : edb-jdbc-42.2.19.1-1.rhel7.x86_64 6/8 + Installing : edb-xdb-7.0.0-1.rhel7.x86_64 7/8 + Installing : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 8/8 + Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 1/8 + Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/8 + Verifying : edb-xdb-debuginfo-7.0.0-1.rhel7.x86_64 3/8 + Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 4/8 + Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 5/8 + Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 6/8 + Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 7/8 + Verifying : edb-as13-server-libs-13.4.8-1.rhel7.x86_64 8/8 + +Installed: + edb-xdb.x86_64 0:7.0.0-1.rhel7 edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-debuginfo.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 + edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 + +Dependency Installed: + edb-as13-server-libs.x86_64 0:13.4.8-1.rhel7 edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 + +Complete! +``` + +The Replication Server is installed in directory location `/usr/edb/xdb` + +```text +[root@localhost xdb]# pwd +/usr/edb/xdb +[root@localhost xdb]# ls -l +total 88 + +drwxr-xr-x. 2 root root 4096 Oct 7 12:50 bin +-r--r--r--. 1 root root 15272 Jul 12 09:58 edb-xdb_license.txt +drwxr-xr-x. 3 root root 151 Oct 7 12:50 etc +drwxr-xr-x. 4 root root 4096 Oct 7 12:50 lib +drwx------. 2 enterprisedb enterprisedb 6 Oct 7 00:07 xdata +-r--r--r--. 1 enterprisedb enterprisedb 61497 Jul 12 09:58 xdb_3rd_party_licenses.txt +``` + +Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in Section [Post-Installation Host Environment](05_post_installation_host_environment/#post_installation_host_environment). + +!!! Note + Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). + +**Step 5 (For Replication Server 7.0 and 6.2):** In the EPRS Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the EPRS Replication Configuration File](../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file/#encrypt_password_in%20conf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the EPRS Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [EPRS Replication Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for information on the EPRS Replication Configuration file. + +**Step 6:** The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the Replication Server Startup Configuration file. See [Post-Installation Host Environment](05_post_installation_host_environment/#post_installation_host_environment) for the location of this file. + +## Installation steps for RHEL 8 on IBM Power (ppc64le) +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```shell +sudo su - +``` + +#### Setting up the repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```shell + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```shell + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```shell + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```shell + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```shell + dnf -qy module disable postgresql + ``` + +#### Installing the package + +```shell +dnf -y install edb-xdb +``` + + +## Updating an RPM installation + +If you have an existing Replication Server RPM installation, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: + +`yum upgrade edb-repo` + +`yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: + +`yum upgrade ppas-xdb*` + +See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details. + +## Updating a Bitrock installer installation + +To upgrade from a 6.2.x version of Replication Server that was installed using the Replication Server Bitrock installer: + +1. Stop the Replication Server Publication and Subscription services. + +1. Back up the following file and folder: + - `/etc/edb-repl.conf` + - `/opt/PostgreSQL/EnterpriseDB-xDBReplicationServer/xdata` + +1. If you have modified any of the following configuration files in the `/opt/PostgreSQL/EnterpriseDB-xDBReplicationServer/etc` folder, back up the modified files: + - `encoding_map.conf` + - `euc_jp.conf` + - `sysconfig` + - `xdb_pubserver.conf` + - `xdb_subserver.conf` + +1. Uninstall Replication Server 6.2.x: + + `/opt/PostgreSQL/EnterpriseDB-xDBReplicationServer/uninstall-xdbreplicationserver` + +1. Complete the [installation steps](#installation-steps) in this topic. + +6. After you complete the installation steps, stop any running Publication and Subscription services. + +7. Replace `/etc/edb-repl.conf` with your backup file. + +8. Replace `/usr/edb/xdb/xdata` with your `/opt/PostgreSQL/EnterpriseDB-xDBReplicationServer/xdata` backup file. + +9. Replace files in `/usr/edb/xdb/etc/` with the backup of any modified files. + +10. Start the Publication and Subscription services. \ No newline at end of file diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/11_eprs_sles15_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/11_eprs_sles15_ppcle.mdx index cf17c35585f..b82149c010b 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/11_eprs_sles15_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/11_eprs_sles15_ppcle.mdx @@ -1,42 +1,35 @@ --- -title: "Installing Replication Server on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Replication Server on SLES 15 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ## Set up the repository -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -# Install the repository configuration and enter your EDB repository +# Install the repository configuration and enter your EDB repository # credentials when prompted zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories zypper install SUSEConnect # Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/ppc64le # Refresh the metadata @@ -50,20 +43,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -y install edb-xdb +zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install package_name +zypper install ``` -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | +Where `` is: +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/12_eprs_sles12_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/12_eprs_sles12_ppcle.mdx index dd2aaa8c75a..24829a6f2c6 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/12_eprs_sles12_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/12_eprs_sles12_ppcle.mdx @@ -1,73 +1,62 @@ --- -title: "Installing Replication Server on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12 " +navTitle: SLES 12 +title: Installing Replication Server on SLES 12 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - -## Set up the Repository +## Set up the repository -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -# Install the repository configuration and enter your EDB repository +# Install the repository configuration and enter your EDB repository # credentials when prompted zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -# Install SUSEConnect to register the host with SUSE, allowing access to SUSE repositories +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories zypper install SUSEConnect # Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' -# Activate the required SUSE modules +# Activate the required SUSE module + SUSEConnect -p PackageHub/12.5/ppc64le SUSEConnect -p sle-sdk/12.5/ppc64le # Refresh the metadata zypper refresh - -# Install OpenJDK (version 1.8) -zypper -n install java-1_8_0-openjdk ``` -## Install the Package +## Install the package You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. To install all Replication Server components: ```shell -zypper install edb-xdb +zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install package_name +zypper install ``` -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | - +Where `` is: +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/05_eprs_sles15_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/05_eprs_sles15_x86.mdx index 1b159b8b807..2d2c199e5db 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/05_eprs_sles15_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/05_eprs_sles15_x86.mdx @@ -1,42 +1,35 @@ --- -title: "Installing Replication Server on SLES 15 x86" -navTitle: "SLES 15" +navTitle: SLES 15 +title: Installing Replication Server on SLES 15 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ## Set up the repository -Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -# Install the repository configuration and enter your EDB repository +# Install the repository configuration and enter your EDB repository # credentials when prompted zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo -# Install SUSEConnect to register the host with SUSE, allowing access to -# SUSE repositories +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories zypper install SUSEConnect # Register the host with SUSE, allowing access to SUSE repositories -# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration -# information +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' # Activate the required SUSE module + SUSEConnect -p PackageHub/15.3/x86_64 # Refresh the metadata @@ -50,19 +43,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper -y install edb-xdb +zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install package_name +zypper install ``` -Where `package_name` is: +Where `` is: -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/06_eprs_sles12_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/06_eprs_sles12_x86.mdx index 74a77cafbc2..ca85d9779ae 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/06_eprs_sles12_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/06_eprs_sles12_x86.mdx @@ -1,78 +1,41 @@ --- -title: "Installing Replication Server on SLES 12 x86" -navTitle: "SLES 12" +navTitle: SLES 12 +title: Installing Replication Server on SLES 12 x86_64 --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: sudo su - ``` -Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - - ## Set up the repository -1. Use the following commands to add EnterpriseDB repository configuration files to your SLES host: - - ```shell - zypper addrepo https://zypp.enterprisedb.com/suse/epas96-sles.repo - zypper addrepo https://zypp.enterprisedb.com/suse/epas-sles-tools.repo - zypper addrepo https://zypp.enterprisedb.com/suse/epas-sles-dependencies.repo - ``` - - Each command creates a repository configuration file in the /etc/zypp/repos.d directory. The files are named: - - - `edbas96suse.repo` - - `edbasdependencies.repo` - - `edbastools.repo` - +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -2. Use the `zypper refresh command` to refresh the metadata on your SLES host to include the EnterpriseDB repositories, as shown below. When prompted for a user name and password, provide your connection credentials for the EnterpriseDB repository. - - ```shell - /etc/zypp/repos.d # zypper refresh - __OUTPUT__ - Repository 'SLES12-12-0' is up to date. - Repository 'SLES12-Pool' is up to date. - Repository 'SLES12-Updates' is up to date. - Retrieving repository 'EDB Postgres Advanced Server 10 12 - x86_64' metadata -----------------------[\] - Authentication required for 'https://zypp.enterprisedb.com/10/suse/suse-12-x86_64' - User Name: - Password: - Retrieving repository 'EDB Postgres Advanced Server 10 12 - x86_64' metadata...................................[done] - Building repository 'EDB Postgres Advanced Server 10 12 - x86_64' cache..........................[done] - All repositories have been refreshed. - ... - ``` - -1. Add SUSEConnect and the SUSE Package Hub extension to the SLES host and register the host with SUSE, allowing access to SUSE repositories. Use the commands: +```shell +# Install the repository configuration and enter your EDB repository +# credentials when prompted +zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo - ```shell - zypper install SUSEConnect - SUSEConnect -p PackageHub/12/x86_64 - SUSEConnect -p sle-sdk/12/x86_64 - ``` +# Install SUSEConnect to register the host with SUSE, allowing access +# to SUSE repositories +zypper install SUSEConnect - For detailed information about registering a SUSE host, visit: +# Register the host with SUSE, allowing access to SUSE repositories +# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE +# registration information +SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' - > +# Activate the required SUSE module -1. Add the Java repository and update the repository metadata. Only OpenJDK 1.8 is supported on SLES hosts of Java components. Before using an RPM installer to add Advanced Server or a supporting component that requires Java, use `zypper` to add supporting repository locations to your system. Enter the following commands: +SUSEConnect -p PackageHub/12.5/x86_64 +SUSEConnect -p sle-sdk/12.5/x86_64 - ```shell - zypper addrepo "http://download.opensuse.org/repositories/Java:/Factory/SLE_12_SP2/Java:Factory.repo" - zypper addrepo "http://download.opensuse.org/repositories/server:/Kolab:/3.3/SLE_12/server:Kolab:3.3.repo" - zypper refresh - ``` +# Refresh the metadata +zypper refresh +``` ## Install the package @@ -81,27 +44,19 @@ You can install all Replication Server components with a single install command, To install all Replication Server components: ```shell -zypper install edb-xdb +zypper -n install edb-xdb ``` To install an individual component: ```shell -zypper install package_name +zypper install ``` -Where `package_name` is: - -| Package name | Component | -| -------------------- | -------------------------------------------------------------------------- | -| `edb-xdb-console` | EPRS Replication Console and the Replication Server Command Line Interface | -| `edb-xdb-publisher` | Publication server | -| `edb-xdb-subscriber` | Subscription server | +Where `` is: -## Initial configuration - -Before starting the publication server and subscription server, the `/etc/hosts` file must contain an entry for the host name that associates it to the host IP address as shown by the following example where `192.168.187.133` is the IP address and `linux-dm8s` is the host name: - -```shell -192.168.187.133 linux-dm8s -``` +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `edb-xdb-console` | Replication console and the Replication Server command line interface | +| `edb-xdb-publisher` | Publication server | +| `edb-xdb-subscriber` | Subscription server | diff --git a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx index b100c3171e0..cbfa97f0c2a 100644 --- a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx @@ -53,7 +53,7 @@ This example shows configuring SSL on a Postgres database server to show the use In the following example, the generated certificate signing request file is `server.csr`. The private key is generated as file server.key. -```shell +```text $ openssl req -new -text -nodes -subj '/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=enterprisedb' -keyout server.key -out server.csr Generating a 1024 bit RSA private key ......................................................++++++ @@ -67,26 +67,61 @@ writing new private key to 'server.key' Alternatively, you can use user name maps as defined in the `pg_ident.conf` file to permit more flexibility for the common name and database user name. Steps 8 and 9 describe the use of user name maps. +There are two options when entering the value for the common name field: the database user name and host name/ip-adress. If entering `CN=hostname/ip-address`, use the following command. +- Create root Certificate Authority (CA) private key (`root.key`) and root CA certificate (`root.crt`) files with these commands: + ```text + $ openssl genrsa -des3 -out root.key 4096 + Generating RSA private key, 4096 bit long modulus + ........++ + .........++ + e is 65537 (0x10001) + Enter pass phrase for root.key: + Verifying - Enter pass phrase for root.key: + + $ openssl req -x509 -new -nodes -key root.key -subj '/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=192.168.22.174' -sha256 -days 1024 -out root.crt + Enter pass phrase for root.key: + $ openssl genrsa -out server.key 2048 + Generating RSA private key, 2048 bit long modulus + ..........................................+++ + .........................................................................................+++ + e is 65537 (0x10001) + + Note: Please note in below command database server ip-address which is given as CN(Common Name) value for server.csr(server certificate signing request) file generation could not be identical as you have used above while generating root.crt file. It must be different. + + $ openssl req -new -sha256 -key server.key -subj '/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=192.168.18.2' -out server.csr + ``` + **Step 2:** Generate the self-signed certificate. The following generates a self-signed certificate to file `server.crt` using the certificate signing request file, `server.csr`, and the private key, `server.key`, as input. -```shell +```text $ openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt Signature ok subject=/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=enterprisedb Getting Private key ``` +The following command generates a server certificate with `CN=hostname/ip-address` to file `server.crt` using the certificate signing request file, `server.csr`, and the private root key, `root.key`, as input. + +```text +$ openssl x509 -req -in server.csr -CA root.crt -CAkey root.key -CAcreateserial -out server.crt -days 1024 -sha256 +Signature ok +subject=/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=localhost.localdomain +Getting CA Private Key +Enter pass phrase for root.key: +``` **Step 3:** Make a copy of the server certificate (`server.crt`) to use as the root Certificate Authority (CA) file (`root.crt`). -```shell +```text $ cp server.crt root.crt ``` +If following the instructions specific to `CN=hostname/ip-address`, make a copy of the `root.crt` file from Step 1. + **Step 4:** Delete the now redundant certificate signing request (`server.csr`). -```shell +```text $ rm server.csr ``` @@ -102,7 +137,7 @@ $ mv server.key /var/lib/edb/as14/data Set the ownership to the operating system account that owns the data subdirectory of the Postgres database server, which is either `enterprisedb` or `postgres` depending upon the installation mode you chose when you installed your Postgres database server (Oracle compatible or PostgreSQL compatible). -```shell +```text $ chown enterprisedb root.crt server.crt server.key $ chgrp enterprisedb root.crt server.crt server.key $ chmod 600 root.crt server.crt server.key @@ -152,7 +187,7 @@ hostssl edb,subnode all 192.168.2.0/24 cert clientcert=verify-full map=ss In other words, these are the permitted set of database user names that can be used by the publication server and subscription server to connect to the publication, subscription, or primary node databases. -```shell +```text # MAPNAME SYSTEM-USERNAME PG-USERNAME sslusers enterprisedb pubuser sslusers enterprisedb subuser @@ -179,7 +214,7 @@ Before you begin, configure the client for SSL with trigger mode. In our example, we use the copy of this self-signed certificate and key generated for the database server on the client side. - The default location of these files is `{user.home}/.postgresql(e.g/var/lib/edb/.postgresql/)`. The file location can be overridden using SSL connection parameters or Postgres SSL environmental variables, see [Setting non-default paths using environment variables](#setting-non-default-paths-using-environment-variables) for more information. + The default location of these files is `{user.home}/.postgresql(e.g/var/lib/edb/.postgresql/)`. The file location can be overridden using SSL connection parameters or Postgres SSL environmental variables, see [Setting non-default paths using environment variables](setting-non-default-paths-using-environment-variables) for more information. !!!note If you have installed Replication Server using the RPM install package from the EDB repository, the value of the {user.home} property is `/var/lib/edb/` and you need to create the `.postgresql` directory in this path to have a valid default client SSL directory path (`/var/lib/edb/.postgresql/`). @@ -205,6 +240,29 @@ Before you begin, configure the client for SSL with trigger mode. Make the following client/cert files available on the publication/subscription server using an SSL connection: - `xdb.keystore` - `xdb_pkcs.p12` +- If you generated the server certificate with `CN=hostname/ip-address`, you cannot use `server.crt/key` as client server/key. Instead, generate the client private key and ceriticate where CN value is specified as db user name. To do so, enter the following commands in the same location as above: + - `postgresql.key` + - `postgresql.crt` + - `postgresql.pk8` + - `root.crt` (copied from database server data directory) + ```text + $ openssl genrsa -out postgresql.key 2048 + Generating RSA private key, 2048 bit long modulus + ....................................................................................................+++ + ..............................................................................................................+++ + e is 65537 (0x10001) + $ openssl req -new -sha256 -key postgresql.key -subj "/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=enterprisedb" -out postgresql.csr + + Create the client certificate using above postgresql.csr certificate signing request and root.crt and root.key files will be given as input(root.crt and root.key files will be used we created in Configuring SSL on a Postgres database server section). + $ openssl x509 -req -in postgresql.csr -CA root.crt -CAkey root.key -CAcreateserial -out postgresql.crt -days 1024 -sha256 + Signature ok + subject=/C=US/ST=Massachusetts/L=Bedford/O=EnterpriseDB/OU=XDB/emailAddress=support@enterprisedb.com/CN=enterprisedb + Getting CA Private Key + Enter pass phrase for root.key: + $ openssl pkcs8 -topk8 -inform PEM -in postgresql.key -outform DER -out postgresql.pk8 -v1 PBE-MD5-DES -nocrypt + + $ cp /var/lib/edb/as14/data/root.crt + ``` **Step 1:** Using files `server.crt` and server.key located under the Postgres database server data subdirectory, create copies of these files and move them to the host where the publication server and subscription server are running. @@ -215,9 +273,15 @@ cp server.key xdb.key For this example, assume file `xdb.crt` is a copy of `server.crt` and `xdb.key` is a copy of `server.key`. +If you generated the server certificate with `CN=hostname/ip-address`, create xdb.keystore/xdb_pkcs.p12 with the `postgresql.crt` and `postgresql.ke`y client files as created with `CN=username` using the following commands : +```shell +$ cp postgresql.crt xdb.crt +$ cp postgresql.key xdb.key +``` + **Step 2:** Create a copy of `xdb.crt`. -```shell +```text $ cp xdb.crt xdb_root.crt $ ls -l total 12 @@ -226,9 +290,15 @@ total 12 -rw-r--r-- 1 user user 1346 Mar 15 10:00 xdb_root.crt ``` -**Step 3:** Create a distinguished encoding rules (DER) format of file `xdb_root.crt`. The generated DER format of this file is `xdb_root.crt.der`. The DER format of the file is required for the keytool program in the next step. +If you generated the server certificate with `CN=hostname/ip-address`, use the `root.crt file` from the database data directory in the following command to make `xdb_root.crt` file: ```shell +$ cp root.crt xdb_root.crt +``` + +**Step 3:** Create a distinguished encoding rules (DER) format of file `xdb_root.crt`. The generated DER format of this file is `xdb_root.crt.der`. The DER format of the file is required for the keytool program in the next step. + +```text $ openssl x509 -in xdb_root.crt -out xdb_root.crt.der -outform der $ ls -l total 16 @@ -244,7 +314,7 @@ You can find the keytool program under the `bin` subdirectory of the Java Runtim You are prompted for a new password. Save this password for the next step. -```shell +```text $ /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-1.el7_9.x86_64/jre/bin/keytool -keystore xdb.keystore -alias xdbstore -import -file xdb_root.crt.der Enter keystore password: Re-enter new password: @@ -275,7 +345,7 @@ You must specify the encrypted password with the `sslTrustStorePassword` configu Encrypt the password using the Replication Server CLI `encrypt` command. The following example shows this process encrypting the password contained in file `infile`. -```shell +```text $ export PATH=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-1.el7_9.x86_64/jre/bin:$PATH $ cd /usr/edb/xdb/bin $ java -jar edb-repcli.jar -encrypt -input ~/infile -output ~/pwdfile @@ -287,7 +357,7 @@ LGn6+AagiXqumxVHlOKk3w== You're prompted for a new password. Save this password for the next step. -```shell +```text $ openssl pkcs12 -export -in xdb.crt -inkey xdb.key -out xdb_pkcs.p12 Enter Export Password: Verifying - Enter Export Password: @@ -307,7 +377,7 @@ Specify the encrypted password with the `sslKeyStorePassword` configuration opti Encrypt the password using the Replication Server CLI `encrypt` command. -```shell +```text $ export PATH=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-1.el7_9.x86_64/jre/bin:$PATH $ cd /usr/edb/xdb/bin $ java -jar edb-repcli.jar -encrypt -input ~/infile -output ~/pwdfile @@ -321,7 +391,7 @@ LGn6+AagiXqumxVHlOKk3w== The following shows the SSL configuration options set for the files generated in this example. -```shell +```text sslTrustStore=/tmp/sslclient/xdb.keystore sslTrustStorePassword=LGn6+AagiXqumxVHlOKk3w== sslKeyStore=/tmp/sslclient/xdb_pkcs.p12 @@ -367,7 +437,7 @@ Make sure that the name of the certificates and key is the same as given in the Execute the following commands to change the permission of the certificates in `${user.home}/.postgresql`. -```shell +```text chmod 0644 root.crt postgresql.crt chmod 0600 postgresql.key chown postgres postgresql.key @@ -476,7 +546,7 @@ For publication, subscription, and primary node databases, in the URL Options fi `ssl=true&sslmode=verify-ca` !!! note - When a server certificate is created with the hostname as the CN value there is no need to specify `sslmode=verify-ca`. + `sslmode=verify-full` can be used if server certificates are generated by using hostname/IP. When a server certificate is created with the hostname/IP as the CN value there is no need to specify `sslmode=verify-ca` and replication server by default will take it `sslmode=verify-full`. You can specify the `ssl=true&sslmode=verify-ca` URL option on the Add Database dialog box.