Merge pull request #3017 from EnterpriseDB/release/2022-08-08

Release: 2022-08-08
EnterpriseDB · Aug 8, 2022 · aeeb3dc · aeeb3dc
2 parents a38696c + a57bd98
commit aeeb3dc
Show file tree

Hide file tree

Showing 44 changed files with 551 additions and 1,269 deletions.
diff --git a/product_docs/docs/biganimal/release/getting_started/02_azure_market_setup.mdx b/product_docs/docs/biganimal/release/getting_started/02_azure_market_setup.mdx
@@ -51,7 +51,7 @@ You are now able to:
 
 - [Log in to BigAnimal](#log-in)
 - [Invite new users](#invite-users)
-- [Set up your cloud service provider](02_connecting_to_your_cloud/01_connecting_your_own_cloud)
+- [Set up your cloud service provider](02_connecting_to_your_cloud/)
 
 ### Log in
 

diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx
@@ -45,7 +45,7 @@ Prior to creating your cluster, make sure you have enough resources. Without eno
 
 1. Select the number of standby replicas for your cluster. 
 
-1. Select the cloud provider for your cluster. If you're using your own account and haven't connected it to BigAnimal yet, see [Set up your cloud service provider](/biganimal/latest/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud/#setting-up-your-cloud-service-provider).
+1. Select the cloud provider for your cluster. If you're using your own account and haven't connected it to BigAnimal yet, see [Connecting to your cloud](/biganimal/latest/getting_started/02_connecting_to_your_cloud).
 
 ### Cluster Settings tab
 

diff --git a/product_docs/docs/biganimal/release/getting_started/identity_provider/index.mdx b/product_docs/docs/biganimal/release/getting_started/identity_provider/index.mdx
@@ -85,4 +85,4 @@ For step-by-step instructions for setting up specific identity providers, see:
 
 You and other users can log in to BigAnimal using your identity provider credentials.
 
-You can [Set up your cloud service provider](02_connecting_to_your_cloud/01_connecting_your_own_cloud) so that you or other users with the correct permissions can create clusters.
+You can [Set up your cloud service provider](/biganimal/latest/getting_started/02_connecting_to_your_cloud/) so that you or other users with the correct permissions can create clusters.
diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx
@@ -20,5 +20,5 @@ The Replication Server documentation describes the latest version including mino
 You can only upgrade to Replication Server 7.x from 6.2.15 or later 6.2.x point version. If you are running a version earlier than 6.2.15, you need to first upgrade to 6.2.15 or later 6.2.x point version before upgrading to 7.x.
 
 !!!note
-   Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments; however, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. 
+   Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments; however, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There is no downgrade path from version 7.x to version 6.2.x so it is essential to test the upgrade first before applying it to the production environment.  
 
diff --git a/...ntication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/...ntication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
@@ -27,22 +27,16 @@ Perform the following installations:
 
 Create users in Active Directory of the Windows server to map with the HTTP service principal for the PEM web application.
 
-1.  Open **Active Directory Users and Computers > &lt;DOMAIN_NAME> > Users**. Right-click and select **New > User**
+1.  Open **Active Directory Users and Computers > &lt;DOMAIN_NAME> > Users**. Right-click and select **New > User**.
 
     ![Active Directory Users and Computers](../../images/active_directory_users_and_computers.png)
 
 1.  Enter the user details.
 
-    ![Active Directory Users and Computers Create User](../../images/active_directory_users_and_computers_create_user.png)
-
 1.  Give the password and make sure to clear **User must change password at next logon**. Also select **User cannot change password** and **Password never expires**.
 
-    ![Active Directory Users and Computers set password](../../images/active_directory_users_and_computers_set_password.png)
-
 1.  Review the user details.
 
-    ![Active Directory Users and Computers User Details](../../images/active_directory_users_and_computers_user_details.png)
-
 1.  On the PEMServer Web Properties dialog box, add the users as members of the Domain Users group:
 
     ![PEM Server Web Properties](../../images/pem_server_web_properties_member_of.png)
@@ -74,17 +68,15 @@ Extract the key tables for the service principals and map them with the respecti
     !!! Note
         The command line argument `+rndpass` resets the password for the domain user pemserverweb to a random password. The `/target` option is optional. 
 
-1.  On the **Accounts** tab, Add Kerberos support for the user accounts.
+1.  On the **Accounts** tab, add Kerberos support for the user accounts.
 
    ![PEM Server Web Properties](../../images/pem_server_web_properties_account.png)
 
     !!! Note
-        On the **Accounts** tab, the user logon name shows **HTTP/pem.[email protected]**. The **Delegation** tab is enabled for the `pemserverweb` user.
+        On the **Accounts** tab, the user logon name shows **HTTP/pem.[email protected]**. The **Delegation** tab is enabled for the pemserverweb user.
 
 1.  On the **Delegation** tab, select **Trust this user for delegation to any service (Kerberos only)** for the users you created.
 
-   ![PEM Server Web Properties Delegation](../../images/pem_server_web_properties_delegation.png)
-
 1.  Copy both the key tables to the PEM server host or to the PEM web server and PEM backend database server hosts if installed on different hosts.
 
 1.  On the PEM server, move the key tables to the required location and change the ownership:

diff --git a/.../8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx b/.../8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx
@@ -39,8 +39,6 @@ Install the PEM agent package:
 
 When the installation is complete, you can review a list of the installed packages and dependencies.
 
-![](../../../images/pem_rpm_installation_agent.png)
-
 When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue.
 
 During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve.

diff --git a/...stalling_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx b/...stalling_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx
@@ -45,8 +45,6 @@ To request credentials for the repository, contact [EDB](https://www.enterprised
 
 When the installation is complete, you can review a list of the installed packages and dependencies.
 
-![](../../../images/pem_rpm_installation_agent.png)
-
 When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue.
 
 During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve.

diff --git a/...em/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx b/...em/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx
@@ -45,8 +45,6 @@ Install the PEM agent package:
 
 When the installation is complete, you can review a list of the installed packages and dependencies.
 
-![](../../../images/pem_rpm_installation_agent.png)
-
 When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue.
 
 During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve.

diff --git a/...em/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx b/...em/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx
@@ -46,8 +46,6 @@ To request credentials for the repository, contact [EDB](https://www.enterprised
 
 When the installation is complete, you can review a list of the installed packages and dependencies.
 
-![](../../../images/pem_rpm_installation_agent.png)
-
 When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue.
 
 During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve.

diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_pem_agent_on_windows.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_pem_agent_on_windows.mdx
@@ -18,65 +18,43 @@ To invoke the PEM agent installer, assume administrator privileges and navigate
 pem_agent-7.<x>.<x>-<x>-platform.exe
 ```
 
-The Setup screen opens, welcoming you to the PEM agent installer.
+1.  The Setup screen opens, welcoming you to the PEM agent installer. Select **Next**.
 
-![PEM Agent Wizard - Welcome dialog](../images/pem_agent_welcome_dialog.png)
+1.  Review the license agreement before selecting the appropriate radio button and accepting the agreement. Select **Next**.
 
-Select **Next**.
+1.  By default, the PEM agent is installed in the `C:\Program Files (x86)\edb\pem` directory. You can accept the default installation directory. Or you can modify the contents of the **Installation Directory** field, specifying an alternate installation directory for the PEM agent.
 
-![PEM Agent Wizard - License Agreement dialog](../images/pem_agent_windows_license_agreement.png)
+  - By default, the PEM agent installer places a certificate in the Administrator’s `%APPDATA%\pem` directory. Select **Show advanced options** to include a dialog box in the installation process that allows you to specify an alternate path for the certificate file.
 
-Review the license agreement before selecting the appropriate radio button and accepting the agreement. Select **Next**.
+  - Select **Register now?** to register the newly installed PEM agent with the PEM server.
 
-![PEM Agent Wizard - Installation Directory dialog](../images/pem_agent_windows_installation_directory.png)
+  - Select **Next**.
 
-By default, the PEM agent is installed in the `C:\Program Files (x86)\edb\pem` directory. You can accept the default installation directory. Or you can modify the contents of the **Installation Directory** field, specifying an alternate installation directory for the PEM agent.
+1.  Enter the connection details for the PEM server in the PEM Server Installation Details dialog box.
 
-By default, the PEM agent installer places a certificate in the Administrator’s `%APPDATA%\pem` directory. Select **Show advanced options** to include a dialog box in the installation process that allows you to specify an alternate path for the certificate file.
+  -   Specify the name or IP address of the system where the PEM database server resides in the **Host** field. If the PEM-HTTPD web server and PEM database are hosted on different systems, you must specify the host of the PEM database.
+  -   Specify the name of the database superuser in the **User Name** field.
+  -   Specify the password associated with the database superuser in the **Password** field.
+  -   Specify the port that PostgreSQL is monitoring in the **Port** field.
 
-Select **Register now?** to register the newly installed PEM agent with the PEM server.
+1.  Select **Next** to continue to pemAgent Service Account. The installer attempts to connect to the server to verify that the details are correct.
 
-Select **Next**.
+  !!! Note
+      The PEM server must allow connections from the PEM agent installer. If you encounter a connection error, confirm the connection properties specified in the PEM Server Installation Details dialog box are correct. Confirm that the `pg_hba.conf` file on the PEM server allows a connection to the server described in the error message.
 
-![PEM Agent Wizard - PEM Server Installation details dialog](../images/pem_agent_pem_server_windows_installation_details.png)
+1.  Provide the password for the edb account for the pemAgent service to run under. The agent certificate and key files are created in the `C:\Users\edb\AppData\Roaming\pem` directory. Select **Next**.
 
-Enter the connection details for the PEM server in the PEM Server Installation Details dialog box:
+1.  The tree displayed in the Browser panel of the PEM web interface displays the value entered in the **Description** field to identify the PEM agent. Specify a descriptive name for the agent, such as the hostname of the machine the agent is installed on or a name that reflects the host's functionality.
 
--   Specify the name or IP address of the system where the PEM database server resides in the **Host** field. If the PEM-HTTPD web server and PEM database are hosted on different systems, you must specify the host of the PEM database.
--   Specify the name of the database superuser in the **User Name** field.
--   Specify the password associated with the database superuser in the **Password** field.
--   Specify the port that PostgreSQL is monitoring in the **Port** field.
+  Provide a descriptive name, or accept the default provided by the PEM Agent host. Select **Next**.
 
-Select **Next** to continue to pemAgent Service Account. The installer attempts to connect to the server to verify that the details are correct.
+1.  If you selected **Show advanced options**, the Advanced Options dialog box opens. By default, the PEM agent installer places the certificate in the `C:\Program Files (x86)\edb\pem` directory. Specify an alternate path for the certificate, or accept the default and select **Next**.
 
-!!! Note
-    The PEM server must allow connections from the PEM agent installer. If you encounter a connection error, confirm the connection properties specified in the PEM Server Installation Details dialog box are correct. Confirm that the `pg_hba.conf` file on the PEM server allows a connection to the server described in the error message.
-
-![PEM Agent Wizard - pemAgent Service Account password dialog](../images/pem_agent_service_account_windows_password.png)
-
-Provide the password for the edb account for the pemAgent service to run undeer. The agent certificate and key files are created in the `C:\Users\edb\AppData\Roaming\pem` directory. Selct **Next**.
-
-![PEM Agent Wizard - Naming PEM Agent dialog](../images/pem_agent_windows_agent_details.png)
-
-The tree displayed in the Browser panel of the PEM web interface displays the value entered in the **Description** field to identify the PEM agent. Specify a descriptive name for the agent, such as the hostname of the machine the agent is installed on or a name that reflects the host's functionality.
-
-Provide a descriptive name, or accept the default provided by the PEM Agent host. Select **Next**.
-
-If you selected **Show advanced options**, the Advanced Options dialog box opens.
+1.  The wizard is ready to install the PEM agent. Select **Next**. 
 
-![PEM Agent Wizard - Advanced Options - Certificate Path dialog](../images/pem_agent_windows_advanced_options_certificate_path.png)
+1.  On the Ready to Install dialog box, select **Next**. The installer copies files to the system and registers the agent on the PEM server.
 
-By default, the PEM agent installer places the certificate in the `C:\Program Files (x86)\edb\pem` directory. Specify an alternate path for the certificate, or accept the default and select **Next**.
-
-The wizard is now ready to install the PEM Agent. Select **Next**.
-
-![PEM Agent Wizard - Ready to install](../images/pem_agent_windows_installation_ready_to_begin.png)
-
-On the Ready to Install dialog box, select **Next**. The installer copies files to the system and registers the agent on the PEM server.
-
-![PEM Agent Wizard - Finish Installation dialog](../images/pem_agent_windows_installation_complete.png)
-
-When the installation has completed, the PEM agent is running and reporting operating system and host data to the PEM server. To start monitoring Postgres instances on the host of the PEM agent, add them to PEM’s enterprise directory and bound them to the agent.
+  When the installation completes, the PEM agent is running and reporting operating system and host data to the PEM server. To start monitoring Postgres instances on the host of the PEM agent, add them to PEM’s enterprise directory and bound them to the agent.
 
 ## Invoking the agent installer from the command ine
 
@@ -111,9 +89,5 @@ Where:
 -   `pguser_password` specifies the password associated with the PEM database superuser.
 -   `agent_name` specifies a descriptive name for the PEM agent.
 
-```text
-EnterpriseDB is the leading provider of value-added products and services for the Postgres community. Please visit our website at www.enterprisedb.com.
-```
-
 !!! Note
     When configuring a shell/batch script run by a Windows agent that has PEM 7.11 or later version installed, set the `AllowBatchJobSteps` parameter to `True` in the `agent.cfg` file. The PEM agent doesn't execute any batch/shell script by default.
diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_windows/index.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_windows/index.mdx
@@ -38,11 +38,7 @@ The PEM server backend database can be an EDB distribution of the PostgreSQL or
 
 -   For troubleshooting the installation or configuration of the PEM agent, see [Troubleshooting PEM agent](../../troubleshooting_agent/).
 
-The PEM server installer also installs the software required to access the server using the PEM web interface. You can access the web interface with a supported version of your browser.
-
-![The PEM web interface](../../images/pem_web_interface.png)
-
-You can use the web interface to:
+The PEM server installer also installs the software required to access the server using the PEM web interface. You can access the web interface with a supported version of your browser. You can use the web interface to:
 -  Review information about objects that reside on monitored servers
 -  Manage databases and database objects that reside on monitored servers
 -  Review statistical information gathered by the PEM server
Original file line number	Diff line number	Diff line change
Expand Up		@@ -85,4 +85,4 @@ For step-by-step instructions for setting up specific identity providers, see:

		You and other users can log in to BigAnimal using your identity provider credentials.

		You can [Set up your cloud service provider](02_connecting_to_your_cloud/01_connecting_your_own_cloud) so that you or other users with the correct permissions can create clusters.
		You can [Set up your cloud service provider](/biganimal/latest/getting_started/02_connecting_to_your_cloud/) so that you or other users with the correct permissions can create clusters.