Merge pull request #1476 from EnterpriseDB/content/josh/pem-8.1.0-con…

…tent-fixes PEM 8.1.0 content fixes Former-commit-id: 2cbe31c
EnterpriseDB · Jun 15, 2021 · a438247 · a438247
2 parents 4beedd4 + 62805ac
commit a438247
Show file tree

Hide file tree

Showing 44 changed files with 669 additions and 886 deletions.
diff --git a/product_docs/docs/pem/8.1.0/images/sql_profiler.png b/product_docs/docs/pem/8.1.0/images/sql_profiler.png
diff --git a/product_docs/docs/pem/8.1.0/pem_admin/01_overview/02_installing_pem_overview.mdx b/product_docs/docs/pem/8.1.0/pem_admin/01_overview/02_installing_pem_overview.mdx
@@ -4,12 +4,12 @@ title: "Installing PEM - Overview"
 
 For detailed instructions about installing PEM, please consult the `PEM Installation Guides`, available at:
 
-   https://www.enterprisedb.com/docs/
+   <https://www.enterprisedb.com/docs/>
 
 The basic steps involved in the PEM installation process are:
 
-1. Install the PEM server components. The PEM server software and backend database (named pem) may reside on the same host as the supporting httpd server, or may reside on a separate host. The PEM server installer installs a PEM agent and the PEM Web client on the host of the PEM server.
+1.  Install the PEM server components. The PEM server software and backend database (named pem) may reside on the same host as the supporting httpd server, or may reside on a separate host. The PEM server installer installs a PEM agent and the PEM Web client on the host of the PEM server.
 
-2. Register each additional physical or virtual machine that you would like to manage with PEM. For convenience, PEM supports remote monitoring (an agent is not required to reside on the same host as the server that it monitors). Please note that a remote agent cannot retrieve all of the information available from a monitored server; you may wish to install an agent on each server host.
+2.  Register each additional physical or virtual machine that you would like to manage with PEM. For convenience, PEM supports remote monitoring (an agent is not required to reside on the same host as the server that it monitors). Please note that a remote agent cannot retrieve all of the information available from a monitored server; you may wish to install an agent on each server host.
 
-3. Install the SQL Profiler component into each Postgres instance on which you want to perform SQL capture and analysis. The SQL Profiler installer will prompt you for the location of your Postgres installation, and place the required software into that directory. The SQL Profiler plugin is already installed on Advanced Server instances, and requires only configuration to enable profiling.
+3.  Install the SQL Profiler component into each Postgres instance on which you want to perform SQL capture and analysis. The SQL Profiler installer will prompt you for the location of your Postgres installation, and place the required software into that directory. The SQL Profiler plugin is already installed on Advanced Server instances, and requires only configuration to enable profiling.
diff --git a/product_docs/docs/pem/8.1.0/pem_admin/01_overview/03_using_pem_web_interface.mdx b/product_docs/docs/pem/8.1.0/pem_admin/01_overview/03_using_pem_web_interface.mdx
diff --git a/product_docs/docs/pem/8.1.0/pem_admin/02_registering_server.mdx b/product_docs/docs/pem/8.1.0/pem_admin/02_registering_server.mdx
@@ -105,24 +105,22 @@ Use fields on the `PEM Agent` tab to specify connection details for the PEM agen
 
 -   Move the `Remote monitoring?` slider to `Yes` to indicate that the PEM agent does not reside on the same host as the monitored server. When remote monitoring is enabled, agent level statistics for the monitored server will not be available for custom charts and dashboards, and the remote server will not be accessible by some PEM utilities (such as Audit Manager, Capacity Manager, Log Manager, Postgres Expert and Tuning Wizard).
 
-- Use the drop-down listbox to the right of the `Bound agent` label to select a PEM agent . One agent can monitor multiple Postgres servers.  
+-   Use the drop-down listbox to the right of the `Bound agent` label to select a PEM agent . One agent can monitor multiple Postgres servers.  
 
 -   Enter the IP address or socket path that the agent should use when connecting to the database server in the `Host` field. By default, the agent will use the host address shown on the `General` tab. On a Unix server, you may wish to specify a socket path, e.g. `/tmp`.
 
 -   Enter the `Port` number that the agent will use when connecting to the server. By default, the agent will use the port defined on the `Properties` tab.
 
 -   Use the drop-down listbox in the `SSL` field to specify an SSL operational mode; specify require, prefer, allow, disable, verify-ca or verify-full. 
 
-
-| Mode              | Description                                                                                                                               |
---------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
-| require           | To require SSL encryption for transactions between the server and the agent.                                                              |
-| prefer            | To use SSL encryption between the server and the agent if SSL encryption is available.                                                    |
-| allow             | To allow the connection to use SSL if required by the server.                                                                             |
-| disable           | To disable SSL encryption between the agent and the server.                                                                               |
-| verify-ca         | To require SSL encryption, and to require the server to authenticate using a certificate registered by a certificate authority.           |
-| verify-full       | To require SSL encryption, and to require the server to authenticate using a certificate registered by a `trusted` certificate authority. |
-
+| Mode        | Description                                                                                                                               |
+| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| require     | To require SSL encryption for transactions between the server and the agent.                                                              |
+| prefer      | To use SSL encryption between the server and the agent if SSL encryption is available.                                                    |
+| allow       | To allow the connection to use SSL if required by the server.                                                                             |
+| disable     | To disable SSL encryption between the agent and the server.                                                                               |
+| verify-ca   | To require SSL encryption, and to require the server to authenticate using a certificate registered by a certificate authority.           |
+| verify-full | To require SSL encryption, and to require the server to authenticate using a certificate registered by a `trusted` certificate authority. |
 
 For more information about using SSL encryption, see the [PostgreSQL documentation](https://www.postgresql.org/docs/12.1/libpq-ssl.html).
 

diff --git a/product_docs/docs/pem/8.1.0/pem_bart/01_managing_bart.mdx b/product_docs/docs/pem/8.1.0/pem_bart/01_managing_bart.mdx
@@ -271,7 +271,6 @@ Use the fields within the `Times` box to specify the times at which the schedule
 -   Use the `Hours` field to select the hour at which the schedule will execute.
 -   Use the `Minutes` field to select the minute at which the schedule will execute.
 
-
 ## Restoring BART Backups
 
 You can restore the backups that you have earlier created using BART server on a target remote host. When you select a particular BART server, all the associated backups are listed in the Dashboard under `Initiated Server Backups`.

diff --git a/product_docs/docs/pem/8.1.0/pem_ent_feat/01_what's_new.mdx b/product_docs/docs/pem/8.1.0/pem_ent_feat/01_what's_new.mdx
@@ -13,4 +13,4 @@ The following changes have been made to Postgres Enterprise Manager to create ve
 -   Added ability to configure the following PEM tools without restarting the monitored server:
     -   Log Manager
     -   Audit Manager
-    -   Tuning Wizard
+    -   Tuning Wizard
diff --git a/product_docs/docs/pem/8.1.0/pem_ent_feat/02_pem_query_tool.mdx b/product_docs/docs/pem/8.1.0/pem_ent_feat/02_pem_query_tool.mdx
@@ -187,22 +187,21 @@ Use the `Notifications` tab to view the notifications using PostgreSQL `Listen/N
 
 Example:
 
-1. Execute ``LISTEN "foo"`` in first ``Query Tool`` session.
+1.  Execute `LISTEN "foo"` in first `Query Tool` session.
 
 ![Query Tool - notifications listen](../images/query_output_notifications_listen.png)
 
-2. In the another ``Query Tool`` session, execute ``Notify`` command or ``pg_notify``
-function to send the notification of the event together with the payload.
+2.  In the another `Query Tool` session, execute `Notify` command or `pg_notify`
+    function to send the notification of the event together with the payload.
 
 ![Query Tool - notifications notify](../images/query_output_notifications_notify.png)
 
-3. You can observe the ``Notification`` tab in the first ``Query Tool`` session
-where it shows the Recorded time, Event, Process ID, and the Payload of the
-particular channel.
+3.  You can observe the `Notification` tab in the first `Query Tool` session
+    where it shows the Recorded time, Event, Process ID, and the Payload of the
+    particular channel.
 
 ![Query Tool - Output Notifications panel](../images/query_output_notifications_panel.png)
 
-
 ## Query History Panel
 
 Use the `Query History` tab to review activity for the current session: