+
+overview registering_server pem_define_aws_instance_connection managing_certificates managing_configuration_settings managing_pem_server managing_pem_agent conclusion
+
+
\ No newline at end of file
diff --git a/product_docs/docs/pem/8.0.1/pem_agent/01_pem_architecture.mdx b/product_docs/docs/pem/8.0.1/pem_agent/01_pem_architecture.mdx
new file mode 100644
index 00000000000..db4f225458f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_agent/01_pem_architecture.mdx
@@ -0,0 +1,100 @@
+---
+title: "PEM Architecture"
+---
+
+Postgres Enterprise Manager (PEM) is a tool designed to monitor and manage multiple Postgres servers through a single GUI interface. PEM is capable of monitoring the following areas of the infrastructure:
+
+!!! Note
+ The term Postgres refers to either PostgreSQL or EDB Postgres Advanced Server.
+
+- **Hosts** - One or more servers (physical or virtual) and their operating systems.
+- **Servers** - One or more instances of PostgreSQL or EDB Postgres Advanced Server running on a host.
+- **Databases** - One or more databases and the schema objects (tables, indexes, etc.) within them.
+
+PEM consists of a number of individual software components; the individual components are described below.
+
+- **PEM Server** - The PEM Server is used as the data repository for monitoring data and as a server to which both Agents and Clients connect. The PEM server consists of an instance of PostgreSQL and an associated database for storage of monitoring data, and a server that provides web services.
+- **PEM Agent** - The PEM Agent is responsible for executing tasks and reporting statistics from the Agent host and monitored Postgres instances to the PEM server. A single PEM Agent can monitor multiple installed instances of Postgres that reside on one or many hosts.
+- **PEM Web Client** - The PEM web interface allows you to manage and monitor Postgres servers and utilize PEM extended functionality. The web interface software is installed with the PEM server and is accessed via any supported web browser.
+- **SQL Profiler** - SQL Profiler is a Postgres server plugin to record the monitoring data and query plans to be analysed by the SQL Profiler tool in PEM. This is an optional component of PEM, but the plugin must be installed into each instance of Postgres with which you wish to use the SQL Profiler tool. The SQL Profiler may be used with any supported version of an EDB distribution of a PostgreSQL server or Advanced Server (not just those managed through the PEM server). See the [PEM SQL Profiler Configuration Guide](https://www.enterprisedb.com/docs/pem/latest/) for details and supported versions.
+
+**PEM architecture**
+
+The following architectural diagram illustrates the relationships between the PEM server, clients, and managed as well as unmanaged Postgres servers.
+
+
+
+PEM Architecture
+
+## The PEM Server
+
+
+
+The PEM server consists of an instance of Postgres, an instance of the Apache web-server providing web services to the client, and a PEM Agent. PEM utilizes a server-side cryptographic plugin to generate authentication certificates.
+
+The instance of Postgres (a database server) and an instance of the Apache web-server ( HTTPD) can be on the same host or on separate hosts.
+
+- **Postgres Instance (Database server)** - This is the backend database server. It hosts a database named **pem** which acts as the repository for PEM Server. The **pem** database contains several schemas that store metric data collected from each monitored host, server, and database.
+ - **pem** - This schema is the core of the PEM application. It contains the definitions of configuration functions, tables, or views required by the application.
+ - **pemdata** - This schema stores the current snapshot of the monitored data.
+ - **pemhistory** - This schema stores the historical monitored data.
+- **Apache Web Server (HTTPD)** - The PEM Web Application is deployed as a WSGI application with HTTPD to provide web services to the client. It is comprised of the following:
+ - **Web content presentation** - The presentation layer is created by the Web Application (for example Browser, login page,..).
+ - **Rest API** - The REST API allows integration with other apps and services.
+ - **Database Server Administration/Management** - Database server administration and management activities like CREATE, ALTER, DROP, etc. can be performed for managed as well as unmanaged servers.
+ - **Dashboard/Chart generation** - Internally, the web application includes functionality that generates Dashboards and Charts.
+ - **Management Tools** - The Audit Manager, Capacity Manager, Log Manager, Postgres Expert, Postgres Log Analysis Expert, and the Tuning Wizard are made available in the Web Application.
+ - Other tools provide functionality on managed or unmanaged servers:
+ - **SQL Profiler UI Integration** - SQL Profiler generates easily analyzed traces of session content.
+ - **Query Editor/Data View** - The Query editor allows you to query, edit, and view data.
+ - **Debugger** - The Debugger helps you debug queries.
+ - **Performance Diagnostics** - Performance Diagnostics help you analyze the performance of Advanced Server.
+
+We recommend that you use a dedicated machine to host production instances of the PEM backend database. The host may be subject to high levels of data throughput, depending on the number of database servers that are being monitored and the workloads the servers are processing.
+
+## The PEM Agent
+
+
+
+The PEM Agent is responsible for the collection of monitoring data from the machine and operating system, as well as from each of the Postgres instances to which they are bound. Each PEM Agent can monitor one physical or virtual machine and is capable of monitoring multiple database servers locally - installed on the same system, or remotely - installed on other systems. It is also responsible for executing other tasks that may be scheduled by the user (for example, server shutdowns, SQL Profiler traces, user-defined jobs).
+
+A PEM Agent is installed by default on the PEM Server along with the installation of the PEM Server. It is generally referred to as a PEM Agent on the PEM Host. Separately, the PEM Agent can also be installed on the other servers hosting the Postgres instances to be monitored using PEM.
+
+Whether monitoring locally or remotely, the PEM Agent connects to the PEM Server using PostgreSQL’s libpq, using SSL certificate-based authentication. The PEM Agent installer in Windows and pemworker CLI in Linux is responsible for registering each agent with the PEM Server, and generating and installing the required certificates.
+
+Please note that there is only one-way traffic between the PEM Agent and PEM Server; the PEM Agent always connects to the PEM Server.
+
+The PEM Agent must be able to connect to each database server that it monitors. This connection is made over a TCP/IP connection (or optionally a Unix Domain Socket on Unix hosts), and may optionally use SSL. The user must configure the connection and authentication to the monitored server.
+
+Once configured, each agent collects statistics and other information on the host and each database server and database that it monitors. Each piece of information is known as a **metric** and is collected by a **probe**. Most probes will collect multiple metrics at once for efficiency. Examples of the metrics collected include:
+
+- Disk I/O statistics
+- Network statistics
+- Database server version string
+- Database server configuration option (GUC) values
+- Table access statistics
+- Table and index sizes
+
+A list of PEM probes can be found [here](https://www.enterprisedb.com/docs/pem/latest/pem_online_help/04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/01_pem_probes/).
+
+By default, the PEM Agent bound to the database server collects the OS/Database monitoring statistics and also runs any scheduled tasks/jobs for that particular database server, storing data in the pem database on the PEM server.
+
+The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in the `pem` database on the PEM server and is then processed by the PEM Agent on the PEM Host by default. However, processing by other PEM Agents can be enabled by adjusting the SNMP/SMTP and Nagios parameters of the PEM Agents.
+
+To see more information about these parameters see [Server Configuration](https://www.enterprisedb.com/docs/pem/latest/pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options/).
+
+## The PEM Web Client
+
+The PEM client is a web-based application that runs in supported browsers. The client's web interface connects to the PEM server and allows direct management of managed or unmanaged servers, and the databases and schemas that reside on them.
+
+The client allows you to use PEM functionality that makes use of the data logged on the server through features such as the dashboards, the Postgres Log Analysis Expert, and Capacity Manager.
+
+## The SQL Profiler Plugin
+
+You are not required to install the SQL Profiler plugin on every server, but you must install and configure the plugin on each server on which you wish to use the SQL Profiler. You may also want to install and configure SQL Profiler on un-monitored development servers. For ad-hoc use also, you may temporarily install the SQL Profiler plugin.
+
+The plugin is installed with the EDB Postgres Advanced Server distribution but must be installed separately for use with PostgreSQL. The SQL Profiler installer is available from the [EDB website](https://www.enterprisedb.com/downloads/edb-postgres-enterprise-manager).
+
+SQL Profiler may be used on servers that are not managed through PEM, but to perform scheduled traces, a server must have the plugin installed, and must be managed by an installed and configured PEM agent.
+
+For more information about using SQL Profiler, see the [PEM SQL Profiler Guide](https://www.enterprisedb.com/docs/pem/latest/)
diff --git a/product_docs/docs/pem/8.0.1/pem_agent/02_registering_agent.mdx b/product_docs/docs/pem/8.0.1/pem_agent/02_registering_agent.mdx
new file mode 100644
index 00000000000..a956169bac9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_agent/02_registering_agent.mdx
@@ -0,0 +1,106 @@
+---
+title: "Registering an Agent"
+---
+
+Each PEM agent must be *registered* with the PEM server. The registration process provides the PEM server with the information it needs to communicate with the agent. The PEM agent graphical installer for Windows supports self-registration for the agent. You must use the `pemworker` utility to register the agent if the agent is on a Linux host.
+
+The RPM installer places the PEM agent in the `/usr/edb/pem/agent/bin` directory. To register an agent, include the `--register-agent` keywords along with registration details when invoking the pemworker utility:
+
+`pemworker --register-agent`
+
+Append command line options to the command string when invoking the `pemworker` utility. Each option should be followed by a corresponding value:
+
+| Option | Description |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--pem-server` | Specifies the IP address of the PEM backend database server. This parameter is required. |
+| `--pem-port` | Specifies the port of the PEM backend database server. The default value is 5432. |
+| `--pem-user` | Specifies the name of the Database user (having superuser privileges) of the PEM backend database server. This parameter is required. |
+| `--pem-agent-user` | Specifies the agent user to connect the PEM server backend database server. |
+| `--cert-path` | Specifies the complete path to the directory in which certificates will be created. If you do not provide a path, certificates will be created in: On Linux, ~/.pem On Windows, %APPDATA%/pem |
+| `--config-dir` | Specifies the directory path where configuration file can be found. The default is the <pemworker path>/../etc. |
+| `--display-name` | Specifies a user-friendly name for the agent that will be displayed in the PEM Browser tree control. The default is the system hostname. |
+| `--force-registration` | Include the force_registration clause to instruct the PEM server to register the agent with the arguments provided; this clause is useful if you are overriding an existing agent configuration. The default value is Yes. |
+| `--group` | The name of the group in which the agent will be displayed. |
+| `--team` | The name of the database role, on the PEM backend database server, that should have access to the monitored database server. |
+| `--owner` | The name of the database user, on the PEM backend database server, who will own the agent. |
+| `--allow_server_restart` | Enable the allow-server_restart parameter to allow PEM to restart the monitored server. The default value is True. |
+| `--allow-batch-probes` | Enable the allow-batch-probes parameter to allow PEM to run batch probes on this agent. The default value is False. |
+| `--batch-script-user` | Specifies the operating system user that should be used for executing the batch/shell scripts. The default value is none; the scripts will not be executed if you leave this parameter blank or the specified user does not exist. |
+| `--enable-heartbeat-connection` | Enable the enable-heartbeat-connection parameter to create a dedicated heartbeat connection between PEM Agent and server to update the active status. The default value is False. |
+| `--enable-smtp` | Enable the enable-smtp parameter to allow the PEM agent to send the email on behalf of the PEM server.The default value is False. |
+| `--enable-snmp` | Enable the enable-snmp parameter to allow the PEM agent to send the SNMP traps on behalf of the PEM server.The default value is False. |
+| `-o` | Specify if you want to override the configuration file options. |
+
+Before using any PEM feature for which a database server restart is required by the pemagent (such as Audit Manager, Log Manager, or Tuning Wizard), you must first set the value for `allow_server_restart` to `true` in the `agent.cfg` file.
+
+!!! Note
+ When configuring a shell/batch script run by a PEM agent that has PEM 7.11 or later version installed, the user for the `batch_script_user` parameter must be specified. It is strongly recommended that a non-root user is used to run the scripts. Using the root user may result in compromising the data security and operating system security. However, if you want to restore the pemagent to its original settings using root user to run the scripts, then the `batch_script_user` parameter value must be set to `root`.
+
+You can use the `PEM_SERVER_PASSWORD` environment variable to set the password of the PEM Admin User. If the `PEM_SERVER_PASSWORD` is not set, the server will use the `PGPASSWORD` or `.pgpass` file when connecting to the PEM Database Server.
+
+Failure to provide the password will result in a password authentication error; you will be prompted for any other required but omitted information. When the registration is complete, the server will confirm that the agent has been successfully registered.
+
+## Setting PEM Agent Configuration Parameters
+
+The PEM agent RPM installer creates a sample configuration file named `agent.cfg.sample` in the `/usr/edb/pem/agent/etc` directory. When you register the PEM agent, the `pemworker` program creates the actual agent configuration file (named `agent.cfg`). You must modify the `agent.cfg` file, adding the following configuration parameter:
+
+`heartbeat_connection = true`
+
+You must also add the location of the `ca-bundle.crt` file (the certificate authority). By default, the installer creates a `ca-bundle.crt` file in the location specified in your `agent.cfg.sample` file. You can copy the default parameter value from the sample file, or, if you use a `ca-bundle.crt` file that is stored in a different location, specify that value in the `ca_file` parameter:
+
+`ca_file=/usr/libexec/libcurl-pem7/share/certs/ca-bundle.crt`
+
+Then, use a platform-specific command to start the PEM agent service; the service is named `pemagent`.
+
+On a RHEL or CentOS 7.x or 8.x host, use systemctl to start the service:
+
+`systemctl start pemagent`
+
+The service will confirm that it is starting the agent; when the agent is registered and started, it will be displayed on the `Global Overview` dashboard and in the Object browser tree control of the PEM web interface.
+
+For information about using the pemworker utility to register a server, please see the [PEM Administrator's Guide](https://www.enterprisedb.com/docs/pem/latest/pem_admin/)
+
+## Using a non-root User Account to Register a PEM Agent
+
+To use a non-root user account to register a PEM agent, you must first install the PEM agent as a root user. After installation, assume the identity of a non-root user (for example, `edb`) and perform the following steps:
+
+1. Create the `.pem` directory and `logs` directory and assign read, write, and execute permissions to the file:
+
+ ```text
+ mkdir /home/
+
+pem_architecture registering_agent managing_pem_agent pem_agent_troubleshooting conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_bart/01_managing_bart.mdx b/product_docs/docs/pem/8.0.1/pem_bart/01_managing_bart.mdx
new file mode 100644
index 00000000000..7718867e422
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_bart/01_managing_bart.mdx
@@ -0,0 +1,292 @@
+---
+title: "Managing a BART Server"
+---
+
+Postgres Enterprise Manager (PEM) is designed to assist database administrators, system architects, and performance analysts when administering, monitoring, and tuning PostgreSQL and Advanced Server database servers.
+
+The EDB Backup and Recovery Tool (BART) is an administrative utility providing simplified backup and recovery management for multiple local or remote EDB Postgres Advanced Server and PostgreSQL database servers. For more information about BART, please visit the EDB website at:
+
+
+
+managing_bart conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_ent_feat/01_what's_new.mdx b/product_docs/docs/pem/8.0.1/pem_ent_feat/01_what's_new.mdx
new file mode 100644
index 00000000000..b034874e7ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_ent_feat/01_what's_new.mdx
@@ -0,0 +1,19 @@
+---
+title: "What's New"
+---
+
+The following features have been added to Postgres Enterprise Manager 8.0:
+
+- **Webhooks**: You can now use PEM to send event based notifications to webhook endpoints like third party systems or partner applications.
+- **Performance Diagnostics**: You can now use Performance Diagnostic tool with PostgreSQL 10 or higher versions after installing `edb_wait_states` plugin.
+- **PEM Backend Database**: You can now use PostgreSQL or EDB Postgres Advanced Server 11 or higher versions only as backend databases.
+- **Enhanced Alerting**: You can now replace alert placeholders inside the script and also can view more informative and contextual alert details for few alerts.
+- **Enhanced BART Integration**: You can now configure `bart_socket_name` and also parameters like `--checksum-algorithm` and `--disable-checksum` through PEM.
+- **Security Best Practices**: You can now view the `PEM Security Best Practices` guide from our edb-docs website. It will help to setup PEM in a secure way to minimize the risk of vulnerabilities.
+- **Other features and changes include**:
+ - You can use the `Macros` feature in the `Query tool`.
+ - You can view trigger function under the respective trigger node.
+ - You can download the utility files at the client side using `Storage Manager`.
+ - You can use the open `Query tool` tab to change the database connection.
+ - You can rename the `Query tool` and `Debugger` tab.
+ - You can ignore the owner while comparing the objects through `Schema diff` tool.
diff --git a/product_docs/docs/pem/8.0.1/pem_ent_feat/02_pem_query_tool.mdx b/product_docs/docs/pem/8.0.1/pem_ent_feat/02_pem_query_tool.mdx
new file mode 100644
index 00000000000..539c2d8b08e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_ent_feat/02_pem_query_tool.mdx
@@ -0,0 +1,243 @@
+---
+title: "The PEM Query Tool"
+---
+
+PEM contains a feature-rich Interactive Development Environment (IDE) that allows you to issue ad-hoc SQL queries against Postgres servers.
+
+You can access the Query Tool via the `Query Tool` menu option on the `Tools` menu, or through the context menu of select nodes of the Browser tree control. The Query Tool allows you to:
+
+- Issue ad-hoc SQL queries.
+- Execute arbitrary SQL commands.
+- Edit the result set of a SELECT query if it is [updatable](../pem_online_help/08_toc_pem_developer_tools/02_query_tool/#updatable-result-set).
+- Displays current connection and transaction status as configured by the user.
+- Save the data displayed in the output panel to a CSV file.
+- Review the execution plan of a SQL statement in either a text, a graphical format or a table format (similar to - Select `Save` to save the selected content of the SQL Editor panel in a file.
- Select Save As to open a new browser dialog and specify a new location to which to save the selected content of the SQL Editor panel. | Accesskey + S | +| `Save Data Changes` | Click the `Save Data Changes` icon to save the data changes (insert, update, or delete) in the Data Output Panel to the server. | F6 | +| `Find` | Use the `Find` menu to search, replace, or navigate the code displayed in the SQL Editor:
- Select `Find` to provide a search target, and search the SQL Editor contents.
- Select `Find next` to locate the next occurrence of the search target.
- Select `Find previous` to move to the last occurrence of the search target.
- Select `Pesistent find` to identify all occurrences of the search target within the editor.
- Select `Replace` to locate and replace (with prompting) individual occurrences of the target.
- Select `Replace all` to locate and replace all occurrences of the target within the editor.
- Select `Jump` to navigate to the next occurrence of the search target. | Cmd+F
Cmd+G
Cmd+Shift+G
Cmd+Shift+F
Alt+G | +| `Copy` | Click the `Copy` icon to copy the content that is currently highlighted in the Data Output panel. when in View/Edit data mode. | Accesskey + C | +| `Paste` | Click the `Paste` icon to paste a previously row into a new row when in View/Edit data mode. | Accesskey + P | +| `Delete` | Click the `Delete` icon to mark the selected rows for deletion. These marked rows get deleted when you click the `Save Data Changes` icon. | Accesskey + D | +| `Edit` | Use options on the `Edit` menu to access text editing tools; the options operate on the text displayed in the SQL Editor panel when in Query Tool mode:
- Select `Indent Selection` to indent the currently selected text.
- Select `Unindent Selection` to remove indentation from the currently selected text.
- Select `Inline Comment Selection` to enclose any lines that contain the selection in SQL style comment notation.
- Select `Inline Uncomment Selection` to remove SQL style comment notation from the selected line.
- Select `Block Comment` to enclose all lines that contain the selection in C style comment notation. This option acts as a toggle. | Tab
Shift+Tab
Cmd+/
Cmd+.
Shift+Cmd+/ | +| `Filter` | Click the `Filter` icon to set filtering and sorting criteria for the data when in View/Edit data mode. Click the down arrow to access other filtering and sorting options:
-Click `Sort/Filter` to open the sorting and filtering dialogue.
- Click `Filter by Selection` to show only the rows containing the values in the selected cells.
- Click `Exclude by Selection` to show only the rows that do not contain the values in the selected cells.
- Click `Remove Sort/Filter` to remove any previously selected sort or filtering options. | Accesskey + F | +| `Limit Selector` | Select a value in the `Limit Selector` to limit the size of the dataset to a number of rows. | Accesskey + R | +| `Stop` | Click the `Stop` icon to cancel the execution of the currently running query. | Accesskey + Q | +| `Execute/Refresh` | Click the `Execute/Refresh` icon to either execute or refresh the query highlighted in the SQL editor panel. Click the down arrow to access other execution options:
- Add a check next to `Auto-Rollback` to instruct the server to automatically roll back a transaction if an error occurs during the transaction.
- Add a check next to `Auto-Commit` to instruct the server to automatically commit each transaction. Any changes made by the transaction will be visible to others, and durable in the event of a crash. | F5 | +| `Explain` | Click the `Explain` icon to view an explanation plan for the current query. The result of EXPLAIN is displayed graphically on the `Explain` tab of the output panel, and in text form on the `Data Output` tab. | F7 | +| `Explain analyze` | Click the `Explain analyze` icon to invoke an EXPLAIN ANALYZE command on the current query.Navigate through the Explain Options menu to select options for the EXPLAIN command:
- Select `Verbose` to display additional information regarding the query plan.
- Select `Costs` to include information on the estimated startup and total cost of each plan node, as well as the estimated number of rows and the estimated width of each row.
- Select `Buffers` to include information on buffer usage.
- Select `Timing` to include information about the startup time and the amount of time spent in each node of the query.
- Select `Summary` to include the summary information about the query plan. | | +| `Commit` | Click the `Commit` icon to commit the transaction. | Shift+CTRL+M | +| `Rollback` | Click the `Rollback` icon to rollback the transaction. | Shift+CTRL+R | +| `Clear` | Use options on the `Clear` drop-down menu to erase display contents:
- Select `Clear Query Window` to erase the content of the SQL Editor panel.
- Select `Clear History` to erase the content of the `History` tab. | Accesskey + L | +| `Download as CSV` | Click the `Download as CSV` icon to download the result set of the current query to a comma-separated list. You can specify the CSV settings through `Preferences -> SQL Editor -> CSV output` dialogue. | F8 | +| `Macros` | Click the `Macros` icon to manage the macros. You can create, edit or clear the `macros` through Manage Macros option. | | + +## The SQL Editor Panel + +The `SQL editor` panel is a workspace where you can manually provide a query, copy a query from another source, or read a query from a file. The SQL editor features syntax coloring and auto-completion. + + + +To use auto-complete, begin typing your query; when you would like the Query editor to suggest object names or commands that might be next in your query, press the Control+Space key combination. For example, type `\*SELECT \* FROM\*` (with a trailing space), and then press the `Control+Space` key combination to select from a popup menu of auto-complete options. + + + +After entering a query, select the `Execute/Refresh` icon from the toolbar. The complete contents of the SQL editor panel will be sent to the database server for execution. To execute only a section of the code that is displayed in the SQL editor, highlight the text that you want the server to execute, and click the `Execute/Refresh` icon. + + + +The message returned by the server when a command executes is displayed on the `Messages` tab. If the command is successful, the `Messages` tab displays execution details. + + + +Options on the `Edit` menu offer functionality that helps with code formatting and commenting: + +- The auto-indent feature will automatically indent text to the same depth as the previous line when you press the Return key. +- Block indent text by selecting two or more lines and pressing the Tab key. +- Implement or remove SQL style or toggle C style comment notation within your code. + +You can also `drag and drop` certain objects from the tree-view to save time spent typing long object names. Text containing the object name will be fully qualified with the schema name. Double quotes will be added if required. For functions and procedures, the function name along with parameter names will be pasted in the Query Tool. + +## The Data Output Panel + +The `Data Output` panel displays data and statistics generated by the most recently executed query. + + + +### Data Output Tab + +The `Data Output` tab displays the result set of the query in a table format. You can: + +- Select and copy from the displayed result set. +- Use the `Execute/Refresh` options to retrieve query execution information and set query execution options. +- Use the `Download as CSV` icon to download the content of the `Data Output` tab as a comma-delimited file. +- Edit the data in the result set of a `SELECT` query if it is updatable. + +A result set is updatable if: + +- All columns are either selected directly from a single table, or they are not actually a table column (for example, the concatenation of two columns). Only columns that are selected directly from the table are editable, other columns are read-only. +- All the primary key columns or OIDs of the table are selected in the result set. + +Any columns that are renamed or selected more than once are also read-only. + +!!! Note + To work with an updatable query result set, you must have `psycopg2` driver version 2.8 or above installed. + +Editable and read-only columns are identified using pencil and lock icons (respectively) in the column headers. + + + +An updatable result set is similar to the `Data Grid` in `View/Edit Data` mode, and can be modified in the same way. + +If Auto-commit is `off`, data changes are made as part of the ongoing transaction; if no transaction is ongoing a new one is initiated. The data changes are not committed to the database unless the transaction is committed. + +If any errors occur during saving (for example, trying to save a NULL into a column with a NOT NULL constraint) the data changes are rolled back to an automatically created SAVEPOINT to ensure any previously executed queries in the ongoing transaction are not rolled back. + +All rowsets from previous queries or commands that are displayed in the `Data Output` panel will be discarded when you invoke another query; open another query tool browser tab to keep your previous results available. + +### Explain Tab + +To generate the `Explain` or `Explain Analyze` plan of a query, click on `Explain` or `Explain Analyze` button in the toolbar. + +More options related to `Explain` and `Explain Analyze` can be selected from the drop down on the right side of `Explain Analyze` button in the toolbar. + + + +Please note that PEM generates the `Explain [Analyze]` plan in JSON format. + +On successful generation of `Explain` plan, it will create three tabs/panels under the `Explain` panel. + +### Graphical Tab + +Hover over an icon on the `Graphical` tab to review information about that item; a popup window will display information about the selected object. For information on JIT statistics, triggers and a summary, hover over the icon on top-right corner; a similar popup window will be displayed when appropriate. + +Please note that `EXPLAIN VERBOSE` cannot be displayed graphically. + +Use the download button on top left corner of the `Explain` canvas to download the plan as an SVG file. Please note that `Download as SVG` feature is not supported on Internet Explorer. + + + +The query plan that accompanies the `Explain analyze` is available on the `Data Output` tab. + +### Analysis Tab + +The `Analysis` tab shows the plan details in table format, it generates a format similar to the format available at `explain.depsez.com`. Each row of the table represents the data for a `Explain Plan Node`. The output may contain the node information, exclusive timing, inclusive timing, actual vs. planned rows, actual rows, planned rows, or loops. When you select a row, the child rows of that selected row are marked with an orange dot. + +If the percentage of the exclusive/inclusive timings of the total query time is: + +Greater than 90 --> Red + +Greater than 50 --> Orange (between red and yellow) + +Greater than 10 --> Yellow + +If the planner has misestimated the number of rows (actual vs planned) by: + +10 times --> Yellow color + +100 times --> Orange (between Red and Yellow) color + +1000 times --> Red color + + + +### Statistics Tab + +The `Statistics` tab displays information in two tables: + +- `Statistics per Node Type` tells you how many times each node type was referenced. +- `Statistics per Table` tells you how many times each table was referenced by the query. + + + +### Messages Tab + +Use the `Messages` tab to view information about the most recently executed query: + + + +If the server returns an error, the error message will be displayed on the `Messages` tab, and the syntax that caused the error will be underlined in the SQL editor. If a query succeeds, the `Messages` tab displays how long the query took to complete and how many rows were retrieved: + + + +### Notifications Tab + +Use the `Notifications` tab to view details of the asynchronous notifications that a client process may have sent: + + + +You can see details such as recorded time of the asynchronous notification event, name of the event or channel, process ID of the client process that has sent the notification, and the payload string that might have been sent along with the notification. + +## Query History Panel + +Use the `Query History` tab to review activity for the current session: + + + +The `Query History` tab displays information about recent commands: + +- The date and time that a query was invoked. +- The text of the query. +- The number of rows returned by the query. +- The amount of time it took the server to process the query and return a result set. +- Messages returned by the server (not noted on the `Messages` tab). +- The source of the query (indicated by icons corresponding to the toolbar). + +You can show or hide the queries generated internally by pgAdmin (during `View/Edit Data` or `Save Data` operations). + +To erase the content of the `Query History` tab, select `Clear history` from the `Clear` drop-down menu. + +Query history is maintained across sessions for each database on a per-user basis when running in `Query Tool` mode. In `View/Edit Data` mode, history is not retained. By default, the last 20 queries are stored for each database. This can be adjusted in `config_local.py` by overriding the `MAX_QUERY_HIST_STORED` value. + +## Connection Status + +Use the `Connection status` feature to view the current connection and transaction status by clicking on the status icon in query tool: + + + +## Macros + +Query Tool Macros enable you to execute pre-defined SQL queries with a single key press. Pre-defined queries can contain the placeholder $SELECTION$. Upon macro execution, the placeholder will be replaced with the currently selected text in the Query Editor pane of the Query Tool. + + + +To create a macro, select the *Manage Macros* option from the *Macros* menu on the *Query Tool*. Select the key you wish to use, enter the name of the macro, and the query, optionally including the selection placeholder, and then click the *Save* button to store the macro. + + + +To clear a macro, select the macro on the *Manage Macros* dialogue, and then click the *Clear* button. + + + +The server will prompt you for confirmation to clear the macro. + + + +To clear all macros, click on the *Clear* button on left side of the key. The server will prompt you for confirmation to clear all the rows. + + + +To execute a macro, simply select the appropriate shortcut keys, or select it from the *Macros* menu. + + diff --git a/product_docs/docs/pem/8.0.1/pem_ent_feat/03_pem_schema_diff_tool.mdx b/product_docs/docs/pem/8.0.1/pem_ent_feat/03_pem_schema_diff_tool.mdx new file mode 100644 index 00000000000..37e21c0db46 --- /dev/null +++ b/product_docs/docs/pem/8.0.1/pem_ent_feat/03_pem_schema_diff_tool.mdx @@ -0,0 +1,78 @@ +--- +title: "The PEM Schema Diff Tool" +--- + +**Schema Diff** is a feature that allows you to compare schema objects between two database schemas. Use the `Tools` menu to access Schema Diff. + +The Schema Diff feature allows you to: + +- Compare and synchronize the database schemas (from source to target). +- Visualize the differences between database schemas. +- List the differences in SQL statement for target schema objects. +- Generate synchronization scripts. + +!!! Note + The source and target databases must be of the same major version. + +Click on `Schema Diff` under the `Tools` menu to open a selection panel. Choose the source and target servers, databases, and schemas that will be compared. After selecting the objects, click on the `Compare` button. + +You can open multiple copies of `Schema Diff` in individual tabs simultaneously. To close a tab, click the `X` in the upper-right hand corner of the tab bar. + + + +Use the `Preferences` dialog to specify if `Schema Diff` should open in a new browser tab. Set `Open in new browser tab` option to `true`. + +The `Schema Diff` panel is divided into two panels; an `Object Comparison panel` and a `DDL Comparison panel`. + +## The Schema Diff Object Comparison Panel + +In the object comparison panel, you can select the source and target servers of the same major version, databases, and schemas to be compared. You can select any server listed under the browser tree whether it is connected or disconnected. If you select a server that is not connected then it will prompt you for the password before using the server. + +Next, select the databases that will be compared. The databases can be the same or different (and within the same server or from different servers). + +Lastly, select the source and target schemas which will be compared. + + + +After you select servers, databases, and schemas, click on the `Compare` button to obtain the `Comparison Result`. + + + +Use the drop-down lists of Functions, Materialized Views, Tables, Trigger Functions, Procedures, and Views to view the DDL statements of all the schema objects. + +In the upper-right hand corner of the object comparison panel is a `Filter` option that you can use to filter the schema objects based on the following comparison criteria: + +- `Identical` – If the object is found in both schemas with the same SQL statement, then the comparison result is identical. +- `Different` – If the object is found in both schemas but have different SQL statements, then the comparison result is different. +- `Source Only` – If the object is found in source schema only and not in target schema, then the comparison result is source only. +- `Target Only` – If the object is found in target schema only and not in source schema, then the comparison result is target only. + + + +Click on any of the schema objects in the object comparison panel to display the DDL statements for that object in the `DDL Comparison` panel. + +## Schema Diff DDL Comparison Panel + +The `DDL Comparison` panel displays three columns: + +- The first column displays the DDL statement of the object from the source schema. +- The second column displays the DDL statement of the object from the target schema. +- The third column displays the difference in the SQL statement of the target schema object. + + + +You can review the DDL statements of all the schema objects to check for the differences in the SQL statements. + +You can also use the Schema Diff tool to generate a SQL script of the differences found in the target schema object based on the SQL statement of the source schema object. To generate the script, select the checkboxes of the schema objects in the object comparison panel and then click on the `Generate Script` button in the upper-right hand corner of the object comparison panel. + + + +Select the schema objects and click on the `Generate Script` button to open the `Query Tool` in a new tab, with the difference in the SQL statement displayed in the `Query Editor`. + +If you have clicked on the schema object to check the difference generated in the `DDL Comparison` Panel, and you have not selected the checkbox of the schema object, PEM will open the `Query Tool` in a new tab, with the differences in the SQL statements displayed in the `Query Editor`. + + + +You can also use the `Copy` button to copy the difference generated in the `DDL Comparison` panel. + +Apply the SQL Statement in the target schema to synchronize the schemas. diff --git a/product_docs/docs/pem/8.0.1/pem_ent_feat/04_performance_monitoring_and_management.mdx b/product_docs/docs/pem/8.0.1/pem_ent_feat/04_performance_monitoring_and_management.mdx new file mode 100644 index 00000000000..10be850c1ae --- /dev/null +++ b/product_docs/docs/pem/8.0.1/pem_ent_feat/04_performance_monitoring_and_management.mdx @@ -0,0 +1,1159 @@ +--- +title: "Performance Monitoring and Management" +--- + +PEM contains built-in functionality that implements enterprise-wide performance monitoring of all managed servers. While you can customize many aspects of the various performance monitoring aspects of PEM, you can also elect to accept the recommended defaults that come out-of-the-box with the product. + + + +The top-level dashboard is the `Global Overview`. The Global Overview presents a status summary of all the servers and agents that are being monitored by the PEM server, a list of the monitored servers, and the state of any currently triggered alerts. + +## Using Dashboards to View Performance Information + +PEM displays performance statistics through a number of dashboards; each dashboard contains a series of summary views that contain charts, graphs and tables that display the statistics related to the selected object. + +The PEM client displays the `Global Overview` dashboard when it connects to the PEM server. Additional dashboards provide statistical information about monitored objects. These include the: + +**Alerts Dashboard** + +The Alerts dashboard displays the currently triggered alerts. If opened from the Global Overview, the dashboard displays the current alerts for all monitored nodes on the system; if opened from a node within a server, the report will reflect alerts related to that node, and all monitored objects that reside below that object in the tree control. + +**Audit Log Analysis dashboard** + +For Advanced Server users, the Audit Log Analysis dashboard allows you to browse the audit logs that have been collected from instances that have audit logging and collection enabled. + +**Database Analysis dashboard** + +The Database Analysis dashboard displays performance statistics for the selected database. + +**I/O Analysis dashboard** + +The I/O Analysis dashboard displays I/O activity across various areas such as object DML activity, log operations and more. + +**Memory Analysis dashboard** + +The Memory Analysis dashboard supplies statistics concerning various memory-related metrics for the Postgres server. + +**Object Activity Analysis dashboard** + +The Object Activity Analysis dashboard provides performance details on tables/indexes of a selected database. + +**Operating System Analysis dashboard** + +The Operating System Analysis dashboard supplies information regarding the performance of the underlying machine’s operating system. + +**Probe Log Analysis Dashboard** + +The Probe Log Analysis dashboard displays any error messages returned by a PEM agent. + +**Server Analysis dashboard** + +The Server Analysis dashboard provides general performance information about the overall operations of a selected Postgres server. + +**Server Log Analysis dashboard** + +The Server Log Analysis dashboard allows you to filter and review the contents of server logs that are stored on the PEM server. + +**Session Activity Analysis dashboard** + +The Session Activity Analysis dashboard provides information about the session workload and lock activity for the selected server + +**Session Waits Analysis dashboard** + +The Session Waits Analysis dashboard provides an overview of the current DRITA wait events for an Advanced Server session. + +**Storage Analysis dashboard** + +The Storage Analysis dashboard displays space-related metrics for tablespaces and objects. + +**System Waits Analysis dashboard** + +The System Waits Analysis dashboard displays a graphical analysis of system wait information for an Advanced Server session. + +**Streaming Replication Analysis dashboard** + +The Streaming Replication Analysis dashboard displays statistical information about WAL activity for a monitored server and allows you to monitor the status of Failover Manager clusters. + +There are two ways to open a dashboard; you can: + +- Select an active dashboard name from the `Dashboards` menu (accessed via the Management menu). +- Right click on the name of a monitored object in the tree control and select the name of the dashboard you would like to review from the Dashboards menu. + +Each dashboard is displayed on the `Monitoring` tab in the main panel of the client window. After opening a dashboard, you can navigate to other dashboards within the same tab. + +Each dashboard header includes navigation menus that allow you to navigate to other dashboards; use your browsers forward and back icons to scroll through previously-viewed dashboards. Use the Refresh icon to update the current dashboard. + +Options on the `Dashboard Configuration` dialog allow you to link the time lines of all of the line graphs on the dashboard. To open the `Dashboard Configuration` dialog, click the Settings icon displayed in the dashboard header. + + + +Use fields on the `Dashboard Configuration` dialog to control attributes of the charts displayed on the dashboard: + +- Set the Link timelines of all the line charts slider to Enable to indicate that the specified timeline should be applied to line graphs displayed on the dashboard; if set to Disable, your preferences will be preserved for later use, but will not modify the amount of data displayed. +- Use the `Days` selector to specify the number of days of gathered data that should be displayed on line graphs. +- Use the `Hour(s)` selector to specify the number of hours of gathered data that should be displayed on line graphs. +- Check the box next to Remember configuration for this dashboard to indicate that the customized time span should be applied to the current dashboard only; if left unchecked, the time span will be applied globally to line graphs on all dashboards. + +Please note that settings specified on the `Dashboard Configuration` dialog are applied only to the current user's session. + +## Managing Custom Dashboards + +PEM displays performance statistics through a number of system-defined dashboards; each dashboard contains a series of summary views that contain charts, graphs and tables that display statistics related to the selected object. You can use the `Manage Dashboards` tab to create and manage custom dashboards that display the information that is most relevant to your system. + + + +To create a custom dashboard, click the `Create New Dashboard` link (located in the Quick Links section of the Manage Dashboards tab). + +To modify an existing dashboard, click the edit icon to the left of a dashboard name. The dashboard editor will open, displaying the definition of the dashboard. When you've finished modifying the dashboard's definition, click the `Save` button to preserve your changes; click `Cancel` to exit without saving your changes. + +To delete a dashboard, click the delete icon to the left of a dashboard name. A popup will ask you to confirm that you wish to delete the dashboard; click `OK` to delete the selected dashboard. + +### Creating a Custom Dashboard + +You can use the PEM dashboard editor to create or modify a user-defined dashboard. The custom dashboard may include pre-defined charts, user-defined charts or a mix of pre-defined and user-defined charts. + + + +Use the fields in the `Configure` section to specify general information about the dashboard: + +- Specify a name for the dashboard in the `Name` field. The name specified will also be the title of the dashboard if the title is displayed. +- Use the `Level` drop-down listbox to specify the level of the PEM hierarchy within the PEM client on which the dashboard will be displayed. A dashboard may be accessed via the Dashboards menu on a Global level, an Agent level, the Server level or the Database level. Each selected level within the list will expose a different set of metrics on which the custom dashboard's charts may be based. +- Provide a description of the dashboard in the Description field. + +Provide information in the fields in the `Ops dashboard options` box if the dashboard will be used as an Ops dashboard: + +- Set the `Ops Dashboard?` field to Yes to instruct the server to create a dashboard that is formatted for display on an Ops monitor. +- Set the `Show Title?` field to Yes to display the dashboard name at the top of the Ops dashboard. +- Use the `Font` drop-down list box to select a custom font style for the title. The selected font style will be displayed in the Preview box. +- Use the `Font size` drop-down list box to select a custom font size for the title. The selected font style will be displayed in the Preview box. + +Use the `Permissions` box to specify the users that will be able to view the new dashboard: + +- Set the `Share with all slider` to Yes to instruct the server to allow all Teams to access the dashboard, or set Share with all to No to enable the Access permissions field. +- Use the `Access permissions` field to specify which roles can view the new dashboard. Click in the field, and select from the list of users to add a role to the list of users with dashboard access. + +When you've completed the `Configure Dashboard` section, click the arrow in the upper-right corner to close the section, and access the `Dashboard Layout Design` section. + + + +Click the edit icon in a section header to specify a section name; then, click the add icon (+) to add a chart to the section. + + + +Use the arrows to the right of each chart category to display the charts available and select a chart. + + + +Use the chart detail selectors to specify placement details for the chart: + +- Use the `Chart width` selector to indicate the width of the chart; select 50% to display the chart in half of the dashboard, or 100% to use the whole dashboard width. + +- Use the `Chart alignment` selector to indicate the position of the chart within the section: + + Select `Left` to indicate that the chart should be left-justified. + + Select `Center` to indicate that the chart should be centered. + + Select `Right` to indicate that the chart should be right-justified. + +Please note that tables are always displayed centered. + +When creating or editing a custom dashboard, you can use drag and drop to re-arrange the charts within a section or to move a chart to a different section. + +To add another chart to your dashboard, click the add icon (+) in the section header. When you've finished editing the dashboard, click the `Save` button to save your edits and exit. + +To exit without saving your changes, click the `Cancel` button. + +### Creating an Ops Dashboard + +You can use the PEM dashboard editor to create a custom dashboard formatted for display on an Ops monitor. An Ops dashboard displays the specified charts and graphs, while omitting header information and minimizing extra banners, titles, and borders. + + + +To create an `Ops dashboard`, provide detailed information about the Ops display in the `Ops dashboard options` section of the `Create Dashboard` dialog. + +- Set the `Ops Dashboard?` field to `Yes` to instruct the server to create a dashboard that is formatted for display on an Ops monitor. +- Set the `Show Title?` field to `Yes` to display the dashboard name at the top of the Ops dashboard. +- Use the `Font` drop-down list box to select a custom font style for the title. The selected font style will be displayed in the `Preview` box. +- Use the `Font size` drop-down list box to select a custom font size for the title. The selected font style will be displayed in the `Preview` box. + +After adding charts and tables to the Ops dashboard, click the `Save` button to save your work. You can then access the dashboard by navigating through the Dashboards menu of the hierarchy level specified in the `Level` field on the `New Dashboard` dialog. + +## Using the Manage Charts tab + +You can use the `Manage Charts` tab to access dialogs that allow you to create or modify a custom line chart or table, or import a Capacity Manager template for use in a custom chart. After defining a chart, you can display the chart on a custom dashboard. To open the `Manage Charts` tab, select `Manage Charts...` from the PEM client `Management` menu. + + + +The `Manage Charts` tab provides a `Quick Links` menu that allows you to access dialogs to: + +- `Create a New Chart` for use on a custom dashboard. +- `Import a Capacity Manager` template to use as a template for creating a custom chart. +- Access online `Help`. + +The `Custom Charts` table displays a list of user-defined charts; when a chart is newly added, the font displays in green. When you add an additional chart or refresh the screen, the name of the chart is displayed in black. + + + +Use the search box in the upper-right hand corner of the `Custom Charts` table to search through your custom charts. Specify a: + +- Chart name +- Type +- Level +- Metrics Category + +Use icons to the left of a charts name in the `Custom Charts` table to manage a chart: + +- Click the edit icon to open the `Chart Configuration` wizard and modify aspects of the chart or table. +- Click the delete icon to delete the selected chart. + +### Creating a Custom Chart + +Click the `Create New Chart` icon in the `Quick Links` section of the `Manage Charts` tab to open the `Create Chart` wizard. The wizard will walk you through the steps required to define a new chart. + + + +Use the fields on the `Configure Chart` dialog to specify general information about the chart: + +- Specify the name of the chart in the `Name` field. +- Use the drop-down listbox in the `Category` field to specify the category in which this chart will be displayed; when adding a custom chart to a custom dashboard, the chart will be displayed for selection in the category specified. +- Use the radio buttons in the `Type` field to specify if the chart will be a `Line chart` or a `Table`. +- Provide a description of the chart in the `Description` field. The description will be displayed to the user viewing the chart (on a custom dashboard) when they click the information icon. + +When you've completed the fields on the `Configure Chart` dialog, click `Next` to continue. + + + +Use the fields on the `Select Metrics` dialog to select the metrics that will be displayed on the chart. + +- Use the `Metric level` drop-down listbox to specify the level of the PEM hierarchy from which you wish to select metrics. You can specify Agent, Database, or Server. Each level offers access to a unique set of probes and metrics. + +- Use the tree control in the Available metrics box to select the metrics that will be displayed on the chart. + + If you are creating a table, you may only select metrics from one probe; each node of the tree control lists the metrics returned by a single probe. Expand a node of the tree control, and check the boxes to the left of a metric name to include that metric data in the table. + + If you are creating a line chart, expand the nodes of the tree control and double-click each metric that you would like to include in the chart. + +- Use the fields in the Selected metrics panel to specify how the metric data will be displayed in your chart. The selection panel displays the name of the metric in the (non-modifiable) Metric \[Probe] column. You can: + + - Click the garbage can icon to delete a metric from the list of selected metrics. + - Use the drop-down listboxes in the `Selection Criteria` column to specify the order of the data displayed. + - Use the `Limit` field to specify the number of rows in a table or lines in a chart: + + The maximum number of lines allowed in a chart is 32. + + The maximum number of rows allowed in a table is 100. + +- If you are creating a line chart, PEM supports comparisons of cross-hierarchy metrics. + + - Click the `compare icon` to open a selection box that allows you to select one or more probe-specific attributes (i.e. CPUs, interfaces, databases, etc.) to compare in the chart. + - Click the `copy` icon to apply your selections to all of the metrics for the same probe. When the popup opens, click `Yes` to confirm that other selections for the same probe will be overwritten, or `No` to exit the popup without copying the attributes. + +When you've completed the fields on the `Select Metrics` dialog, click `Next` to continue. + + + +Use the fields on the `Set Options` dialog to specify display options for your chart: + +- Use the `Auto Refresh` field to specify the number of minutes between chart updates - choose a value from 1 to 120. The default auto refresh rate is 2 minutes. + +Use fields under the Line chart options heading to specify display preferences for a line chart: + +- Use the `Points to plot` field to specify the maximum number of points that will be plotted on the chart. +- Use the fields to the right of the Historical span label to specify how much historical data should be displayed on the chart: +- Use the `Day(s)` field to specify the number of days of historical data that should be included on the chart. +- Use the `Hour(s)` field to specify the number of hours of historical data that should be included on the chart. +- Use the `Minute(s)` field to specify the number of minutes of historical data that should be included on the chart. + +Use the fields in the `Data extrapolation` box to specify if PEM should generate extrapolated data based on historical data: + +- Click the `No Extrapolation` label to omit extrapolated data from the chart. +- Click the `Span` label to use the Days and Hours selectors to specify the period of time spanned by the metrics on the chart. +- Click the `Threshold` label to use threshold selectors to specify a maximum or minimum value for the chart. + +When you've completed the fields on the `Set Options` dialog, click `Next` to continue. + + + +Use the fields on the `Set Permissions` dialog to specify display options for your chart. + +- Set the `Share with all slider` to `Yes` to indicate that the chart will be available to all authorized users, or `No` to restrict access to the users or groups specified in the Access permissions field. +- Use the `Access permissions` field to select the group or groups that will have access to the chart. + + + +When you've finished defining the chart, click `Finish` to save your edits and add your chart to the list on the `Manage Charts` tab. + +### Importing a Capacity Manager Template + +Click the `Import Capacity Manager Template` icon in the Quick Links section of the `Manage Charts` tab to open the `Create Chart` dialog, and use a Capacity Manager template as a starting point for a chart or table. + + + +When the `Create Chart` dialog opens, provide information about the custom chart: + +- Use the drop-down listbox in the `Import capacity template` field to select the name of the template on which the chart will be based. +- Specify the name of the chart in the `Name` field. +- Use the drop-down listbox in the `Category` field to specify the category in which this chart will be displayed. When adding a custom chart to a custom dashboard, the chart will be displayed for selection in the Category specified. +- Use the radio buttons in the `Type` field to specify if the chart will be a `Line chart` or a `Table`. +- Provide a description of the chart in the `Description` field. The description will be displayed to the user viewing the chart (on a custom dashboard) when they click the information icon. + +Click `Next` to continue to the Select Metrics dialog. + + + +The `Select Metrics` window allows you to review the metrics specified by the selected template. The bottom panel of the chart editor displays the metrics that will be included in the chart. The metrics included in the chart are not modifiable via the chart editor; to modify the metrics, you must use the Capacity Manager utility to update the template. + +When you've reviewed the metrics, click `Next` to continue to the Set Options dialog. + + + +Use the fields on the `Set Options` window to specify display options for your chart: + +- Use the `Auto Refresh` field to specify the number of minutes between chart updates - choose a value from 1 to 120. The default auto refresh rate is 2 minutes. + +Use the fields in the `Data extrapolation` box to specify the time period covered by the chart. You can either: + +- click the `Historical days and extrapolated days` label and provide: + - the number of days of historical data that should be charted in the `Historical` field. + - the number of projected days that should be charted in the `Extrapolated` field. +- or, click the Historical days and threshold label and provide: + - the number of days of historical data that should be charted in the `Historical` field + - the `threshold` value at which the chart will end. + +When you've completed the Set Options window, click `Next` to continue. + + + +Use the fields on the `Set Permissions` window to specify display options for your chart: + +- Set the `Share with all slider` to Yes to indicate that the chart will be available to all authorized users, or No to restrict access to the users or groups specified in the Access permissions field. +- Use the `Access permissions` field to select the group or groups that will have access to the chart. + +When you've finished defining the chart, click `Finish` to save your edits and add your chart to the list on the `Manage Charts` tab. + +## Probes + +A `probe` is a scheduled task that retrieves information about the database objects that are being monitored by the PEM agent. PEM uses the collected information to build the graphs displayed on each homepage. The `Manage Probes` tab (accessed via the `Management` menu) allows you to modify the data collection schedule and the length of time that PEM will retain information returned by a specific probe. + +Unless otherwise noted, Postgres Enterprise Manager enables the probes listed in the table below: + +| Probe Name | Information Monitored by Probe | Level | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Background Writer Statistics | This probe monitors information about the background writer. The information includes:
The number of timed checkpoints
The number of requested checkpoints
The number of buffers written (by checkpoint)
The number of buffers written (by background writer)
The number of background writer cycles
The number of background buffers written
The number of buffers allocated | Server | +| Blocked Session Information | This probe provides information about blocked sessions. | Server | +| CPU Usage | This probe monitors CPU Usage information. | Agent | +| Data and Log File Analysis | This probe monitors information about log files. The information includes:
The name of the log file
The directory in which the log file resides | Server | +| Database Statistics | This probe monitors database statistics. The information includes:
The number of backends
The number of transactions committed
The number of transactions rolled back
The number of blocks read
The number of blocks hit
The number of rows returned
The number of rows fetched
The number of rows inserted
The number of rows updated
The number of rows deleted | Server | +| Disk Busy Info | This probe monitors information about disk activity.
Note: This probe is not supported on Mac OS X, Solaris or HP-UX | Agent | +| Disk Space | This probe monitors information about disk space usage. The information includes:
The amount of disk space used
The amount of disk space available | Agent | +| EDB Audit Configuration | This probe monitors the audit logging configuration of EDB Postgres Advanced Server. | Server | +| Failover Manager Cluster Info | This probe monitors a Failover Manager cluster, returning information about the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server | +| Failover Manager Node Status | This probe monitors a Failover Manager cluster, returning detailed about each node within the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server | +| Function Statistics | This probe monitors a database, retrieving information about functions. The information includes:
Function names
Argument types
Return values | Database | +| Index Size | This probe monitors a database, retrieving information about indexes. The information includes:
The name of the index
The time the data was gathered
The size of the index (in MB's) | Database | +| Index Statistics | This probe monitors index statistics. The information includes:
The number of index scans
The number of rows read
The number of rows fetched
The number of blocks read
The number of blocks hit | Database | +| Installed Packages | This probe monitors the packages that are currently installed. The information gathered includes:
The name of the installed package
The version of the installed package
The date and time that the probe executed | Agent | +| IO Analysis | This probe monitors disk I/O information in. The information includes:
The number of blocks read
The number of blocks written
The date and time that the probe executed
Note: This probe is not supported on Mac OS X | Agent | +| Load Average | This probe monitors CPU load averages. The information includes:
The 1-minute load average
The 5-minute load average
The 15-minute load average
Note: This probe is not supported on Windows | Agent | +| Lock Information | This probe monitors lock information. The information includes:
The database name
The lock type
The lock mode
The process holding the lock | Server | +| Memory Usage | This probe monitors information about system memory usage. | Agent | +| Network Statistics | This probe monitors network statistics. The information includes:
The interface IP address
The number of packets sent
The number of packets received
The number of bytes sent
The number of bytes received
The link speed (in MB/second) | Agent | +| Number of Prepared Transactions | This probe stores the number of prepared transactions. | Server | +| Number of WAL Files | This probe monitors the number of WAL files. | Server | +| Object Catalog: Database | This probe monitors a list of databases and their properties The information includes:
The database name
The database encoding type
If the database allows user connections or system connections | Server | +| Object Catalog: Foreign Key | This probe monitors a list of foreign keys and their properties. The information includes:
The name of the table that contains the foreign key
The name of the table that the foreign key references
The name of the database in which the table resides
The name of the schema in which the table resides | Schema | +| Object Catalog: Function | This probe monitors a list of functions and their properties. The information includes:
The name of the function
The name of the schema in which the function resides
The name of the database in which the function resides | Schema | +| Object Catalog: Index | This probe monitors a list of indexes and their properties. The information includes:
The name of the index
The name of the table that the index is associated with
The name of the database in which the indexed table resides | Schema | +| Object Catalog: Schema | This probe monitors a list of schemas and their associated databases and servers. | Database | +| Object Catalog: Sequence | This probe monitors a list of sequences and their properties. | Schema | +| Object Catalog: Table | This probe monitors a list of table information. The information includes:
The table name
The name of the schema in which the table resides
The name of the database in which the schema resides
A Boolean indicator that indicates if the table has a primary key | Schema | +| Object Catalog: Tablespace | This probe monitors a list of tablespaces. | Server | +| Operating System Information | This probe monitors the operating system details and boot time. | Agent | +| Package Catalog | This probe monitors the packages that are currently available for installation. The information gathered includes:
The package name
The package version | Agent | +| PG HBA Conf | This probe monitors authentication configuration information from the pg_hba.conf file. | Server | +| Server Information | This probe monitors server information. | Server | +| Session Information | This probe monitors session information. The information includes:
The name of the session user
The date and time that the session connected to the server
The status of the session at the time that the information was gathered (idle, waiting, etc)
The client address and port number | Server | +| Settings | This probe monitors the values currently assigned to GUC variables. | Server | +| SQL Protect | This probe monitors a server, retrieving information about SQL injection attacks. | Server | +| Slony Replication | This probe monitors lag data for clusters replicated using Slony. | Database | +| Streaming Replication | This probe monitors a cluster that is using streaming replication, retrieving information about:
The sent Xlog location (in bytes)
The write Xlog location (in bytes)
The flush Xlog location (in bytes)
The replay Xlog location (in bytes)
The Xlog lag (in segments)
The Xlog lag (in pages) | Server | +| Streaming Replication Lag Time | This probe monitors a cluster that is using streaming replication, retrieving lag information about:
Replication lag time (in seconds)
Current status of replication (running/paused) | Server | +| Streaming Replication Database Conflicts | This probe monitors a database that is using streaming replication, retrieving information about any conflicts that arise. This includes information about queries that have been canceled due to:
The # of drop tablespace conflicts
The # of lock timeout conflicts
The # of old snapshot conflicts
The # of pinned buffer conflicts
The # of deadlock conflicts | Server | +| Table Bloat | This probe monitors information about the current table bloat. The information includes:
The name of the table
The name of the schema in which the table resides
The estimated number of pages
The estimated number of wasted pages
The estimated number of bytes per row | Database | +| Table Frozen XID | This probe monitors the frozen XID of each table. | Schema | +| Table Size | This probe monitors table statistics. The information includes:
The number of sequential scans
The number of sequential scan rows
The number of index scans
The number of index scan rows
The number of rows inserted
The number of rows updated
The number of rows deleted
The number of live rows
The number of dead rows
The last VACUUM
The last auto-vacuum
The last ANALYZE
The last auto-analyze
The number of pages estimated by ANALYZE
The number of rows estimated by ANALYZE | Database | +| Table Statistics | This probe monitors a list of tablespaces and their sizes. | Server | +| Tablespace Size | This probe monitors a list of tablespaces and their sizes. | Server | +| User Information | This probe monitors a list of the current users. The stored information includes:
The user name
The user type (superuser vs. non-superuser)
The server to which the user is connected | Server | +| WAL Archive Status | This probe monitors the status of the WAL archive. The stored information includes:
The # of WAL archives done
The # of WAL archives pending
The last archive time
The # of WAL archives failed
The time of the last failure | Server | +| xDB Replication | This probe monitors lag data for clusters replicated using xDB replication. | Database | + +## Customizing Probes + +A probe is a scheduled task that returns a set of performance metrics about a specific monitored object. A probe retrieves statistics from a monitored server, database, operating system or agent. You can use the `Manage Probes` tab to override the default configuration and customize the behavior of each probe. + +To open the `Manage Probes` tab, select `Manage Probes...` from the `Management` menu. The `Manage Probes` tab opens in the PEM client. + + + +The `Manage Probes` tab provides a set of Quick Links that you can use to create and manage probes: + +- Click the `Manage Custom Probes` icon to open the `Custom Probes` tab and create or modify a custom probe. +- Click the `Copy Probes` icon to open the Copy Probe dialog, and copy the probe configurations from the currently selected object to one or more monitored objects. + +A probe monitors a unique set of metrics for each specific object type (server, database, database object, or agent); select the name of an object in the tree control to review the probes for that object. + +To modify the properties associated with a probe, highlight the name of a probe, and customize the settings that are displayed in the Probes table: + +- Move the `Default` switch in the `Execution Frequency` columns to `N` to enable the Minutes and Seconds selectors, and specify a non-default value for the length of time between executions of the probe. +- Move the `Default` switch in the `Enabled?` column to `No` to change the state of the probe, and indicate if the probe is active or not active. + +!!! Note + If data from a disabled probe is used in a chart, the chart will display an information icon in the upper-left corner that allows you to enable the probe by clicking the provided link. + +- Move the `Default` switch in the `Data Retention` column to `No` to enable the Day(s) field and specify the number of days that information gathered by the probe is stored on the PEM server. + +The `Manage Probes` tab may display information about probes that cannot be modified from the current node. If a probe cannot be modified from the current dialog, the switches are disabled. Generally, a disabled probe can be modified from a node that is higher in the hierarchy of the PEM client tree control; select another object in the tree control to modify which probes are displayed or enabled in the `Manage Probes` tab. + +### Creating a Custom Probe + +You can use the `PEM Custom Probes` tab to create a new probe or modify an existing user-defined probe. To open the `Custom Probes` tab, select the `Manage Custom Probes...` icon from the `Manage Probes` tab. + + + +Use the `Show System Probes?` switch to display or conceal the system probes on the `Custom Probes` tab. + +You can use the `Custom Probes` tab to create a new probe or modify an existing probe. To create a new probe, click the `Add` icon in the upper-right corner of the tab; provide a name for the new probe in the `Probe Name` column. Then, select the `Edit` icon (located to the left of the probe name) to review or add the probe definition. + + + +Use the fields on the `General` tab to modify the definition of an existing probe or to specify the properties of a new probe: + +- Use the `Probe Name` field to provide a name for a new probe. + +- Use the `Collection method` field to specify the probe type. Use the drop-down listbox to select: + + - SQL - the probe will gather information via a SQL statement. + - WMI - the probe will gather information via a Windows Management Instrumentation extension. + - Batch - the probe will use a command-script or shell-script to gather information. + + Before creating a batch probe on a Linux system, you must modify the `agent.cfg` file, setting the `allow_batch_probes` parameter equal to `true`, and restart the PEM agent. The `agent.cfg` file is located in one of the following directories: + + > - If you have installed PEM using graphical installer: `/opt/edb/pem/agent/etc/agent.cfg` + > - If you have installed PEM using RPM: `/usr/edb/pem/agent/etc/agent.cfg` + + On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`. + + Please note that batch probes are platform-specific. If you specify a collection method of Batch, you must specify a platform type in the Platform field. + + To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of `agent.cfg` file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. + + To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. + +- Use the `Target Type` drop-down listbox to select the object type that the probe will monitor. Target type is disabled if Collection method is WMI. + +- Use the `Minutes` and `Seconds` selectors to specify how often the probe will collect data. + +- Use the `Probe Enable?` switch to specify if the probe in enabled by default. Specify Yes to enable the probe by default, or No to specify that the probe is disabled by default. + +!!! Note + If data from a disabled probe is used in a chart, the chart will display an information icon in the upper-left corner that allows you to enable the probe by clicking the provided link. + +- Use the `Data Retention` field to specify the number of days that gathered information will be retained in the probe's history table. +- Use the switch next to `Discard from history` to specify if the server should create a history table for the probe. Select `Yes` to discard probe history, or `No` to retain the probe history in a table. +- Use the `Platform` drop-down listbox to specify the type of platform that the probe will monitor. This field is enabled only when the Collection method is Batch. + + + +Use the `Columns` tab to define the columns in which the probe data will be stored. Navigate to the `Columns` tab, and click the `Add` button (in the upper-right corner) to define a new column. After a providing a column name in the `Name` field, click the `Edit` button (to the left of the new column name) to provide information about the column: + +- Provide a descriptive name for the column in the `Name` field. + +- The `Internal Name` field is not enabled for user-defined probes. + +- Use the `Column Type` drop-down listbox to specify if the column is a Key column (a primary key) or a Non key column. Non-key columns are generally metric items (values that can be graphed). + +- Use the `Data Type` drop-down listbox to specify the type of data that will be stored in the column. + +- Use the `Unit` field to specify the unit of measure that applies to the metric stored in the column. This unit is displayed on the Y-Axis of a custom chart or a Capacity Manager chart. This is an optional field. + +- Use the `Graphable` switch to specify if the defined metric may be graphed, and that the probe should be accessible from the Capacity Manager or Manage Charts dialogs. + +- Use the `Is PIT` switch to specify if the metric should be stored by point-in-time. + + 'Point-in-time' metrics are those metrics that change (increase or decrease) at any given point of time. For example, database size is a point-in-time metric; at any given point-in-time, the size of the database is fluctuating. Metrics that are not point-in-time (also referred to as cumulative metrics) are metrics whose size always increases over time. For example, Blocks Read and Tuples Read are cumulative metrics; the value stays the same or increases. + +- Use the `Calculate PIT` switch to specify that the server should calculate a point-in-time value for the metric data. `Calculate PIT` is disabled if `Is PIT` is `Yes`. + + PEM allows you to store point-in time-values of cumulative metrics as well. PEM subtracts the last collected value of a cumulative metric from the current value, and stores the difference as a point-in-time value. + + + +Use the `Code` tab to specify the default code that will be executed by the probe: + +- If the probe is a SQL probe, you must specify the `SQL SELECT` statement invoked by the probe on the `Code` tab. The column names returned by the query must match the Internal Name specified on the `Columns` tab. The number of columns returned by the query, as well as the column name, data type, etc. must match the information specified on the `Columns` tab. + +- If the probe is a batch probe, you must specify the shell or .bat script that will be invoked when the probe runs. The output of the script should be as follows: + + The first line must contain the names of the columns provided on the `Columns` tab. Each column name should be separated by a tab (t) character. From the second line onwards, each line should contain the data for each column, separated by a tab character. + + If a specified column is defined as key column, you should ensure that the script does not produce duplicate data for that column across lines of output. The number of columns specified in the `Columns` tab and their names, data type, etc. should match with the output of the script output. + +- If the probe is a WMI probe, you must specify the WMI query as a `SELECT WMI` query. The column name referenced in the `SELECT` statement should be same as the name of the corresponding column specified on the `Column` tab. The column names returned by the query must match the `Internal Name` specified on the `Column` tab. The number of columns returned by the query, as well as the column name, data type, etc. must match the information specified on the Columns tab. + + + +Use the `Alternate Code` tab to provide code that will be invoked if the probe fires on a specific version of the server. To provide version-specific code, move the `Applies to any server version?` switch to `No`, and click the `Add` button. Then, use the `Database Version(s)` drop-down listbox to select a version, and click the `Edit` button (to the left of the version name) to provide the code that will execute when the probe fires. + +If you select a database version, and leave the `Probe Code` column blank, PEM will invoke the code specified on the `Code` tab when the probe executes on a server that matches that version. + +When you've finished defining the probe, click the `Save` icon (in the corner of the `Custom Probes` tab) to save the definition, and make the probe data available for use on custom charts and graphs. + +### Deleting a Probe + +Use the `Delete` icon (located to the left of a probe name) to delete a user-defined probe. When you delete a probe, the probe is marked for deletion and will be deleted later (when custom probes are purged). During the deletion, the probe definition is deleted and any corresponding tables are dropped from the `pemdata` and `pemhistory` schemas. + +System probes are the built-in probes provided by PEM, and are part of the PEM schema. If you attempt to delete a system probe, the PEM client will display a notice, informing you that the probe cannot be deleted. + + + +### Copying a Probe + +You can use the `Copy Probe Configuration...` dialog to copy probe definitions from one monitored object to one or more monitored objects of the same type. To open the `Copy Probe Configuration...` dialog, highlight the object from which you are copying probes in the PEM client tree control, and select `Manage Probes` from the `Management` menu. When the `Manage Probes` tab opens, click on `Copy Probe` to open the `Copy Probe Configuration` dialog: + + + +The dialog will copy the probe definitions from the object through which the Copy Probe Configuration dialog was opened, to the location(s) selected on the tree control. + +Note that if you specify a parent node in the `Copy Probe Configuration` tree control, PEM will copy the probe configurations to each object (of the same type) that resides under that node in the tree control. For example, to copy the probe definitions from one schema to all schemas that reside within a database, select only the parent database of the target schemas. Please note that a red warning symbol is displayed to the left of the name of a listed target object if that object is the source of the probe that is being copied. + +When you have selected the target object or objects, click the `Configure Probes` button to copy the probe definitions to the location selected on the dialog. + +## Alerting + +PEM continually monitors registered servers and compares performance metrics against pre-defined and user-specified thresholds that constitute good or acceptable performance for each statistic. Any deviation from an acceptable threshold value triggers an alert. An alert is a system-defined or user-defined set of conditions that PEM compares to the system statistics. Alerts call your attention to conditions on registered servers that require your attention. + +**Reviewing alerts on the Global Overview** + +When your system statistics deviate from the boundaries specified for that statistic, the alert triggers, displaying a high (red), low (yellow), or medium (orange) severity warning in the left-most column of the `Alert Status` table on the `Global Overview` dashboard. + + + +The PEM server includes a number of pre-defined alerts that are actively monitoring your servers. If the alert definition makes details available about the cause of the alert, you can click the down arrow to the right of the severity warning to access a dialog with detailed information about the condition that triggered the alert. + + + +PEM also provides an interface that allows you to create customized alerts. Each alert uses metrics defined on an alert template. An alert template defines how the server will evaluate the statistics for a resource or metric. The PEM server includes a number of pre-defined alert templates, or you can create custom alert templates. + +### Using the Alerts Dashboard + +Use the `Dashboards` menu (on the `Monitoring` tab) to access the `Alerts` dashboard. The `Alerts` dashboard displays a summary of the active alerts and the status of each alert: + + + +The `Alerts Dashboard` header displays the date and time that the dashboard was last updated, and the number of current alerts. + +The `Alerts Overview` section displays a graphic representation of the active alerts, as well as a count of the current high, low and medium alerts. The vertical bar on the left of the graph provides the count of the alerts displayed in each column. Hover over a bar to display the alert count for the selected alert severity in the upper-right hand corner of the graph. + +The `Alert Details` table provides a list of the alerts that are currently triggered. The entries are prioritized from high-severity to lower-severity; each entry includes information that will allow you to identify the alert and recognize the condition that triggered the alert. Click the name of an alert to review detailed information about the alert definition. + +The `Alert Errors` table displays configuration-related errors (eg. accidentally disabling a required probe, or improperly configuring an alert parameter). You can use the information provided in the Error Message column to identify and resolve the conflict that is causing the error. + +**Customizing the Alerts Dashboard** + +You can customize tables and charts that appear on the Alerts dashboard. To customize a table or chart, click the Settings icon located in the upper-right corner. + + + +Use fields on the Personalize chart configuration dialog to provide your display preferences: + +- Use the `Auto Refresh` field to specify the number of seconds between updates of the data displayed in the table or chart. +- If applicable, use the `Download as` field to indicate if you would like a chart to be downloaded as a JPEG image or a PNG image. +- If applicable, use the `Colours selectors` to specify the display colors that will be used on a chart. +- If applicable, set the `Show Acknowledged Alerts` switch to Yes indicate that you would like the table to display alerts that you have acknowledged with a checkbox in the Ack'ed column. Set the field to No to indicate that the table should hide any acknowledged alerts. The switch acts as a toggle; acknowledged alerts are not purged from the table content until the time specified in the alert definition passes. + +To save your customizations, click the `Save` icon (a check mark) in the upper-right corner; to delete any previous changes and revert to the default values, click the `Delete` icon. The `Save` and `Delete` drop-down menus allow you to specify if your preferences should be applied to `All Dashboards`, or to a selected server or database. + +### Using the Manage Alerts Tab + +Use the PEM Client's `Manage Alerts` tab to define, copy, or manage alerts. To open the `Manage Alerts` tab, select `Manage Alerts` from the `Management` menu. + + + +Use the `Quick Links` toolbar to open dialogs and tabs that will assist you when managing alerts: + +- Click `Copy Alerts` to open the `Copy Alert Configuration` dialog and copy an alert definition. +- Click `Alert Templates` to open the `Alert Template` tab, and modify or create an alert template. +- Click `Email Groups` to open the `Email Groups` tab, and modify or create an email group. +- Click `Webhooks` to open the `Webhooks` tab, and create or manage the webhooks endpoints. +- Click `Server Configurations` to open the `Server Configuration` dialog and review or modify server configuration settings. +- Click `Help` to open the PEM online help in a new tab of the PEM web interface. + +Use the table in the `Alerts` section of the `Manage Alerts` tab to create new alerts or manage existing alerts. + +#### Creating a Custom Alert Template + +An alert template is a prototype that defines the properties of an alert. An alert instructs the server to compare the current state of the monitored object to a threshold (specified in the alert template) to determine if a situation exists that requires administrative attention. + +You can use the `Alert Templates` tab to define a custom alert template or view the definitions of existing alert templates. To open the `Alert Templates` tab, select the `Manage Alerts...` menu option from the `Management` menu. When the `Manage Alerts` tab opens, select `Alert Templates` from the `Quick Links` toolbar. + + + +Use the `Show System Template` drop-down listbox to filter the alert templates that are displayed in the `Alert Templates` table. Use the listbox to select a level of the PEM hierarchy to view all of the templates for the selected level. + +**Defining a New Alert Template** + +To define a new alert template, use the `Show System Template` drop-down listbox to select None, and click the `Add` icon (+) located in the upper-right corner of the alert template table. The alert template editor opens. + + + +Use fields on the `General` tab to specify general information about the template: + +- Use the `Template name` field to specify a name for the new alert template. + +- Use the `Description` field to provide a description of the alert template. + +- Use the `Target type` drop-down listbox to select the type of object that will be the focus of the alert. + +- Use the `Applies to server` drop-down listbox to specify the server type (EDB Postgres Advanced Server or PostgreSQL) to which the alert will be applied; you can specify a single server type, or ALL. + +- Use the `History retention` field to specify the number of days that the result of the alert execution will be stored on the PEM server. + +- Use the `Threshold unit` field to specify the unit type of the threshold value. + +- Use fields in the `Auto create` box to indicate if PEM should use the template to generate an automatic alert. If enabled, PEM will automatically create an alert when a new server or agent (as specified by the Target type drop-down listbox) is added, and delete that alert when the target object is dropped. + + - Move the `Auto create?` slider to `Yes` to indicate that PEM should automatically create alerts based on the template. If you modify an existing alert template, changing the Auto create? slider from No to Yes, PEM will create alerts on the existing agents and servers. Please note that if you change the slider from Yes to No, the default threshold values in existing alerts will be erased, and cannot be recovered. + - Use the `Operator` drop-down listbox to select the operator that PEM will use when evaluating the current system values. + + Select a greater-than sign (>) to indicate that the alert should be triggered when the system values are greater than the values entered in the Threshold values fields. + + Select a less-than sign (<) to indicate that the alert should be triggered when the system values are less than the values entered in the Threshold values fields. + +- Use the threshold fields to specify the values that PEM will compare to the system values to determine if an alert should be raised. Please note that you must specify values for all three thresholds (Low, Medium, and High): + + Enter a value that will trigger a low-severity alert in the `Low` field. + + Enter a value that will trigger a medium-severity alert in the `Medium` field. + + Enter a value that will trigger a high-severity alert in the `High` field. + +- Use the `Check frequency` field to specify the default number of minutes between alert executions. This value specifies how often the server will invoke the SQL code specified in the definition and compare the result to the threshold value specified in the template. + + + +Use the fields on the `Probe Dependency` tab to specify the names of probes referred to in the SQL query specified on the SQL tab: + +- Use the `Probes` drop-down listbox to select from a list of the available probes; highlight a probe name, and click the `Add` button to add the probe to the list of probes used by the alert template. To remove a probe from the selected probes list, highlight the probe name, and click the `Delete` icon. + + + +- Use fields on the `Parameters` tab to define the parameters that will be used in the SQL code specified on the `SQL` tab. Click the `Add` icon (+) and: + + Use the `Name` field to specify the parameter name. + + Use the `Data type` drop-down listbox to specify the type of parameter. + + Use the `Unit` field to specify the type of unit specified by the parameter. + +- Use the `Code` field on the `SQL` tab to provide the text of the SQL query that the server will invoke when executing the alert. The SQL query will provide the result against which the threshold value is compared; if the alert result deviates from the specified threshold value, an alert will be raised. + + + +Within the query, parameters defined on the `Parameters` tab should be referenced sequentially by the variable param\_`x`, where `x` indicates the position of the parameter definition within the parameter list. For example, param_1 refers to the first parameter in the parameter list, param_2 refers to the second parameter in the parameter list, and so on. + +The query can also include the following pre-defined variables: + +| **Variable Description** | **Variable Name** | +| ------------------------ | ------------------ | +| agent identifier | '${agent_id}' | +| server identifier | '${server_id}' | +| database name | '${database_name}' | +| schema name | '${schema_name}' | +| Table | '${object_name}' | +| index | '${object_name}' | +| sequence | '${object_name}' | +| function name | '${object_name}' | + +- Use the `Detailed Information SQL` field to provide a SQL query that will be invoked if the alert is triggered. The result set of the query may be displayed as part of the detailed alert information on the `Alerts` dashboard or `Global Overview` dashboard. + +!!! Note + If the specified query is dependent on one or more probes from different levels within the PEM hierarchy (server, database, schema, etc.), and a probe becomes disabled, any resulting alerts will be displayed as follows: + +- If the alert definition and the probe referenced by the query are from the same level within the PEM hierarchy, the server will display any alerts that reference the alert template on the `Alert Error` table of the `Global Alert` dashboard. +- If the alert definition and the probe referenced by the query are from different levels of the PEM hierarchy, the server will display any triggered alerts that reference the alert template on the `Alert Details` table of the hierarchy on which the alert was defined. + +Click the `Save` icon to save the alert template definition and add the template name to the Alert Templates list. After saving a custom alert template, you can use the Alerting dialog to define an alert based on the template. + +**Modifying or Deleting an Alert Template** + +To view the definition of an existing template (including PEM pre-defined alert templates), use the `Show System Template` drop-down listbox to select the type of object monitored. When you select the object type, the `Alert Templates` table will display the currently defined alert templates that correspond with that object type. + +Highlight a Template Name in the list, and click the Edit icon (at the left end of the row) to review the template definition. + +Use the tabs on the `Alert Templates` dialog to view detailed information about the alert template: + +- General information is displayed on the `General` tab. +- The names of probes that provide data for the template are listed on the `Probe Dependency` tab. +- The names of any parameters referred to in the SQL code are listed on the `Parameters` tab. +- The SQL code that defines the behavior of the alert is displayed on the `SQL` tab. + +To delete an alert template, highlight the template name in the alert templates table, and click the Delete icon. The alert history will persist for the length of time specified in the `History Retention` field in the template definition. + +#### Creating a New Alert + +The `Manage Alerts` tab displays a table of alerts that are defined on the object currently selected in the PEM client tree control. You can use the `Alerts` table to modify an existing alert, or to create a new alert. + + + +To open the alert editor and create a new alert, click the Add icon (+) in the upper-right corner of the table. The editor opens as shown below. + + + +Use the fields on the `General` tab to provide information about the alert: + +- Enter the name of the alert in the `Name` field. +- Use the drop-down listbox in the `Template` field to select a template for the alert. An alert template is a function that uses one (or more) metrics or parameters to generate a value to which PEM compares user-specified alert boundaries. If the value returned by the template function evaluates to a value that is within the boundary of a user-defined alert (as specified by the Operator and Threshold values fields), PEM raises an alert, adds a notice to the Alerts overview display, and performs any actions specified on the template. +- Use the `Enable?` switch to specify if the alert is enabled (Yes) or disabled (No). +- Use the controls in the `Interval` box to specify how often the alert should confirm if the alert conditions are satisfied. Use the Minutes selector to specify an interval value. Use the Default switch to set or reset the Minutes value to the default (recommended) value for the selected template. +- Use controls in the `History retention` box to specify the number of days that PEM will store data collected by the alert. Use the `Days` selector to specify the number of days that the data will be stored. Use the Default switch to set or reset the `Days` value to the default value (30 days). +- Use controls in the `Threshold values` box to define the triggering criteria for the alert. When the value specified in the Threshold Values fields evaluates to greater-than or less-than the system value (as specified with the Operator), PEM will raise a Low, Medium or High level alert: +- Use the `Operator` drop-down listbox to select the operator that PEM will use when evaluating the current system values: + - Select a greater-than sign (>) to indicate that the alert should be triggered when the system values are greater than the values entered in the Threshold values fields. + - Select a less-than sign (<) to indicate that the alert should be triggered when the system values are less than the values entered in the Threshold values fields. +- Use the `threshold` fields to specify the values that PEM will compare to the system values to determine if an alert should be raised. Please note that you must specify values for all three thresholds (Low, Medium, and High): + - Enter a value that will trigger a low-severity alert in the `Low` field. + - Enter a value that will trigger a medium-severity alert in the `Medium` field. + - Enter a value that will trigger a high-severity alert in the `High` field. + +The `Parameter Options` table contains a list of parameters that are required by the selected template; the table displays both pre-defined parameters, and parameters for which you must specify a value. Please note that you must specify a value for any parameter that displays a prompt in the Value column. + +PEM can send a notification or execute a script if an alert is triggered, or if an alert is cleared. Use the `Notification` tab to specify how PEM will behave if an alert is raised. + + + +Use the fields in the `Email notification` box to specify the email group that will receive an email notification if the alert is triggered at the specified level. Use the `Email Groups` tab to create an email group that contains the address of the user or users that will be notified when an alert is triggered. To access the `Email Groups` tab, click the `Email Groups` icon located in the `Quick Links` menu of the `Manage Alerts` tab. + +- To instruct PEM to send an email when a specific alert level is reached, set the slider next to an alert level to Yes, and use the drop-down listbox to select the pre-defined user or group that will be notified. + +Please note that you must configure the PEM Server to use an SMTP server to deliver email before PEM can send email notifications. + +Use the `Trap notification` options to configure trap notifications for this alert: + +- Set the `Send trap` slider to `Yes` to send SNMP trap notifications when the state of this alert changes. +- Set the `SNMP Ver` to `v1`, `v2`, or `v3` to identify the SNMP version. +- Use the `Low alert`, `Med alert` and `High alert` sliders to select the level(s) of alert that will trigger the trap. For example, if you set the slider next to High alert to Yes, PEM will send a notification when an alert with a high severity level is triggered. + +Please note that you must configure the PEM Server to send notifications to an SNMP trap/notification receiver before notifications can be sent. For sending SNMP v3 traps, pemAgent will use 'User Security Model(USM)' which is in charge of authenticating, encrypting, and decrypting SNMP packets. + +Also note while sending SNMP v3 traps, agent will create snmp_boot_counter file. This file will get created in location mentioned by batch_script_dir parameter in agent.cfg, if this parameter is not configured or if directory is not accessible due to authentication restrictions then in operating systems temporary directory, if that is also not possible then in user’s home directory. + +Use the field in the `Nagios notification` box to instruct the PEM server to notify Nagios network-alerting software when the alert is triggered or cleared. + +- Set the `Submit passive service check result to Nagios` switch to `Yes` to instruct the PEM server to notify Nagios when the alert is triggered or cleared. + +Use the fields in the `Script execution` box to (optionally) define a script that will be executed if an alert is triggered, and to specify details about the script execution. + +- Set the `Execute script` slider to `Yes` to instruct PEM to execute the provided script if an alert is triggered. + +- Set the `Execute on alert cleared` slider to `Yes` to instruct PEM to execute the provided script when the situation that triggered the alert has been resolved. + +- Use the radio buttons next to `Execute script on` to indicate that the script should execute on the PEM Server or the Monitored Server. + +- Provide the script that PEM should execute in the `Code` field. You can provide a batch/shell script, or SQL code. Within the script, you can use placeholders for the following: + + `%AlertName%` - this placeholder will be replaced with the name of the triggered alert. + + `%ObjectName%` - this placeholder will be replaced with the name of the server or agent on which the alert was triggered. + + `%ThresholdValue%` - this placeholder will be replaced with the threshold value reached by the metric when the alert triggered. + + `%CurrentValue%` - this placeholder will be replaced with the current value of the metric that triggered the alert. + + `%CurrentState%` - this placeholder will be replaced with the current state of the alert. + + `%OldState%` - this placeholder will be replaced with the previous state of the alert. + + `%AlertRaisedTime%` - this placeholder will be replaced with the time that the alert was raised, or the most recent time that the alert state was changed. + + To invoke a script on a Linux system, you must modify the entry for the `batch_script_user` parameter of the `agent.cfg` file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. + + To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in HKEY_LOCAL_MACHINE/Software/Wow6432Node/EnterpriseDB/PEM/agent. + +When you have defined the alert attributes, click the edit icon to close the alert definition editor, and then the save icon (in the upper-right corner of the `Alerts` table). To discard your changes, click the refresh icon; a popup will ask you to confirm that you wish to discard the changes. + +!!! Note + Suppose you need to use the alert configuration placeholder values in an external script. You can do it either by passing them as the command-line arguments or exporting them as environment variables. Please note that the external script must have proper execution permissions. + +- You can run the script with any of the placeholders as command-line argument. + + For eg: + + ```bash + #!/bin/bash + + bash
The number of timed checkpoints
The number of requested checkpoints
The number of buffers written (by checkpoint)
The number of buffers written (by background writer)
The number of background writer cycles
The number of background buffers written
The number of buffers allocated | Server | +| Blocked Session Information | This probe provides information about blocked sessions. | Server | +| CPU Usage | This probe monitors CPU Usage information. | Agent | +| Data and Log File Analysis | This probe monitors information about log files. The information includes:
The name of the log file
The directory in which the log file resides | Server | +| Database Statistics | This probe monitors database statistics. The information includes:
The number of backends
The number of transactions committed
The number of transactions rolled back
The number of blocks read
The number of blocks hit
The number of rows returned
The number of rows fetched
The number of rows inserted
The number of rows updated
The number of rows deleted | Server | +| Disk Busy Info | This probe monitors information about disk activity.
Note: This probe is not supported on Mac OS X, Solaris or HP-UX | Agent | +| Disk Space | This probe monitors information about disk space usage. The information includes:
The amount of disk space used
The amount of disk space available | Agent | +| EDB Audit Configuration | This probe monitors the audit logging configuration of EDB Postgres Advanced Server. | Server | +| Failover Manager Cluster Info | This probe monitors a Failover Manager cluster, returning information about the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server | +| Failover Manager Node Status | This probe monitors a Failover Manager cluster, returning detailed about each node within the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server | +| Function Statistics | This probe monitors a database, retrieving information about functions. The information includes:
Function names
Argument types
Return values | Database | +| Index Size | This probe monitors a database, retrieving information about indexes. The information includes:
The name of the index
The time the data was gathered
The size of the index (in MB's) | Database | +| Index Statistics | This probe monitors index statistics. The information includes:
The number of index scans
The number of rows read
The number of rows fetched
The number of blocks read
The number of blocks hit | Database | +| Installed Packages | This probe monitors the packages that are currently installed. The information gathered includes:
The name of the installed package
The version of the installed package
The date and time that the probe executed | Agent | +| IO Analysis | This probe monitors disk I/O information in. The information includes:
The number of blocks read
The number of blocks written
The date and time that the probe executed
Note: This probe is not supported on Mac OS X | Agent | +| Load Average | This probe monitors CPU load averages. The information includes:
The 1-minute load average
The 5-minute load average
The 15-minute load average
Note: This probe is not supported on Windows | Agent | +| Lock Information | This probe monitors lock information. The information includes:
The database name
The lock type
The lock mode
The process holding the lock | Server | +| Memory Usage | This probe monitors information about system memory usage. | Agent | +| Network Statistics | This probe monitors network statistics. The information includes:
The interface IP address
The number of packets sent
The number of packets received
The number of bytes sent
The number of bytes received
The link speed (in MB/second) | Agent | +| Number of Prepared Transactions | This probe stores the number of prepared transactions. | Server | +| Number of WAL Files | This probe monitors the number of WAL files. | Server | +| Object Catalog: Database | This probe monitors a list of databases and their properties The information includes:
The database name
The database encoding type
If the database allows user connections or system connections | Server | +| Object Catalog: Foreign Key | This probe monitors a list of foreign keys and their properties. The information includes:
The name of the table that contains the foreign key
The name of the table that the foreign key references
The name of the database in which the table resides
The name of the schema in which the table resides | Schema | +| Object Catalog: Function | This probe monitors a list of functions and their properties. The information includes:
The name of the function
The name of the schema in which the function resides
The name of the database in which the function resides | Schema | +| Object Catalog: Index | This probe monitors a list of indexes and their properties. The information includes:
The name of the index
The name of the table that the index is associated with
The name of the database in which the indexed table resides | Schema | +| Object Catalog: Schema | This probe monitors a list of schemas and their associated databases and servers. | Database | +| Object Catalog: Sequence | This probe monitors a list of sequences and their properties. | Schema | +| Object Catalog: Table | This probe monitors a list of table information. The information includes:
The table name
The name of the schema in which the table resides
The name of the database in which the schema resides
A Boolean indicator that indicates if the table has a primary key | Schema | +| Object Catalog: Tablespace | This probe monitors a list of tablespaces. | Server | +| Operating System Information | This probe monitors the operating system details and boot time. | Agent | +| Package Catalog | This probe monitors the packages that are currently available for installation. The information gathered includes:
The package name
The package version | Agent | +| PG HBA Conf | This probe monitors authentication configuration information from the pg_hba.conf file. | Server | +| Server Information | This probe monitors server information. | Server | +| Session Information | This probe monitors session information. The information includes:
The name of the session user
The date and time that the session connected to the server
The status of the session at the time that the information was gathered (idle, waiting, etc)
The client address and port number | Server | +| Settings | This probe monitors the values currently assigned to GUC variables. | Server | +| SQL Protect | This probe monitors a server, retrieving information about SQL injection attacks. | Server | +| Slony Replication | This probe monitors lag data for clusters replicated using Slony. | Database | +| Streaming Replication | This probe monitors a cluster that is using streaming replication, retrieving information about:
The sent Xlog location (in bytes)
The write Xlog location (in bytes)
The flush Xlog location (in bytes)
The replay Xlog location (in bytes)
The Xlog lag (in segments)
The Xlog lag (in pages) | Server | +| Streaming Replication Lag Time | This probe monitors a cluster that is using streaming replication, retrieving lag information about:
Replication lag time (in seconds)
Current status of replication (running/paused) | Server | +| Streaming Replication Database Conflicts | This probe monitors a database that is using streaming replication, retrieving information about any conflicts that arise. This includes information about queries that have been canceled due to:
The # of drop tablespace conflicts
The # of lock timeout conflicts
The # of old snapshot conflicts
The # of pinned buffer conflicts
The # of deadlock conflicts | Server | +| Table Bloat | This probe monitors information about the current table bloat. The information includes:
The name of the table
The name of the schema in which the table resides
The estimated number of pages
The estimated number of wasted pages
The estimated number of bytes per row | Database | +| Table Frozen XID | This probe monitors the frozen XID of each table. | Schema | +| Table Size | This probe monitors table statistics. The information includes:
The number of sequential scans
The number of sequential scan rows
The number of index scans
The number of index scan rows
The number of rows inserted
The number of rows updated
The number of rows deleted
The number of live rows
The number of dead rows
The last VACUUM
The last auto-vacuum
The last ANALYZE
The last auto-analyze
The number of pages estimated by ANALYZE
The number of rows estimated by ANALYZE | Database | +| Table Statistics | This probe monitors a list of tablespaces and their sizes. | Server | +| Tablespace Size | This probe monitors a list of tablespaces and their sizes. | Server | +| User Information | This probe monitors a list of the current users. The stored information includes:
The user name
The user type (superuser vs. non-superuser)
The server to which the user is connected | Server | +| WAL Archive Status | This probe monitors the status of the WAL archive. The stored information includes:
The # of WAL archives done
The # of WAL archives pending
The last archive time
The # of WAL archives failed
The time of the last failure | Server | +| xDB Replication | This probe monitors lag data for clusters replicated using xDB replication. | Database | + +## PEM Pre-defined Alert Templates – Reference + +An alert definition contains a system-defined or user-defined set of conditions that PEM compares to the system statistics; if the statistics deviate from the boundaries specified for that statistic, the alert triggers, and the PEM client displays a warning on the \*Alerts Overview\* page, and optionally sends a notification to a monitoring user. + +The tables that follow list the system-defined alert templates that you can use to create an alert; please note that this list is subject to change, and may vary by system: + +### Templates applicable on Agent + +| Template Name | Description | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------- | +| Load Average (1 minute) | 1-minute system load average. | +| Load Average (5 minutes) | 5-minute system load average. | +| Load Average (15 minutes) | 15-minute system load average. | +| Load Average per CPU Core (1 minutes) | 1-minute system load average per CPU core. | +| Load Average per CPU Core (5 minutes) | 5-minute system load average per CPU core. | +| Load Average per CPU Core (15 minutes) | 15-minute system load average per CPU core. | +| CPU utilization | Average CPU consumption. | +| Number of CPUs running higher than a | Number of CPUs running at greater than K% utilization threshold | +| Free memory percentage | Free memory as a percent of total system memory. | +| Memory used percentage | Percentage of memory used. | +| Swap consumption | Swap space consumed (in megabytes). | +| Swap consumption percentage | Percentage of swap area consumed. | +| Disk Consumption | Disk space consumed (in megabytes). | +| Disk consumption percentage | Percentage of disk consumed. | +| Disk Available | Disk space available (in megabytes). | +| Disk busy percentage | Percentage of disk busy. | +| Most used disk percentage | Percentage used of the most utilized disk on the system. | +| Total table bloat on host | The total space wasted by tables on a host, in MB. | +| Highest table bloat on host | The most space wasted by a table on a host, in MB. | +| Average table bloat on host | The average space wasted by tables on host, in MB. | +| Table size on host | The size of tables on host, in MB. | +| Database size on host | The size of databases on host, in MB. | +| Number of ERRORS in the logfile on agent N in last X hours. | The number of ERRORS in the logfile on agent N in last X hours | +| Number of WARNINGS in the logfile on agent N in last X hours | The number of WARNINGS in the logfile on agent N in last X hours. | +| Number of WARNINGS or ERRORS in the logfile on agent N in last X hours | The number of WARNINGS or ERRORS in the logfile on agent N in last X hours. | +| Package version mismatch | Check for package version mismatch as per catalog. | +| Total materialized view bloat on host | The total space wasted by materialized views on a host, in MB. | +| Highest materialized view bloat on host | The most space wasted by a materialized view on a host, in MB. | +| Average materialized view bloat on host | The average space wasted by materialized views on host, in MB. | +| Materialized view size on host | The size of materialized views on host, in MB. | +| Agent Down | Specified agent is currently down. | + +### Templates applicable on Server + +| Template Name | Description | +| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| Total table bloat in server | The total space wasted by tables in server, in MB. | +| Largest table (by multiple of unbloated size) | Largest table in server, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | +| Highest table bloat in server | The most space wasted by a table in server, in MB. | +| Average table bloat in server | The average space wasted by tables in server, in MB. | +| Table size in server | The size of tables in server, in MB. | +| Database size in server | The size of databases in server, in MB. | +| Number of WAL files | Total number of Write Ahead Log files. | +| Number of prepared transactions | Number of transactions in prepared state. | +| Total connections | Total number of connections in the server. | +| Total connections as percentage of | Total number of connections in the server as a percentage of maximum | +| max_connections | connections allowed on server, settings. | +| Unused, non-superuser connections | Number of unused, non-superuser connections on the server, user_info, settings. | +| Unused, non-superuser connections as percentage of max_connections | Number of unused, non-superuser connections on the server as a percentage of max_connections of max_connections, user_info, settings. | +| Ungranted locks | Number of ungranted locks in server. | +| Percentage of buffers written by backends | The percentage of buffers written by backends vs. the total buffers written. | +| Percentage of buffers written by checkpoint | The percentage of buffers written by the checkpoints vs. the total buffers written. | +| Buffers written per second | Number of buffers written per second, over the last two probe cycles. | +| Buffers allocated per second | Number of buffers allocated per second, over the last two probe cycles. | +| Connections in idle state | Number of connections in server that are in idle state. | +| Connections in idle-in-transaction state | Number of connections in server that are in idle-in-transaction state. | +| Connections in idle-in-transaction state, as percentage of max_connections | Number of connections in server that are in idle-in-transaction state, as a percentage of maximum connections allowed on server, settings. | +| Long-running idle connections | Number of connections in the server that have been idle for more than N seconds. | +| Long-running idle connections and idle transactions | Number of connections in the server that have been idle or transactions idle-in-transaction for more than N seconds. | +| Long-running idle transactions | Number of connections in the server that have been idle in transaction for more than N seconds. | +| Long-running transactions | Number of transactions in server that have been running for more than N seconds. | +| Long-running queries | Number of queries in server that have been running for more than N seconds. | +| Long-running vacuums | Number of vacuum operations in server that have been running for more than N seconds. | +| Long-running autovacuums | Number of autovacuum operations in server that have been running for more than N seconds. | +| Committed transactions percentage | Percentage of transactions in the server that committed vs. that rolled-back over last N minutes. | +| Shared buffers hit percentage | Percentage of block read requests in the server that were satisfied by shared buffers, over last N minutes. | +| Tuples inserted | Tuples inserted into server over last N minutes. | +| InfiniteCache buffers hit percentage | Percentage of block read requests in the server that were satisfied by InfiniteCache, over last N minutes. | +| Tuples fetched | Tuples fetched from server over last N minutes. | +| Tuples returned | Tuples returned from server over last N minutes. | +| Dead Tuples | Number of estimated dead tuples in server. | +| Tuples updated | Tuples updated in server over last N minutes. | +| Tuples deleted | Tuples deleted from server over last N minutes. | +| Tuples hot updated | Tuples hot updated in server, over last N minutes. | +| Sequential Scans | Number of full table scans in server, over last N minutes. | +| Index Scans | Number of index scans in server, over last N minutes. | +| Hot update percentage | Percentage of hot updates in the server over last N minutes. | +| Live Tuples | Number of estimated live tuples in server. | +| Dead tuples percentage | Percentage of estimated dead tuples in server. | +| Last Vacuum | Hours since last vacuum on the server. | +| Last AutoVacuum | Hours since last autovacuum on the server. | +| Last Analyze | Hours since last analyze on the server. | +| Last AutoAnalyze | Hours since last autoanalyze on the server. | +| Percentage of buffers written by backends over the last N minutes | The percentage of buffers written by backends vs. the total buffers backends over last N | +| Table Count | Total number of tables in server. | +| Function Count | Total number of functions in server. | +| Sequence Count | Total number of sequences in server. | +| A user expires in N days | Number of days before a user's validity expires. | +| Index size as a percentage of table size | Size of the indexes in server, as a percentage of their tables' size. | +| Largest index by table-size percentage oc_index, table_size. | Largest index in server, calculated as percentage of its table's size. | +| Number of ERRORS in the logfile on server M in the last X hours | The number of ERRORS in the logfile on server M in last X hours. | +| Number of WARNINGS in the logfile on server M in the last X hours | The number of WARNINGS in logfile on server M in the last X hours. | +| Number of WARNINGS or ERRORS in the logfile on server M in the last X hours | The number of WARNINGS or ERRORS in the logfile on server M in the last X hours. | +| Number of attacks detected in the last N minutes | The number of SQL injection attacks occurred in the last N minutes. | +| Number of attacks detected in the last N minutes by username | The number of SQL injection attacks occurred in the last N minutes by username. | +| Number of replica servers lag behind the primary by write location | > Streaming Replication: number of replica servers lag behind the primary by write location. | +| Number of replica servers lag behind the primary by flush location | > Streaming Replication: number of replica servers lag behind the primary by flush location. | +| Number of replica servers lag behind the primary by replay location | > Streaming Replication: number of replica servers lag behind the primary by replay location. | +| Replica server lag behind the primary by write location | > Streaming Replication: replica server lag behind the primary by write location in MB. | +| Replica server lag behind the primary by flush location | > Streaming Replication: replica server lag behind the primary by flush location in MB. | +| Replica server lag behind the primary by replay location | > Streaming Replication: replica server lag behind the primary by replay location in MB. | +| Replica server lag behind the primary by size (MB) | > Streaming Replication: replica server lag behind the primary by size in MB. | +| Replica server lag behind the primary by WAL segments | > Streaming Replication: replica server lag behind the primary by WAL segments. | +| Replica server lag behind the primary by WAL pages | > Streaming Replication: replica server lag behind the primary by WAL pages. | +| Total materialized view bloat in server | The total space wasted by materialized views in server, in MB. | +| Largest materialized view (by multiple of unbloated size) | Largest materialized view in server, calculated as a multiple of its own estimated unbloated size; exclude materialized views smaller than N MB. | +| Highest materialized view bloat in server | The most space wasted by a materialized view in server, in MB. | +| Average materialized view bloat in server | The average space wasted by materialized views in server, in MB. | +| Materialized view size in server | The size of materialized view in server, in MB. | +| View Count | Total number of views in server. | +| Materialized View Count | Total number of materialized views in server. | +| Audit config mismatch | Check for audit config parameter mismatch | +| Server Down | Specified server is currently inaccessible. | +| Number of WAL archives pending | Streaming Replication: number of WAL files pending to be replayed at replica. | +| Number of minutes lag of replica server from primary server | > Streaming Replication: number of minutes replica node is lagging behind the primary node. | +| Log config mismatch | Check for log config parameter mismatch. | + +### Templates applicable on Database + +| Template Name | Description | +| ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| Total table bloat in database | The total space wasted by tables in database, in MB. | +| Largest table (by multiple of unbloated size) | Largest table in database, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | +| Highest table bloat in database | The most space wasted by a table in database, in MB. | +| Average table bloat in database | The average space wasted by tables in database, in MB. | +| Table size in database | The size of tables in database, in MB. | +| Database size | The size of the database, in MB. | +| Total connections | Total number of connections in the database. | +| Total connections as percentage of max_connections | Total number of connections in the database as a percentage of maximum connections allowed on server, settings. | +| Ungranted locks | Number of ungranted locks in database. | +| Connections in idle state | Number of connections in database that are in idle state. | +| Connections in idle-in-transaction state | Number of connections in database that are in idle-in-transaction state | +| Connections in idle-in-transaction state,as percentage of max_connections | Number of connections in database that are in idle-in-transaction state, as a percentage of maximum connections allowed on server, settings. | +| Long-running idle connections | Number of connections in the database that have been idle for more than N seconds. | +| Long-running idle connections and idle transactions | Number of connections in the database that have been idle or idle-in-transaction for more than N seconds. | +| Long-running idle transactions | Number of connections in the database that have been idle in transaction for more than N seconds. | +| Long-running transactions | Number of transactions in database that have been running for more than N seconds. | +| Long-running queries | Number of queries in database that have been running for more than N seconds. | +| Long-running vacuums | Number of vacuum operations in database that have been running for more than N seconds. | +| Long-running autovacuums | Number of autovacuum operations in database that have been running for more than N seconds. | +| Committed transactions percentage | Percentage of transactions in the database that committed vs. that rolled-back over last N minutes. | +| Shared buffers hit percentage | Percentage of block read requests in the database that were satisfied by shared buffers, over last N minutes. | +| InfiniteCache buffers hit percentage | Percentage of block read requests in the database that were satisfied by InfiniteCache, over last N minutes. | +| Tuples fetched | Tuples fetched from database over last N minutes. | +| Tuples returned | Tuples returned from database over last N minutes. | +| Tuples inserted | Tuples inserted into database over last N minutes. | +| Tuples updated | Tuples updated in database over last N minutes. | +| Tuples deleted | Tuples deleted from database over last N minutes. | +| Tuples hot updated | Tuples hot updated in database, over last N minutes. | +| Sequential Scans | Number of full table scans in database, over last N minutes. | +| Index Scans | Number of index scans in database, over last N minutes. | +| Hot update percentage | Percentage of hot updates in the database over last N minutes. | +| Live Tuples | Number of estimated live tuples in database. | +| Dead Tuples | Number of estimated dead tuples in database. | +| Dead tuples percentage | Percentage of estimated dead tuples in database. | +| Last Vacuum | Hours since last vacuum on the database. | +| Last AutoVacuum | Hours since last autovacuum on the database. | +| Last Analyze | Hours since last analyze on the database. | +| Last AutoAnalyze | Hours since last autoanalyze on the database. | +| Table Count | Total number of tables in database. | +| Function Count | Total number of functions in database. | +| Sequence Count | Total number of sequences in database. | +| Index size as a percentage of table size | Size of the indexes in database, as a percentage of their tables' size. | +| Largest index by table-size percentage | Largest index in database, calculated as percentage of its table's size, oc_index, table_size. | +| Database Frozen XID | The age (in transactions before the current transaction) of the database's frozen transaction ID. | +| Number of attacks detected in the | The number of SQL injection attacks occurred in the last N minutes. last N minutes | +| Number of attacks detected in the | The number of SQL injection attacks occurred in the last N minutes by last N minutes by username. | +| Queries that have been cancelled due to dropped tablespaces | Streaming Replication: number of queries that have been cancelled due to dropped tablespaces. | +| Queries that have been cancelled due to lock timeouts | Streaming Replication: number of queries that have been cancelled due to lock timeouts. | +| Queries that have been cancelled due to old snapshots | Streaming Replication: number of queries that have been cancelled due to old snapshots. | +| Queries that have been cancelled due to pinned buffers | Streaming Replication: number of queries that have been cancelled due to pinned buffers. | +| Queries that have been cancelled due to deadlocks | Streaming Replication: number of queries that have been cancelled due to deadlocks. | +| Total events lagging in all slony clusters | Slony Replication: total events lagging in all slony clusters. | +| Events lagging in one slony cluster | Slony Replication: events lagging in one slony cluster. | +| Lag time (minutes) in one slony cluster | Slony Replication: lag time (minutes) in one slony cluster. | +| Total rows lagging in xdb single primary replication | > xDB Replication: Total rows lagging in xdb single primary replication | +| Total rows lagging in xdb multi primary replication | > xDB Replication: Total rows lagging in xdb multi primary replication. | +| Total materialized view bloat in database | The total space wasted by materialized views in database, in MB. | +| Largest materialized view (by multiple of unbloated size) | Largest materialized view in database, calculated as a multiple of its estimated unbloated size; exclude materialized views smaller than N MB. | +| Highest materialized view bloat in database | The most space wasted by a materialized view in database, in MB. | +| Average materialized view bloat in database | The average space wasted by materialized views in database, in MB. | +| Materialized view size in database | The size of materialized view in database, in MB. | +| View Count | Total number of views in database. | +| Materialized View Count | Total number of materialized views in database. | + +### Templates applicable on Schema + +| Template Name | Description | +| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| Total table bloat in schema | The total space wasted by tables in schema, in MB. | +| Largest table (by multiple of unbloated size) | Largest table in schema, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | +| Highest table bloat in schema | The most space wasted by a table in schema, in MB. | +| Average table bloat in schema | The average space wasted by tables in schema, in MB. | +| Table size in schema | The size of tables in schema, in MB. | +| Tuples inserted | Tuples inserted in schema over last N minutes. | +| Tuples updated | Tuples updated in schema over last N minutes. | +| Tuples deleted | Tuples deleted from schema over last N minutes. | +| Tuples hot updated | Tuples hot updated in schema, over last N minutes. | +| Sequential Scans | Number of full table scans in schema, over last N minutes. | +| Index Scans | Number of index scans in schema, over last N minutes. | +| Hot update percentage | Percentage of hot updates in the schema over last N minutes. | +| Live Tuples | Number of estimated live tuples in schema. | +| Dead Tuples | Number of estimated dead tuples in schema. | +| Dead tuples percentage | Percentage of estimated dead tuples in schema. | +| Last Vacuum | Hours since last vacuum on the schema. | +| Last AutoVacuum | Hours since last autovacuum on the schema. | +| Last Analyze | Hours since last analyze on the schema. | +| Last AutoAnalyze | Hours since last autoanalyze on the schema. | +| Table Count | Total number of tables in schema. | +| Function Count | Total number of functions in schema. | +| Sequence Count | Total number of sequences in schema. | +| Index size as a percentage of table size | Size of the indexes in schema, as a percentage of their table's size. | +| Largest index by table-size percentage | Largest index in schema, calculated as percentage of its table's size, oc_index, table_size | +| Materialized View bloat | Space wasted by the materialized view, in MB. | +| Total materialized view bloat in schema | The total space wasted by materialized views in schema, in MB. | +| Materialized view size as a multiple of unbloated size | Size of the materialized view as a multiple of estimated unbloated size. | +| Largest materialized view (by multiple of unbloated size) | Largest materialized view in schema, calculated as a multiple of its own estimated unbloated size; exclude materialized view smaller than N MB. | +| Highest materialized view bloat in schema | The most space wasted by a materialized view in schema, in MB. | +| Average materialized view bloat in schema | The average space wasted by materialized views in schema, in MB. | +| Materialized view size | The size of materialized view, in MB. | +| Materialized view size in schema | The size of materialized views in schema, in MB. | +| View Count | Total number of views in schema. | +| Materialized View Count | Total number of materialized views in schema. | +| Materialized View Frozen XID | The age (in transactions before the current transaction) of the materialized view's frozen transaction ID. | + +### Templates applicable on Table + +| Template Name | Description | +| ----------------------------------------- | ---------------------------------------------------------------------------------------------- | +| Table bloat | Space wasted by the table, in MB. | +| Table size | The size of table, in MB. | +| Table size as a multiple of ubloated size | Size of the table as a multiple of estimated unbloated size. | +| Tuples inserted | Tuples inserted in table over last N minutes. | +| Tuples updated | Tuples updated in table over last N minutes. | +| Tuples deleted | Tuples deleted from table over last N minutes. | +| Tuples hot updated | Tuples hot updated in table, over last N minutes. | +| Sequential Scans | Number of full table scans on table, over last N minutes. | +| Index Scans | Number of index scans on table, over last N minutes. | +| Hot update percentage | Percentage of hot updates in the table over last N minutes. | +| Live Tuples | Number of estimated live tuples in table. | +| Dead Tuples | Number of estimated dead tuples in table. | +| Dead tuples percentage | Percentage of estimated dead tuples in table. | +| Last Vacuum | Hours since last vacuum on the table. | +| Last AutoVacuum | Hours since last autovacuum on the table. | +| Last Analyze | Hours since last analyze on the table. | +| Last AutoAnalyze | Hours since last autoanalyze on the table. | +| Row Count | Estimated number of rows in a table. | +| Index size as a percentage of table size | Size of the indexes on table, as a percentage of table's size. | +| Table Frozen XID | The age (in transactions before the current transaction) of the table's frozen transaction ID. | + +### Global Templates + +| Template Name | Description | +| ------------- | --------------------------------------------------- | +| Agents Down | Number of agents that haven't reported in recently. | +| Servers Down | Number of servers that are currently inaccessible. | +| Alert Errors | Number of alerts in an error state. | diff --git a/product_docs/docs/pem/8.0.1/pem_ent_feat/index.mdx b/product_docs/docs/pem/8.0.1/pem_ent_feat/index.mdx new file mode 100644 index 00000000000..bd743b61d8e --- /dev/null +++ b/product_docs/docs/pem/8.0.1/pem_ent_feat/index.mdx @@ -0,0 +1,16 @@ +--- +navTitle: Enterprise Features Guide +title: "PEM Enterprise Features Guide" +--- + +This guide will acquaint you with the tools and wizards that are built into the Postgres Enterprise Manager (PEM) web interface that make it easier for you to monitor and manage your system. + +This guide is not a comprehensive resource; rather, it is meant to serve as an aid to help you evaluate the tool and bring you up to speed with the basics of how to use the product. For more detailed information about using PEM's functionality, please see the online help made available by the PEM client. + +This document uses `Postgres` to mean either the PostgreSQL or EDB Postgres Advanced Server database. + +
+
+what's_new pem_query_tool pem_schema_diff_tool performance_monitoring_and_management capacity_manager audit_manager log_manager sql_profiler tuning_wizard postgres_expert reports monitoring_failover_manager monitoring_xdb_replication_cluster performance_diagnostic reference conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/01_whats_new.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/01_whats_new.mdx
new file mode 100644
index 00000000000..b034874e7ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/01_whats_new.mdx
@@ -0,0 +1,19 @@
+---
+title: "What's New"
+---
+
+The following features have been added to Postgres Enterprise Manager 8.0:
+
+- **Webhooks**: You can now use PEM to send event based notifications to webhook endpoints like third party systems or partner applications.
+- **Performance Diagnostics**: You can now use Performance Diagnostic tool with PostgreSQL 10 or higher versions after installing `edb_wait_states` plugin.
+- **PEM Backend Database**: You can now use PostgreSQL or EDB Postgres Advanced Server 11 or higher versions only as backend databases.
+- **Enhanced Alerting**: You can now replace alert placeholders inside the script and also can view more informative and contextual alert details for few alerts.
+- **Enhanced BART Integration**: You can now configure `bart_socket_name` and also parameters like `--checksum-algorithm` and `--disable-checksum` through PEM.
+- **Security Best Practices**: You can now view the `PEM Security Best Practices` guide from our edb-docs website. It will help to setup PEM in a secure way to minimize the risk of vulnerabilities.
+- **Other features and changes include**:
+ - You can use the `Macros` feature in the `Query tool`.
+ - You can view trigger function under the respective trigger node.
+ - You can download the utility files at the client side using `Storage Manager`.
+ - You can use the open `Query tool` tab to change the database connection.
+ - You can rename the `Query tool` and `Debugger` tab.
+ - You can ignore the owner while comparing the objects through `Schema diff` tool.
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx
new file mode 100644
index 00000000000..119dc8d6bfd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx
@@ -0,0 +1,41 @@
+---
+title: "PEM - Hardware and Software Requirements"
+---
+
+
+
+## Hardware Prerequisites
+
+For optimum performance when monitoring servers and rendering dashboards, we recommend installing PEM on a system with at least:
+
+- 4 CPU cores
+- 8 GB of RAM
+- 100 GB of Storage
+
+Additional disk space is required for data storage. Please note that resource usage will vary based on which probes are defined and enabled, and the activity level on the monitored databases. Monitoring server resources (as you use PEM) will let you know when you need to expand your initial system configuration.
+
+## Software Prerequisites
+
+**Platforms and Versions Support**
+
+For information about the platforms and versions supported by PEM, visit the EnterpriseDB website at:
+
+
+
+prerequisites_for_installing_pem_server installing_pem_server_and_apache_web_server_preferences installing_pem_server_on_linux creating_pem_repository_in_isolated_network configuring_the_pem_server_on_linux installing_pem_agent_on_linux registering_a_pem_agent
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/05_the_pem_web_interface.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/05_the_pem_web_interface.mdx
new file mode 100644
index 00000000000..02610ff1d19
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_linux/05_the_pem_web_interface.mdx
@@ -0,0 +1,33 @@
+---
+title: "The PEM Web Interface"
+---
+
+After installing a PEM server and Agent, you can configure PEM to start monitoring and managing PostgreSQL or Advanced Server instances. The PEM server installer installs the PEM web interface. You can use the interface to review information about objects that reside on monitored servers, or to review statistical information gathered by the PEM server.
+
+After installing and configuring PEM, you can use your browser to access the PEM web interface. Open your browser, and navigate to:
+
+`https://
+
+whats_new pem_hardware_software_requirements pem_architecture installing_postgres_enterprise_manager the_pem_web_interface uninstalling_pem_components reference_linux_service_script conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/01_whats_new.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/01_whats_new.mdx
new file mode 100644
index 00000000000..b034874e7ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/01_whats_new.mdx
@@ -0,0 +1,19 @@
+---
+title: "What's New"
+---
+
+The following features have been added to Postgres Enterprise Manager 8.0:
+
+- **Webhooks**: You can now use PEM to send event based notifications to webhook endpoints like third party systems or partner applications.
+- **Performance Diagnostics**: You can now use Performance Diagnostic tool with PostgreSQL 10 or higher versions after installing `edb_wait_states` plugin.
+- **PEM Backend Database**: You can now use PostgreSQL or EDB Postgres Advanced Server 11 or higher versions only as backend databases.
+- **Enhanced Alerting**: You can now replace alert placeholders inside the script and also can view more informative and contextual alert details for few alerts.
+- **Enhanced BART Integration**: You can now configure `bart_socket_name` and also parameters like `--checksum-algorithm` and `--disable-checksum` through PEM.
+- **Security Best Practices**: You can now view the `PEM Security Best Practices` guide from our edb-docs website. It will help to setup PEM in a secure way to minimize the risk of vulnerabilities.
+- **Other features and changes include**:
+ - You can use the `Macros` feature in the `Query tool`.
+ - You can view trigger function under the respective trigger node.
+ - You can download the utility files at the client side using `Storage Manager`.
+ - You can use the open `Query tool` tab to change the database connection.
+ - You can rename the `Query tool` and `Debugger` tab.
+ - You can ignore the owner while comparing the objects through `Schema diff` tool.
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx
new file mode 100644
index 00000000000..aa06c49b387
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx
@@ -0,0 +1,39 @@
+---
+title: "PEM - Hardware and Software Requirements"
+---
+
+## Hardware Prerequisites
+
+For optimum performance when monitoring servers and rendering dashboards, we recommend installing PEM on a system with at least:
+
+- 4 CPU cores
+- 8 GB of RAM
+- 100 GB of Storage
+
+Additional disk space is required for data storage. Please note that resource usage will vary based on which probes are defined and enabled, and the activity level on the monitored databases. Monitoring server resources (as you use PEM) will let you know when you need to expand your initial system configuration.
+
+## Software Prerequisites
+
+**Supported Platforms and Versions**
+
+For information about the platforms and versions supported by PEM, visit the EnterpriseDB website at:
+
+
+
+installing_pem_server_on_windows installing_pem_agent_on_windows
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/05_the_pem_web_interface.mdx b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/05_the_pem_web_interface.mdx
new file mode 100644
index 00000000000..fcddad6879f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_inst_guide_windows/05_the_pem_web_interface.mdx
@@ -0,0 +1,39 @@
+---
+title: "The PEM Web Interface"
+---
+
+After installing a PEM Server and Agent, you can configure PEM to start monitoring and managing PostgreSQL or Advanced Server instances. The PEM Server installer installs the PEM web interface. You can use the interface to review information about objects that reside on monitored servers, or to review statistical information gathered by the PEM Server.
+
+After installing and configuring PEM, you can use any supported browser to access the PEM web interface. Open your browser, and navigate to:
+
+ `https://
+
+whats_new pem_hardware_software_requirements pem_architecture installing_postgres_enterprise_manager the_pem_web_interface uninstalling_pem_components conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/01_pem_architecture.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/01_pem_architecture.mdx
new file mode 100644
index 00000000000..39d4bf91e18
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/01_pem_architecture.mdx
@@ -0,0 +1,100 @@
+---
+title: "PEM Architecture"
+---
+
+
+
+
+Postgres Enterprise Manager (PEM) is a tool designed to monitor and manage multiple Postgres servers through a single GUI interface. PEM is capable of monitoring the following areas of the infrastructure:
+
+Note: The term Postgres refers to either PostgreSQL or EDB Postgres Advanced Server.
+
+- **Hosts** - One or more servers (physical or virtual) and their operating systems.
+- **Servers** - One or more instances of PostgreSQL or EDB Postgres Advanced Server running on a host.
+- **Databases** - One or more databases and the schema objects (tables, indexes, etc.) within them.
+
+PEM consists of a number of individual software components; the individual components are described below.
+
+- **PEM Server** - The PEM Server is used as the data repository for monitoring data and as a server to which both Agents and Clients connect. The PEM server consists of an instance of PostgreSQL and an associated database for storage of monitoring data, and a server that provides web services.
+- **PEM Agent** - The PEM Agent is responsible for executing tasks and reporting statistics from the Agent host and monitored Postgres instances to the PEM server. A single PEM Agent can monitor multiple installed instances of Postgres that reside on one or many hosts.
+- **PEM Web Client** - The PEM web interface allows you to manage and monitor Postgres servers and utilize PEM extended functionality. The web interface software is installed with the PEM server and is accessed via any supported web browser.
+- **SQL Profiler** - SQL Profiler is a Postgres server plugin to record the monitoring data and query plans to be analysed by the SQL Profiler tool in PEM. This is an optional component of PEM, but the plugin must be installed into each instance of Postgres with which you wish to use the SQL Profiler tool. The SQL Profiler may be used with any supported version of an EnterpriseDB distribution of a PostgreSQL server or Advanced Server (not just those managed through the PEM server). See the [PEM SQL Profiler Configuration Guide](https://www.enterprisedb.com/edb-docs/p/edb-postgres-enterprise-manager) for details and supported versions.
+
+**PEM architecture**
+
+The following architectural diagram illustrates the relationships between the PEM server, clients, and managed as well as unmanaged Postgres servers.
+
+
+
+## **The PEM Server**
+
+
+
+The PEM server consists of an instance of Postgres, an instance of the Apache web-server providing web services to the client, and a PEM Agent. PEM utilizes a server-side cryptographic plugin to generate authentication certificates.
+
+The instance of Postgres (a database server) and an instance of the Apache web-server ( HTTPD) can be on the same host or on separate hosts.
+
+- **Postgres Instance (Database server)** - This is the backend database server. It hosts a database named **pem** which acts as the repository for PEM Server. The **pem** database contains several schemas that store metric data collected from each monitored host, server, and database.
+ - **pem** - This schema is the core of the PEM application. It contains the definitions of configuration functions, tables, or views required by the application.
+ - **pemdata** - This schema stores the current snapshot of the monitored data.
+ - **pemhistory** - This schema stores the historical monitored data.
+- **Apache Web Server (HTTPD)** - The PEM Web Application is deployed as a WSGI application with HTTPD to provide web services to the client. It is comprised of the following:
+ - **Web content presentation** - The presentation layer is created by the Web Application (for example Browser, login page,..).
+ - **Rest API** - The REST API allows integration with other apps and services.
+ - **Database Server Administration/Management** - Database server administration and management activities like CREATE, ALTER, DROP, etc. can be performed for managed as well as unmanaged servers.
+ - **Dashboard/Chart generation** - Internally, the web application includes functionality that generates Dashboards and Charts.
+ - **Management Tools** - The Audit Manager, Capacity Manager, Log Manager, Postgres Expert, Postgres Log Analysis Expert, and the Tuning Wizard are made available in the Web Application.
+ - Other tools provide functionality on managed or unmanaged servers:
+ - **SQL Profiler UI Integration** - SQL Profiler generates easily analyzed traces of session content.
+ - **Query Editor/Data View** - The Query editor allows you to query, edit, and view data.
+ - **Debugger** - The Debugger helps you debug queries.
+ - **Performance Diagnostics** - Performance Diagnostics help you analyze the performance of Advanced Server.
+
+We recommended that you use a dedicated machine to host production instances of the PEM backend database. The host may be subject to high levels of data throughput, depending on the number of database servers that are being monitored and the workloads the servers are processing.
+
+## **The PEM Agent**
+
+
+
+The PEM Agent is responsible for the collection of monitoring data from the machine and operating system, as well as from each of the Postgres instances to which they are bound. Each PEM Agent can monitor one physical or virtual machine and is capable of monitoring multiple database servers locally - installed on the same system, or remotely - installed on other systems. It is also responsible for executing other tasks that may be scheduled by the user (for example, server shutdowns, SQL Profiler traces, user-defined jobs).
+
+A PEM Agent is installed by default on the PEM Server along with the installation of the PEM Server. It is generally referred to as a PEM Agent on the PEM Host. Separately, the PEM Agent can also be installed on the other servers hosting the Postgres instances to be monitored using PEM.
+
+Whether monitoring locally or remotely, the PEM Agent connects to the PEM Server using PostgreSQL’s libpq, using SSL certificate-based authentication. The PEM Agent installer in Windows and pemworker CLI in Linux is responsible for registering each agent with the PEM Server, and generating and installing the required certificates.
+
+Please note that there is only one-way traffic between the PEM Agent and PEM Server; the PEM Agent always connects to the PEM Server.
+
+The PEM Agent must be able to connect to each database server that it monitors. This connection is made over a TCP/IP connection (or optionally a Unix Domain Socket on Unix hosts), and may optionally use SSL. The user must configure the connection and authentication to the monitored server.
+
+Once configured, each agent collects statistics and other information on the host and each database server and database that it monitors. Each piece of information is known as a **metric** and is collected by a **probe**. Most probes will collect multiple metrics at once for efficiency. Examples of the metrics collected include:
+
+- Disk I/O statistics
+- Network statistics
+- Database server version string
+- Database server configuration option (GUC) values
+- Table access statistics
+- Table and index sizes
+
+A list of PEM probes can be found [here](../04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/#pem_probes).
+
+By default, the PEM Agent bound to the database server collects the OS/Database monitoring statistics and also runs any scheduled tasks/jobs for that particular database server, storing data in the pem database on the PEM server.
+
+The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in the pem database on the PEM server and is then processed by the PEM Agent on the PEM Host by default. However, processing by other PEM Agents can be enabled by adjusting the SNMP/SMTP and Nagios parameters of the PEM Agents.
+
+To see more information about these parameters see [Server Configuration](../04_toc_pem_features/02_pem_server_config/#pem_server_config).
+
+## **The PEM Web Client**
+
+The PEM client is a web-based application that runs in supported browsers. The client's web interface connects to the PEM server and allows direct management of managed or unmanaged servers, and the databases and schemas that reside on them.
+
+The client allows you to use PEM functionality that makes use of the data logged on the server through features such as the dashboards, the Postgres Log Analysis Expert, and Capacity Manager.
+
+## **The SQL Profiler Plugin**
+
+You are not required to install the SQL Profiler plugin on every server, but you must install and configure the plugin on each server on which you wish to use the SQL Profiler. You may also want to install and configure SQL Profiler on un-monitored development servers. For ad-hoc use also, you may temporarily install the SQL Profiler plugin.
+
+The plugin is installed with the EDB Postgres Advanced Server distribution but must be installed separately for use with PostgreSQL. The SQL Profiler installer is available from the [EnterpriseDB website](http://www.enterprisedb.com/download-postgres-enterprise-manager).
+
+SQL Profiler may be used on servers that are not managed through PEM, but to perform scheduled traces, a server must have the plugin installed, and must be managed by an installed and configured PEM agent.
+
+For more information about using SQL Profiler, see the [PEM SQL Profiler Configuration Guide](https://www.enterprisedb.com/edb-docs/p/edb-postgres-enterprise-manager)
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/02_pem_server_logon.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/02_pem_server_logon.mdx
new file mode 100644
index 00000000000..2ec3b0c35aa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/02_pem_server_logon.mdx
@@ -0,0 +1,31 @@
+---
+title: "PEM Server Logon"
+---
+
+
+
+
+The PEM web interface uses Apache to connect to the PEM server on port 8080 of the IP address on which the PEM server is installed. To connect to PEM, open your browser of choice, and navigate to:
+
+> *<ip\_address\_of\_PEM\_host>:8080/pem*
+
+Where `ip_address_of_PEM_host` specifies the IP address of the host of the PEM server.
+
+
+
+Use the fields on the Login window to authenticate yourself with the PEM server:
+
+- Provide the name of a `pem` database user in the `Username` field. Users logon to PEM using user credentials setup as `login roles` on the PostgreSQL database used by the PEM server. By default, the `postgres` superuser account will be used for the initial logon.
+
+ We strongly recommend you create an individual role for each user. You can create a login role with the `CREATE ROLE` SQL statement, or by defining a role with the PEM client `Create - Login/Group Role` dialog. To access the dialog, connect to the PEM server database; right-click the `Login/Group Roles` node in the tree control, and select `New Login Role...` from the `Create` pull-aside menu. Roles must be granted permissions and role memberships to properly use PEM:
+
+ - users that are members of the `pem_user` role are essentially `read-only` users; they may view dashboards, change the database server connection options, but they will not be able to install agents or configure the server directory, alerts, probes, or run any of the wizard/dialog based components of PEM.
+ - users that are members of the `pem_admin` role have the same read permissions as members of the pem\_user role, plus sufficient privileges to configure the servers, directory, alerts and probes.
+ - `administrative` users must be added to the pem\_admin role and explicitly granted the create role privilege. in addition to the permissions granted through membership in the pem\_admin role, the create role privilege allows an administrator to create additional pem users, and to install and register new agents.
+ - users can be member of one of the [PEM roles](../01_toc_pem_getting_started/#pem_roles) to give right to run a particular component, to manage, or to configure PEM.
+
+- Provide the password associated with the user in the `Password` field.
+
+After providing your credentials, click `Login` to connect to the PEM client. PEM opens, displaying the `Global Overview` Dashboard:
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/03_pem_managing_configuration_settings.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/03_pem_managing_configuration_settings.mdx
new file mode 100644
index 00000000000..0cb08ae21ba
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/03_pem_managing_configuration_settings.mdx
@@ -0,0 +1,20 @@
+---
+title: "Managing Configuration Settings"
+---
+
+
+
+
+There are multiple configuration files that are read at startup by Postgres Enterprise Manager. These are as follows:
+
+- `config.py`: This is the main configuration file, and should not be modified. It can be used as a reference for configuration settings, that may be overridden in one of the following files.
+- `config_distro.py`: This file is read after `config.py` and is intended for packagers to change any settings that are required for their Postgres Enterprise Manager distribution. This may typically include certain paths and file locations. This file is optional, and may be created by packagers in the same directory as `config.py` if needed.
+- `config_local.py`: This file is read after `config_distro.py` and is intended for end users to change any default or packaging specific settings that they may wish to adjust to meet local preferences or standards.This file is optional, and may be created by users in the same directory as `config.py` if needed.
+
+The default `config.py` file is shown below for reference:
+
+
+
+../../web/config.py
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/04_pem_roles.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/04_pem_roles.mdx
new file mode 100644
index 00000000000..2a5c6f37562
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/04_pem_roles.mdx
@@ -0,0 +1,60 @@
+---
+title: "Roles for managing PEM"
+---
+
+
+
+
+You can use the `Login/Group Role` dialog to allow a role with limited privileges to access PEM features such as the Audit Manager, Capacity Manager, or SQL Profiler. PEM pre-defined roles allow access to PEM functionality; roles that are assigned membership in these roles can access the associated feature.
+
+
+
+When defining a user, use the `Membership` tab to specify the roles in which the new user is a member. The new user will share the privileges associated with each role in which it is a member. For a user to have access to PEM extended functionality, the role must be a member of the pem\_user role and the pre-defined role that grants access to the feature. Use the `Roles` field to select pre-defined role names from a drop down list.
+
+Check the checkbox to the right of the role name to allow administrative access to the functionality.
+
+The `SQL` tab displays the SQL command that the server will execute when you click `Save`.
+
+
+
+The examples shown above creates a login role named `acctg_clerk` that will have access to the Audit Manager; the role can make unlimited connections to the server at any given time.
+
+You can use PEM pre-defined roles to allow access to the functionality listed in the table below:
+
+| Value | Parent Role | Description |
+|-------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| pem\_super\_admin | | Role for administration/management/configuration of all the objects within Postgres Enterprise Manager console. |
+| pem\_admin | pem\_super\_admin | Role for administration/management/configuration of all the agents, servers, or monitored objects that are visible to a user having pem\_admin role. A user with pem\_admin role can view and manage only those objects where this role has been mentioned in the Team field under the server's properties. |
+| pem\_user | | Role for having read-only access to all the agents, servers, or monitored objects that are visible to a user having pem\_user role. A user with pem\_user role can view only those objects where this role has been mentioned in the Team field under the server's properties. |
+| pem\_config | pem\_admin | Role for configuration management of Postgres Enterprise Manager. |
+| pem\_component | pem\_admin | Role to run/execute all wizard/dialog based components. |
+| pem\_rest\_api | pem\_admin | Role to access the REST API. |
+| pem\_server\_service\_manager | pem\_admin | Role for allowing to restart/reload the monitored database server (if server-id provided). |
+| pem\_manage\_schedule\_task | pem\_admin | Role to configure the schedule tasks. |
+| pem\_manage\_alert | pem\_admin | Role for managing/configuring alerts, and its templates. |
+| pem\_config\_alert | pem\_config, pem\_manage\_alert | Role for configuring the alerts on any monitored objects. |
+| pem\_manage\_probe | pem\_admin | Role to create, update, delete the custom probes, and change custom probe configuration. |
+| pem\_config\_probe | pem\_config, pem\_manage\_probe | Role for probe configuration (history retention, execution frequency, enable/disble the probe) on all visible monitored objects. |
+| pem\_database\_server\_registration | pem\_admin | Role to register a database server. |
+| pem\_comp\_postgres\_expert | pem\_component | Role to run the Postgres Expert. |
+| pem\_comp\_auto\_discovery | pem\_component | Role to run the Auto discovery of a database server dialog. |
+| pem\_comp\_log\_analysis\_expert | pem\_component | Role to run the Log Analysis Expert. |
+| pem\_comp\_sqlprofiler | pem\_component | Role to run the SQL Profiler. |
+| pem\_manage\_efm | pem\_admin | Role to manage Failover Manager functionalities. |
+| pem\_comp\_capacity\_manager | pem\_component | Role to run the Capacity Manager. |
+| pem\_comp\_log\_manager | pem\_component | Role to run the Log Manager. |
+| pem\_comp\_audit\_manager | pem\_component | Role to run the Audit Manager. |
+| pem\_comp\_tuning\_wizard | pem\_component | Role to run the Tuning Wizard. |
+| pem\_comp\_bart | pem\_component | Role to configure and manage BART server. |
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/05_group_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/05_group_dialog.mdx
new file mode 100644
index 00000000000..43ba5a3bc88
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/05_group_dialog.mdx
@@ -0,0 +1,18 @@
+---
+title: "The Group Dialog"
+---
+
+
+
+
+Use the `Group` dialog to add a new group to the PEM client tree control. You can use a group to simplify management of related servers or agents.
+
+
+
+Use the `Name` field to specify a name that will identify the group in the `PEM` browser tree control.
+
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
+
+To add a server or agent to a group, right-click on the name of a server or agent, and select `Properties...` to open the properties dialog. Then, use the drop-down listbox in the `Group` field to select the group in which the object should reside.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/06_auto_discovery_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/06_auto_discovery_dialog.mdx
new file mode 100644
index 00000000000..cd1925544e4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/06_auto_discovery_dialog.mdx
@@ -0,0 +1,40 @@
+---
+title: "Automatic Discovery of Servers"
+---
+
+
+
+
+Use the `Auto Discovery` dialog to instruct a PEM agent to locate database servers that reside on a monitored system, and add a binding that allows the agent to monitor the selected server.
+
+To enable auto discovery for a specific agent, you must enable the `Server Auto Discovery` probe. To access the `Manage Probes` tab, highlight the name of a PEM agent in the PEM client tree control, and select `Manage Probes...` from the `Management` menu. When the Manage Probes tab opens, confirm that the slider control in the `Enabled?` column is set to `Yes`.
+
+To open the `Auto Discovery` dialog, highlight the name of a PEM agent in the PEM client tree control, and select `Auto Discovery...` from the `Management` menu.
+
+
+
+When the `Auto Discovery` dialog opens, the `Discovered Database Servers` box will display a list of servers that are not currently monitored by a PEM agent. Check the box next to a server name to display information about the server in the `Server Connection Details` box, and provide any missing information to bind the server to the currently selected agent in the `Agent Connection Details` box.
+
+Use the `Select All` button to select the box next to all of the displayed servers, or `Unselect All` to unselect all of the boxes to the left of the server names.
+
+The fields in the `Server Connection Details` box provide information about the server that PEM will monitor:
+
+- Accept or modify the name of the monitored server in the `Name` field. The specified name will be displayed in the tree control of the PEM client.
+- Use the `Server group` drop-down listbox to select the server group under which the server will be displayed in the PEM client tree control.
+- Use the `Host name/address` field to specify the IP address of the monitored server.
+- The `Port` field displays the port that is monitored by the server; this field may not be modified.
+- Provide the name of the service in the `Service ID` field. Please note that the service name must be provided to enable some PEM functionality.
+- By default, the `Maintenance database` field indicates that the selected server uses a `postgres` maintenance database. Customize the content of the `Maintenance database` field for your installation.
+
+The fields in the `Agent Connection Details` box specify the properties that the PEM agent will use when connecting to the server:
+
+- The `Host` field displays the IP address that will be used for the PEM agent binding.
+- The `Username` field displays the name that will be used by the PEM agent when connecting to the selected server.
+- The `Password` field displays the password associated with the specified user name.
+- Use the drop-down listbox in the `SSL mode` field to specify your SSL connection preferences.
+
+When you've finished specifying the connection properties for the servers that you are binding for monitoring, click the `OK` button to save the properties. Click `Cancel` to exit without preserving any changes.
+
+
+
+The dialog shown above displays the values required to bind an instance of Advanced Server for monitoring by PEM.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx
new file mode 100644
index 00000000000..419abef0210
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx
@@ -0,0 +1,105 @@
+---
+title: "Defining a server"
+---
+
+
+
+
+Use the `Create - Server` dialog to describe a new server connection, bind the server to a PEM agent, and display the server to the PEM tree control.
+
+
+
+Use the fields on the `General` tab to describe the general properties of the server:
+
+- Use the `Name` field to specify a user-friendly name for the server. The name specified will identify the server in the PEM client tree control.
+- You can use [groups](../01_toc_pem_getting_started/#group_dialog) to organize your servers and agents in the PEM client tree control. Using groups can help you manage large numbers of servers more easily. For example, you may want to have a production group, a test group, or LAN specific groups. Use the `Group` drop-down listbox to select the group in which the new server will be displayed.
+- Use the `Team` field to specify a PostgreSQL role name. Only PEM users who are members of this role, who created the server initially, or have superuser privileges on the PEM server will see this server when they logon to PEM. If this field is left blank, all PEM users will see the server.
+- Use the `Background` color selector to select the color that will be displayed in the PEM tree control behind database objects that are stored on the server.
+- Use the `Foreground` color selector to select the font color of labels in the PEM tree control for objects stored on the server.
+- Check the box next to `Connect now?` to instruct PEM to attempt a connection to the database server when you click the Save button on the Create - Server dialog. Leave the `Connect now?` checkbox unchecked if you do not want to establish a connection to the server immediately. If you do not select the `Connect now?` option, the connection parameters are not validated until you attempt a connection.
+- Provide notes about the server in the `Comments` field.
+
+
+
+Use fields on the `Connection` tab to specify connection details for the server:
+
+- Specify the IP address of the server host, or the fully qualified domain name in the `Host name/address` field. On Unix based systems, the address field may be left blank to use the default PostgreSQL Unix Domain Socket on the local machine, or may be set to an alternate path containing a PostgreSQL socket. If you enter a path, the path must begin with a "/".
+- Specify the port number of the host in the `Port` field.
+- Use the `Maintenance database` field to specify the name of the initial database that PEM will connect to, and that will be expected to contain the [pgAgent](../10_pgagent/#pgagent) schema and adminpack objects if installed (both are optional). On an Advanced Server database, the maintenance database is named 'edb'. On PostgreSQL 8.1 and above, the maintenance DB for PostgreSQL is named 'postgres'; on earlier versions 'template1' is often used, though it is preferrable to create a 'postgres' database for this purpose to avoid cluttering the template database.
+- Specify the name that will be used when authenticating with the server in the `Username` field.
+- Provide the password associated with the specified user in the `Password` field.
+- Check the box next to `Save password?` to instruct the PEM server to save the password in encrypted format on the PEM server backend database server for later reuse. Password will be stored per server per user basis, hence - it won't be shared with other team members. To remove a password, disconnect from the server, click on the 'Clear Saved Password' menu item under Object/Context menu of the database server.
+- Use the `Role` field to specify the name of the role that is assigned the privileges that the client should use after connecting to the server. This allows you to connect as one role, and then assume the permissions of another role when the connection is established (the one you specified in this field). The connecting role must be a member of the role specified.
+
+
+
+Use the fields on the `SSL` tab to configure SSL.
+
+- Use the drop-down list box in the `SSL mode` field to select the type of SSL connection the server should use. For more information about using SSL encryption, see [Section 33.18 of the Postgres documentation](https://www.postgresql.org/docs/current/static/libpq-ssl.html).
+
+You can use the platform-specific File manager dialog to upload files that support SSL encryption to the server. To access the File manager dialog, click the icon that is located to the right of each of the following fields.
+
+- Use the `Client certificate` field to specify the file containing the client SSL certificate. This file will replace the default `~/.postgresql/postgresql.crt` if PEM is installed in Desktop mode, and `
+
+Note
+
+
+
+The difference between pem\_admin role and pem\_super\_admin role is that a user with pem\_admin role can view and manage only those objects where the role has been mentioned in the Team field under the server's properties, while a user with pem\_super\_admin role can view and manage all the objects within Postgres Enterprise Manager console.
+
+
+
+
+
+The PEM Agent running on AWS EC2 or on your local machine should be registered to the PEM Server. Please note that when registering the PEM Agent with the PEM Server you should use the hostname of AWS EC2 instance. For more details on registering the PEM Agent see, [PEM Self Registration](../02_toc_pem_agent/#pem_agent_self_registration).
+
+You can register the Postgres instance running on AWS EC2 on PEM Server using the `Create - Server` dialog. For more details on registering the server using `Create - Server` dialog see, [Define a Server](../01_toc_pem_getting_started/#pem_define_connection). Use the `PEM Agent` tab on the `Create - Server` dialog to bind the registered PEM Agent with the Postgres instance.
+
+When the PEM Agent is registered to the PEM Server and your Postgres instance that is running on AWS EC2 is registered to the PEM Server, you can monitor your instance with PEM.
+
+## Monitoring a Postgres Instance Running on AWS RDS
+
+While creating an AWS RDS database, choose `PostgreSQL` when prompted for `Engine options`. After creating a `Postgres(RDS)` instance on AWS, use `Create - Server` dialog to add the `Postgres(RDS)` instance to the PEM Server. Using this dialog you can describe a new server connection, bind the server to a PEM Agent, and display the server to the PEM browser tree control.
+
+For detailed information on the `Create - Server` dialog and configuration details for each tab, see [Define a Server](../01_toc_pem_getting_started/#pem_define_connection).
+
+The `PEM Agent` tab in the `Create - Server` dialog must have the `Remote Monitoring` field set to `Yes` to monitor the `Postgres(RDS)` instance on AWS instance using PEM Server.
+
+
+
+As the PEM Agent will be monitoring the Postgres(RDS) AWS instance remotely, the functionality will be limited as described below:
+
+| **Feature Name** | **Works with remote PEM Agent** | **Comments** |
+|------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Audit Manager | No | |
+| Capacity Manager | Limited | There will be no correlation between the database server and operating system metrices. |
+| Log Manager | No | |
+| Manage Alerts | Limited | When you run an alert script on the database server, it will run on the machine where the bound PEM Agent is running, and not on the actual database server machine. |
+| Manage Charts | Yes | |
+| Manage Dashboards | Limited | Some dashboards may not be able to show complete data. For example, the operating system information of the database server will not be displayed as it is not available. |
+| Manage Probes | Limited | Some of the PEM probes will not return information, and some of the functionalities may be affected. For details about probe functionality, see the [PEM Agent Guide](https://enterprisedb.com/edb-docs). |
+| Postgres Expert | Limited | The Postgres Expert will provide partial information as operating system information is not available. |
+| Postgres Log Analysis Expert | No | The Postgres Log Analysis Expert will not be able to perform an analysis as it is dependent on the logs imported by log manager, which will not work as required. |
+| Scheduled Tasks | Limited | Scheduled tasks will work only for database server; scripts will run on a remote Agent. |
+| Tuning Wizard | No | |
+| System Reports | Yes | |
+| Core Usage Reports | Limited | The Core Usage report will not show complete information. For example, the platform, number of cores, and total RAM will not be displayed. |
+| Managing BART | No | BART requires password less authentication between two machines, where database server and BART are installed. An AWS RDS instance doesn't allow to use host access. |
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/09_pem_connect_to_server.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/09_pem_connect_to_server.mdx
new file mode 100644
index 00000000000..613972609f2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/09_pem_connect_to_server.mdx
@@ -0,0 +1,27 @@
+---
+title: "Connect to server"
+---
+
+
+
+
+After defining a server connection, use the `Connect to Server` dialog to authenticate with a server and access the objects stored on the server. To access the dialog, right click on the server name in the PEM client tree control, and select `Connect Server` from the context menu.
+
+
+
+If prompted, provide authentication information for the selected server:
+
+> - Use the `Password` field to provide the password of the user that is associated with the defined server.
+> - Check the box next to `Save Password` to instruct the server to save the password for future connections; if you save the password, you will not be prompted when reconnecting to the database server with this server definition.
+
+The browser displays a message in a green status bar in the lower right corner when the server connects successfully.
+
+If you receive an error message while attempting a connection, verify that your network is allowing PEM and the host of the database server to communicate. For detailed information about a specific error message, please see the [Connection Error](../01_toc_pem_getting_started/#connect_error) help page.
+
+To review or modify connection details, right-click on the name of the server, and select `Properties...` from the context menu.
+
+## Disconnecting from a Server
+
+To disconnect from a server, right-click on the server name in the `Browser` tree control and select Disconnect Server from the context menu. A popup will ask you to confirm that you wish to disconnect the selected server.
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/10_control_server.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/10_control_server.mdx
new file mode 100644
index 00000000000..bb6c9599333
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/10_control_server.mdx
@@ -0,0 +1,11 @@
+---
+title: "Controlling a Server"
+---
+
+
+
+
+If you provided a `Service ID` on the `Advanced` tab of the [Server](../01_toc_pem_getting_started/#pem_define_connection) property dialogue, the PEM server can control the database service process.
+
+> - If the PEM client is running on a Windows machine, it can control the postmaster service if you have sufficient access rights. In case of a remote server, the service name must be prepended by the machine name (e.g. PSE1pgsql-8.0).
+> - If the PEM client is running on a Unix machine, it can control processes running on the local machine if you have sufficient access rights. When executing service control functions, PEM will append status/start/stop keywords to the service name provided.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/11_connect_error.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/11_connect_error.mdx
new file mode 100644
index 00000000000..a07e874eb92
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/11_connect_error.mdx
@@ -0,0 +1,45 @@
+---
+title: "Connection error"
+---
+
+
+
+
+When connecting to a PostgreSQL server, you may get an error message. If you encounter an error message, please review the message carefully; each error message attempts to incorporate the information you'll need to resolve the problem. For more details about specific errors, please locate the error message in the list below:
+
+**Connection to the server has been lost**
+
+
+
+This error message indicates that the connection attempt has taken longer than the specified threshold; there may be a problem with the connection properties provided on the `Server` dialog, network connectivity issues, or the server may not be running.
+
+**could not connect to Server: Connection refused**
+
+
+
+If pgAdmin displays this message, there are two possible reasons for this:
+- the database server isn't running - simply start it.
+- the server isn't configured to accept TCP/IP requests on the address shown.
+
+For security reasons, a PostgreSQL server "out of the box" doesn't listen on TCP/IP ports. Instead, it must be enabled to listen for TCP/IP requests. This can be done by adding **tcpip = true** to the postgresql.conf file for Versions 7.3.x and 7.4.x, or **listen\_addresses='\*'** for Version 8.0.x and above; this will make the server accept connections on any IP interface.
+
+For further information, please refer to the PostgreSQL documentation about [runtime configuration](http://www.postgresql.org/docs/current/interactive/runtime-config.html).
+
+**FATAL: no pg\_hba.conf entry**
+
+
+
+If pgAdmin displays this message when connecting, your server can be contacted correctly over the network, but is not configured to accept your connection. Your client has not been detected as a legal user for the database.
+
+To connect to a server, the pg\_hba.conf file on the database server must be configured to accept connections from the host of the pgAdmin client. Modify the pg\_hba.conf file on the database server host, and add an entry in the form:
+
+> - **host template1 postgres 192.168.0.0/24 md5** for an IPV4 network
+> - **host template1 postgres ::ffff:192.168.0.0/120 md5** for an IPV6 network
+
+For more information, please refer to the PostgreSQL documentation about [client authentication](http://www.postgresql.org/docs/current/interactive/client-authentication.html).
+
+**FATAL: password authentication failed**
+
+
+
+- The `password authentication failed for user` error message indicates there may be a problem with the password you entered. Retry the password to confirm you entered it correctly. If the error message returns, make sure that you have the correct password, that you are authorized to access the server, and that the access has been correctly configured in the server's postgresql.conf configuration file.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/index.mdx
new file mode 100644
index 00000000000..66b888c90fe
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/01_toc_pem_getting_started/index.mdx
@@ -0,0 +1,28 @@
+---
+title: "PEM Getting Started"
+---
+
+
+
+
+You can use either a graphical installer or an RPM package to install the PEM server and PEM agent; for detailed installation instructions, please see the Postgres Enterprise Manager Installation Guide, available at www.enterprisedb.com.
+
+Contents:
+
+
+
+Note
+
+
+
+In the first two scenarios, you must configure the VPN on AWS EC2 , so the AWS EC2 instance can access the `pem` database. Please contact your network administrator to setup the VPN if needed.
+
+
+
+pem\_architecture pem\_server\_logon pem\_managing\_configuration\_settings pem\_roles
+
+
+
+Each `server` in the PEM client tree control defines a set of connection and authentication properties that creates a connection to a Database server. The server can optionally bind the server to a PEM agent, defining a `managed` server, or not specify an agent binding, defining an `unmanaged` server. The process of defining the connection to a server is referred to as registering a server. You can use the `Auto Discovery` dialog to simplify the process of registering a managed server, or register a server manually.
+
+You can (optionally) use the `Server Group` dialog to create server groups to organize the server connections within the tree control for easier server management. To open the `Server Group` dialog, open the `Object` menu, and select `Server Group` from the `Create` menu.
+
+Contents:
+
+
+
+group\_dialog auto\_discovery\_dialog pem\_define\_connection pem\_define\_aws\_instance\_connection pem\_connect\_to\_server control\_server connect\_error
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/01_pem_agent_properties.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/01_pem_agent_properties.mdx
new file mode 100644
index 00000000000..ea508368ec1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/01_pem_agent_properties.mdx
@@ -0,0 +1,32 @@
+---
+title: "PEM Agent Properties"
+---
+
+
+
+
+The `PEM Agent Properties` dialog provides information about the PEM agent from which the dialog was opened; to open the dialog, right-click on an agent name in the PEM client tree control, and select `Properties` from the context menu.
+
+
+
+- The `Description` field displays a modifiable description of the PEM agent. This description is displayed in the tree control of the PEM client.
+- You can use [groups](../01_toc_pem_getting_started/#group_dialog) to organize your servers and agents in the PEM client tree control. Use the `Group` drop-down listbox to select the group in which the agent will be displayed.
+- Use the `Team` field to specify the name of the group role that should be able to access servers monitored by the agent; the servers monitored by this agent will be displayed in the PEM client tree control to connected team members. Please note that this is a convenience feature. The `Team` field does not provide true isolation, and should not be used for security purposes.
+- The `Heartbeat interval` fields displays the length of time that will elapse between reports from the PEM agent to the PEM server. Use the selectors next to the `Minutes` or `Seconds` fields to modify the interval.
+
+
+
+Use the fields on the `Job Notifications` tab to configure the email notification settings on agent level:
+
+- Use the `Override default configuration?` switch to specify if you want the agent level job notification settings to override the default job notification settings. If you select Yes for this switch, you can use the rest of the settings on this dialog to define when and to whom the job notifications should be sent. Please note that the rest of the settings on this dialog work only if you enable the `Override default configuration?` switch.
+- Use the `Email on job completion?` switch to specify if the job notification should be sent on the successful job completion.
+- Use the `Email on a job failure?` switch to specify if the job notification should be sent on the failure of a job.
+- Use the `Email group` field to specify the email group to whom the job notification should be sent.
+
+
+
+`Agent Configurations` tab lists down all the current configurations and capabilities of a agent.
+
+- The `Parameter` column displays list of parameters.
+- The `Value` column displays current value of the corresponding parameter.
+- The `Category` column displays category of the corresponding parameter, it can be either "configuration" or "capability".
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/01_pem_agent_config_params.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/01_pem_agent_config_params.mdx
new file mode 100644
index 00000000000..c16f844165d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/01_pem_agent_config_params.mdx
@@ -0,0 +1,60 @@
+---
+title: "PEM Agent Configuration Parameters"
+---
+
+
+
+
+A number of user-configurable parameters and registry entries control the behavior of the PEM Agent. With the exception of the PEM\_MAXCONN (or pem\_maxconn) parameter, we strongly recommend against modifying any of the configuration parameters or registry entries listed below without first consulting EnterpriseDB support experts.
+
+> - On 32 bit Windows systems, PEM registry entries are located in HKEY\_LOCAL\_MACHINE\\Software\\EnterpriseDB\\PEM\\agent
+> - On 64 bit Windows systems, PEM registry entries are located in HKEY\_LOCAL\_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent
+> - On Linux systems, PEM configuration options are stored in the agent.cfg file, located (by default) in /usr/edb/pem/agent/etc
+
+| **Parameter Name** | **Description** | **Value (if applicable)** |
+|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PEM\_HOST (on Windows) or pem\_host (on Linux) | The IP address or hostname of the PEM server. | By default, set to 127.0.0.1. |
+| PEM\_PORT (on Windows) or pem\_port (on Linux) | The database server port to which the agent connects to communicate with the PEM server. | By default, the PEM server monitors port 5432. |
+| AgentID (on Windows) or agent\_id (on Linux) | A unique identifier assigned to the PEM agent. | The first agent is assigned an identifier of '1', the second agent is assigned an identifier of '2', and so on. |
+| AgentUser (on Windows) or agent\_user (on Linux) | User to connect the PEM database server | If present, and not set to empty string, it will be used to connect the PEM database server. |
+| AgentCrtPath (on Windows) or agent\_ssl\_crt (on Linux) | The complete path to the PEM agent's certificate file. | By default, on Windows, C:\\Users\\user\_name\\AppData\\Roaming\\pem/agent.crt. By default on Linux, /root/.pem/agent.crt. |
+| AgentKeyPath (on Windows) or agent\_ssl\_key (on Linux) | The complete path to the PEM agent's key file. | By default, on Windows, C:\\Users\\user\_name\\AppData\\Roaming\\pem/agent.key. By default on Linux, /root/.pem/agent.key. |
+| AgentFlagDir (on Windows) or agent\_flag\_dir (on Linux) | Used for HA support. Specifies the directory path checked for requests to take over monitoring another server. Requests are made in the form of a file in the specified flag directory. | Not set by default. This option allows you to override the hard-coded default. |
+| LogLevel (on Windows) or log\_level (on Linux) | Log level specifies the type of event that will be written to the PEM log files. | Log level may be set to: error, debug1, debug2, or warning By default, log level is set to `warning` |
+| log\_location (on Linux only) | Specifies the location of the PEM worker log file. | On Linux, /var/log/pem/worker.log. On Windows, Logs & errors will be reported in the Application event log. |
+| agent\_log\_location (on Linux only) | Specifies the location of the PEM agent log file. | On Linux, /var/log/pem/agent.log. On Windows, Logs & errors will be reported in the Application event log. |
+| ShortWait (on Windows) or short\_wait (on Linux) | The minimum length of time (in seconds) that the PEM agent will wait before checking which probes are next in the queue (waiting to run). | By default, 10 seconds. |
+| LongWait (on Windows) or long\_wait (on Linux) | The maximum length of time (in seconds) that the PEM agent will wait before attempting to connect to the PEM server if an initial connection attempt fails. | By default, 30 seconds. |
+| AlertThreads (on Windows) or alert\_threads (on Linux) | The number of alert threads to be spawned by the agent. | Set to 1 for the agent that resides on the host of the PEM server; should be set to 0 for all other agents. |
+| EnableSMTP (on Windows) or enable\_smtp (on Linux) | When set to true for multiple PEM Agents (7.13 or lesser) and PEM backend database (9.4 or lesser) then it may send more duplicate emails. Whereas for PEM Agents (7.14 or higher) and PEM backend database (9.5 or higher) then it may send lesser duplicate emails. | By default, set to true for the agent that resides on the host of the PEM server; false for all other agents. |
+| EnableSNMP (on Windows) or enable\_snmp (on Linux) | When set to true for multiple PEM Agents (7.13 or lesser) and PEM backend database (9.4 or lesser) then it may send more duplicate traps. Whereas for PEM Agents (7.14 or higher) and PEM backend database (9.5 or higher) then it may send lesser duplicate traps. | By default, set to true for the agent that resides on the host of the PEM server; false for all other agents. |
+| enable\_nagios (on Linux only) | When set to true, Nagios alerting is enabled. | By default, set to true for the agent that resides on the host of the PEM server; false for all other agents. |
+| EnableWebhook (on Windows) or enable\_webhook (on Linux) | When set to true, Webhook alerting is enabled. | By default, set to true for the agent that resides on the host of the PEM server; false for all other agents. |
+| MaxWebhookRetries (on Windows) or max\_webhook\_retries (on Linux) | Set maximum number of times pemAgent should retry to call webhooks on failure. | Default 3. |
+| ConnectTimeout (on Windows) or connect\_timeout (on Linux) | The maximum length of time (in seconds, written as a decimal integer string) that the agent will wait for a connection. | Not set by default. If set to 0, the agent will wait indefinitely. |
+| AllowServerRestart (on Windows) or allow\_server\_restart (on Linux) | If set to TRUE, the agent can restart the database server that it monitors. Some PEM features may be enabled/disabled, depending on the value of this parameter. | By default, set to TRUE. |
+| MaxConnections (on Windows) or max\_connections (on Linux) | The maximum number of probe connections used by the connection throttler. | By default, set to 0 (an unlimited number of connections). |
+| ConnectionLifetime (on Windows) or connection\_lifetime (on Linux) | Use ConnectionLifetime (or connection\_lifetime) to specify the minimum number of seconds an open but idle connection is retained. This parameter is ignored if the value specified in MaxConnections is reached and a new connection (to a different database) is required to satisfy a waiting request. | By default, set to 0 (a connection is dropped when the connection is idle after the agent's processing loop completes a cycle in which the connection has not been used). |
+| HeartbeatConnection (on Windows) or heartbeat\_connection (on Linux) | When set to TRUE, a dedicated connection used for sending the heartbeats. | By default, set to FALSE. |
+| AllowBatchProbes (on Windows) or allow\_batch\_probes (on Linux) | If set to TRUE, the user will be able to create batch probes using custom probes feature. | By default, set to FALSE. |
+| BatchScriptDir (on Windows) or batch\_script\_dir (on Linux) | Provide the path where script file (for alerting) will be stored. | On Windows, C:Usersuser\_nameAppDataLocalTemp. On Linux, set to /tmp. |
+| AllowBatchJobSteps (on Windows) or batch\_script\_user | Provide the username who will run the script. | On Windows, set to TRUE and restart PEM Agent. Entries located in HKEY\_LOCAL\_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent. On Linux, Restart the agent after modifying the file. If you do not specify a user, or the specified user does not exist, then the script will not be executed. |
+| ConnectionCustomSetup (on Windows) or connection\_custom\_setup (on Linux) | Use this parameter to provide SQL code that will be invoked each time a new connection with the monitored server is established. | By default, no value is provided. |
+| ca\_file (Linux only) | Provide the path where the CA certificate resides. | By default, /opt/PEM/agent/share/certs/ca-bundle.crt |
+| WebhookSSLKey (on Windows) or webhook\_ssl\_key (on Linux) | The complete path to the webhook's SSL client key file. | |
+| WebhookSSLCrt (on Windows) or webhook\_ssl\_crt (on Linux) | The complete path to the webhook's SSL client certificate file. | |
+| WebhookSSLCaCrt (on Windows) or webhook\_ssl\_ca\_crt (on Linux) | The complete path to the webhook's SSL ca certificate file. | |
+| WebhookSSLCrl (on Windows) or webhook\_ssl\_crl (on Linux) | The complete path of the CRL file to validate webhook server certificate. | |
+| AllowInsecureWebhooks (on Windows) or allow\_insecure\_webhooks (on Linux) | When set to true, allow webhooks to call with insecure flag. | false |
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/02_pem_agent_ha.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/02_pem_agent_ha.mdx
new file mode 100644
index 00000000000..97af6a4e2d6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/02_pem_agent_ha.mdx
@@ -0,0 +1,20 @@
+---
+title: "High Availability Integration"
+---
+
+
+
+
+In high availability (HA) configurations, the database servers that are being monitored may be moved ("failed over") to a different host in the event of any problems, such as a hardware failure. There are numerous ways to maintain a backup server using features of Postgres and external tools. Please consult the Postgres documentation for further details.
+
+In order to run in an HA environment, it is recommended that a PEM agent be installed on both the primary host machine, and any secondary machines that may be used as backups. The server is bound to the agent running on the primary host in the [normal fashion](../../02_toc_pem_agent/02_pem_agent_binding/#binding_pem_agent).
+
+When the clustering solution initiates a failover of Postgres from one server to another, the PEM agent on the server that is taking over the running of the database may be instructed to take over the monitoring of the database server as well. The server must first be configured to allow "takeovers" using the `Allow takeover?` [configuration option](../../01_toc_pem_getting_started/#pem_define_connection) on the `PEM Agent` tab of the server configuration dialogue.
+
+To instruct the agent to takeover the monitoring of a server, the failover process must simply create a file in a special "flag" directory which will instruct the agent to take responsibility for the specified server. A command such as the following could be added to a failover script on a Linux server for example:
+
+`touch /tmp/pem/agent-AGENTID/takeover-server-SERVERID` where `AGENTID` is the numeric ID of the agent that should takeover the monitoring of the server, and `SERVERID` is the numeric ID of the server that should be taken over. The IDs may be found by logging into the PEM client, and selecting the Agent or Server and viewing the ID values on the `Properties` pane of the main window.
+
+The agent will take over monitoring of the failed-over server within approximately 30 seconds in a standard configuration of PEM.
+
+The flag directory used by the agent is `$TMPDIR/pem/agent-AGENTID` by default (where $TMPDIR is as set for the user account under which the agent runs, usually `root` on Linux/Unix, or `Administrator` on Windows). The directory path can be overridden using the `AgentFlagDir` configuration option in the registry on Windows, or the `agent_flag_dir` option in the agent configuration file on other platforms.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/index.mdx
new file mode 100644
index 00000000000..3b52e5c225e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/02_pem_agent_binding/index.mdx
@@ -0,0 +1,47 @@
+---
+title: "Binding an Agent to a Server"
+---
+
+
+
+
+The PEM agent runs as a service (on Windows) or as a daemon (on Linux), and is responsible for implementing scheduled tasks on the PEM server on behalf of the server. The PEM server installer automatically installs and configures an agent that is responsible for monitoring the PEM server. The PEM agent installer will setup and configure the agent to start automatically at boot time, however the agent can also be manually [started](../02_toc_pem_agent/#pem_agent_start_pem_agent) if required.
+
+To create a binding for a registered server, right click on the name of the server in the tree control, and select `Properties` from the context menu. Open the `PEM Agent` tab:
+
+
+
+Use the fields on the `PEM Agent` tab to associate the server (defined on the Connection tab) with a PEM agent:
+
+Use fields on the `PEM Agent` tab to specify connection details for the PEM agent:
+
+- Specify `Yes` in the `Remote monitoring?` field 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).
+- Select an Enterprise Manager agent using the drop-down listbox to the right of the `Bound agent` label. 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.
+- Use the `SSL` field to specify an SSL operational mode.
+
+| Mode | Specify: |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| 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 information about using SSL encryption, see [Section 31.17 of the Postgres documentation](http://enterprisedb.com/docs/en/9.0/pg/libpq-ssl.html).
+
+- Use the `Database` field to specify the name of the Postgres Plus database to which the agent will initially connect.
+- Specify the name of the user that agent should use when connecting to the server in the `User name` field. Note that if the specified user is not a database superuser, then some of the features will not work as expected. If you are using Postgres version 10 or above, you can use the `pg_monitor` role to grant the required privileges to a non-superuser. For information about `pg_monitor` role, see [Default Roles](https://www.postgresql.org/docs/current/default-roles.html).
+- Specify the password that the agent should use when connecting to the server in the `Password` field, and verify it by typing it again in the `Confirm password` field. If you do not specify a password, you will need to configure the authentication for the agent manually; you can use a `.pgpass` file for example.
+- Specify `Yes` in the `Allow takeover?` field to specify that the server may be "taken over" by another agent. This feature allows an agent to take responsibility for the monitoring of the database server if, for example, the server has been moved to another host as part of a [high availability](../02_toc_pem_agent/02_pem_agent_binding/#pem_agent_ha) failover process.
+
+Contents:
+
+
+
+Note
+
+
+
+If you add or remove any of the parameter in the `agent.cfg` file then agent must be restarted to apply the changes.
+
+
+
+pem\_agent\_config\_params pem\_agent\_ha
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx
new file mode 100644
index 00000000000..cb8c783ad35
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx
@@ -0,0 +1,36 @@
+---
+title: "Controlling the PEM Agent"
+---
+
+
+
+
+On Linux platforms, the name of the service script that controls a PEM agent is `pemagent`. You can use the pemagent service script to control the PEM agent. Enter:
+
+> `/etc/init.d/pem_agent action`
+
+Where `action` specifies the action taken by the service. Specify:
+
+- start to start the service.
+- stop to stop the service.
+- restart to stop and then start the service.
+- status to check the status of the service.
+
+To determine if a service is running on RHEL or CentOS version 7.x, open a command line, and issue the command:
+
+> `systemctl pemagent action`
+
+Where `action` is the action taken by the service. You can specify:
+
+- start to start the service.
+- stop to stop the service.
+- restart to stop and then start the service.
+- status to inquire about the current status of the service.
+
+## Controlling the PEM Agent on Windows
+
+The Windows operating system includes a graphical service controller (the Windows `Services` applet) that displays the server status, and offers point-and-click service control. The Services applet can be accessed through the Windows Control Panel. When the utility opens, use the scroll bar to navigate through the listed services to highlight the `Postgres Enterprise Manager - pemAgent` service name.
+
+- Use the Stop the service option to stop a service.
+- Use the Pause the service option to instruct Postgres to reload a service's configuration parameters.
+- Use the Start the service option to start a service.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/04_pem_agent_ha.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/04_pem_agent_ha.mdx
new file mode 100644
index 00000000000..1f447792fdf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/04_pem_agent_ha.mdx
@@ -0,0 +1,20 @@
+---
+title: "High Availability Integration"
+---
+
+
+
+
+In high availability (HA) configurations, the database servers that are being monitored may be moved ("failed over") to a different host in the event of any problems, such as a hardware failure. There are numerous ways to maintain a backup server using features of Postgres and external tools. Please consult the Postgres documentation for further details.
+
+In order to run in an HA environment, it is recommended that a PEM agent be installed on both the primary host machine, and any secondary machines that may be used as backups. The server is bound to the agent running on the primary host in the [normal fashion](../02_toc_pem_agent/02_pem_agent_binding/#binding_pem_agent).
+
+When the clustering solution initiates a failover of Postgres from one server to another, the PEM agent on the server that is taking over the running of the database may be instructed to take over the monitoring of the database server as well. The server must first be configured to allow "takeovers" using the `Allow takeover?` [configuration option](../01_toc_pem_getting_started/#pem_define_connection) on the `PEM Agent` tab of the server configuration dialogue.
+
+To instruct the agent to takeover the monitoring of a server, the failover process must simply create a file in a special "flag" directory which will instruct the agent to take responsibility for the specified server. A command such as the following could be added to a failover script on a Linux server for example:
+
+`touch /tmp/pem/agent-AGENTID/takeover-server-SERVERID` where `AGENTID` is the numeric ID of the agent that should takeover the monitoring of the server, and `SERVERID` is the numeric ID of the server that should be taken over. The IDs may be found by logging into the PEM client, and selecting the Agent or Server and viewing the ID values on the `Properties` pane of the main window.
+
+The agent will take over monitoring of the failed-over server within approximately 30 seconds in a standard configuration of PEM.
+
+The flag directory used by the agent is `$TMPDIR/pem/agent-AGENTID` by default (where $TMPDIR is as set for the user account under which the agent runs, usually `root` on Linux/Unix, or `Administrator` on Windows). The directory path can be overridden using the `AgentFlagDir` configuration option in the registry on Windows, or the `agent_flag_dir` option in the agent configuration file on other platforms.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/05_pem_agent_privileges.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/05_pem_agent_privileges.mdx
new file mode 100644
index 00000000000..8ad2546be97
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/05_pem_agent_privileges.mdx
@@ -0,0 +1,16 @@
+---
+title: "PEM Agent Privileges"
+---
+
+
+
+
+By default, the PEM agent is installed with `root` privileges for the operating system host and superuser privileges for the database server. These privileges allow the PEM agent to invoke unrestricted probes on the monitored host and database server about system usage, retrieving and returning the information to the PEM server.
+
+Please note that PEM functionality diminishes as the privileges of the PEM agent decrease. For complete functionality, the PEM agent should run as `root` and on the same host as the database server.
+
+> - If the PEM agent is run under the database server's service account, PEM probes will not have complete access to the statistical information used to generate reports, and functionality will be limited to the capabilities of that account.
+> - If the PEM agent is run under another lesser-privileged account, functionality will be limited even further.
+> - If the PEM agent is installed on a different host and is monitoring the database server remotely, then the functionality will be limited.
+
+| Feature Name | Works with root User | Works with non-root User | Works with remote PEM Agent |
|---|---|---|---|
| Audit Manager | yes | The Audit Log Manager may be unable to apply requested modifications if the service cannot be restarted. The user running PEM Agent may be different from the user who owns the data directory of the database server, so user running PEM Agent may not be able to change the configuration and also may not be able to restart the services of the database server. | no |
| Capacity Manager | yes | yes | yes NOTE: There will be no co-relation between the database server and operating system metrices |
| Log Manager | yes | The Log Manager may be unable to apply requested modifications if the service cannot be restarted. The user running PEM Agent may be different from the user who owns the data directory of the database server, so user running the PEM Agent may not be able to change the configuration and also may not be able to restart the services of the database server. | no |
| Manage Alerts | yes | yes | yes NOTE: When run alert script on the database server is selected, it will run on the machine, where bound PEM Agent is running, and not on the actual database server machine. |
| Manage Charts | yes | yes | yes |
| Manage Dashboards | yes | Some dashboards may not be able to show complete data. For example, columns such as swap usage, CPU usage, IO read, and IO write will be displayed as 0 in the session activity dashboard. | Some dashboards may not be able to show complete data. For example, the operating system information of the database server will not be displayed as not available. |
| Manage Probes | yes | Some of the PEM probes will not return information, and some of functionalities may be affected. For details about probe functionality, see the PEM Agent Guide. | Some of the PEM probes will not return information, and some of the functionalities may be affected. |
| Postgres Expert | yes | The Postgres Expert will be able to access the configuration expert and schema expert, but not the security expert. | The Expert will provide partial information as operating system information is not available. |
| Postgres Log Analysis Expert | yes | The Postgres Log Analysis Expert may not be able to do the analysis as it is dependent on the logs imported by log manager, which will not work as required. | The Postgres Log Analysis Expert will not be able to do the analysis as it is dependent on the logs imported by log manager, which will not work as required. |
| Scheduled Tasks | yes | For Linux if user is the same as batch_script_user in agent.cfg then shell script will run. | Scheduled tasks will work only for database server; scripts will run on a remote Agent. |
| Tuning Wizard | yes | The Tuning Wizard will be unable to run if the service cannot be restarted. The user running PEM Agent may be different from the user who owns the data directory of the database server, so user running PEM Agent may not be able to change the configuration and also may not be able to restart the services of the database server. | no |
| System Reports | yes | yes | yes |
| Core Usage Reports | yes | yes | The Core Usage report will not show complete information. For example, the platform, number of cores, and total RAM will not be displayed. |
| Managing BART | yes | BART and the BART scanner may not be able to start/reload. | no NOTE: BART requires password less authentication between two machines, where database server and BART are installed. |
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/07_pem_agent_self_registration.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/07_pem_agent_self_registration.mdx
new file mode 100644
index 00000000000..b8e67da81f8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/02_toc_pem_agent/07_pem_agent_self_registration.mdx
@@ -0,0 +1,25 @@
+---
+title: "PEM Agent Self Registration"
+---
+
+
+
+
+Each PEM agent must be `registered` with the PEM server. The registration process provides the PEM server with the information it needs to communicate with the agent. The PEM agent graphical installer supports agent self-registration, but you can use the `pemworker` utility to register the agent if you skip PEM agent registration during a graphical installation or use an RPM package to install a PEM agent.
+
+The RPM installer places the PEM worker utility in the `/usr/edb/pem/agent/bin` directory. Use the following commands to register an agent:
+
+- **On Linux**: pemworker −−register-agent \[register-options\]
+- **On Windows**: pemworker.exe REGISTER \[register-options\]
+
+The following information is required when registering an agent with the PEM Server; you will be prompted for information if it is not provided on the command line:
+
+
+
+Note
+
+
+
+If you add or remove any of the parameter in the `agent.cfg` file then agent must be restarted to apply the changes.
+
+| Parameters | Command-line options | Optional | Description | Default Value |
|---|---|---|---|---|
| PEM Database Server Host | −−pem-server <hostname/address> | No | Address/Host name of the PEM database server | |
| PEM Admin User | −−pem-user <username> | No | PEM Admin User to connect to the PEM database server. | |
| PEM Database Server Port | −−pem-port <port number> | Yes | Port on which PEM database server is running. | 5432 |
| Agent Certificate Path | −−cert-path <certificate path> | Yes | Path, where certificates need to be created. | On Linux, "~/.pem" On Windows, “%APPDATA%/pem” |
| Agent Display Name | −−display-name <agent_name> | Yes | Display name of the PEM Agent. | System hostname |
| Agent Group | −−group <group_name> | Yes | The name of the group in which the agent will be displayed. | |
| Agent Team | −−team <team_name> | Yes | The name of the group role that may access the PEM Agent. | |
| Agent Owner | −−owner <owner_name> | Yes | The name of the owner of the PEM Agent. | |
| Force registration | −−force-registration | Yes | Forcefully registers the agent to the PEM server with the arguments provided. It can be used to override the existing agent configuration. | |
| Enable Heartbeat | −−enable-heartbeat-connection | Yes | Agent to use dedicated connection to update the heartbeat. | false |
| Agent User | −−pem-agent-user | Yes | Use this user to connect the PEM database server. Specify, it when you would like to use a connection pooler between PEM Agent and PEM database server. It will generate the SSL Ceriticates, which will used by the pemworker to connect to the PEM database server instead, for this user instead of the default agent user. NOTE: Specified user must be a member of 'pem_agent' role. |
| Parameters | Command-line options | Optional | Description | Default Value |
|---|---|---|---|---|
| PEM Admin User | −−pem-user <username> | No | The name of the PEM Admin User that will connect to the monitored server. | |
| Server Host | −−server-addr <host name/address> | No | Host name/address of the monitored server. | |
| Server Port | −−server-port <port> | No | Port on which database server is running. | |
| Server Database | −−server-database <name> | No | The database to which PEM will connect. | |
| Server User | −−server-user <name> | No | The database user role that will be used by the agent for monitoring purposes. | |
| Server Service Name | −−server-service-name <name> | Yes | Name of the system level service, which controls the operations like start, stop, restart, reload, etc. of the server. | |
| Remote Monitoring? | −−remote-monitoring <yes/no> | No | no if the monitored server resides on the same machine as the bound PEM agent, yes if the agent is on another host. | no |
| −−efm-cluster-name <name> | Yes | Name of EDB Failover Manager Cluster associated with this server. | |
| EDB Failover manager Installation Path | −−efm-install-path <path> | Yes | Installation path of EDB Failover Manager associated with this server. | |
| Server Display Name | −−display-name <server_name> | Yes | Display name of the registred server. | System hostname |
| Host Name | −−asb-host-name <name_of_host> | Yes | The name of the host to which the agent is connecting. | The value specified by the −−server-addr property. |
| Host Port | −−asb-host-port <port_number> | Yes | The port number that the agent will use when connecting to the database. | The value specified by the −−server-port property. |
| Host DB | −−asb-host-db <database_name> | Yes | The name of the database to which the agent will connect. | The value specified by the −−server-database property. |
| Host User Name | −−asb-host-user <database_user> | Yes | The database user name that the agent will supply when authenticating with the database. | The value specified by the −−server-user property. |
| SSL Mode | −−asb-ssl-mode <certificate path> | Yes | Type of SSL authentication that will be used for connections. Supported values include prefer, require, disable, verify-CA, verify-full. | prefer |
| Server Group | −−group <group_name> | Yes | Specify the name of the server group in which the server will be displayed. | |
| Server Team | −−team <team_name> | Yes | Specify the name of the group role that will be allowed to access the server. | |
| Owner | −−owner <owner_name> | Yes | Specify the name of the role that will own the monitored server. |
+
+pem\_agent\_properties pem\_agent\_binding pem\_agent\_start\_pem\_agent pem\_agent\_ha
+
+
+
+The PEM agent has a number of configuration parameters that control agent behaviors and enable PEM functionality. For a list of the parameters, see:
+
+
+
+pem\_agent\_privileges pem\_agent\_config\_params pem\_agent\_self\_registration pem\_agent\_server\_registration
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/01_pem_browser_window.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/01_pem_browser_window.mdx
new file mode 100644
index 00000000000..e1265e5743a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/01_pem_browser_window.mdx
@@ -0,0 +1,162 @@
+---
+title: "PEM Main Browser Window"
+---
+
+
+
+
+The PEM client features a menu bar and a window divided into two panes: the `Browser` tree control in the left pane, and a tabbed browser in the right pane.
+
+
+
+[Menus](../03_toc_pem_client/#pem_menu_bar) displayed across the top of the browser window provide quick, context-sensitive access to PEM features and functionality.
+
+## The PEM Client Object Browser
+
+The `Browser` tree control provides access to information and management options for the database objects that reside on each server. The tree control expands to display a hierarchical view of the servers and objects that are monitored by the PEM server. You can use context menu options (accessed by right-clicking on nodes of the tree control) to create new objects, and modify and delete existing objects if your role holds the required privileges.
+
+Expand nodes in the tree control to display a hierarchical view of the database objects that reside on a selected server:
+
+- Use the plus sign (+) to the left of a node to expand a segment of the tree control.
+- Click the minus sign (-) to the left of a node to close that node.
+
+Right-click on a node of the tree control to access a context-sensitive menu and perform common tasks. Context menu options may include one or more of the following selections:
+
+| Option | Action |
|---|---|
Add named restore point | Click to create and enter the name of a restore point. |
Backup... | Click to open the Backup... dialog to backup database objects. |
Backup Globals... | Click to open the Backup Globals... dialog to backup cluster objects. |
Backup Server... | Click to open the Backup Server... dialog to backup a server. |
Connect Server | Click to establish a connection with the selected server. |
Create | Click to access a context menu that provides context-sensitive selections. Your selection opens aCreate dialog for creating a new object. |
CREATE Script | Click to open the Query tool to edit or view the CREATE script. |
CREATE Script | Click to open the Query tool to edit or view the CREATE script. |
Dashboards | Click through for quick access to PEM dashboards. |
Delete/Drop | Click to delete the currently selected object from the server. |
Disconnect Database... | Click to terminate a database connection. |
Disconnect Server... | Click to refresh the currently selected object. |
Drop Cascade | Click to delete the currently selected object and all dependent objects from the server. |
Debugging | Click to access the Debugger tool. |
Grant Wizard | Click to access the Grant Wizard tool. |
Maintenance... | Click to open the Maintenance... dialog to VACUUM, ANALYZE, REINDEX, or CLUSTER. |
Management | Click to access management tasks that are relevant to the node. |
Properties... | Click to review or modify the currently selected object's properties. |
Refresh... | Click to refresh the currently selected object. |
Reload Configuration... | Click to update configuration files without restarting the server. |
Restore... | Click to access the Restore dialog to restore database files from a backup. |
View Data | Use the |
| Option | Action |
|---|---|
Import/Export... | Click open the Import/Export... <import_export_data> dialog to import data to or export data from the selected table. |
Reset Statistics | Click to reset statistics for the selected table. |
Scripts | Click to open the Query tool to edit or view the selected script from the flyout menu. |
Truncate | Click to remove all rows from a table. |
Truncate Cascade | Click to remove all rows from a table and its child tables. |
View First 100 Rows | Click to access the data grid that displays the first 100 rows of the selected table. |
View Last 100 Rows | Click to access the data grid that displays the last 100 rows of the selected table. |
View All Rows | Click to access the data grid that displays all rows of the selected table. |
View Filtered Rows... | Click to access the |
| Option | Action |
|---|---|
None | No locking. Every panel is resizable and dockable. |
Prevent docking | This will disable the docking/undocking of the panels |
Full | This will disable resizing, docking/undocking of the panels |
+
+- Use *Debugger tab title placeholder* field to customize the Debugger tab title.
+- When the *Dynamic tab size* If set to True, the tabs will take full size as per the title, it will also applicable for already opened tabs
+- When the *Open in new browser tab* filed is selected for Query tool, Schema Diff or Debugger, it will open in a new browser tab when invoked.
+- Use the *Query tool tab title placeholder* field to customize the query tool tab title.
+- Use *View/Edit tab title placeholder* field to customize the View/Edit Data tab title.
+
+**The Dashboards Node**
+
+Expand the `Dashboards` node to specify your dashboard display preferences.
+
+
+
+- When the `Show activity?` switch is set to `True`, activity tables will be displayed on dashboards.
+- When the `Show graph data points?` switch is set to `True`, data points will be visible on graph lines.
+- When the `Show graphs?` switch is set to `True`, graphs will be displayed on dashboards.
+- When the `Show mouse hover tooltip?` switch is set to `True`, a tooltip will appear on mouse hover on the graph lines giving the data point details.
+
+Use the fields on the `Graphs` panel to specify your display preferences for the graphs on the `Dashboard` tab:
+
+
+
+Use the fields on the `Graphs` panel to specify your display preferences for the graphs on the `Dashboard` tab:
+
+- Use the `Block I/O statistics refresh rate` field to specify the number of seconds between block I/O statistic samples displayed in graphs.
+- Use the `Session statistics refresh rate` field to specify the number of seconds between session statistic samples displayed in graphs.
+- Use the `Transaction throughput refresh rate` field to specify the number of seconds between transaction throughput samples displayed in graphs.
+- Use the `Tuples in refresh rate` field to specify the number of seconds between tuples-in samples displayed in graphs.
+- Use the `Tuples out refresh rate` field to specify the number of seconds between tuples-out samples displayed in graphs.
+
+**The Debugger Node**
+
+Expand the `Debugger` node to specify your debugger display preferences.
+
+Use the fields on the `Keyboard shortcuts` panel to configure shortcuts for the debugger window navigation:
+
+
+
+**The Miscellaneous Node**
+
+Expand the `Miscellaneous` node to specify miscellaneous display preferences.
+
+
+
+- Use the `User language` drop-down listbox to select the display language for the PEM web interface.
+
+
+
+- Use the `Themes` drop-down listbox to select the theme for PEM. You'll also get a preview just below the drop down. Note that, to apply the theme you need to refresh the PEM page.
+
+**The Paths Node**
+
+Expand the `Paths` node to specify the locations of supporting utility and help files.
+
+
+
+Use the fields on the `Binary paths` panel to specify the path to the directory that contains the utility programs (pg\_dump, pg\_restore, and pg\_dumpall) for monitored databases:
+
+- Use the `EDB Advanced Server Binary Path` field to specify the location of the EDB Postgres Advanced Server utility programs. If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by EnterpriseDB.
+- Use the `Greenplum Database Binary Path` field to specify the location of the Greenplum database utility programs. If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by Greenplum.
+- Use the `PostgreSQL Binary Path` field to specify the location of the PostgreSQL utility programs. If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by PostgreSQL.
+
+
+
+Use the fields on the `Help` panel to specify the location of help files.
+
+- Use the `EDB Advanced Server Help Path` field to specify the path to EDB Postgres Advanced Server documentation.
+- Use the `PostgreSQL Help Path` field to specify the path to PostgreSQL documentation.
+
+Please note: the default help paths include the `VERSION` placeholder; the $VERSION$ placeholder will be replaced by the current database version.
+
+**The Performance Diagnostic Node**
+
+Expand the `Performance Diagnostic` node to specify your preferences for the Performance Diagnostic tool.
+
+
+
+Use the fields on the `Performance Diagnostic` panel to control the Performance Diagnostic output.
+
+- Use the `Default graph selection` field to specify the default selection range in hours for performance diagnostic graphs.
+- When the `Open in new browser tab?` switch is set to True, the Performance Diagnostic tool will be opened in a new browser tab.
+
+**The Query Tool Node**
+
+Expand the `Query Tool` node to access panels that allow you to specify your preferences for the Query Editor tool.
+
+
+
+Use the fields on the `Auto Completion` panel to set the auto completion options.
+
+- When the `Keywords in uppercase` switch is set to `True`, keywords are displayed in upper case.
+
+
+
+Use the fields on the `CSV Output` panel to control the CSV output.
+
+- Use the `CSV field separator` drop-down listbox to specify the separator character that will be used in CSV/TXT output.
+- Use the `CSV quote character` drop-down listbox to specify the quote character that will be used in CSV/TXT output.
+- Use the `CSV quoting` drop-down listbox to select the fields that will be quoted in the CSV/TXT output; select `Strings`, *All*, or `None`.
+- Use the `Replace null values with` option to replace null values with specified string in the output file. Default is set to 'NULL'.
+
+
+
+Use the fields on the `Display` panel to specify your preferences for the Query Tool display.
+
+- When the `Connection status` switch is set to `True`, each new instance of the Query Tool will display connection and transaction status.
+- Use the `Connection status refresh rate` field to specify the number of seconds between connection/transaction status updates.
+- Use the `Query info notifier timeout` field to control the behaviour of the notifier that is displayed when query execution completes. A value of `-1` will disable the notifier, and a value of 0 will display it until clicked. If a positive value above zero is specified, the notifier will be displayed for the specified number of seconds. The default is `5`.
+
+
+
+Use the fields on the `Editor` panel to change settings of the query editor.
+
+- When the `Brace matching?` switch is set to `True`, the editor will highlight pairs of matched braces.
+- When the `Code folding?` switch is set to `False`, the editor will disable code folding. Disabling will improve editor performance with large files.
+- Use the `Font size` field to specify the font size that will be used in text boxes and editors.
+- When the `Insert bracket pairs?` switch is set to `True`, the editor will automatically insert paired brackets.
+- When the `Line wrapping` switch is set to `True`, the editor will implement line-wrapping behavior.
+- When the `Plain text mode?` switch is set to `True`, the editor mode will be changed to text/plain. Keyword highlighting and code folding will be disabled. This will improve editor performance with large files.
+
+
+
+Use the fields on the `Explain` panel to specify the level of detail included in a graphical EXPLAIN.
+
+- When the `Show Buffers?` switch is set to `True`, graphical explain details will include information about buffer usage.
+- When the `Show Costs?` switch is set to `True`, graphical explain details will include information about the estimated startup and total cost of each plan, as well as the estimated number of rows and the estimated width of each row.
+- When the `Show Timing?` switch is set to `True`, graphical explain details will include the startup time and time spent in each node in the output.
+- When the `Verbose output?` switch is set to `True`, graphical explain details will include extended information about the query execution plan.
+
+Use the fields on the `Keyboard shortcuts` panel to configure shortcuts for the Query Tool.
+
+
+
+Use the fields on the `Options` panel to manage Query Tool preferences.
+
+
+
+- When the `Auto-Commit?` switch is set to `True`, each successful query is committed after execution.
+- When the `Auto-Rollback?` switch is set to `True`, failed queries are rolled back.
+- When the `Prompt to save unsaved data changes?` switch is set to `True`, the editor will prompt the user to saved unsaved data when exiting the data editor.
+- When the `Prompt to save unsaved query changes?` switch is set to `True`, the editor will prompt the user to saved unsaved query modifications when exiting the query tool.
+- When the `Prompt to commit/rollback active transactions?` switch is set to `True`, the editor will prompt the user to commit or rollback changes when exiting the Query Tool while the current transaction is not committed.
+- When the `Sort View Data results by primary key columns?` If set to `True`, data returned when using the View/Edit Data - All Rows option will be sorted by the Primary Key columns by default. When using the First/Last 100 Rows options, data is always sorted.
+
+
+
+Use the fields on the *SQL formatting* panel to specify your preferences for reformatting of SQL.
+
+- Use the *Command-first notation* option to specify whether to place commas before or after column names.
+- Use the *Identifier case* option to specify whether to change identifiers (object names) into upper, lower, or capitalized case.
+- Use the *Keyword case* option to specify whether to change keywords into upper, lower, or capitalized case.
+- Use the *Re-indent aligned?* option to specify that indentations of statements should be changed, aligned by keywords.
+- Use the *Re-indent?* option to specify that indentations of statements should be changed.
+- Use the *Spaces around operators?* option to specify whether or not to include spaces on either side of operators.
+- Use the *Strip comments?* option to specify whether or not comments should be removed.
+- Use the *Tab size* option to specify the number of spaces per tab or indent.
+- Use the *Use spaces?* option to select whether to use spaces or tabs when indenting.
+- Use the *Wrap after N characters* option to specify the column limit for wrapping column separated lists (e.g. of column names in a table). If set to 0 (zero), each item will be on it's own line.
+
+
+
+Use the fields on the `Results grid` panel to specify your formatting preferences for copied data.
+
+- Use the `Result copy field separator` drop-down listbox to select the field separator for copied data.
+- Use the `Result copy quote character` drop-down listbox to select the quote character for copied data.
+- Use the `Result copy quoting` drop-down listbox to select which type of fields require quoting; select `All`, *None*, or `Strings`.
+
+**The SQL Profiler Node**
+
+Use fields on the `Display` panel to specify SQL Profiler preferences.
+
+
+
+Set `Open in New Browser Tab?` to `True` to open SQL Profiler in a new browser tab when SQL Profiler is invoked.
+
+Use the fields on the Keyboard shortcuts panel to configure shortcuts for toolbar buttons on SQL profiler trace window.
+
+
+
+**The Scheduled Tasks Node**
+
+Use fields on the `Options` panel to specify Scheduled Tasks preferences.
+
+
+
+Use the `Auto refresh interval` field to specify the number of seconds between automatic refreshes; a value of 0 disables auto refresh.
+
+**The Schema Diff Node**
+
+Expand the `Schema Diff` node to specify your display preferences.
+
+
+
+Use the *Ignore owner* switch to ignores the owner while comparing the objects.
+
+Use the `Ignore whitespaces` switch to ignores the whitespaces while comparing the string objects. Whitespace includes space, tabs, and CRLF.
+
+**The Storage Node**
+
+Expand the `Storage` node to specify your storage preferences.
+
+
+
+Use the fields on the `Options` panel to specify storage preferences.
+
+- Use the `File dialog view` drop-down listbox to select the style of icons and display format that will be displayed when you open the file manager; select `List` to display a list view, or `Grid` to display folder icons.
+- Use the `Last directory visited` field to specify the name of the folder in which the file manager will open.
+- Use the `Maximum file upload size(MB)` field on the `Options` panel of the **Storage** node to specify the maximum file size for an upload.
+- When the `Show hidden files and folders?` switch is set to `True`, the file manager will display hidden files and folders.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/05_keyboard_shortcuts.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/05_keyboard_shortcuts.mdx
new file mode 100644
index 00000000000..e0f6a74efe4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/05_keyboard_shortcuts.mdx
@@ -0,0 +1,137 @@
+---
+title: "Keyboard Shortcuts"
+---
+
+
+
+Keyboard shortcuts are provided in pgAdmin to allow easy access to specific functions. Alternate shortcuts can be configured through File > Preferences if desired.˝
+
+## Main Browser Window
+
+When using main browser window, the following keyboard shortcuts are available:
+
+| Shortcut for all platforms | Function |
+|----------------------------|---------------------------------------------|
+| Alt+Shift+F | Open the File menu |
+| Alt+Shift+O | Open the Object menu |
+| Alt+Shift+L | Open the Tools menu |
+| Alt+Shift+H | Open the Help menu |
+| Alt+Shift+B | Focus the browser tree |
+| Alt+Shift+\[ | Move tabbed panel backward |
+| Alt+Shift+\] | Move tabbed panel forward |
+| Alt+Shift+Q | Open the Query Tool in the current database |
+| Alt+Shift+V | View Data in the selected table/view |
+| Alt+Shift+C | Open the context menu |
+| Alt+Shift+N | Create an object |
+| Alt+Shift+E | Edit object properties |
+| Alt+Shift+D | Delete the object |
+| Alt+Shift+G | Direct debugging |
+
+## Dialog Tabs
+
+Use the shortcuts below to navigate the tabsets on dialogs:
+
+| Shortcut for all platforms | Function |
+|----------------------------|---------------------|
+| Control+Shift+\[ | Dialog tab backward |
+| Control+Shift+\] | Dialog tab forward |
+
+## Property Grid Controls
+
+Use the shortcuts below when working with property grid controls:
+
+| Shortcut for all platforms | Function |
+|----------------------------|------------------------------------------|
+| Control+Shift+A | Add row in Grid |
+| Tab | Move focus to the next control |
+| Shift+Tab | Move focus to the previous control |
+| Return | Pick the selected an item in a combo box |
+| Control+Shift+A | Add row in Grid |
+
+## SQL Editors
+
+When using the syntax-highlighting SQL editors, the following shortcuts are available:
+
+| Shortcut (Windows/Linux) | Shortcut (Mac) | Function |
+|--------------------------|----------------------|-------------------------------------|
+| Alt + Left | Option + Left | Move to the beginning of the line |
+| Alt + Right | Option + Right | Move to the end of the line |
+| Ctrl + Alt + Left | Cmd + Option + Left | Move left one word |
+| Ctrl + Alt + Right | Cmd + Option + Right | Move right one word |
+| Ctrl + / | Cmd + / | Comment selected code (Inline) |
+| Ctrl + . | Cmd + . | Uncomment selected code (Inline) |
+| Ctrl + Shift + / | Cmd + Shift + / | Comment/Uncomment code (Block) |
+| Ctrl + a | Cmd + a | Select all |
+| Ctrl + c | Cmd + c | Copy selected text to the clipboard |
+| Ctrl + r | Cmd + r | Redo last edit un-done |
+| Ctrl + v | Cmd + v | Paste text from the clipboard |
+| Ctrl + z | Cmd + z | Undo last edit |
+| Tab | Tab | Indent selected text |
+| Shift + Tab | Shift + Tab | Un-indent selected text |
+| Alt + g | Option + g | Jump (to line:column) |
+| Ctrl + Space | Ctrl + Space | Auto-complete |
+| Ctrl + f | Cmd + f | Find |
+| Ctrl + g | Cmd + g | Find next |
+| Ctrl + Shift + g | Cmd + Shift + g | Find previous |
+| Ctrl + Shift + f | Cmd + Shift + f | Replace |
+
+## Query Tool
+
+When using the Query Tool, the following shortcuts are available:
+
+| Shortcut (Windows/Linux) | Shortcut (Mac) | Function |
+|--------------------------|-----------------------|---------------------------|
+| F5 | F5 | Execute query |
+| F6 | F6 | Save data changes |
+| F7 | F7 | EXPLAIN query |
+| Shift + F7 | Shift + F7 | EXPLAIN ANALYZE query |
+| F8 | F8 | Execute query to CSV file |
+| <accesskey> + o | <accesskey> + o | Open file |
+| <accesskey> + s | <accesskey> + s | Save file |
+| <accesskey> + n | <accesskey> + n | Find option drop down |
+| <accesskey> + c | <accesskey> + c | Copy row(s) |
+| <accesskey> + p | <accesskey> + p | Paste row(s) |
+| <accesskey> + d | <accesskey> + d | Delete row(s) |
+| <accesskey> + f | <accesskey> + f | Filter dialog |
+| <accesskey> + i | <accesskey> + i | Filter options drop down |
+| <accesskey> + r | <accesskey> + r | Row limit |
+| <accesskey> + q | <accesskey> + q | Cancel query |
+| <accesskey> + l | <accesskey> + l | Clear option drop down |
+| <accesskey> + x | <accesskey> + x | Execute option drop down |
+| <accesskey> + t | <accesskey> + t | Display connection status |
+| <accesskey> + y | <accesskey> + y | Copy SQL on history panel |
+
+## Debugger
+
+When using the Debugger, the following shortcuts are available:
+
+| Shortcut (Windows/Linux) | Shortcut (Mac) | Function |
+|--------------------------|-----------------------|------------------------------|
+| <accesskey> + i | <accesskey> + i | Step in |
+| <accesskey> + o | <accesskey> + o | Step over |
+| <accesskey> + c | <accesskey> + c | Continue/Restart |
+| <accesskey> + t | <accesskey> + t | Toggle breakpoint |
+| <accesskey> + x | <accesskey> + x | Clear all breakpoints |
+| <accesskey> + s | <accesskey> + s | Stop |
+| Alt + Shift + q | Option + Shift + q | Enter or Edit values in Grid |
+
+## Inner Tab and Panel Navigation
+
+When using the Query Tool and Debugger, the following shortcuts are available for inner panel navigation:
+
+| Shortcut (Windows/Linux) | Shortcut (Mac) | Function |
+|--------------------------|-------------------|-------------------------------------|
+| Alt + Shift + \] | Alt + Shift + \] | Move to next tab within a panel |
+| Alt + Shift + \[ | Alt + Shift + \[ | Move to previous tab within a panel |
+| Alt + Shift + Tab | Alt + Shift + Tab | Move between inner panels |
+
+## Access Key
+
+<accesskey> is browser and platform dependant. The following table lists the default access keys for supported browsers.
+
+| Browser | Windows | Linux | Mac |
+|-------------------|-------------|-------------|---------------|
+| Internet Explorer | Alt | Alt | |
+| Chrome | Alt | Alt | Ctrl + Option |
+| Firefox | Alt + Shift | Alt + Shift | Ctrl + Option |
+| Safari | Alt | | Ctrl + Option |
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/06_search_objects.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/06_search_objects.mdx
new file mode 100644
index 00000000000..2a6c40ad11d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/06_search_objects.mdx
@@ -0,0 +1,18 @@
+---
+title: "Search objects"
+---
+
+
+
+
+
+
+With this dialog, you can search for almost any kind of objects in a database.
+
+You can access it by right clicking a database or any of its child nodes and select "Search objects". You can also access it by hitting the shortcut (default ALT+SHIFT+S).
+
+The minimum pattern length are 3 characters. The search performed is non-casesensitive and will find all objets whose name contains the pattern. You can only search for object names currently. Examples are: abc, %ab%, ab%c, %%%, etc.
+
+The result is presented in the grid with object name, object type and the object tree path in the browser tree. You can double click on a result row to select the object in the browser tree. If the object is greyed out, this means that you have not enabled those object types in the [preferences](../03_toc_pem_client/#preferences), so you can't double click on it. You can click on the ellipsis appended to the function and procedure names to see there arguments.
+
+You can filter based on a particular object type by selecting one from the object type dropdown. If the search button is hit when one of the object type is selected then only those types will be fetch from the database. An object type will not be visible in the dropdown if the database server does not support it or if it is not enabled from the [preferences](../03_toc_pem_client/#preferences).
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/index.mdx
new file mode 100644
index 00000000000..7f10e725d10
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/03_toc_pem_client/index.mdx
@@ -0,0 +1,38 @@
+---
+title: "The PEM Client"
+---
+
+
+
+
+The Postgres Enterprise Manager client provides a powerful and intuitive user interface that you can use to manage Advanced Server and PostgreSQL databases. The client interface is easily customized, and will preserve your preferences between sessions. Client features include:
+
+> - auto-detection and support for objects discovered at run-time
+> - a live SQL query tool with direct data editing
+> - support for administrative queries
+> - a syntax-highlighting SQL editor
+> - powerful graphical management dialogs and tools for common tasks
+> - a responsive, context-sensitive behavior
+> - supportive error messages
+> - helpful hints
+> - online help and information for dialogs and tools.
+
+The PEM client features a highly-customizable display that features drag-and-drop panels that you can arrange to make the best use of your desktop environment. The application is installed during the PEM server installation; use your browser of choice to connect to the client.
+
+The client tree control (the *Browser*) provides an elegant overview of the managed servers, and the objects that reside on each server. Right-click on a node within the tree control to access context-sensitive menus that provide quick access to management tasks for the selected object. The tabbed browser window provide quick access to statistical information about each object in the tree control, tools and utilities, and extended PEM features. The client opens an additional feature tab each time you access the extended functionality offered by PEM; you can open, close, and re-arrange tabs as needed.
+
+You can search for objects in the database using the [Search objects](03_toc_pem_client/#search_objects)
+
+Contents:
+
+
+
+pem\_browser\_window pem\_toolbar pem\_menu\_bar preferences keyboard\_shortcuts search\_objects
+
+
+
+Please note that database changes made from other users or clients will not cause a browser refresh. It is generally advisable to manually refresh an object before modifying it. You may find some options are disabled when you are reviewing object properties or making menu selections. If this is the case:
+
+- The database server to which you are currently connected may not support the selected feature.
+- The selected property cannot be modified by design.
+- The role that you have used to connect to the server may have insufficient privileges to change the selected object.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/01_alerts_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/01_alerts_dashboard.mdx
new file mode 100644
index 00000000000..0b470767bc4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/01_alerts_dashboard.mdx
@@ -0,0 +1,73 @@
+---
+title: "The Alerts Dashboard"
+---
+
+
+
+
+The Alerts Dashboard displays the currently triggered alerts; if opened from the Global Overview, the dashboard displays the current alerts for all monitored nodes on the system. If the Alerts Dashboard is opened from a node within a monitored hierarchy, the report will reflect alerts related to that node, and all monitored objects that reside below that object in the tree control.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the `Alerts` dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The `Alerts Dashboard` header includes the date and time that the page was last updated and a current count of triggered alerts.
+
+The `Alerts Overview` provides an overview of triggered alerts. The right-most bar indicates the total number of configured alerts that are **not** currently in an alert state; the three left-most bars indicate the number of Low, Medium and High alerts for the selected object. The vertical key on the left side of the graph provides an alert count.
+
+The `Alert Details` table lists the currently triggered alerts for the selected object; if opened from the global overview, the Alert Details table lists all of the currently triggered alerts for all monitored objects. Click a column heading to sort the table by the contents of a selected column; click a second time to reverse the sort order. The table contains detailed information about each alert:
+
+- An alert level icon displays in red for a `High` severity alert, in orange for a `Medium` severity alert, and in yellow for a `Low` severity alert.
+- Use the arrow to the right of the alert level icon to access a dialog with detailed information about the alert. Within the dialog, the `Details` tab displays detailed information about the condition that triggered the alert; the `Parameters` tab displays the values of parameters used in the alert definition. Not all alerts return data that can be viewed on the `Details` dialog; for information about which templates display detailed metrics, please see the [alert templates list](../../04_toc_pem_features/09_pem_alerting/#pem_alert_templates)
+
+
+
+- The `Ack'ed` column provides a checkbox to allow you to acknowledge an alert to prevent additional notifications being sent. This flag is cleared automatically if the alert condition clears and is then detected again.
+- The `Alert Type` column indicates the severity of the alert.
+- The `Name` column displays the names of the currently triggered alerts. Click the name of an alert to open the `Alerting` configuration dialogue that defines the alert.
+- The `Value` column displays the value of the metric that triggered the alert.
+- If applicable, the `Agent` column indicates the name of the agent on which the alert is defined.
+- If applicable, the `Server` column indicates the name of the server triggering the error message.
+- If applicable, the `Database` column indicates the name of the database on which the alert is defined.
+- If applicable, the `Schema` column indicates the name of the schema on which the alert is defined.
+- If applicable, the `Package` column indicates the name of the package on which the alert is defined.
+- If applicable, the `Object` column indicates the name of the monitored object on which the alert is defined.
+- If the alert definition includes specified parameters, the parameter values are displayed in the `Additional Params` column.
+- If the alert definition includes additional specified parameters, the additional parameter values are displayed in the `Additional Params Value` column.
+- The `Alerting Since` column displays the date and time that the alert triggered.
+
+The `Alert Errors` table displays configuration-related errors (eg.accidentally disabling a required probe, or improperly configuring an alert parameter):
+
+
+
+- An alert indicator in the left-most column indicates that the alert was triggered by an Error.
+- The `Alert Type` column indicates the severity of the alert.
+- The `Name` column displays the name of the alert. Click an alert name to open the configuration dialogue for the alert.
+- The `Value` column displays the value of the metric that triggered the alert, if applicable.
+- If applicable, the `Agent` column displays the name of the agent triggering the alert.
+- If applicable, the `Server` column displays the name of the server triggering the alert.
+- If applicable, the `Database` column indicates the name of the database on which the alert is defined.
+- If applicable, the `Schema` column indicates the name of the schema on which the alert is defined.
+- If applicable, the `Package` column indicates the name of the package on which the alert is defined.
+- If applicable, the `Object` column indicates the name of the monitored object on which the alert is defined.
+- The `Error Message` column describes the condition that triggered the alert.
+- The `Error Timestamp` column displays the date and time that the alert was triggered.
+
+## Customizing the Alerts Dashboard
+
+You can customize tables and charts that appear on the Alerts dashboard. To open the `Personalize chart configuration` dialog, click the wrench icon in the upper-right corner.
+
+
+
+The fields displayed on the dialog will vary based on the table or chart from which the dialog is opened.
+
+
+
+Use fields on the `Personalize chart configuration` dialog to provide your display preferences:
+
+- Use the `Auto Refresh` field to specify the number of seconds between updates of the data displayed in the table or chart.
+- If applicable, use the `Download as` field to indicate if you would like a chart to be downloaded as a JPEG image or a PNG image.
+- If applicable, use the `Colours` selectors to specify the display colors that will be used on a chart.
+- If applicable, set the `Show Acknowledged Alerts` switch to `Yes` indicate that you would like the table to display alerts that you have acknowledged with a checkbox in the `Ack'ed` column. Set the field to `No` to indicate that the table should hide any acknowledged alerts. The switch acts as a toggle; acknowledged alerts are not purged from the table content until the time specified in the alert definition passes.
+
+To save your customizations, click the save icon (a check mark) in the upper-right corner; to delete any previous changes and revert to the default values, click the delete icon. Save and Delete drop-down menus allow you to specify if your preferences should be applied to `All Dashboards`, or to a selected server or database. Use the close icon to close the `Personalize chart configuration` dialog without preserving your changes.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/02_audit_log_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/02_audit_log_dashboard.mdx
new file mode 100644
index 00000000000..d64ce92562e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/02_audit_log_dashboard.mdx
@@ -0,0 +1,38 @@
+---
+title: "The Audit Log Analysis Dashboard"
+---
+
+
+
+
+The Audit Log Dashboard allows you to browse the audit logs that have been collected from Advanced Server instances which have enabled audit logging and collection with the [Audit Manager](../../04_toc_pem_features/#audit_manager). If the Audit Log Dashboard is opened from the Global level, it will display logs from all servers. If opened from the Agent level, it will show logs from all servers monitored by that Agent. If opened from the Server level, it will show logs from that server only.
+
+
+
+The `Audit Log Dashboard` header includes the date and time that the page was last updated, and a current count of triggered alerts.
+
+Audit Log table entries are loaded on demand in batches; to load additional entries, scroll to the end of the log and the additional rows will be automatically loaded from the database and added to the table. Log entries are show in chronological order, most recent first.
+
+- The `Id` column identifies the PEM agent that monitors the server that initiated the recorded transaction.
+- The `Server` column identifies the server that initiated the recorded transaction.
+- The `Timestamp` column shows the date and time that the log entry was made.
+- The `User Name` column shows the user which executed the statment in the audit log entry.
+- the `Database Name` column shows the database on which the statment in the audit log entry was executed.
+- The `Process ID` column shows the ID of the process which executed the statement in the audit log entry.
+- The `Session ID` column shows the ID of the session in which the statement in the audit log entry was executed.
+- The `Transaction ID` column shows the ID of the transaction in which the statement in the audit log entry was executed.
+- The `Connection From` column shows the client's address from where the session was connected.
+- The `Command` column shows the type of command executed.
+- The `Message` column shows the message associated with the audit log entry.
+
+Click `Show Filters` to display a panel that you can use to filter the audit log entries that are shown in the table below; click on `Hide Filters` to close the panel.
+
+
+
+Use the fields within the filter definition box to describe a selection criteria that PEM will use to select a subset of a report for display:
+
+- Use the date and time selectors in the `From` field to specify a starting date and time for the displayed log entries.
+- Use the date and time selectors in the `To` field to specify an ending date and time for the displayed log entries.
+- Enter a username in the `Username` field to show log entries for the specified user only.
+- Enter a database name in the `Database` field to show log entries for the specified database only.
+- Enter a command type (for example; 'SELECT', 'authentication' or 'idle') in the `Command Type` field to show log entries of that type only.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/03_database_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/03_database_analysis_dashboard.mdx
new file mode 100644
index 00000000000..16d9ebc7f84
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/03_database_analysis_dashboard.mdx
@@ -0,0 +1,51 @@
+---
+title: "The Database Analysis Dashboard"
+---
+
+
+
+
+The Database Analysis dashboard provides a high-level overview of database activity for the selected database, including a comparative storage analysis of the 5 largest tables/indexes, user activity analysis, weekly I/O analysis, and an activity analysis of the tables that reside in the selected database.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The Database Analysis dashboard header displays the date and time that the server started, the date and time that the Database Analysis dashboard was last updated, and the number of alerts currently triggered for the specified database (and monitored objects that reside within that database).
+
+The `Storage` bar graph plots the relative size of the 5 largest tables and indexes that reside within the selected database. The vertical key on the left side of the graph indicates each table or index in megabytes; the key on the right side of the chart identifies the tables and indexes by name.
+
+The `Users` section of the Database Analysis dashboard displays information about user connections:
+
+- The `User Activity` graph plots the active and idle connections over the previous week. The vertical key on the left side of the chart indicates the connection count.
+- The `Connection Overview` chart provides a comparative display of the active and idle connections currently established with the server (when the most recent probe executed).
+
+The graphs in the `I/O` section present an analysis of I/O activity over the previous week.
+
+
+
+- The `Database I/O` graph plots the number of blocks found in cached memory and the number of blocks read from disk over the previous week. The vertical key on the left side of the graph indicates number of blocks hit.
+- The `Row Activity` graph displays the row activity for tables residing within the database over the previous week.
+
+> The vertical key on the left side of the graph indicates the number of rows.
+
+- The `Commits/Rollbacks` graph displays the number of transactions committed and rolled back within the selected database over the previous week.
+
+> The vertical key on the left side of the graph indicates the transaction count.
+
+
+
+The `Hot Tables` table provides a detailed analysis of the activity for each table that resides within the selected database. Click a column heading to sort the table by the values within the column; click again to reverse the sort order.
+
+- The `Schema` column identifies the schema in which the table resides.
+- The `Table Name` column identifies the name of the table.
+- The `Scans` column displays the number of scans performed on the table.
+- The `Rows Read` column displays the number of rows read from the specified table.
+- The `Index Scans` column displays the number of index scans performed on the specified table.
+- The `Index Rows Read` column displays the number of rows read during index scans on the specified table.
+- The `Rows Inserted` column displays the number of rows inserted into the specified table.
+- The `Rows Updated` column displays the number of rows updated in the specified table.
+- The `Rows Deleted` column displays the number of rows deleted from the specified table.
+- The `Hot Rows Updated` column displays the number of hot row updates into the table; when a hot row update occurs, the new row occupies the same page as the previous row.
+- The `Total Rows` column displays the number of total rows in the table.
+- The `Dead Rows` column displays the number of rows that have been deleted, but have not been reclaimed via a VACUUM command or the AUTOVACUUM process.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/04_global_overview_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/04_global_overview_dashboard.mdx
new file mode 100644
index 00000000000..92fe60c83ac
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/04_global_overview_dashboard.mdx
@@ -0,0 +1,55 @@
+---
+title: "The Global Overview Dashboard"
+---
+
+
+
+
+Upon connecting to Postgres Enterprise Manager, the web interface displays the `Global Overview` dashboard. The Global Overview dashboard displays the status of each PEM server and agent, and calls your attention to any triggered alerts on monitored objects.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The `Global Overview` header displays the date and time that the overview was last updated and the current number of triggered alerts.
+
+The `Enterprise Dashboard` bar graph provides an at-a-glance overview of the status of your PEM agents and servers.
+
+The `Agent Status` table provides detailed information about the status of each individual PEM agent:
+
+- Check the box in the `Blackout` column to disable alert processing for the agent and all servers monitored by the agent. This is useful when undertaking maintenance on the agent or the host on which the agent runs.
+- The `Status` column reports the current state of the agent; `UP`, `DOWN` or `UNKNOWN`. A healthy agent displays a green 'check' circle icon; an agent that is down displays a red 'info' circle icon; an agent registered with PEM, but - never sent an heartbeat, displays a gray 'question' circle icon. If user changes the colour for UP, DOWN or UNKNOWN status of agents in \**Enterprise Dashboard*\* bar chart, then that color will be reflected for the respective status icon.
+- The `Name` column displays the name of the agent. Click the name to navigate to the `Operating System Analysis` dashboard for the selected host.
+- The `Alerts` column displays the number of current alerts triggered on the server.
+- The `Version` column displays the agent's version.
+- The `Processes` column lists the number of processes running on the agent's host.
+- The `Threads` column lists the number of threads running on the agent's host.
+- The `CPU Utilisation (%)` column shows the average utilisation of all CPU cores on the host.
+- The `Memory Utilisation (%)` column shows the percentage of available RAM memory used on the host.
+- The `Swap Utilisation (%)` column shows the percentage of available swap memory used on the host.
+- The `Disk Utilisation` column shows the total percentage of disk space used, for all disks on the host.
+
+The `Postgres Server Status` table provides detailed information about the status of each individual server:
+
+- Check the box in the `Blackout` column provides a checkbox to disable alert processing for the server. This is useful when performing maintenance on the server.
+- The `Status` column reports the current state of the server; UP, DOWN, UNKNOWN or UNMANAGED.
+- A healthy server displays a green 'check' circle icon; a disabled server displays a red 'info' circle icon; an unknown server displays a grey 'question' circle icon; an unmanged server displays a light gray 'user' circle icon. If user changes the colour for UP, DOWN, UNKNOWN or UNMANAGED servers in **Enterprise Dashboard** bar chart, then that color will be reflected for the respective status icon.
+- The `Name` column displays the name of the agent. Click the name to navigate to the `Operating System Analysis` dashboard for the host.
+- The `Connections` column reports the current number of connections to the server.
+- The `Alerts` column displays the number of current alerts triggered on the server.
+- The `Version` column lists the PostgreSQL version and build signature.
+- The `Remotely Monitored` column displays a `Yes` if the PEM agent that is bound to the monitored server does not reside on the same host as the server, and a `No` if the agent resides on the same host as the server.
+
+Triggered alerts displayed in the `Alert Status` table include both PEM-defined alerts and user-defined alerts for all PEM-monitored hosts, servers, agents and database objects. The `Alert Status` table will also display an alert if an [agent or server is down](../../02_toc_pem_agent/#pem_agent_start_pem_agent).
+
+- The `Alarm Type` column reports the alert severity. An icon displays in red for a `High` severity alert, in yellow for a `Medium` severity alert, and in grey for a `Low` severity alert.
+- The `Object Description` column displays a description of the object that triggered the alert.
+- The `Alert Name` column displays the name of the triggered alert. When viewing the dashboard in the PEM client, you can click the Alert Name to open the configuration dialogue for the alert.
+- The `Value` column displays the current value of the object that triggered the alert.
+- The `Database` column displays the name of the database with which the alert is associated (if applicable).
+- The `Schema` column displays the name of the schema with which the alert is associated (if applicable).
+- The `Package` column displays the name of the package with which the alert is associated (if applicable).
+- The `Object` column displays the name of the object with which the alert is associated (if applicable).
+- The `Additional Params` column displays any additional parameters specified for the alert.
+- The `Additional Param Values` column displays any additional parameter values specified for the alert.
+- The `Alerting Since` column displays the date and time at which the alert triggered.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/05_io_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/05_io_analysis_dashboard.mdx
new file mode 100644
index 00000000000..87e3ba53b73
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/05_io_analysis_dashboard.mdx
@@ -0,0 +1,65 @@
+---
+title: "The I/O Analysis Dashboard"
+---
+
+
+
+
+The I/O Analysis dashboard displays usage statistics for a specific database.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The I/O Analysis dashboard header displays the date and time that the server started, the date and time that the I/O Analysis dashboard was last updated, and the number of alerts currently triggered for the specified database (and any monitored object that resides within that database).
+
+The graphs in the `I/O Overview` provide information about the week's activity for the specified database:
+
+- The `Database I/O` graph displays the number of blocks read to and written from disk and memory buffers for the specified database over the course of the previous week.
+
+> The vertical key on the left side of the graph charts the block count.
+
+- The `Row Activity` graph displays tuple activity for tables residing within the database over the last week.
+
+> The vertical key on the left side of the graph charts the row count.
+
+- The `Checkpoints` graph displays the number of timed and untimed (requested) checkpoints written for the database over the last week.
+
+> The vertical key on the left side of the graph displays the checkpoint count.
+>
+> > A checkpoint is a point in the transaction logging sequence at which all data files have been updated to reflect the information in the log, and data files are flushed to disk. Checkpoints can be automatically generated, or forced by use of the CHECKPOINT command. A timed checkpoint occurs when the checkpoints\_timeout parameter time limit is met. An untimed (requested) checkpoint occurs when the checkpoint\_segments parameter is met, or when a superuser issues the CHECKPOINT command. Frequent checkpointing can impose extra load on the server, but can reduce recovery time in the event of a crash or hardware failure.
+
+The `Hot Tables/Indexes` section of the I/O Analysis dashboard provides an overview of the 5 most scanned tables and indexes that reside within the database.
+
+- The `Hot Tables` bar graph represents the comparative usage of the 5 most scanned tables that reside in the database; a vertical key displays the number of table scans.
+- The `Hot Indexes` bar graph represents the comparative usage of the 5 most scanned indexes that reside in the database; a vertical key displays the number of index scans.
+
+The `Object I/O Details` section of the I/O Analysis dashboard provides tables that display the table and index activity for the selected database.
+
+The `Tables Activity` table provides a detailed analysis of the activity for the 20 most active tables that reside within the database. Click a column heading to sort the table by the values within the column; click again to reverse the sort order.
+
+
+
+- The `Schema` column identifies the schema in which the table resides.
+- The `Table Name` column identifies the name of the table.
+- The `Scans` column displays the number of scans performed on the table.
+- The `Rows Read` column displays the number of rows read from the specified table.
+- The `Index Scans` column displays the number of index scans performed on the specified table.
+- The `Index Rows Read` column displays the number of rows read during index scans on the specified table.
+- The `Rows Inserted` column displays the number of rows inserted into the specified table.
+- The `Rows Updated` column displays the number of rows updated in the specified table.
+- The `Rows Deleted` column displays the number of rows deleted from the specified table.
+- The `Hot Rows Updated` column displays the number of hot row updates for the table; when a hot row update occurs, the new row occupies the same page as the previous row.
+- The `Total Rows` column displays the number of total rows in the table.
+- The `Dead Rows` column displays the number of rows that have been deleted, but have not been reclaimed via a VACUUM command or the AUTOVACUUM process.
+
+The `Indexes Activity` table provides a detailed analysis of the activity for the 20 most active indexes. Click a column heading to sort the table by the values within the column; click again to reverse the sort order.
+
+- The `Schema` column identifies the schema in which the index resides.
+- The `Table Name` column identifies the name of the table on which the index is defined.
+- The `Index Name` column displays the name of the index.
+- The `Scans` column displays the number of index scans performed on the specified table.
+- The `Rows Read` column displays the number of tuples read during index scans on the specified table.
+- The `Rows Fetched` column displays the number of tuples fetched by index scans.
+- The `Blocks Read` column displays the number of index blocks read.
+- The `Blocks Hit` column displays the number of index blocks hit.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/06_memory_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/06_memory_analysis_dashboard.mdx
new file mode 100644
index 00000000000..ab5e904626e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/06_memory_analysis_dashboard.mdx
@@ -0,0 +1,24 @@
+---
+title: "The Memory Analysis Dashboard"
+---
+
+
+
+
+The `Memory Analysis` dashboard provides an overview of the memory usage for the selected server and server host for the previous week:
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The Memory Analysis dashboard header displays the date and time that the server was started, the date and time that the dashboard was last updated and the number of current alerts for objects monitored by the PEM server.
+
+The `Database Server` section displays memory usage trends for the selected server.
+
+- The `Server Memory Activity` graph displays the previous week's activity on the server; the `Legend` at the bottom of the graph provide a key to the colors used to chart information for each database. A vertical key on the left side of the graph indicates the actual block count for each value.
+- The `Server Memory Configuration` pie chart displays the current memory usage (in megabytes).
+
+The `Host` section displays the free and used memory on the host system:
+
+- The `Host Memory Activity` chart plots the free and used memory on the host system over the last week.
+- Sections of the `Host Memory Configuration` pie chart represent the free and available memory on the host system when the last probe executed.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/07_object_activity_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/07_object_activity_analysis_dashboard.mdx
new file mode 100644
index 00000000000..91bbc3a55a8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/07_object_activity_analysis_dashboard.mdx
@@ -0,0 +1,45 @@
+---
+title: "The Objects Activity Analysis Dashboard"
+---
+
+
+
+
+The Objects Activity Analysis dashboard provides an overview of the size and activity of the objects that reside within the selected database.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The Objects Activity Analysis dashboard header displays the date and time that the server started, the date and time that the Object Activity Analysis dashboard was last updated, and the number of alerts currently triggered for the specified database (and monitored objects that reside within that database).
+
+The bar graphs in the `Size Overview` section plot the comparative sizes of the 5 largest tables and indexes that reside within the selected database:
+
+- The `Top 5 Largest Tables` bar graph represents the comparative sizes of the 5 largest tables that reside in the database; a vertical key displays the table size in megabytes.
+- The `Top 5 Largest Indexes` bar graph represents the comparative sizes of the 5 largest indexes that reside in the database; a vertical key displays the index size in megabytes.
+
+The `Objects Activity` table provides a detailed analysis of the activity for each table that resides within the database. Click a column heading to sort the table by the values within the column; click again to reverse the sort order.
+
+- The `Schema` column identifies the schema in which the specified table resides.
+- The `Table Name` column identifies the name of the table.
+- The `Scans` column displays the number of scans performed on the table.
+- The `Rows Read` column displays the number of rows read from the specified table.
+- The `Index Scans` column displays the number of index scans performed on the specified table.
+- The `Index Rows Read` column displays the number of rows read during index scans on the specified table.
+- The `Rows Inserted` column displays the number of rows inserted into the specified table.
+- The `Rows Updated` column displays the number of rows updated in the specified table.
+- The `Rows Deleted` column displays the number of rows deleted from the specified table.
+- The `Hot Rows Updated` column displays the number of hot row updates into the table; when a hot row update occurs, the new row occupies the same page as the previous row.
+- The `Total Rows` column displays the number of total rows in the table.
+- The `Dead Rows` column displays the number of rows that have been deleted, but have not been reclaimed via a VACUUM command or the AUTOVACUUM process.
+
+The `Objects Storage` table displays the schema objects that reside in the selected database. Click a column heading to sort the table data by the values within that column; click again to reverse the sort order.
+
+
+
+- The `Schema` column identifies the schema in which the object resides.
+- The `Object` column identifies the name of the schema object.
+- The `Object Type` column identifies the type of schema object (Table or Index).
+- The `Table Size` column lists the size of the table in megabytes (if applicable).
+- The `Index Size` column lists the size of the index (or associated index) in megabytes (if applicable).
+- The `Total (MB)` column lists the cumulative size (in megabytes) of the specified table and/or indexes and associated TOAST tables.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/08_os_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/08_os_analysis_dashboard.mdx
new file mode 100644
index 00000000000..755e08c67eb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/08_os_analysis_dashboard.mdx
@@ -0,0 +1,47 @@
+---
+title: "The Operating System Analysis Dashboard"
+---
+
+
+
+
+The `Operating System Analysis` dashboard provides a graphical analysis of the resource usage on the system hosting the selected agent.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The `Operating System Analysis` dashboard header displays the date and time that the server was last booted, the date and time that the display was last updated, and the number of triggered alerts on the system.
+
+The Operating System Analysis dashboard provides an overview of system resources. Within the `OS Overview` section:
+
+- The `CPU` graph represents the percentage of the CPU used at a given point in time. The vertical key on the left side of the graph indicates the percentage.
+- Segments of the `Storage` pie chart represent the free and used storage on the host.
+- The `Memory` graph displays the memory usage on the PEM server.
+- The `Process` graph plots the number of processes on the system. A vertical key on the left side of the graph displays the process count.
+
+The `Disk` section of the `Operating System Analysis` dashboard displays charts and information about operating system disk usage.
+
+
+
+- The `Disk` graph displays the amount of disk space used. The vertical key on the left side of the chart displays the amount of disk space used (in Megabytes). Each horizontal line on the graph represents a different mounted file system; a file system key is provided in the `Legend`.
+
+- The `I/O` graph displays the blocks read from and written to disk. A vertical key on the left side of the graph provides a block count.
+
+- The `Host File System Details` table provides information about the host file system:
+
+ > - The `File System` column displays the name of the file system.
+ > - The `Size (GB)` column displays the size of the file system in Gigabytes.
+ > - The `Used (GB)` column displays the amount of the file system that is currently storing information.
+ > - The `Available (GB)` column displays the amount of space still available on the file system.
+ > - The `% Used` column displays the percentage of the total storage space in use.
+ > - The `Mounted On` column displays the directory or drove on which the file system is mounted.
+
+Graphs in the `Network` section of the `Operating System Analysis` dashboard plot the network and packet traffic:
+
+
+
+- The `Packets` graph displays the number of packets sent and received across the network. The `Legend` provides a key to the color charted for each network interface. The vertical key on the left side of the graph indicates the packet count.
+- The `Traffic` graph displays the amount of data transferred across the network. The `Legend` provides a key to the color charted for each network interface. The vertical key on the left side of the graph displays the traffic, in KB.
+
+Please note: The network bandwidth may not display if the monitored server is a Linux platform that resides in a virtual machine. This is expected behavior.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/09_probe_log_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/09_probe_log_analysis_dashboard.mdx
new file mode 100644
index 00000000000..8e04935ca38
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/09_probe_log_analysis_dashboard.mdx
@@ -0,0 +1,22 @@
+---
+title: "The Probe Log Analysis Dashboard"
+---
+
+
+
+
+The Probe Log Analysis dashboard displays error messages from the PEM agent.
+
+
+
+The header information includes the date and time that the server was first started, the date and time that the page was last updated, and the current number of triggered alerts.
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The `Probe Log` table displays error messages returned by the PEM Agent. Entries in the Probe Log table may reflect incorrect agent binding information or authentication errors between the PEM agent and the server.
+
+- The `Id` column displays a unique identifier for each entry in the table.
+- The `Timestamp` column displays the date and time that the log entry was made.
+- The `Probe Name` column displays the name of the probe that recorded the log entry.
+- The `Server Name` column displays the name of the server on which the error occurred.
+- The `Error Message` column displays the error message returned by the probe.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/10_server_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/10_server_analysis_dashboard.mdx
new file mode 100644
index 00000000000..682b45fbe75
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/10_server_analysis_dashboard.mdx
@@ -0,0 +1,53 @@
+---
+title: "The Server Analysis Dashboard"
+---
+
+
+
+
+The Server Analysis dashboard provides a graphical analysis of a monitored server's usage statistics.
+
+
+
+The Server Analysis dashboard header displays the date and time that the server was started, the date and time that the display was last updated, and the number of current alerts for items monitored by the PEM server.
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+Graphs within the `Storage` section of the dashboard provide an analysis of the space consumed by databases and tablespaces on the server:
+
+- The `Database Size` graph displays the size (in Megabytes) of the 5 largest databases that reside on the PEM server. The `Legend` at the bottom of the graph associates each database name with a color in the graph.
+- The `Tablespace Size` graph displays the size (in Megabytes) of the 5 largest tablespaces that reside on the PEM server. The `Legend` at the bottom of the graph associates each tablespace name with a color in the graph.
+
+The `Memory` section of the dashboard provides an overview of the efficiency of the buffer cache over the previous week, and an analysis of the current swap memory usage:
+
+- The `Shared Buffers` chart compares the number of data blocks found in the shared memory cache with the number of blocks read from disk. A high hit-to-miss ratio indicates an efficiently configured memory cache.
+- The `Host Memory` pie chart displays the current swap memory usage.
+
+The `Users` section of the `Server Analysis` dashboard provides an overview of the user activity on the server:
+
+- The `User Activity` chart displays connection statistics gathered over the last week. The `Legend` at the bottom of the chart provides a key to the data displayed.
+- The `Connection Overview` pie chart compares the currently active connections to the currently idle connections.
+
+The `I/O` section of the `Server Analysis` dashboard provides an overview of the transactions processed by the server over the last week:
+
+
+
+- The `Disk` chart displays the number of 8KB blocks read from disk, and the number of 8KB blocks written to disk over the last week.
+- The `Row Activity` chart plots row activity on tables stored on the server over the past week. The `Legend` at the bottom of the chart provides a key to the data displayed.
+- The `Commits/Rollbacks` chart displays the number of transactions committed and rolled back on the selected server within the last week. A vertical count on the left side of the graph indicates the aborted transaction count, while the `Legend` at the bottom of the chart provides a key to the commits and rollbacks charted.
+
+The `Database Analysis` table displays a list of the monitored databases that reside on the server, and the statistics gathered for each database over the last week. Click a column heading to sort the table by the data displayed in the column; click again to reverse the sort order.
+
+
+
+- The `Database` column displays the database name.
+- The `Connections` column displays the number of current connections to the database.
+- The `TX Committed` column displays the number of transactions committed to the database within the last week.
+- The `TX Rolled Back` column displays the number of transactions rolled back within the last week.
+- The `Blocks Hit` column displays the number of blocks hit in the cache (in megabytes) within the last week.
+- The `Blocks Read` column displays the number of blocks read from memory (in megabytes) within the last week.
+- The `Tuples Fetched` column displays the number of tuples fetched within the last week.
+- The `Tuples Returned` column displays the number of tuples returned within the last week.
+- The `Tuples Inserted` column displays the number of tuples inserted into the database within the last week.
+- The `Tuples Updated` column displays the number of tuples updated in the database within the last week.
+- The `Tuples Deleted` column displays the number of tuples deleted from the database within the last week.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/11_server_log_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/11_server_log_analysis_dashboard.mdx
new file mode 100644
index 00000000000..7677fd1d5cf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/11_server_log_analysis_dashboard.mdx
@@ -0,0 +1,44 @@
+---
+title: "The Server Log Analysis Dashboard"
+---
+
+
+
+
+The `Server Log Analysis` dashboard displays the log files for the selected server. To view the `Server Log Analysis` dashboard, right-click on the name of a monitored server in the PEM client tree control, and navigate through the `Dashboards` menu, selecting `Server Log Analysis`.
+
+
+
+The header information on the `Server Log Analysis` dashboard displays the date and time that the server was started, the date and time that the page was last updated, and the current number of triggered alerts.
+
+The `Server Log` table displays the contents of the log files that are stored on the PEM server. For content to displayed, you must check the box next to `Import logs to PEM` when using Log Manager to configure logging for the server.
+
+Entries are displayed in chronological order, most-recent log entries first. Use the scroll bars to navigate through the log entries, or to view columns that are off of the display.
+
+Headings at the top of the server log table identify the information stored in each column:
+
+- The `Id` column identifies the PEM agent that monitors the server that initiated the recorded transaction.
+- The `Server` column identifies the server that initiated the recorded transaction.
+- The `Timestamp` column displays the date and time that the log entry was made.
+- The `User Name` column displays the name of the user that executed the recorded transaction.
+- The `Database Name` column displays the name of the database on which the recorded transaction was executed.
+- The `Process ID` column displays the identifier of the process that executed the recorded transaction.
+- The `Session ID` column displays the identifier of the session in which the transaction was executed.
+- The `Transaction ID` column displays the transaction identifier.
+- The `Connection From` column displays the host name or IP address from which the client session connected.
+- The `Command` column displays the type of command executed.
+- The `Message` column displays the transaction message.
+
+Click `Show Filters` to display a panel that you can use to filter the audit log entries that are shown in the table below; click on `Hide Filters` to close the panel.
+
+
+
+Use the fields within the filter definition box to describe a selection criteria that PEM will use to select a subset of a report for display:
+
+- Use the date and time selectors in the `From` field to specify a starting date and time for the displayed log entries.
+- Use the date and time selectors in the `To` field to specify an ending date and time for the displayed log entries.
+- Enter a username in the `Username` field to show log entries for the specified user only.
+- Enter a database name in the `Database` field to show log entries for the specified database only.
+- Enter a command type (for example; 'SELECT', 'authentication' or 'idle') in the `Command type` field to show log entries of that type only.mmands that will be displayed in the filtered report.
+
+When you've described the criteria by which you wish to filter the audit logs, click `Filter` to display the filtered server log in the lower portion of the `Server Log Analysis` dashboard. Click the `Hide Filters` label to close the filter definition box.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/12_session_activity_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/12_session_activity_analysis_dashboard.mdx
new file mode 100644
index 00000000000..89ba62d318f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/12_session_activity_analysis_dashboard.mdx
@@ -0,0 +1,54 @@
+---
+title: "The Session Activity Analysis Dashboard"
+---
+
+
+
+
+The Session Activity Analysis dashboard provides information about the session workload and lock activity for the selected server:
+
+
+
+The Session Activity Analysis dashboard header displays the date and time that the server was started, the date and time that the dashboard was last updated and the number of current alerts for the server.
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the `Session Activity Analysis` dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM client `Management` menu.
+
+The `Session Workload` table provides information about the current session workload for the server. Click a column heading to sort the table data by the selected column; click the heading a second time to reverse the sort order. The Session Workload table displays the following information:
+
+- The `Session ID` column displays the process identifier for the session.
+- The `User Name` column displays the (role) name of the user that established the client connection to the server.
+- The `Source` column displays the IP address and port number of the client.
+- The `Database Name` column displays the name of the database to which the client is connected.
+- The `Waiting` column displays `Yes` if the session is waiting for a lock; `No` if the session is not waiting for a lock.
+- The `Backend Start` column displays the date and time that the client established a connection to the server.
+- The `Transaction Start` column displays the date and time that the current transaction started, if applicable.
+- The `Query Start` column displays the date and time that the current query started, if applicable.
+- The `Memory Usage` column displays the amount of memory used by the session; this column is not displayed if the server is remotely monitored.
+- The `Swap Usage` column displays the amount of swap space used by the session; this column is not displayed if the server is remotely monitored.
+- The `CPU Usage` column displays the amount of CPU resources used by the session; this column is not displayed if the server is remotely monitored.
+- The `IO Reads (#bytes)` column displays the number of bytes used during read transactions the session; this column is not displayed if the server is remotely monitored.
+- The `IO Writes (#bytes)` column displays the number of bytes used during write transactions the session; this column is not displayed if the server is remotely monitored.
+
+The `Session Lock Activity` table displays a list of locks held by processes on the server. Click a column heading to sort the table data by the selected column; click the heading a second time to reverse the sort order. The Session Lock Activity table displays the following information:
+
+- The `Session ID` column displays the process ID for the session.
+- The `User Name` column displays the name of the user holding (or waiting for) the lock.
+- The `Source` column displays the IP address and port number of the client.
+- The `Database Name` column displays the name of the database to which the client is connected.
+- The `Blocked` column indicates if the lock request is blocked by another lock.
+- The `Blocked By` column specifies the session ID of the session that is holding the lock.
+- The `Lock Type` column displays the type of lock that is held by the client. Lock Type may be:
+
+> - `advisory` - a user-defined lock created by pg\_advisory\_lock() or pg\_advisory\_lock\_shared()
+> - `extend` - a lock held while extending a table or index
+> - `object` - a lock held on a database object
+> - `page` - a lock held on a page (within the shared buffer cache)
+> - `relation` - a lock held on the metadata describing a table, view, or sequence (to prevent another session from altering the table, view, or sequence)
+> - `transactionid` - a lock held on a transaction ID (one session typically waits for another transaction to complete by waiting on the other session's transaction ID)
+> - `tuple` - lock held on a tuple (typically, a tuple which has been inserted, updated, or deleted, but not yet committed)
+> - `userlock` - a user-defined lock created with the LOCK statement
+> - `virtualxid` - a lock identified by a virtual transaction ID.
+
+- The `Object ID` column displays the OID of the relation, or NULL if the object is not a relation (of part of a relation).
+- The `Mode` column displays the name of the lock mode help (or sought) by the process.
+- The `Transaction Start` column displays the date and time that the transaction started.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/13_session_waits_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/13_session_waits_dashboard.mdx
new file mode 100644
index 00000000000..35926cb7c0f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/13_session_waits_dashboard.mdx
@@ -0,0 +1,29 @@
+---
+title: "The Session Waits Analysis Dashboard"
+---
+
+
+
+
+The `Session Wait Analysis` dashboard provides an overview of the current DRITA wait events for an Advanced Server session. For more information about DRITA wait events, please see the EDB Postgres Advanced Server Guide.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the `Alerts` dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The Session Wait Analysis dashboard header displays the date and time that the server started, the date and time that the dashboard was last updated, and the number of alerts currently triggered for the specified database (and monitored objects that reside within that database).
+
+The `Session Waits Overview` displays statistics gathered by the most recent execution of the PEM probe:
+
+- The `Session Waits By Number Of Waits` pie chart displays the 5 most frequently encountered wait events, per Advanced Server session. For more information about the events that can cause a wait event, see the EDB Postgres Advanced Server Guide.
+- The `Session Waits By Time Waited` pie chart displays the 5 wait events that consume the most time, per Advanced Server session. To gather and display data in the `Session Time Waits by Time Waited` pie chart, you must modify the `postgresql.conf` file for the monitored server, setting *timed\_statistics = on*, and restart the server. Please note that this will cause server performance to degrade. For more information about using Advanced Server DRITA timers and the events that can cause a wait event, please see the EDB Postgres Advanced Server Guide.
+
+The `Session Waits Details` table lists the current system wait events for the selected database. Click a column heading to sort the table by the column data; click again to reverse the sort order.The table displays:
+
+- The `User` column displays the name of the user that encountered the wait.
+- The `Wait Name` column displays the name of the of wait event.
+- The `Wait Count` column displays the total number of waits encountered by the user.
+- The `Time (ms)` displays the number of milliseconds that the user waited for the specified event.
+- The `Wait Time (%)` column displays the percentage of the total wait time consumed by the specified wait event.
+
+To gather and display data in the Time (ms) and Wait Time (%) columns, you must modify the `postgresql.conf` file for the monitored server, setting *timed\_statistics = on*, and restart the server. Please note that this will cause server performance to degrade. For more information about using Advanced Server DRITA timers, please see the EDB Postgres Advanced Server Guide.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/14_storage_analysis_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/14_storage_analysis_dashboard.mdx
new file mode 100644
index 00000000000..411207b9316
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/14_storage_analysis_dashboard.mdx
@@ -0,0 +1,37 @@
+---
+title: "The Storage Analysis Dashboard"
+---
+
+
+
+
+The `Storage Analysis` dashboard provides information about the size of objects stored on the server and about available storage space on the server.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The Storage Analysis dashboard header displays the date and time that the PEM server started, the date and time that the dashboard was most recently updated, and the number of triggered alerts on objects monitored by the PEM server.
+
+The Storage Overview section displays information about the size of databases, tablespaces and the host:
+
+- The `Database Overview` pie chart shows the relative size of monitored databases stored on the server. The key (located below the chart) matches the database name to the respective color on the chart.
+- The `Tablespace Overview` pie chart shows the relative size of tablespaces on the server. The key (located below the chart) matches the tablespace name to the respective color on the chart.
+- The `Host Overview` pie chart represents the amount of used and free storage space on the server as of the last probe execution.
+
+The `Database Details` table displays the size of each database stored on the server. Click a column heading to sort the table by the specified column; click again to reverse the sort order.
+
+- The `Database Name` column displays the name of the database.
+- The `Database Size (MB)` column displays the size of the database in megabytes.
+- The `Tablespace Name` column displays the name of the default tablespace assigned to the database.
+
+The `Tablespace Details` table lists the name and size (in megabytes) of each tablespace defined for the server. Click a column heading to sort the table by the specified column; click again to reverse the sort order.
+
+The `Host File System Details` table displays information about the file systems that reside on the system that hosts the PEM server:
+
+- The `File System` column displays the name of the file system.
+- The `Size (GB)` column displays the size of the file system in megabytes.
+- The `Used (GB)` column displays the amount of the file system that is currently storing information.
+- The `Available (GB)` column displays the amount of space available on the file system.
+- The `% Used` column displays the percentage of the total storage space in use.
+- The `Mounted On` column displays the directory on which the file system is mounted.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/15_system_wait_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/15_system_wait_dashboard.mdx
new file mode 100644
index 00000000000..cb4020ca842
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/15_system_wait_dashboard.mdx
@@ -0,0 +1,30 @@
+---
+title: "The System Wait Analysis Dashboard"
+---
+
+
+
+
+The System Wait Analysis dashboard provides an overview of the current DRITA wait events for an Advanced Server database. For more information about DRITA wait events, please see the EDB Postgres Advanced Server Guide.
+
+
+
+Use parameters on the [PEM Server Configurations](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog to specify the auto-refresh rate for the `Alerts` dashboard. To access the `Server Configuration` dialog, select `Server Configuration...` from the PEM web interface `Management` menu.
+
+The System Waits Analysis dashboard header displays the date and time that the server started, the date and time that the System Waits Analysis dashboard was last updated, and the number of alerts currently triggered for the specified database (and monitored objects that reside within that database).
+
+The `System Waits Overview` displays statistics gathered by the most recent execution of the PEM probe:
+
+- The `System Waits by Number of Waits` pie chart displays the 5 most frequently encountered wait events for the selected Advanced Server server. For more information about the events that can cause a wait event, see the EDB Postgres Advanced Server Guide.
+- The `System Waits by Time Waited` pie chart displays the 5 wait events that consume the most time for the selected Advanced Server server. To gather and display data in the `System Waits by Time Waited` pie chart, you must modify the `postgresql.conf` file for the monitored server, setting *timed\_statistics = on*, and restart the server. Please note that this will cause server performance to degrade. For more information about using Advanced Server DRITA timers, please see the EDB Postgres Advanced Server Guide.
+
+The `System Waits Details` table lists the current system wait events for the selected server. Click a column heading to sort the table by the column data; click again to reverse the sort order.The table displays:
+
+- The `Event` column displays the name of the wait event.
+- The `Wait Count` column contains the number of times that the wait event occurred.
+- The `Percent of Total` column displays the percentage of the total wait count consumed by this event.
+- The `Time Waited (ms)` displays the number of milliseconds that the server waited for the event.
+- The `Percent of Time Waited` displays the percentage of the total wait time consumed by this event.
+- The `Average Wait Time (ms)` column displays the average wait time for this event.
+
+To gather and display data in the `Time Waited (ms)` and `Percent of Time Waited` columns, you must modify the `postgresql.conf` file for the monitored server, setting *timed\_statistics = on*, and restart the server. Please note that this will cause server performance to degrade. For more information about using Advanced Server DRITA timers, please see the EDB Postgres Advanced Server Guide.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/16_str_replication_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/16_str_replication_dashboard.mdx
new file mode 100644
index 00000000000..93707db275b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/16_str_replication_dashboard.mdx
@@ -0,0 +1,77 @@
+---
+title: "The Streaming Replication Analysis Dashboard"
+---
+
+
+
+
+The `Streaming Replication Analysis` Dashboard displays statistical information about WAL activity for a monitored server. By default, replication probes are disabled; to view the `Streaming Replication Analysis` dashboard, you must enable probes on the primary and replica nodes. To enable the probes on the primary node, highlight the name of the primary server in the PEM client `Browser` tree control, and select `Manage Probes...` from the `Management` menu. Use the `Manage Probes` tab to enable the following probes:
+
+- Streaming Replication
+- WAL Archive Status
+
+To enable the probes on the replica node, highlight the name of the replica server in the PEM client `Browser` tree control, and select `Manage Probes...` from the `Management` menu. Use the `Manage Probes` tab to enable the following probe:
+
+- Streaming Replication Lag Time
+
+Then, to open the `Streaming Replication Analysis` dashboard, navigate to the `Monitoring` tab, and:
+
+1. Select the name of the agent that monitors the node from the `Agents` drop-down menu.
+2. Select the name of the monitored server from the `Servers` drop-down menu.
+3. Select `Streaming Replication Analysis` from the `Dashboards` drop-down menu.
+
+The `Streaming Replication Analysis` dashboard header includes the date and time that the server was last started, the date and time that the page was last updated, and a current count of triggered alerts.
+
+When accessing the `Streaming Replication Analysis` dashboard for the primary node of a replication scenario, the dashboard displays information about the write-ahead log activity for the server.
+
+
+
+The `WAL Archive Status` graph displays WAL activity; the vertical key on the left side of the graph indicates the archive count; times are displayed across the bottom of the graph.
+
+The `WAL Segment Lag` graph displays the segment lag for the replica nodes that are associated with the selected server. The vertical key on the left side of the graph indicates the archive count. Each node is displayed in a different color on the graph. The `Legend` provides a key to the identity (hostname and port) of each graphed replica node.
+
+The `WAL Page Lag` graph displays the page lag activity for each replica node associated with the selected server. The vertical key on the left side of the graph indicates the page count. Each node is displayed in a different color on the graph. The `Legend` provides a key to the identity (hostname and port) of each graphed replica node.
+
+## Monitoring a Replica Node
+
+When accessing the `Streaming Replication Analysis` dashboard for the replica node of a replication scenario, the dashboard displays information about the write-ahead log activity for the server.
+
+
+
+The `WAL Archive Status` graph displays WAL activity; the vertical key on the left side of the graph indicates the archive count; times are displayed across the bottom of the graph.
+
+The `WAL Segment Lag` graph displays the segment lag for the replica nodes that are associated with the selected server. The vertical key on the left side of the graph indicates the archive count. Each replica node is displayed in a different color on the graph. The `Legend` provides a key to the identity (hostname and port) of each graphed slave node.
+
+The `WAL Page Lag` graph displays the page lag activity for each replica node associated with the selected server. The vertical key on the left side of the graph indicates the page count. Each node is displayed in a different color on the graph. The `Legend` provides a key to the identity (hostname and port) of each graphed slave node.
+
+The `Replication Time Lag` graph displays the delay between the time that an operation is performed on the primary node of the replication scenario and the time that the operation is written to the replica node. The vertical key on the left side of the graph indicates the replication delay in minutes. Hover your mouse over a point on the graph to display the date and time that corresponds to that coordinate.
+
+A label at the bottom of the dashboard confirms the status of the replication replica.
+
+## Monitoring a Failover Manager Cluster
+
+If you have configured PEM to monitor a [Failover Manager](../../04_toc_pem_features/#monitoring_a_failover_manager_cluster) cluster, the Streaming Replication Analysis dashboard will display tables that provide an overview of the clusters status and configuration, and information about each cluster member. To display cluster information on the Streaming Replication dashboard, you must provide the following information on the `Advanced` tab of the server `Properties` dialog for each node of the cluster:
+
+- Use the `EFM Cluster Name` field to specify the name of the Failover Manager cluster. The cluster name is the prefix of the name of the cluster properties file. For example, if your cluster properties file is named `efm.properties`, your cluster name is `efm`.
+- Use the `EFM Installation Path` field to specify the location of the Failover Manager binary file. By default, the Failover Manager binary file is installed in `/usr/edb/efm-3.1/bin`.
+
+The `Failover Manager Cluster Status` section of the Streaming Replication Analysis dashboard displays information about the monitored cluster:
+
+
+
+The `Failover Manager Cluster Information` table provides information about the Failover Manager cluster:
+
+- The `Properties` column displays the name of the cluster property.
+- The `Values` column displays the current value of the property.
+
+The `Failover Manager Node Status` table displays information about each node of the Failover Manager cluster:
+
+- The `Agent Type` column displays the type of agent that resides on the node; the possible values are Primary, Replica, Witness, Idle, and Promoting.
+- The `Address` column displays the IP address of the node.
+- The `Agent` column displays the status of the agent that resides on the node.
+- The `DB` column displays the status of the database that resides on the node.
+- The `XLog Location` column displays the transaction log location of the database.
+- The `Status Information` column displays any error-related information about the node.
+- The `XLog Information` column displays any error-related information about the transaction log.
+- The `VIP` column displays the VIP address that is associated with the node.
+- The `VIP Status` column displays `True` if the VIP is active for the node, `False` if the VIP is not.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/index.mdx
new file mode 100644
index 00000000000..d1ec34aa910
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/01_dashboards/index.mdx
@@ -0,0 +1,94 @@
+---
+title: "Dashboards"
+---
+
+
+
+
+Postgres Enterprise Manager uses metrics (retrieved by probes) to generate the statistical information displayed on the dashboards. Dashboards are presented in a hierarchy comparable to the PEM client tree control; the dashboard for each object within the tree control displays the information for that object, as well as for any monitored object that resides below that level in the tree control, if appropriate.
+
+Each dashboard header displays the date and time that the server was started (if relevant), the date and time that the dashboard was last updated, and the current number of triggered alerts. Navigation menus displayed in the dashboard header provide easy access to other dashboards. Menus are organised hierarchically; only those menus appropriate for the object currently highlighted in the tree control are available:
+
+- Select `Global Overview` from any dashboard to return to the Global Overview dashboard.
+- Select the name of an agent from the `Agents` menu to navigate to the Operating System Analysis dashboard for that agent.
+- Select a server name from the `Servers` menu to navigate to the Server Analysis dashboard for that server.
+- Select a database name from the `Databases` menu to navigate to the Database Analysis dashboard for that database.
+- Use the `Dashboards` menu to navigate to informational dashboards at the global level, or for the selected agent, server or database.
+
+Dashboards display statistical information in the form of:
+
+- Tables - Tables provide statistical information collected by a PEM probe.
+- Pie charts - Pie charts display information collected by the most recent execution of a probe.
+- Bar graphs - Bar graphs display comparative statistics collected by the most recent execution of a probe.
+- Line graphs - Line graphs display statistical data collected by PEM probes.
+
+Options on the `Dashboard Configuration` dialog allow you to link the time lines of all of the line graphs on the dashboard. To open the `Dashboard Configuration` dialog, click the wrench icon displayed in the dashboard header.
+
+
+
+- Set the `Link timelines of all the line charts` slider to `Enable` to indicate that the specified timeline should be applied to line graphs displayed on the dashboard; if set to `Disable`, your preferences will be preserved for later use, but will not modify the amount of data displayed.
+- Use the `Days` selector to specify the number of days of gathered data that should be displayed on line graphs.
+- Use the `Hour(s)` selector to specify the number of hours of gathered data that should be displayed on line graphs.
+- Check the box next to `Remember configuration for this dashboard` to indicate that the customized time span should be applied to the current dashboard only; if left unchecked, the time span will be applied globally to line graphs on all dashboards.
+
+Please note that settings specified on the `Dashboard Configuration` dialog are applied only to the current user's session.
+
+When you've specified your preferences, click `Save` to preserve your changes and exit the dialog; click `Cancel` to exit the dialog without preserving your changes.
+
+To sort statistics that are provided in table form, click on a column heading; click again to reverse the sort order. Each table offers a stable sort feature - For example, to sort a table by ascending `Session ID` within each user name group, sort first by the `Session ID` column, then sort by the `User Name` column.
+
+Hover your mouse over the upper-right corner of each graph, chart or table to reveal the PEM client toolbar icons. Hover over an icon to display a tooltip that briefly explains the icon's functionality:
+
+- Use the `Refresh` icon to update the information displayed on a dashboard.
+- Use the `Save Chart as Image` icon to save the selected chart as a .jpeg image.
+- Use the `Full Screen` icon to enlarge the chart to reveal granular details about the charted data.
+- Click the `Personalize the chart configuration` icon to access a control panel that allows you to select chart-specific display details.
+- Hover over the `Explain` icon to review a description of the information shared in the graph or chart.
+
+In the lower-right corner of each graph or chart is a legend that identifies each item plotted in the graph or chart.
+
+If displayed, click the information icon in the upper-left hand corner of a chart to display a note about the chart content, and if applicable, a link that will allow you to enable one or more probes that retrieve content for the chart.
+
+## Accessing Dashboards
+
+Navigation menus in the dashboard header provide easy access to other dashboards. The menus are organized hierarchically, allowing you to jump from object to object at any level:
+
+- The [Global Overview](../04_toc_pem_features/01_dashboards/#global_overview_dashboard) option opens the `Global Overview` dashboard.
+- The `Agents` menu expands to display a list of agents. Select an agent from the list to access the `Operating System Analysis` dashboard for that agent.
+- The `Servers` menu expands to display a list of monitored servers. Select a server from the list to access the `Server Analysis` dashboard for that server.
+- The `Remote Servers` menu expands to display a list of servers that are monitored by a remote agent. Select a server from the list to access the `Server Analysis` dashboard for the server.
+- The `Databases` menu expands to display a list of databases. Select a database from the list to access the `Database Analysis` dashboard for the database.
+- The `Dashboards` menu expands to display a list of the dashboards that are available at the global level, or for the current agent, server or database. Select a dashboard from the list to navigate to that dashboard.
+
+## Creating custom charts and dashboards
+
+PEM (version 4.0 and above) allows you to create your own [Charts](../04_toc_pem_features/10_pem_manage_charts/#pem_create_new_chart) and [Dashboards](../04_toc_pem_features/11_pem_manage_dashboards/#pem_custom_dashboard), allowing you to tailor the interface to the requirements of your organization or individual responsibility.
+
+## Available Dashboards
+
+PEM offers the following dashboards:
+
+- [Alerts Dashboard](../04_toc_pem_features/01_dashboards/#alerts_dashboard)
+- [Audit Log Dashboard](../04_toc_pem_features/01_dashboards/#audit_log_dashboard)
+- [Database Analysis Dashboard](../04_toc_pem_features/01_dashboards/#database_analysis_dashboard)
+- [Global Overview Dashboard](../04_toc_pem_features/01_dashboards/#global_overview_dashboard)
+- I/O Analysis Dashboard <io\_analysis\_dashboard>
+- [Memory Analysis Dashboard](../04_toc_pem_features/01_dashboards/#memory_analysis_dashboard)
+- [Object Activity Analysis Dashboard](../04_toc_pem_features/01_dashboards/#object_activity_analysis_dashboard)
+- [Operating System Analysis Dashboard](../04_toc_pem_features/01_dashboards/#os_analysis_dashboard)
+- [Probe Log Analysis Dashboard](../04_toc_pem_features/01_dashboards/#probe_log_analysis_dashboard)
+- [Server Analysis Dashboard](../04_toc_pem_features/01_dashboards/#server_analysis_dashboard)
+- [Server Log Analysis Dashboard](../04_toc_pem_features/01_dashboards/#server_log_analysis_dashboard)
+- [Session Activity Analysis Dashboard](../04_toc_pem_features/01_dashboards/#session_activity_analysis_dashboard)
+- [Session Wait Analysis Dashboard](../04_toc_pem_features/01_dashboards/#session_waits_dashboard)
+- [Storage Analysis Dashboard](../04_toc_pem_features/01_dashboards/#storage_analysis_dashboard)
+- [System Wait Analysis Dashboard](../04_toc_pem_features/01_dashboards/#system_wait_dashboard)
+- [Streaming Replication Analysis Dashboard](../04_toc_pem_features/01_dashboards/#str_replication_dashboard)
+
+Contents:
+
+
+
+alerts\_dashboard audit\_log\_dashboard database\_analysis\_dashboard global\_overview\_dashboard io\_analysis\_dashboard memory\_analysis\_dashboard object\_activity\_analysis\_dashboard os\_analysis\_dashboard probe\_log\_analysis\_dashboard server\_analysis\_dashboard server\_log\_analysis\_dashboard session\_activity\_analysis\_dashboard session\_waits\_dashboard storage\_analysis\_dashboard system\_wait\_dashboard str\_replication\_dashboard
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options.mdx
new file mode 100644
index 00000000000..f2b80f951d0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options.mdx
@@ -0,0 +1,12 @@
+---
+title: "Configuration Options"
+---
+
+
+
+
+A number of aspects of PEM's behaviour can be controlled using global configuration options. Use the [Server Configuration dialogue](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) to manage Server Options. The configuration parameters used are listed below.
+
+Please note that this list is subject to change.
+
+| Parameter name | Value/Unit | Description |
|---|---|---|
| audit_log_retention_time | 30 days | Specifies the number of days that an audit log will be retained on the PEM server. |
| auto_create_agent_alerts | true | Specifies whether to create default agent level alerts automatically when an agent is registered. |
| auto_create_server_alerts | true | Specifies whether to create default server level alerts automatically when a server is bound to an agent. |
| chart_disable_bullets | false | Enable/disable bullets on line charts on dashboards and Capacity Manager reports. |
| cm_data_points_per_report | 50 | Specifies the number of data points to plot on charts on Capacity Manager reports. |
| cm_max_end_date_in_years | 5 years | Specifies the maximum amount of time that the Capacity Manager will extrapolate data for. Ensures that threshold-based end dates of on reports do not get extrapolated indefinitely. |
| dash_alerts_timeout | 60 seconds | Specifies the number of seconds after which the components of the Alerts dashboard are auto-refreshed. |
| dash_db_comrol_span | 7 days | Specifies the number of days worth of data to plot on the Commit/Rollback Analysis chart on the Database Analysis dashboard and Server Analysis dashboard. |
| dash_db_comrol_timeout | 1800 seconds | Specifies the number of seconds after which the Commits/Rollbacks line chart is auto-refreshed on the Database Analysis dashboard and Server Analysis dashboard. |
| dash_db_connovervw_timeout | 300 seconds | Specifies the number of seconds after which the Connection Overview pie chart is auto-refreshed in the Database Analysis dashboard. |
| dash_db_eventlag_span |
| Specifies the number of days worth of data to plot on the Number of Events Lag chart for slony replication on the Database Analysis dashboard. |
| dash_db_eventlag_timeout | 1800 seconds | Specifies the number of seconds after which the Number of Events Lag line chart for slony replication is auto-refreshed on the Database Analysis dashboard. |
| dash_db_hottable_rows | 25 rows | Specifies the number of rows to show on the HOT Table Analysis table on the Database Analysis dashboard. |
| dash_db_hottable_timeout | 300 seconds | Specifies the number of seconds after which the Hot Tables table is auto-refreshed in the Database Analysis dashboard. |
| dash_db_io_span | 7 days | Specifies the number of days worth of data to plot on the Database I/O Analysis chart on the Database Analysis dashboard and I/O Analysis dashboard. |
| dash_db_io_timeout | 1800 seconds | Specifies the number of seconds after which the Database I/O line chart is auto-refreshed on the Database Analysis dashboard and I/O Analysis dashboard. |
| dash_db_rowact_span | 7 days | Specifies the number of days worth of data to plot on the Row Activity Analysis chart on the Database Analysis dashboard, the I/O Analysis dashboard, and the Server Analysis dashboard. |
| dash_db_rowact_timeout | 1800 seconds | Specifies the number of seconds after which the Row Activity line chart is auto-refreshed on the Database Analysis dashboard, the I/O Analysis dashboard, and the Server Analysis dashboard. |
| dash_db_storage_timeout | 300 seconds | Specifies the number of seconds after which the Storage bar chart is auto-refreshed in the Database Analysis dashboard. |
| dash_db_timelag_span | 7 days | Specifies the number of days worth of data to plot on the Time Lag chart for Slony replication on the Database Analysis dashboard. |
| dash_db_timelag_timeout | 1800 seconds | Specifies the number of seconds after which the Time Lag line chart for slony replication is auto-refreshed on the Database Analysis dashboard. |
| dash_db_useract_span | 7 days | Specifies the number of days worth of data to plot on the User Activity Analysis chart on the Database Analysis dashboard. |
| dash_db_useract_timeout | 1800 seconds | Specifies the number of seconds after which the User Activity line chart is auto-refreshed in the Database Analysis dashboard. |
| dash_efm_timeout | 300 seconds | Specifies the number of seconds after which the Failover Manager Node Status and Failover Manager Cluster Info line chart is auto-refreshed on the Streaming Replication dashboard. |
| dash_global_overview_timeout | 30 seconds | Specifies the number of seconds after which the components of the Global Overview dashboard are auto-refreshed. |
| dash_header_timeout | 60 seconds | Specifies the number of seconds after which the information on the header of all the dashboards are auto-refreshed. |
| dash_io_chkpt_span | 7 days | Specifies the number of days worth of data to plot on the Checkpoints chart on the I/O Analysis dashboard. |
| dash_io_chkpt_timeout | 1800 seconds | Specifies the number of seconds after which the Checkpoints line chart is auto-refreshed on the I/O Analysis dashboard. |
| dash_io_hotindx_timeout | 300 seconds | Specifies the number of seconds after which the Hot Indexes bar chart is auto-refreshed on the I/O Analysis dashboard. |
| dash_io_hottbl_timeout | 300 seconds | Specifies the number of seconds after which the Hot Tables bar chart is auto-refreshed on the I/O Analysis dashboard. |
| dash_io_index_objectio_rows | 25 rows | Specifies the number of rows displayed on the Index Activity table on the I/O Analysis dashboard and the Object Activity Analysis dashboard. |
| dash_io_index_objectio_timeout | 60 seconds | Specifies the number of seconds after which the Index Activity table is auto-refreshed on the I/O Analysis dashboard and the Object Activity Analysis dashboard. |
| dash_io_objectio_rows | 25 rows | Specifies the number of rows displayed in the Object I/O Details table on the I/O Analysis dashboard and Object Activity Analysis dashboard. |
| dash_io_objectio_timeout | 300 seconds | Specifies the number of seconds after which the Object I/O Details table is auto-refreshed on the I/O Analysis dashboard and Object Activity Analysis dashboard. |
| dash_memory_hostmemact_span | 7 days | Specifies the number of days worth of data to plot on the Host Memory Activity Analysis chart on the Memory Analysis dashboard. |
| dash_memory_hostmemact_timeout | 1800 seconds | Specifies the number of seconds after which the Host Memory Activity line chart is auto-refreshed on the Memory Analysis dashboard. |
| dash_memory_hostmemconf_timeout | 300 seconds | Specifies the number of seconds after which the Host Memory Configuration pie chart is auto-refreshed on the Memory Analysis dashboard and Server Analysis dashboard. |
| dash_memory_servmemact_span | 7 days | Specifies the number of days worth of data to plot on the server Memory Activity Analysis chart on the Memory Analysis dashboard. |
| dash_memory_servmemact_timeout | 1800 seconds | Specifies the number of seconds after which the Server Memory Activity line chart is auto-refreshed on the Memory Analysis dashboard. |
| dash_memory_servmemconf_timeout | 300 seconds | Specifies the number of seconds after which the Server Memory Configuration pie chart is auto-refreshed on the Memory Analysis dashboard. |
| dash_objectact_objstorage_rows | 15 rows | Specifies the number of rows to show on the Object Storage table on the Object Activity Analysis dashboard. |
| dash_objectact_objstorage_timeout | 300 seconds | Specifies the number of seconds after which the Object Storage table is auto-refreshed in the Object Activity Analysis dashboard. |
| dash_objectact_objtopindexes_timeout | 300 seconds | Specifies the number of seconds after which the Top 5 Largest Indexes bar chart is auto-refreshed in the Object Activity Analysis dashboard. |
| dash_objectact_objtoptables_timeout | 300 seconds | Specifies the number of seconds after which the Top 5 Largest Tables bar chart is auto-refreshed in the Object Activity Analysis dashboard. |
| dash_os_cpu_span | 7 days | Specifies the number of days worth of data to plot on the CPU chart on the Operating System Analysis dashboard. |
| dash_os_cpu_timeout | 1800 seconds | Specifies the number of seconds after which the CPU line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_data_span | 7 days | Specifies the number of days worth of data to plot on the I/O line chart on the Operating System Analysis dashboard. |
| dash_os_disk_span | 7 days | Specifies the number of days worth of data to plot on the Utilisation chart on the Operating System Analysis dashboard. |
| dash_os_hostfs_timeout | 1800 seconds | Specifies the number of seconds after which the Host File System Details table is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_io_timeout | 1800 seconds | Specifies the number of seconds after which the I/O line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_memory_span | 7 days | Specifies the number of days worth of data to plot on the Memory chart on the Operating System Analysis dashboard. |
| dash_os_memory_timeout | 1800 seconds | Specifies the number of seconds after which the Memory line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_packet_span | 7 days | Specifies the number of days worth of data to plot on the Packet chart on the Operating System Analysis dashboard. |
| dash_os_packet_timeout | 1800 seconds | Specifies the number of seconds after which the Network Packets line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_process_span | 7 days | Specifies the number of days worth of data to plot on the Process chart on the Operating System Analysis dashboard. |
| dash_os_process_timeout | 1800 seconds | Specifies the number of seconds after which the Process line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_storage_timeout | 1800 seconds | Specifies the number of seconds after which the Storage pie chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_traffic_span | 7 days | Specifies the number of days worth of data to plot on the Traffic chart on the Operating System Analysis dashboard. |
| dash_os_traffic_timeout | 1800 seconds | Specifies the number of seconds after which the Traffic line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_os_util_timeout | 1800 seconds | Specifies the number of seconds after which the Utilisation line chart is auto-refreshed on the Operating System Analysis dashboard. |
| dash_probe_log_timeout | 300 seconds | Specifies the number of seconds after which the Probe Log table is auto-refreshed on the Probe Log Analysis dashboard. |
| dash_replication_archivestat_span | 7 days | Specifies the number of days worth of data to plot on the WAL Archive Status chart on the Streaming Replication Analysis dashboard. |
| dash_replication_archivestat_timeout | 1800 seconds | Specifies the number of seconds after which the WAL Archive Status line chart is auto-refreshed on the Streaming Replication dashboard. |
| dash_replication_pagelag_span | 7 days | Specifies the number of days worth of data to plot on the WAL Lag Pages chart on the Streaming Replication dashboard. |
| dash_replication_pagelag_timeout | 1800 seconds | Specifies the number of seconds after which the WAL Lag Pages line chart is auto-refreshed on the Streaming Replication dashboard. |
| dash_replication_segmentlag_span | 7 days | Specifies the number of days worth of data to plot on the WAL Lag Segments chart on the Streaming Replication dashboard. |
| dash_replication_segmentlag_timeout | 1800 seconds | Specifies the number of seconds after which the WAL Lag Segments line chart is auto-refreshed on the Streaming Replication dashboard. |
| dash_replication_timelag_span | 7 days | Specifies the number of days worth of data to plot on the Replication Lag Time chart on the Streaming Replication dashboard. |
| dash_replication_timelag_timeout | 1800 seconds | Specifies the number of seconds after which the Replication Lag Time line chart is auto-refreshed on the Streaming Replication dashboard. |
| dash_server_buffers_written | 168 hours | Specifies the number of days worth of data to plot on the Background Writer Statistics chart on the Server Analysis dashboard. |
| dash_server_buffers_written_timeout | 300 seconds | Specifies the number of seconds after which the Background Writer Statistics line chart is auto-refreshed on the Server Analysis dashboard. |
| dash_server_connovervw_timeout | 300 seconds | Specifies the number of seconds after which the Connection Overview pie chart is auto-refreshed in the Server Analysis dashboard. |
| dash_server_database_timeout | 300 seconds | Specifies the number of seconds after which the Databases table is auto-refreshed in the Server Analysis dashboard. |
| dash_server_dbsize_span | 7 days | Specifies the number of days worth of data to plot on the Database Size Analysis chart on the Server Analysis dashboard. |
| dash_server_dbsize_timeout | 1800 seconds | Specifies the number of seconds after which the Database Size line chart is auto-refreshed in the Server Analysis dashboard. |
| dash_server_disk_timeout | 1800 seconds | Specifies the number of seconds after which the Disk line chart is auto-refreshed in the Server Analysis dashboard. |
| dash_server_global_span | 7 days | Specifies the number of days worth of data to plot on the Disk line chart on the Server Analysis dashboard. |
| dash_server_sharedbuff_span | 7 days | Specifies the number of days worth of data to plot on the Shared Buffer chart on the Server Analysis dashboard. |
| dash_server_sharedbuff_timeout | 1800 seconds | Specifies the number of seconds after which the Shared Buffers line chart is auto-refreshed in the Server Analysis dashboard. |
| dash_server_tabspacesize_span | 7 days | Specifies the number of days worth of data to plot on the Tablespace Size chart on the Server Analysis dashboard. |
| dash_server_tabspacesize_timeout | 1800 seconds | Specifies the number of seconds after which the Tablespace Size line chart is auto-refreshed in the Server Analysis dashboard. |
| dash_server_useract_span | 7 days | Specifies the number of days worth of data to plot on the User Activity chart on the Server Analysis dashboard. |
| dash_server_useract_timeout | 1800 seconds | Specifies the number of seconds after which the User Activity line chart is auto-refreshed in the Server Analysis dashboard. |
| dash_sessact_lockact_timeout | 300 seconds | Specifies the number of seconds after which the Session Lock Activity table is auto-refreshed in the Session Activity Analysis dashboard. |
| dash_sessact_workload_timeout | 300 seconds | Specifies the number of seconds after which the Session Workload table is auto-refreshed in the Session Activity Analysis dashboard. |
| dash_sess_waits_nowaits_timeout | 300 seconds | Specifies the number of seconds after which the Session Waits By Number Of Waits pie chart is auto-refreshed in the Session Waits Analysis dashboard. |
| dash_sess_waits_timewait_timeout | 300 seconds | Specifies the number of seconds after which the Session Waits By Time Waited pie chart is auto-refreshed in the Session Waits Analysis dashboard. |
| dash_sess_waits_waitdtl_timeout | 300 seconds | Specifies the number of seconds after which the Session Waits Details table is auto-refreshed in the Session Waits Analysis dashboard. |
| dash_storage_dbdtls_timeout | 300 seconds | Specifies the number of seconds after which the Database Details table is auto-refreshed in the Storage Analysis dashboard. |
| dash_storage_dbovervw_timeout | 300 seconds | Specifies the number of seconds after which the Database Overview pie chart is auto-refreshed in the Storage Analysis dashboard. |
| dash_storage_hostdtls_timeout | 300 seconds | Specifies the number of seconds after which the Host Details table is auto-refreshed in the Storage Analysis dashboard. |
| dash_storage_hostovervw_timeout | 300 seconds | Specifies the number of seconds after which the Host Overview pie chart is auto-refreshed in the Storage Analysis dashboard. |
| dash_storage_tblspcdtls_timeout | 300 seconds | Specifies the number of seconds after which the Tablespace Details table is auto-refreshed in the Storage Analysis dashboard. |
| dash_storage_tblspcovervw_timeout | 300 seconds | Specifies the number of seconds after which the Tablespace Overview pie chart is auto-refreshed in the Storage Analysis dashboard. |
| dash_sys_waits_nowaits_timeout | 300 seconds | Specifies the number of seconds after which the System Waits By Number Of Waits pie chart is auto-refreshed in the System Waits Analysis dashboard. |
| dash_sys_waits_timewait_timeout | 300 seconds | Specifies the number of seconds after which the System Waits By Time Waited pie chart is auto-refreshed in the System Waits Analysis dashboard. |
| dash_sys_waits_waitdtl_timeout | 300 seconds | Specifies the number of seconds after which the System Waits Details table is auto-refreshed in the System Waits Analysis dashboard. |
| deleted_charts_retention_time | 7 days | Specifies the number of days that a custom chart (displayed on a user-defined dashboard) is stored. |
| deleted_probes_retention_time | 7 days | Specifies the number of days that a custom probe (displayed on a user-defined dashboard) is stored. |
| download_chart_format | jpeg | Specifies the format in which a downloaded chart will be stored. May be jpeg or png. |
| flapping_detection_state_change | 3 | Specifies the number of state changes detected within a specified interval to define a given alert as flapping.
|
| job_retention_time | 30 days | Specifies the number of days that non-recurring scheduled tasks and their associated logs are retained, after their execution time. |
| long_running_transaction_minutes | 5 minutes | Specifies the number of minutes a query executes for before being considered long running. |
| nagios_cmd_file_name | <file_name> | Specifies nagios command file to which passive service check result will be sent. |
| nagios_enabled | t | Specifies whether alert notification will be submitted to nagios or not. |
| nagios_medium_alert_as_critical | f | Specifies whether medium level PEM alert will be considered as critical in nagios. |
| nagios_spool_retention_time | 7 days | Specifies the number of days to retain nagios messages in the spool table before they are discarded. |
| reminder_notification_interval | 24 hours | Specifies the number of hours after which a reminder email is sent in case an alert has not been cleared. |
| server_log_retention_time | 30 days | Specifies the number of days that the server log is retained on the PEM server. |
| show_data_tab_on_graph | false | If 'true', a Data tab is added to each graph. Select the Data tab to review the data that is plotted on the graph. |
| smtp_authentication | false | Specifies whether to enable/disable authentication over SMTP. |
| smtp_enabled | true | Specifies whether to enable/disable sending of emails. |
| smtp_encryption | false | Specifies whether to send SMTP email using an encrypted connection. |
| smtp_password | Specifies the password to be used to connect to the SMTP server. | |
| smtp_port | 25 | Specifies the SMTP server port to be used for sending email. |
| smtp_server | 127.0.0.1 | Specifies the SMTP server host address to be used for sending email. |
| smtp_spool_retention_time | 7 days | Specifies the number of days to retain sent email messages in the spool table before they are discarded. |
| smtp_username | Specifies the username to be used to connect to SMTP server. | |
| snmp_community | public | Specifies the SNMP community used when sending traps. Used only with SNMPv1 and SNMPv2. |
| snmp_enabled | true | Specifies whether to enable/disable sending SNMP traps. |
| snmp_port | 162 | Specifies the SNMP server port to be used for sending SNMP traps. |
| snmp_server | 127.0.0.1 | Specifies the SNMP server host address to be used for sending SNMP traps. |
| snmp_spool_retention_time | 7 days | Specifies the number of days to retain sent traps in the spool table before they are discarded. |
| snmp_security_name | Specifies the user name or security name for sending SNMP traps. Used only with SNMPv3. | |
| snmp_security_engine_id | Specifies the Engine id of the SNMP Agent on the SNMP Server. Used only with SNMPv3. | |
| snmp_security_level | NOAUTH_NOPRIV | Specifies Security level and its possible values can be: AUTH_NOPRIV - Authentication, No Privacy AUTH_PRIV - Authentication, Privacy NOAUTH_NOPRIV - no Authentication, no Privacy. Used only with SNMPv3. |
| snmp_context_name | Specifies the Context name, the identifier for MIB objects when sending SNMP traps. Used only with SNMPv3. | |
| snmp_context_engine_id | Specifies the Context engine id, the identifier for MIB objects when sending SNMP traps. If not specified, snmp_security_engine_id will be used. Used only with SNMPv3. | |
| snmp_authentication_protocol | NONE | Specifies the authentication type for SNMP traps. Its possible values can be NONE, HMACMD5 or HMACSHA. Used only with SNMPv3. |
| snmp_privacy_protocol | NONE | Specifies the privacy protocol for SNMP traps. Its possible values can be NONE, DES, AES128, IDEA, AES192, or AES256. Used only with SNMPv3. |
| snmp_authentication_password | Specifies the authentication password associated with security name mentioned in snmp_security_name. Used only for SNMPv3. | |
| snmp_privacy_password | Specifies the privacy password associated with security name mentioned in snmp_security_name. Used only for SNMPv3. | |
| webclient_help_pg | EnterpriseDB hosted documentation | Specifies the location of the online PostgreSQL core documentation. |
+
+pem\_config\_options
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/03_log_manager.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/03_log_manager.mdx
new file mode 100644
index 00000000000..09cd7eac33d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/03_log_manager.mdx
@@ -0,0 +1,170 @@
+---
+title: "Log Manager"
+---
+
+
+
+
+Use the Log Manager wizard to specify logging preferences for a Postgres database server. Log Manager supports Advanced Server and PostgreSQL versions 9.0 (and later). The Log Manager wizard assists in modifying configuration parameters that control:
+
+- Where log files are written.
+- How often log files are written.
+- The type of information written to log files.
+- The format of log file entries.
+
+Before using Log Manager to define logging properties for a server, you must specify the name of the associated Advanced Server or PostgreSQL database server in the `Service ID` field on the `Advanced` tab of the `New Server Registration` (or `Properties`) dialog. If you do not specify the name of the service in the `Service ID` field, the server will not be made available for configuration on the `Server Selection` dialog.
+
+For example, if you are setting logging preferences for an Advanced Server 9.4 instance that resides on a Linux host, set the `Service ID` field on the `Advanced` tab of the `Properties` dialog for the monitored server to `ppas-9.4`.
+
+To run the Log Manager, select the `Log Manager` menu option from the `Management` menu of the PEM client. The wizard opens, welcoming you to the Log Manager:
+
+
+
+Click `Next` to continue to the `Server selection` dialog:
+
+
+
+The `Server selection` dialog displays a list of the server connections monitored by PEM. Check the box next to the name of a server (or servers) to which the Log Manager wizard will apply the specified configuration. Log Manager is disabled for any server displaying a red exclamation mark to the left of its name in the Server selection tree control; there are several reasons that a server may not be enabled:
+
+> - Only a server that specifies a `Service ID` on the `Advanced` tab of the `Properties` dialog can be configured by Log Manager.
+>
+> > To provide a service ID, right click on the server name in the tree control, and select `Disconnect Server` from the context menu; if prompted, provide a password. Then, open the context menu for the server, and select `Properties`. Navigate to the `Advanced` tab, and provide the name of the service in the `Service ID` field; click `Save` to save your change and exit the dialog.
+>
+> - If the PEM agent bound to the server does not have sufficient privileges to restart the server, the server will be disabled.
+> - If the PEM agent bound to the server is an older version than the associated PEM server, the server will be disabled.
+
+Click `Next` to continue:
+
+
+
+Use options within the `Import logs` box to specify how often log files will be imported to PEM.
+
+- Set the `Import logs to PEM` switch to `Yes` to specify that log files will be imported to PEM, and displayed on the Server Log Analysis dashboard.
+- Use the `Import Frequency` drop-down list box to specify how often log files are imported to PEM. This option is only enabled when the `Import logs to PEM` option is enabled. The default value is 5 minutes.
+
+Use the options in the `Log rotation configuration` box to specify the maximum length (lifespan or size) of a log file.
+
+- Use the `Rotation size` field to specify the maximum size in megabytes of an individual log file. The default value is 10 MB; when set to 0, no limit is placed on the maximum size of a log file.
+- Use the `Rotation time` field to specify the number of whole days that should be stored in each log file. The default value is 1 day.
+
+Use the `Truncate on Rotation` switch to specify server behavior for time-based log file rotation:
+
+- Select `ON` to specify that the server should overwrite any existing log file that has the same name that a new file would take.
+- Select `OFF` to specify that the server should append any new log file entries to an existing log file with the same name that a new log file would take. This is the default behavior.
+
+Click `Next` to continue to the `Where to Log` dialog:
+
+
+
+Use the fields on the `Where to Log` dialog to specify where log files should be written. Select an option from the `Log destination` box to specify a destination for the server log output:
+
+- Set the `stderr` switch to `Yes` to specify that log files should be written to `stderr`. By default, server log entries are written to `stderr`.
+- Set the `csvlog` switch to `Yes` to specify that log files should be written to file in a comma-separated value format. This option is automatically enabled (and no longer editable) if you have selected `Import logs to PEM` on the `Schedule` dialog; if you are not importing server log files to PEM, this option is editable.
+- Set the `syslog` switch to `Yes` to specify that log files should be written to the system log files.
+- On Windows, set the `eventlog` switch to `Yes` to specify that log files should be written to the event log.
+
+Use options in the `Log collection` box to specify collection preferences. Use the `Log Collector` switch to instruct the server to re-direct captured log messages (directed to STDERR) into log files:
+
+- Specify `Enable` to instruct the server to re-direct captured error messages to a log file. By default, Log Collector is enabled.
+- Specify `Disable` to instruct the server that it should not re-direct error messages to a log file.
+
+Use the `Log Silent Mode` switch to instruct the server to run silently in the background, disassociated from the controlling terminal:
+
+- Select `Enable` to instruct the server to run silently in the background.
+- Select `Disable` to instruct the server to display log file entries on the controlling terminal as each log entry is written.
+
+Use options in the Log Directory box to specify log file location preferences:
+
+- Set the `Change log directory for selected servers?` switch to `Yes` to specify that each set of log files should be maintained in a separate directory.
+- When `Log Collector` is enabled, you can use the `Directory name` field to specify the directory to which the log file will be written. By default, logs are written to the `pg_log` directory under the installation directory of the monitored server.
+
+When `Import logs to PEM` is disabled, you can use the `Log file name` field to specify the filename to which the logs will be written. The 'DEFAULT' value in the `Log File Name` field represents 'postgresql-%Y-%m-%d\_%H%M%S.log' for all the PostgreSQL servers and 'enterprisedb-%Y-%m-%d\_%H%M%S.log' for all the Postgres Plus Advanced Servers.
+
+When logging to `syslog` is enabled, you can use the `Syslog facility` drop-down list box to specify which syslog facility should be used.
+
+When logging to `syslog` is enabled, you can use the `Syslog ident` field to specify the program name that will identify Advanced Server entries in system logs.
+
+Click `Next` to continue:
+
+
+
+Use the fields on the `When to Log` dialog to specify which events will initiate a log file entry. The severity levels (in order of severity, from most severe to least severe) are:
+
+| | |
+|-----------------------|------------------------------------------------------------------------------------|
+| Severity | Description |
+| panic | Errors that cause all database sessions to abort. |
+| fatal | Errors that cause a session to abort. |
+| log | Information messages of interest to administrators. |
+| error | Errors that cause a command to abort. |
+| warning | Error conditions in which a command will complete but may not perform as expected. |
+| notice | Items of interest to users. This is the default. |
+| info | Information implicitly requested by the user. |
+| debug5 through debug1 | Detailed debugging information useful to developers |
+
+- Use the `Client min messages` drop-down list box to specify the minimum severity level that will be sent to the client application. The default value is `notice`.
+- Use the `Log min messages` drop-down list box to specify the minimum severity level that will be written to the server log. The default value is `warning`.
+- By default, when an error message is written to the server log, the text of the SQL statement that initiated the log entry is not included. Use the `Log min error statement` drop-down list box to specify a severity level that will trigger SQL statement logging. If a message is of the specified severity or higher, the SQL statement that produced the message will be written to the server log. The default value is `error`.
+- Use the `Log min duration statement` field to specify a statement duration (in milliseconds); any statements that exceed the specified number of milliseconds will be written to the server log. The length of time that it took for the statement to execute will be included in the log entry. A value of -1 disables all duration-based logging; a value of 0 logs all statements and their duration. The default value is `-1`.
+- Use the `Log temp files` field to specify a file size in kilobytes; when a temporary file reaches the specified size, it will be logged. The default value is `-1`.
+- Use the `Log autoVacuum min duration` field to specify a time length in milliseconds; if auto-vacuuming exceeds the length of time specified, the activity will be logged. The default value is `-1`.
+
+Click `Next` to continue to the `What to log` dialog:
+
+
+
+Use the fields on the `What to log` dialog to specify log entry options that are useful for debugging and auditing.
+
+The switches in the `Debug options` box instruct the server to include information in the log files related to query execution that may be of interest to a developer:
+
+- Set the `Parse tree` switch to `Yes` to instruct the server to include the parse tree in the log file. The default value is `No`.
+- Set the `Rewriter output` switch to `Yes` to instruct the server to include query rewriter output in the log file. The default value is `No`.
+- Set the `Execution plan` switch to `Yes` to instruct the server to include the execution plan for each executed query in the log file. The default value is `No`.
+
+By default, `Indent Debug Options Output in Log` option is set to `No`. When this option is enabled, the server indents each line that contains a parse tree entry, a query rewriter entry or query execution plan entry. While indentation makes the resulting log file more readable, it results in a longer log file. To enable indentation of log file entries related to debugging, move the switch to `Yes`.
+
+Use the switches in the `General options` box to instruct the server to include auditing information in the log file:
+
+- Set the `Checkpoints` switch to `Yes` to include checkpoints and restartpoints in the server log. By default, this is set to `No`.
+
+- Set the `Connections` switch to `Yes` to include each attempted connection to the server (as well as successfully authenticated connections) in the server log. By default, this is set to `No`.
+
+- Set the `Disconnections` switch to `Yes` to include a server log entry for each terminated session that provides the session information and session duration. By default, this is set to `No`.
+
+- Set the `Duration` switch to `Yes` to include the amount of time required to execute each logged statement in the server log. By default, this is set to `No`.
+
+- Set the `Hostname` switch to `Yes` to include both the IP address and host name in each server log entry (by default, only the IP address is logged). Please note that this may cause a performance penalty. By default, this is set to `No`.
+
+- Set the `Lock Waits` switch to `Yes` to instruct the server to write a log entry for any session that waits longer than the time specified in the `deadlock_timeout` parameter to acquire a lock. This is useful when trying to determine if lock waits are the cause of poor performance. By default, this is set to `No`.
+
+- Use the `Error verbosity` drop-down list box to specify the detail written to each entry in the server log.
+
+ > - Select `default` to include the error message, DETAIL, HINT, QUERY and CONTEXT in each server log entry.
+ > - Select `terse` to log only the error message, excluding the DETAIL, HINT, QUERY and CONTEXT information from each server log entry.
+ > - Select `verbose` to include the error message, the DETAIL, HINT, QUERY and CONTEXT error information, SQLSTATE error code and source code file name, the function name, and the line number that generated the error.
+
+- Use the `Prefix string` field to specify a printf-style string that is written at the beginning of each log file entry. The `Escape` characters in the following table represent the information described in the `Information` column. Some information is available to `Session` processes only; `Helper` processes can provide all of the information specified in the `Prefix String`. The default value is %t (timestamp without milliseconds).
+
+You can include:
+
+| Escape | Information | Session/Helper |
| Application Name | Session |
| User Name | Session |
| Database Name | Session |
| Remote host name or IP address, and remote port | Session |
| Remote host name or IP address | Session |
| Process ID | Helper |
| Time stamp without milliseconds | Helper |
| Time stamp with milliseconds | Helper |
| %i | Command tag: type of statement that generated the log entry | Session |
| SQLSTATE error code | Helper |
| Session identifier | Helper |
| Line number of the log entry | Helper |
| Process start time stamp | Helper |
| Virtual transaction ID (backendID/localXID) | Helper |
| Transaction ID (0 if not assigned) | Helper |
| %q | Produces no output, but instructs non-session processes to stop at this point in the string; will be ignored by session processes | Helper |
| Literal % | Helper |
| Section Heading |
|
| Trigger |
|
| Recommended Value |
|
| Description |
|
| Current Values |
|
+
+pe\_schema\_config\_expert\_recommendations pe\_security\_expert\_recommendations pe\_configuration\_expert\_recommendations
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/01_capacity_manager_metrics.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/01_capacity_manager_metrics.mdx
new file mode 100644
index 00000000000..5352595cd57
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/01_capacity_manager_metrics.mdx
@@ -0,0 +1,27 @@
+---
+title: "Tab 1 (Metrics)"
+---
+
+
+
+
+To create a Capacity Manager report, expand the tree control on the `Metrics` tab to locate the metrics that are available for the node that you wish to analyze.
+
+
+
+To include a metric in the Capacity Manager report, check the box to the left of the name of the metric on the `Metrics` tab.
+
+
+
+Capacity Manager will use the aggregation method specified by the `Aggregation` drop-down listbox (located at the bottom of the `Metrics` tab). The aggregation method instructs Capacity Manager how to evaluate and plot the metric values. Select from:
+
+- **Average:** Use the average of the values recorded during the time period.
+- **Maximum:** Use the maximum value recorded during the time period.
+- **Minimum:** Use the minimum value recorded during the time period.
+- **First:** Use the first value recorded during the time period.
+
+To remove a metric from the Capacity Manager report, uncheck the box to the left of the name of a metric.
+
+Move the slider next to `Graph/chart metrics individually?` to `Yes` to instruct Capacity Manager to produce a separate report for each metric selected on the `Metrics` tab. If the option is set to `No`, all selected metrics will be merged into a single graph or table.
+
+Click the `Generate` button to display the report onscreen (accepting the default configuration options), or continue to the [Options](../../04_toc_pem_features/08_capacity_manager/#capacity_manager_options) tab to specify sampling boundaries, report type and report destination.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/02_capacity_manager_options.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/02_capacity_manager_options.mdx
new file mode 100644
index 00000000000..4f0fb9c5a1f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/02_capacity_manager_options.mdx
@@ -0,0 +1,54 @@
+---
+title: "Tab 2 (Options)"
+---
+
+
+
+
+Use the fields on the `Options` tab to specify the starting and ending boundaries of the Capacity Manager report, the type of report generated, and the location to which the report will be displayed or written.
+
+
+
+Use the fields within the `Time Period` box to define the boundaries of the Capacity Manager report:
+
+- Use the `Period` drop-down listbox to select the type of time period you wish to use for the report. You can select:
+
+| Value | Description |
+|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Start time and end time | Specify a start and end date and time for the report. |
+| Start time and threshold | Specify a start date and time, and a threshold to determine the end time and date for the report. |
+| Historical days and extrapolated days | Specify a start date for the report that is a number of days in the past, and an end date that is a number of days in the future. This option is useful for report templates that do not specify fixed dates. |
+| Historical days and threshold | Specify a start date that is a number of days in the past, and end it when a threshold value is reached. |
+
+After specifying the type of time period for the report, select from other options in the `Time Period` box to refine the time period:
+
+- Use the date and time selectors next to the `Start time` field to specify the starting date and time of the sampling period, or select the number of `Historical day(s)` of data to include in the report. By default, Capacity Manager will select a start time that is one week prior to the current date and time. The date and time specified in the `Start time` field must not be later than the current date/time.
+- Use the date and time selectors next to the `End time` field to specify an end boundary for the report, or select the number of `Extrapolated day(s)` of data to include in the report. The end boundary can be either a time, a number of days in the future, or the point at which a selected metric reaches a user-specified threshold value. The time specified in the `End time` field must be later than the time specified in the `Start time` field.
+
+> Note that if you select an end date and time in the future, Capacity Manager will use historical usage information to extrapolate anticipated future usage. Since the projected usage is based on the sampling of historical data, the accuracy of the future usage trend will improve with a longer sampling period.
+>
+> To specify a threshold value, use the drop-down listbox in the `Threshold` field to select a metric (from the metrics specified on the `Metrics` tab), an operator (`Exceeds` or `Falls below`), and to enter a target value for the metric. If you choose to define the end of the report using a threshold, the Capacity Manager report will terminate when the value for the selected metric exceeds or falls below the specified value.
+>
+> **Please Note:** If you specify a starting boundary that is later than the ending boundary for the report, the status bar will display an error informing you that you must enter a valid time.
+
+The cm\_max\_end\_date\_in\_years <pem\_config\_options> configuration parameter defines a default time value for the end boundary of Capacity Manager reports. If you specify a threshold value as the end boundary of a report, and the anticipated usage of the boundary is not met before the maximum time has passed (as specified in the `cm_max_date_in_years` parameter), the report will terminate at the time specified by the `cm_max_date_in_years` parameter. By default, `cm_max_end_date_in_years` is 5; use the `` `Server Configuration `` dialog <pem\_server\_config> to modify the value of cm\_max\_end\_date\_in\_years\`.
+
+**Please Note:** The PEM client will display time in the PEM client's timezone, rather than the timezone in which the PEM server resides.
+
+Use the fields in the `Report` box to specify the report type and destination.
+
+The radio buttons next to `Include on report` specify the type of report produced by Capacity Manager. Choose from:
+
+> - Select `Graph` to instruct Capacity Manager to display the report in the form of a line graph in the PEM client window.
+> - Select `Table of data` to instruct Capacity Manager to display a table containing the report data in the PEM client window.
+> - Select `Graph and table of data` to instruct Capacity Manager to display both a line graph and a data table in the PEM client window.
+
+Use the `Report destination` radio buttons to instruct Capacity Manager where to display or save the report:
+
+> - Select `New tab` to instruct Capacity Manager to display the report on a new tab in the PEM client. You must select `New tab` to display the first generation of a Capacity Manager report; for subsequent reports, you may select `Previous` tab.
+> - Select `Previous` tab to instruct Capacity Manager to re-use a previously opened tab when displaying the report.
+> - Select `Download the report as a file` and specify a file name to instruct Capacity Manager to write the report to the specified file.
+
+Reports saved to file are stored in HTML format. You can review Capacity Manager reports with any web browser that supports Scalable Vector Graphics (SVG). Browsers that do not support SVG will be unable to display Capacity Manager graphs and may include unwanted characters.
+
+When you have specified the report boundaries and selected the type and destination of the Capacity Manager report, click the `Generate` button to create the report.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/index.mdx
new file mode 100644
index 00000000000..7a68be69371
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/08_capacity_manager/index.mdx
@@ -0,0 +1,170 @@
+---
+title: "Capacity Manager"
+---
+
+
+
+
+PEM's Capacity Manager analyzes collected statistics (metrics) to generate a graph or table that displays the historical usage statistics of an object, and can project the anticipated usage statistics for an object. You can configure Capacity Manager to collect and analyze metrics for a specific:
+
+- Host/operating system
+- EDB Postgres Advanced Server or PostgreSQL server
+- Database
+- Database object (table, index, function etc).
+
+You can tailor the content of the Capacity Manager report by choosing a specific metric (or metrics) to include in the report, the time range over which the metrics were gathered, and a high or low threshold for the metrics analyzed. You can also specify a start and end date for the Capacity Manager report. If the end date of the report specifies a time in the future, Capacity Manager will analyze the `historical` usage of the selected object to extrapolate the `projected` object usage in the future.
+
+To open Capacity Manager, select the `Capacity Manager...` option from the `Management` menu in the PEM client window; the `Capacity Manager` wizard opens, displaying a tree control on the `Metrics` tab.
+
+
+
+Expand the tree control on the [Metrics](../04_toc_pem_features/08_capacity_manager/#capacity_manager_metrics) tab to select the metrics that will be included in the Capacity Manager report.
+
+When defining report options, you can specify an `aggregation` method for each selected metric. The aggregation method determines how Capacity Manager will analyze the data points within the sampling period to reduce the data to a more visually meaningful quantity within a report (if required). The aggregation method can instruct Capacity Manager to compute an average of the data within a time period, the high or low value, or the first sampled value.
+
+Use the [Options](../04_toc_pem_features/08_capacity_manager/#capacity_manager_options) tab to specify additional report details.
+
+When defining the boundaries of a Capacity Manager report, specify the starting date and time, and an end boundary. The end boundary can be a point in time or a threshold boundary (when the data meets a specified criteria). If the sample contains more data points than the number of points specified by the cm\_data\_points\_per\_report <pem\_config\_options> configuration parameter, Capacity Manager applies the aggregation method to calculate a reduced number of graph points for the report.
+
+## Report Templates
+
+You can save a report definition as a template for future reports. Capacity Manager report templates may be accessed by all PEM users. To save a report definition as a template:
+
+1. Use the `Metrics` and `Options` tabs to define your report.
+2. Click the `Save` button to open the `Save Template` dialog.
+3. Provide a report name in the Title field, select a location to store the template in the tree control.
+4. Click `OK`.
+
+When creating a report, you can use the `Load Template` button to browse and open an existing template. Once opened, the report definition may be modified if required, and optionally saved again, either as a new template, or overwriting the original template. Use the `Manage Templates` button open a dialog that allows you to rename or remove unwanted templates.
+
+## Available Metrics
+
+Please Note that the available metrics will vary by platform, and are subject to change. The available metrics may include the metrics described in the table below:
+
+| Metric Name | Description |
+|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| \# Dead Tuples | The number of dead tuples in the selected table. |
+| \# Dead Tuples+ | The cumulative number of dead tuples in the selected table. |
+| \# Heap Tuples Fetched by Index Scans | The number of heap tuples fetched by index scans. |
+| \# Heap Tuples Fetched by Index Scans+ | The cumulative number of heap tuples fetched by index scans. |
+| \# Idle Backends+ | The cumulative number of currently idle backend clients. |
+| \# Index Scans | The number of index scans performed on the specified object. |
+| \# Index Scans+ | The cumulative number of index scans performed on the specified object. |
+| \# Index Tuples Read | The number of index tuples read. |
+| \# Index Tuples Read+ | The cumulative number of index tuples read. |
+| \# Live Tuples | The number of tuples visible to transactions. |
+| \# Live Tuples+ | The cumulative number of tuples visible to transactions. |
+| \# Pages Estimated by ANALYZE | The number of pages estimated by ANALYZE. |
+| \# Pages Estimated by ANALYZE+ | The cumulative number of pages estimated by ANALYZE. |
+| \# Sequential Scans | The number of sequential scans performed on the specific table. |
+| \# Sequential Scans+ | The cumulative number of sequential scans performed on the specific table. |
+| \# Sequential Scan Tuples | The number of tuples sequentially scanned in the specific table. |
+| \# Sequential Scan Tuples+ | The cumulative number of tuples sequentially scanned in the specific table. |
+| \# Tuples Deleted | The number of tuples deleted. |
+| \# Tuples Deleted+ | The cumulative number of tuples deleted. |
+| \# Tuples Estimated by ANALYZE | The number of live (visible) tuples estimated by ANALYZE. |
+| \# Tuples Estimated by ANALYZE+ | The cumulative number of live tuples estimated by ANALYZE. |
+| \# Tuples HOT Updated | The number of tuples HOT updated. In a HOT update, the new tuple resides in the same block as the original tuple and the tuples share an index entry. |
+| \# Tuples HOT Updated+ | The cumulative number of tuples HOT updated. |
+| \# Tuples Inserted | The number of tuples inserted into the specified table. |
+| \# Tuples Inserted+ | The cumulative number of tuples inserted into the specified table. |
+| \# Tuples Updated | The number of tuples updated in the selected table. |
+| \# Tuples Updated+ | The cumulative number of tuples updated in the selected table. |
+| Blocks Hit | The number of blocks found in the cache. |
+| Blocks Hit+ | The cumulative number of blocks found in the cache. |
+| Blocks Read | The number of blocks read. |
+| Blocks Read+ | The cumulative number of blocks read. |
+| Blocks Read from InfiniteCache | The number of blocks read from InfiniteCache. |
+| Blocks Read from InfiniteCache+ | The cumulative number of blocks read from InfiniteCache. |
+| Blocks Written | The number of blocks written. |
+| Blocks Written+ | The cumulative number of blocks written. |
+| Buffers Allocated | The number of buffers allocated. |
+| Buffers Allocated+ | The cumulative number of buffers allocated. |
+| Buffers Written - Backends | The number of buffer blocks written to disk by server processes (processes connected to a client application). |
+| Buffers Written - Backends+ | The cumulative number of buffer blocks written to disk by server processes. |
+| Buffers Written - Checkpoint | The number of blocks written to disk by the checkpoint process. |
+| Buffers Written - Checkpoint+ | The cumulative number of blocks written to disk by the checkpoint process. |
+| Buffers Written - Cleaning Scan | The number of blocks written to disk by the autovacuum process. |
+| Buffers Written - Cleaning Scan+ | The cumulative number of blocks written to disk by the autovacuum process. |
+| Bytes Received (KB) | The number of bytes received from the client (in kilobytes). |
+| Bytes Received (KB)+ | The cumulative number of bytes received (in kilobytes). |
+| Bytes Sent (KB) | The number of bytes sent to the client (in kilobytes). |
+| Bytes Sent (KB)+ | The cumulative number of bytes sent (in kilobytes). |
+| Checkpoints - Timed | The number of checkpoint operations triggered by the checkpoint interval. |
+| Checkpoints - Timed+ | The cumulative number of checkpoint operations triggered by the checkpoint interval. |
+| Checkpoints - Untimed | The number of checkpoint operations triggered by checkpoint size. |
+| Checkpoints - Untimed+ | The cumulative number of checkpoint operations triggered by checkpoint size. |
+| Database Size (MB) | The size of the specified database (in megabytes). |
+| Free RAM Memory | The amount of free RAM memory (in megabytes). |
+| Free Swap Memory | The amount of free swap space on disk (in megabytes). |
+| Heap Blocks Hit | The number of heap blocks found in the cache. |
+| Heap Blocks Hit+ | The cumulative number of heap blocks found in the cache. |
+| Heap Blocks Read | The number of heap blocks read. |
+| Heap Blocks Read+ | The cumulative number of heap blocks read. |
+| Index Blocks Hit | The number of index blocks found in the cache. |
+| Index Blocks Hit+ | The cumulative number of index blocks found in the cache. |
+| Index Blocks Read | The number of index blocks read. |
+| Index Blocks Read+ | The cumulative number of index blocks read. |
+| Index Size (MB) | The size of the specified index (in megabytes). |
+| In Packets Discards | The number of inbound packets discarded. |
+| In Packets Discards+ | The cumulative number of inbound packets discarded. |
+| In Packets Errors | The number of inbound packets that contain errors. |
+| In Packets Errors+ | The cumulative number of inbound packets that contain errors. |
+| Link Bandwidth (Mbit/s) | The speed of the network adapter (in megabits per second). |
+| Load Average - 15 Minute | CPU saturation (in percent) - 15 minute sampling average. |
+| Load Average - 1 Minute | CPU saturation (in percent) - 1 minute sampling average. |
+| Load Average - 5 Minute | CPU saturation (in percent) - 5 minute sampling average. |
+| Load Percentage | CPU saturation in percent. |
+| Number of Prepared Transactions+ | The cumulative number of prepared transactions. |
+| Number of WAL Files+ | The cumulative number of write-ahead log files. |
+| Out Packets Discards | The number of outbound packets discarded. |
+| Out Packets Discards+ | The cumulative number of outbound packets discarded. |
+| Out Packets Errors | The number of outbound packets that contain errors. |
+| Out Packets Errors+ | The cumulative number of outbound packets that contain errors. |
+| Packets Received | The number of packets received. |
+| Packets Received+ | The cumulative number of packets received. |
+| Packets Sent | The number of packets sent. |
+| Packets Sent+ | The cumulative number of packets sent. |
+| Size (MB) | The total size of the disk (in megabytes). |
+| Size of Indexes (MB) | The size of indexes on the specified table (in megabytes). |
+| Space Available (MB) | The current disk space available (in megabytes). |
+| Space Used (MB) | The current disk space used (in megabytes). |
+| Table Size (MB) | The size of the specified table (in megabytes). |
+| Tablespace Size (MB) | The size of the specified tablespace (in megabytes). |
+| Temp Buffers (MB) | The size of temporary buffers (in megabytes). |
+| Toast Blocks Hit | The number of TOAST blocks found in the cache. |
+| Toast Blocks Hit+ | The cumulative number of TOAST blocks found in the cache. |
+| Toast Blocks Read | The number of TOAST blocks read. |
+| Toast Blocks Read+ | The cumulative number of TOAST blocks read. |
+| Total RAM Memory | The total amount of RAM memory on the system (in megabytes). |
+| Total Swap Memory | The total amount of swap space on the system (in megabytes). |
+| Total Table Size w/Indexes and Toast | The total size of the specified table (including indexes and associated oversized attributes). |
+| Transactions Aborted | The number of aborted transactions. |
+| Transactions Aborted+ | The cumulative number of aborted transactions. |
+| Transactions Committed | The number of committed transactions. |
+| Transactions Committed+ | The cumulative number of committed transactions. |
+| Tuples Deleted | The number of tuples deleted from the specified table. |
+| Tuples Deleted+ | The cumulative number of tuples deleted from the specified table. |
+| Tuples Estimated by ANALYZE | The number of visible tuples in the specified table. |
+| Tuples Estimated by ANALYZE+ | The cumulative number of visible tuples in the specified table. |
+| Tuples Fetched | The number of tuples fetched from the specified table. |
+| Tuples Fetched+ | The cumulative number of tuples fetched from the specified table. |
+| Tuples HOT Updated | The number of tuples HOT updated. In a HOT update, the new tuple resides in the same block as the original tuple and the tuples share an index entry. |
+| Tuples HOT Updated+ | The cumulative number of tuples HOT updated. In a HOT update, the new tuple resides in the same block as the original tuple and the tuples share an index entry. |
+| Tuples Inserted | The number of tuples inserted into the specified table. |
+| Tuples Inserted+ | The cumulative number of tuples inserted into the specified table. |
+| Tuples Returned | The number of tuples returned in result sets. |
+| Tuples Returned+ | The cumulative number of tuples returned in result sets. |
+| Tuples Updated | The number of tuples updated in the specified table. |
+| Tuples Updated+ | The cumulative number of tuples updated in the specified table. |
+| WAL Segment Size (MB) | The segment size of the write-ahead log (in megabytes). |
+
+**Note:** The '+' following the name of a metric signifies that the data for the metric is gathered cumulatively; those metrics that are not followed by the '+' sign are collected as a 'point-in-time' value.
+
+Contents:
+
+
+
+capacity\_manager\_metrics capacity\_manager\_options
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/01_pem_alerting_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/01_pem_alerting_dialog.mdx
new file mode 100644
index 00000000000..a95bcc94582
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/01_pem_alerting_dialog.mdx
@@ -0,0 +1,207 @@
+---
+title: "Creating and Managing Alerts"
+---
+
+
+
+
+Use options accessed through the `Manage Alerts` tab to create, copy, or modify an alert. To open the `Manage Alerts` tab, select `Manage Alerts...` from the PEM client's `Management` menu.
+
+
+
+Use the `Quick Links` toolbar to open dialogs and tabs that you can use to manage alerts and alerting behavior:
+
+> - Select `Copy Alerts` to open the [Copy Alert Configuration](../../04_toc_pem_features/09_pem_alerting/#pem_alert_copy) dialog and copy an alert definition.
+> - Select `Alert Templates` to open the [Alert Template](../../04_toc_pem_features/09_pem_alerting/#pem_custom_alert_templates) tab, and create or modify an alert template.
+> - Select `Email Groups` to open the [Email Groups](../../04_toc_pem_features/09_pem_alerting/#pem_email_groups) tab, and manage or create an email group.
+> - Select `Webhooks` to open the [Webhooks](../../04_toc_pem_features/09_pem_alerting/#pem_webhooks) tab, and manage or create a webhook endpoint.
+> - Select `Server Configuration` to open the [server configuration](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog and review or modify server configuration settings.
+> - Select `Help` to open the PEM online help.
+
+The `Alerts` table displays the alerts that are defined for the item currently highlighted in the PEM client tree control. You can use the `Alerts` table to modify an existing alert, or to create a new alert.
+
+## Creating a New Alert
+
+To open the alert definition dialog and create a new alert, click the `Add` icon (+) in the upper-right corner of the table.
+
+
+
+Use the fields on the `General` tab to provide information about the alert:
+
+- Enter the name of the alert in the `Name` field.
+- Use the drop-down listbox in the `Template` field to select a template for the alert. An alert template is a function that uses one (or more) metrics or parameters to generate a value to which PEM compares user-specified alert boundaries. If the value returned by the template function evaluates to a value that is within the boundary of a user-defined alert (as specified by the `Operator` and `Threshold values` fields), PEM raises an alert, adds a notice to the `Alerts overview` display, and performs any actions specified on the template.
+- Use the `Enable?` switch to specify if the alert is enabled (`Yes`) or disabled (`No`).
+- Use the controls in the `Interval` box to specify how often the alert should confirm if the alert conditions are satisfied. Use the `Minutes` selector to specify an interval value. Use the `Default` switch to set or reset the `Minutes` value to the default (recommended) value for the selected template.
+- Use controls in the `History retention` box to specify the number of days that PEM will store data collected by the alert. Use the `Days` selector to specify the number of days that the data will be stored. Use the `Default` switch to set or reset the `Days` value to the default value (30 days).
+- Use controls in the `Threshold values` box to define the triggering criteria for the alert. When the value specified in the `Threshold Values` fields evaluates to greater-than or less-than the system value (as specified with the `Operator`), PEM will raise a `Low`, `Medium` or `High` level alert:
+
+> - Use the `Operator` drop-down listbox to select the operator that PEM will use when evaluating the current system values.
+> - Select a greater-than sign (>) to indicate that the alert should be triggered when the system values are greater than the values entered in the `Threshold values` fields.
+> - Select a less-than sign (<) to indicate that the alert should be triggered when the system values are less than the values entered in the `Threshold values` fields.
+> - Use the threshold fields to specify the values that PEM will compare to the system values to determine if an alert should be raised. Please note that you must specify values for all three thresholds (`Low`, `Medium`, and `High`):
+> - Enter a value that will trigger a low-severity alert in the `Low` field.
+> - Enter a value that will trigger a medium-severity alert in the `Medium` field.
+> - Enter a value that will trigger a high-severity alert in the `High` field.
+
+The `Parameter Options` table contains a list of parameters that are required by the selected template; the table displays both pre-defined parameters, and parameters for which you must specify a value. Please note that you must specify a value for any parameter that displays a prompt in the `Value` column.
+
+Use the `Notification` tab to specify how PEM will behave if an alert is raised.
+
+
+
+PEM can send a notification or execute a script if an alert is triggered, or if an alert is cleared.
+
+Use the fields in the `Email` tab to specify the email group that will receive an email notification if the alert is triggered at the specified level. Use the [Email Groups](../../04_toc_pem_features/09_pem_alerting/#pem_email_groups) tab to create an email group that contains the address of the user or users that will be notified when an alert is triggered. To access the `Email Groups` tab, click the `Email Groups` icon located in the `Quick Links` menu of the `Manage Alerts` tab.
+
+To instruct PEM to send an email when a specific alert level is reached, set the slider next to an alert level to `Yes`, and use the drop-down listbox to select the pre-defined user or group that will be notified.
+
+Please note that you must [configure the PEM Server](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) to use an SMTP server to deliver email before PEM can send email notifications.
+
+
+
+Use the fields in the `Webhook` tab to specify the webhook endpoints that will receive a notification if the alert is triggered at the specified level. Use the [Webhooks](../../04_toc_pem_features/09_pem_alerting/#pem_webhooks) tab to create an endpoint that contains the details of URL that will be notified when an alert is triggered along with other details like payload. To access the `Webhooks` tab, click the `Webhooks` icon located in `Quick Links` menu of the `Manage Alerts` tab.
+
+By default `Webhook` notifications will be sent to created endpoints according to their default settings. To disable the `Webhook` set the slider next to `Enable` field to `No`.
+
+Also to override default settings set the slider next to `Override default configuration?` to `Yes`, and use the drop-down listbox to select the pre-defined endpoints.
+
+
+
+Use the `Trap notification` options to configure trap notifications for this alert:
+
+- Set the `Send trap` slider to `Yes` to send SNMP trap notifications when the state of this alert changes.
+- Set the `SNMP Ver` to `v1`, `v2`, or `v3` to identify the SNMP version.
+- Use the `Low alert`, `Med alert` and `High alert` sliders to select the level(s) of alert that will trigger the trap. For example, if you set the slider next to `High alert` to `Yes`, PEM will send a notification when an alert with a high severity level is triggered.
+
+Please note that you must [configure the PEM Server](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) to send notifications to an SNMP trap/notification receiver before notifications can be sent. For sending SNMP v3 traps, pemAgent will use 'User Security Model(USM)' which is in charge of authenticating, encrypting, and decrypting SNMP packets.
+
+Also note while sending SNMP v3 traps, agent will create snmp\_boot\_counter file. This file will get created in location mentioned by batch\_script\_dir parameter in agent.cfg, if this parameter is not configured or if directory is not accessible due to authentication restrictions then in operating systems temporary directory, if that is also not possible then in user’s home directory.
+
+Please see How SNMP traps are formed? <snmp\_trap\_details>
+
+
+
+Use the field in the `Nagios notification` box to instruct the PEM server to notify Nagios network-alerting software when the alert is triggered or cleared. For detailed information about configuring and using Nagios with PEM, please see [Using PEM with Nagios](../../04_toc_pem_features/09_pem_alerting/#using_pem_with_nagios).
+
+- Set the `Submit passive service check result to Nagios` switch to `Yes` to instruct the PEM server to notify Nagios when the alert is triggered or cleared.
+
+
+
+Use the fields in the `Script execution` tab to (optionally) define a script that will be executed if an alert is triggered, and to specify details about the script execution.
+
+- Set the `Execute script` slider to `Yes` to instruct PEM to execute the provided script if an alert is triggered.
+- Set the `Execute on alert cleared` slider to `Yes` to instruct PEM to execute the provided script when the situation that triggered the alert has been resolved.
+- Use the radio buttons next to `Execute script on` to indicate that the script should execute on the `PEM Server` or the `Monitored Server`.
+- Provide the script that PEM should execute in the `Code` field. You can provide a batch/shell script, or SQL code. Within the script, you can use placeholders for the following:
+ - `%AlertID%` - this placeholder will be replaced with the id of the triggered alert.
+ - `%AlertName%` - this placeholder will be replaced with the name of the triggered alert.
+ - `%ObjectName%` - this placeholder will be replaced with the name of the server or agent on which the alert was triggered.
+ - `%ObjectType%` - this placeholder will be replaced with the type of the object on which the alert was triggered.
+ - `%ThresholdValue%` - this placeholder will be replaced with the threshold value reached by the metric when the alert triggered.
+ - `%CurrentValue%` - this placeholder will be replaced with the current value of the metric that triggered the alert.
+ - `%CurrentState%` - this placeholder will be replaced with the current state of the alert.
+ - `%OldState%` - this placeholder will be replaced with the previous state of the alert.
+ - `%AlertRaisedTime%` - this placeholder will be replaced with the time that the alert was raised, or the most recent time that the alert state was changed.
+ - `%AgentID%` - this placeholder will be replaced with the id of the agent by which alert was generated.
+ - `%AgentName%` - this placeholder will be replaced with the name of the agent by which alert was generated.
+ - `%ServerID%` - this placeholder will be replaced with the id of the server on which alert was generated.
+ - `%ServerName%` - this placeholder will be replaced with the name of the server on which alert was generated.
+ - `%ServerIP%` - this placeholder will be replaced with the IP or address of the server on which alert was generated.
+ - `%ServerPort%` - this placeholder will be replaced with the port of the server on which alert was generated.
+ - `%DatabaseName%` - this placeholder will be replaced with the name of the database on which alert was generated.
+ - `%SchemaName%` - this placeholder will be replaced with the name of the schema on which alert was generated.
+ - `%PackageName%` - this placeholder will be replaced with the name of the package on which alert was generated.
+ - `%DatabaseObjectName%` - this placeholder will be replaced with the name of the database object on which alert was generated.
+ - `%Parameters%` - this placeholder will be replaced with the list of custom parameters used to generate the alert.
+ - `%AlertInfo%` - this placeholder will be replaced with the detailed database object level information of the alert.
+
+When you have defined the alert attributes, click the edit icon to close the alert definition editor, and then the save icon (in the upper-right corner of the `Alerts` table). To discard your changes, click the refresh icon; a popup will ask you to confirm that you wish to discard the changes.
+
+
+
+/script.sh "%AlertName% %AlertLevel% %AlertDetails%"
+ > ```
+
+- You can define the environment variables for any of the placeholders and then use those environment variables in the script.
+
+ For eg:
+
+ > ``` bash
+ > #!/bin/bash
+ >
+ > export AlertName=%AlertName%
+ > export AlertState=%AlertState%
+ >
+ > bash /script.sh
+ > ```
+
+
+
+## Modifying an Existing Alert
+
+Use the `Alerts` table to manage an existing alert or create a new alert. Highlight an object in the PEM client tree control to view the alerts that monitor that object.
+
+
+
+You can modify some properties of an existing alert in the `Alerts` table:
+
+> - The `Name` column displays the name of the alert; to change the alert name, simply replace the name in the table, and click the save icon.
+> - The `Auto created?` column indicates if the alert definition was automatically created; `Yes` indicates that the alert was created by PEM, and `No` indicates that the alert was manually created.
+> - The `Template` column displays the name of the alert template that specifies properties used by the alert. You can use the drop-down listbox to change the alert template associated with an alert.
+> - Use the `Enable?` switch to specify if an alert is enabled (Yes) or disabled (No).
+> - Use the `Interval` column to specify how often PEM should check to see if the alert conditions are satisfied. Set the `Default` switch to `No` and specify an alternate value (in `Minutes`), or return the `Default` switch to `Yes` to reset the value to its default setting. By default, PEM will check the status of each alert once every minute.
+> - Use the `History retention` field to specify the number of days that PEM will store data collected by the alert. Set the `Default` switch to `No` and specify an alternate value (in `Days`), or return the `Default` switch to `Yes` to reset the value to its default setting. By default, PEM will recommend storing historical data for 30 days.
+
+Click the `Edit` icon to the left of an alert name to open the `Alert details` editor and access the complete alert definition. After modifying an alert in the editor, click the `Save` button to make your changes persistent.
+
+## Deleting an Alert
+
+To mark an alert for deletion, highlight the alert name in the `Alerts` table and click the delete icon to the left of the name; the alert will remain in the list, but in red strike-through font.
+
+
+
+The delete icon acts as a toggle; you can undo the deletion by clicking the delete icon a second time; when you click the Save icon, the alert definition will be permanently deleted.
+
+## Example
+
+The screen shown below defines an alert (named System Usage High) that monitors the committed transactions on the system:
+
+
+
+To re-create this example, highlight the name of a PEM Agent in the tree-control, and select `Manage Alerts...` from the PEM client `Management` menu. When the `Manage Alerts` tab opens, click the add icon (+) in the upper-right hand corner of the `Alerts` table to open the alert editor.
+
+Fields on the `General` tab instruct PEM to use the Disk busy percentage template to create the alert. The PEM server will check the free memory available once every minute, and:
+
+- Trigger a low-severity alert if the free memory available drops below 20%
+- Trigger a medium-severity alert if the free memory available drops below 10%
+- Trigger a high-severity alert if the free memory available drops below 5%
+
+
+
+
+
+Fields on the `Notifications` tab instruct PEM to:
+
+- Send an email notification to the `administrator` email group.
+- Submit a passive service check result to Nagios.
+- Execute the script shown in the `Code` field when the alert is triggered.
+
+> - To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of agent.cfg file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. If pemagent is being run by a non-root user then the value of `batch_script_user` will be ignored and the script will be executed by the same non-root user that is being used for running the pemagent.
+> - To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in HKEY\_LOCAL\_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent.
+
+Click the edit icon to close the editor and add the example to the `Alert List`; click the save icon before closing the `Manage Alerts` tab to save your work.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/02_pem_alert_copy.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/02_pem_alert_copy.mdx
new file mode 100644
index 00000000000..6c06bea3b62
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/02_pem_alert_copy.mdx
@@ -0,0 +1,20 @@
+---
+title: "Copy Alerts"
+---
+
+
+
+
+To speed up the deployment of alerts in the PEM system, you can copy alert definitions from one object to one or more target objects.
+
+To copy alerts from an object, highlight the object name (from which you will copy alerts) in the PEM client tree control, and select the `Manage Alerts...` option from the `Management` menu. When the `Manage Alerts` tab opens, click the `Copy Alerts` icon (located on the `Quick Links` toolbar) to open the `Copy Alert Configuration` dialog.
+
+
+
+The `Copy Alert Configuration` dialog copies all alerts from the object highlighted in the PEM client tree control to the object or objects selected on the dialog. Expand the tree control to select a node or nodes to specify the target object(s). Please note that the tree control displays a red warning indicator next to the source object.
+
+To copy alerts to multiple objects at once, select a parent node of the targets. For example, to copy the alerts from one table to all tables in a schema, you can simply select the checkbox next to the schema name. PEM will only copy alerts to targets that are of the same type as the source object.
+
+Check the `Ignore duplicates` radio button to prevent PEM from updating any existing alerts on the target objects with the same name as those being copied. Check the `Replace duplicates` radio button to replace existing alerts with alerts of the same name from the source object.
+
+Click the `Configure Alerts` button to proceed to copy the alerts from the source object to all objects of the same type in, or below those objects selected on the `Copy Alert Configuration` dialog. When the copy is complete, a popup will notify you that the alerts have been copied to the selected target(s).
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/03_pem_alert_templates.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/03_pem_alert_templates.mdx
new file mode 100644
index 00000000000..5b9c3d9b2cd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/03_pem_alert_templates.mdx
@@ -0,0 +1,273 @@
+---
+title: "Alert Templates"
+---
+
+
+
+
+An alert definition contains a system-defined or user-defined set of conditions that PEM compares to the system statistics; if the statistics deviate from the boundaries specified for that statistic, the alert triggers, and the PEM client displays a warning on the `Alerts Overview` page, and optionally sends a notification to a monitoring user.
+
+The table below lists the system-defined alert templates that you can use to create an alert; please note that this list is subject to change, and may vary by system.
+
+Within the table, the alerts are sorted by the target of the alert. The `Template Name` and `Description` columns identify and describe the behavior of the template. If the template `Details` column specifies `Yes`, metrics returned by the alert and alert parameters (if applicable) are accessible in the `Alerts table` on the `Global Overview` or `Alerts` dashboards:
+
+## Templates applicable on Agent
+
+| Template Name | Description | Details |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------|
+| Load Average (1 minute) | 1-minute system load average. | |
+| Load Average (5 minutes) | 5-minute system load average. | |
+| Load Average (15 minutes) | 15-minute system load average. | |
+| Load Average per CPU Core (1 minutes) | 1-minute system load average per CPU core. | |
+| Load Average per CPU Core (5 minutes) | 5-minute system load average per CPU core. | |
+| Load Average per CPU Core (15 minutes) | 15-minute system load average per CPU core. | |
+| CPU utilization | Average CPU consumption. | |
+| Number of CPUs running higher than a threshold | Number of CPUs running at greater than K% utilization. | Yes |
+| Free memory percentage | Free memory as a percent of total system memory. | |
+| Memory used percentage | Percentage of memory used. | |
+| Swap consumption | Swap space consumed (in megabytes). | |
+| Swap consumption percentage | Percentage of swap area consumed. | |
+| Disk Consumption | Disk space consumed (in megabytes). | |
+| Disk consumption percentage | Percentage of disk consumed. | |
+| Disk Available | Disk space available (in megabytes). | |
+| Disk busy percentage | Percentage of disk busy. | |
+| Most used disk percentage | Percentage used of the most utilized disk on the system. | Yes |
+| Total table bloat on host | The total space wasted by tables on a host, in MB. | |
+| Highest table bloat on host | The most space wasted by a table on a host, in MB. | |
+| Average table bloat on host | The average space wasted by tables on host, in MB. | |
+| Table size on host | The size of tables on host, in MB. | |
+| Database size on host | The size of databases on host, in MB. | |
+| Number of ERRORS in the logfile on agent N in last X hours | The number of ERRORS in the logfile on agent N in last X hours. | |
+| Number of WARNINGS in the logfile on agent N in last X hours | The number of WARNINGS in the logfile on agent N in last X hours. | |
+| Number of WARNINGS or ERRORS in the logfile on agent N in last X hours | The number of WARNINGS or ERRORS in the logfile on agent N in last X hours. | |
+| Package version mismatch | Check for package version mismatch as per catalog. | Yes |
+| Total materialized view bloat on host | The total space wasted by materialized views on a host, in MB. | |
+| Highest materialized view bloat on host | The most space wasted by a materialized view on a host, in MB. | |
+| Average materialized view bloat on host | The average space wasted by materialized views on host, in MB. | |
+| Materialized view size on host | The size of materialized views on host, in MB. | |
+| Agent Down | Specified agent is currently down. | |
+
+## Templates applicable on Server
+
+| Template Name | Description | Details |
+|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Total table bloat in server | The total space wasted by tables in server, in MB. | |
+| Largest table (by multiple of unbloated size) | Largest table in server, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | |
+| Highest table bloat in server | The most space wasted by a table in server, in MB. | Yes |
+| Average table bloat in server | The average space wasted by tables in server, in MB. | |
+| Table size in server | The size of tables in server, in MB. | Yes |
+| Database size in server | The size of databases in server, in MB. | Yes |
+| Number of WAL files | Total number of Write Ahead Log files. | |
+| Number of prepared transactions | Number of transactions in prepared state. | |
+| Total connections | Total number of connections in the server. | Yes |
+| Total connections as percentage of max\_connections | Total number of connections in the server as a percentage of maximum connections allowed on server, settings. | |
+| Unused, non-superuser connections | Number of unused, non-superuser connections on the server, user\_info, settings. | |
+| Unused, non-superuser connections as percentage of max\_connections | Number of unused, non-superuser connections on the server as a percentage of max\_connections, user\_info, settings. | |
+| Ungranted locks | Number of ungranted locks in server. | |
+| Percentage of buffers written by backends | The percentage of buffers written by backends vs. the total buffers written. | |
+| Percentage of buffers written by checkpoint | The percentage of buffers written by the checkpoints vs. the total buffers written. | |
+| Buffers written per second | Number of buffers written per second, over the last two probe cycles. | |
+| Buffers allocated per second | Number of buffers allocated per second, over the last two probe cycles. | |
+| Connections in idle state | Number of connections in server that are in idle state. | Yes |
+| Connections in idle-in-transaction state | Number of connections in server that are in idle-in-transaction state. | Yes |
+| Connections in idle-in-transaction state,as percentage of max\_connections | Number of connections in server that are in idle-in-transaction state, as a percentage of maximum connections allowed on server, settings | |
+| Long-running idle connections | Number of connections in the server that have been idle for more than N seconds. | Yes |
+| Long-running idle connections and idle transactions | Number of connections in the server that have been idle or idle-in-transaction for more than N seconds. | Yes |
+| Long-running idle transactions | Number of connections in the server that have been idle in transaction for more than N seconds. | Yes |
+| Long-running transactions | Number of transactions in server that have been running for more than N seconds. | Yes |
+| Long-running queries | Number of queries in server that have been running for more than N seconds. It does not include the long running vacuum or auto vacuum queries. | Yes |
+| Long-running vacuums | Number of vacuum operations in server that have been running for more than N seconds. | Yes |
+| Long-running autovacuums | Number of autovacuum operations in server that have been running for more than N seconds. | Yes |
+| Committed transactions percentage | Percentage of transactions in the server that committed vs. that rolled-back over last N minutes. | |
+| Shared buffers hit percentage | Percentage of block read requests in the server that were satisfied by shared buffers, over last N minutes. | |
+| Tuples inserted | Tuples inserted into server over last N minutes. | |
+| InfiniteCache buffers hit percentage | Percentage of block read requests in the server that were satisfied by InfiniteCache, over last N minutes. | |
+| Tuples fetched | Tuples fetched from server over last N minutes. | |
+| Tuples returned | Tuples returned from server over last N minutes. | |
+| Dead Tuples | Number of estimated dead tuples in server. | |
+| Tuples updated | Tuples updated in server over last N minutes. | |
+| Tuples deleted | Tuples deleted from server over last N minutes. | |
+| Tuples hot updated | Tuples hot updated in server, over last N minutes. | |
+| Sequential Scans | Number of full table scans in server, over last N minutes. | |
+| Index Scans | Number of index scans in server, over last N minutes. | |
+| Hot update percentage | Percentage of hot updates in the server over last N minutes. | |
+| Live Tuples | Number of estimated live tuples in server. | |
+| Dead tuples percentage | Percentage of estimated dead tuples in server. | |
+| Last Vacuum | Hours since last vacuum on the server. | |
+| Last AutoVacuum | Hours since last autovacuum on the server. | |
+| Last Analyze | Hours since last analyze on the server. | |
+| Last AutoAnalyze | Hours since last autoanalyze on the server. | |
+| Percentage of buffers written by backends over last N minutes | The percentage of buffers written by backends vs. the total buffers written over last N minutes. | |
+| Table Count | Total number of tables in server. | |
+| Function Count | Total number of functions in server. | |
+| Sequence Count | Total number of sequences in server. | |
+| A user expires in N days | Number of days before a user's validity expires. | |
+| Index size as a percentage of table size | Size of the indexes in server, as a percentage of their tables' size. | |
+| Largest index by table-size percentage | Largest index in server, calculated as percentage of its table's size, oc\_index, table\_size. | |
+| Number of ERRORS in the logfile on server M in the last X hours | The number of ERRORS in the logfile on server M in last X hours. | |
+| Number of WARNINGS in the logfile on server M in the last X hours | The number of WARNINGS in logfile on server M in the last X hours. | |
+| Number of WARNINGS or ERRORS in the logfile on server M in the last X hours | The number of WARNINGS or ERRORS in the logfile on server M in the last X hours. | |
+| Number of attacks detected in the last N minutes | The number of SQL injection attacks occurred in the last N minutes. | |
+| Number of attacks detected in the last N minutes by username | The number of SQL injection attacks occurred in the last N minutes by username. | |
+| Number of replica servers lag behind the primary by write location | Streaming Replication: number of replica servers lag behind the primary by write location. | Yes |
+| Number of replica servers lag behind the primary by flush location | Streaming Replication: number of replica servers lag behind the primary by flush location. | Yes |
+| Number of replica servers lag behind the primary by replay location | Streaming Replication: number of replica servers lag behind the primary by replay location. | Yes |
+| Replica server lag behind the primary by write location | Streaming Replication: replica server lag behind the primary by write location in MB. | Yes |
+| Replica server lag behind the primary by flush location | Streaming Replication: replica server lag behind the primary by flush location in MB. | Yes |
+| Replica server lag behind the primary by WAL pages | Streaming Replication: replica server lag behind the primary by WAL pages. | |
+| Replica server lag behind the primary by WAL segments | Streaming Replication: replica server lag behind the primary by WAL segments. | |
+| Replica server lag behind the primary by replay location | Streaming Replication: replica server lag behind the primary by replay location in MB. | Yes |
+| Replica server lag behind the primary by size (MB) | Streaming Replication: replica server lag behind the primary by size in MB. | Yes |
+| Total materialized view bloat in server | The total space wasted by materialized views in server, in MB. | |
+| Largest materialized view (by multiple of unbloated size) | Largest materialized view in server, calculated as a multiple of its own estimated unbloated size; exclude materialized views smaller than N MB. | |
+| Highest materialized view bloat in server | The most space wasted by a materialized view in server, in MB. | |
+| Average materialized view bloat in server | The average space wasted by materialized views in server, in MB. | |
+| Materialized view size in server | The size of materialized view in server, in MB. | |
+| View Count | Total number of views in server. | |
+| Materialized View Count | Total number of materialized views in server. | |
+| Audit config mismatch | Check for audit config parameter mismatch | Yes |
+| Server Down | Specified server is currently inaccessible. | |
+| Number of WAL archives pending | Streaming Replication: number of WAL files pending to be replayed at replica. | |
+| Number of minutes lag of replica server from primary server | Streaming Replication: number of minutes replica node is lagging behind the primary node. | |
+| Log config mismatch | Check for log config parameter mismatch. | Yes |
+
+## Templates applicable on Database
+
+| Template Name | Description | Details |
+|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Total table bloat in database | The total space wasted by tables in database, in MB. | |
+| Largest table (by multiple of unbloated size) | Largest table in database, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | |
+| Highest table bloat in database | The most space wasted by a table in database, in MB. | |
+| Average table bloat in database | The average space wasted by tables in database, in MB. | |
+| Table size in database | The size of tables in database, in MB. | Yes |
+| Database size | The size of the database, in MB. | |
+| Total connections | Total number of connections in the database. | Yes |
+| Total connections as percentage of max\_connections | Total number of connections in the database as a percentage of maximum connections allowed on server, settings. | |
+| Ungranted locks | Number of ungranted locks in database. | |
+| Connections in idle state | Number of connections in database that are in idle state. | Yes |
+| Connections in idle-in-transaction state | Number of connections in database that are in idle-in-transaction state. | Yes |
+| Connections in idle-in-transaction state,as percentage of max\_connections | Number of connections in database that are in idle-in-transaction state, as a percentage of maximum connections allowed on server, settings. | |
+| Long-running idle connections | Number of connections in the database that have been idle for more than N seconds. | Yes |
+| Long-running idle connections and idle transactions | Number of connections in the database that have been idle or idle-in-transaction for more than N seconds. | Yes |
+| Long-running idle transactions | Number of connections in the database that have been idle in transaction for more than N seconds. | Yes |
+| Long-running transactions | Number of transactions in database that have been running for more than N seconds. | Yes |
+| Long-running queries | Number of queries in database that have been running for more than N seconds. It does not include the long running vacuum or auto vacuum queries. | Yes |
+| Long-running vacuums | Number of vacuum operations in database that have been running for more than N seconds. | Yes |
+| Long-running autovacuums | Number of autovacuum operations in database that have been running for more than N seconds. | Yes |
+| Committed transactions percentage | Percentage of transactions in the database that committed vs. that rolled-back over last N minutes. | |
+| Shared buffers hit percentage | Percentage of block read requests in the database that were satisfied by shared buffers, over last N minutes. | |
+| InfiniteCache buffers hit percentage | Percentage of block read requests in the database that were satisfied by InfiniteCache, over last N minutes. | |
+| Tuples fetched | Tuples fetched from database over last N minutes. | |
+| Tuples returned | Tuples returned from database over last N minutes. | |
+| Tuples inserted | Tuples inserted into database over last N minutes. | |
+| Tuples updated | Tuples updated in database over last N minutes. | |
+| Tuples deleted | Tuples deleted from database over last N minutes. | |
+| Tuples hot updated | Tuples hot updated in database, over last N minutes. | |
+| Sequential Scans | Number of full table scans in database, over last N minutes. | |
+| Index Scans | Number of index scans in database, over last N minutes. | |
+| Hot update percentage | Percentage of hot updates in the database over last N minutes. | |
+| Live Tuples | Number of estimated live tuples in database. | |
+| Dead Tuples | Number of estimated dead tuples in database. | |
+| Dead tuples percentage | Percentage of estimated dead tuples in database. | |
+| Last Vacuum | Hours since last vacuum on the database. | |
+| Last AutoVacuum | Hours since last autovacuum on the database. | |
+| Last Analyze | Hours since last analyze on the database. | |
+| Last AutoAnalyze | Hours since last autoanalyze on the database. | |
+| Table Count | Total number of tables in database. | |
+| Function Count | Total number of functions in database. | |
+| Sequence Count | Total number of sequences in database. | |
+| Index size as a percentage of table size | Size of the indexes in database, as a percentage of their tables' size. | |
+| Largest index by table-size percentage | Largest index in database, calculated as percentage of its table's size, oc\_index, table\_size | |
+| Database Frozen XID | The age (in transactions before the current transaction) of the database's frozen transaction ID. | |
+| Number of attacks detected in the last N minutes | The number of SQL injection attacks occurred in the last N minutes. | |
+| Number of attacks detected in the last N minutes by username | The number of SQL injection attacks occurred in the last N minutes by username. | |
+| Queries that have been cancelled due to dropped tablespaces | Streaming Replication: number of queries that have been cancelled due to dropped tablespaces. | |
+| Queries that have been cancelled due to lock timeouts | Streaming Replication: number of queries that have been cancelled due to lock timeouts. | |
+| Queries that have been cancelled due to old snapshots | Streaming Replication: number of queries that have been cancelled due to old snapshots. | |
+| Queries that have been cancelled due to pinned buffers | Streaming Replication: number of queries that have been cancelled due to pinned buffers. | |
+| Queries that have been cancelled due to deadlocks | Streaming Replication: number of queries that have been cancelled due to deadlocks. | |
+| Total events lagging in all slony clusters | Slony Replication: total events lagging in all slony clusters. | Yes |
+| Events lagging in one slony cluster | Slony Replication: events lagging in one slony cluster. | |
+| Lag time (minutes) in one slony cluster | Slony Replication: lag time (minutes) in one slony cluster. | |
+| Total rows lagging in xdb single primary replication | xDB Replication: Total rows lagging in xdb single primary replication | Yes |
+| Total rows lagging in xdb multi primary replication | xDB Replication: Total rows lagging in xdb multi primary replication | Yes |
+| Total materialized view bloat in database | The total space wasted by materialized views in database, in MB. | |
+| Largest materialized view (by multiple of unbloated size) | Largest materialized view in database, calculated as a multiple of its own estimated unbloated size; exclude materialized views smaller than N MB. | |
+| Highest materialized view bloat in database | The most space wasted by a materialized view in database, in MB. | |
+| Average materialized view bloat in database | The average space wasted by materialized views in database, in MB. | |
+| Materialized view size in database | The size of materialized view in database, in MB. | |
+| View Count | Total number of views in database. | |
+| Materialized View Count | Total number of materialized views in database. | |
+
+## Templates applicable on Schema
+
+| Template Name | Description | Details |
+|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Total table bloat in schema | The total space wasted by tables in schema, in MB. | Yes |
+| Largest table (by multiple of unbloated size) | Largest table in schema, calculated as a multiple of its own estimated unbloated size; exclude tables smaller than N MB. | |
+| Highest table bloat in schema | The most space wasted by a table in schema, in MB. | |
+| Average table bloat in schema | The average space wasted by tables in schema, in MB. | |
+| Table size in schema | The size of tables in schema, in MB. | Yes |
+| Tuples inserted | Tuples inserted in schema over last N minutes. | |
+| Tuples updated | Tuples updated in schema over last N minutes. | |
+| Tuples deleted | Tuples deleted from schema over last N minutes. | |
+| Tuples hot updated | Tuples hot updated in schema, over last N minutes. | |
+| Sequential Scans | Number of full table scans in schema, over last N minutes. | |
+| Index Scans | Number of index scans in schema, over last N minutes. | |
+| Hot update percentage | Percentage of hot updates in the schema over last N minutes. | |
+| Live Tuples | Number of estimated live tuples in schema. | |
+| Dead Tuples | Number of estimated dead tuples in schema. | |
+| Dead tuples percentage | Percentage of estimated dead tuples in schema. | |
+| Last Vacuum | Hours since last vacuum on the schema. | |
+| Last AutoVacuum | Hours since last autovacuum on the schema. | |
+| Last Analyze | Hours since last analyze on the schema. | |
+| Last AutoAnalyze | Hours since last autoanalyze on the schema. | |
+| Table Count | Total number of tables in schema. | |
+| Function Count | Total number of functions in schema. | |
+| Sequence Count | Total number of sequences in schema. | |
+| Index size as a percentage of table size | Size of the indexes in schema, as a percentage of their table's size. | |
+| Largest index by table-size percentage | Largest index in schema, calculated as percentage of its table's size, oc\_index, table\_size | |
+| Materialized View bloat | Space wasted by the materialized view, in MB. | |
+| Total materialized view bloat in schema | The total space wasted by materialized views in schema, in MB. | |
+| Materialized view size as a multiple of ubloated size | Size of the materialized view as a multiple of estimated unbloated size. | |
+| Largest materialized view (by multiple of unbloated size) | Largest materialized view in schema, calculated as a multiple of its own estimated unbloated size; exclude materialized view smaller than N MB. | |
+| Highest materialized view bloat in schema | The most space wasted by a materialized view in schema, in MB. | |
+| Average materialized view bloat in schema | The average space wasted by materialized views in schema, in MB. | |
+| Materialized view size | The size of materialized view, in MB. | |
+| Materialized view size in schema | The size of materialized views in schema, in MB. | |
+| View Count | Total number of views in schema. | |
+| Materialized View Count | Total number of materialized views in schema. | |
+| Materialized View Frozen XID | The age (in transactions before the current transaction) of the materialized view's frozen transaction ID. | |
+
+## Templates applicable on Table
+
+| Template Name | Description | Details |
+|-------------------------------------------|------------------------------------------------------------------------------------------------|---------|
+| Table bloat | Space wasted by the table, in MB. | |
+| Table size | The size of table, in MB. | |
+| Table size as a multiple of ubloated size | Size of the table as a multiple of estimated unbloated size. | |
+| Tuples inserted | Tuples inserted in table over last N minutes. | |
+| Tuples updated | Tuples updated in table over last N minutes. | |
+| Tuples deleted | Tuples deleted from table over last N minutes. | |
+| Tuples hot updated | Tuples hot updated in table, over last N minutes. | |
+| Sequential Scans | Number of full table scans on table, over last N minutes. | |
+| Index Scans | Number of index scans on table, over last N minutes. | |
+| Hot update percentage | Percentage of hot updates in the table over last N minutes. | |
+| Live Tuples | Number of estimated live tuples in table. | |
+| Dead Tuples | Number of estimated dead tuples in table. | |
+| Dead tuples percentage | Percentage of estimated dead tuples in table. | |
+| Last Vacuum | Hours since last vacuum on the table. | |
+| Last AutoVacuum | Hours since last autovacuum on the table. | |
+| Last Analyze | Hours since last analyze on the table. | |
+| Last AutoAnalyze | Hours since last autoanalyze on the table. | |
+| Row Count | Estimated number of rows in a table. | |
+| Index size as a percentage of table size | Size of the indexes on table, as a percentage of table's size. | |
+| Table Frozen XID | The age (in transactions before the current transaction) of the table's frozen transaction ID. | |
+
+## Global Templates
+
+| Template Name | Description | Details |
+|---------------|-----------------------------------------------------|---------|
+| Agents Down | Number of agents that haven't reported in recently. | |
+| Servers Down | Number of servers that are currently inaccessible. | |
+| Alert Errors | Number of alerts in an error state. | |
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/04_pem_custom_alert_templates.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/04_pem_custom_alert_templates.mdx
new file mode 100644
index 00000000000..8b33e5e307e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/04_pem_custom_alert_templates.mdx
@@ -0,0 +1,106 @@
+---
+title: "Custom Alert Templates"
+---
+
+
+
+
+An alert template is a prototype that defines the properties of an [alert](../../04_toc_pem_features/09_pem_alerting/#pem_alerting_dialog). An alert instructs the server to compare the current state of the monitored object to a threshold (specified in the alert template) to determine if a situation exists that requires administrative attention.
+
+You can use the `Alert Templates` tab to define a custom alert template or view the definitions of existing alert templates. To open the `Alert Template` tab, select the `Manage Alerts...` menu option from the `Management` menu; when the `Manage Alerts` tab opens, select `Alert Templates` from the `Quick Links` menu.
+
+
+
+Use the `Show System Template` drop-down listbox to filter the alert templates; select a type from the listbox to view all of the templates for that level of the PEM hierarchy.
+
+## Reviewing an Existing Alert Template
+
+To view the definition of an existing template (including PEM pre-defined alert templates), use the `Show System Template` drop-down listbox to select the type of object monitored. When you select the object type, the `Alert Templates` table will display the currently defined alert templates that correspond with that object type. Highlight a template name and click the edit icon (at the left end of the row) to review the template definition.
+
+
+
+Use the edit button to the left of a template name to view detailed information about the template:
+
+- General information is displayed on the `General` tab.
+- The names of probes that provide data for the template are listed on the `Probe Dependency` tab.
+- The names of any parameters referred to in the SQL code are listed on the `Parameters` tab.
+- The SQL code that defines the behavior of the alert is displayed on the `SQL` tab.
+
+## Defining a New Alert Template
+
+To define a new alert template, use the `Show System Template` drop-down listbox to select `None`, and click the `Add` icon (+) located in the upper-right corner of the alert template table.
+
+
+
+Use fields on the `General` tab to specify general information about the template:
+
+- Use the `Template name` field to specify a name for the new alert template; this field is required.
+- Use the `Description` field to provide a description of the alert template; this field is required.
+- Use the `Target type` drop-down listbox to select the type of object that will be the focus of the alert.
+- Use the `Applies to server` drop-down listbox to specify the server type (EDB Postgres Advanced Server or PostgreSQL) to which the alert will be applied; you can specify a single server type, or `ALL`.
+- Use the `History retention` field to specify the number of days that the result of the alert execution will be stored on the PEM server.
+- Use the `Threshold unit` field to specify the unit type of the threshold value.
+- Use fields in the `Auto create` box to indicate if PEM should use the template to generate an automatic alert. If enabled, PEM will automatically create an alert when a new server or agent (as specified by the `Target type` drop-down listbox) is added, and delete that alert when the target object is dropped.
+ - Move the `Auto create?` slider to `Yes` to indicate that PEM should automatically create alerts based on the template. If you modify an existing alert template, changing the `Auto create?` slider from `No` to `Yes`, PEM will create alerts on the existing agents and servers. Please note that if you change the slider from `Yes` to `No`, the default threshold values in existing alerts will be erased, and cannot be recovered.
+
+ - Use the `Operator` drop-down listbox to select the operator that PEM will use when evaluating the current system values.
+
+ > Select a greater-than sign (>) to indicate that the alert should be triggered when the system values are greater than the values entered in the `Threshold values` fields.
+ >
+ > Select a less-than sign (<) to indicate that the alert should be triggered when the system values are less than the values entered in the `Threshold values` fields.
+
+ - Use the threshold fields to specify the values that PEM will compare to the system values to determine if an alert should be raised. Please note that you must specify values for all three thresholds (`Low`, *Medium*, and `High`):
+
+ - Enter a value that will trigger a low-severity alert in the `Low` field.
+ - Enter a value that will trigger a medium-severity alert in the `Medium` field.
+ - Enter a value that will trigger a high-severity alert in the `High` field.
+- Use the `Check frequency` field to specify the default number of minutes between alert executions. This value specifies how often the server will invoke the SQL code specified in the definition and compare the result to the threshold value specified in the template.
+
+
+
+Use the fields on the `Probe Dependency` tab to specify the names of probes referred to in the SQL query specified on the `SQL` tab:
+
+- Use the `Probes` drop-down listbox to select from a list of the available probes; highlight a probe name, and click the `Add` button to add the probe to the list of probes used by the alert template. To remove a probe from the selected probes list, highlight the probe name, and click the `Delete` icon.
+
+
+
+Use fields on the `Parameters` tab to define the parameters that will be used in the SQL code specified on the `SQL` tab. Click the `Add` icon, and:
+
+- Use the `Name` field to specify the parameter name.
+- Use the `Data type` drop-down listbox to select the type of parameter.
+- Use the `Unit` field to specify the type of unit specified by the parameter.
+
+When you've defined a new parameter, click the `Add/Change` button to save the definition and add the parameter to the parameter list.
+
+To modify an existing parameter definition, highlight a parameter name in the list, modify the parameter values in the fields at the bottom of the tab, and click `Add/Change` to preserve the changes. To remove one or more parameter definitions, highlight the parameter name(s) and click the `Remove` button.
+
+
+
+Use the `Code` field on the `SQL` tab to provide the text of the SQL query that the server will invoke when executing the alert. The SQL query will provide the result against which the threshold value is compared; if the alert result deviates from the specified threshold value, an alert will be raised.
+
+Within the query, parameters defined on the `Parameters` tab should be referenced (sequentially) by the variable `param_x`, where `x` indicates the position of the parameter definition within the parameter list. For example, `param_1` refers to the first parameter in the parameter list, param\_2 refers to the second parameter in the parameter list, and so on.
+
+The query can also include the following pre-defined variables:
+
+| Variable Description | Variable Name |
+|-----------------------------------------|---------------------|
+| agent identifier | '${agent\_id}' |
+| server identifier | '${server\_id}' |
+| database name | '${database\_name}' |
+| schema name | '${schema\_name}' |
+| table, index, sequence or function name | '${object\_name}' |
+
+Please Note: If the specified query is dependent on one or more probes from different levels within the PEM hierarchy (server, database, schema, etc.), and a probe becomes disabled, any resulting alerts will be displayed as follows:
+
+- If the alert definition and the probe referenced by the query are from the same level within the PEM hierarchy, the server will display any alerts that reference the alert template on the Alert Error table of the Global Alert Dashboard.
+- If the alert definition and the probe referenced by the query are from different levels of the PEM hierarchy, the server will display any triggered alerts that reference the alert template on the Alert Details table of the hierarchy on which the Alert was defined.
+
+Use the `Detailed Information SQL` field to provide a SQL query that will be invoked if the alert is triggered. The result set of the query may be displayed as part of the detailed alert information on the `Alerts` dashboard or `Global Overview` dashboard.
+
+After defining a new alert template, click the `Add/Change` button to save the definition and add the template to the `Alert Templates list`. Click `Cancel` to exit the `Alert Templates` dialog without saving changes.
+
+After defining a template, you can use the [Manage Alerts](../../04_toc_pem_features/09_pem_alerting/#pem_alerting_dialog) tab to create and enable an alert based on the template.
+
+## Deleting an Alert Template
+
+To delete an alert template, highlight the template name in the alert templates table, and click the `Delete` icon (located to the left of the alert template name). The alert history will persist for the length of time specified on the `History Retention` field in the template definition.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/05_pem_email_groups.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/05_pem_email_groups.mdx
new file mode 100644
index 00000000000..8dbe732e434
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/05_pem_email_groups.mdx
@@ -0,0 +1,46 @@
+---
+title: "Email Groups"
+---
+
+
+
+
+Postgres Enterprise Manager monitors your system for conditions that require user attention. You can use an email group to specify the email addresses of users that the server will notify if current values deviate from threshold values specified in an alert definition. An email group has the flexibility to notify multiple users, or target specific users during user-defined time periods.
+
+Please note that you must configure the PEM Server to use an SMTP server to deliver email before PEM can send email notifications.
+
+Use the `Email Groups` tab to configure groups of SMTP email recipients. To access the `Email Groups` tab, select `Manage Alerts...` from the PEM client's `Management` menu; when the `Manage Alerts` tab opens, select `Email Groups` from the `Quick Links` toolbar.
+
+
+
+The `Email Groups` tab displays a list of the currently defined email groups. Highlight a group name and click the edit icon (at the far left end of the row) to modify an existing group.
+
+To define a new email group, click the Add icon (+) in the upper-right corner of the table.
+
+
+
+Use the `Email Group` tab to define an email group and its members:
+
+- Provide a name for the email group in the `Group name` field.
+
+Each row within the email group definition will associate a unique set of email addresses with a specific time period. When an alert is triggered, the server will evaluate the times specified in each row and send the message to those group members whose definitions are associated with the time that the alert triggered.
+
+Click the Add icon (+) in the group members table to open the `Options` tab, and add the member addresses that will receive notifications for the time period specified:
+
+- Enter a comma-delimited list of recipient addresses in the `Reply to addresses` field.
+- Enter a comma-delimited list of return addresses in the `Reply to addresses` field.
+- Enter a comma-delimited list of addresses that will receive a copy of the email in the `Cc addresses` field.
+- Enter a comma-delimited list of addresses that will receive a copy of the email (without the knowledge of other recipients) in the `Bcc addresses` field.
+- Enter the email address that messages to this group should be sent from in the `From address` field.
+- Provide a comment that will be used as a subject line prefix for any emails sent as part of a notification in the `Subject prefix` field.
+- Use the `From time` and `To time` time selectors to specify the time range for notifications to the group member(s) that are identified on this row of the email group dialog. When an alert is triggered, the server will evaluate the times specified in each row and send the message to those group members whose definitions include the current time. Provide the `From time` and `To time` values in the locale of the PEM client host, and the PEM server will translate the time into other time zones as required.
+
+When you've identified the member or members that will receive an email during a specific time period, click the add icon to specify another time period and the email addresses that will be notified during those hours. When you've finished defining the email group, click the save icon.
+
+## Deleting an Email Group
+
+To mark an email group for deletion, highlight the group name in the `Email Groups` table and click the delete icon to the left of the name; the alert will remain in the list, but in red strike-through font.
+
+
+
+The delete icon acts as a toggle; you can undo the deletion by clicking the delete icon a second time; when you click the save icon, the email group definition will be permanently deleted.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/06_pem_webhooks.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/06_pem_webhooks.mdx
new file mode 100644
index 00000000000..0a79bc6be74
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/06_pem_webhooks.mdx
@@ -0,0 +1,110 @@
+---
+title: "Webhooks"
+---
+
+
+
+
+Postgres Enterprise Manager monitors your system for conditions that require user attention. You can use a webhook to create the endpoints that will receive a notification if current values deviate from threshold values specified in an alert definition. PEM sends a notification to multiple webhook endpoints, or to specific target webhook endpoints based on the events triggered.
+
+Please note that you must configure the PEM Server to use webhooks to receive notification of alert events on threshold value violations in your configured applications.
+
+Use the `Webhooks` tab to configure endpoint recipients. To access the `Webhooks` tab, select `Manage Alerts...` from the PEM client's `Management` menu; when the `Manage Alerts` tab opens, select `Webhooks` from the `Quick Links` toolbar.
+
+
+
+The `Webhooks` tab displays a list of the currently defined recipient applications as endpoints. Highlight an endpoint and click the edit icon (at the far left end of the row) to modify an existing endpoint.
+
+## Creating a Webhook
+
+To define a new webhook, click the `Add` icon (+) in the upper-right corner of the table.
+
+
+
+Use the `General` tab to define the basic details of the webhook:
+
+- Provide a name for the webhook in the `Name` field.
+- Specify a webhook URL where all the notifications will be delivered in the `URL` field.
+- Set the request method type used to make the call in the `Request Method` field i.e. `POST` or `PUT`.
+- By default `webhooks` will be enabled; to disable a webhook set `Enable?` to `No`.
+
+
+
+Note
+
+
+
+Suppose you need to use the alert configuration placeholder values in an external script. You can do it either by passing them as the command-line arguments or exporting them as environment variables. Please note that the external script must have proper execution permissions.
+
+- You can run the script with any of the placeholders as command-line argument.
+
+ For eg:
+
+ > ``` bash
+ > #!/bin/bash
+ >
+ > bash
+
+
+
+## Defining a Webhook SSL configurations
+
+You can define the Webhook SSL parameters in the respective agent configuration file or registry in windows. You can find the list of Webhook SSL parameters in PEM Agent Configuration Parameters <pem\_agent\_config\_params> section. If you add or remove any of the agent configuration parameters, you must restart the agent to apply them.
+
+> - On 32 bit Windows systems, PEM registry entries for Webhooks are located in HKEY\_LOCAL\_MACHINE\\Software\\EnterpriseDB\\PEM\\agent\\WEBHOOK
+> - On 64 bit Windows systems, PEM registry entries for Webhooks are located in HKEY\_LOCAL\_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent\\WEBHOOK
+> - On Linux systems, PEM configuration options for Webhooks are stored in the agent.cfg file, located (by default) in /usr/edb/pem/agent/etc
+
+
+
+
+
+
+
+Use the `HTTP Headers` tab to define the header parameters to pass while calling the webhook endpoints:
+
+- All the values will be specified as a key and value pair.
+- Specify a key parameter in the `Key` field and a value in the `Value` field.
+- To add multiple `HTTP Headers`, click the `Add` icon (+) in the upper-right corner of the `HTTP Headers` table.
+- To delete the `HTTP Headers`, click on `Delete` icon to the left of the `Key`; the alert will remain in the list, but in strike-through font. Click the `Save` button to reflect the changes.
+- To edit the `HTTP Headers`, click on the `Edit` icon to the left of `Key`.
+
+
+
+Use the `Payload` tab to define the JSON data to be sent to the endpoint when an alert is triggered:
+
+- `Type` specifies data to be sent in format type (i.e. JSON).
+
+- Use `Template` to configure JSON data sent to endpoints. Within the `Template`, you can use placeholders for the following:
+
+ > - `%AlertID%` - the id of the triggered alert.
+ > - `%AlertName%` - the name of the triggered alert.
+ > - `%ObjectName%` - the name of the server or agent on which the alert was triggered.
+ > - `%ObjectType%` - the type on which alert was generated.
+ > - `%ThresholdValue%` - the threshold value reached by the metric when the alert triggered.
+ > - `%CurrentValue%` - the current value of the metric that triggered the alert.
+ > - `%CurrentState%` - the current state of the alert.
+ > - `%OldState%` - the previous state of the alert.
+ > - `%AlertRaisedTime%` - the time that the alert was raised, or the most recent time that the alert state was changed.
+ > - `%AgentID%` - the id of the agent by which alert was generated.
+ > - `%AgentName%` - the name of the agent by which alert was generated.
+ > - `%ServerID%` - the id of the server on which alert was generated.
+ > - `%ServerName%` - the name of the server on which alert was generated.
+ > - `%ServerIP%` - the ip or address of the server on which alert was generated.
+ > - `%ServerPort%` - the the port of the server on which alert was generated.
+ > - `%DatabaseName%` - the name of the database on which alert was generated.
+ > - `%SchemaName%` - the name of the schema on which alert was generated.
+ > - `%PackageName%` - the name of the package on which alert was generated.
+ > - `%DatabaseObjectName%` - the name of the database object name like table name, function name etc on which alert was generated.
+ > - `%Parameters%` - the list of custom parameters used to generate the alert.
+ > - `%AlertInfo%` - the detailed database object level information of the alert.
+
+- Click on the `Test Connection` button, to test notification delivery to the mentioned endpoint.
+
+
+
+Use the `Notifications` tab to specify an alert level for webhook endpoints:
+
+- Set `All alerts` to `Yes` to enable all alert levels to send notifications.
+- To instruct PEM to send an notification when a specific alert level is reached, set the slider next to an alert level to `Yes`. Please note that you must set `All alerts` to `No` to configure an individual alert level.
+
+## Deleting a Webhook
+
+To mark a webhook for deletion, highlight the webhook name in the `Webhooks` table and click the delete icon to the left of the name; the alert will remain in the list, but in strike-through font.
+
+
+
+The delete icon acts as a toggle; you can undo the deletion by clicking the delete icon a second time; when you save your work (by clicking the save icon), the webhook definition will be permanently deleted.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/07_snmp_mib_generation.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/07_snmp_mib_generation.mdx
new file mode 100644
index 00000000000..f33c63ae45e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/07_snmp_mib_generation.mdx
@@ -0,0 +1,10 @@
+---
+title: "SNMP MIB Generation"
+---
+
+
+
+
+PEM allows alerts to be sent as SNMP traps or notifications to receivers such as network monitoring tools. To enable such tools to understand these notifications, a MIB file may be generated that describes the different alerts and accompanying information that PEM may send. The `pem.generate_alert_mib()` SQL function in the PEM database may be used to generate the MIB file from the alert templates defined in the database. For example:
+
+ psql.exe -U postgres -d pem -A -t -c "SELECT pem.generate_alert_mib();" > PEM-ALERTING-MIB
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/08_snmp_trap_details.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/08_snmp_trap_details.mdx
new file mode 100644
index 00000000000..3c076bbecc7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/08_snmp_trap_details.mdx
@@ -0,0 +1,79 @@
+---
+title: "SNMP Trap Details"
+---
+
+
+
+
+Every SNMP trap send by PEM starts with oid .1.3.6.1.4.1.27645.5444, Significance of each identifier in oid is as follow’s.
+
+| Identifier | Meaning |
+|------------|---------------------------------------------------------------------------------|
+| 1 | ISO, ISO is the group that established the OID standard |
+| 3 | org, Organization identification schemes registered according to ISO/IEC 6523-2 |
+| 6 | dod, United States Department of Defense (DoD) |
+| 1 | internet, Communication will be via Internet/network |
+| 4 | private, This is a device manufactured by a private entity (not goverment) |
+| 1 | enterprise, The device manufacturer is classified as an enterprise |
+| 27645 | PostgreSQL global development group |
+| 5444 | pem |
+
+## How OID's are formed?
+
+PEM’s SNMP trap has following oid format 1.3.6.1.4.1.27645.5444.<alert\_target\_level\_identifier>.<alert\_identifier>
+
+Following table lists down possible values for <alert\_target\_level\_identifier>.
+
+| Identifier | Alert Target Level |
+|------------|--------------------|
+| 1 | Agent |
+| 2 | Server |
+| 3 | Database |
+| 4 | Schema |
+| 5 | Table |
+| 6 | Index |
+| 7 | Sequence |
+| 8 | Function |
+| 9 | Global |
+
+<alert\_identifier> is unique identifier for each alert, which you can find in snmp\_oid column of pem.alert\_template table.
+
+For example, snmp\_oid for Agent Down alert template is 34, hence trapOID for agent down alert will be 1.3.6.1.4.1.27645.5444.1.34
+
+## How OID's for binding variables are formed?
+
+Every binding variable oid has following format 1.3.6.1.4.1.27645.5444.10.<binding\_variable\_identifier>, where 10 is identifier for binding variable Following table lists down possible values for <binding\_variable\_identifier>
+
+| Identifier | Variable Name |
+|------------|---------------------|
+| 1 | alertName |
+| 2 | agentID |
+| 3 | serverID |
+| 4 | agentName |
+| 5 | serverName |
+| 6 | databaseName |
+| 7 | schemaName |
+| 8 | objectName |
+| 9 | thresholdvalue |
+| 10 | previousValue |
+| 11 | value |
+| 12 | previousStatus |
+| 13 | status |
+| 14 | recordedTime |
+| 15 | downObjects |
+| 16 | detailedInformation |
+
+For example, 1.3.6.1.4.1.27645.5444.10.1 is oid for binding variable alertName.
+
+Details of each snmp traps in pem.snmp\_spool table. For example,
+
+ pem=# select * from pem.snmp_spool;
+ -[ RECORD 1 ]----+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+ id | 1
+ trap_oid | .1.3.6.1.4.1.27645.5444.1.34
+ enterprise_oid | .1.3.6.1.4.1.27645.5444
+ trap_version | 2
+ varbinding_oid | .1.3.6.1.4.1.27645.5444.10.1|.1.3.6.1.4.1.27645.5444.10.2|.1.3.6.1.4.1.27645.5444.10.4|.1.3.6.1.4.1.27645.5444.10.9|.1.3.6.1.4.1.27645.5444.10.10|.1.3.6.1.4.1.27645.5444.10.11|.1.3.6.1.4.1.27645.5444.10.12|.1.3.6.1.4.1.27645.5444.10.13|.1.3.6.1.4.1.27645.5444.10.14
+ varbinding_value | Agent Down||Postgres Enterprise Manager Host|{0.1,0.2,0.3}|0|1|CLEAR|HIGH|2020-06-22 15:51:03.266437+10
+ sent_status | s
+ recorded_time | 22-JUN-20 15:51:03.266437 +10:00
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/09_using_pem_with_nagios.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/09_using_pem_with_nagios.mdx
new file mode 100644
index 00000000000..90c67000be5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/09_using_pem_with_nagios.mdx
@@ -0,0 +1,94 @@
+---
+title: "Using PEM with Nagios"
+---
+
+
+
+
+The PEM server can send a passive alert result to Nagios network-alerting software when an alert is triggered. To instruct the PEM server to notify Nagios of a triggered alert, you must:
+
+- Enable Nagios notification for each alert that will trigger a notification from the PEM server to Nagios. Please note that PEM alerting must be configured before you create the host.cfg file and services.cfg file.
+- Configure Nagios-related behaviors of the PEM server.
+- Create the host.cfg and services.cfg configuration files.
+- If necessary, modify the Nagios configuration file and restart the Nagios server.
+- Install the PEM Agent on the system where Nagios server is installed and register it with the PEM Server. Set `enable_nagios` configuration to `true` in the agent.cfg for that agent, and restart the agent service.
+
+Detailed information about each configuration step is listed below.
+
+After configuring the server to enable Nagios alerting, any triggered alerts will send a passive check result to the Nagios service. The syntax of a passive alert is:
+
+> \[*timestamp*\] PROCESS\_SERVICE\_CHECK\_RESULT; `host_name` ; `service_name` ; `service_status` ;
+
+Where:
+
+> - `timestamp` is the date and time that the alert was triggered.
+> - `host_name` is the name of the server or agent.
+> - `service_name` is the name of the alert.
+> - `service_status` is the numeric service status value:
+> - 0 if the service status is *OK*
+> - 1 if the service status is *WARNING*
+> - 2 if the service status is *CRITICAL*
+> - 3 if the service status is *UNKNOWN*
+>
+> The PEM server uses the following rules to evaluate the service status:
+>
+> - If the PEM alert level is `CLEARED`, the warning message will read *OK*
+> - If the PEM alert level is `LOW`, the warning message will read *WARNING*
+> - If the `is_nagios_medium_alert_as_critical` flag (specified in the PEM server configuration dialog) is set to `FALSE` and the alert level is `MEDIUM`, the warning message will read *WARNING*
+> - If the `is_nagios_medium_alert_as_critical` flag (specified in the PEM server configuration dialog) is set to `TRUE` and the alert level is `MEDIUM`, the warning message will read *CRITICAL*
+> - If the PEM alert level is `HIGH`, the warning message will read *CRITICAL*
+
+## Enabling Nagios Notification for an Alert
+
+The PEM server maintains a unique set of notification properties for each enabled alert. Use the `Notification` tab of the `` `Manage Alerts `` <pem\_alerting\_dialog> tab to specify that (when triggered), a given alert will send an alert notice to Nagios. To modify the notification properties of an alert, right-click on the name of the object monitored by the alert, and select Manage Alerts... from the Management menu. When the Manage Alerts tab opens, locate the alert, and then click the edit button to the left of the alert name in the Alerts list. When the Manage Alerts tab opens, select the Notification\` tab.
+
+
+
+To enable Nagios notification, move the slider next to `Submit passive service check result to Nagios` to `Yes`; before exiting the `Manage Alerts` tab, click the save icon to preserve your changes.
+
+## Configuring Nagios-related behavior of the PEM Server
+
+You can use the `Server Configuration` dialog to provide information about your Nagios configuration to the PEM server. To open the [Server Configuration](../../04_toc_pem_features/02_pem_server_config/#pem_server_config) dialog, select `Server Configuration...` from the PEM client's `Management` menu.
+
+
+
+Four server configuration parameters specify information about your Nagios installation and PEM server behavior related to Nagios:
+
+> - Use the `nagios_cmd_file_name` parameter to specify the location of the Nagios pipeline file that will receive passive check alerts from PEM. The default value of this parameter is `/usr/local/nagios/var/rw/nagios.cmd`. The parameter specifies the default file location; if your nagios.cmd file resides in an alternate location, specify the file location in the `Value` field.
+> - Move the slider in the `nagios_enabled` parameter to `Yes` to instruct the PEM server to send passive check alerts to Nagios.
+> - Use the `nagios_medium_alert_as_critical` slider to specify the warning severity that the PEM server will pass to Nagios if a medium alert is triggered:
+> - If the `is_nagios_medium_alert_as_critical` flag is set to `FALSE` and the alert level `MEDIUM`, the warning message will read *WARNING*
+> - If the `is_nagios_medium_alert_as_critical` flag is set to `TRUE` and the alert level `MEDIUM`, the warning message will read *CRITICAL*
+> - Use the `nagios_spool_retention_time` parameter to specify the number of days of notification history that will be stored on the PEM server. The default value is 7 days.
+
+After modifying parameter values, click the save icon to preserve your changes.
+
+## Creating the hosts.cfg and services.cfg File
+
+The templates.cfg file (by default, located in /usr/local/nagios/etc/objects) specifies the properties of a generic-host and generic-service. The properties specify the parameters used in the hosts.cfg and services.cfg files.
+
+In most cases (when PEM is installed in a default configuration), you will not be required to modify the templates.cfg file before creating the hosts.cfg and services.cfg files. If necessary, you can modify the templates.cfg file to specify alternate values for parameters or to create new templates.
+
+Before modifying the Nagios configuration file, use the following command to create a hosts.cfg file that contains information about the PEM hosts that reside on the local system:
+
+> ./psql -U postgres -p 5433 -d pem -A -t -c "select pem.create\_nagios\_host\_config('generic-host')" > /usr/local/nagios/etc/objects/hosts.cfg
+
+Then, use the following command to create a `services.cfg` file that contains information about the PEM services that reside on the local system:
+
+> ./psql -U postgres -p 5433 -d pem -A -t -c "select pem.create\_nagios\_service\_config('generic-service')" > /usr/local/nagios/etc/objects/services.cfg
+
+If you wish to use a custom template.cfg file entry, specify the entry name in place of generic-host or generic-service in the above commands.
+
+## Modifying the Nagios Configuration File
+
+After creating the host.cfg and services.cfg files, you must specify their location in the Nagios configuration file (by default, /usr/local/nagios/etc/nagios.cfg). Modify the configuration file, adding entries that specify the location of the files:
+
+> cfg\_file=/usr/local/etc/objects/hosts.cfg cfg\_file=/usr/local/etc/objects/services.cfg
+
+You can use the following command to confirm that Nagios is properly configured:
+
+> /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
+
+After confirming that Nagios is configured correctly, restart the Nagios service:
+
+> /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/index.mdx
new file mode 100644
index 00000000000..e87d094bc61
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/09_pem_alerting/index.mdx
@@ -0,0 +1,54 @@
+---
+title: "Alerting"
+---
+
+
+
+
+Postgres Enterprise Manager monitors a system for conditions that require user attention. An alert definition contains a system-defined or user-defined set of conditions that PEM compares to the system statistics; if the statistics deviate from the boundaries specified for that statistic, the alert triggers, displaying a `High` (red), `Low` (yellow) or `Medium` (orange) severity warning in the left-most column of the `Alerts Status` table on the `Global Overview` dashboard, and optionally sends a notification via email to [Email Groups](../04_toc_pem_features/09_pem_alerting/#pem_email_groups) or SNMP trap/notification receivers <snmp\_mib\_generation>.
+
+
+
+The PEM server includes a number of pre-defined alerts that are actively monitoring your servers. If the alert definition makes details available about the cause of the alert, you can click the down arrow to the right of the severity warning to access a dialog with detailed information about the condition that triggered the alert. Please note that Alert Details section lists top 10 entries only in the general tab.
+
+
+
+PEM also provides an interface that allows you to create customized alerts. Each alert uses metrics defined on an alert template. An alert template defines how the server will evaluate the statistics for a resource or metric. The PEM server includes a number of pre-defined alert templates, or you can create custom alert templates.
+
+## Using the Alerts Dashboard
+
+Use the `Dashboards` menu (at the top of the `Global Overview` dashboard) to access the [Alerts Dashboard](../04_toc_pem_features/01_dashboards/#alerts_dashboard). The Alerts Dashboard displays a summary of the active alerts and the status of each alert:
+
+
+
+The `Alerts Overview` section displays a graphic representation of the active alerts, as well as a count of the current High, Low and Medium alerts. The vertical bar on the left of the graph provides the count of the alerts displayed in each column. Hover over a bar to display the alert count for the selected alert severity in the upper-right hand corner of the `Alerts Status` graph.
+
+The `Alert Details` table provides a list of the alerts that are currently triggered. The entries are prioritized from high-severity to lower-severity; each entry includes information that will allow you to identify the alert and recognize the condition that triggered the alert. Click the name of an alert to review the alert definition, or the down arrow next to the alert icon to review the metrics that triggered the alert.
+
+The `Alert Errors` table displays configuration-related errors (eg. accidentally disabling a required probe, or improperly configuring an alert parameter). You can use the information provided in the `Error Message` column to identify and resolve the conflict that is causing the error; for additional assistance, contact [EnterpriseDB Support](mailto:support@enterprisedb.com).
+
+## Managing Alerts
+
+PEM's `Manage Alerts` tab allows you to define custom alerts or modify existing alerts. To open the [Manage Alerts tab](../04_toc_pem_features/09_pem_alerting/#pem_alerting_dialog), select `Manage Alerts...` from the `Management` menu. The Manage Alerts tab provides an easy way to review the alerts that are currently defined for the object that is highlighted in the PEM client tree control; simply select an object to see the alerts that are defined for that object.
+
+
+
+The `Manage Alerts` tab also provides `Quick Links` that provide quick access to dialogs that allow you to:
+
+> - [Copy an alert](../04_toc_pem_features/09_pem_alerting/#pem_alert_copy) from one object to one or more objects.
+> - [Create or modify an alert template](../04_toc_pem_features/09_pem_alerting/#pem_custom_alert_templates).
+> - [Create or Modify an email group](../04_toc_pem_features/09_pem_alerting/#pem_email_groups).
+> - Manage [PEM Server configuration](../04_toc_pem_features/09_pem_alerting/#pem_email_groups) details.
+> - Access the PEM online help.
+
+You can configure an alert to notify Nagios network-alerting software when that alert is triggered. For more information, see [Using PEM with Nagios](../04_toc_pem_features/09_pem_alerting/#using_pem_with_nagios).
+
+To [create a new alert](../04_toc_pem_features/09_pem_alerting/#pem_alerting_dialog), click the add icon in the upper-right corner of the `Alerts` table.
+
+Contents:
+
+
+
+Note
+
+
+
+The above `Enable?` setting will work only if `enable_webhook` parameter is set to true in `agent.cfg` file. By default, `enable_webhook` parameter is set to true only for the Agent running on the PEM Server Host. For all other Agents running on other hosts, it needs to be set to true manually.
+
+
+
+pem\_alerting\_dialog pem\_alert\_copy pem\_alert\_templates pem\_custom\_alert\_templates pem\_email\_groups pem\_webhooks snmp\_mib\_generation snmp\_trap\_details using\_pem\_with\_nagios
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/01_pem_create_new_chart.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/01_pem_create_new_chart.mdx
new file mode 100644
index 00000000000..b2b4283e253
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/01_pem_create_new_chart.mdx
@@ -0,0 +1,77 @@
+---
+title: "Creating a New Chart"
+---
+
+
+
+
+Click the `Create New Chart` icon in the `Quick Links` section of the `Manage Charts` tab to open the `Create Chart` wizard. The `Create Chart` wizard will walk you through the steps required to define a new chart.
+
+
+
+Use the fields on the `Configure Chart` dialog to specify general information about the chart:
+
+> - Specify the name of the chart in the `Name` field.
+> - Use the drop-down listbox in the `Category` field to specify the category in which this chart will be displayed; when adding a custom chart to a custom dashboard, the chart will be displayed for selection in the `Category` specified.
+> - Use the radio buttons in the `Type` field to specify if the chart will be a `Line chart` or a `Table`.
+> - Provide a description of the chart in the `Description` field. The description will be displayed to the user viewing the chart (on a custom dashboard) when they click the information icon.
+
+When you've completed the fields on the `Configure Chart` dialog, click `Next` to continue.
+
+
+
+Use the fields on the `Select Metrics` dialog to select the metrics that will be displayed on the chart:
+
+> - Use the `Metric level` drop-down listbox to specify the level of the PEM hierarchy from which you wish to select metrics. You can specify `Agent`, `Database`, or `Server`. Each level offers access to a unique set of probes and metrics.
+>
+> - Use the tree control in the `Available metrics` box to select the metrics that will be displayed on the chart.
+>
+> - If you are creating a table, you may only select metrics from one probe; each node of the tree control lists the metrics returned by a single probe. Expand a node of the tree control, and check the boxes to the left of a metric name to include that metric data in the table.
+> - If you are creating a line chart, expand the nodes of the tree control and double-click each metric that you would like to include in the chart.
+>
+> - Use the fields in the `Selected metrics` panel to specify how the metric data will be displayed in your chart. The selection panel displays the name of the metric in the (non-modifiable) `Metric [Probe]` column. You can:
+>
+> - Click the garbage can icon to delete a metric from the list of selected metrics.
+> - Use the drop-down listboxes in the `Selection Criteria` column to specify the order of the data displayed.
+> - Use the `Limit` field to specify the number of rows in a table or lines in a chart:
+>
+> > - The maximum number of lines allowed in a chart is 32.
+> > - The maximum number of rows allowed in a table is 100.
+>
+> - If you are creating a line chart, PEM supports comparisons of cross-hierarchy metrics.
+>
+> - Click the compare icon to open a selection box that allows you to select one or more probe-specific attributes (i.e. CPUs, interfaces, databases, etc.) to compare in the chart.
+> - Click the copy icon to apply your selections to all of the metrics for the same probe. When the popup opens, click `Yes` to confirm that other selections for the same probe will be overwritten, or `No` to exit the popup without copying the attributes.
+
+When you've completed the fields on the `Select Metrics` dialog, click `Next` to continue.
+
+
+
+Use the fields on the `Set Options` dialog to specify display options for your chart:
+
+> - Use the `Auto Refresh` field to specify the number of minutes between chart updates - choose a value from 1 to 120. The default auto refresh rate is 2 minutes.
+
+Use fields under the `Line chart options` heading to specify display preferences for a line chart:
+
+> - Use the `Points to plot` field to specify the maximum number of points that will be plotted on the chart.
+> - Use the fields to the right of the `Historical span` label to specify how much historical data should be displayed on the chart:
+> - Use the `Day(s)` field to specify the number of days of historical data that should be included on the chart.
+> - Use the `Hour(s)` field to specify the number of hours of historical data that should be included on the chart.
+> - Use the `Minute(s)` field to specify the number of minutes of historical data that should be included on the chart.
+> - Use the fields in the `Data extrapolation` box to specify if PEM should generate extrapolated data based on historical data.
+> - Click the `No Extrapolation` label to omit extrapolated data from the chart.
+> - Click the `Span` label to use the `Days` and `Hours` selectors to specify the period of time spanned by the metrics on the chart.
+> - Click the `Threshold` label to use threshold selectors to specify a maximum or minimum value for the chart.
+
+When you've completed the fields on the `Set Options` dialog, click `Next` to continue.
+
+
+
+Use the fields on the `Set Permissions` dialog to specify display options for your chart:
+
+> - Set the `Share with all` slider to `Yes` to indicate that the chart will be available to all authorized users, or `No` to restrict access to the users or groups specified in the `Access permissions` field.
+> - Use the `Access permissions` field to select the group or groups that will have access to the chart.
+
+When you've finished defining the chart, click `Finish` to save your edits and add your chart to the list on the `Manage Charts` tab:
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/02_pem_manage_charts_template.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/02_pem_manage_charts_template.mdx
new file mode 100644
index 00000000000..de458f29450
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/02_pem_manage_charts_template.mdx
@@ -0,0 +1,46 @@
+---
+title: "Importing a Capacity Manager Template"
+---
+
+
+
+
+Selecting the `Import Capacity Manager Template` from the `Manage Charts` tab's `Quick Links` section opens the `Create Chart` dialog, allowing you to select from your saved Capacity Manager templates. When the dialog opens, use the `Import capacity template` drop-down listbox to select the template you would like to use for your chart.
+
+
+
+Use the fields on the `Create Chart` dialog to provide information about the chart:
+
+- Specify the name of the chart in the `Name` field.
+- Use the drop-down listbox in the `Category` field to specify the category in which this chart will be displayed. When adding a custom chart to a custom dashboard, the chart will be displayed for selection in the `Category` specified.
+- Use the radio buttons in the `Type` field to specify if the chart will be a `Line chart` or a `Table`.
+- Provide a description of the chart in the `Description` field. The description will be displayed to the user viewing the chart (on a custom dashboard) when they click the information icon.
+
+Click `Next` to continue to the `Select Metrics` window.
+
+
+
+The `Select Metrics` window displays details about the metrics that are used by the template. When you've reviewed the metrics, click `Next` to continue to the `Set Options` window.
+
+
+
+Use the fields on the `Set Options` window to specify display options for your chart:
+
+- Use the `Auto Refresh` field to specify the number of minutes between chart updates - choose a value from 1 to 999. The default auto refresh rate is 2 minutes.
+
+- Use the fields in the `Data extrapolation` box to specify the time period covered by the chart. You can either:
+
+ > - click the `Historical days and extrapolated days` label and:
+ > - specify the number of days of historical data that should be charted in the `Historical` field.
+ > - specify the number of projected days that should be charted in the `Extrapolated` field.
+ > - or, click the `Historical days and threshold` label and:
+ > - provide the number of days of historical data that should be charted in the `Historical` field.
+ > - use the threshold selection fields to specify the threshold value at which the chart will end.
+
+When you've completed the `Set Options` window, click `Next` to continue.
+
+
+
+After making any required modifications to the chart definition, click `Finish` to save your edits. PEM will open a popup, confirming that the edits have been saved:
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/index.mdx
new file mode 100644
index 00000000000..03403d38846
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/10_pem_manage_charts/index.mdx
@@ -0,0 +1,39 @@
+---
+title: "Using the Manage Charts Tab"
+---
+
+
+
+
+You can use the `Manage Charts` tab to access dialogs that allow you to create or modify a custom line chart or table, or import a Capacity Manager template for use in a custom chart. After defining a chart, you can display the chart on a custom dashboard. To open the `Manage Charts` tab, select `Manage Charts...` from the PEM client `Management` menu.
+
+
+
+The `Manage Charts` tab provides a `Quick Links` menu that allows you to access dialogs to:
+
+> - [Create a New Chart](../04_toc_pem_features/10_pem_manage_charts/#pem_create_new_chart) for use on a custom dashboard.
+> - [Import a Capacity Manager template](../04_toc_pem_features/10_pem_manage_charts/#pem_manage_charts_template) to use as a template for creating a custom chart.
+
+The `Custom Charts` table displays a list of user-defined charts; when a chart is newly added, the font displays in green. When you add an additional chart or refresh the screen, the name of the chart is displayed in black.
+
+
+
+Use the search box in the upper-right hand corner of the `Custom Charts` section to search through your custom charts. Specify a:
+
+> - Chart name
+> - Type
+> - Level
+> - Metrics Category
+
+Use icons to the left of a charts name in the `Custom Charts` table to manage a chart:
+
+> - Click the edit icon to open the `Chart Configuration` wizard and modify aspects of the chart or table.
+> - Click the delete icon to delete the selected chart.
+
+Contents:
+
+
+
+pem\_create\_new\_chart pem\_manage\_charts\_template
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/01_pem_custom_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/01_pem_custom_dashboard.mdx
new file mode 100644
index 00000000000..1ce150128d1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/01_pem_custom_dashboard.mdx
@@ -0,0 +1,54 @@
+---
+title: "Creating a Custom Dashboard"
+---
+
+
+
+
+You can use the PEM dashboard editor to create or modify a user-defined dashboard. The custom dashboard may include pre-defined charts, user-defined charts or a mix of pre-defined and user-defined charts. To create a new dashboard, select `Create New Dashboard...` from the `Quick Links` section of the `Manage Dashboards` tab.
+
+
+
+Use the fields in the `Configure` section to specify general information about the dashboard:
+
+- Specify a name for the dashboard in the `Name` field. The name specified will also be the title of the dashboard if the title is displayed.
+- Use the `Level` drop-down listbox to specify the level of the PEM hierarchy within the PEM client on which the dashboard will be displayed. A dashboard may be accessed via the `Dashboards` menu on a `Global` level, an `Agent` level, the `Server` level or the `Database` level. Each selected level within the list will expose a different set of metrics on which the custom dashboard's charts may be based.
+- Provide a description of the dashboard in the `Description` field.
+
+Provide information in the fields in the `Ops dashboard options` box if the dashboard will be used as an Ops dashboard:
+
+- Set the `Ops Dashboard?` field to `Yes` to instruct the server to create a dashboard that is formatted for display on an [Ops monitor](../../04_toc_pem_features/11_pem_manage_dashboards/#pem_ops_dashboard).
+- Set the `Show Title?` field to `Yes` to display the dashboard name at the top of the Ops dashboard.
+- Use the `Font` drop-down list box to select a custom font style for the title. The selected font style will be displayed in the `Preview` box.
+- Use the `Font size` drop-down list box to select a custom font size for the title. The selected font style will be displayed in the `Preview` box.
+
+Use the `Permissions` box to specify the users that will be able to view the new dashboard:
+
+- Set the `Share with all` slider to `Yes` to instruct the server to allow all `Teams` to access the dashboard, or set `Share with all` to `No` to enable the `Access permissions` field.
+- Use the `Access permissions` field to specify which roles can view the new dashboard. Click in the field, and select from the list of users to add a role to the list of users with dashboard access.
+
+When you've completed the `Configure Dashboard` section, click the arrow in the upper-right corner to close the section, and access the `Dashboard Layout Design` section.
+
+
+
+Click the edit icon in a section header to specify a section name; then, click the add icon (+) to add a chart to the section.
+
+
+
+Use the arrows to the right of each chart category to display the charts available and select a chart.
+
+
+
+Use the chart detail selectors to specify placement details for the chart: \* Use the `Chart width` selector to indicate the width of the chart; select 50% to display the chart in half of the dashboard, or 100% to use the whole dashboard width. \* Use the `Chart alignment` selector to indicate the position of the chart within the section:
+
+> - Select `Left` to indicate that the chart should be left-justified.
+> - Select `Center` to indicate that the chart should be centered.
+> - Select `Right` to indicate that the chart should be right-justified.
+
+Please note that tables are always displayed centered.
+
+When creating or editing a custom dashboard, you can use drag and drop to re-arrange the charts within a section or to move a chart to a different section.
+
+To add another chart to your dashboard, click the add icon (+) in the section header. When you've finished editing the dashboard, click the `Save` button to save your edits and exit.
+
+To exit without saving your changes, click the `Cancel` button.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/02_pem_ops_dashboard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/02_pem_ops_dashboard.mdx
new file mode 100644
index 00000000000..488aa63ded5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/02_pem_ops_dashboard.mdx
@@ -0,0 +1,19 @@
+---
+title: "Creating an Ops Dashboard"
+---
+
+
+
+
+You can use the PEM [dashboard editor](../../04_toc_pem_features/11_pem_manage_dashboards/#pem_custom_dashboard) to create a custom dashboard formatted for display on an Ops monitor. An Ops dashboard displays the specified charts and graphs, while omitting header information and minimizing extra banners, titles, and borders.
+
+To create an Ops dashboard, provide detailed information about the Ops display in the `Ops dashboard options` section of the `Create Dashboard` dialog:
+
+
+
+- Set the `Ops Dashboard?` field to `Yes` to instruct the server to create a dashboard that is formatted for display on an Ops monitor.
+- Set the `Show Title?` field to `Yes` to display the dashboard name at the top of the Ops dashboard.
+- Use the `Font` drop-down list box to select a custom font style for the title. The selected font style will be displayed in the `Preview` box.
+- Use the `Font size` drop-down list box to select a custom font size for the title. The selected font style will be displayed in the `Preview` box.
+
+After adding charts and tables to the Ops dashboard, click the `Save` button to save your work. You can then access the dashboard by navigating through the `Dashboards` menu of the hierarchy level specified in the `Level` field on the `New Dashboard` dialog.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/index.mdx
new file mode 100644
index 00000000000..e16a4bb37a2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/11_pem_manage_dashboards/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "The PEM Manage Dashboards Tab"
+---
+
+
+
+
+PEM displays performance statistics through a number of system-defined dashboards; each dashboard contains a series of summary views that contain charts, graphs and tables that display statistics related to the selected object. You can use the Manage Dashboards tab to create and manage custom dashboards that display the information that is most relevant to your system.
+
+
+
+To create a custom dashboard, click the `Create New Dashboard` link (located in the `Quick Links section of the`Manage Dashboards`tab). To modify an existing dashboard, click the edit icon to the left of a dashboard name. The dashboard editor will open, displaying the definition of the dashboard. When you've finished modifying the dashboard's definition, click the`Save`button to preserve your changes; click`Cancel`to exit without saving your changes. To delete a dashboard, click the delete icon to the left of a dashboard name. A popup will ask you to confirm that you wish to delete the dashboard; click`OK\`\` to delete the selected dashboard.
+
+Contents:
+
+
+
+pem\_custom\_dashboard pem\_ops\_dashboard
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/01_pem_custom_probes.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/01_pem_custom_probes.mdx
new file mode 100644
index 00000000000..92832965e3e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/01_pem_custom_probes.mdx
@@ -0,0 +1,94 @@
+---
+title: "Custom Probes"
+---
+
+
+
+
+Use the `Custom Probes` tab to create a new probe or modify an existing probe. After creating or modifying a probe, you can incorporate the data gathered by custom probes into existing or new charts or graphs. To open the `Custom Probes` tab, select the `Manage Custom Probes` icon from the `Quick Links` section of the `Manage Probes` tab.
+
+
+
+Use the `Show system probes?` switch to display the system probes on the `Custom Probes` tab.
+
+To modify an existing probe, click the `Edit` icon located to the left of a probe name. To create a new probe, click the `Add` icon in the upper-right corner of the tab.
+
+
+
+Use the fields on the `General` tab to modify the definition of an existing probe or to specify the properties of a new probe.
+
+- Use the `Probe name` field to provide a name for a new probe.
+- Use the `Collection method` field to specify the probe type. Use the drop-down listbox to select from:
+
+> - `SQL` (the probe will gather information via a SQL statement)
+>
+> - `WMI` (the probe will gather information via a Windows Management Instrumentation extension)
+>
+> - `Batch/Shell Script` (the probe will use a command-script or shell-script to gather information).
+>
+> Before creating a batch probe on a Linux system, you must modify the `agent.cfg` file, setting the `allow_batch_probes` parameter equal to `true` and restart the PEM agent. The `agent.cfg` file is located in `/opt/PEM/agent/etc`.
+>
+> On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent`.
+>
+> Please note that batch probes are platform-specific. If you specify a collection method of `Batch`, you must specify a platform type in the `Platform` field.
+>
+> To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of agent.cfg file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. If pemagent is being run by a non-root user then the value of `batch_script_user` will be ignored and the script will be executed by the same non-root user that is being used for running the pemagent.
+
+- Use the `Target type` drop-down listbox to select the object type that the probe will monitor. `Target type` is disabled if `Collection method` is `WMI`.
+- Use the `Minutes` and `Seconds` selectors to specify how often the probe will collect data.
+- Use the `Probe enable?` switch to specify if the probe is enabled. Specify `Yes` to enable the probe, or `No` to specify that the probe is disabled.
+- Set the `Data retention` switch to `Yes` to specify the number of days that gathered information will be retained in the probe's history table.
+- Use the switch next to `Discard from history` to specify if the server should create a history table for the probe. Select `Yes` to discard probe history, or `No` to retain the probe history in a table.
+- Use the `Platform` drop-down listbox to specify the type of platform that the probe will monitor. This field is enabled only when the `Collection method` is `Batch`.
+
+
+
+Use the `Columns` tab to define the columns in which the probe data will be stored. Navigate to the Columns tab, and click the `Add` button (in the upper-right corner) to define a new column.
+
+- Provide a name for the column in the `Name` field.
+
+- The `Internal name` field is not enabled for user-defined probes.
+
+- Use the `Column type` drop-down listbox to specify if the column is a `Key` column (a primary key) or a `Non key` column. Non-key columns are generally metric items (values that can be graphed).
+
+- Use the `Data type` drop-down listbox to specify the type of data that will be stored in the column.
+
+- Use the `Unit` field to specify the unit of measure that applies to the metric stored in the column. This unit is displayed on the Y-Axis of a custom chart or a Capacity Manager chart. This is an optional field.
+
+- Use the `Graphable` switch to specify if the defined metric may be graphed, and that the probe should be accessible from the Capacity Manager or Manage Charts dialogs.
+
+- Use the `Is PIT` switch to specify if the metric is stored by point-in-time (by default).
+
+ 'Point-in-time' metrics are those metrics that change (increase or decrease) at any given point of time. For example, database size is a point-in-time metric; at any given point-in-time, the size of the database is fluctuating. Metrics that are not point-in-time (also referred to as cumulative metrics) are metrics whose size always increases over time. For example, Blocks Read and Tuples Read are cumulative metrics; the value stays the same or increases.
+
+- Use the `Calculate PIT` switch to specify that the server should calculate a point-in-time value for the metric data. `Calculate PIT` is disabled if `Is PIT` is `Yes`.
+
+PEM allows you to store point-in time-values of cumulative metrics as well. PEM subtracts the last collected value of a cumulative metric from the current value, and stores the difference as a point-in-time value.
+
+
+
+Use the `Code` tab to specify the default code that will be executed by the probe.
+
+- If the probe is a SQL probe, you must specify the SQL SELECT statement invoked by the probe on the `Code` tab. The column names returned by the query must match the `Internal Name` specified on the `Column` tab. The number of columns returned by the query, as well as the column name, datatype, etc. must match the information specified on the `Columns` tab.
+- If the probe is a Batch probe, you must specify the shell or .bat script that will be invoked when the probe runs. The output of the script should be as follows:
+
+> - The first line must contain the names of the columns provided on the `Columns` tab. Each column name should be separated by a tab (t) character.
+> - From the second line onwards, each line should contain the data for each column, separated by a tab character.
+> - If a specified column is defined as key column, make sure the script does not produce duplicate data for that column across lines of output.
+> - The number of columns specified in the `Columns` tab and their names, data type, etc. should match with the output of the script output.
+
+- If the probe is a WMI probe, you must specify the WMI query as a SELECT WMI query. The column name referenced in the SELECT statement should be same as the name of the corresponding column specified on the `Column` tab. The column names returned by the query must match the `Internal Name` specified on the `Column` tab. The number of columns returned by the query, as well as the column name, datatype, etc. must match the information specified on the `Columns` tab.
+
+
+
+Use the `Alternate Code` tab to provide code that will be invoked if the probe fires on a specific version of the server. To provide version-specific code, move the `Applies to all database server versions?` switch to `No`, and click the `Add` button. Then, use the `Database version(s)` drop-down listbox to select the version to which the code will apply. After selecting the version, click the `Edit` button (to the left of the version name) to provide the code that will execute when the probe fires.
+
+If you select a database version, and leave the `Probe code` column blank, PEM will invoke the code specified on the `Code` tab when the probe executes on a server that matches that version.
+
+When you've finished defining the probe, click the `Save` icon (in the corner of the `Custom Probes` tab) to save the definition, and make the probe data available for use on custom charts and graphs.
+
+**Deleting Probes**
+
+You may delete only user-defined probes. When you delete a probe, the probe is marked for deletion, and displayed in red font in the Custom Probes table. Probes marked for deletion will be deleted when you click the Save icon (preserving changes made on the Custom Probes tab). During the deletion the probe definition is deleted and any corresponding tables are dropped from the `pemdata` and `pemhistory` schemas.
+
+System probes are the built-in probes provided by PEM, and are part of the PEM schema. You may only modify system probes; if you attempt to delete a system probe, you will receive an error from PEM.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/02_copy_probe_config.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/02_copy_probe_config.mdx
new file mode 100644
index 00000000000..6f86646cbde
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/02_copy_probe_config.mdx
@@ -0,0 +1,16 @@
+---
+title: "Copy Probe Configuration"
+---
+
+
+
+
+You can use the `Copy Probe Configuration...` dialog to copy probe definitions from one monitored object to one or more monitored objects of the same type. To open the `Copy Probe Configuration...` dialog, highlight the object from which you are copying probes in the PEM client tree control, and select `Manage Probes...` from the `Management` menu. When the `Manage Probes` tab opens, click on `Copy Probe` to open the `Copy Probe Configuration` dialog:
+
+
+
+The dialog will copy the probe definitions from the object through which the `Copy Probe Configuration` dialog was opened, to the location(s) selected on the `Copy Probe Configuration` dialog tree control.
+
+Note that if you specify a parent node in the `Copy Probe Configuration` tree control, PEM will copy the probe configurations to each object (of the same type) that resides under that node in the tree control. For example, to copy the probe definitions from one schema to all schemas that reside within a database, you only need to select the parent database of the target schemas. Please note that a red warning symbol is displayed to the left of the name of a listed target object if that object is the source of the probe that is being copied.
+
+When you have selected the target object or objects, click the `Configure Probes` button to copy the probe definitions to the location selected on the dialog.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/01_pem_probes.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/01_pem_probes.mdx
new file mode 100644
index 00000000000..4128d30b707
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/01_pem_probes.mdx
@@ -0,0 +1,12 @@
+---
+title: "Probes"
+---
+
+
+
+
+A `probe` is a scheduled task that retrieves information about the database objects that are being monitored by the PEM agent. PEM uses the collected information to build the graphs displayed on each homepage. The `Manage Probes` tab (accessed via the `Management` menu) allows you to modify the data collection schedule and the length of time that PEM will retain information returned by a specific probe.
+
+Unless otherwise noted, Postgres Enterprise Manager enables the probes listed in the table below:
+
+| Probe Name | Information Monitored by Probe | Probe Configuration Level |
|---|---|---|
| Background Writer Statistics | This probe monitors information about the background writer. The information includes:
| Server |
| Blocked Session Information | This probe returns information about blocked sessions. | Server |
| CPU Usage | This probe monitors CPU Usage information. | Agent |
| Data and Log File Analysis | This probe monitors information about log files. The information includes:
| Server |
| Database Frozen XID | This probe monitors the frozen XID of each database. | Server |
| Database Size | This probe monitors information about the size of the monitored databases. The information includes:
| Server |
| Database Statistics | This probe monitors database statistics. The information includes:
| Server |
| Disk Busy Info | This probe monitors information about disk activity.
| Agent |
| Disk Space | This probe monitors information about disk space usage. The information includes:
| Agent |
| EDB Audit Configuration | This probe monitors the audit logging configuration of Postgres Plus Advanced Servers. | Server |
| Failover Manager Cluster Info | This probe monitors a Failover Manager cluster, returning information about the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server |
| Failover Manager Node Status | This probe monitors a Failover Manager cluster, returning detailed about each node within the cluster. This probe is disabled unless a cluster name and path of the Failover Manager binary is provided on the Server Properties dialog. | Server |
| Function Statistics | This probe monitors a database, retrieving information about functions. The information includes:
| Database |
| Index Size | This probe monitors a database, retrieving information about indexes. The information includes:
| Database |
| Index Statistics | This probe monitors index statistics. The information includes:
| Database |
| Installed Packages | This probe monitors the packages that are currently installed. The information gathered includes:
|
|
| IO Analysis | This probe monitors disk I/O information in. The information includes:
|
|
| Load Average | This probe monitors CPU load averages. The information includes:
| Agent |
| Lock Information | This probe monitors lock information. The information includes:
| Server |
| Memory Usage | This probe monitors information about system memory usage. The information includes:
| Agent |
| Network Statistics | This probe monitors network statistics. The information includes:
| Agent |
| Number of Prepared Transactions | This probe stores the number of prepared transactions. | Server |
| Number of WAL Files | This probe monitors the number of WAL files. | Server |
| Object Catalog: Database | This probe monitors a list of databases and their properties The information includes:
| Server |
| Object Catalog: Foreign Key | This probe monitors a list of foreign keys and their properties. The information includes:
| Schema |
| Object Catalog: Function | This probe monitors a list of functions and their properties. The information includes:
| Schema |
| Object Catalog: Index | This probe monitors a list of indexes and their properties. The information includes:
| Schema |
| Object Catalog: Schema | This probe monitors a list of schemas and their associated databases and servers. | Database |
| Object Catalog: Sequence | This probe monitors a list of sequences and their properties. | Schema |
| Object Catalog: Table | This probe monitors a list of table information. The information includes:
| Schema |
| Object Catalog: Tablespace | This probe monitors a list of tablespaces. | Server |
| Operating System Information | This probe monitors the operating system details and boot time. | Agent |
| Package Catalog | This probe monitors the packages that are currently available for installation. The information gathered includes:
| Agent |
| PG HBA Conf | This probe monitors authentication configuration information from the pg_hba.conf file. | Server |
| Server Information | This probe monitors information about servers. | Server |
| Session Information | This probe monitors session information. The information includes:
| Server |
| Settings | This probe monitors the values currently assigned to GUC variables. | Server |
| SQL Protect | This probe monitors a server, retrieving information about SQL injection attacks. | Server |
| Slony Replication | This probe monitors lag data for clusters replicated using Slony. | Database |
| Streaming Replication | This probe monitors a cluster that is using streaming replication, retrieving information about:
| Server |
| Streaming Replication Lag Time | This probe monitors a cluster that is using streaming replication, retrieving lag information about:
| Server |
| Streaming Replication Database Conflicts | This probe monitors a database that is using streaming replication, retrieving information about any conflicts that arise. This includes information about queries that have been canceled due to:
| Server |
| Table Bloat | This probe monitors information about the current table bloat. The information includes:
| Database |
| Table Frozen XID | This probe monitors the frozen XID of each table. | Schema |
| Table Size | This probe monitors information about table size. The information includes:
| Database |
| Table Statistics | This probe monitors table statistics. The information includes:
| Database |
| Tablespace Size | This probe monitors a list of tablespaces and their sizes. | Server |
| User Information | This probe monitors a list of the current users. The stored information includes:
| Server |
| WAL Archive Status | This probe monitors the status of the WAL archive. The stored information includes:
| Server |
| xDB Replication | This probe monitors lag data for clusters replicated using xDB replication. | Database |
+
+pem\_probes
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/index.mdx
new file mode 100644
index 00000000000..42847c56e23
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/12_pem_manage_probes/index.mdx
@@ -0,0 +1,33 @@
+---
+title: "The Manage Probes Tab"
+---
+
+
+
+
+A [probe](../04_toc_pem_features/12_pem_manage_probes/03_pem_probe_config/#pem_probes) is a scheduled task that returns a set of performance metrics about a specific monitored server, database, operating system or agent. You can use the Manage Probes tab to override the default configuration and customize the behavior of each probe. To open the Manage Probes tab, select `Manage Probes…` from the `Management` menu.
+
+
+
+The `Manage Probes` tab provides a set of `Quick Links` that you can use to create and manage probes:
+
+> - Click the `` `Manage Custom Probes `` <pem\_custom\_probes> icon to open the Custom Probes\` tab and create or modify a custom probe.
+> - Click the `` `Copy Probes `` <copy\_probe\_config> icon to open the Copy Probe\` dialog, and copy the probe configurations from the currently selected object to one or more monitored objects.
+
+A probe monitors a unique set of metrics for each specific object type (server, database, database object, or agent); select the name of an object in the tree control to review the probes for that object.
+
+To modify the properties associated with a probe, highlight the name of a probe, and customize the settings that are displayed in the `Probes` table:
+
+> - Move the `Default` switch in the `Execution Frequency` columns to `No` to enable the `Minutes` and `Seconds` selectors, and specify a non-default value for the length of time between executions of the probe.
+> - Move the `Default` switch in the `Enabled?` column to `No` to change the state of the probe, and indicate if the probe is active or not active.
+> - Move the `Default` switch in the `Data Retention` column to `No` to enable the `Day(s)` field and specify the number of days that information gathered by the probe is stored on the PEM server.
+
+The `Manage Probes` tab may also display information about probes that cannot be modified from the current node; if a probe cannot be modified from the current dialog, the switches for that probe are disabled. Generally, a disabled probe can be modified from a node that is higher in the hierarchy of the PEM client tree control. Select another object in the tree control to change which probes are displayed or enabled on the `Manage Probes` tab.
+
+Contents:
+
+
+
+pem\_custom\_probes copy\_probe\_config pem\_probe\_config
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/13_pem_alert_blackout.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/13_pem_alert_blackout.mdx
new file mode 100644
index 00000000000..f337f9f77ea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/13_pem_alert_blackout.mdx
@@ -0,0 +1,48 @@
+---
+title: "Schedule Alert Blackout"
+---
+
+
+
+
+You can use the `Schedule Alert Blackout` option on the `Management` menu to schedule an alert blackout for your Postgres servers and PEM Agents during maintenance. Alerts will not be raised during a defined blackout period.
+
+To schedule an alert blackout, click on the `Management` menu and select `Schedule Alert Blackout`.
+
+
+
+When the `Schedule Alert Blackout` dialog opens, use the tabs on the dialog to define the blackout period for servers and agents. Open the `Server` tab and click the Add icon (+) at the top right corner to add new row.
+
+
+
+Use the fields on the `Server` tab to provide information about a Server to blackout the alerts:
+
+- Use the `Start time` field to provide the date and time to start the alert blackout.
+- Use the `Duration` field to provide the interval for which you want to blackout the alerts.
+- Use the `Servers` field to provide the server name for which you want to blackout the alerts. You can also select multiple servers to blackout the alerts at same time.
+
+Once all the details are provided, you can save the details by clicking on `Save` button on the right bottom corner of the dialog. Once saved, it cannot be edited. The alerts will not be displayed on the Alerts dashboard for the scheduled interval of that particular server.
+
+You can also schedule a blackout period for PEM Agents via the `Agent` tab on the dialog. Open the `Agent` tab and click the Add icon (+) at the top right corner to add new row.
+
+
+
+Use the fields on the `Agent` tab to provide the information about an Agent to blackout the alerts:
+
+- Use the `Start time` field to provide the date and time to start the alert blackout.
+- Use the `Duration` field to provide the interval for which you want to blackout the alerts.
+- Use the `Agents` field to provide the Agent name for which you want to blackout the alerts. All server level alerts, for the servers bind to that particular agent will blackout.
+
+Once all the details are provided, you can save the details by clicking on `Save` button on the right bottom corner of the dialog. Once saved, it cannot be edited. The alerts will not be displayed on the Alert dashboard for the scheduled interval for that `PEM Agent`.
+
+You can use `Clone` button from the top right corner of dialog, to clone the scheduling of alert blackout. Select the servers or agents you want to clone and then click on `Clone` button to create the cloned copy of all the selected servers or agents. You can edit newly created schedules as needed, and then click `Save`.
+
+You can use `Delete` button from the top right corner of dialog to remove a scheduled alert blackout. Select the servers or agents and then click on highlighted `Delete` button in the right top corner to remove the scheduled alerts associated with that server or agent.
+
+
+
+Select a server for which you wish to delete the scheduled alert backout and then click on the `Delete` button. The server will ask for confirmation before deleting that row.
+
+
+
+You can use the `Reset` button to reset the details on the Alert Blackout dialog to the default settings. Please note that all saved blackouts will remain unaffected after resetting the current dialog values.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/14_pem_scheduled_system_jobs.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/14_pem_scheduled_system_jobs.mdx
new file mode 100644
index 00000000000..b05f16db511
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/14_pem_scheduled_system_jobs.mdx
@@ -0,0 +1,10 @@
+---
+title: "Scheduled System Jobs"
+---
+
+
+
+
+PEM defines system jobs to take care of cleanup activities at scheduled intervals. All of the system jobs are enabled by default, and are scheduled to deploy on a regular interval. You can query the `pem.job` table in the `pem` database to review a list of the system jobs. The current schedule for system jobs is stored in the `pem.schedule` table in the `pem` database.
+
+The system job names, their descriptions, and default deployment intervals are listed in the table below:
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/15_pem_scheduled_task_tab.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/15_pem_scheduled_task_tab.mdx
new file mode 100644
index 00000000000..59ace19d862
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/15_pem_scheduled_task_tab.mdx
@@ -0,0 +1,65 @@
+---
+title: "Scheduled Task Tab"
+---
+
+
+
+
+You can schedule the execution of user-defined tasks on registered servers for a time that is most convenient, and least intrusive to your users. Tasks may be one-off, or recurring and are comprised of one or more steps, which may be a SQL script, a batch/shell script, or an internal function in the PEM agent. You can view pending tasks on the *Scheduled Tasks tab.*
+
+To open the `Scheduled Tasks` tab, select either a PEM Agent or a managed server in the tree control of the PEM client and select `Scheduled Tasks...` from the `Management` menu.
+
+
+
+The tab features a legend, displaying the icons that identify the status of each task.
+
+The `Manage Tasks` table displays a list of tasks. Set `Show system tasks?` to `Yes` to display system tasks; if it is set to `No`, only user-defined tasks are displayed. System tasks are displayed with a grey background, and may not be modified.
+
+Use the `Refresh` icon to update the list of tasks displayed in the table. The table displays general information about each task.
+
+- The `Execution` drop-down provides access to detailed information about each step in the task.
+- The `Status` field lists the status of the current task.
+- The `Enabled?` switch displays `Yes` if the task is enabled; `No` if the task is disabled.
+- The `Name` field displays the name of the task.
+- The `Agent` or `Server` field displays the name of the agent responsible for executing the task or the server on which the task will execute.
+
+Highlight the name of a user-defined task and click the `Edit` icon (to the left of a task name) to access detailed information about the selected task.
+
+
+
+The `General` tab displays information about the scheduled task:
+
+- The `Status` field lists the status of the current task.
+- The `Enabled?` switch displays `Yes` if the task is enabled; `No` if the task is disabled.
+- The `Name` field displays the name of the task.
+- The `Agent` or `Server` field displays the name of the agent responsible for executing the task or the server on which the task will be performed.
+- The `Description` field displays a description of the task.
+- The `Last run` field displays the date and time of the last execution of the task.
+- The `Next run` field displays the date and time of the next scheduled execution of the task.
+- The `Created` field displays the date and time that the task was defined.
+
+Highlight the name of a user-defined task and open the `Steps` arrow to review a list of the steps within the task.
+
+
+
+The list of steps displays general information about each step in the task:
+
+- The `Execution date` field displays the date on which the step will execute. Step history is grouped by execution date; use the arrow to the left of an execution date to expand the node and review the task logs for that date.
+- The `Description` field displays a description of the step.
+
+Use the arrow to the left of an execution date (in the `Steps` column) to view detailed information about the step:
+
+- The `Step` field displays a description of the step.
+- The `Type` field displays the task type.
+- The `Status` field lists the status of the current task.
+- If applicable, the `Result` field displays code generated during the execution of the step.
+- The `Start/Next run` field displays the date and time at which the task executed or will execute again.
+- The `Duration` field displays the length of time that the task required for execution.
+- The `Output` field displays the result set returned by the execution of the task. By default, it displays the first 250 characters. You can also change the display characters by changing the `Schedule Tasks` options in the `Preference` dialog.
+- The `Log details` field allows you to open the log in the new browser window and also download the complete log.
+
+To delete a user-defined task, highlight the name of the task, and click the `Delete` icon located to the left of a task's name. The task will be marked for deletion, and removed when you click the `Save` icon (located in the upper-right corner of the `Manage Tasks` table.
+
+**Note:** Tasks with no `Next run` date will automatically be removed from the PEM server when the last run date is more than probe\_log\_retention\_time <pem\_config\_options> days ago.
+
+Please note that if any of the scheduled tasks for backup, restore, validate host, validate server or delete obsolete backup for any of the BART Server gets deleted, it will not display under the `BART Tool Activities` graph of BART Server's dashboard. However, it gets listed under the `Initiated Server Backups` list.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/16_pem_scheduled_jobs.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/16_pem_scheduled_jobs.mdx
new file mode 100644
index 00000000000..089ad24d9c6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/16_pem_scheduled_jobs.mdx
@@ -0,0 +1,132 @@
+---
+title: "Creating a PEM Scheduled Job"
+---
+
+
+
+
+You can create a PEM scheduled job to perform a set of custom-defined steps in the specified sequence. These steps may contain SQL code or a batch/shell script that you may run on a server that is bound with the agent. You can schedule these jobs to suit your business requirements. For example, you can create a job for taking a backup of a particular database server and schedule it to run on a specific date and time of every month.
+
+To create or manage a PEM scheduled job, use the PEM tree control to browse to the PEM agent for which you want to create the job. The tree control will display a Jobs node, under which currently defined jobs are displayed. To add a new job, right click on the Jobs node, and select Create Job... from the context menu.
+
+When the Create Agent Job dialog opens, use the tabs on the Create - Agent Job dialog to define the steps and schedule that make up a PEM scheduled job.
+
+
+
+Use the fields on the `General` tab to provide general information about a job:
+
+> - Provide a name for the job in the `Name` field.
+> - Move the `Enabled` switch to the `Yes` position to enable a job, or `No` to disable a job.
+> - Use the `Comment` field to store notes about the job.
+
+
+
+Use the `Steps` tab to define and manage the steps that the job will perform. Click the Add icon (+) to add a new step; then click the compose icon (located at the left side of the header) to open the step definition dialog:
+
+
+
+Use fields on the step definition dialog to define the step:
+
+> - Provide a name for the step in the `Name` field; please note that steps will be performed in alphanumeric order by name.
+> - Use the `Enabled` switch to include the step when executing the job (`True`) or to disable the step (`False`).
+> - Use the `Kind` switch to indicate if the job step invokes SQL code (`SQL`) or a batch script (`Batch`).
+>
+> > - If you select `SQL`, use the `Code` tab to provide SQL code for the step.
+> > - If you select `Batch`, use the `Code` tab to provide the batch script that will be executed during the step.
+>
+> Use the `On error` drop-down to specify the behavior of pgAgent if it encounters an error while executing the step. Select from:
+>
+> > - `Fail` - Stop the job if you encounter an error while processing this step.
+> > - `Success` - Mark the step as completing successfully, and continue.
+> > - `Ignore` - Ignore the error, and continue.
+>
+> - If you have selected SQL as your input for `Kind` switch, provide the following additional information:
+> - Use the `Server` field to specify the server that is bound with the agent for which you are creating the PEM scheduled job.
+> - Use the `Database` field to specify the database that is associated with the server that you have selected.
+> - Use the `Comment` field to provide a comment about the step.
+
+
+
+Use the context-sensitive field on the step definition dialog's `Code` tab to provide the SQL code or batch script that will be executed during the step:
+
+> - If the step invokes SQL code, provide one or more SQL statements in the `SQL query` field.
+> - If the step invokes a batch script, provide the script in the `Code` field. If you are running on a Windows server, standard batch file syntax must be used. When running on a Linux server, any shell script may be used, provided that a suitable interpreter is specified on the first line (e.g. *\#!/bin/sh*). Along with the defined inline code, you can also provide the path of any batch script, shell script, or SQL file on the filesystem.
+
+To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of agent.cfg file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. If pemagent is being run by a non-root user then the value of `batch_script_user` will be ignored and the script will be executed by the same non-root user that is being used for running the pemagent.
+
+To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` as true and restart the PEM agent. PEM registry entries are located in HKEY\_LOCAL\_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent.
+
+After providing all the information required by the step, click the `Save` button to save and close the step definition dialog.
+
+Click the add icon (+) to add each additional step, or select the `Schedules` tab to define the job schedule.
+
+
+
+
+
+Click the Add icon (+) to add a schedule for the job; then click the compose icon (located at the left side of the header) to open the schedule definition dialog:
+
+
+
+Use the fields on the Schedules definition tab to specify the days and times at which the job will execute.
+
+> - Provide a name for the schedule in the `Name` field.
+> - Use the `Enabled` switch to indicate that pgAgent should use the schedule (`Yes`) or to disable the schedule (`No`).
+> - Use the calendar selector in the `Start` field to specify the starting date and time for the schedule.
+> - Use the calendar selector in the `End` field to specify the ending date and time for the schedule.
+> - Use the `Comment` field to provide a comment about the schedule.
+
+Select the `Repeat` tab to define the days on which the schedule will execute.
+
+
+
+Use the fields on the `Repeat` tab to specify the details about the schedule in a cron-style format. The job will execute on each date or time element selected on the `Repeat` tab.
+
+Click within a field to open a list of valid values for that field; click on a specific value to add that value to the list of selected values for the field. To clear the values from a field, click the X located at the right-side of the field.
+
+Use the fields within the `Days` box to specify the days on which the job will execute:
+
+> - Use the `Week Days` field to select the days on which the job will execute.
+> - Use the `Month Days` field to select the numeric days on which the job will execute. Specify the `Last Day` to indicate that the job should be performed on the last day of the month, irregardless of the date.
+> - Use the `Months` field to select the months in which the job will execute.
+
+Use the fields within the `Times` box to specify the times at which the job will execute:
+
+> - Use the `Hours` field to select the hour at which the job will execute.
+> - Use the `Minutes` field to select the minute at which the job will execute.
+
+Select the `Exceptions` tab to specify any days on which the schedule will `not` execute.
+
+
+
+Use the fields on the `Exceptions` tab to specify days on which you wish the job to not execute; for example, you may wish for jobs to not execute on national holidays.
+
+Click the Add icon (+) to add a row to the exception table, then:
+
+> - Click within the `Date` column to open a calendar selector, and select a date on which the job will not execute. Specify `
+
+Note
+
+
+
+When you create the Job, the time fields under `Schedules` tab takes the timezone of the client machine. While saving the jobs on the PEM Server, the timezone gets converted according to PEM Server's timezone irrespective of PEM Agent's location.
+
+
+
+pem\_log\_view
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/19_monitoring_a_failover_manager_cluster.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/19_monitoring_a_failover_manager_cluster.mdx
new file mode 100644
index 00000000000..1d7181c217d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/19_monitoring_a_failover_manager_cluster.mdx
@@ -0,0 +1,57 @@
+---
+title: "Monitoring a Failover Manager Cluster"
+---
+
+
+
+
+You can configure PEM to display status information about one or more Failover Manager clusters on the Streaming Replication dashboard. Before configuring PEM to monitor a Failover Manager cluster, you must install and configure Streaming Replication and Failover Manager on the cluster.
+
+Please note that your Streaming Replication `standby.signal` file must include the following parameters:
+
+- primary\_conninfo
+- promote\_trigger\_file
+
+For information about installing and configuring Failover Manager and Streaming Replication, please see the EnterpriseDB Failover Manager Guide, available at www.enterprisedb.com.
+
+To configure PEM to monitor a Failover Manager cluster, use the PEM client to create a server definition for the primary node of the Failover Manager cluster. Use the tabs on the [New Server Registration](../01_toc_pem_getting_started/#pem_define_connection) dialog to specify general connection properties for the primary node; use fields on the `Advanced` tab to specify information about the Failover Manager cluster:
+
+- Use the `EFM Cluster Name` field to specify the name of the Failover Manager cluster. The cluster name is the prefix of the name of the cluster properties file. For example, if your cluster properties file is named `efm.properties`, your cluster name is `efm`.
+- Use the `EFM Installation Path` field to specify the location of the Failover Manager binary file. By default, the Failover Manager binary file is installed in `/usr/efm-x.x/bin`.
+
+After saving the server definition, the primary node will be included in the list of servers under the `PEM Server Directory` in the PEM client `Object browser` tree, and will be displayed on the `Global Overview` dashboard.
+
+To include Failover Manager information on the Streaming Analysis dashboard, you must enable the following probes for each node in the Failover Manager cluster:
+
+- Failover Manager Cluster Info
+- Failover Manager Node Status
+
+To enable a probe, right click on the node name, and select `Manage Probes` from the `Management` menu.
+
+To view the `Streaming Replication Analysis` dashboard and the status of the Failover Manager cluster, right click on the name of the primary node in the `Object browser` tree control and navigate through the `Dashboards` menu to select [Streaming Replication Analysis](../04_toc_pem_features/01_dashboards/#str_replication_dashboard).
+
+## Promoting a Cluster
+
+Select the `Replace Cluster Primary` from `Server` under the `Tools` menu to start the failover process. When you select `Replace Cluster Primary`, a popup opens, asking you to confirm that you wish to replace the current primary node:
+
+
+
+Select `No` to exit the popup without replacing the current primary node.
+
+Select `Yes` to remove the current primary node from the Failover Manager cluster and promote a replica node to the role of read/write primary node within a Failover Manager cluster. The node with the highest promotion priority (defined in Failover Manager) will become the new primary node. PEM will display a dialog, reporting the job status.
+
+
+
+When the job completes and the Streaming Replication Analysis dashboard refreshes, you can review the `Failover Manager Node Status` table to confirm that a replica node has been promoted to the role of primary within the Failover Manager cluster.
+
+### Switchover EFM Cluster
+
+You can use the PEM client to switchover the primary node of a Failover Manager cluster with a replica node. To initiate the switchover process, select Switchover EFM Cluster from the Tools menu. A dialog opens, asking you to confirm that you wish to switchover EFM cluster.
+
+
+
+Select `Yes` to switchover EFM cluster from the Failover Manager cluster and promote a replica node to the role of read/write primary node and reconfigure the primary database as a new replica within a Failover Manager cluster. The node with the highest promotion priority (defined in Failover Manager) will become the new primary node. PEM will display a dialog, reporting the job status.
+
+
+
+When the job completes and the Streaming Replication Analysis dashboard refreshes, you can review the `Failover Manager Node Status` table to confirm that a switchover within the Failover Manager cluster.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/20_performance_diagnostic.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/20_performance_diagnostic.mdx
new file mode 100644
index 00000000000..86261cc767a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/04_toc_pem_features/20_performance_diagnostic.mdx
@@ -0,0 +1,104 @@
+---
+title: "Performance Diagnostic"
+---
+
+
+
+
+You can use the Performance Diagnostic dashboard to analyze the database performance for Postgres instances by monitoring the wait events. To display the diagnostic graphs, PEM uses the data collected by EDB Wait States module.
+
+Peformance Diagnostic feature is supported for Advanced Server databases from PEM 7.6 version onwards and for PostgreSQL databases it is supported from PEM 8.0 onwards.
+
+
+
+
+
+For more information on EDB Wait States, see [EDB Postgres Advanced Server Guide](https://www.enterprisedb.com/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/latest/performance_analysis_and_tuning.html#edb-wait-states).
+
+You can analyze the Wait States data on multiple levels by narrowing down your selection of data. Each level of the graph is populated on the basis of your selection of data at the higher level.
+
+Prerequisite:
+
+- For PostgreSQL, you need to install `edb_wait_states_
+
+Note
+
+
+
+For PostgreSQL databases, Performance Diagnostics is supported only for versions 10, 11, and 12 installed on the supported CentOS or RHEL platforms.
+
+
+
+dashboards pem\_server\_config
+
+
+
+PEM configuration wizards simplify the process of configuring logging; after logs are gathered, you can use PEM features like the PEM Log Analysis Expert and Tuning Wizard to help you skillfully analyze log file contents. Postgres Expert analyses server configuration, and recommends changes that may improve performance, security, or reliability. Capacity Manager uses statistical data to analyze historical usage, and extrapolate future usage statistics for monitored objects.
+
+Contents:
+
+
+
+log\_manager audit\_manager pem\_log\_analysis\_expert tuning\_wizard pem\_postgres\_expert capacity\_manager
+
+
+
+PEM is highly customizable. You can modify system-defined alerts, or create custom alerts that notify a responsible administrator or group during a specific time period. PEM charts and dashboards are designed to provide an at-a-glance overview of the state of your systems, but you can design custom charts that display the most useful combinations of metric data returned by PEM probes. Then, create custom dashboards with details that `you` need to identify problems, plan for resource usage, or diagnose unique performance issues.
+
+Contents:
+
+
+
+pem\_alerting pem\_manage\_charts pem\_manage\_dashboards pem\_manage\_probes
+
+
+
+PEM can schedule jobs on monitored servers. you can use the wizards to schedule the setup to occur at a time when server usage is low, or when a system restart won't interrupt your users. The Scheduled Task tab provides an overview of all the tasks that are pending execution or that have recently completed on your servers. Performance diagnostic feature helps you analyze the database performance for Advanced Server instances by monitoring the wait events.
+
+Contents:
+
+
+
+pem\_alert\_blackout pem\_scheduled\_system\_jobs pem\_scheduled\_task\_tab pem\_scheduled\_jobs pem\_job\_notification pem\_task\_view monitoring\_a\_failover\_manager\_cluster performance\_diagnostic
+
+
+
+PEM can generate system configuration and core usage reports of locally or remotely monitored servers in HTML as well as in JSON format.
+
+Contents:
+
+
+
+reports
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/01_grant_wizard.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/01_grant_wizard.mdx
new file mode 100644
index 00000000000..cef8d921668
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/01_grant_wizard.mdx
@@ -0,0 +1,52 @@
+---
+title: "Grant Wizard"
+---
+
+
+
+
+The `Grant Wizard` tool is a graphical interface that allows you to manage the privileges of one or more database objects in a point-and-click environment. A search box, dropdown lists, and checkboxes facilitate quick selections of database objects, roles and privileges.
+
+The wizard organizes privilege management through a sequence of windows: `Object Selection (step 1 of 3)`, `Privileges Selection (step 2 of 3)` and `Final (Review Selection) (step 3 of 3)`. The `Final (Review Selection)` window displays the SQL code generated by wizard selections.
+
+To launch the `Grant Wizard` tool, select a database object in the `Browser` tree control, then navigate through `Tools` on the menu bar to click on the `Grant Wizard` option.
+
+
+
+Use the fields in the `Object Selection (step 1 of 3)` window to select the object or objects on which you are modifying privileges. Use the `Search by object type or name` field to locate a database object, or use the scrollbar to scroll through the list of all accessible objects.
+
+- Each row in the table lists object identifiers; check the checkbox in the left column to include an object as a target of the Grant Wizard. The table displays:
+
+ > - The object type in the `Object Type` field
+ > - The schema in which the object resides in the `Schema` field
+ > - The object name in the `Name` field.
+
+Click the `Next` button to continue, or the `Cancel` button to close the wizard without modifying privileges.
+
+
+
+Use the fields in the `Privileges Selection (step 2 of 3)` window to grant privileges. If you grant a privilege WITH GRANT OPTION, the Grantee will have the right to grant privileges on the object to others. If WITH GRANT OPTION is subsequently revoked, any role who received access to that object from that Grantee (directly or through a chain of grants) will lose thier privileges on the object.
+
+- Click the `Add` icon (+) to assign a set of privileges.
+- Select the name of the role from the drop-down listbox in the `Grantee` field.
+- Click inside the `Privileges` field. Check the boxes to the left of one or more privileges to grant the selected privileges to the specified user. If privileges have previously been granted on a database object, unchecking a privilege for a group or user will result in revoking that privilege.
+- The current user, who is the default grantor for granting the privilege, is displayed in the `Grantor` field.
+- Click the `Add` icon (+) to assign a set of privileges to another role; to discard a privilege, click the trash icon to the left of the row and confirm deletion in the `Delete Row` dialog.
+
+For more information about granting privileges on database objects, see the [PostgreSQL core documentation](http://www.postgresql.org/docs/9.5/static/sql-grant.html).
+
+Click the `Next` button to continue, the `Back` button to select or deselect additional database objects, or the `Cancel` button to close the wizard without modifying privileges.
+
+Your entries in the `Grant Wizard` tool generate a SQL command; you can review the command in the `Final (Review Selection) (step 3 of 3)` window (see an example below).
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Grant Wizard` tool:
+
+
+
+The commands displayed assign a role named `Bob` `INSERT` and `UPDATE` privileges `WITH GRANT OPTION` on the `sales_meetings` and the `sales_territories` tables.
+
+- Click the `Back` button to select or deselect additional database objects, roles and privileges.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Finish` button to save selections and exit the wizard.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/02_add_restore_point_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/02_add_restore_point_dialog.mdx
new file mode 100644
index 00000000000..a085523150a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/02_add_restore_point_dialog.mdx
@@ -0,0 +1,17 @@
+---
+title: "Add named restore point Dialog"
+---
+
+
+
+
+Use the `Add named restore point` dialog to take a named snapshot of the state of the server for use in a recovery file. To create a named restore point, the server's postgresql.conf file must specify a `wal_level` value of `replica`, or `logical`. You must be a database superuser to create a restore point.
+
+
+
+When the `Restore point name` window launches, use the field `Enter the name of the restore point to add` to provide a descriptive name for the restore point.
+
+For more information about using a restore point as a recovery target, please see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY-TARGET).
+
+- Click the `OK` button to save the restore point.
+- Click the `Cancel` button to exit without saving work.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/03_import_export_data.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/03_import_export_data.mdx
new file mode 100644
index 00000000000..8595c646c6f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/03_import_export_data.mdx
@@ -0,0 +1,67 @@
+---
+title: "Import/Export data Dialog"
+---
+
+
+
+
+Use the `Import/Export data` dialog to copy data from a table to a file, or copy data from a file into a table.
+
+The `Import/Export data` dialog organizes the import/export of data through the `Options` and `Columns` tabs.
+
+
+
+Use the fields in the `Options` tab to specify import and export preferences:
+
+- Move the `Import/Export` switch to the `Import` position to specify that the server should import data to a table from a file. The default is `Export`.
+
+- Use the fields in the `File Info` field box to specify information about the source or target file:
+
+ > - Enter the name of the source or target file in the `Filename` field. Optionally, select the `Browser` icon (ellipsis) to the right to navigate into a directory and select a file.
+ > - Use the drop-down listbox in the `Format` field to specify the file type. Select:
+ > - `binary` for a .bin file.
+ > - `csv` for a .csv file.
+ > - `text` for a .txt file.
+ > - Use the drop-down listbox in the `Encoding` field to specify the type of character encoding.
+
+
+
+- Use the fields in the `Miscellaneous` field box to specify additional information:
+
+ > - Move the `OID` switch to the `Yes` position to include the `OID` column. The `OID` is a system-assigned value that may not be modified. The default is `No`.
+ > - Move the `Header` switch to the `Yes` position to include the table header with the data rows. If you include the table header, the first row of the file will contain the column names.
+ > - If you are exporting data, specify the delimiter that will separate the columns within the target file in the `Delimiter` field. The separating character can be a colon, semicolon, a vertical bar, or a tab.
+ > - Specify a quoting character used in the `Quote` field. Quoting can be applied to string columns only (i.e. numeric columns will not be quoted) or all columns regardless of data type. The character used for quoting can be a single quote or a double quote.
+ > - Specify a character that should appear before a data character that matches the `QUOTE` value in the `Escape` field.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the fields in the `Columns` tab to select the columns that will be imported or exported:
+
+- Click inside the `Columns to export/import` field to deselect one or more columns from the drop-down listbox. To delete a selection, click the `x` to the left of the column name. Click an empty spot inside the field to access the drop-down list.
+- Use the `NULL Strings` field to specify a string that will represent a null value within the source or target file.
+- If enabled, click inside the `Not null columns` field to select one or more columns that will not be checked for a NULL value. To delete a column, click the `x` to the left of the column name.
+
+After completing the `Import/Export data` dialog, click the `OK` button to perform the import or export. PEM will inform you when the background process completes:
+
+
+
+Use the **Stop Process** button to stop the Import/Export process.
+
+Use the `Click here for details` link on the notification to open the `Process Watcher` and review detailed information about the execution of the command that performed the import or export:
+
+
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/01_maintenance_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/01_maintenance_dialog.mdx
new file mode 100644
index 00000000000..c78bc2f6ffb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/01_maintenance_dialog.mdx
@@ -0,0 +1,40 @@
+---
+title: "Maintenance Dialog"
+---
+
+
+
+
+Use the `Maintenance` dialog to VACUUM, ANALYZE, REINDEX or CLUSTER a database or selected database objects.
+
+
+
+While this utility is useful for ad-hoc maintenance purposes, you are encouraged to perform automatic VACUUM jobs on a regular schedule.
+
+Select a button next to `Maintenance operation` to specify the type of maintenance:
+
+- Click `VACUUM` to scan the selected database or table to reclaim storage used by dead tuples.
+
+ > - Move the `FULL` switch to the `Yes` position to compact tables by writing a completely new version of the table file without dead space. The default is `No`.
+ > - Move the `FREEZE` switch to the `Yes` position to freeze data in a table when it will have no further updates. The default is `No`.
+ > - Move the `ANALYZE` switch to the `Yes` position to issue ANALYZE commands whenever the content of a table has changed sufficiently. The default is `No`.
+
+- Click `ANALYZE` to update the stored statistics used by the query planner. This enables the query optimizer to select the fastest query plan for optimal performance.
+
+- Click `REINDEX` to rebuild any index in case it has degenerated due to the insertion of unusual data patterns. This happens, for example, if you insert rows with increasing index values, and delete low index values.
+
+- Click `CLUSTER` to instruct PostgreSQL to cluster the selected table.
+
+To exclude status messages from the process output, move the `Verbose Messages` switch to the `No` position; by default, status messages are included.
+
+When you've completed the dialog, click `OK` to start the background process; to exit the dialog without performing maintenance operations, click `Cancel`.
+
+pgAdmin will inform you when the background process completes:
+
+
+
+Use the **Stop Process** button to stop the Maintenance process.
+
+Use the `Click here for details` link on the notification to open the `Process Watcher` and review detailed information about the execution of the command that performed the import or export:
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/index.mdx
new file mode 100644
index 00000000000..0edb7e192ea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/04_maintenance/index.mdx
@@ -0,0 +1,38 @@
+---
+title: "Maintain a database object"
+---
+
+
+
+
+
+
+This tool allows to maintain the database in total, or only a selected table, or a selected index.
+
+Maintenance comes in three flavors.
+
+## VACUUM
+
+VACUUM will scan the database or table for rows, that are not in use any more. If a row is updated or deleted, the previous content isn't replaced, but rather marked invalid. The new data is inserted freshly into the database. You need to perform a garbage collection regularly, to insure that your database doesn't contain too much unused data, wasting disk space and ultimately degrading performance.
+
+Please press the Help button to see the PostgreSQL help about the VACUUM command to learn more about the options.
+
+The output of the database server is displayed in the messages page as they arrive. If Verbose is selected, the server will send very detailed info about what it did.
+
+While this tool is very handy for ad-hoc maintenance purposes, you are encouraged to install an automatic job, that performs a VACUUM job regularly to keep your database in a neat state.
+
+## ANALYZE
+
+ANALYZE investigates statistical values about the selected database or table. This enables the query optimizer to select the fastest query plan, to give optimal performance. Every time your data is changing radically, you should perform this task. It can be included in a VACUUM run, using the appropriate option.
+
+## REINDEX
+
+REINDEX rebuilds the indexes in case these have degenerated caused by unusual data patterns inserted. This can happen for example if you insert many rows with increasing index values, and delete low index values.
+
+The RECREATE option doesn't call the REINDEX SQL command internally, instead it drops the existing table and recreates it according to the current index definition.This doesn't lock the table exclusively, as REINDEX does, but will lock write access only.
+
+
+
+Note
+
+
+
+You can click on the  icon in the process watcher window to open the file location in the Storage Manager. You can use the [Storage Manager](../05_toc_pem_management_basics/#storage_manager) to download the backup file on the client machine .
+
+
+
+maintenance\_dialog
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/05_storage_manager.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/05_storage_manager.mdx
new file mode 100644
index 00000000000..d9584df4050
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/05_storage_manager.mdx
@@ -0,0 +1,48 @@
+---
+title: "Storage Manager"
+---
+
+
+
+
+*Storage Manager* is a feature that helps you manage your systems storage device. You can use *Storage Manager* to:
+
+- Download, upload, or manage operating system files.
+- Download *backup* or *export* files (custom, tar and plain text format) on a client machine.
+- Download *export* dump files of tables.
+
+You can access *Storage Manager* from the *Tools* Menu.
+
+
+
+Use icons on the top of the *Storage Manager* window to manage storage:
+
+Use the `Home` icon  to return to the home directory.
+
+Use the `Up Arrow` icon  to return to the previous directory.
+
+Use the `Refresh` icon  to display the most-recent files available.
+
+Select the `Download` icon  to download the selected file.
+
+Select the `Delete` icon  to delete the selected file or folder.
+
+Select the `Edit` icon  to rename a file or folder.
+
+Use the `Upload` icon  to upload a file.
+
+Use the `New Folder` icon  to add a new folder.
+
+Use the `Grid View` icon  to display all the files and folders in a grid view.
+
+Use the `Table View` icon  to display all the files and folders in a list view.
+
+Click on the check box next to *Show hidden files and folders* at the bottom of the window to view hidden files and folders.
+
+Use the *Format* drop down list to select the format of the files to be displayed; choose from *sql*, *csv*, or *All Files*.
+
+You can also download backup files through *Storage Manager* at the successful completion of the backups taken through [Backup Dialog](../05_toc_pem_management_basics/#backup_dialog), [Backup Global Dialog](../05_toc_pem_management_basics/#backup_globals_dialog), or [Backup Server Dialog](../05_toc_pem_management_basics/#backup_server_dialog).
+
+At the successful completion of a backup, click on the icon to open the current backup file in *Storage Manager* on the *process watcher* window.
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/06_backup_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/06_backup_dialog.mdx
new file mode 100644
index 00000000000..58e8d649aa6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/06_backup_dialog.mdx
@@ -0,0 +1,112 @@
+---
+title: "Backup Dialog"
+---
+
+
+
+
+`PEM` uses the *pg\_dump* utility to provide an easy way to create a backup in a plain-text or archived format. You can then use a client application (like `psql` or the `Query Tool`) to restore a plain-text backup file, or use the Postgres `pg_restore` utility to restore an archived backup. The `pg_dump` utility must have read access to all database objects that you want to back up.
+
+You can backup a single table, a schema, or a complete database. Select the name of the backup source in the `Browser` tree control, right click to open the context menu, and select `Backup...` to open the `Backup` dialog. The name of the object selected will appear in the dialog title bar.
+
+
+
+Use the fields in the `General` tab to specify parameters for the backup:
+
+- Enter the name of the backup file in the `Filename` field. Optionally, select the `Browser` icon (...) to the right to navigate into a directory and select a file that will contain the archive.
+
+- Use the drop-down listbox in the `Format` field to select the format that is best suited for your application. Each format has advantages and disadvantages:
+
+ > - Select `Custom` to create a custom archive file that you can use with `pg_restore` to create a copy of a database. Custom archive file formats must be restored with `pg_restore`. This format offers the opportunity to select which database objects to restore from the backup file. `Custom` archive format is recommended for medium to large databases as it is compressed by default.
+ > - Select `Tar` to generate a tar archive file that you can restore with `pg_restore`. The tar format does not support compression.
+ > - Select `Plain` to create a plain-text script file. A plain-text script file contains SQL statements and commands that you can execute at the `psql` command line to recreate the database objects and load the table data. A plain-text backup file can be edited in a text editor, if desired, before using the `psql` program to restore database objects. `Plain` format is normally recommended for smaller databases; script dumps are not recommended for blobs. The SQL commands within the script will reconstruct the database to the last saved state of the database. A plain-text script can be used to reconstruct the database on another machine, or (with modifications) on other architectures.
+ > - Select `Directory` to generate a directory-format archive suitable for use with `pg_restore`. This file format creates a directory with one file for each table and blob being dumped, plus a `Table of Contents` file describing the dumped objects in a machine-readable format that `pg_restore` can read. This format is compressed by default.
+
+- Use the `Compression Ratio` field to select a compression level for the backup. Specify a value of zero to mean use no compression; specify a maximum compression value of 9. Please note that tar archives do not support compression.
+
+- Use the `Encoding` drop-down listbox to select the character encoding method that should be used for the archive.
+
+- Use the `Number of Jobs` field (when applicable) to specify the number of tables that will be dumped simultaneously in a parallel backup.
+
+- Use the dropdown listbox next to `Rolename` to specify the role that owns the backup.
+
+Click the `Dump options` tab to continue. Use the box fields in the `Dump options` tab to provide options for `pg_dump`.
+
+
+
+- Move switches in the **Sections** field box to select a portion of the object that will be backed up.
+
+ > - Move the switch next to `Pre-data` to the `Yes` position to include all data definition items not included in the data or post-data item lists.
+ > - Move the switch next to `Data` to the `Yes` position to backup actual table data, large-object contents, and sequence values.
+ > - Move the switch next to `Post-data` to the `Yes` position to include definitions of indexes, triggers, rules, and constraints other than validated check constraints.
+
+
+
+- Move switches in the **Type of objects** field box to specify details about the type of objects that will be backed up.
+
+ > - Move the switch next to `Only data` to the `Yes` position to limit the back up to data.
+ > - Move the switch next to `Only schema` to limit the back up to schema-level database objects.
+ > - Move the switch next to `Blobs` to the `No` position to exclude large objects in the backup.
+
+
+
+- Move switches in the **Do not save** field box to select the objects that will not be included in the backup.
+
+ > - Move the switch next to `Owner` to the `Yes` position to exclude commands that set object ownership.
+ > - Move the switch next to `Privilege` to the `Yes` position to exclude commands that create access privileges.
+ > - Move the switch next to `Tablespace` to the `Yes` position to exclude tablespaces.
+ > - Move the switch next to `Unlogged table data` to the `Yes` position to exclude the contents of unlogged tables.
+ > - Move the switch next to `Comments` to the `Yes` position to exclude commands that set the comments. **Note:** This option is visible only for database server greater than or equal to 11.
+
+
+
+- Move switches in the **Queries** field box to specify the type of statements that should be included in the backup.
+
+ > - Move the switch next to `Use Column Inserts` to the `Yes` position to dump the data in the form of INSERT statements and include explicit column names. Please note: this may make restoration from backup slow.
+ > - Move the switch next to `Use Insert commands` to the `Yes` position to dump the data in the form of INSERT statements rather than using a COPY command. Please note: this may make restoration from backup slow.
+ > - Move the switch next to `Include CREATE DATABASE statement` to the `Yes` position to include a command in the backup that creates a new database when restoring the backup.
+ > - Move the switch next to `Include DROP DATABASE statement` to the `Yes` position to include a command in the backup that will drop any existing database object with the same name before recreating the object during a backup.
+ > - Move the switch next to `Load Via Partition Root` to the `Yes` position, so when dumping a COPY or INSERT statement for a partitioned table, target the root of the partitioning hierarchy which contains it rather than the partition itself. **Note:** This option is visible only for database server greater than or equal to 11.
+
+
+
+- Move switches in the **Disable** field box to specify the type of statements that should be excluded from the backup.
+
+ > - Move the switch next to `Trigger` (active when creating a data-only backup) to the `Yes` position to include commands that will disable triggers on the target table while the data is being loaded.
+ > - Move the switch next to `$ quoting` to the `Yes` position to enable dollar quoting within function bodies; if disabled, the function body will be quoted using SQL standard string syntax.
+
+
+
+- Move switches in the **Miscellaneous** field box to specify miscellaneous backup options.
+
+ > - Move the switch next to `With OIDs` to the `Yes` position to include object identifiers as part of the table data for each table.
+ > - Move the switch next to `Verbose messages` to the `No` position to instruct `pg_dump` to exclude verbose messages.
+ > - Move the switch next to `Force double quotes on identifiers` to the `Yes` position to force the quoting of all identifiers.
+ > - Move the switch next to `Use SET SESSION AUTHORIZATION` to the `Yes` position to include a statement that will use a SET SESSION AUTHORIZATION command to determine object ownership (instead of an ALTER OWNER command).
+
+When you’ve specified the details that will be incorporated into the pg\_dump command:
+
+- Click the `Backup` button to build and execute a command that builds a backup based on your selections on the `Backup` dialog.
+- Click the `Cancel` button to exit without saving work.
+
+
+
+Use the **Stop Process** button to stop the Backup process.
+
+If the backup is successful, a popup window will confirm success. Click *More details* on the popup window to launch the *Process Watcher*. The *Process Watcher* logs all the activity associated with the backup and provides additional information for troubleshooting.
+
+
+
+If the backup is unsuccessful, you can review the error messages returned by the backup command on the `Process Watcher`.
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/07_backup_globals_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/07_backup_globals_dialog.mdx
new file mode 100644
index 00000000000..1021a858415
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/07_backup_globals_dialog.mdx
@@ -0,0 +1,44 @@
+---
+title: "Backup Globals Dialog"
+---
+
+
+
+
+Use the `Backup Globals` dialog to create a plain-text script that recreates all of the database objects within a cluster, and the global objects that are shared by those databases. Global objects include tablespaces, roles, and object properties. You can use the PEM `Query Tool` to play back a plain-text script, and recreate the objects in the backup.
+
+
+
+Use the fields in the `General` tab to specify the following:
+
+- Enter the name of the backup file in the `Filename` field. Optionally, select the `Browser` icon (ellipsis) to the right to navigate into a directory and select a file that will contain the archive.
+- Use the drop-down listbox next to `Role name` to specify a role with connection privileges on the selected server. The role will be used for authentication during the backup.
+
+Move switches in the **Miscellaneous** field box to specify the type of statements that should be included in the backup.
+
+- Move the `Verbose messages` switch to the `No` position to exclude status messages from the backup. The default is `Yes`.
+- Move the `Force double quote on identifiers` switch to the `Yes` position to name identifiers without changing case. The default is `No`.
+
+Click the `Backup` button to build and execute a command based on your selections; click the `Cancel` button to exit without saving work.
+
+
+
+Use the **Stop Process** button to stop the Backup process.
+
+If the backup is successful, a popup window will confirm success. Click `Click here for details` on the popup window to launch the `Process Watcher`. The `Process Watcher` logs all the activity associated with the backup and provides additional information for troubleshooting.
+
+
+
+If the backup is unsuccessful, review the error message returned by the `Process Watcher` to resolve any issue.
+
+
+
+Note
+
+
+
+You can click on the  icon in the process watcher window to open the file location in the Storage Manager. You can use the [Storage Manager](../05_toc_pem_management_basics/#storage_manager) to download the backup file on the client machine .
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/08_backup_server_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/08_backup_server_dialog.mdx
new file mode 100644
index 00000000000..afab3e8d32e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/08_backup_server_dialog.mdx
@@ -0,0 +1,81 @@
+---
+title: "Backup Server Dialog"
+---
+
+
+
+
+Use the `Backup Server` dialog to create a plain-text script that will recreate the selected server. You can use the PEM `Query Tool` to play back a plain-text script, and recreate the server.
+
+
+
+Use the fields in the `General` tab to specify the following:
+
+- Enter the name of the backup file in the `Filename` field. Optionally, select the `Browser` icon (ellipsis) to the right to navigate into a directory and select a file that will contain the archive.
+- Use the `Encoding` drop-down listbox to select the character encoding method that should be used for the archive. **Note:** This option is visible only for database server greater than or equal to 11.
+- Use the drop-down listbox next to `Role name` to specify a role with connection privileges on the selected server. The role will be used for authentication during the backup.
+
+
+
+- Move switches in the **Type of objects** field box to specify details about the type of objects that will be backed up.
+
+ > - Move the switch next to `Only data` to the `Yes` position to limit the back up to data.
+ > - Move the switch next to `Only schema` to limit the back up to schema-level database objects.
+
+
+
+- Move switches in the **Do not save** field box to select the objects that will not be included in the backup.
+
+ > - Move the switch next to `Owner` to the `Yes` position to exclude commands that set object ownership.
+ > - Move the switch next to `Privilege` to the `Yes` position to exclude commands that create access privileges.
+ > - Move the switch next to `Tablespace` to the `Yes` position to exclude tablespaces.
+ > - Move the switch next to `Unlogged table data` to the `Yes` position to exclude the contents of unlogged tables.
+ > - Move the switch next to `Comments` to the `Yes` position to exclude commands that set the comments. **Note:** This option is visible only for database server greater than or equal to 11.
+
+
+
+- Move switches in the **Queries** field box to specify the type of statements that should be included in the backup.
+
+ > - Move the switch next to `Use Column Inserts` to the `Yes` position to dump the data in the form of INSERT statements and include explicit column names. Please note: this may make restoration from backup slow.
+ > - Move the switch next to `Use Insert commands` to the `Yes` position to dump the data in the form of INSERT statements rather than using a COPY command. Please note: this may make restoration from backup slow.
+ > - Move the switch next to `Include DROP DATABASE statement` to the `Yes` position to include a command in the backup that will drop any existing database object with the same name before recreating the object during a backup.
+
+
+
+- Move switches in the **Disable** field box to specify the type of statements that should be excluded from the backup.
+
+ > - Move the switch next to `Trigger` (active when creating a data-only backup) to the `Yes` position to include commands that will disable triggers on the target table while the data is being loaded.
+ > - Move the switch next to `$ quoting` to the `Yes` position to enable dollar quoting within function bodies; if disabled, the function body will be quoted using SQL standard string syntax.
+
+
+
+- Move switches in the **Miscellaneous** field box to specify miscellaneous backup options.
+
+ > - Move the switch next to `With OIDs` to the `Yes` position to include object identifiers as part of the table data for each table.
+ > - Move the switch next to `Verbose messages` to the `No` position to instruct `pg_dump` to exclude verbose messages.
+ > - Move the switch next to `Force double quotes on identifiers` to the `Yes` position to force the quoting of all identifiers.
+ > - Move the switch next to `Use SET SESSION AUTHORIZATION` to the `Yes` position to include a statement that will use a SET SESSION AUTHORIZATION command to determine object ownership (instead of an ALTER OWNER command).
+
+Click the `Backup` button to build and execute a command based on your selections; click the `Cancel` button to exit without saving work.
+
+
+
+Use the **Stop Process** button to stop the Backup process.
+
+If the backup is successful, a popup window will confirm success. Click `Click here for details` on the popup window to launch the `Process Watcher`. The `Process Watcher` logs all the activity associated with the backup and provides additional information for troubleshooting.
+
+
+
+If the backup is unsuccessful, review the error message returned by the `Process Watcher` to resolve any issue.
+
+
+
+Note
+
+
+
+You can click on the  icon in the process watcher window to open the file location in the Storage Manager. You can use the [Storage Manager](../05_toc_pem_management_basics/#storage_manager) to download the backup file on the client machine .
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/09_restore_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/09_restore_dialog.mdx
new file mode 100644
index 00000000000..4cec4761af7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/09_restore_dialog.mdx
@@ -0,0 +1,84 @@
+---
+title: "Restore Dialog"
+---
+
+
+
+
+The `Restore` dialog provides an easy way to use a Custom, tar, or Directory format backup taken with the PEM `Backup` dialog to recreate a database or database object. The `Backup` dialog invokes options of the pg\_dump client utility; the `Restore` dialog invokes options of the pg\_restore client utility.
+
+You can use the `Query Tool` to play back the script created during a plain-text backup made with the `Backup` dialog. For more information about backing up or restoring, please refer to the documentation for [pg\_dump](https://www.postgresql.org/docs/current/static/app-pgdump.html) or [pg\_restore](https://www.postgresql.org/docs/current/static/app-pgrestore.html).
+
+
+
+Use the fields on the `General` tab to specify general information about the restore process:
+
+- Use the drop-down listbox in the `Format` field to select the format of your backup file.
+
+ > - Select `Custom or tar` to restore from a custom archive file to create a copy of the backed-up object.
+ > - Select `Directory` to restore from a compressed directory-format archive.
+
+- Enter the complete path to the backup file in the `Filename` field. Optionally, select the `Browser` icon (ellipsis) to the right to navigate into a directory and select the file that contains the archive.
+
+- Use the `Number of Jobs` field to specify if pg\_restore should use multiple (concurrent) jobs to process the restore. Each job uses a separate connection to the server.
+
+- Use the drop-down listbox next to `Rolename` to specify the role that will be used to authenticate with the server during the restore process.
+
+Click the `Restore options` tab to continue. Use the fields on the `Restore options` tab to specify options that correspond to `pg_restore` options.
+
+
+
+- Use the switches in the **Sections** box to specify the content that will be restored:
+
+ > - Move the switch next to `Pre-data` to the `Yes` position to restore all data definition items not included in the data or post-data item lists.
+ > - Move the switch next to `Data` to the `Yes` position to restore actual table data, large-object contents, and sequence values.
+ > - Move the switch next to `Post-data` to the `Yes` position to restore definitions of indexes, triggers, rules, and constraints (other than validated check constraints).
+
+
+
+- Use the switches in the **Type of objects** box to specify the objects that will be restored:
+
+ > - Move the switch next to `Only data` to the `Yes` position to limit the restoration to data.
+ > - Move the switch next to `Only schema` to limit the restoration to schema-level database objects.
+
+
+
+- Use the switches in the **Do not save** box to specify which objects will not be restored:
+
+ > - Move the switch next to `Owner` to the `Yes` position to exclude commands that set object ownership.
+ > - Move the switch next to `Privilege` to the `Yes` position to exclude commands that create access privileges.
+ > - Move the switch next to `Tablespace` to the `Yes` position to exclude tablespaces.
+ > - Move the switch next to `Comments` to the `Yes` position to exclude commands that set the comments. **Note:** This option is visible only for database server greater than or equal to 11.
+
+
+
+- Use the switches in the **Queries** box to specify the type of statements that should be included in the restore:
+
+ > - Move the switch next to `Include CREATE DATABASE statement` to the `Yes` position to include a command that creates a new database before performing the restore.
+ > - Move the switch next to `Clean before restore` to the `Yes` position to drop each existing database object (and data) before restoring.
+ > - Move the switch next to `Single transaction` to the `Yes` position to execute the restore as a single transaction (that is, wrap the emitted commands in `BEGIN/COMMIT`). This ensures that either all the commands complete successfully, or no changes are applied. This option implies `--exit-on-error`.
+
+
+
+- Use the switches in the **Disable** box to specify the type of statements that should be excluded from the restore:
+
+ > - Move the switch next to `Trigger` (active when creating a data-only restore) to the `Yes` position to include commands that will disable triggers on the target table while the data is being loaded.
+ > - Move the switch next to `No data for Failed Tables` to the `Yes` position to ignore data that fails a trigger.
+
+
+
+- Use the switches in the **Miscellaneous/Behavior** box to specify miscellaneous restore options:
+
+ > - Move the switch next to `Verbose messages` to the `No` position to instruct `pg_restore` to exclude verbose messages.
+ > - Move the switch next to `Use SET SESSION AUTHORIZATION` to the `Yes` position to include a statement that will use a SET SESSION AUTHORIZATION command to determine object ownership (instead of an ALTER OWNER command).
+ > - Move the switch next to `Exit on error` to the `Yes` position to instruct `pg_restore` to exit restore if there is an error in sending SQL commands. The default is to continue and to display a count of errors at the end of the restore.
+
+When you’ve specified the details that will be incorporated into the pg\_restore command, click the `Restore` button to start the process, or click the `Cancel` button to exit without saving your work. A popup will confirm if the restore is successful.
+
+
+
+Use the **Stop Process** button to stop the Restore process.
+
+Click `Click here for details` on the popup to launch the `Process Watcher`. The `Process Watcher` logs all the activity associated with the restore, and provides additional information for troubleshooting should the restore command encounter problems.
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/01_database_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/01_database_dialog.mdx
new file mode 100644
index 00000000000..ef7eafe6ab0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/01_database_dialog.mdx
@@ -0,0 +1,89 @@
+---
+title: "Database Dialog"
+---
+
+
+
+
+Use the `Database` dialog to define or modify a database. To create a database, you must be a database superuser or have the CREATE privilege.
+
+The `Database` dialog organizes the development of a database through the following dialog tabs: `General`, `Definition`, `Security`, and `Parameters`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the database:
+
+- Use the `Database` field to add a descriptive name for the database. The name will be displayed in the `Browser` tree control.
+- Select the owner of the database from the drop-down listbox in the `Owner` field.
+- Store notes about the database in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the `Definition` tab to set properties for the database:
+
+- Select a character set from the drop-down listbox in the `Encoding` field. The default is `UTF8`.
+- Select a template from the drop-down listbox in the `Template` field. If you do not specify a template, the database will use template1.
+- Select a tablespace from the drop-down listbox in the `Tablespace` field. The selected tablespace will be the default tablespace used to contain database objects.
+- Select the collation order from the drop-down listbox in the `Collation` field.
+- Select the character classification from the drop-down listbox in the `Character Type` field. This affects the categorization of characters, e.g. lower, upper and digit. The default, or a blank field, uses the character classification of the template database.
+- Specify a connection limit in the `Connection Limit` field to configure the maximum number of connection requests. The default value (`-1`) allows unlimited connections to the database.
+
+Click the `Security` tab to continue.
+
+
+
+Use the `Security` tab to assign privileges and define security labels.
+
+Use the `Privileges` panel to assign privileges to a role. Click the `Add` icon (+) to set privileges for database objects:
+
+- Select the name of the role from the drop-down listbox in the `Grantee` field.
+- Click inside the `Privileges` field. Check the boxes to the left of one or more privileges to grant the selected privilege to the specified user.
+- The current user, who is the default grantor for granting the privilege, is displayed in the `Grantor` field.
+
+Click add to set additional privileges; to discard a privilege, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Use the `Security Labels` panel to define security labels applied to the database. Click the `Add` icon (+) to add each security label selection:
+
+- Specify a security label provider in the `Provider` field. The named provider must be loaded and must consent to the proposed labeling operation.
+- Specify a a security label in the `Security Label` field. The meaning of a given label is at the discretion of the label provider. PostgreSQL places no restrictions on whether or how a label provider must interpret security labels; it merely provides a mechanism for storing them.
+
+To discard a security label, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `Parameters` tab to continue.
+
+
+
+Use the `Parameters` tab to set parameters for the database. Click the `Add` icon (+) to add each parameter:
+
+- Use the drop-down listbox in the `Name` field to select a parameter.
+- Use the `Value` field to set a value for the parameter.
+- Use the drop-down listbox next to `Role` to select a role to which the parameter setting specified will apply.
+
+Follow these steps to add additional parameter value definitions; to discard a parameter, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `Advanced` tab to continue.
+
+
+
+Note
+
+
+
+You can click on the  icon in the process watcher window to open the file location in the Storage Manager. You can use the [Storage Manager](../05_toc_pem_management_basics/#storage_manager) to download the backup file on the client machine .
+
+
+
+Use the `Advanced` tab to set advanced parameters for the database.
+
+- Use `Schema restriction` field to provide a SQL restriction that will be used against the pg\_namespace table to limit the schemas that you see. For example, you might enter: `public` so that only `public` are shown in the pgAdmin browser.Separate entries with a comma or tab as you type.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Database` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Database` dialog:
+
+
+
+The example creates a database named `hr` that is owned by `postgres`. It allows unlimited connections, and is available to all authenticated users.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/02_move_objects.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/02_move_objects.mdx
new file mode 100644
index 00000000000..38aa81caa32
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/02_move_objects.mdx
@@ -0,0 +1,41 @@
+---
+title: "Move Objects Dialog"
+---
+
+
+
+
+Use the `Move Objects` dialog to to move database objects from one tablespace to another tablespace.
+
+The `Move Objects` dialog organizes the movement of database objects with the `General` tab; the `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the items that will be moved and the tablespace to which they will be moved:
+
+- Use the `New tablespace` drop-down listbox to select a pre-existing tablespace to which the object will be moved. (To create a tablespace, use the `Tablespace` dialog; access the dialog by right clicking `Tablespaces` in the `Browser` tree control and selecting `Create Tablespace...` from the context-menu.)
+
+- Use the `Object type` drop-down listbox to select from the following:
+
+ > - Select `All` to move all tables, indexes, and materialized views from the current tablespace (currently selected in the `Browser` tree control) to the new tablespace.
+ > - Select `Tables` to move tables from the current tablespace to the new tablespace.
+ > - Select `Indexes` to move indexes from the current tablespace to the new tablespace.
+ > - Select `Materialized views` to move materialized views from the current tablespace to the new tablespace.
+
+- Use the `Object owner` drop-down listbox to select the role that owns the objects selected in the `Object type` field. This field is optional.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Move Objects` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit the `General` tab to modify the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Move Objects` dialog:
+
+
+
+The example shown demonstrates moving materialized views owned by Alice from tablespace `tbspace_01` to `tbspace_02`.
+
+- Click the `Help` button (?) to access online help.
+- Click the `OK` button to save work.
+- Click the `Cancel` button to exit without saving work.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/03_resource_group_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/03_resource_group_dialog.mdx
new file mode 100644
index 00000000000..22510112237
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/03_resource_group_dialog.mdx
@@ -0,0 +1,38 @@
+---
+title: "Resource Group Dialog"
+---
+
+
+
+
+Use the `Resource Group` dialog to create a resource group and set values for its resources. A resource group is a named, global group on which various resource usage limits can be defined. The resource group is accessible from all databases in the cluster. To use the `Resource Group` dialog, you must have superuser privileges. Please note that resource groups are supported when connected to EDB Postgres Advanced Server; for more information about using resource groups, please see the EDB Postgres Advanced Server Guide, available at:
+
+>
+
+database\_dialog move\_objects resource\_group\_dialog role\_dialog tablespace\_dialog
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/01_cast_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/01_cast_dialog.mdx
new file mode 100644
index 00000000000..3be8f1021ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/01_cast_dialog.mdx
@@ -0,0 +1,45 @@
+---
+title: "Cast Dialog"
+---
+
+
+
+
+Use the `Cast` dialog to define a cast. A cast specifies how to convert a value from one data type to another.
+
+The `Cast` dialog organizes the development of a cast through the following dialog tabs: `General` and `Definition`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the cast:
+
+- The `Name` field is disabled. The name that will be displayed in the `Browser` tree control is the `Source` type concatenated with the `Target` type, and is generated automatically when you make selections on the `Cast` dialog `Definition` tab.
+- Store notes about the cast in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define parameters:
+
+- Use the drop-down listbox next to `Source type` to select the name of the source data type of the cast.
+- Use the drop-down listbox next to `Target type` to select the name of the target data type of the cast.
+- Use the drop-down listbox next to `Function` to select the function used to perform the cast. The function's result data type must match the target type of the cast.
+- Move the `Context` switch to the `Implicit` position if the cast is implicit. By default, a cast can be invoked only by an explicit cast request. If the cast is marked `Implicit` then it can be invoked implicitly in any context, whether by assignment or internally in an expression.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Cast` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Cast` dialog:
+
+
+
+The cast uses a function named `int4(bigint)` to convert a biginteger data type to an integer.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/02_collation_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/02_collation_dialog.mdx
new file mode 100644
index 00000000000..f3003180b5c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/11_managing_database_objects/02_collation_dialog.mdx
@@ -0,0 +1,52 @@
+---
+title: "Collation Dialog"
+---
+
+
+
+
+Use the `Collation` dialog to define a collation. A collation is an SQL schema object that maps a SQL name to operating system locales. To create a collation, you must have a CREATE privilege on the destination schema.
+
+The `Collation` dialog organizes the development of a collation through the following dialog tabs: `General` and `Definition`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the collation:
+
+- Use the `Name` field to provide a name for the collation. The collation name must be unique within a schema. The name will be displayed in the Browser tree control.
+- Select the name of the owner from the drop-down listbox in the `Owner` field.
+- Select the name of the schema in which the collation will reside from the drop-down listbox in the `Schema` field.
+- Store notes about the collation in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to specify the operating system locale settings:
+
+- Use the drop-down listbox next to `Copy collation` to select the name of an existing collation to copy. The new collation will have the same properties as the existing one, but will be an independent object. If you choose to copy an existing collation, you cannot modify the collation properties displayed on this tab.
+- Use the `Locale` field to specify a locale; a locale specifies language and language formatting characteristics. If you specify this, you cannot specify either of the following parameters. To view a list of locales supported by your Linux system use the command `locale -a`.
+- Use the `LC_COLLATE` field to specify a locale with specified string sort order. The locale must be applicable to the current database encoding. (See CREATE DATABASE for details.)
+- Use the `LC_CTYPE` field to specify a locale with specified character classification. The locale must be applicable to the current database encoding. (See CREATE DATABASE for details.)
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Collation` dialog generate a SQL command (see an example b elow). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+## Example
+
+The following is an example of the sql command generated by user selections in the `Collation` dialog:
+
+
+
+The example shown demonstrates creating a collation named `french` that uses the rules specified for the locale, `fr-BI-x-icu`. The collation is owned by `postgres`.
+
+- Click the `Info` button (i) to access online help. For more information about setting a locale, see Chapter 22.1 Locale Support of the PostgreSQL core documentation:
+
+ >
+
+cast\_dialog collation\_dialog domain\_dialog domain\_constraint\_dialog event\_trigger\_dialog extension\_dialog foreign\_data\_wrapper\_dialog foreign\_server\_dialog foreign\_table\_dialog fts\_configuration\_dialog fts\_dictionary\_dialog fts\_parser\_dialog fts\_template\_dialog function\_dialog language\_dialog materialized\_view\_dialog package\_dialog procedure\_dialog schema\_dialog sequence\_dialog synonym\_dialog trigger\_function\_dialog type\_dialog user\_mapping\_dialog view\_dialog
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/01_check_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/01_check_dialog.mdx
new file mode 100644
index 00000000000..90bdefbd687
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/01_check_dialog.mdx
@@ -0,0 +1,44 @@
+---
+title: "Check Dialog"
+---
+
+
+
+
+Use the `Check` dialog to define or modify a check constraint. A check constraint specifies an expression that produces a Boolean result that new or updated rows must satisfy for an insert or update operation to succeed.
+
+The `Check` dialog organizes the development of a check constraint through the `General` and `Definition` tabs. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the check constraint:
+
+- Use the `Name` field to provide a descriptive name for the check constraint that will be displayed in the `Browser` tree control. With PostgreSQL 9.5 forward, when a table has multiple check constraints, they will be tested for each row in alphabetical order by name and after NOT NULL constraints.
+- Store notes about the check constraint in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the check constraint:
+
+- Provide the expression that a row must satisfy in the `Check` field.
+- Move the `No Inherit?` switch to the `Yes` position to specify this constraint is automatically inherited by a table's children. The default is `No`.
+- Move the `Don't validate?` switch to the `No` position to skip validation of existing data; the constraint may not hold for all rows in the table. The default is `Yes`.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Check` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Check` dialog:
+
+
+
+The example shown demonstrates creating a check constraint named `check_price` on the `price` column of the `products` table. The constraint confirms that any values added to the column are greater than 0.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/02_column_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/02_column_dialog.mdx
new file mode 100644
index 00000000000..057fff327df
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/02_column_dialog.mdx
@@ -0,0 +1,102 @@
+---
+title: "Column Dialog"
+---
+
+
+
+
+Use the `Column` dialog to add a column to an existing table or modify a column definition.
+
+The `Column` dialog organizes the development of a column through the following dialog tabs: `General`, `Definition`, and `Security`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the column:
+
+- Use the `Name` field to add a descriptive name for the column. The name will be displayed in the `Browser` tree control. This field is required.
+- Store notes about the column in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to add parameters for the column. (Fields are disabled if inapplicable.)
+
+- Use the drop-down listbox next to `Data Type` to select a data type for the column. For more information on the data types that are supported by PostgreSQL, refer to Chapter 8 of the Postgres core documentation. This field is required.
+- Use the `Length/Precision` and `Scale` fields to specify the maximum number of significant digits in a numeric value, or the maximum number of characters in a text value.
+- Use the drop-down listbox next to `Collation` to apply a collation setting to the column.
+
+Click the `Constraints` tab to continue.
+
+
+
+Use the fields in the `Constraints` tab to specify constraints for the column. (Fields are disabled if inapplicable.)
+
+- Use the `Default Value` field to specify a default data value.
+- Move the `Not Null` switch to the `Yes` position to specify the column may not contain null values. The default is `No`.
+- Use the `Type` field to specify the column type (NONE/IDENTITY/GENERATED). The default is `NONE`.
+
+Click the `IDENTITY` type to create Identity column.
+
+
+
+Use the following fields to create `IDENTITY` column. Identity columns are applicable for PG/EPAS version 10 and above.
+
+- Use the `Identity` field to specify ALWAYS or BY DEFAULT. This clause is used to determine how the sequence value is given precedence over a user-specified value in an INSERT statement.
+- Use the `Increment` field to specify which value is added to the current sequence value to create a new value.
+- Provide a value in the `Start` field to specify the beginning value of the sequence. The default starting value is MINVALUE for ascending sequences and MAXVALUE for descending ones.
+- Provide a value in the `Minimum` field to specify the minimum value a sequence can generate. If this clause is not supplied or NO MINVALUE is specified, then defaults will be used. The defaults are 1 and -263-1 for ascending and descending sequences, respectively.
+- Provide a value in the `Maximum` field to specify the maximum value for the sequence. If this clause is not supplied or NO MAXVALUE is specified, then default values will be used. The defaults are 263-1 and -1 for ascending and descending sequences, respectively.
+- Provide a value in the `Cache` field to specify how many sequence numbers are to be preallocated and stored in memory for faster access. The minimum value is 1 (only one value can be generated at a time, i.e., no cache), and this is also the default.
+- Move the `Cycled` switch to the `Yes` position to allow the sequence to wrap around when the MAXVALUE or the MINVALUE has been reached by an ascending or descending sequence respectively. If the limit is reached, the next number generated will be the MINVALUE or MAXVALUE, respectively. The default is `No`.
+
+Click the `GENERATED` type to create Generated column.
+
+
+
+Use the following fields to create `GENERATED` column. Generated columns are applicable for PG/EPAS version 12 and above.
+
+- Use the `Expression` field to specify the generation expression. It can refer to other columns in the table, but not other generated columns. Any functions and operators used must be immutable. References to other tables are not allowed.
+
+Click the `Variables` tab to continue.
+
+
+
+Use the `Variables` tab to to specify the number of distinct values that may be present in the column; this value overrides estimates made by the ANALYZE command. Click the `Add` icon (+) to add a `Name`/`Value` pair:
+
+- Select the name of the variable from the drop-down listbox in the `Name` field.
+
+ > - Select `n_distinct` to specify the number of distinct values for the column.
+ > - Select `n_distinct_inherited` to specify the number of distinct values for the table and its children.
+
+- Specify the number of distinct values in the `Value` field. For more information, see the documentation for [ALTER TABLE](http://www.postgresql.org/docs/9.6/static/sql_altertable.html).
+
+Click the `Add` icon (+) to specify each additional `Name`/`Value` pair; to discard a variable, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `Security` tab to continue.
+
+
+
+Use the `Security` tab to assign attributes and define security labels. Click the `Add` icon (+) to add each security label selection:
+
+- Specify a security label provider in the `Provider` field. The named provider must be loaded and must consent to the proposed labeling operation.
+- Specify a a security label in the `Security Label` field. The meaning of a given label is at the discretion of the label provider. PostgreSQL places no restrictions on whether or how a label provider must interpret security labels; it merely provides a mechanism for storing them.
+
+Click the `Add` icon (+) to assign additional security labels; to discard a security label, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Column` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Column` dialog:
+
+
+
+The example shown demonstrates creating a column named `territory` in the table named `distributors`.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/03_compound_trigger_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/03_compound_trigger_dialog.mdx
new file mode 100644
index 00000000000..fcfb8db8a47
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/03_compound_trigger_dialog.mdx
@@ -0,0 +1,54 @@
+---
+title: "Compound Trigger Dialog"
+---
+
+
+
+
+Use the `Compound Trigger` dialog to create a compound trigger or modify an existing compound trigger. `Compound Trigger` is supported only for EPAS server 12 and above. A compound trigger executes a specified code when certain events occur.
+
+The `Compound Trigger` dialog organizes the development of a compound trigger through the following dialog tabs: `General`, `Events`, and `Code`. The SQL tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the compound trigger:
+
+- Use the `Name` field to add a descriptive name for the compound trigger. This must be distinct from the name of any other compound trigger for the same table. The name will be displayed in the `Browser` tree control.
+- Store notes about the compound trigger in the `Comment` field.
+
+
+
+- `Trigger enabled` field is available in compound trigger dialog once the trigger is created by selecting the `properties` of the trigger. You can select one of the four options available.
+
+Click the `Events` tab to continue.
+
+
+
+Use the fields in the `Events` tab to specify how and when the compound trigger fires:
+
+- Select the type of event(s) that will invoke the compound trigger; to select an event type, move the switch next to the event to the `YES` position. The supported event types are `INSERT`, `UPDATE`, `DELETE` and `TRUNCATE`. Views cannot have TRUNCATE triggers.
+- Use the `When` field to provide a boolean condition that will invoke the compound trigger.
+- If defining a column-specific compound trigger, use the `Columns` field to specify the columns or columns that are the target of the compound trigger.
+
+Click the `Code` tab to continue.
+
+
+
+Use the `Code` field to specify the code for the five timing events `BEFORE STATEMENT`, `AFTER STATEMENT`, `BEFORE EACH ROW`, `AFTER EACH ROW`, `INSTEAD OF EACH ROW` that will be invoked when the compound trigger fires. Basic template is provided with place holders.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Compound Trigger` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+## Example
+
+The following is an example of the sql command generated by user selections in the `Compound Trigger` dialog:
+
+
+
+The example demonstrates creating a compound trigger named `test_ct`.
+
+- Click the `Info` button (i) to access online help.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/04_exclusion_constraint_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/04_exclusion_constraint_dialog.mdx
new file mode 100644
index 00000000000..5887e94bc81
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/04_exclusion_constraint_dialog.mdx
@@ -0,0 +1,70 @@
+---
+title: "Exclusion constraint Dialog"
+---
+
+
+
+
+Use the `Exclusion constraint` dialog to define or modify the behavior of an exclusion constraint. An exclusion constraint guarantees that if any two rows are compared on the specified column or expression (using the specified operator), at least one of the operator comparisons will return false or null.
+
+The `Exclusion constraint` dialog organizes the development of an exclusion constraint through the following dialog tabs: `General`, `Definition`, and `Columns`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the exclusion constraint:
+
+- Use the `Name` field to provide a descriptive name for the exclusion constraint. The name will be displayed in the `Browser` tree control.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the exclusion constraint:
+
+- Use the drop-down listbox next to `Tablespace` to select the tablespace in which the index associated with the exclude constraint will reside.
+
+- Use the drop-down listbox next to `Access method` to specify the type of index that will be used when implementing the exclusion constraint:
+
+ > - Select `gist` to specify a GiST index.
+ > - Select `spgist` to specify a space-partitioned GiST index.
+ > - Select `btree` to specify a B-tree index.
+ > - Select `hash` to specify a hash index.
+
+- Use the `Fill Factor` field to specify a fill factor for the table and associated index. The fill factor is a percentage between 10 and 100. 100 (complete packing) is the default.
+
+- Move the `Deferrable?` switch to the `Yes` position to specify that the timing of the constraint is deferrable, and can be postponed until the end of the statement. The default is `No`.
+
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+- Use the `Constraint` field to provide a condition that a row must satisfy to be included in the table.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the fields in the *Columns* tab to specify the column(s) or expression(s) to which the constraint applies. Use the *Is expression ?* switch to enable expression text input. Use the drop-down listbox next to *Column* to select a column. Once the *Column* is selected or the *Expression* is entered then click the *Add* icon (+) to provide details of the action on the column/expression:
+
+- The *Col/Exp* field is populated with the selection made in the *Column* drop-down listbox or the *Expression* entered.
+- If applicable, use the drop-down listbox in the `Operator class` to specify the operator class that will be used by the index for the column.
+- Move the `DESC` switch to `DESC` to specify a descending sort order. The default is `ASC` which specifies an ascending sort order.
+- Use the `NULLs order` column to specify the placement of NULL values (when sorted). Specify `FIRST` or `LAST`.
+- Use the drop-down list next to `Operator` to specify a comparison or conditional operator.
+
+Use `Include columns` field to specify columns for `INCLUDE` clause of the constraint. This option is available in Postgres 11 and later.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Exclusion Constraint` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Exclusion Constraint` dialog:
+
+
+
+The example shown demonstrates creating an exclusion constraint named `exclude_department` that restricts additions to the dept table to those additions that are not equal to the value of the `deptno` column. The constraint uses a btree index.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/05_foreign_key_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/05_foreign_key_dialog.mdx
new file mode 100644
index 00000000000..6be0439a0c9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/05_foreign_key_dialog.mdx
@@ -0,0 +1,86 @@
+---
+title: "Foreign key Dialog"
+---
+
+
+
+
+Use the `Foreign key` dialog to specify the behavior of a foreign key constraint. A foreign key constraint maintains referential integrity between two tables. A foreign key constraint cannot be defined between a temporary table and a permanent table.
+
+The `Foreign key` dialog organizes the development of a foreign key constraint through the following dialog tabs: `General`, `Definition`, `Columns`, and `Action`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the foreign key constraint:
+
+- Use the `Name` field to add a descriptive name for the foreign key. The name will be displayed in the `Browser` tree control.
+- Store notes about the foreign key constraint in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the foreign key constraint:
+
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+- Move the `Match type` switch specify the type of matching that is enforced by the constraint:
+
+ > - Select `Full` to indicate that all columns of a multicolumn foreign key must be null if any column is null; if all columns are null, the row is not required to have a match in the referenced table.
+ > - Select `Simple` to specify that a single foreign key column may be null; if any column is null, the row is not required to have a match in the referenced table.
+
+- Move the `Validated` switch to the `Yes` position to instruct the server to validate the existing table content (against a foreign key or check constraint) when you save modifications to this dialog.
+
+- Move the `Auto FK Index` switch to the `No` position to disable the automatic index feature.
+
+- The field next to `Covering Index` generates the name of an index if the `Auto FK Index` switch is in the `Yes` position; or, this field is disabled.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the fields in the `Columns` tab to specify one or more reference column(s). A Foreign Key constraint requires that one or more columns of a table must only contain values that match values in the referenced column(s) of a row of a referenced table:
+
+- Use the drop-down listbox next to `Local column` to specify the column in the current table that will be compared to the foreign table.
+- Use the drop-down listbox next to `References` to specify the name of the table in which the comparison column(s) resides.
+- Use the drop-down listbox next to `Referencing` to specify a column in the foreign table.
+
+Click the `Add` icon (+) to add a column to the list; repeat the steps above and click the `Add` icon (+) to add additional columns. To discard an entry, click the trash icon to the left of the entry and confirm deletion in the `Delete Row` popup.
+
+Click the `Action` tab to continue.
+
+
+
+Use the drop-down listboxes on the `Action` tab to specify behavior related to the foreign key constraint that will be performed when data within the table is updated or deleted:
+
+- Use the drop-down listbox next to `On update` to select an action that will be performed when data in the table is updated.
+- Use the drop-down listbox next to `On delete` to select an action that will be performed when data in the table is deleted.
+
+The supported actions are:
+
+| | |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NO ACTION | Produce an error indicating that the deletion or update will create a foreign key constraint violation. If the constraint is deferred, this error will be produced at constraint check time if any referencing rows still exist. This is the default. |
+| RESTRICT | Throw an error indicating that the deletion or update would create a foreign key constraint violation. This is the same as NO ACTION except that the check is not deferrable. |
+| CASCADE | Delete any rows referencing the deleted row, or update the values of the referencing column(s) to the new values of the referenced columns, respectively. |
+| SET NULL | Set the referencing column(s) to null. |
+| SET DEFAULT | Set the referencing column(s) to their default values. There must be a row in the referenced table that matches the default values (if they are not null), or the operation will fail. |
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Foreign key` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Foreign key` dialog:
+
+
+
+The example shown demonstrates creating a foreign key constraint named `territory_fkey` that matches values in the `distributors` table `territory` column with those of the `sales_territories` table `region` column.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/06_index_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/06_index_dialog.mdx
new file mode 100644
index 00000000000..6ffae054da8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/06_index_dialog.mdx
@@ -0,0 +1,80 @@
+---
+title: "Index Dialog"
+---
+
+
+
+
+Use the `Index` dialog to create an index on a specified table or materialized view.
+
+The `Index` dialog organizes the development of a index through the following dialog tabs: `General` and `Definition`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the index:
+
+- Use the `Name` field to add a descriptive name for the index. The name will be displayed in the `Browser` tree control.
+- Use the drop-down listbox next to `Tablespace` to select the tablespace in which the index will reside.
+- Store notes about the index in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the index:
+
+- Use the drop-down listbox next to `Access Method` to select an index type:
+
+ > - Select `btree` to create a B-tree index. A B-tree index may improve performance when managing equality and range queries on data that can be sorted into some ordering (the default).
+ > - Select `hash` to create a hash index. A hash index may improve performance when managing simple equality comparisons.
+ > - Select `gist` to create a GiST index. A GiST index may improve performance when managing two-dimensional geometric data types and nearest-neighbor searches
+ > - Select `gin` to create a GIN index. A GIN index may performance when managing values with more than one key.
+ > - Select `spgist` to create a space-partitioned GiST index. A SP-GiST index may improve performance when managing non-balanced data structures.
+ > - Select `brin` to create a BRIN index. A BRIN index may improve performance when managing minimum and maximum values and ranges.
+
+- Use the `Fill Factor` field to specify a fill factor for the index. The fill factor specifies how full the selected method will try to fill each index page.
+
+- Move the `Unique?` switch to the `Yes` position to check for duplicate values in the table when the index is created and when data is added. The default is `No`.
+
+- Move the `Clustered?` switch to the `Yes` position to instruct the server to cluster the table.
+
+- Move the `Concurrent build?` switch to the `Yes` position to build the index without taking any locks that prevent concurrent inserts, updates, or deletes on the table.
+
+- Use the `Constraint` field to provide a constraint expression; a constraint expression limits the entries in the index to those rows that satisfy the constraint.
+
+Use the context-sensitive fields in the `Columns` panel to specify which column(s) the index queries. Click the `Add` icon (+) to add a column:
+
+- Use the drop-down listbox in `Column` field to select the name of the column from the table.
+
+- If enabled, use the drop-down listbox to select an available `Operator class` to specify the type of action performed on the column.
+
+- If enabled, move the `Sort order` switch to specify the sort order:
+
+ > - Select `ASC` to specify an ascending sort order (the default);
+ > - Select `DESC` to specify a descending sort order.
+
+- If enabled, move the `Nulls` switch to specify the sort order of nulls:
+
+ > - Select `First` to specify nulls sort before non-nulls;
+ > - Select `Last` to specify nulls sort after non-nulls (the default).
+
+- Use the drop-down listbox in the `Collation` field to select a collation to use for the index.
+
+Use `Include columns` field to specify columns for `INCLUDE` clause of the index. This option is available in Postgres 11 and later.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Index` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Index` dialog:
+
+
+
+The example shown demonstrates creating an index named `dist_codes` that indexes the values in the `code` column of the `distributors` table.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/07_primary_key_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/07_primary_key_dialog.mdx
new file mode 100644
index 00000000000..fda0778c1d6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/07_primary_key_dialog.mdx
@@ -0,0 +1,47 @@
+---
+title: "Primary key Dialog"
+---
+
+
+
+
+Use the `Primary key` dialog to create or modify a primary key constraint. A primary key constraint indicates that a column, or group of columns, uniquely identifies rows in a table. This requires that the values in the selected column(s) be both unique and not null.
+
+The `Primary key` dialog organizes the development of a primary key constraint through the `General` and `Definition` tabs. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the primary key:
+
+- Use the `Name` field to add a descriptive name for the primary key constraint. The name will be displayed in the `Browser` tree control.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the primary key constraint:
+
+- Click inside the `Columns` field and select one or more column names from the drop-down listbox. To delete a selection, click the `x` to the left of the column name. The primary key constraint should be different from any unique constraint defined for the same table; the selected column(s) for the constraints must be distinct.
+- Use `Include columns` field to specify columns for `INCLUDE` clause of the index. This option is available in Postgres 11 and later.
+- Select the name of the tablespace in which the primary key constraint will reside from the drop-down listbox in the `Tablespace` field.
+- Select the name of an index from the drop-down listbox in the `Index` field. This field is optional. Adding a primary key will automatically create a unique B-tree index on the column or group of columns listed in the primary key, and will force the column(s) to be marked NOT NULL.
+- Use the `Fill Factor` field to specify a fill factor for the table and index. The fill factor for a table is a percentage between 10 and 100. 100 (complete packing) is the default.
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Primary key` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Primary key` dialog:
+
+
+
+The example shown demonstrates creating a primary key constraint named `dept_pkey` on the `dept_id` column of the `dept` table.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/08_rls_policy_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/08_rls_policy_dialog.mdx
new file mode 100644
index 00000000000..0a7607ef81d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/08_rls_policy_dialog.mdx
@@ -0,0 +1,57 @@
+---
+title: "RLS Policy Dialog"
+---
+
+
+
+
+Use the `RLS Policy` dialog to Create a Row Level Security Policy.
+
+
+
+
+
+The `RLS Policy` dialog creates a Row Level Security Policy through the following dialog tabs: `General`, and `Commands`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Note
+
+
+
+If the Row Level Security is enabled at table level and no policy is created then by default `Deny Policy` is applied. That means, no rows are visible or can be modified for that table.
+
+
+
+Use the fields in the `General` tab to define the RLS Policy:
+
+- Use the `Name` field to add a descriptive name for the RLS Policy. The name will be displayed in the `pgAdmin` tree control.
+- Use the drop-down listbox next to `Role` to select the Role to which the RLS Policy is to be applied.
+- Use the drop-down listbox next to `Type` to select the type of the policy.
+
+Click the `Commands` tab to continue.
+
+
+
+Use the fields in the `Commands` tab to define the RLS Policy:
+
+- Use the drop-down listbox next to `Event` to select the command to which policy applies. Valid options are ALL, SELECT, INSERT, UPDATE, and DELETE. Default is ALL.
+- Use the `Using` field to add a SQL conditional expression returning boolean. This expression will be added to queries that refer to the table if row level security is enabled.
+- Use the `With check` field to add a SQL conditional expression returning boolean. This expression will be used in INSERT and UPDATE queries against the table if row level security is enabled.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `RLS Policy` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+## Example
+
+The following is an example of the sql command generated by user selections in the `RLS Policy` dialog:
+
+
+
+The example shown demonstrates creating a RLS Policy named `account_managers` that applies the Row Level Security on the `accounts` table.
+
+- Click the `Info` button (i) to access online help.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/09_rule_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/09_rule_dialog.mdx
new file mode 100644
index 00000000000..713c26c81c2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/09_rule_dialog.mdx
@@ -0,0 +1,55 @@
+---
+title: "Rule Dialog"
+---
+
+
+
+
+Use the `Rule` dialog to define or modify a rule for a specified table or view. A PostgreSQL rule allows you to define an additional action that will be performed when a SELECT, INSERT, UPDATE, or DELETE is performed against a table.
+
+The `Rule` dialog organizes the development of a rule through the `General`, `Definition`, `Condition`, `Commands` tabs. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the rule:
+
+- Use the `Name` field to add a descriptive name for the rule. The name will be displayed in the `Browser` tree control. Multiple rules on the same table are applied in alphabetical name order.
+- Store notes about the rule in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to write parameters:
+
+- Click inside the `Event` field to select the type of event that will invoke the rule; event may be `Select`, `Insert`, `Update`, or `Delete`.
+- Move the `Do Instead` switch to `Yes` indicate that the commands should be executed instead of the original command; if Do Instead specifies `No`, the rule will be invoked in addition to the original command.
+
+Click the `Condition` tab to continue.
+
+
+
+Specify a SQL conditional expression that returns a boolean value in the editor.
+
+Click the `Commands` tab to continue.
+
+
+
+Provide a command in the editor that defines the action performed by the rule.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Rule` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Rule` dialog:
+
+
+
+The example sends a notification when an UPDATE executes against a table.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog.mdx
new file mode 100644
index 00000000000..157c582f431
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog.mdx
@@ -0,0 +1,323 @@
+---
+title: "Table Dialog"
+---
+
+
+
+
+Use the `Table` dialog to create or modify a table.
+
+The `Table` dialog organizes the development of a table through the following dialog tabs: `General`, *Columns*, `Constraints`, *Advanced*, `Parameter`, and `Security`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the table:
+
+- Use the `Name` field to add a descriptive name for the table. A table cannot have the same name as any existing table, sequence, index, view, foreign table, or data type in the same schema. The name specified will be displayed in the `Browser` tree control. This field is required.
+- Select the owner of the table from the drop-down listbox in the `Owner` field. By default, the owner of the table is the role that creates the table.
+- Select the name of the schema in which the table will reside from the drop-down listbox in the `Schema` field.
+- Use the drop-down listbox in the `Tablespace` field to specify the tablespace in which the table will be stored.
+- Move the `Partitioned Table?` switch to the `Yes` in case you want to create a partitioned table. Option is available for PostgreSQL 10 and above.
+- Store notes about the table in the `Comment` field.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the drop-down listbox next to `Inherited from table(s)` to specify any parent table(s); the table will inherit columns from the selected parent table(s). Click inside the `Inherited from table(s)` field to select a table name from a drop-down list. Repeat to add any other parent tables. Delete a selected table by clicking the `x` to the left of the parent name. Note that inherited column names and datatypes are not editable in the current dialog; they must be modified at the parent level.
+
+Click the `Add` icon (+) to specify the names of columns and their datatypes in the `Columns` table:
+
+- Use the `Name` field to add a descriptive name for the column.
+- Use the drop-down listbox in the `Data type` field to select a data type for the column. This can include array specifiers. For more information on the data types supported by PostgreSQL, refer to Chapter 8 of the core documentation.
+- If enabled, use the `Length` and `Precision` fields to specify the maximum number of significant digits in a numeric value, or the maximum number of characters in a text value.
+- Move the `Not NULL?` switch to the `Yes` position to require a value in the column field.
+- Move the `Primary key?` switch to the `Yes` position to specify the column is the primary key constraint.
+
+> Click the `Add` icon (+) to add additional columns; to discard a column, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `Constraints` tab to continue.
+
+
+
+Use the fields in the `Constraints` tab to provide a table or column constraint. Optional constraint clauses specify constraints (tests) that new or updated rows must satisfy for an `INSERT` or `UPDATE` operation to succeed. Select the appropriate constraint type by selecting one of the following tabs on the `Constraints` panel:
+
+| Tab Name | Constraint |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `Primary Key` | Provides a unique identifier for each row in the table. |
+| `Foreign Key` | Maintains referential integrity between two tables. |
+| `Check` | Requires data satisfies an expression or condition before insertion or modification. |
+| `Unique` | Ensures that the data contained in a column, or a group of columns, is unique among all the rows in the table. |
+| `Exclude` | Guarantees that if any two rows are compared on the specified column or expression (using the specified operator), at least one of the operator comparisons will return false or null. |
+
+To add a primary key for the table, select the `Primary Key` tab, and click the `Add` icon (+). To define the primary key, click the `Edit` icon to the left of the `Trash` icon. A dialog similar to the `Primary key` dialog (accessed by right clicking on `Constraints` in the `Browser` tree control) opens.
+
+Use the fields in the `General` tab to identify the primary key:
+
+- Use the `Name` field to add a descriptive name for the primary key constraint. The name will be displayed in the `Browser` tree control.
+- Provide notes about the primary key in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the primary key constraint:
+
+- Click inside the `Columns` field and select one or more column names from the drop-down listbox. To delete a selection, click the `x` to the left of the column name. The primary key constraint should be different from any unique constraint defined for the same table; the selected column(s) for the constraints must be distinct.
+- Select the name of the tablespace in which the primary key constraint will reside from the drop-down listbox in the `Tablespace` field.
+- Use the `Fill Factor` field to specify a fill factor for the table and index. The fill factor for a table is a percentage between 10 and 100. 100 (complete packing) is the default.
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+
+
+To add a foreign key constraint, select the `Foreign Key` tab, and click the `Add` icon (+). To define the constraint, click the `Edit` icon to the left of the `Trash` icon. A dialog similar to the `Foreign key` dialog (accessed by right clicking on `Constraints` in the `Browser` tree control) opens.
+
+Use the fields in the `General` tab to identify the foreign key constraint:
+
+- Use the `Name` field to add a descriptive name for the foreign key constraint. The name will be displayed in the `Browser` tree control.
+- Provide notes about the foreign key in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the foreign key constraint:
+
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+- Move the `Match type` switch specify the type of matching that is enforced by the constraint:
+
+ > - Select `Full` to indicate that all columns of a multicolumn foreign key must be null if any column is null; if all columns are null, the row is not required to have a match in the referenced table.
+ > - Select `Simple` to specify that a single foreign key column may be null; if any column is null, the row is not required to have a match in the referenced table.
+
+- Move the `Validated` switch to the `Yes` position to instruct the server to validate the existing table content (against a foreign key or check constraint) when you save modifications to this dialog.
+
+- Move the `Auto FK Index` switch to the `No` position to disable the automatic index feature.
+
+- The field next to `Covering Index` generates the name of an index if the `Auto FK Index` switch is in the `Yes` position; or, this field is disabled.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the fields in the `Columns` tab to specify one or more reference column(s). A Foreign Key constraint requires that one or more columns of a table must only contain values that match values in the referenced column(s) of a row of a referenced table:
+
+- Use the drop-down listbox next to `Local column` to specify the column in the current table that will be compared to the foreign table.
+- Use the drop-down listbox next to `References` to specify the name of the table in which the comparison column(s) resides.
+- Use the drop-down listbox next to `Referencing` to specify a column in the foreign table.
+
+Click the `Add` icon (+) to add a column to the list; repeat the steps above and click the `Add` icon (+) to add additional columns. To discard an entry, click the trash icon to the left of the entry and confirm deletion in the `Delete Row` popup.
+
+Click the `Action` tab to continue.
+
+
+
+Use the drop-down listboxes on the `Action` tab to specify behavior related to the foreign key constraint that will be performed when data within the table is updated or deleted:
+
+- Use the drop-down listbox next to `On update` to select an action that will be performed when data in the table is updated.
+- Use the drop-down listbox next to `On delete` to select an action that will be performed when data in the table is deleted.
+
+The supported actions are:
+
+| | |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NO ACTION | Produce an error indicating that the deletion or update will create a foreign key constraint violation. If the constraint is deferred, this error will be produced at constraint check time if any referencing rows still exist. This is the default. |
+| RESTRICT | Throw an error indicating that the deletion or update would create a foreign key constraint violation. This is the same as NO ACTION except that the check is not deferrable. |
+| CASCADE | Delete any rows referencing the deleted row, or update the values of the referencing column(s) to the new values of the referenced columns, respectively. |
+| SET NULL | Set the referencing column(s) to null. |
+| SET DEFAULT | Set the referencing column(s) to their default values. There must be a row in the referenced table that matches the default values (if they are not null), or the operation will fail. |
+
+
+
+To add a check constraint, select the `Check` tab on the panel, and click the `Add` icon (+). To define the check constraint, click the `Edit` icon to the left of the `Trash` icon. A dialog similar to the `Check` dialog (accessed by right clicking on `Constraints` in the `Browser` tree control) opens.
+
+Use the fields in the `General` tab to identify the check constraint:
+
+- Use the `Name` field to add a descriptive name for the check constraint. The name will be displayed in the `Browser` tree control. With PostgreSQL 9.5 forward, when a table has multiple check constraints, they will be tested for each row in alphabetical order by name and after NOT NULL constraints.
+- Provide notes about the check constraint in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the check constraint:
+
+- Provide the expression that a row must satisfy in the `Check` field. This field is required.
+- Move the `No Inherit?` switch to the `Yes` position to specify this constraint is automatically inherited by a table's children. The default is `No`.
+- Move the `Don't validate?` switch to the `No` position to skip validation of existing data; the constraint may not hold for all rows in the table. The default is `Yes`.
+
+
+
+To add a unique constraint, select the `Unique` tab on the panel, and click the `Add` icon (+). To define the constraint, click the `Edit` icon to the left of the `Trash` icon. A dialog similar to the `Unique constraint` dialog (accessed by right clicking on `Constraints` in the `Browser` tree control) opens.
+
+Use the fields in the `General` tab to identify the unique constraint:
+
+- Use the `Name` field to add a descriptive name for the unique constraint. The name will be displayed in the `Browser` tree control.
+- Provide notes about the unique constraint in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the unique constraint:
+
+- Click inside the `Columns` field and select one or more column names from the drop-down listbox. To delete a selection, click the `x` to the left of the column name. The unique constraint should be different from the primary key constraint defined for the same table; the selected column(s) for the constraints must be distinct.
+- Select the name of the tablespace in which the unique constraint will reside from the drop-down listbox in the `Tablespace` field.
+- Use the `Fill Factor` field to specify a fill factor for the table and index. The fill factor for a table is a percentage between 10 and 100. 100 (complete packing) is the default.
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+
+
+To add an exclusion constraint, select the `Exclude` tab on the panel, and click the `Add` icon (+). To define the constraint, click the `Edit` icon to the left of the `Trash` icon. A dialog similar to the `Exclusion constraint` dialog (accessed by right clicking on `Constraints` in the `Browser` tree control) opens.
+
+Use the fields in the `General` tab to identify the exclusion constraint:
+
+- Use the `Name` field to provide a descriptive name for the exclusion constraint. The name will be displayed in the `Browser` tree control.
+- Provide notes about the exclusion constraint in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the exclusion constraint:
+
+- Use the drop-down listbox next to `Tablespace` to select the tablespace in which the index associated with the exclude constraint will reside.
+
+- Use the drop-down listbox next to `Access method` to specify the type of index that will be used when implementing the exclusion constraint:
+
+ > - Select `gist` to specify a GiST index (the default).
+ > - Select `spgist` to specify a space-partitioned GiST index.
+ > - Select `btree` to specify a B-tree index.
+ > - Select `hash` to specify a hash index.
+
+- Use the `Fill Factor` field to specify a fill factor for the table and associated index. The fill factor is a percentage between 10 and 100. 100 (complete packing) is the default.
+
+- Move the `Deferrable?` switch to the `Yes` position to specify that the timing of the constraint is deferrable, and can be postponed until the end of the statement. The default is `No`.
+
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+- Use the `Constraint` field to provide a condition that a row must satisfy to be included in the table.
+
+Click the `Columns` tab to continue.
+
+
+
+Use the fields in the `Columns` tab to to specify the column(s) to which the constraint applies. Use the drop-down listbox next to `Column` to select a column and click the `Add` icon (+) to provide details of the action on the column:
+
+- The `Column` field is populated with the selection made in the `Column` drop-down listbox.
+- If applicable, use the drop-down listbox in the `Operator class` to specify the operator class that will be used by the index for the column.
+- Move the `DESC` switch to `DESC` to specify a descending sort order. The default is `ASC` which specifies an ascending sort order.
+- Move the `NULLs order` switch to `LAST` to define an ascending sort order for NULLs. The default is `FIRST` which specifies a descending order.
+- Use the drop-down list next to `Operator` to specify a comparison or conditional operator.
+
+Click the `Advanced` tab to continue.
+
+
+
+Use the fields in the `Advanced` tab to define advanced features for the table:
+
+- Move the `RLS Policy?` switch to the `Yes` position to enable the Row Level Security.
+- Move the `Force RLS Policy?` to the `Yes` position to force the policy on the owner of the table.
+- Use the drop-down listbox next to `Of type` to copy the table structure from the specified composite type. Please note that a typed table will be dropped if the type is dropped (with DROP TYPE ... CASCADE).
+- Use the `Fill Factor` field to specify a fill factor for the table. The fill factor for a table is a percentage between 10 and 100. 100 (complete packing) is the default.
+- Use the `Toast tuple target` field to set toast\_tuple\_target storage parameter of the table. The toast\_tuple\_target value is in bytes and has minimum value of 128. This field will be enabled only for PostgreSQL version >= 11
+- Use the `Parallel workers` field to set parallel\_workers storage parameter of the table. The parallel\_workers sets the number of workers that should be used to assist a parallel scan of the table. This field will be enabled only for PostgreSQL version >= 9.6
+- Move the `Has OIDs?` switch to the `Yes` position to specify that each row within a table has a system-assigned object identifier. The default is `No`.
+- Move the `Unlogged?` switch to the `Yes` position to disable logging for the table. Data written to an unlogged table is not written to the write-ahead log. Any indexes created on an unlogged table are automatically unlogged as well. The default is `No`.
+
+Use the fields in the **Like** box to specify which attributes of an existing table from which a table will automatically copy column names, data types, and not-null constraints; after saving the new or modified table, any changes to the original table will not be applied to the new table.
+
+- Use the drop-down listbox next to `Relation` to select a reference table.
+- Move the `With default values?` switch to the `Yes` position to copy default values.
+- Move the `With constraints?` switch to the `Yes` position to copy table and column constraints.
+- Move the `With indexes?` switch to the `Yes` position to copy indexes.
+- Move the `With storage?` switch to the `Yes` position to copy storage settings.
+- Move the `With comments?` switch to the `Yes` position to copy comments.
+
+With PostgreSQL 10 forward, the `Partition` tab will be visible.
+
+Click the `Partition` tab to continue.
+
+
+
+Use the fields in the `partition` tab to create the partitions for the table:
+
+- Select a partition type from the `Partition Type` selection box. There are 3 options available; Range, List and Hash. Hash option will only enable for PostgreSQL version >= 11.
+
+Use the `Partition Keys` panel to define the partition keys. Click the `Add` icon (+) to add each partition keys selection:
+
+- Select a partition key type in the `Keytype` field.
+- Select a partition column in the `Column` field if Column option selected for `Keytype` field .
+- Specify the expression in the `Expression` field if Expression option selected for the `Keytype` field.
+
+Use the `Partitions` panel to define the partitions of a table. Click the `Add` icon (+) to add each partition:
+
+- Move the `Operation` switch to `attach` to attach the partition, by default it is `create`.
+- Use the `Name` field to add the name of the partition.
+- If partition type is Range or List then `Default` field will be enabled.
+- If partition type is Range then `From` and `To` fields will be enabled.
+- If partition type is List then `In` field will be enabled.
+- If partition type is Hash then `Modulus` and `Remainder` fields will be enabled.
+
+Users can create a partition and define them as a partitioned table. Click the `Edit` icon to expand the properties of a partition. Use the `Partition` tab to create that partition as a partitioned table.
+
+- Move the `Partitioned Table?` switch to the `Yes` in case you want to create a partitioned table.
+- Select a partition type from the `Partition Type` selection box.
+- Use the `Partition Keys` panel to define the partition keys.
+
+View of multi level Partitioned Table in browser tree:
+
+
+
+Click the `Parameter` tab to continue.
+
+
+
+Use the tabs nested inside the `Parameter` tab to specify VACUUM and ANALYZE thresholds; use the `Table` tab and the `Toast Table` tab to customize values for the table and the associated toast table:
+
+- Move the `Custom auto-vacuum?` switch to the `Yes` position to perform custom maintenance on the table and to select values in the `Vacuum table`. The `Vacuum Table` provides default values for maintenance operations.
+- Changing `Autovacuum enabled?` to `Not set` will reset autovacuum\_enabled.
+
+Provide a custom value in the `Value` column for each metric listed in the `Label` column.
+
+Click the `Security` tab to continue.
+
+
+
+Use the `Security` tab to assign privileges and define security labels.
+
+Use the `Privileges` panel to assign privileges to a role. Click the `Add` icon (+) to set privileges for database objects:
+
+- Select the name of the role from the drop-down listbox in the `Grantee` field.
+- Click inside the `Privileges` field. Check the boxes to the left of one or more privileges to grant the selected privilege to the specified user.
+- The current user, who is the default grantor for granting the privilege, is displayed in the `Grantor` field.
+
+Click the `Add` icon (+) to assign additional privileges; to discard a privilege, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Use the `Security Labels` panel to define security labels applied to the function. Click the `Add` icon (+) to add each security label selection:
+
+- Specify a security label provider in the `Provider` field. The named provider must be loaded and must consent to the proposed labeling operation.
+- Specify a a security label in the `Security Label` field. The meaning of a given label is at the discretion of the label provider. PostgreSQL places no restrictions on whether or how a label provider must interpret security labels; it merely provides a mechanism for storing them.
+
+Click the `Add` icon (+) to assign additional security labels; to discard a security label, click the trash icon to the left of the row and confirm deletion in the `Delete Row` popup.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Table` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Table` dialog:
+
+
+
+The example shown demonstrates creating a table named `product_category`. It has three columns and a primary key constraint on the `category_id` column.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/11_trigger_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/11_trigger_dialog.mdx
new file mode 100644
index 00000000000..612b153ce20
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/11_trigger_dialog.mdx
@@ -0,0 +1,68 @@
+---
+title: "Trigger Dialog"
+---
+
+
+
+
+Use the `Trigger` dialog to create a trigger or modify an existing trigger. A trigger executes a specified function when certain events occur.
+
+The `Trigger` dialog organizes the development of a trigger through the following dialog tabs: `General`, *Definition*, `Events`, and `Code`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the trigger:
+
+- Use the `Name` field to add a descriptive name for the trigger. This must be distinct from the name of any other trigger for the same table. The name will be displayed in the `Browser` tree control. Note that if multiple triggers of the same kind are defined for the same event, they will be fired in alphabetical order by name.
+- Store notes about the trigger in the `Comment` field.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the trigger:
+
+- Move the `Row trigger?` switch to the `No` position to disassociate the trigger from firing on each row in a table. The default is `Yes`.
+- Move the `Constraint trigger?` switch to the `Yes` position to specify the trigger is a constraint trigger.
+- If enabled, move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint trigger is deferrable and can be postponed until the end of the statement. The default is `No`.
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint trigger is deferred to the end of the statement causing the triggering event. The default is `No`.
+- Use the drop-down listbox next to `Trigger Function` to select a trigger function or procedure.
+- Use the `Arguments` field to provide an optional (comma-separated) list of arguments to the function when the trigger is executed. The arguments are literal string constants.
+
+
+
+- `Trigger enabled` field is available in trigger dialog once the trigger is created. You can select one of the four options available.
+
+Click the `Events` tab to continue.
+
+
+
+Use the fields in the `Events` tab to specify how and when the trigger fires:
+
+- Use the drop-down listbox next to the `Fires` fields to determine if the trigger fires `BEFORE` or `AFTER` a specified event. The default is `BEFORE`.
+- Select the type of event(s) that will invoke the trigger; to select an event type, move the switch next to the event to the `YES` position. The supported event types are `INSERT`, *UPDATE*, `DELETE`, and `TRUNCATE`.
+- Use the `When` field to provide a boolean condition that will invoke the trigger.
+- If defining a column-specific trigger, use the `Columns` field to specify the columns or columns that are the target of the trigger.
+
+Click the `Code` tab to continue.
+
+
+
+Use the `Code` field to specify any additional code that will be invoked when the trigger fires.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Trigger` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Trigger` dialog:
+
+
+
+The example demonstrates creating a trigger named `log_update` that calls a procedure named `log_account_update` that logs any updates to the `distributors` table.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/12_unique_constraint_dialog.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/12_unique_constraint_dialog.mdx
new file mode 100644
index 00000000000..a72a6a7585e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/12_unique_constraint_dialog.mdx
@@ -0,0 +1,47 @@
+---
+title: "Unique Constraint Dialog"
+---
+
+
+
+
+Use the `Unique constraint` dialog to define a unique constraint for a specified table. Unique constraints ensure that the data contained in a column, or a group of columns, is unique among all the rows in the table.
+
+The `Unique constraint` dialog organizes the development of a unique constraint through the following dialog tabs: `General` and `Definition`. The `SQL` tab displays the SQL code generated by dialog selections.
+
+
+
+Use the fields in the `General` tab to identify the unique constraint:
+
+- Use the `Name` field to add a descriptive name for the unique constraint. The name will be displayed in the `Browser` tree control.
+
+Click the `Definition` tab to continue.
+
+
+
+Use the fields in the `Definition` tab to define the unique constraint:
+
+- Click inside the `Columns` field and select one or more column names from the drop-down listbox. To delete a selection, click the `x` to the left of the column name. The unique constraint should be different from the primary key constraint defined for the same table; the selected column(s) for the constraints must be distinct.
+- Use `Include columns` field to specify columns for `INCLUDE` clause of the constraint. This option is available in Postgres 11 and later.
+- Select the name of the tablespace in which the unique constraint will reside from the drop-down listbox in the `Tablespace` field.
+- Select the name of an index from the drop-down listbox in the `Index` field. This field is optional. Adding a unique constraint will automatically create a unique B-tree index on the column or group of columns listed in the constraint, and will force the column(s) to be marked NOT NULL.
+- Use the `Fill Factor` field to specify a fill factor for the table and index. The fill factor for a table is a percentage between 10 and 100. 100 (complete packing) is the default.
+- Move the `Deferrable?` switch to the `Yes` position to specify the timing of the constraint is deferrable and can be postponed until the end of the statement. The default is `No`.
+- If enabled, move the `Deferred?` switch to the `Yes` position to specify the timing of the constraint is deferred to the end of the statement. The default is `No`.
+
+Click the `SQL` tab to continue.
+
+Your entries in the `Unique constraint` dialog generate a SQL command (see an example below). Use the `SQL` tab for review; revisit or switch tabs to make any changes to the SQL command.
+
+**Example**
+
+The following is an example of the sql command generated by user selections in the `Unique constraint` dialog:
+
+
+
+The example shown demonstrates creating a unique constraint named `name_con` on the `name` column of the `distributors` table.
+
+- Click the `Info` button (i) to access online help. View context-sensitive help in the `Tabbed browser`, where a new tab displays the PostgreSQL core documentation.
+- Click the `Save` button to save work.
+- Click the `Cancel` button to exit without saving work.
+- Click the `Reset` button to restore configuration parameters.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/index.mdx
new file mode 100644
index 00000000000..0486c7cec51
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/index.mdx
@@ -0,0 +1,18 @@
+---
+title: "Creating or Modifying a Table"
+---
+
+
+
+
+PEM provides dialogs that allow you to modify all table properties and attributes.
+
+To access a dialog that allows you to create a database object, right-click on the object type in the `Browser` tree control, and select the `Create` option for that object. For example, to create a new table, Select a database from the tree control, select the schema under the database, right-click on the *Tables* node, and select *Create Table...*
+
+Contents:
+
+
+
+check\_dialog column\_dialog compound\_trigger\_dialog exclusion\_constraint\_dialog foreign\_key\_dialog index\_dialog primary\_key\_dialog rls\_policy\_dialog rule\_dialog table\_dialog trigger\_dialog unique\_constraint\_dialog
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/index.mdx
new file mode 100644
index 00000000000..37eb9b58161
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/05_toc_pem_management_basics/index.mdx
@@ -0,0 +1,48 @@
+---
+title: "Management Basics"
+---
+
+
+
+
+PEM provides a graphical interface that you can use to simplify management of your Postgres servers and the objects that reside on them.
+
+The Grant Wizard simplifies the task of privilege management; to open the Grant Wizard, highlight the name of a server, database, or schema in the PEM client tree control, and select `Grant Wizard...` from the `Tools` menu.
+
+Contents:
+
+
+
+grant\_wizard
+
+
+
+PEM provides an easy to use environment in which to manage restore points, import/export tasks, and organize vacuum/analyze management.
+
+Contents:
+
+
+
+add\_restore\_point\_dialog import\_export\_data maintenance storage\_manager
+
+
+
+A powerful, but user-friendly interface provides an easy way to use take backups and create copies of databases or database objects.
+
+Contents:
+
+
+
+backup\_dialog backup\_globals\_dialog backup\_server\_dialog restore\_dialog
+
+
+
+You can also use the client to manage objects that reside on managed and unmanaged database servers:
+
+Contents:
+
+
+
+managing\_cluster\_objects managing\_database\_objects modifying\_tables
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/01_managing_bart_prerequisites.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/01_managing_bart_prerequisites.mdx
new file mode 100644
index 00000000000..f1599b24af2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/01_managing_bart_prerequisites.mdx
@@ -0,0 +1,16 @@
+---
+title: "Prerequisites for managing BART"
+---
+
+
+
+
+- Before adding a BART server to the PEM console, you must manually install and configure BART on the BART host. For more information about installing and configuring BART, please see the `BART Installation Guide` available at:
+
+
+
+
+
+
+
+Use the fields on the `Notifications` tab to specify the email notification settings for restoring the backup.
+
+- Use the `Send the notifications` field to specify when you want the email notifications to be sent.
+- Use the `Email group` field to specify the email group that should receive the email notification.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/index.mdx
new file mode 100644
index 00000000000..28df15307fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/06_toc_pem_bart_management/index.mdx
@@ -0,0 +1,40 @@
+---
+title: "Managing a BART Server"
+---
+
+
+
+
+
+
+Postgres Enterprise Manager (PEM) is designed to assist database administrators, system architects, and performance analysts when administering, monitoring, and tuning PostgreSQL and Advanced Server database servers.
+
+The EDB Backup and Recovery Tool (BART) is an administrative utility providing simplified backup and recovery management for multiple local or remote EDB Postgres Advanced Server and PostgreSQL database servers. For more information about BART, please visit the EnterpriseDB website at:
+
+>
+
+Note
+
+
+
+You can specify either `Transaction ID` or `Timestamp` for the point-in-time recovery.
+
+
+
+managing\_bart\_prerequisites
+
+
+
+You must add a BART server to the PEM console and then associate that BART server with the database server whose backup you want to manage with BART. For more information, see:
+
+
+
+configuring\_bart\_server associating\_bart\_server\_with\_database\_server
+
+
+
+After you associate the BART server with the database server, you will be able to view the details of the backups in the dashboard. You can perform operations such as scheduling a backup or restoring a backup. For more information, see:
+
+
+
+viewing\_bart\_dashboard scheduling\_bart\_backups scheduling\_bart\_obsolete\_backups\_deletion bart\_backup\_dialog restoring\_bart\_backups
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/01_sp_installing_sql_profiler.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/01_sp_installing_sql_profiler.mdx
new file mode 100644
index 00000000000..b6d1d72df1e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/01_sp_installing_sql_profiler.mdx
@@ -0,0 +1,92 @@
+---
+title: "Installing SQL Profiler"
+---
+
+
+
+
+SQL Profiler allows a database superuser to locate and optimize poorly-running SQL code. Users of Microsoft SQL Server’s Profiler will find PEM’s SQL Profiler very similar in operation and capabilities. SQL Profiler is installed with each Advanced Server instance; if you are using PostgreSQL, you must download the SQL Profiler installer or packages and install the SQL Profiler product into each managed database instance you wish to profile.
+
+SQL Profiler is officially supported only on the EnterpriseDB distributions of PostgreSQL version 9.4 or above and Advanced Server version 9.4 or above. The plugin is distributed via StackBuilder, or is available from the [EnterpriseDB website](https://www.enterprisedb.com/advanced-downloads)
+
+You can use the graphical installer to install any version of SQL Profiler on Windows platform.
+
+On Linux, if you have installed your database server through graphical installer then you must use the graphical installer to install the SQL Profiler. If you have installed your database server using the RPM or DEB package, then you must use the RPM or DEB package to install the SQL Profiler.
+
+## Installing SQL Profiler on Windows
+
+To invoke the SQL Profiler graphical installer, assume superuser privileges (or `Administrator` privileges on Windows), navigate into the directory that contains the installer, and invoke the installer:
+
+> `sqlprofiler-pg-
+
+
+
+You can install SQL Profiler using rpm on RHEL or Centos 6 or 7, using yum command as root user:
+
+> `yum install postgresql
+
+Note
+
+
+
+You may be required to add the `sslutils` package to your PostgreSQL database servers before installing SQL Profiler.
+
+
+
+
+
+You can install SQL Profiler using DEB on Debian 9.x or Ubuntu 18, using apt command as root user:
+
+> `apt install postgresql-
+
+Note
+
+
+
+You may be required to add the `sslutils` package to your PostgreSQL database servers before installing SQL Profiler.
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/05_sp_sql_profiler_tab.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/05_sp_sql_profiler_tab.mdx
new file mode 100644
index 00000000000..afb93fa2b5d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/05_sp_sql_profiler_tab.mdx
@@ -0,0 +1,88 @@
+---
+title: "The SQL Profiler Tab"
+---
+
+
+
+
+## Toolbar Options
+
+Toolbar options on the SQL Profiler tab allow you to define new traces, start or stop existing traces, open and search through previous traces, and filter trace results.
+
+
+
+Use the following options to manage your SQL Profiler traces:
+
+| Option | Action | Shortcut |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| `Menu` | Use options accessed through the drop\_down menu icon to manage SQL Profiler traces. | Accesskey + O |
+| `Start Trace` | Select the `Start Trace` icon to start a new trace, using the attributes (user names, database names, comments, etc) that were defined for the trace currently displayed in the SQL Profiler dialog. | Accesskey + S |
+| `Stop Trace` | Select the `Stop Trace` icon to stop an executing trace. | Accesskey + Q |
+| `Refresh Trace` | Select the `Refresh Trace` icon to update the display to include any recent changes to an active trace. | Accesskey + R |
+| `Clear Trace` | Select the `Clear Trace` icon to delete the trace and close the SQL Profiler window. | Accesskey + C |
+| `Filter` | Select the `Filter` icon to define a new filter, or apply an existing filter to the trace. | Accesskey + T |
+| `Information` | Select the information icon to view the properties of the trace displayed in the SQL Profiler window. | Accesskey + P |
+| `Index Advisor` | Select the `Index Advisor` icon to open the [PEM Index Advisor](../07_toc_pem_sql_profiler/#sp_index_advisor). \| Ac | cesskey + I |
+| `Download Trace` | Use options accessed through the `Download Trace` menu to download a CSV file that contains the trace events shown on the current page or the complete set of trace data. | Accesskey + X |
+| `Column Picker` | Click the `Column Picker` icon to choose the columns to be displayed in below table. | Accesskey + W |
+
+## Viewing Trace Data
+
+The SQL Profiler tab is divided into three panes:
+
+- The top of the tabbed browser window (the trace data pane) displays a list of the SQL commands executed during the trace.
+- The lower-left panel dislays the SQL query that was executed, or the metrics gathered during the execution.
+- The lower-right panel displays the query execution plan; you can view the execution plan in a Text-based form, or as a Graphical Plan.
+
+
+
+**The Trace Data Pane**
+
+The Trace Data pane displays the SQL commands executed during the trace. By default, the commands are displayed in the order that the command was executed.
+
+Double-click a column heading to sort the trace by the column values; double-click the column heading a second time to toggle the data in the column to be in ascending or descending order.
+
+Use the drop-down listbox next to the `Show queries per page` label to specify the number of events that SQL Profiler should display in the pane. Select from 20, 50, 100, 200, 500, 1000, or 2000. The default is 500.
+
+If the number of events in the trace exceeds the count of events per page, use the page selector controls (located in the top left corner of the table) to navigate through pages of the trace.
+
+To include or exclude events from the currently displayed trace, select the Filter icon from the SQL Profiler toolbar. The Trace Filter dialog will allow you to define and apply a filter that will screen the displayed trace.
+
+**The Query/Metrics Pane**
+
+The Query/Metrics pane is located in the lower-left corner of the SQL Profiler window. The tabs provide detailed information about the currently selected query:
+
+- The `SQL Query` tab displays the text of the query that is currently highlighted in Trace Data pane.
+- The `Metrics` tab displays detailed statistical information about the execution of the query. The table below describes the metrics that are displayed in the Metrics dialog; the percentages listed describe the percentage of the total quantity of the parameter that is attributed to the selected SQL command:
+
+| **Property** | **Description** |
+|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Executed (\#) | The number of times that the selected SQL command executed. |
+| Execution (%) | The percentage of the execution count that the SQL command represents. For example if the trace profiles 4 SQL commands, each command will represent 25% of the trace execution %. |
+| Duration (%) | The percentage of the total trace time consumed by the highlighted SQL Command. |
+| Rows updated (%) | The percentage of the rows updated during the trace that were updated by the selected SQL command. |
+| Page faults (%) | The percentage of the page faults that occur during the trace that can be attributed to the selected SQL command. |
+| Page reclaims (%) | The percentage of the pages reclaimed during the trace that can be attributed to the selected SQL command. |
+| Swaps (%) | The percentage of swaps that occur during the trace that can be attributed to the selected SQL command. |
+| File system in (%) | The percentage of bytes written to disk during the trace that can be attributed to the selected SQL command. |
+| File system out (%) | The percentage of bytes read from disk during the trace that can be attributed to the selected SQL command. |
+| Signals received (%) | Currently unused. |
+| Messages received | (%)Currently unused. |
+| Messages sent (%) | Currently unused. |
+| Voluntary context switches | (%)Currently unused. |
+| Involuntary context switches | (%)Currently unused. |
+| Shared blocks read (%) | The percentage of the shared blocks read by the highlighted SQL command. |
+| Shared blocks written (%) | The percentage of the shared blocks written by the highlighted SQL command. |
+| Shared blocks hit (%) | The percentage of the shared blocks hit by the highlighted SQL command. |
+| Local blocks read (%) | The percentage of local blocks read by the highlighted SQL command. |
+| Local blocks written (%) | The percentage of local blocks written by the highlighted SQL command. |
+| Local blocks hit (%) | The percentage of local blocks hit by the highlighted SQL commands. |
+| Temporary blocks read (%) | The percentage of the temporary blocks read by the highlighted SQL commands. |
+| Temporary blocks written (%) | The percentage of the temporary blocks written by the highlighted SQL commands. |
+
+**The Explain Pane**
+
+The Graphical or Text-based explain pane displays one of two representations of the query execution plan for the selected query.
+
+- Select the Text-based Plan tab to display the execution plan for the currently highlighted event in text format:
+- Select the Graphical-based Plan tab to display a graphical interpretation of the execution plan of the highlighted query. For more information about interpreting the graphical query plan, see [Interpreting the Graphical Query Plan](../08_toc_pem_developer_tools/#pem_interpreting_graphical_query).
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/index.mdx
new file mode 100644
index 00000000000..21d10f5af7b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/07_toc_pem_sql_profiler/index.mdx
@@ -0,0 +1,18 @@
+---
+title: "SQL Profiler"
+---
+
+
+
+
+SQL Profiler captures statistical information and query execution plans for SQL statements executed during a trace session. You can use the information stored by SQL Profiler to identify performance issues. Before using SQL Profiler, you must [install and configure SQL Profiler](07_toc_pem_sql_profiler/#sp_installing_sql_profiler) on each database you intend to profile.
+
+Contents:
+
+
+
+Note
+
+
+
+It is recommended that you disable the index advisor while using the pg\_dump functionality.
+
+
+
+sp\_installing\_sql\_profiler sp\_configuring\_sql\_profiler sp\_create\_new\_trace sp\_index\_advisor sp\_sql\_profiler\_tab
+
+
+
+SQL Profiler can support as many as 15 concurrently active traces. Open traces are displayed on the SQL Profiler tab.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/01_debugger.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/01_debugger.mdx
new file mode 100644
index 00000000000..d5af9b3d042
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/01_debugger.mdx
@@ -0,0 +1,82 @@
+---
+title: "pgAdmin Debugger"
+---
+
+
+
+
+
+
+The debugger may be used to debug PL/pgSQL functions in PostgreSQL, as well as EDB-SPL functions, stored procedures and packages in Advanced Server. The Debugger is available as an extension for your PostgreSQL installation, and is distributed as part of Advanced Server. You must have superuser privileges to use the debugger.
+
+Before using the debugger, you must modify the `postgresql.conf` file, adding the server-side debugger components to the the value of the `shared_preload_libraries` parameter:
+
+> shared\_preload\_libraries = '$libdir/`other_libraries`/plugin\_debugger'
+
+After modifying the `shared_preload_libraries` parameter, restart the server to apply the changes.
+
+The debugger may be used for either in-context debugging or direct debugging of a target function or procedure. When you use the debugger for in-context debugging, you set a breakpoint at the first line of a program; when a session invokes the target, control is transferred to the debugger. When using direct debugging, the debugger prompts you for any parameters required by the target, and then allows you to step through the code.
+
+**In-context Debugging**
+
+To set a breakpoint at the first line of a program, right-click the name of the object you would like to debug, and select `Set breakpoint` from the `Debugging` sub-menu. The debugger window will open, waiting for another session to invoke the program.
+
+
+
+When another session invokes the target, the debugger will display the code, allowing you to add break points, or step through line-by-line. The other session is suspended until the debugging completes; then control is returned to the session.
+
+
+
+**Direct Debugging**
+
+To use the debugger for direct debugging, right click on the name of the object that you wish to debug in the pgAdmin tree control and select `Debug` from the `Debugging` sub-menu. The debugger window will open, prompting you for any values required by the program:
+
+
+
+Use the fields on the `Debugger` dialog to provide a value for each parameter:
+
+> - The `Name` field contains the formal parameter name.
+> - The `Type` field contains the parameter data type.
+> - Check the `Null?` checkbox to indicate that the parameter is a NULL value.
+> - Check the `Expression?` checkbox if the Value field contains an expression.
+> - Use the `Value` field to provide the parameter value that will be passed to the program. When entering parameter values, type the value into the appropriate cell on the grid, or, leave the cell empty to represent NULL, enter '' (two single quotes) to represent an empty string, or to enter a literal string consisting of just two single quotes, enter ''. PostgreSQL 8.4 and above supports variadic function parameters. These may be entered as a comma-delimited list of values, quoted and/or cast as required.
+> - Check the `Use default?` checkbox to indicate that the program should use the value in the Default Value field.
+> - The `Default Value` field contains the default value of the parameter.
+
+Provide values required by the program, and click the `Debug` button to start stepping through the program, The values of the arguments provided here are saved. The values will be pre-filled next time the dialog opens. To clear the values, use the `Clear All` button.
+
+
+
+**Using the Debugger**
+
+The main debugger window consists of two panels and a context-sensitive toolbar. Use toolbar icons to manage breakpoints and step into or through code; hover over an icon for a tooltip that identifies the option associated with the icon. The toolbar options are:
+
+
+
+| Option | Action |
|---|---|
Step into | Click the |
Step over | Click the |
Continue/Start | Click the |
Toggle breakpoint | Use the |
Clear all breakpoints | Click the |
Stop | Click the |
| Icon | Behavior | Shortcut |
|---|---|---|
Open File | Click the Open File icon to display a previously saved query in the SQL Editor. | Accesskey + O |
Save | Click the
| Accesskey + S |
Find | Use the
| Cmd+F Cmd+G Cmd+Shift+G Cmd+Shift+F Alt+G |
Copy | Click the Copy icon to copy the content that is currently highlighted in the Data Output panel. when in View/Edit data mode. | Accesskey + C |
Paste | Click the Paste icon to paste a previously row into a new row when in View/Edit data mode. | Accesskey + P |
Delete | Click the Delete icon to mark the selected rows for delete when in View/Edit data mode. | Accesskey + D |
Edit | Use options on the
| Tab Shift+Tab Cmd+/ Cmd+. Shift+Cmd+/ |
Filter | Click the
| Accesskey + F |
| Limit Selector | Select a value in the Limit Selector to limit the size of the dataset to a number of rows. | Accesskey + R |
Stop | Click the Stop icon to cancel the execution of the currently running query. | Accesskey + Q |
Execute/Refresh | Click the
| F5 |
Explain |
| F7 |
Explain analyze | Click the Navigate through the
| Shift+F7 |
Commit | Click the Commit icon to commit the transaction. | Shift+CTRL+M |
Rollback | Click the Rollback icon to rollback the transaction. | Shift+CTRL+R |
Clear | Use options on the
| Accesskey + L |
Download as CSV | Click the Download as CSV icon to download the result set of the current query to a comma-separated list. You can specify the CSV settings through Preferences -> SQL Editor -> CSV output dialogue. | F8 |
Macros | Click the Macros icon to manage the macros. You can create, edit or clear the macros through Manage Macros option. |
+
+- Now select server, database, user, and role to connect and click OK.
+
+
+
+- A newly created connection will now get listed in the options.
+- To connect, select the newly created connection from the dropdown list.
+
+## Macros
+
+Query Tool Macros enable you to execute pre-defined SQL queries with a single key press. Pre-defined queries can contain the placeholder $SELECTION$. Upon macro execution, the placeholder will be replaced with the currently selected text in the Query Editor pane of the Query Tool.
+
+
+
+To create a macro, select the *Manage Macros* option from the *Macros* menu on the *Query Tool*. Select the key you wish to use, enter the name of the macro, and the query, optionally including the selection placeholder, and then click the *Save* button to store the macro.
+
+
+
+To clear a macro, select the macro on the *Manage Macros* dialogue, and then click the *Clear* button.
+
+
+
+The server will prompt you for confirmation to clear the macro.
+
+
+
+To clear all macros, click on the *Clear* button on left side of the key. The server will prompt you for confirmation to clear all the rows.
+
+
+
+To execute a macro, simply select the appropriate shortcut keys, or select it from the *Macros* menu.
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/03_pem_interpreting_graphical_query.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/03_pem_interpreting_graphical_query.mdx
new file mode 100644
index 00000000000..4a9c86f1053
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/03_pem_interpreting_graphical_query.mdx
@@ -0,0 +1,62 @@
+---
+title: "Interpreting Graphical Query Plans"
+---
+
+
+
+
+The graphical explain plan provides clues that can help you identify the aspects of the selected query that consume the most resources; within the diagram, thicker lines indicate the portions of the query that are expected to take the most processing time.
+
+To view a graphical interpretation of an executed query, select `Explain` or `Explain Analyze` from the `Execute/Refresh` drop-down menu. Please note that you can use the `Explain Options` pull-aside menu to specify the level of detail displayed for each node.
+
+
+
+Hover over an icon within the plan to view details for the selected node:
+
+
+
+Each query operator (within the selected query) is represented in the graphical display by an icon. The table below describes the Advanced Server query operators:
+
+| Icon | Represents | Description |
+|----------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | Result Set | The Result Set icon represents a simple result set in the query plan. Typically, a Result Set operator is used to evaluate a query that does not fetch data from a table. |
+|  | Aggregate | The server creates an Aggregate operator whenever the query invokes an aggregate function (a function that returns a value computed from multiple rows). Aggregate functions include: AVG(), COUNT(), MAX(), MIN(), STDDEV(), SUM(), and VARIANCE(). |
+|  | Window Aggregate | The server may use a Window aggregate operator to implement windowed aggregate functions; a windowed aggregate function is a function that returns a value computed from a set of rows within the input. |
+|  | Seek | The server may use a Seek operator in any plan that includes an Index Scan operator. The Seek operator represents a probe into the heap to fetch the tuple that corresponds to an index entry (found by the Index Scan operator). |
+|  | Seq Scan | The server may use a Seq scan (sequential scan) to read through a table from beginning to end. |
+|  | Index Scan | The server may use an Index scan operator to read through a table in the order specified in the index. |
+|  | CTE Scan | The server may use a CTE Scan operator if the query performs a scan of a common table expression. |
+|  | Tuple ID Scan | The server uses a Tuple ID scan if the query uses the Tuple ID (ctid) as a constraint in a WHERE clause. |
+|  | Group | The server may use a Group operator when the query includes a GROUP BY clause. The operator requires a single input set ordered by the target column(s). |
+|  | Sort | The server may use a Sort operator when a query includes an ORDER BY clause to impose an order on a result set. |
+|  | Limit | The server may use the Limit operator to limit the size of a result set (when a query includes the LIMIT or OFFSET clause). |
+|  | Sub Plan | The server may use a Subplan operator for queries that include subselects. |
+|  | Unique | The server may use the Unique operator to remove duplicate values from a result set; the diagram will include a Unique operator if the query includes a DISTINCT clause. |
+|  | Hash | The server may use a Hash operator when joining two input sets that are not ordered by the column that controls the join. |
+|  | Hash Semi-Join | The server may use a Hash Semi-Join operator to evaluate a query that joins two tables, but returns data from only one of those tables. |
+|  | Hash Anti-Join | The server may use a Hash Anti-Join operator to evaluate a query that includes a NOT IN clause. |
+|  | Anti-Join | The server may use an Anti-Join operator to evaluate a query that includes a NOT IN clause. |
+|  | Join | The server may use a Join operator when joining two input sets that are ordered by the column that controls the join. |
+|  | Recursive Union | The server may use a Recursive Union operator if the query includes a WITH RECURSIVE clause. |
+|  | Set Operator | The server may use a Set operator if the query includes an INTERSECT, INTERSECT ALL, EXCEPT or EXCEPT ALL clause. |
+|  | Hash Set Operator (Setop) Intersect | The server may use an Intersect Set operator if the query includes an INTERSECT clause. |
+|  | Hash Set Operator (Setop) Intersect All | The server may use an Intersect Set operator if the query includes an INTERSECT ALL. |
+|  | Hash Set Operator (Setop) Except | The server may use an Except Set operator if the query includes an EXCEPT. |
+|  | Hash Set Operator (Setop) Except All | The server may use an Except All Set operator if the query includes an EXCEPT ALL clause. |
+|  | Materialize | The server may choose to use a Materialize operator for a subselect operation (a nested query). |
+|  | Append | The server may use an Append operator to implement queries that contain a UNION clause. |
+|  | Nested Loop | The server may use a Nested Loop operator to perform a join between two tables. When implementing a nested loop, the server searches for rows from the inner table that match the corresponding row in the outer table. |
+|  | Merge Join | The server may use a Merge Join operator to join two tables. A Merge Join requires two sets of inputs, where each set is ordered by the column used for the comparison. |
+|  | Merge Semi-Join | The server may use a Merge Semi-Join operator to evaluate a query that joins two tables, but returns data from only one of those tables. |
+|  | Merge Anti-Join | The server may use a Merge Anti-Join operator to evaluate a query that includes a NOT IN clause. |
+|  | Nested Loop Semi-Join | The server may use a Nested Semi-Join operator to evaluate a query that joins two tables, but returns data fro m only one of those tables. |
+|  | Nested Loop Anti-Join | The server may use a Nested Anti-Join operator to evaluate a query that includes a NOT IN clause. |
+|  | Bitmap Index | The server may use a Bitmap Index operator when locating a subset of rows in an indexed table. |
+|  | Bitmap Heap | The server may use a Bitmap Heap operator when the query returns a subset of rows from an indexed table. |
+
+While you cannot directly specify the execution plan of a query, you can use indexes, configuration parameters and optimizer hints to direct Advanced Server as it selects from the query plans presented by the server. See the following resources for more information about query optimization:
+
+- For more information about interpreting and understanding a query plan, see Using EXPLAIN, in the PostgreSQL documentation.
+- For information about using PEM's Index Advisor, see the EDB Postgres Advanced Server Guide, available from the EnterpriseDB website at [www.enterprisedb.com](http://www.enterprisedb.com).
+- For information about using configuration parameters to influence query plans, see Query Planning, in the PostgreSQL documentation.
+- For more information about using Oracle-compatible optimizer hints, see the EDB Postgres Advanced Server Oracle Compatibility Developer's Guide, available from the EnterpriseDB website at [www.enterprisedb.com](http://www.enterprisedb.com).
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/01_viewdata_filter.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/01_viewdata_filter.mdx
new file mode 100644
index 00000000000..630ae563aa0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/01_viewdata_filter.mdx
@@ -0,0 +1,24 @@
+---
+title: "View/Edit Data Filter"
+---
+
+
+
+
+You can access `Data Filter dialog` by clicking on `Filtered Rows` toolbar button visible on the Browser panel or by selecting *View/Edit Data -> Filtered Rows* context menu option.
+
+This allows you to specify an SQL Filter to limit the data displayed in the edit grid window:
+
+
+
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/index.mdx
new file mode 100644
index 00000000000..a874a9ed1cd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/04_editgrid/index.mdx
@@ -0,0 +1,98 @@
+---
+title: "Reviewing and Editing Data"
+---
+
+
+
+
+To review or modify data, right click on a table or view name in the `Browser` tree control. When the context menu opens, use the `View/Edit Data` menu to specify the number of rows you would like to display in the editor panel.
+
+
+
+To modify the content of a table, each row in the table must be uniquely identifiable. If the table definition does not include an OID or a primary key, the displayed data is read only. Note that views cannot be edited; updatable views (using rules) are not supported.
+
+The editor features a toolbar that allows quick access to frequently used options, and a work environment divided into two panels:
+
+- The upper panel displays the SQL command that was used to select the content displayed in the lower panel.
+- The lower panel (the Data Grid) displays the data selected from the table or view.
+
+**The View/Edit Data Toolbar**
+
+The toolbar includes context-sensitive icons that provide shortcuts to frequently performed tasks.
+
+
+
+Hover over an icon to display a tooltip that describes the icon's functionality.
+
+
+
+Note
+
+
+
+Use SHIFT + ENTER keys to apply filter.
+
+| Icon | Behavior | Shortcut |
|---|---|---|
Save | Use the Save icon to save your changes to the currently displayed table contents. | |
Find | Use options on the Find menu to access Search and Replace functionality or to Jump to another line. | Ctrl/Cmd +F |
Copy | Click the Copy icon to copy the currently selected data. | Ctrl+C |
Paste Row | Click the Paste Row icon to paste the content that is currently on the clipboard. | |
Delete Row | Use the Delete Row icon to delete all the selected rows from the output panel. | |
Filter | Click the
| |
No limit | Use the No limit drop-down listbox to specify how many rows to display in the output panel. Select from: No limit (the default), 1000 rows, 500 rows, or 100 rows. | |
Execute/Refresh | Click the Execute/Refresh icon to execute the SQL command that is displayed in the top panel. If you have not saved modifications to the content displayed in the data grid, you will be prompted to confirm the execution. To preserve your changes before refreshing the content, click the Save toolbar button before executing the refresh. | F5 |
Stop | Click the Stop icon to cancel the execution of the currently running query. | |
Clear History | Use the Clear History drop-down menu to erase the contents of the History tab. | |
Download as CSV | Click the Download as CSV icon to download the result set of the current query to a comma-separated list. You can control the CSV settings through Preferences -> SQL Editor -> CSV output dialogue. | F8 |
+
+viewdata\_filter
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/05_schema_diff.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/05_schema_diff.mdx
new file mode 100644
index 00000000000..062addeeb45
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/05_schema_diff.mdx
@@ -0,0 +1,85 @@
+---
+title: "Schema Diff"
+---
+
+
+
+
+**Schema Diff** is a feature that allows you to compare objects between two database or two schemas. Use the `Tools` menu to access Schema Diff.
+
+The Schema Diff feature allows you to:
+
+> - Compare and synchronize the database objects (from source to target).
+> - Visualize the differences between database objects.
+> - List the differences in SQL statement for target database objects.
+> - Generate synchronization scripts.
+
+**Note:**
+
+> - The source and target database servers must be of the same major version.
+> - If you compare two **schemas** then dependencies won't be resolved.
+
+Click on *Schema Diff* under the *Tools* menu to open a selection panel. To compare **databases** choose the source and target servers, and databases. To compare **schemas** choose the source and target servers, databases, and schemas. After selecting the objects, click on the *Compare* button.
+
+You can open multiple copies of `Schema Diff` in individual tabs simultaneously. To close a copy of Schema Diff, click the \*X\* in the upper-right hand corner of the tab bar. You can rename the panel title by right-clicking and select the "Rename Panel" option.
+
+
+
+Use the [Preferences](../03_toc_pem_client/#preferences) dialog to specify following:
+
+> - *Schema Diff* should open in a new browser tab. Set *Open in new browser tab* option to true.
+> - *Schema Diff* should ignore the whitespaces while comparing string objects. Set *Ignore whitespaces* option to true.
+> - *Schema Diff* should ignore the owner while comparing objects. Set *Ignore owner* option to true.
+
+The `Schema Diff` panel is divided into two panels; an Object Comparison panel and a DDL Comparison panel.
+
+## The Schema Diff Object Comparison Panel
+
+In the object comparison panel, you can select the source and target servers of the same major version, and databases to be compared. You can select any server listed under the browser tree whether it is connected or disconnected. If you select a server that is not connected then it will prompt you for the password before using the server.
+
+Next, select the databases that will be compared. The databases can be the same or different (and within the same server or from different servers).
+
+
+
+After you select servers and databases, click on the *Compare* button to obtain the `Comparison Result`.
+
+
+
+Use the drop-down lists of Database Objects to view the DDL statements.
+
+In the upper-right hand corner of the object comparison panel is a *Filter* option that you can use to filter the database objects based on the following comparison criteria:
+
+> - Identical – If the object is found in both databases with the same SQL statement, then the comparison result is identical.
+> - Different – If the object is found in both databases but have different SQL statements, then the comparison result is different.
+> - Source Only – If the object is found in source database only and not in target database, then the comparison result is source only.
+> - Target Only – If the object is found in target database only and not in source database, then the comparison result is target only.
+
+
+
+Click on any of the database objects in the object comparison panel to display the DDL Statements of that object in the DDL Comparison panel.
+
+## Schema Diff DDL Comparison Panel
+
+The `DDL Comparison` panel displays three columns:
+
+- The first column displays the DDL statement of the object from the source database.
+- The second column displays the DDL statement of the object from the target database.
+- The third column displays the difference in the SQL statement of the target database object.
+
+
+
+You can review the DDL statements of all the database objects to check for the differences in the SQL statements.
+
+Also, you can generate the SQL script of the differences found in the target database object based on the SQL statement of the source database object. To generate the script, select the checkboxes of the database objects in the object comparison panel and then click on the *Generate Script* button in the upper-right hand corner of the object comparison panel.
+
+
+
+Select the database objects and click on the *Generate Script* button to open the `Query Tool` in a new tab, with the difference in the SQL statement displayed in the `Query Editor`.
+
+If you have clicked on the database object to check the difference generated in the `DDL Comparison` Panel, and you have not selected the checkbox of the database object, PEM will open the `Query Tool` in a new tab, with the differences in the SQL statements displayed in the `Query Editor`.
+
+You can also use the `Copy` button to copy the difference generated in the `DDL Comparison` panel.
+
+
+
+Apply the SQL Statement in the target database to synchronize the databases.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/index.mdx
new file mode 100644
index 00000000000..38182336587
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/08_toc_pem_developer_tools/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Developer Tools"
+---
+
+
+
+
+The PEM client features powerful developer tools that you can use to execute and analyze complex SQL commands, manage data, and debug PL/SQL code.
+
+Contents:
+
+
+
+debugger query\_tool pem\_interpreting\_graphical\_query editgrid schema\_diff
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/01_pem_pgbouncer_server_agent_connection.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/01_pem_pgbouncer_server_agent_connection.mdx
new file mode 100644
index 00000000000..479f4d7e627
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/01_pem_pgbouncer_server_agent_connection.mdx
@@ -0,0 +1,16 @@
+---
+title: "Connecting PEM to pgBouncer"
+---
+
+
+
+
+Each PEM agent connects to the PEM database server using the SSL certificates for each individual user. For example, an agent with ID\#1 connects to the PEM database server using the agent1 user.
+
+
+
+Prior to PEM version 7.5, the following limitations did not allow use of the connection pooler between the PEM server and PEM agent: \* The PEM agent uses an SSL Certificate to connect the PEM database server. \* It uses an individual user identifier when connecting to the PEM database server. EnterpriseDB has modified the PEM agent to allow the agent to use a common database user (instead of the dedicated agent users) to connect the PEM database server.
+
+
+
+We recommend using pgBouncer versions equal to or later than version 1.9.0 as the connection pooler. Since versions 1.9.0 or later support cert authentication; PEM Agents can connect to pgBouncer using SSL certificates.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/02_pem_pgbouncer_preparing_dbserver.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/02_pem_pgbouncer_preparing_dbserver.mdx
new file mode 100644
index 00000000000..0e6c277b65a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/02_pem_pgbouncer_preparing_dbserver.mdx
@@ -0,0 +1,52 @@
+---
+title: "Preparing the PEM Server for pgBouncer Connections"
+---
+
+
+
+
+You must configure the PEM database server to accept connections from pgBouncer; the following example demonstrates the steps required to prepare the PEM database server.
+
+1. Create a dedicated user named pgbouncer on the PEM database server. For example:
+
+ pem=# CREATE USER pgbouncer PASSWORD 'ANY_PASSWORD' LOGIN;
+ CREATE ROLE
+
+2. Create a user named pem\_admin1 (a non-super user) with pem\_admin and pem\_agent\_pool role membership on the PEM database server. For example:
+
+ pem=# CREATE USER pem_admin1 PASSWORD 'ANY_PASSWORD' LOGIN CREATEROLE;
+ CREATE ROLE
+ pem=# GRANT pem_admin, pem_agent_pool TO pem_admin1;
+ GRANT ROLE
+
+3. Grant CONNECT privilege to the pgbouncer user on the pem database. For example:
+
+ pem=# GRANT CONNECT ON DATABASE pem TO pgbouncer ;GRANT USAGE ON SCHEMA pem TO pgbouncer;
+ GRANT
+
+4. Grant USAGE privilege to the pgbouncer user for the pem schema on the pem database. For example:
+
+ pem=# GRANT USAGE ON SCHEMA pem TO pgbouncer;
+ GRANT
+
+5. Grant EXECUTE privilege to the pgbouncer user on the pem.get\_agent\_pool\_auth(text) function in the pem database. For example:
+
+ pem=# GRANT EXECUTE ON FUNCTION pem.get_agent_pool_auth(text) TO pgbouncer;
+ GRANT
+
+6. Use the pem.create\_proxy\_agent\_user(varchar) function to create a user named pem\_agent\_user1 on the PEM database server. The function will create a user with the same name with a random password, and grant `pem_agent` and `pem_agent_pool` roles to the user. This allows pgBouncer to use a proxy user on behalf of the agent. For example:
+
+ pem=# SELECT pem.create_proxy_agent_user('pem_agent_user1');
+ create_proxy_agent_user
+ -------------------------
+ (1 row)
+
+7. Add the following entries to the start of the `pg_hba.conf` file of the PEM database server; this will allow pgBouncer user to connect to the pem database using the md5 authentication method. For example:
+
+ # Allow the PEM agent proxy user (used by
+ # pgbouncer) to connect the to PEM server using
+ # md5
+
+ local pem pgbouncer,pem_admin1 md5
+
+After configuring the PEM server, you should configure pgBouncer.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/03_pem_pgbouncer_configuring_pgbouncer.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/03_pem_pgbouncer_configuring_pgbouncer.mdx
new file mode 100644
index 00000000000..7633fd63acf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/03_pem_pgbouncer_configuring_pgbouncer.mdx
@@ -0,0 +1,97 @@
+---
+title: "Configuring pgBouncer"
+---
+
+
+
+
+You must configure pgBouncer to work with the PEM database server. In our example, we will run pgBouncer as the enterprisedb system user. The following steps outline the process of configuring pgBouncer (version >= 1.9).
+
+1. Open a terminal window and navigate into the pgBouncer directory.
+
+2. Change the owner of the etc directory for pgBouncer (where pgbouncer.ini resides) to enterprisedb, and change the directory permissions to 0700. For example:
+
+ $ chown enterprisedb:enterprisedb /etc/edb/pgbouncer1.9
+ $ chmod 0700 /etc/edb/pgbouncer1.9
+
+3. Change the contents of the pgbouncer.ini or edb-pgbouncer.ini file as follows:
+
+ [databases]
+ ;; Change the pool_size according to maximum connections allowed
+ ;; to the PEM database server as required.
+ ;; 'auth_user' will be used for authenticate the db user (proxy
+ ;; agent user in our case)
+ pem = port=5444 host=/tmp dbname=pem auth_user=pgbouncer pool_size=80 pool_mode=transaction
+ * = port=5444 host=/tmp dbname=pem auth_user=pgbouncer pool_size=10
+ [pgbouncer]
+ logfile = /var/log/edb/pgbouncer1.9/edb-pgbouncer-1.9.log
+ pidfile = /var/run/edb/pgbouncer1.9/edb-pgbouncer-1.9.pid
+ listen_addr = *
+ ;; Agent needs to use this port to connect the pem database now
+ listen_port = 6432
+ ;; Require to support for the SSL Certificate authentications
+ ;; for PEM Agents
+ client_tls_sslmode = require
+ ;; These are the root.crt, server.key, server.crt files present
+ ;; in the present under the data directory of the PEM database
+ ;; server, used by the PEM Agents for connections.
+ client_tls_ca_file = /var/lib/edb/as11/data/root.crt
+ client_tls_key_file = /var/lib/edb/as11/data/server.key
+ client_tls_cert_file = /var/lib/edb/as11/data/server.crt
+ ;; Use hba file for client connections
+ auth_type = hba
+ ;; Authentication file, Reference:
+ ;; https://pgbouncer.github.io/config.html#auth_file
+ auth_file = /etc/edb/pgbouncer1.9/userlist.txt
+ ;; HBA file
+ auth_hba_file = /etc/edb/pgbouncer1.9/hba_file
+ ;; Use pem.get_agent_pool_auth(TEXT) function to authenticate
+ ;; the db user (used as a proxy agent user).
+ auth_query = SELECT * FROM pem.get_agent_pool_auth($1)
+ ;; DB User for administration of the pgbouncer
+ admin_users = pem_admin1
+ ;; DB User for collecting the statistics of pgbouncer
+ stats_users = pem_admin1
+ server_reset_query = DISCARD ALL
+ ;; Change based on the number of agents installed/required
+ max_client_conn = 500
+ ;; Close server connection if its not been used in this time.
+ ;; Allows to clean unnecessary connections from pool after peak.
+ server_idle_timeout = 60
+
+4. Use the following command to create and update the /etc/edb/pgbouncer1.9/userlist.txt authentication file for pgBouncer:
+
+ pem=# COPY (
+ SELECT 'pgbouncer'::TEXT, 'pgbouncer_password'
+ UNION ALL
+ SELECT 'pem_admin1'::TEXT, 'pem_admin1_password'
+ ) TO '/etc/edb/pgbouncer1.9/userlist.txt'
+ WITH (FORMAT CSV, DELIMITER ' ', FORCE_QUOTE *);
+ COPY 2
+
+> NOTE: A super user cannot invoke the PEM authentication query function pem.get\_proxy\_auth(text). If the pem\_admin user is a super user, you must add the password to the authentication file, which is enterprisedb in the above example.
+
+1. Create an HBA file (/etc/edb/pgbouncer1.9/hba\_file) for pgBouncer that contains the following content:
+
+ # Use authentication method md5 for the local connections to
+ # connect pem database & pgbouncer (virtual) database.
+ local pgbouncer all md5
+
+ # Use authentication method md5 for the remote connections to
+ # connect to pgbouncer (virtual database) using enterprisedb
+ # user.
+ host pgbouncer,pem pem_admin1 0.0.0.0/0 md5
+ # Use authentication method cert for the TCP/IP connections to
+ # connect the pem database using pem_agent_user1
+ hostssl pem pem_agent_user1 0.0.0.0/0 cert
+
+2. Change the owner of the HBA file (/etc/edb/pgbouncer1.9/hba\_file) to enterprisedb, and change the directory permissions to 0600. For example:
+
+ $ chown enterprisedb:enterprisedb /etc/edb/pgbouncer1.9/hba_file
+ $ chmod 0600 /etc/edb/pgbouncer1.9/hba_file
+
+3. Enable the pgBouncer service, and start the service. For example:
+
+ $ systemctl enable edb-pgbouncer-1.9
+ Created symlink from /etc/systemd/system/multi-user.target.wants/edb-pgbouncer-1.9.service to /usr/lib/systemd/system/edb-pgbouncer-1.9.service.
+ $ systemctl start edb-pgbouncer-1.9
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/04_pem_pgbouncer_configuring_pem_agent.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/04_pem_pgbouncer_configuring_pem_agent.mdx
new file mode 100644
index 00000000000..e684c3bdf88
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/04_pem_pgbouncer_configuring_pem_agent.mdx
@@ -0,0 +1,75 @@
+---
+title: "Configuring the PEM Agent to use pgBouncer"
+---
+
+
+
+
+You can use an RPM package to install a PEM Agent; for detailed installation information, please see the PEM Installation Guide, available from the [EnterpriseDB website](https://www.enterprisedb.com/resources/product-documentation)
+
+Please note that PEM Agent which is responsible for sending SNMP notifications should not be configured with pgBouncer. For Example - If default PEM Agent installed along with PEM Server is used for SNMP notifications, then it should not be configured with pgBouncer.
+
+## Configuring a New PEM Agent (installed using an RPM)
+
+After using an RPM package to install the PEM agent, you will need to configure it to work it against a particular PEM database server. Use the following command:
+
+ $ PGSSLMODE=require PEM_SERVER_PASSWORD=pem_admin1_password /usr/edb/pem/agent/bin/pemworker --register-agent --pem-server 172.16.254.22 --pem-port 6432 --pem-user pem_admin1 --pem-agent-user pem_agent_user1 --display-name *Agent_Name*
+ Postgres Enterprise Manager Agent registered successfully!
+
+In above command, the command line argument --pem-agent-user instructs the agent to create an SSL certificate and key pair for the pem\_agent\_user1 database user in /root/.pem directory. For example:
+
+ /root/.pem/pem_agent_user1.crt
+ /root/.pem/pem_agent_user1.key
+
+They will be used by the PEM agent to connect to the PEM database server as pem\_agent\_user1. It will also create /usr/edb/pem/agent/etc/agent.cfg.
+
+You will find a line mentioning the agent-user to be used in the agent.cfg configuration file. For example:
+
+ $ cat /usr/edb/pem/agent/etc/agent.cfg
+ [PEM/agent]
+ pem_host=172.16.254.22
+ pem_port=6432
+ agent_id=12
+ agent_user=pem_agent_user1
+ agent_ssl_key=/root/.pem/pem_agent_user1.key
+ agent_ssl_crt=/root/.pem/pem_agent_user1.crt
+ log_level=warning
+ log_location=/var/log/pem/worker.log
+ agent_log_location=/var/log/pem/agent.log
+ long_wait=30
+ short_wait=10
+ alert_threads=0
+ enable_smtp=false
+ enable_snmp=false
+ enable_webhook=false
+ max_webhook_retries=3
+ allow_server_restart=true
+ max_connections=0
+ connect_timeout=-1
+ connection_lifetime=0
+ allow_batch_probes=false
+ heartbeat_connection=false
+
+## Configuring an Existing PEM Agent (installed using an RPM)
+
+If you are using an existing PEM agent, you can copy the SSL certificate and key files to the target machine, and reuse the files. You will need to modify the files, adding a new parameter and replacing some parameters in the existing `agent.cfg` file.
+
+Add a line for agent\_user to be used for the agent. For example:
+
+ agent_user=pem_agent_user1
+
+Update the port to specify the pgBouncer port. For example:
+
+ pem_port=6432
+
+Update the certificate and key path locations. For example:
+
+ agent_ssl_key=/root/.pem/pem_agent_user1.key
+ agent_ssl_crt=/root/.pem/pem_agent_user1.crt
+
+Please note: as an alternative, you can run the agent self registration, but that will create a new agent id. If you do run the agent self-registration, you must replace the new agent id with existing id, and disable the entry for the new agent id in the pem.agent table. For example:
+
+ pem=# UPDATE pem.agent SET active = false WHERE id = *new_agent_id*;
+ UPDATE 1
+
+Please keep a backup of the existing SSL certificate, key file, and agent configuration file.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/index.mdx
new file mode 100644
index 00000000000..fea89226d65
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/09_toc_pem_configure_pgbouncer/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Configuring pgBouncer for use with PEM Agents"
+---
+
+
+
+
+pgBouncer is a lightweight connection pooler for Postgres. You can use pgBouncer to limit the number of connections from the PEM Agent towards the Postgres Enterprise Manager (PEM) server on a non-Windows machine.
+
+Contents:
+
+
+
+pem\_pgbouncer\_server\_agent\_connection pem\_pgbouncer\_preparing\_dbserver pem\_pgbouncer\_configuring\_pgbouncer pem\_pgbouncer\_configuring\_pem\_agent
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/01_using_pgagent.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/01_using_pgagent.mdx
new file mode 100644
index 00000000000..e9d17c943fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/01_using_pgagent.mdx
@@ -0,0 +1,22 @@
+---
+title: "Using pgAgent"
+---
+
+
+
+
+pgAgent is a scheduling agent that runs and manages jobs; each job consists of one or more steps and schedules. If two or more jobs are scheduled to execute concurrently, pgAgent will execute the jobs in parallel (each with its own thread).
+
+A step may be a series of SQL statements or an operating system batch/shell script. Each step in a given job is executed when the previous step completes, in alphanumeric order by name. Switches on the `pgAgent Job` dialog (accessed through the `Properties` context menu) allow you to modify a job, enabling or disabling individual steps as needed.
+
+Each job is executed according to one or more schedules. Each time the job or any of its schedules are altered, the next runtime of the job is re-calculated. Each instance of pgAgent periodically polls the database for jobs with the next runtime value in the past. By polling at least once every minute, all jobs will normally start within one minute of the specified start time. If no pgAgent instance is running at the next runtime of a job, it will run as soon as pgAgent is next started, following which it will return to the normal schedule.
+
+When you highlight the name of a defined job in the browser tree control, the `Properties` tab of the main PEM window will display details about the job, and the `Statistics` tab will display details about the job's execution.
+
+## Security concerns
+
+pgAgent is a very powerful tool, but does have some security considerations that you should be aware of:
+
+**Database password** - `DO NOT` be tempted to include a password in the pgAgent connection string - on Unix systems it may be visible to all users in 'ps' output, and on Windows systems it will be stored in the registry in plain text. Instead, use a libpq `~/.pgpass` file to store the passwords for every database that pgAgent must access. Details of this technique may be found in the [PostgreSQL documentation on .pgpass file](http://www.postgresql.org/docs/current/static/libpq-pgpass.html).
+
+**System/database access** - all jobs run by pgAgent will run with the security privileges of the pgAgent user. SQL steps will run as the user that pgAgent connects to the database as, and batch/shell scripts will run as the operating system user that the pgAgent service or daemon is running under. Because of this, it is essential to maintain control over the users that are able to create and modify jobs. By default, only the user that created the pgAgent database objects will be able to do this - this will normally be the PostgreSQL superuser.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/02_pgagent_install.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/02_pgagent_install.mdx
new file mode 100644
index 00000000000..12b373e77a9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/10_pgagent/02_pgagent_install.mdx
@@ -0,0 +1,88 @@
+---
+title: "Installing pgAgent"
+---
+
+
+
+
+pgAgent runs as a daemon on Unix systems, and a service on Windows systems. In most cases it will run on the database server itself - for this reason, pgAgent is not automatically configured when PEM is installed. In some cases however, it may be preferable to run pgAgent on multiple systems, against the same database; individual jobs may be targeted at a particular host, or left for execution by any host. Locking prevents execution of the same instance of a job by multiple hosts.
+
+## Database setup
+
+Before using PEM to manage pgAgent, you must create the pgAgent extension in the maintenance database registered with PEM. To install pgAgent on a PostgreSQL host, connect to the `postgres` database, and navigate through the `Tools` menu to open the Query tool. For server versions 9.1 or later, and pgAgent 3.4.0 or later, enter the following command in the query window, and click the `Execute` icon:
+
+ CREATE EXTENSION pgagent;
+
+This command will create a number of tables and other objects in a schema called 'pgagent'.
+
+The database must also have the pl/pgsql procedural language installed - use the PostgreSQL `CREATE LANGUAGE` command to install pl/pgsql if necessary. To install pl/pgsql, enter the following command in the query window, and click the `Execute` icon:
+
+ CREATE LANGUAGE plpgsql;
+
+## Daemon installation on Unix
+
+
+
+
+
+To install the pgAgent daemon on a Unix system, you will normally need to have root privileges to modify the system startup scripts. Modifying system startup scripts is quite system-specific so you should consult your system documentation for further information.
+
+The program itself takes few command line options, most of which are only needed for debugging or specialised configurations:
+
+ Usage:
+ /path/to/pgagent [options]
+
+Note
+
+
+
+pgAgent is available in Debian/Ubuntu (DEB) and Redhat/Fedora (RPM) packages for Linux users, as well as source code. See the [pgAdmin Website](https://www.pgadmin.org/download/). for more information.
+
+
+
+
+
+pgAgent can install itself as a service on Windows systems. The command line options available are similar to those on Unix systems, but include an additional parameter to tell the service what to do:
+
+ Usage:
+ pgAgent REMOVE
+
+Note
+
+
+
+pgAgent is available in a pre-built installer if you use [EnterpriseDB's PostgreSQL Installers](https://www.enterprisedb.com/downloads/postgres-postgresql-downloads). Use the StackBuilder application to download and install it. If installed in this way, the service will automatically be created and the instructions below can be ignored.
+
+
+
+
+
+- Use the `Connection type` switch to indicate if the step is performed on a local server (`Local`) or on a remote host (`Remote`). If you specify a remote connection should be used for the step, the `Connection string` field will be enabled, and you must provide a libpq-style connection string.
+- Use the `Database` drop-down to select the database on which the job step will be performed.
+- Use the `Connection string` field to specify a libpq-style connection string to the remote server on which the step will be performed. For more information about writing a connection string, please see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/libpq.html#libpq-connect).
+- Use the `On error` drop-down to specify the behavior of pgAgent if it encounters an error while executing the step. Select from:
+ - `Fail` - Stop the job if you encounter an error while processing this step.
+ - `Success` - Mark the step as completing successfully, and continue.
+ - `Ignore` - Ignore the error, and continue.
+
+> - Use the `Comment` field to provide a comment about the step.
+
+
+
+Use the context-sensitive field on the step definition dialog's `Code` tab to provide the SQL code or batch script that will be executed during the step:
+
+> - If the step invokes SQL code, provide one or more SQL statements in the `SQL query` field.
+> - If the step performs a batch script, provide the script in the `Script` field. If you are running on a Windows server, standard batch file syntax must be used. When running on a Linux server, any shell script may be used, provided that a suitable interpreter is specified on the first line (e.g. `#!/bin/sh`).
+
+When you've provided all of the information required by the step, click the compose icon to close the step definition dialog. Click the add icon (+) to add each additional step, or select the `Schedules` tab to define the job schedule.
+
+
+
+Click the Add icon (+) to add a schedule for the job; then click the compose icon (located at the left side of the header) to open the schedule definition dialog:
+
+
+
+Use the fields on the schedule definition tab to specify the days and times at which the job will execute.
+
+> - Provide a name for the schedule in the `Name` field.
+> - Use the `Enabled` switch to indicate that pgAgent should use the schedule (`Yes`) or to disable the schedule (`No`).
+> - Use the calendar selector in the `Start` field to specify the starting date and time for the schedule.
+> - Use the calendar selector in the `End` field to specify the ending date and time for the schedule.
+> - Use the `Comment` field to provide a comment about the schedule.
+
+Select the `Repeat` tab to define the days on which the schedule will execute.
+
+
+
+Use the fields on the `Repeat` tab to specify the details about the schedule in a cron-style format. The job will execute on each date or time element selected on the `Repeat` tab.
+
+Click within a field to open a list of valid values for that field; click on a specific value to add that value to the list of selected values for the field. To clear the values from a field, click the X located at the right-side of the field.
+
+Use the fields within the `Days` box to specify the days on which the job will execute:
+
+> - Use the `Week Days` field to select the days on which the job will execute.
+> - Use the `Month Days` field to select the numeric days on which the job will execute. Specify the `Last Day` to indicate that the job should be performed on the last day of the month, irregardless of the date.
+> - Use the `Months` field to select the months in which the job will execute.
+
+Use the fields within the `Times` box to specify the times at which the job will execute:
+
+> - Use the `Hours` field to select the hour at which the job will execute.
+> - Use the `Minutes` field to select the minute at which the job will execute.
+
+Select the `Exceptions` tab to specify any days on which the schedule will `not` execute.
+
+
+
+Use the fields on the `Exceptions` tab to specify days on which you wish the job to not execute; for example, you may wish for jobs to not execute on national holidays.
+
+Click the Add icon (+) to add a row to the exception table, then:
+
+> - Click within the `Date` column to open a calendar selector, and select a date on which the job will not execute. Specify `
+
+Note
+
+
+
+The fields `Connection type`, `Database` and `Connection string` are only applicable when `SQL` is selected because `Batch` cannot be run on remote servers.
+
+
+
+using\_pgagent pgagent\_install pgagent\_jobs pgagent-steps pgagent-schedules
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/01_licence.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/01_licence.mdx
new file mode 100644
index 00000000000..76b93db72f1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/01_licence.mdx
@@ -0,0 +1,8 @@
+---
+title: "Licence"
+---
+
+
+
+
+pgAdmin is released under the [PostgreSQL Licence](http://www.postgresql.org/about/licence), which is a liberal Open Source licence similar to BSD or MIT, and approved by the Open Source Initiative. The copyright for the project source code, website and documentation is attributed to the [pgAdmin Development Team](https://www.pgadmin.org/development/team.php).
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/02_kerberos.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/02_kerberos.mdx
new file mode 100644
index 00000000000..82bd81cc64c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/02_kerberos.mdx
@@ -0,0 +1,22 @@
+---
+title: "The MIT Kerberos Licence"
+---
+
+
+
+
+PostgreSQL Enterprise Manager uses PostgreSQL's libpq library which may be linked with MIT Kerberos Libraries on some distributions. The MIT Kerberos licence is included below:
+
+## Kerberos Copyright
+
+This software is being provided to you, the LICENSEE, by the Massachusetts Institute of Technology (M.I.T.) under the following license. By obtaining, using and/or copying this software, you agree that you have read, understood, and will comply with these terms and conditions:
+
+Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee or royalty is hereby granted, provided that you agree to comply with the following copyright notice and statements, including the disclaimer, and that the same appear on ALL copies of the software and documentation, including modifications that you make for internal use or for distribution:
+
+Copyright 1992-2004 by the Massachusetts Institute of Technology. All rights reserved.
+
+THIS SOFTWARE IS PROVIDED "AS IS", AND M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. By way of example, but not limitation, M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+The name of the Massachusetts Institute of Technology or M.I.T. may NOT be used in advertising or publicity pertaining to distribution of the software. Title to copyright in this software and any associated documentation shall at all times remain with M.I.T., and USER agrees to preserve same.
+
+Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos, Moira, OLC, X Window System, and Zephyr are trademarks of the Massachusetts Institute of Technology (MIT). No commercial use of these trademarks may be made without prior written permission of MIT.
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/03_openssl.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/03_openssl.mdx
new file mode 100644
index 00000000000..87680f07fff
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/11_appendices/03_openssl.mdx
@@ -0,0 +1,23 @@
+---
+title: "The OpenSSL Licence"
+---
+
+
+
+
+Postgres Enterprise Manager uses code from the OpenSSL project to provide support for SSL encrypted connections. The OpenSSL licence is included below:
+
+**Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.**
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+- All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (
+
+licence kerberos openssl snmp++ jquery\_table\_sort
+
+
+
+**Additional Licences**
+
+| Component Name | Licence Name | Licence Url |
+|-----------------------------------|------------------------|-------------------------------------------------------------------------------|
+| wxWidgets | wxWidgets Licence |
+
+pem\_release\_notes\_8\_0\_1 pem\_release\_notes\_8\_0 pem\_release\_notes\_7\_16 pem\_release\_notes\_7\_15 pem\_release\_notes\_7\_14 pem\_release\_notes\_7\_13 pem\_release\_notes\_7\_12 pem\_release\_notes\_7\_11 pem\_release\_notes\_7\_10 pem\_release\_notes\_7\_9 pem\_release\_notes\_7\_8 pem\_release\_notes\_7\_7\_1 pem\_release\_notes\_7\_7 pem\_release\_notes\_7\_6 pem\_release\_notes\_7\_5
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_advanced.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_advanced.png
new file mode 100644
index 00000000000..63fc437a2e8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_advanced.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09e0de686454c757ceb690daf99ff3467e769e5ac9b4f306068ab648abf3625e
+size 102068
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_general.png
new file mode 100644
index 00000000000..6e9c24b34a9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1768bd7af02645e43b8b205d3fa8f5b18d63e47c6bb602a8ae78c5a05ee026f6
+size 132531
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_notifications.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_notifications.png
new file mode 100644
index 00000000000..427e940e340
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_restore_notifications.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac397d41556e18c2a42d6b8e13c2145b157bd937622251c36a44e4ca6e882bc3
+size 104710
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_general.png
new file mode 100644
index 00000000000..3e365e2dfbc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84ebff3dc9a9d0c04adf5786447bea03ac956ae7ed27df3c03bdc73f8f9a5dfe
+size 122504
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_general.png
new file mode 100755
index 00000000000..824eb47366d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a97fc45fbc1d0e934ff882e6ff4e0a6526c06cfb141f4e207e8458ba825be13
+size 51876
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_notifications.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_notifications.png
new file mode 100755
index 00000000000..e9db671e6ee
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_notifications.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db1f4ee4695c99775fc26a6780070c3febd749237ec6c1c3f7b65c2bfb384046
+size 75689
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_repeat.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_repeat.png
new file mode 100755
index 00000000000..12677903e5c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_backup_scheduler_schedule_repeat.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8d6bc00c6f5cf792c64291c6742a1872f7f752d46b1169cfa8ebd4cab576e46
+size 93116
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_general.png
new file mode 100644
index 00000000000..ef21ba09eaa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04ea1348462015b830cb0b9657bddd23f64dc0b4347665e2226444764360240e
+size 79043
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_repeat.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_repeat.png
new file mode 100644
index 00000000000..a5a5779405e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/BART_obsolete_backup_scheduler_repeat.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f468a59bba0d4f6049bb229289c36ca6462d3dc67c42ce308f9ec22a68d8d99a
+size 174869
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_audit_config_probe.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_audit_config_probe.png
new file mode 100755
index 00000000000..c00e720ab19
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_audit_config_probe.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9f69d80ac0f2de4e7aeefb0a5b631fcb29de82b9799728b8ca3a6bd3d3102b5
+size 183148
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_logo.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_logo.png
new file mode 100644
index 00000000000..9fb5e3972a4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/EDB_logo.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:908368bfc5ecd7deb52f203fe0d43b410f1ea2dfabc18115a316663c37d361e9
+size 12379
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/EPAS_instance.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/EPAS_instance.png
new file mode 100755
index 00000000000..7a944e87f1e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/EPAS_instance.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afe9535bd215c758e98f8db28e10d923bb692af114304fd642e75518e99c501b
+size 76590
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/add_restore_point.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/add_restore_point.png
new file mode 100644
index 00000000000..6205e9f221e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/add_restore_point.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3990082699928d137949af2b15c92236e9b932972088f9178457a76fa221c64
+size 28694
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/aggregate_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/aggregate_icon.png
new file mode 100644
index 00000000000..c280ccc4a0a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/aggregate_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e2da69747a89a7b66e482dc041e2d1e8f66bb7ea43c56ff47f40a77fc344cf0
+size 911
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_copy.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_copy.png
new file mode 100755
index 00000000000..02f990ef970
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_copy.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72b715546e266575e40f4c4b85fdf883f3f4126345a48bdca981a2a93cc22d36
+size 62210
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_details.png
new file mode 100755
index 00000000000..3ea7185b918
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9f6c39d786a771ea2bec07425687f3ca9fb0321b8058d5671fa8a6bc247f1d9
+size 138508
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_errors_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_errors_table.png
new file mode 100644
index 00000000000..b487b8024ba
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_errors_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c5b6366706eb2749ae0d3ff83b150e9c373c956e73021f14eed64977e2474df
+size 61278
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_templates_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_templates_tab.png
new file mode 100755
index 00000000000..bf9ec06e649
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alert_templates_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad2e9725566f5b290c2a9aafa1492c562413d10ed263e17afcb55607f966bfef
+size 147702
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_new_alert.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_new_alert.png
new file mode 100755
index 00000000000..399c83da002
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_new_alert.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4ca4e58a625c657798d574dd326cc166d272779596bad2de127edf07f4c7a59
+size 39073
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification.png
new file mode 100644
index 00000000000..d0115c79e93
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7093888c37903fd46dd596999b74bead05e2ba83d8a5f497c1e05750d7aa06f7
+size 101825
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_nagios.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_nagios.png
new file mode 100644
index 00000000000..4e4737dd4aa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_nagios.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f50e3895df205b1ce9a05a1f53e4c560a3d7dafda048f9a72edb8c24aad1b98
+size 53594
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_snmp.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_snmp.png
new file mode 100644
index 00000000000..182f459e64f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_snmp.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04968aa8970237ee5e04949a7e063e2a6b5bff7c7dff3b3efca9b4d080fd500c
+size 65321
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_webhook.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_webhook.png
new file mode 100644
index 00000000000..215936c2894
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_notification_webhook.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55a44906d59370fbabe88841acae56c1da04858663dec8445997dac4bc08cc40
+size 84157
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_script_execution.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_script_execution.png
new file mode 100644
index 00000000000..5950c88b596
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_define_script_execution.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ade89becf4c5fdf99610e402db946ad1ca7ce1a21a1c01670c5181f1854620dd
+size 286168
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_general.png
new file mode 100644
index 00000000000..6eefed4b05d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f03f6050c150ab45452ed987779e4e9179937fdb898a1c237b730705d09f9cc5
+size 167578
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_notification.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_notification.png
new file mode 100644
index 00000000000..2376dc144e5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_notification.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f1d578eecb890800dea2ffa76edbb66253a82a4ed3fd70d9b0cf0357b071a49
+size 121642
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_script_execution.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_script_execution.png
new file mode 100644
index 00000000000..75c69086f9c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_example_script_execution.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02f94546137805982dba12e849f50075a11062f11776004cdbb4514f38d133e6
+size 378891
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts.png
new file mode 100644
index 00000000000..8571dbe614d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f65c79ea86b8355493a226ef6ae144ab1ced63ece1a1f12965e829ad5bd83b6
+size 227680
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_delete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_delete.png
new file mode 100755
index 00000000000..4856e50b33b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_delete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bf906db4056da1dc8006a99e97e875df05c7e9ce79eefa8993decbfeb768482
+size 481144
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_table.png
new file mode 100755
index 00000000000..50ce83cdada
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerting_manage_alerts_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbe58ac7377d6d69b3a0951f852ab010c9abdb1475de230403f6a56a85ba2d47
+size 478572
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_chart.png
new file mode 100644
index 00000000000..02f2dca8755
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7709108ecc159203a6b4cee10dfd2f5ad65aa0bb29a087e1c020756c100223b
+size 44154
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_table.png
new file mode 100644
index 00000000000..a96263dfd5c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_customize_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc8cb0ad4a849fc3875d2542ab0cf80e999d09446af43d6c546a38bd316a04dc
+size 69753
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_dashboard.png
new file mode 100755
index 00000000000..fcf8526e5bf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2a7e55c4bf5a5731dbc9cef45a5c0a77f4f0d2ef45850e025ba0e7b6756b13b
+size 237724
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_status_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_status_table.png
new file mode 100755
index 00000000000..1af606eeb34
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/alerts_status_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9891bd30db80258b32d9cc59f19dee91375841a8fdd8f88178271c72b0976335
+size 287601
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/anti_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/anti_join_icon.png
new file mode 100644
index 00000000000..c343ec001b6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/anti_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8ca093e6ebe4cc0f01599bba78c19fc7d04035a20d020377a1b479446219104
+size 1153
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/append_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/append_icon.png
new file mode 100644
index 00000000000..c7dded03df4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/append_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1188f7553d5b30b6a247f32595f929acc508f398bf7004acc4647dc0a80cbb2e
+size 1180
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_connection.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_connection.png
new file mode 100644
index 00000000000..037e2d10a66
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_connection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b8e52f64f6cd50e9d90b5fa115e81b904647912d8d1c6f1e147bf109f96762c
+size 88978
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_general.png
new file mode 100644
index 00000000000..4a6118e4158
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ark_connect_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4655a29a720e56a4f1512a4f4f726a65560fc18748d1a0ecaf6406e07f22b6b3
+size 81148
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_dashboard.png
new file mode 100755
index 00000000000..592902bcdae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d8a61355c9b4556b0a0ead932fc75fe7e0791e4a4a5840b870176491912b8a1
+size 406992
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_filter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_filter.png
new file mode 100755
index 00000000000..103ece63fc3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_log_analysis_filter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9e2654143a902c2e50308d62ca90eb0a226e05479e57b4646aa2e0e4f592c9b
+size 99029
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config1.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config1.png
new file mode 100755
index 00000000000..5cbb064dbea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config1.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3da3b0c6635ba7ff1a0e255f3954af51e2458c5ab96be44986b9101ee4a8f0f0
+size 111374
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config2.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config2.png
new file mode 100755
index 00000000000..b9aa4008d6e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_config2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d00b5e2313f3a60a07bb31f3a0229939b9a58d91269cbd36262b69a8936655da
+size 150100
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_finish.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_finish.png
new file mode 100755
index 00000000000..c64bdce55d2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_finish.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b3e018c474be488d05645b0548b8d60579d03dd0e22af978602c2dde68ac5e3
+size 70026
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_intro.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_intro.png
new file mode 100755
index 00000000000..78482fe5300
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_intro.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6e39e2a6dd4b82626d86cf319db40b50ba007a99048841cf9c8766bc77e9127
+size 64701
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_servers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_servers.png
new file mode 100755
index 00000000000..eaf21a1e9a6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/audit_manager_servers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:528049b00aad665a521b3734d2d4d4beea1f7574eff706ad1c5d81bfbc627721
+size 67768
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery.png
new file mode 100755
index 00000000000..cc2dc86907b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4989aad4f13f67290bc2e60a6ec429e873257e1fda537bd1dc0269b420b738e7
+size 77699
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery_example.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery_example.png
new file mode 100644
index 00000000000..f250cbc12e4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/auto_discovery_example.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:742c2236d34e4f37265713d9681e52d53d78305baafc00cd2d4f2f951b4d9e7e
+size 82828
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_disable.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_disable.png
new file mode 100644
index 00000000000..687a7a8c7f6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_disable.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edb492f891ce6dd3d144d4adf3ef9b32667bea3fd19c4a848b474a7bc808b3a4
+size 47022
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_do_not_save.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_do_not_save.png
new file mode 100644
index 00000000000..e9d9ba60e7f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_do_not_save.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:227ccafec5b051e2f192ac6897b78a73809243423ed89c3d2b83689f3334ff64
+size 71323
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_general.png
new file mode 100644
index 00000000000..6bdf8997af7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eca4d29a4dcd2da158b3076fd0fe2be5b28cb51546b2b15604179851b1c8dab3
+size 85124
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_general.png
new file mode 100644
index 00000000000..70a3cde4b96
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9d18874f4b698f46d85a3d4718f8160de47b3ac1d1ddc87790bb6a9c105a8ac
+size 67237
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_messages.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_messages.png
new file mode 100644
index 00000000000..0165fd9948d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_messages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af22a288f692f20d01688798976368b4383968ff0aa33a9b344bdd4519602099
+size 78793
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_process_watcher.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_process_watcher.png
new file mode 100644
index 00000000000..15c0c1af388
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_globals_process_watcher.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1823960055564744d43042aa9f2234508b0c264a7287ff24c44e7c1a6e91ac5d
+size 239060
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_messages.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_messages.png
new file mode 100644
index 00000000000..2128d04566e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_messages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:078238641e4743a0fbbcdf41d95b0f25ac1b3e00d4aecff16203d8edba524709
+size 83780
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_miscellaneous.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_miscellaneous.png
new file mode 100644
index 00000000000..2091cd1bef0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_miscellaneous.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:989474fa155f267dde776d99c6507927f930b4fc2d1f1b2e39f17e743080ce05
+size 74549
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_objects.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_objects.png
new file mode 100644
index 00000000000..1dc89988ac6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_objects.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a6df319a7614b2e2523f4919e9ac49107bd798578afff62872b765e6b1bafbb
+size 62482
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_process_watcher.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_process_watcher.png
new file mode 100644
index 00000000000..79ace86f49e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_process_watcher.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdd6c7935392bfcb52e9536b8e667362ffa249c60292a087df1361aaedb330e0
+size 268464
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_queries.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_queries.png
new file mode 100644
index 00000000000..a7827e59a8f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_queries.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c49c086530c334cb95f77d26053050427c5ae4a1b48002d0a8952e289d0813c
+size 89585
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_sections.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_sections.png
new file mode 100644
index 00000000000..4d8adfdb231
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_sections.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61f7abfefca60b3f878428f4876152c2ddeaaae5fe9bb8f892ee0299264273a3
+size 53367
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_disable.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_disable.png
new file mode 100644
index 00000000000..1a8553c2931
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_disable.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50b8b053256296b062e23d3ae2a1ebba0570e91352a0547f3267a194b319df30
+size 46074
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_do_not_save.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_do_not_save.png
new file mode 100644
index 00000000000..22c1346d7ca
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_do_not_save.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2ed1b4c37c339f4419b1590ec0aa6c0d538fba93749eca3314464a1013eddd6
+size 65630
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_general.png
new file mode 100644
index 00000000000..d1f6a94cf86
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b428ce7e4a441b6e3ee4fafd01d0de938f274c90f5d70bbd5bbd0e40dfbb30e
+size 70874
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_messages.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_messages.png
new file mode 100644
index 00000000000..e5e90cac31b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_messages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e41b5678213114b1ea3d82a62f5e6b460e623f61f5049b130e81fd2c22b699a
+size 61716
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_miscellaneous.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_miscellaneous.png
new file mode 100644
index 00000000000..306dc1bed29
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_miscellaneous.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:934a84afa3cd3e18e13020ad083398bd7ab0d28417e47cfb5a20093ece028a11
+size 77313
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_objects.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_objects.png
new file mode 100644
index 00000000000..eb603accaa8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_objects.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cee9e4dc5064aeb961661c9d739d634c91dcec12dc319bbecc14d2e30adbdf36
+size 48692
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_process_watcher.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_process_watcher.png
new file mode 100644
index 00000000000..e1e20096ba2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_process_watcher.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73b83efa70c10c825626fd69e989ad988609c12bc97dbf7f183c3f9be88fe8df
+size 246348
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_queries.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_queries.png
new file mode 100644
index 00000000000..4eec116ef10
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/backup_server_queries.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db046d7bf99ece5f017cffaf3a89432f54678d9971e974eb34ea9b863d81f983
+size 65552
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dashboard.png
new file mode 100644
index 00000000000..d1a95fa80fc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97d6c4a4fe69e915c49b426a6f9333229928d8d5d01e8609b297060ec7e805f5
+size 182631
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_general.png
new file mode 100644
index 00000000000..1e450e93ef5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76bd8e14772540ea75f4a658aaeefe108aaea88ef8564f358fe3b9b1de6d20bf
+size 125411
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_notifications.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_notifications.png
new file mode 100644
index 00000000000..6aceb1f5003
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/bart_backup_dialog_notifications.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b553224d723e9fe8716ca52f206bd571fb25b632f8e97387420613180fb2ebe6
+size 104443
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_heap_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_heap_icon.png
new file mode 100644
index 00000000000..00e943bb249
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_heap_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:387b0cad99147667e4f44db6c278095ba20d33b8ae7bbeb75e966882c7c45f4b
+size 1061
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_index_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_index_icon.png
new file mode 100644
index 00000000000..e0256aca966
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/bitmap_index_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7053b065a0871ae68c97b54fbf1d656918a5a644375add37e865107af63565b2
+size 1147
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_add_metric.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_add_metric.png
new file mode 100644
index 00000000000..42212ec4387
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_add_metric.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a2d903f9875f7d3e63b0cd0d65d06fe491810a1c1f41b442ac7a2f4304b84c4
+size 146631
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_metrics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_metrics.png
new file mode 100755
index 00000000000..2bfa7b92288
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_metrics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:594b431486b1371b36ef1af84ffe6bd19583f60f7fd679e95af3c00aafa14a93
+size 142126
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_opens.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_opens.png
new file mode 100755
index 00000000000..d97fd83b80a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_opens.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbce95abf648ed0a7703c5c3d88ce31a32668536d92e01ab69fefb4da45558c7
+size 74119
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_options.png
new file mode 100755
index 00000000000..e9a9c7c44fa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e22377f0f093e217f7a889522aea7927d4c093d8378ec4394d94797cae006102
+size 121163
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_report.png
new file mode 100755
index 00000000000..db2abeec019
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/capacity_manager_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da4185d38714b93971f060634fbafbf0193c729fbb1011812fc3cd60f3e093e8
+size 107642
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_definition.png
new file mode 100644
index 00000000000..69f7eaf0863
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c46c11ace461959473bb3fa4a1f4cfb972db566b3d0f1dac5848294b4a23a76
+size 75457
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_general.png
new file mode 100644
index 00000000000..c8bfa2337fe
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0421c4ebb90354c5c2edae030a4b29a212651b2bfc4bedc941891e79adcc0661
+size 56602
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_sql.png
new file mode 100644
index 00000000000..7d3a90eb314
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/cast_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16795e87a7aef8163fb81887ecf9e45e9402aa487c6001d2e303106ab9969785
+size 60068
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_error_hba.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_error_hba.png
new file mode 100644
index 00000000000..6380af390f5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_error_hba.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9976a1f5a0770a66349db8ed0df290e9f94beced6676a16785db78fd683194e9
+size 57323
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_not_running.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_not_running.png
new file mode 100644
index 00000000000..c8523e7cd86
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_not_running.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99adaad3dd3f78ac2dd4020dbf38c3ad73a18ee8c3ca10284ef91672f2ee5d13
+size 70050
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_password_failed.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_password_failed.png
new file mode 100644
index 00000000000..320e6539986
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_password_failed.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d19a18cfaf46e5ee5af8d5867f390a7afa333a0fdbe008f03c2bc5c9601eeb9
+size 49903
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_timeout.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_timeout.png
new file mode 100644
index 00000000000..066d9c03c9c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/ce_timeout.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30598abb47ebdd77aea2e5d61c33d59171ce1472122c2856908c79e8b15b596f
+size 21743
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/chart_icons.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/chart_icons.png
new file mode 100755
index 00000000000..33c91201d11
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/chart_icons.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14e5a72573d47374a7d0bb2cbf89c3967cc7204d259687aa10873eba4c7cc380
+size 27673
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/check_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_definition.png
new file mode 100644
index 00000000000..4af6bed5ac1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55012321124069e430b78bf44d00f45416cd554d53d4d347984128b99e3a868f
+size 58807
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/check_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_general.png
new file mode 100644
index 00000000000..19e6d6f2cab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2afbe27065e3482039a7286c561bd0a59b56633f9487c3baa9633102b9a31b11
+size 55332
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/check_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_sql.png
new file mode 100644
index 00000000000..caf03b040c3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/check_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1013bb0513daf49157485d02759596cec4ae7c305ab66e95ececb41abff1712b
+size 66243
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_definition.png
new file mode 100644
index 00000000000..6d21a2dffd8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:056b4204d20975170f5b3b9345db9a374e6831a2b49c5c8c03ffedd3a5c5002b
+size 70523
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_general.png
new file mode 100644
index 00000000000..b357c0c51a7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cb0a89bbabd7d4e7a17d091cc82ec55e514486d8e5fdb7265369d279fca3436
+size 71530
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_sql.png
new file mode 100644
index 00000000000..0d5d45160b2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/collation_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87238e3237c727fbce4f61d405821f0858ea07f53297f67a17d999b7f9f7d3ea
+size 75689
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_generated.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_generated.png
new file mode 100644
index 00000000000..ff34c581414
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_generated.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:537021ce5e8f08d2f12a7dbbf04ce70059735ec6ae84d8708d493fd2fa2bdddb
+size 71911
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_identity.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_identity.png
new file mode 100644
index 00000000000..ab6d1424bd5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraint_identity.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a51f82aec2344a24e6033f5d2572a89fa299b886016037c1472fbc566ec8b9b6
+size 99691
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraints.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraints.png
new file mode 100644
index 00000000000..b9f2d7c8e56
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_constraints.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24320613ee3df8a302aa61d7e9e9235d51ac3c9e73e8acb960c9dd847b2aa412
+size 67376
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_definition.png
new file mode 100644
index 00000000000..77d40f86bcc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:755a91033e65da2ad6509a82fcbf2291b626be214bda073e688c94f811b830f2
+size 74492
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_general.png
new file mode 100644
index 00000000000..e5e765284c8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:544b46bd8cf5e65c62e30d84a5b84e2f1a14ad9c003bab06d3d9e547c140e12f
+size 57330
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_security.png
new file mode 100644
index 00000000000..303b8001c50
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8ab191ad9661ca1bebe9334a164583cfc866648b04be874440965f7bd5bb7ae
+size 60315
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_sql.png
new file mode 100644
index 00000000000..1125af6747d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81c99e189c0991750ea2a60e2361ce0a6d7048b7efe1a7dff58fe775312e5adf
+size 65353
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/column_variables.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_variables.png
new file mode 100644
index 00000000000..48e3bb8a5cb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/column_variables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c276c732668ee35906c04a4e2a79d792663d8dec962d85a6757792d2d1a276dd
+size 57891
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_code.png
new file mode 100644
index 00000000000..f6b4581cc2b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e26408a0e5d3985dac5f4feb83624f41ac886fd4b124424cc19a9cc1713184c
+size 150948
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_events.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_events.png
new file mode 100644
index 00000000000..e70156d25dd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_events.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39df32f386b380f740aa6d211415e8060aca7dd6994d5e490b7e754aee372748
+size 84224
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general.png
new file mode 100644
index 00000000000..cc00ddd31e2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00a52a091a24e96b8b61792172cae02ca527270a1b913ca2d28d53b18c894b7f
+size 58951
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general_enabled.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general_enabled.png
new file mode 100644
index 00000000000..cf43204cc6c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_general_enabled.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5be5c96a670b35c4536435ff55dbf48d47984ef7f98060fdfc20d6a5bcee8c1
+size 76063
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_sql.png
new file mode 100644
index 00000000000..fac4a419b16
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/compound_trigger_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce0d4455733b9fedf4c4feb86d5d6ba323d379f43fa467dab88d4b439a0a5424
+size 207230
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_pem_agent.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_pem_agent.png
new file mode 100644
index 00000000000..af7e74b6fab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_pem_agent.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7eca2e22b86e4ad7ddf1009d55c4bf68f240ea90d8fdd078560201657b320d35
+size 91988
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_to_server.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_to_server.png
new file mode 100644
index 00000000000..9b24353cff3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/connect_to_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d4f60643e8deffa05e82e011fc994f2742ba095a2e936683e3b64e53c99e3a0
+size 43370
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/copy_probe_config.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/copy_probe_config.png
new file mode 100755
index 00000000000..a8570a0558f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/copy_probe_config.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93ac0b1c8a3db7167d9bc8cdb075858ec41b7b4b9023e357b3cb40a8e84a8466
+size 57778
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/core_usage_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/core_usage_report.png
new file mode 100755
index 00000000000..acc12ee3b56
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/core_usage_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b83cb50cb298e6cc745cc236dd7818d0219a645fce3a93e783a523fbf3054a6
+size 149490
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_general.png
new file mode 100755
index 00000000000..2a9122b3986
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7a5b5df04f2a1df9fed9a23274bcb31a43651cfef0492c228502378717cf61e
+size 178118
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_misc.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_misc.png
new file mode 100644
index 00000000000..613da0b689c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_BART_server_misc.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62c0834dfa01f9e6044faf4110fd7a606010bceae823b98c75889ead0f12244f
+size 242898
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_group.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_group.png
new file mode 100644
index 00000000000..42666458a76
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_group.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92f501e0f357ecd77a0c7d188b576d3ba2a07bf5c043086dbc1b11ac05a2e586
+size 34480
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_general.png
new file mode 100755
index 00000000000..9b3ce7994f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a28bfdc43083ece9db704f4b3317ad0d32ccf9222294cf29f249dc4af1f88744
+size 64518
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_notifications.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_notifications.png
new file mode 100755
index 00000000000..6de1a23ce11
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_notifications.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49d20c62b300962f59f045c7f9a67ba194bf4fceed7ffb290a10992eb0bacfce
+size 128144
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules.png
new file mode 100755
index 00000000000..9434f25dbec
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63ae2d9984b7257240f33fcdabe74925431299435585f5ded9f164949e370217
+size 105504
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_exceptions.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_exceptions.png
new file mode 100755
index 00000000000..dce886b58cf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_exceptions.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67b37cff2232fd1a707c94e3487883c0a4ce22b17714991306d5e112a268654c
+size 86415
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_repeat.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_repeat.png
new file mode 100755
index 00000000000..dec595db656
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_schedules_repeat.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5707de3a9f9e52ba554695676754180e65bdae181fac2ecfe855e14304e27a4
+size 175073
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_sql.png
new file mode 100755
index 00000000000..cd7335f23d7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a23bb662c4e6c016cd5f06e0539f67c65c4304e7447343ffe35b42a297c5ead6
+size 176218
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps.png
new file mode 100755
index 00000000000..eb8094ba4e2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de151350e4bb9986df5a0f2e4172bf73f5734f6d568fde732f09a70005c38c6a
+size 104298
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition.png
new file mode 100755
index 00000000000..0a3174f852c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe8c23f0358e50d30b3165932a470fc36a445e63224c03c95701adff54dc2344
+size 63785
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition_code.png
new file mode 100755
index 00000000000..4bb5416573d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_pem_jobs_steps_definition_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a25e924980a9d083eb081b2acdff2a6ac24797c6b68072043b98fbe74923f83
+size 107921
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_advanced_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_advanced_tab.png
new file mode 100755
index 00000000000..c869a1a22b9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_advanced_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e908e538f382a75f8286143380d2fd92c106306d13d2091b965ee099d0efab1c
+size 68640
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_general.png
new file mode 100755
index 00000000000..ed2f3218b84
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d92143e6d790004f176588aa5d91c28ece7e3e3e725a09d34c2bc7a3333a81e
+size 156378
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_misc.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_misc.png
new file mode 100755
index 00000000000..fdd758a85ad
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_misc.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c22a97b6d4816e919f499c1aa13a486072c68267f4ac144edaebf7d71ea6a20c
+size 175592
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_tab.png
new file mode 100755
index 00000000000..0396dbd3a17
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_bart_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90525d9ddadb30f9f54fc8d3b8d6d51b70cd3fd9f40533ff62a63249e9c2a272
+size 138645
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_connection_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_connection_tab.png
new file mode 100755
index 00000000000..d94ebbbbc5e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_connection_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25614a83385a6662a120ec380e6b6fa60a1c4288f6e46c9cbdc77871cd2ed9c1
+size 79604
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_general_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_general_tab.png
new file mode 100755
index 00000000000..3b6d5e2d276
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_general_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ea53fd0c60fd431b26686e2c9b568c4f5c8bcfe06cc58a9c4b048abc4a102a1
+size 65020
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab.png
new file mode 100755
index 00000000000..c168edd1ac7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0974c0d2682633d05825870b7dc8d0c926188f9c854d1af34c965302077cf2da
+size 87737
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab_remote_monitoring.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab_remote_monitoring.png
new file mode 100644
index 00000000000..459acff6d37
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_pem_agent_tab_remote_monitoring.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4b84a3a9f1f5b1507524a6e98870928ae0b903a0f40269eb8d14503b12c2f5b
+size 90681
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssh_tunnel_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssh_tunnel_tab.png
new file mode 100755
index 00000000000..391bb2fbd85
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssh_tunnel_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:769bdd1f722d707e0653f91d070f8e5eff3c5f1076ab5812609abd97605d6922
+size 74353
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssl_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssl_tab.png
new file mode 100755
index 00000000000..a73d75ae3f2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/create_server_ssl_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ad6669cd8ace186746543fa8d03ca5faae13fdc8ee79b04a5bef6dccb507eb8
+size 70939
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/cte_scan_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/cte_scan_icon.png
new file mode 100644
index 00000000000..cc99e6a3378
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/cte_scan_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1817ed69e4abd2de738f74b40b0442c5de33066d81083b9a72017c3e5184e92
+size 1432
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_dashboard_add_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_dashboard_add_chart.png
new file mode 100644
index 00000000000..15a38c12292
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_dashboard_add_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:116e22f314e5f5fb434602ba1a100a821c42a151f53f98ce8cf911787332027e
+size 50828
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes.png
new file mode 100755
index 00000000000..f5d18df4b89
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77689175e8bcfc4e4be33125e626e4764902daa70111b33cfe247306e2845e28
+size 163504
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_alt_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_alt_code.png
new file mode 100755
index 00000000000..73f7db2fb7b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_alt_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee23af6cb9fad4e16899fa0098dc1b6d784ef0eef4e45df0bcac52c9c04162d2
+size 139555
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_code.png
new file mode 100755
index 00000000000..2f989cfd62b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b531f4050fc1783a8ac58f89563840c149cb2ac2ea6e97c20bb9f1eede4d7ae4
+size 105204
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_columns.png
new file mode 100755
index 00000000000..39c4fa34d92
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76e77f2fe8932da4d8487e506195930ce425ad83198b28105509c7f299706bf1
+size 324636
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_general.png
new file mode 100755
index 00000000000..7d2eb5a92b3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/custom_probes_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7b5f27856b6bee96e6588e0c03bb24fc98ef792193a241484941e53ff8e1430
+size 282182
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_alert_configure_dialogue.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_alert_configure_dialogue.png
new file mode 100644
index 00000000000..445eb5cf35c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_alert_configure_dialogue.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:387d5487dc9670cd0dc367bc9a6e8ab6d1c64c27cdd80cdc1d52276e5a0efe87
+size 111109
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_configuration.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_configuration.png
new file mode 100755
index 00000000000..bb13e93bd5c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/dashboard_configuration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e96e9523ee2cdd4b3642db54ccd365d2cf205d61590286dd795bfd87d13cda63
+size 92658
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_advanced.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_advanced.png
new file mode 100644
index 00000000000..b8ff9ec15fb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_advanced.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ced27b488ed108dcb3bce9d0e104aaf4c42f2a9c397dc22439264a21ca79ef71
+size 74920
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_dashboard.png
new file mode 100644
index 00000000000..359da3b0f13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75ca023fe49e6691347d63c6683c68d766e2935ae7ab542b0abc53b840cf829a
+size 526608
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_table.png
new file mode 100644
index 00000000000..020de85eb48
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_analysis_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcb12c6b891f0c0f5ec1b42e3a32d64d9bbd8a6969d119448968a09e250296e6
+size 108954
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_definition.png
new file mode 100644
index 00000000000..28c4996554e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07c6e1717d10566fe2c9e40d35c85d87641e81831bf15e5c487fea1a4a63a8e2
+size 94969
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_general.png
new file mode 100644
index 00000000000..ab6d108a2c7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa53f6ad607433411a7bef42f6c394ab7ac782bf8a291506bdfbd6481dc7bfed
+size 62648
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_io_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_io_analysis.png
new file mode 100644
index 00000000000..b89c0a254ec
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_io_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9dbc5b1757243e772d456f9edc17849e16ae0cdcc20aca390a5b9b3d9b7208e2
+size 146042
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_parameters.png
new file mode 100644
index 00000000000..a51ca188ab3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c2c1e57296dc97fd7006751c5eee3afab8e198891c55406761ce61bec16e111
+size 64573
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_security.png
new file mode 100644
index 00000000000..157870ddaf8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1363ef5a9090eece861d251745ec0fe4f1a1f314142745c6447e01ec94792ddf
+size 120006
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/database_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_sql.png
new file mode 100644
index 00000000000..cb448cfad6a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/database_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e48ea3ff0316bffec11151d4f9da7be757dec1ede69b7428baafed38ac6ddde9
+size 106611
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_error_message.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_error_message.png
new file mode 100644
index 00000000000..88e55285e3e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_error_message.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:759553d7bc8f597302b158b089f617de54535ce5723beb3eb84b0bc03e86faa7
+size 194174
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_ic_step_in.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_ic_step_in.png
new file mode 100644
index 00000000000..bdaced7555f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_ic_step_in.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b405308474888a646690e238abbf5d2d5706de2a72fbb36c167c4a41775b580
+size 166478
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_main.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_main.png
new file mode 100644
index 00000000000..e4d6bda02bd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_main.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6af26ca8a1ca495dd389ebb2e4b47ae99c1c0eb443362a3ec3a0bd91dc5dfee6
+size 185347
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_params.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_params.png
new file mode 100644
index 00000000000..8fa70f33bf1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_params.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74fd90b54e90931bb5c5203f4bc4f37c0b0c850f12846c66919106e6e90bda52
+size 76428
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_set_breakpoint.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_set_breakpoint.png
new file mode 100644
index 00000000000..5782d13526e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_set_breakpoint.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:482011d95cdfb25504038d05e6e37b4737e225523ee8cfff0a62786b7780bd11
+size 59790
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_stack.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_stack.png
new file mode 100644
index 00000000000..8bdbcaa1bb3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_stack.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fee078a1f3d4440b01d0fb702f7a49e3d8ccfb712702342f21cb9410a022919b
+size 34348
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_step_in.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_step_in.png
new file mode 100644
index 00000000000..7bd787ef7d4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_step_in.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1573d77056a1cdc8778ea5250726cf6a5d3a74c81233652add2dff2cf9b56e14
+size 166899
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_toolbar.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_toolbar.png
new file mode 100644
index 00000000000..b3b5df5f6a5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_toolbar.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7eaaf288253a8069cbb7696e5d162c2f730746285d13fb109d899889e0a20453
+size 16682
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_variables.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_variables.png
new file mode 100644
index 00000000000..bb1382af75d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/debug_variables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9931210674b0f45085db0bd26f76e1c4931182b931b6f9cfb9abe988486b808f
+size 30995
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/define_ops_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/define_ops_dashboard.png
new file mode 100755
index 00000000000..392bab388bf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/define_ops_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee3fb9174ca51507bae5d1863758f419ba5412e5c3e5787d22b9d0f3d2e897fe
+size 28713
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/delete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/delete.png
new file mode 100644
index 00000000000..4f415f0135e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/delete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c748b2a246ccd8b4a8b5ee70fc79970870c5867d5ef7b2da1e5b679c3be622f
+size 5414
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/delete_system_probe.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/delete_system_probe.png
new file mode 100755
index 00000000000..32a92a8f3f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/delete_system_probe.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80937868bae6b4c3e742542330e838470084ee7f034464fbefd760993b234866
+size 26955
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/disconnect_server.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/disconnect_server.png
new file mode 100644
index 00000000000..b3391d15b12
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/disconnect_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f671653cc301468e3e2f2f53190747c4410d6ff87ee57a046f63ae183f73f7a5
+size 26817
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_definition.png
new file mode 100644
index 00000000000..ec6a024b778
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3c19adc35a827dba80d40ec654f56deb0ed55638860e428769947202d063566
+size 62446
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_general.png
new file mode 100644
index 00000000000..067918a8733
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5092c59016944db6a0309eb9b6e168b92039859e067c3f2ed3aeb3c28bb45798
+size 56140
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_sql.png
new file mode 100644
index 00000000000..727649e1872
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraint_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8425f7e011ae7d2e183c33ced76a2a5b55c99a82b3aaee47167d44aaa02b19ff
+size 57706
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraints.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraints.png
new file mode 100644
index 00000000000..d187bc6ee6d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_constraints.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:297e07d34033a0e8814b78f357e3065ac70347bdaeee7a9aab541874e1e8a4e4
+size 49744
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_definition.png
new file mode 100644
index 00000000000..545a9c4bb69
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f480ee14a58b50f2cbd7192590246cbe51abc256862aaf42a65f0889778fb7b8
+size 90302
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_general.png
new file mode 100644
index 00000000000..3afe76e9e2c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0df8c5ebf7f9c8d928efa92464ba7f17b6b014286990c1f1c47d06ddcbe5f06e
+size 75071
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_security.png
new file mode 100644
index 00000000000..93fa5b6e9a2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9aeab0c64b6bb9158691f4eaae61bd705b1f1eac4a7adca09dacf71c746f2f6
+size 56768
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_sql.png
new file mode 100644
index 00000000000..43e1388bb01
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/domain_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa4b463c711d82144aa03a723d283008bdea2cf3cd99b8532c65cd2d99f92fc8
+size 84388
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/download.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/download.png
new file mode 100644
index 00000000000..149169b6ade
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/download.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f69c5d907dc2f0528c29e951b8fa4db7705d15f03a0def9117cf55136f13d36e
+size 5710
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/edb_logo.svg b/product_docs/docs/pem/8.0.1/pem_online_help/images/edb_logo.svg
new file mode 100644
index 00000000000..f24d1dfefee
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/edb_logo.svg
@@ -0,0 +1,19 @@
+
+
\ No newline at end of file
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/edit.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/edit.png
new file mode 100644
index 00000000000..9ea4216d1d1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/edit.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05e9f77f14e9d6e9ff4115925e9dd204895815da0d2d27d871586bcea14a3c5b
+size 5787
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid.png
new file mode 100644
index 00000000000..b501e4404b5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab37fd875604768a58fc064999c8985dbd13036ad710367413d0bcec57cec2cf
+size 247208
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_filter_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_filter_dialog.png
new file mode 100644
index 00000000000..d7609d18442
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_filter_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee51e5500fb4d9597b72bc0a2a1fbf46e94775e8b416def263592c5c325d42f5
+size 66059
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_toolbar.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_toolbar.png
new file mode 100644
index 00000000000..aee5e1fd3f1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/editgrid_toolbar.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41feb7600cc59ec4e5f140aa04e4a092ca97eb7621652a666ae633be98fc4af4
+size 31850
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_add.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_add.png
new file mode 100755
index 00000000000..28811642e7b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_add.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d25ac9f0118558c964261fa86a986ce41b7731bd489938d5d335aa0d61d16a6
+size 314004
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_delete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_delete.png
new file mode 100755
index 00000000000..c1fda6760ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_group_delete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e99159164501f6bf0432743e0bbf9ff708d727269f7f176711e432a6bdf4798
+size 40499
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/email_groups_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_groups_tab.png
new file mode 100755
index 00000000000..f5b04bab037
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/email_groups_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abc215b665ec954a3bcbb86adc57406e08168f92bb2f9b406875121e0653cd4e
+size 64717
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_definition.png
new file mode 100644
index 00000000000..503a1c5d36e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7c3a8c68ac843488f24951d82ad08d86c04a69459a8fa9d8f0cb8c20570149c
+size 79338
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_general.png
new file mode 100644
index 00000000000..9515bd629a9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8ac1366ac8ea2b5ada3667cb9353137fca490f18214b1f023c26861f288bb6e
+size 59931
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_security.png
new file mode 100644
index 00000000000..7b846bc27fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a42c42ab910b6a38874745339196ec135809816c0ff39096b32d3a1f2119e07
+size 53046
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_sql.png
new file mode 100644
index 00000000000..b888ea0198c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/event_trigger_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8245ae9279f2dd43b319fe9d9e47fb3a6773c6c5ac5eb10bc0a48277dc9ed84
+size 85586
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_columns.png
new file mode 100644
index 00000000000..62233679b7d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65af27b1997a4ddf5b2b7c46473246c315759c9af486877803ef80ed235c94fa
+size 95428
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_definition.png
new file mode 100644
index 00000000000..e480d6ed2c1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58dbdba0d2be23339c64232f341a9efb0dfbe155b212e7d4c2f9467dc5b479f9
+size 81903
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_general.png
new file mode 100644
index 00000000000..c65530e7d3e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:054c27917133c749c74a1434195e0975cc866d89fbb9efa6caf1bc4b687a5a4c
+size 54933
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_sql.png
new file mode 100644
index 00000000000..fddc93526a7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/exclusion_constraint_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:512411d2e9677baddfb740fb625ee55211649f15f9de909ad67a09950f28f780
+size 77029
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_definition.png
new file mode 100644
index 00000000000..0197b333806
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25047c5acfce59bfe4e217ede9ef0eded5a410758c8c1fd059bb81506fa8ead6
+size 50872
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_general.png
new file mode 100644
index 00000000000..ba0c030b773
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd9bd68788375020b4d0ad620f62903efbcc675f672026207e088c192d8008cd
+size 53356
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_sql.png
new file mode 100644
index 00000000000..288bcbd9f45
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/extension_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccbc212ad325be7a27c7fb025b936119775517a438ce3bedd2e38c87ebeb7e39
+size 61553
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/favicon32.ico b/product_docs/docs/pem/8.0.1/pem_online_help/images/favicon32.ico
new file mode 100644
index 00000000000..7be2392833c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/favicon32.ico
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:890b83da8580893248e6ac1b36033fea0969ddeb650bb37d3dd4bd5e6b716a63
+size 6465
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_cluster_status.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_cluster_status.png
new file mode 100644
index 00000000000..417de037027
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_cluster_status.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c34de7adf87adcbd5deadfbb95a3ea37cb194cb97d187bebd7c3bd8fd659c9af
+size 87299
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_job_result.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_job_result.png
new file mode 100755
index 00000000000..87e215d3e61
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_job_result.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7446efcdd9338967c9066bbab404eb106eb203f148e09b39161802ad773e065c
+size 21338
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_replace_primary.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_replace_primary.png
new file mode 100644
index 00000000000..040c2fe18df
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_replace_primary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8380c89c1a6d3c3810c305e8ea24c940ae0adb696518e97ca2e346710cea4d0
+size 29865
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_cluster.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_cluster.png
new file mode 100644
index 00000000000..476060142ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_cluster.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4dc7e7f5b986a2055a2d53a070129b71f896b4e93c316345b91ecfe0d11c77c
+size 41628
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_job_result.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_job_result.png
new file mode 100755
index 00000000000..92d31821ad2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fm_switchover_job_result.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a2abb77a0732a3134db2b3e83eb55d27a717cdab754f32f57c7b5143672f189
+size 48590
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/folder.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/folder.png
new file mode 100644
index 00000000000..21759ed5ecf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/folder.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbbad6821d767b4eaf41f0c9f02cc7dab44b209ee06fcf0fb5cc09aa20d2413e
+size 5803
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_definition.png
new file mode 100644
index 00000000000..c04ffc4ee41
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24fab6420304367f611f7747552f0bbd1676799b4e6470d748f3ce26da93aa84
+size 67878
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_general.png
new file mode 100644
index 00000000000..914b0dc5360
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:014966b15c2a438f3675cd88235789586f5613769ab681c04959dece805fdf81
+size 74433
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_options.png
new file mode 100644
index 00000000000..878ddb802f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f6fe51fb20c49519e51f5c20b59054068c6382a4cfef94530100ba94573e639
+size 57170
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_security.png
new file mode 100644
index 00000000000..f331a2605fc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86b88d6904db259571f8f3a3960ba03bb6e951d002f2fa2eedbef4876d6d353c
+size 67208
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_sql.png
new file mode 100644
index 00000000000..c5d729ace2c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_data_wrapper_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71c5785d8a195b5b17b314f15af1ab84048c29d97d37ff2a7b3e92da1551ed44
+size 126826
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_action.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_action.png
new file mode 100644
index 00000000000..249536b6074
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_action.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3138ac48c82eaea45cc0fe8df55ea7a40269f3c6a171fb8b01bfd17e3da08892
+size 57833
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_columns.png
new file mode 100644
index 00000000000..c03208ca9e4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1afc1b94c5161aaf788ec15397dde1c8b91b4515971469e655a9fccf2051d0e1
+size 87746
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_definition.png
new file mode 100644
index 00000000000..8bce0f2a3ca
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:663b43626e94c4625ac55623f0f2e0b214008c8235abecf21ca5546d4c61c1ae
+size 85902
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_general.png
new file mode 100644
index 00000000000..e9459c001aa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e25176b54f9e9877e709d53907d922c9af487160068861bb05a398c7ead8a16
+size 52664
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_sql.png
new file mode 100644
index 00000000000..0ff3b9e68f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_key_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c9e87e2da0ca31187495adfd468acb16963936d7f592a01bd408c4f1f373f25
+size 129363
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_definition.png
new file mode 100644
index 00000000000..5996c15d4b7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ca56c1710e6c407aa58dd72122ddd7b5fa4a005f274dd8e6f76d23db21cfb3e
+size 53760
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_general.png
new file mode 100644
index 00000000000..b471567c019
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddd9a4fde4605983a7f1b89fc0dd7ebfbc027facc857bab229a1659a7ed98abe
+size 65916
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_options.png
new file mode 100644
index 00000000000..9e05df949a8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c371c2bdfe47eed95927d9e51c41d5322dbf82d2a666ea8661a34015eb2856b9
+size 69365
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_security.png
new file mode 100644
index 00000000000..d168547ce68
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fcede538f303937699c32403fe6d1b4975a623f0da25d1af314de4b1e34375b
+size 55197
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_sql.png
new file mode 100644
index 00000000000..afcd6eabd06
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_server_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3766c1c83f5408a04d5716647573fdc6fc8cf18e44eefe0f60ceb099bf6cdd31
+size 90033
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_columns.png
new file mode 100644
index 00000000000..faa25acecae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a3cff8f9a99546b171ddaf2c21bca30ef3139a71050fc9284110b08ddd01a06
+size 66750
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_constraints.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_constraints.png
new file mode 100644
index 00000000000..ec69bd4f07e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_constraints.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6712e45a4636d8a81eb31902a278cf59c6083bb75d5db88c823253fc0aea04ac
+size 65670
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_definition.png
new file mode 100644
index 00000000000..a0217809e4c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72816825c9808086625daa1712168214ff514a00c16d84958943ad32fb70988e
+size 64726
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_general.png
new file mode 100644
index 00000000000..0bf9f48791e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d36120591909b5a2f73faa9f56ebf61660556f4de8de406f578a31fd1cc703f
+size 76614
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_options.png
new file mode 100644
index 00000000000..7ded40f3dc8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78050c76a2ad6c9287c12512b0c0f9435b442c112f74693677ac8c25a36edbb3
+size 60082
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_security.png
new file mode 100644
index 00000000000..7a66edd1526
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea0b0f5fa779bc03523a68300b97eb5a3cdd6c41708e30cdd2099f296030c4c2
+size 132248
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_sql.png
new file mode 100644
index 00000000000..8232207c42e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/foreign_table_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a13ca04816df54300c2180793f55ceb265c6eac6441ae0279c9a66b28f11d7b
+size 109136
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_definition.png
new file mode 100644
index 00000000000..28caf66e58e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ece991253aabafcc3ca1bbbc6ea1e1d4e55de1d1e5bcfd330b7fd87a0844f9f1
+size 55996
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_general.png
new file mode 100644
index 00000000000..d21a3ebb073
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ce1c58763f2f45084ac82fccf6b5f51e86c352297ae2178c0fabef7218a67ae
+size 72074
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_sql.png
new file mode 100644
index 00000000000..9d6b312f541
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2255a6d468939d3bef679792a259011615b858d7aa33efc828b6b45e44029268
+size 69497
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_tokens.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_tokens.png
new file mode 100644
index 00000000000..22854e9ee6e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_configuration_tokens.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10500be3d00f617d7cf422b34a9ec45d8d9210c5d75de38ad38dd650982014b1
+size 58913
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_definition.png
new file mode 100644
index 00000000000..7c72a85786c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9cea920ad4d74efc5d0711c144d3480119d9e581668a840c676c2bdd95c62323
+size 54387
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_general.png
new file mode 100644
index 00000000000..62033cedea3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da06ed3ee1af66259d53ce361dd94d289c8568561393dc81b3491e8d32944002
+size 69657
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_options.png
new file mode 100644
index 00000000000..5e894619d3f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91214cad0c6fdc712d05857f6871960b4471d908237f29a0075f354200511ac2
+size 63038
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_sql.png
new file mode 100644
index 00000000000..efe4b3dec0f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_dictionary_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6b735022ea7c5f497ce53f73f766fe5f0f208c8564f5b6d06dcb78dc74d7d3c
+size 77099
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_definition.png
new file mode 100644
index 00000000000..ce12f9f298b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e56cce864602cc2785b482675b2eb2d92e34a918fab536388793c28fdf82e11
+size 93677
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_general.png
new file mode 100644
index 00000000000..52833f14656
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c96f845b907a865daa4b638957cb73adffce95351d3f622d67967578452651d7
+size 61917
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_sql.png
new file mode 100644
index 00000000000..500b4037ce4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_parser_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7f4968fe8ed2361fcb057b10bb39247a9c557b0da56995bbd3baf62d3ac52b6
+size 89984
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_definition.png
new file mode 100644
index 00000000000..75fba5e2b4e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41eeca7af091733792925bc941b6565065c28c63fcfaf3fa64839977e3596b00
+size 62206
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_general.png
new file mode 100644
index 00000000000..eaa9fbbeac8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56668d50490d2900e2e4f0aa107ca77af178418f00b187837b3038d03b752a9d
+size 63871
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_sql.png
new file mode 100644
index 00000000000..3914a8c6f1b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/fts_template_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42884bc16f537005249f8eec882fa1eb37c38a4340c42ee559cebb7fbc1966b5
+size 67244
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_arguments.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_arguments.png
new file mode 100644
index 00000000000..6ef34c1770a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_arguments.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d2a24f397cdfa45c86e38b626ba7fce396deac46945c38461da07d624bf545d
+size 38851
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_code.png
new file mode 100644
index 00000000000..2fbd1f93bef
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2ea5ca1a89b67303e494f4f585eb3da827239e1efbad7084c6d088d2e512b26
+size 40242
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_definition.png
new file mode 100644
index 00000000000..613ad0a712d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eeaf9f19980b9a1d66ee5932837fde987d6a4626a1b3b8f5d74c2dea5a9857cd
+size 59697
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_general.png
new file mode 100644
index 00000000000..6f7cd82cd95
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff81da96b3b454647f0ac7cc29d029028fc2945838a09c96a1b54a9931e7d71e
+size 59378
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_options.png
new file mode 100644
index 00000000000..c0da1ac65d3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:002843d456f877f7568cde57ba316832d72523f8d2682b01ca54479181953ccb
+size 68995
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_parameters.png
new file mode 100644
index 00000000000..c70b86ce201
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dd321784180545c62e0ca62a4e1d0220d61b1c03f85bd65dce93f90284069be
+size 39715
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_security.png
new file mode 100644
index 00000000000..794ff3c670b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71a60d721a20a8538c2cb7221bcba88c744a96e9f9b56187f526c8f03cc59430
+size 55166
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/function_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_sql.png
new file mode 100644
index 00000000000..d9306fca0a0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/function_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:018c243109790ca456afee664fcac38a8cb580ccdf4bbbc2225a117c30ccab67
+size 88823
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer.png
new file mode 100644
index 00000000000..6df6f2a05fc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1eb22df649684292910ab3271d7639201337227dec2bbe0c5dd23673ef4806b
+size 716836
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer_property_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer_property_table.png
new file mode 100644
index 00000000000..232661bd6c8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/geometry_viewer_property_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a8ee77cae418570461802cf002cdc4f2228fad586b6a4208f6705c9deddbceb
+size 817464
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/global_overview.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/global_overview.png
new file mode 100755
index 00000000000..4468403ff1f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/global_overview.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c80e71d920e09633f0d90c64091c71ba0fb5d2232a58f2afeab0c6e237e2e83
+size 469645
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step1.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step1.png
new file mode 100644
index 00000000000..3cf5bef0c5a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step1.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cea66cedcef379df64ec43a48004a0a3e38e6a2ab21006244f4519fa0d6267f6
+size 142248
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step2.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step2.png
new file mode 100644
index 00000000000..e322e6d18d7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba23f8f02e608efbe07b2ffcc3e7a12bff114ef03f3fff810bdd6ddd0da6f62b
+size 69897
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step3.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step3.png
new file mode 100644
index 00000000000..764a5e02c51
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/grant_wizard_step3.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c6e088758c11c22c45a0610683e65f3b3318efcb48f32b0517f750d6f99eefc
+size 88450
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain.png
new file mode 100644
index 00000000000..c50ba6dbf14
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30f5d902a32c015d439eb4fc6d9f05bad74ff30ed47467b109e6d4ded7df8ba6
+size 133660
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain_details.png
new file mode 100644
index 00000000000..98e80aa183b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/graphical_explain_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:214771df9bf5b5e309792314bfc95b70125bcbad544265d2d36fe5b6c5f67439
+size 130013
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/gridview.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/gridview.png
new file mode 100644
index 00000000000..9e8446b83ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/gridview.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc73f3661421adbbe942627a4887d37efa0bf77242b1777ec8c778e27de19029
+size 5781
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/group_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/group_icon.png
new file mode 100644
index 00000000000..64910408e1d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/group_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e5f4c071abe3a7632c7749738f8aa094829d5feadba291b6f3ecbecfbeba1a4
+size 1261
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_anti_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_anti_join_icon.png
new file mode 100644
index 00000000000..c343ec001b6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_anti_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8ca093e6ebe4cc0f01599bba78c19fc7d04035a20d020377a1b479446219104
+size 1153
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_icon.png
new file mode 100644
index 00000000000..a7cb7ab6bfb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8df923ba3e6fe1860f75478f6c4a3578c8c35f340600a21d80282f9ab9387eea
+size 1030
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_semi_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_semi_join_icon.png
new file mode 100644
index 00000000000..a36f6fafec8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_semi_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14e746926af9a172ed5eea701d5a35beeeeae25bad3debede9f9d4726eabe854
+size 1137
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_set_operator_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_set_operator_icon.png
new file mode 100644
index 00000000000..8d2430283e6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_set_operator_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b55a6ea9e347b4d872f2317bcca030fa8451c88bab67220e7fb8df75d1ed210
+size 1152
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_all_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_all_icon.png
new file mode 100644
index 00000000000..75cc696f13a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_all_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f894a6753397d727abf12b000eeb5f881aef8c737935d3a2d08377557028bd2
+size 1166
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_icon.png
new file mode 100644
index 00000000000..75cc696f13a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_except_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f894a6753397d727abf12b000eeb5f881aef8c737935d3a2d08377557028bd2
+size 1166
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_int_all_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_int_all_icon.png
new file mode 100644
index 00000000000..beed1e55867
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hash_setop_int_all_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9dfda093c349f2319bce7c2025874a1d872f8e7d8e9707da3be4e3fd2a3936d9
+size 1152
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/home.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/home.png
new file mode 100644
index 00000000000..611f7886c9f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/home.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63d9418c62861df467371d9c513305dc7245e44e6166f4b0aad187efb6dd36e7
+size 6043
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/hot_table_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/hot_table_analysis.png
new file mode 100644
index 00000000000..061a5931ec2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/hot_table_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0e58c26b4912c6fb264ff5d3425d3bea8e14bb7e3d9cff77c0da8461c689605
+size 292843
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_columns.png
new file mode 100644
index 00000000000..dd5081e7ed1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a43c5ed503aca29ab2c6b2941fd4ab673b361aa86e866b089b1597116f502ae
+size 139811
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_complete.png
new file mode 100644
index 00000000000..40f93706b17
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94fe2bc9215060b5591f9ac21cdeaa781e8193a0101021f2389d5a5d27d7f5cc
+size 73819
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_miscellaneous.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_miscellaneous.png
new file mode 100644
index 00000000000..168ed746aa7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_miscellaneous.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:305555dd5b021e07b8cfc2987c9b161cb0f803d2e223bc456567da9c0fd244db
+size 155998
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_options.png
new file mode 100644
index 00000000000..da935b49f15
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8687cfea4758e49e6e5d276ac76ac018d1a26b5fd3246507506c3deb638b89d
+size 54340
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_pw.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_pw.png
new file mode 100644
index 00000000000..5eff2ecc8ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/import_export_pw.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e8329ecadcd2586abe0734ad52e08cae3ae9eb3bd1cad80ff45dc37bcd3178d
+size 70242
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/index_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_definition.png
new file mode 100644
index 00000000000..22ce6b470fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1e7ed1572375f6d18e3a8066c4482a86de8e9cc8987a1289dbebfd951f740f3
+size 116076
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/index_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_general.png
new file mode 100644
index 00000000000..33dd994d942
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdd7d090ce10cc658daea494e9efcd3fcd75dfd7d363229e5953998c3c497bba
+size 57586
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/index_scan_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_scan_icon.png
new file mode 100644
index 00000000000..6b8156251cf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_scan_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:306bb67c183531d1f3d455d16c816d6270f610063de18b32264f5f2140df92be
+size 1087
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/index_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_sql.png
new file mode 100644
index 00000000000..4a3aa092164
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/index_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:266058d24982a54d744ea44a6e75f498513cb015fec4b27af9a8d0dcd6c64f3f
+size 81273
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_plugin_windows_ready_to_install.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_plugin_windows_ready_to_install.png
new file mode 100755
index 00000000000..656e783c388
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_plugin_windows_ready_to_install.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d57017c74b601b951504928d180c9a6c74062cfd0299d1d52c8ac700f28bac8
+size 40353
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_finish.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_finish.png
new file mode 100755
index 00000000000..b1207a0025a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_finish.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3347c2404d3155bc8c0179161d0ca49769f3b666a39f5b54cece3cb386f91341
+size 66687
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_in_progress.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_in_progress.png
new file mode 100755
index 00000000000..99a56f86add
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_in_progress.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f64cdc66cde778f86230c3edf4d2783903d598c0bb88eabb86d99a9b1e14bf4
+size 117050
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_installation_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_installation_directory.png
new file mode 100755
index 00000000000..62b843da529
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0fe20fb8f8311ab8eb0c6dfcfb50c1c8f9b674e1279d170f217f30fd70b52924
+size 123103
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_license_agreement.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_license_agreement.png
new file mode 100755
index 00000000000..5704197ea86
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd1bb4cd23eb57e623cfa0b1477451016e1f96c4a2bb6f391c6ce8a1ba849bb4
+size 72819
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_welcome.png
new file mode 100755
index 00000000000..0966496ac98
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/installing_pem_sql_profiler_plugin_windows_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33953244b6415f6cd045edb279553bb24338550b3e09659bfb4084c70bb3e7b4
+size 162756
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis.png
new file mode 100644
index 00000000000..5380be1d968
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f2eab8e5287ec55eafe411ada3380862f9d8b6a862e488c2eddff91e366764e
+size 132683
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis_dashboard.png
new file mode 100644
index 00000000000..330dde80e41
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/io_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:718db63d1235570c500280658763bc728ee7a98ed26832ebc71e71397085d268
+size 725395
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_agent_level.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_agent_level.png
new file mode 100755
index 00000000000..01d61dccead
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_agent_level.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:baf36eef335b19037a3d085a28050d716986f8755b0d9848680cdc2dd915a7d0
+size 184619
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_job_level.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_job_level.png
new file mode 100755
index 00000000000..6de1a23ce11
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_job_level.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49d20c62b300962f59f045c7f9a67ba194bf4fceed7ffb290a10992eb0bacfce
+size 128144
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_server_level.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_server_level.png
new file mode 100755
index 00000000000..5622edcdb70
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/job_notifications_server_level.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64cff9ef14f5884bbc977663d0f2457cb5cf1648822610f6e424b544678f8706
+size 103671
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/join_Icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/join_Icon.png
new file mode 100644
index 00000000000..7fc5fd1c0eb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/join_Icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:576aca8c0ecb669df975c466a55f01c5cb874ca17c2e9c1ff15b587745ba89cd
+size 1059
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/language_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_definition.png
new file mode 100644
index 00000000000..dd94e9b1062
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50c4fbc37ecc9f79cbccd0583317dae4f7d57722728306a05d3e5e94cf4dc863
+size 70664
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/language_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_general.png
new file mode 100644
index 00000000000..5927c54c300
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8158758911a8bde2f015ac0bced3478f6c8e30fd171d648f61a3f49ccdc8fdd4
+size 59197
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/language_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_security.png
new file mode 100644
index 00000000000..ee82b3479ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13c3cef4623165cf6c667029780e1430ccf80254cc0cfdfe52121e24f5f10551
+size 84096
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/language_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_sql.png
new file mode 100644
index 00000000000..9be23062343
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/language_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eeffdf6ea0553a1f0303e7e82a26ff9a29173d0154702f2b32c7610b42af36a6
+size 78853
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lgdownload.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgdownload.png
new file mode 100755
index 00000000000..c30aba4bedb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgdownload.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e809ff6930ac40b06412186ed9b7bce0ea0cdf234b9cdf0af461f88c6e573130
+size 4356
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lgfullscreen.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgfullscreen.png
new file mode 100755
index 00000000000..25f3cc9e17b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgfullscreen.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:734eeb5b093de9d187a770709000502817f8b01242562029b2d07179c664004d
+size 4206
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lginformation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lginformation.png
new file mode 100755
index 00000000000..4da2b27e4c7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lginformation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc0b43993ecbb58882cb0521c200195337c85c2ed70e4189d9b99f35df3130b8
+size 4205
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lgpersonalize.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgpersonalize.png
new file mode 100755
index 00000000000..29bf34a76d0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgpersonalize.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:956e73a53671184d30b80ddf931415ced488c4be1ce77f4b1a6c851f7187b12b
+size 1685
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lgrefresh.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgrefresh.png
new file mode 100755
index 00000000000..920a965716d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lgrefresh.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cf7efaa0fef20aa391c0d6861ccef5035fa33e204b316e93335db67f3965d3a
+size 4482
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/limit_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/limit_icon.png
new file mode 100644
index 00000000000..2f21c3d53d0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/limit_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:073408ab066557685ab192211a790b569fa958541fe66baeee492dcf0c115a02
+size 1089
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_import_rotation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_import_rotation.png
new file mode 100755
index 00000000000..3e9f2771196
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_import_rotation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21538111e09ac00fe435bd664fefd75678b1070d29c60be72a601fa61652de68
+size 132839
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_scheduling.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_scheduling.png
new file mode 100755
index 00000000000..81622de4e0e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_scheduling.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a92d07e57dfaef6dc298fb176f1d46c737d1230a02dcfce77689c9f4f6ce637
+size 90078
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_server_select.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_server_select.png
new file mode 100755
index 00000000000..b16ed67be72
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_server_select.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20661643572e77b4ffb33553fe48e69f35974b4824c72025602efd034ea60ab4
+size 92310
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_welcome.png
new file mode 100755
index 00000000000..86e4b167235
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a18bc7df357d9783956656b747fc82db7598c97c366b7c13a73179db639e501f
+size 79972
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_what_to_log.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_what_to_log.png
new file mode 100755
index 00000000000..f17127f2dcf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_what_to_log.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ce447edcd8fab9d33d417b9032b3076acd635c801bd747daa78f336e5603a25
+size 143211
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_when_to_log.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_when_to_log.png
new file mode 100755
index 00000000000..825b7d6ae82
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_when_to_log.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15005d710c848af8d4322e94720863ba271c8714931d8297857e327c90626701
+size 170908
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_where_to_log.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_where_to_log.png
new file mode 100755
index 00000000000..b078bd6e3de
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/lm_where_to_log.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65db4b833342cfd63442cb03383353d2d4ac3100266076a8731ca4f1c85f90da
+size 148810
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/logo_base.svg b/product_docs/docs/pem/8.0.1/pem_online_help/images/logo_base.svg
new file mode 100644
index 00000000000..67624dbbaed
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/logo_base.svg
@@ -0,0 +1,18 @@
+
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/main_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/main_sql.png
new file mode 100644
index 00000000000..1b39c5c473d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/main_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1e2f34f2e3d11ed415a4c7948260febfc294f4854429ef906e5364e5e377a51
+size 53231
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance.png
new file mode 100644
index 00000000000..b0e572d347f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4df96efc16476e73efa93154bf4a3ae23ff06b9bbb9c8b3f46193389851b59da
+size 55461
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_complete.png
new file mode 100644
index 00000000000..1e9247acef2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b18cd1d0e6630a8943c027e0f28581d7999f6ae3952b418ebbd69cce90c2d3d3
+size 24194
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_pw.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_pw.png
new file mode 100644
index 00000000000..4b5da2799e0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/maintenance_pw.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f96e52a41eccee97d478444aa7bb13c0498cab548a46a885c1ef615ec42eec58
+size 121682
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/manage_dashboard_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/manage_dashboard_tab.png
new file mode 100755
index 00000000000..1f7d65636ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/manage_dashboard_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33d9034196c2b006bd942917068400fd65560b4264b570eb6d15f7dffe386735
+size 91985
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialize_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialize_icon.png
new file mode 100644
index 00000000000..ca63f8af02f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialize_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9eb80d3708b42a52ccc44c48715af02b3321fcbdfcbe5ab65779e7543b030b17
+size 1027
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_definition.png
new file mode 100644
index 00000000000..2c83682382a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34b02535bc5e2b2219edcf18bf5c02392aba497ccf601c8d3d024368f029062c
+size 56748
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_general.png
new file mode 100644
index 00000000000..ecd6911c170
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d3eac6a663c0d61c68f65472b91c32fadf83efb974702e8eca2ba9e9fa45565
+size 73571
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_parameter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_parameter.png
new file mode 100644
index 00000000000..2db4d6726dc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_parameter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18a3ea3f4ca652a36e61a42e7a68dacf7d7788c5a8b7bb82b1ce9340a15feb47
+size 130756
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_security.png
new file mode 100644
index 00000000000..b4199dc72e3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89e01b8abf81a135f8ab36cb429fe508ae0417b651c88712316260ef321e260a
+size 149870
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_sql.png
new file mode 100644
index 00000000000..d939c7e587b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90864fcc0382fff3a6ea09c0d98dfd2da852c3eb177eec153a22dbe71acc192c
+size 115650
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_storage.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_storage.png
new file mode 100644
index 00000000000..a2418bdd664
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/materialized_view_storage.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc73671a7cfa6ca2ef3784b3bb9954b53e88ddeae4367eb948166d28b1b89e6b
+size 68869
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/memory_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/memory_analysis_dashboard.png
new file mode 100644
index 00000000000..ef9551bbde5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/memory_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2056fbd60173066925e7ff35ab78a2e4dfa8d545ee0acaea0a7f219d4e219bc8
+size 171811
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_anti_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_anti_join_icon.png
new file mode 100644
index 00000000000..b1645f98ec1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_anti_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b8e5f8250f28faaf1c2a62a3037a97a233174865b1262f9e05371e4fd0083c7
+size 1157
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_join_icon.png
new file mode 100644
index 00000000000..af5d48eec0d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3ae5447c769876c5c2718141b7695ae8973505ce797be9ff8f43c79e8772e91
+size 1013
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_semi_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_semi_join_icon.png
new file mode 100644
index 00000000000..10f25b6bcdf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/merge_semi_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:143b044ff5e59ba23d7fc47af97a90a67b20726b9680d69b3f4b353f02763d79
+size 1125
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_general.png
new file mode 100644
index 00000000000..88eaf0ab2cf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06f73a65ba56e1faf593e810eaa7a3bca2005b0f89eae7d9cbccfba9a8877cb4
+size 62245
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_sql.png
new file mode 100644
index 00000000000..53d30388755
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_objects_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3101b75a2c3734bbd5119012e421b5903fa282dda03e8d8c6fcfbf6ea2fa7ab4
+size 61701
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_agent_cfg.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_agent_cfg.png
new file mode 100755
index 00000000000..efb182e829f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_agent_cfg.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9f6ba45a4538c1dc5d6f6f43a4d1dbe88aaaa856ff3729239b2ef051540c1db
+size 70853
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_restart_agent.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_restart_agent.png
new file mode 100755
index 00000000000..53b730c33ab
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_restart_agent.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7785d943c38b6ba62cfc8affca9d51c9f3baa8cb6668325c845ea4897517df6
+size 36479
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry.png
new file mode 100755
index 00000000000..104689184d6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bf077799ca9aed755fd96f623300c4dab4fd04283e41115c1b64eaf70179fd8
+size 89973
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry_edit.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry_edit.png
new file mode 100755
index 00000000000..098a9323ebe
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_pem_server_windows_registry_edit.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02b6e559dd7974ff91f66e190db53b872ee3e6bcf97b63b36596127193fe21cb
+size 3094
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/move_server_windows_permission.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_server_windows_permission.png
new file mode 100755
index 00000000000..a384eda4312
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/move_server_windows_permission.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:657c8fb80da17fdbe9f214b96b53d7171c5537841caa2aea399fdc11f397e7cb
+size 18225
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_alert_notification.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_alert_notification.png
new file mode 100755
index 00000000000..e45bfe15d01
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_alert_notification.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56dc6382331207b312dae9b9e5178c608320fbe7ac389790291b2ef0f870bfc1
+size 435218
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_server_configuration.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_server_configuration.png
new file mode 100755
index 00000000000..3ff61503e8e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/nagios_server_configuration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e06886530c51a7ba75db17999000cf4cda23472165e3e14077bf4233942dcd9
+size 251266
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_anti_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_anti_join_icon.png
new file mode 100644
index 00000000000..72ccde3d82b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_anti_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:328b5a3d60598b883b7d0046f26464ed218d1f8ba41c19392a0b03c389714708
+size 1476
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_icon.png
new file mode 100644
index 00000000000..163f3e4c6d5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54c9d60035efcbe3f3377df4589f3632d490616eab66d1f8112a91a59df8d1e9
+size 888
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_semi_join_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_semi_join_icon.png
new file mode 100644
index 00000000000..31019e899a6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/nested_loop_semi_join_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a2fda955bbe6560bbbece5191d3fc23680a3c5071beb7f58f4829d89aab325d
+size 1401
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_dialog.png
new file mode 100644
index 00000000000..38a6a48c4dd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68570f1bdd4749962a5271bf71526579500a894f4b771a15ad9258fae0f1818c
+size 89655
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_options.png
new file mode 100644
index 00000000000..52ea7cdbdca
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/new_connection_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00f0fed8cdd910e8ac558ef463c528cd7983270ef381b60c00d54dbad1b4ae85
+size 69703
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/object_activity_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_activity_analysis_dashboard.png
new file mode 100644
index 00000000000..2b937581025
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_activity_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80cc44aa66781baf0d21dda60ec4266f91326131ac9e76d20c1d07855a4cb0ba
+size 733369
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/object_io_details_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_io_details_table.png
new file mode 100644
index 00000000000..3f16ec5e95b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_io_details_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b186e7b0b926d2f595d36c46bbaf31f15dd844ebc56e712696218ea8ed84e558
+size 220610
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/object_storage_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_storage_table.png
new file mode 100644
index 00000000000..51ac7c08f2d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/object_storage_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aed8f97a3f9f721691bed4c7df68a8bcf18ad20a1140608b72ae88ea81eaf52e
+size 405859
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/oper_system_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/oper_system_analysis.png
new file mode 100644
index 00000000000..0af646bd597
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/oper_system_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2657b40b4d2650ab524f8dd8839b80be7c3260dbf4c74000a17356cd5b00fac9
+size 582748
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_disk.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_disk.png
new file mode 100644
index 00000000000..e692e79006a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_disk.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bb6fbeb17caaaf314a4b2477a71af572de3263f21cba245d957185490d859c7
+size 255327
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_network.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_network.png
new file mode 100644
index 00000000000..22237c76141
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/os_analysis_network.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa105a15c4efacba45761c867d37d8e6a030849682019eded5291d15e6330008
+size 85836
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/package_body.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_body.png
new file mode 100644
index 00000000000..de345d0d8ce
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_body.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c97c0e7105ff96d877d6ed1fc11add83bf6f5be906e03e9e678022eadef906e
+size 116520
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/package_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_general.png
new file mode 100644
index 00000000000..3c58daaa96c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e201a463ab40e4c274b6101b1b80748e6577e306f6e6b32dfb3ec2fb1b6c9c77
+size 85559
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/package_header.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_header.png
new file mode 100644
index 00000000000..291478be23f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_header.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d34f07ea1e5b9d2c9c16c903a4d37b1c209246738c33a65b47a41a5168d065f4
+size 59093
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/package_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_security.png
new file mode 100644
index 00000000000..5c99ebe4268
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a7a1d916f8210819ca58283caced35ccda90216294d01afc1619fb0d411f759
+size 45445
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/package_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_sql.png
new file mode 100644
index 00000000000..bc33c16e9a9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/package_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ea21f3f482800f52ef353746b9b0b63526dfe880da77cad41b390c31030c60e
+size 185840
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_direct_output.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_direct_output.png
new file mode 100755
index 00000000000..b9da1792d0f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_direct_output.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7912995d5940fb7372751b10a2d544f81d45d785433a67bd25c0115e3d90c8bc
+size 76204
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_param_value.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_param_value.png
new file mode 100755
index 00000000000..978649e55d2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_param_value.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e66dace9110b1a49c9044d6d87e41f802155efcd12bcdc153256e1c0ca635583
+size 297979
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_report.png
new file mode 100755
index 00000000000..ccdc1b5cc3a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30cfa744dfa90e6b0378aae3be56530a8cc03e79dd6d6b1dcdfcc6ff78bfae8f
+size 133991
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_rules.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_rules.png
new file mode 100755
index 00000000000..110e1a5ab4e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_rules.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7137afcab562b29ee400fc18bcbef13362645c88ac32997c423bd98a656c596
+size 76297
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_servers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_servers.png
new file mode 100755
index 00000000000..47dfec51b1e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_select_servers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9e49a38119db12cd0dd226a6a293118524d4f5da739b8cad4cb875262194113
+size 89395
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_welcome.png
new file mode 100755
index 00000000000..6f5c596f444
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pe_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64ad4f340b3e47218da77773a6d91ef6e5057fb8baad5dc9356c93f8c46d73cb
+size 87093
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem-architecture.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem-architecture.png
new file mode 100644
index 00000000000..0bc32745e13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem-architecture.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:244e0f8ed10b65d003dc70652c02054ad9d517c53b4ea07285d55c9018c76e53
+size 149105
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_access_create_login.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_access_create_login.png
new file mode 100755
index 00000000000..88bacfac6e6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_access_create_login.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d0b6d799192958d92af3f58de098a646d7b3d63965b509c096c62ef16e37e98
+size 115348
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_accessing_create_server_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_accessing_create_server_dialog.png
new file mode 100755
index 00000000000..433852334d3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_accessing_create_server_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1104b859268048b50a8e26e87191825a63f0bf6e1704b7a636e424b3c956ee9
+size 109953
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent.png
new file mode 100644
index 00000000000..869ee7b81e8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d32e0c1e7177afbfb8722643880c4eea1e42ae223ba3b2ec1d0895ce0d45fc2c
+size 203227
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_configurations_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_configurations_properties.png
new file mode 100755
index 00000000000..dbf8541cad7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_configurations_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a562f73d7e0bb9d61b843eedf2472d036cd07810d5ab3edc03703ae9a881957
+size 148863
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_job_notification_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_job_notification_properties.png
new file mode 100755
index 00000000000..37c357af917
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_job_notification_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:034576b003bc73195230ea729099d8043976c7c1b4c5f8d36ec232c88cc2be1c
+size 179122
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_pem_server_windows_installation_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_pem_server_windows_installation_details.png
new file mode 100755
index 00000000000..0eb613487a0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_pem_server_windows_installation_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ea659c749befc0446f84bf6817cdb509aaa58f4538d3dd9fed0eba58e2d38f7
+size 49887
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_properties.png
new file mode 100755
index 00000000000..7c6aeeb8a0b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03550425682609bffd0e341c297f0863566f49cb47ad0c042a0fe1721fbd676f
+size 83748
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_self_registration.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_self_registration.png
new file mode 100644
index 00000000000..fd8836ed5f3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_self_registration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64da02697d4c687a915282fac8ebf9a2712d2c49dbcb1bf8832b6a8641b7bcf6
+size 142259
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_service_account_windows_password.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_service_account_windows_password.png
new file mode 100755
index 00000000000..04fff107d44
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_service_account_windows_password.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:235c8edad793b49e0c906b38868c5e9c66d19869a2ffe532b3bb75d9e25e6b7d
+size 53178
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_welcome_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_welcome_dialog.png
new file mode 100644
index 00000000000..afd4543cd13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_welcome_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77b5a5e3f3178229671721c80b2b9a8720f181322294a15b1831810ec1680dd7
+size 168049
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_advanced_options_certificate_path.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_advanced_options_certificate_path.png
new file mode 100755
index 00000000000..0c1ee820c73
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_advanced_options_certificate_path.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f288bdd22551caf784ad9e083def77379aa6389b25d38fa08501c83bc6a8d027
+size 85966
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_agent_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_agent_details.png
new file mode 100755
index 00000000000..3d6449cf998
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_agent_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5e177b75b81292553e8c4c2d684add09be746d90517f0c933a028ead30ff5a5
+size 46705
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_complete.png
new file mode 100644
index 00000000000..9ab505484ea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a35ca3cc9b9bebcc22f6b69128fc7bd675176fa7de83776d415ea5a4f44fb13
+size 192252
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_directory.png
new file mode 100755
index 00000000000..5a03c05e0f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:971218e280fa26c0f5311b67d794440cac2ec0249ee51de8ce90d1a81c43456e
+size 53697
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_in_progress.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_in_progress.png
new file mode 100755
index 00000000000..b5495f3d665
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_in_progress.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:224a115d1af11b658f37a50740ffaf70c86f0e8718034cbd854d96a348050991
+size 50202
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_ready_to_begin.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_ready_to_begin.png
new file mode 100755
index 00000000000..beab9772b84
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_installation_ready_to_begin.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:080e7a485253c53dfce25a4e54d942317d5fcc449b980523742dc70b2eccd2da
+size 48432
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_license_agreement.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_license_agreement.png
new file mode 100755
index 00000000000..75e898efd78
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_agent_windows_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce61260c3b8bb10124ccb72c2a8fa405158a15b2209ab0f4303d4b64e71425e3
+size 79656
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_agent_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_agent_tab.png
new file mode 100644
index 00000000000..91ec51e844a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_agent_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:772cfd131e1263c61cbb579166999d1a0664b0f9d88cce7a8d5d6f6c574c8c2b
+size 93571
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_delete_confirm.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_delete_confirm.png
new file mode 100644
index 00000000000..489a4a86b97
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_delete_confirm.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d45c61620acec1d4329b6513dad4cb05eb1e7cedd04cb775ce4cce9cef71972
+size 108851
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_select_servers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_select_servers.png
new file mode 100644
index 00000000000..02a6926572d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_select_servers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b19d71f922c1ee040a744fbace12862118290e4f46b6fce98c777bb2a694edcc
+size 89412
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_server_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_server_tab.png
new file mode 100644
index 00000000000..67e65436b62
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_blackout_server_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa42b6fc50f9e6ac250cc88434154c6a2604c4c26d8358d3dfd9edc4526a5d11
+size 86401
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_general.png
new file mode 100755
index 00000000000..19fb0f05aad
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87236a228a0acb87a8726a95a90fc3a6f2b81331f563b5aee071ee8bb6e0f8c5
+size 235550
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_paramtab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_paramtab.png
new file mode 100755
index 00000000000..d8b4a4cc50c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_paramtab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4decb9661b34ef4f4d90e88df6b5d20cdb76032185bd00d1ae76ee73efda1805
+size 47951
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pdtab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pdtab.png
new file mode 100755
index 00000000000..27e5dbf85fb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pdtab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf527b382ff579720a2ae09a1d670392a51a531f3a88414d108ad899ea79da85
+size 34871
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pre-def.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pre-def.png
new file mode 100755
index 00000000000..769a478a374
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_pre-def.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d26f5677f26bb25a9416f187a6717e5f5d7ad98285bfa46e5edb664e18ae2ad1
+size 91483
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_sqltab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_sqltab.png
new file mode 100755
index 00000000000..aea0cfda11d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_sqltab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b77333f71b536926bd44117a99d50da469a478bb68dc384e851d361ac3dd411
+size 98150
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_tab.png
new file mode 100755
index 00000000000..90f5c5aea7f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_alert_templates_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06941453f4c35686e923a0563189893ecb7fe12926b5db602fc90271b8db6b1c
+size 127584
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_architecture.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_architecture.png
new file mode 100644
index 00000000000..efe4cff5ef1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_architecture.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5d7c587c6747d8709a9d13de727fddc4aee266cab9b100156e15b36dc6a1c24
+size 223708
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_statistics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_statistics.png
new file mode 100644
index 00000000000..e3b642b33ea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_statistics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f20be432fd1b0cbe1352fd9dd6eb47003d4fcacd29886dd0716f4363c8206ecf
+size 330802
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_welcome.png
new file mode 100644
index 00000000000..634f6a3fa76
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dashboard_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87a8923cc79bd04ca41437ae4d35d3119675e86838b4554c687c5b926cfd27e8
+size 465596
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependencies.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependencies.png
new file mode 100644
index 00000000000..3f76e3c8c94
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependencies.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfea893842ca9217044a5a46e09248c693430894b68d6bc571e8ddc3410730c3
+size 122380
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependents.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependents.png
new file mode 100644
index 00000000000..c4651357423
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_dependents.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c1fd2c5d994a630f6da9c8f1f2245d0c995ec13ed0e259be251555e144946d3
+size 135577
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_monitoring.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_monitoring.png
new file mode 100644
index 00000000000..f46d8cf926f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_monitoring.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1aef1aedcc4559adee797a6b60326c5f599e86ec28251ff41a68194cfbcfbce0
+size 157453
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_properties.png
new file mode 100644
index 00000000000..b3cc0d3ef45
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:266e3f4170897cc28f2d6214f2fcc6070e6b93e67475376aa9ac14449f7b4958
+size 167168
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_sql.png
new file mode 100644
index 00000000000..f9918af2930
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:200ea54a53311fe7634b82ef6fc860d7d6e6bd817d462a6f2974fdeb51076d22
+size 100314
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_statistics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_statistics.png
new file mode 100644
index 00000000000..04743e77039
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_statistics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07d5f04fd154f476a8cf56fdb84d7cd7a11c404fb2a09ac48fca44490622db67
+size 285503
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_window.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_window.png
new file mode 100644
index 00000000000..b43b8293782
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_browser_window.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b07095d6e050a68e26ab52cc83ba74160cfe6c97f03a1b70eefebbb799aea9b6
+size 195306
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_conf_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_conf_chart.png
new file mode 100755
index 00000000000..012020fc2ed
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_conf_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f31b0fe8f74146249301f02b251c922805ba9c3cd6ae9d35475d0e108f43472
+size 79744
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_select_metrics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_select_metrics.png
new file mode 100755
index 00000000000..8565c473d17
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_select_metrics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f97a6e5d0fec0787af242e4b37aaa23d8e11f2f494722abc9e9ace891821bc8
+size 153435
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_set_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_set_options.png
new file mode 100755
index 00000000000..c5882c4ce20
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_create_new_chart_set_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3054e22b65b4dddb785052844434a8c02539c5b767e9fec14b849b4cbae69ad
+size 162833
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_chart.png
new file mode 100755
index 00000000000..7c6e1cb3b1a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b696bb86ed0aa97306b626107941d40a73cf62c73e3dc3e7edcadd947bd8ecc
+size 104164
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_section_name.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_section_name.png
new file mode 100755
index 00000000000..5007a2dcab7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_add_section_name.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a6ecc2f18ba398229754c1c6932e686f9e341ccf7175c14f70f226d5844a698
+size 94079
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_chart_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_chart_details.png
new file mode 100755
index 00000000000..cc7e9d9684e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_chart_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef6b9df60f581101e44644f9360589b4748c9132559cb48aec9886dc78716170
+size 56545
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_configure_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_configure_dashboard.png
new file mode 100755
index 00000000000..8e8aeda9504
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_custom_dashboard_configure_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:117f8866389a6e15232eb967b7e58795b7609628346d59de7c2624d9488a3f95
+size 87346
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_dashboards_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_dashboards_menu.png
new file mode 100755
index 00000000000..99004887b87
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_dashboards_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56d325c5f34a6b303e013e234f448fb31b4866aea878a570e85d2608fbb4a32e
+size 117748
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_with_pgbouncer.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_with_pgbouncer.png
new file mode 100755
index 00000000000..ea025f63969
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_with_pgbouncer.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:226d52b5c8e60a4d22ca95b4951a5e70e0814f723050bde1542a2b4fc51de929
+size 197095
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_without_pgbouncer.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_without_pgbouncer.png
new file mode 100755
index 00000000000..2eca5f6c393
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_database_without_pgbouncer.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c376a383bbc5a5999589d5932fa27004f6453dc3f14bf99686143743f8147fc
+size 180375
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_file_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_file_menu.png
new file mode 100755
index 00000000000..e81ca60dbc9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_file_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05fcda76c4cf7064723a3689e4ef679121cd7f8c9ba8383c888c23f984614f32
+size 114672
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_help_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_help_menu.png
new file mode 100755
index 00000000000..bada137dbb7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_help_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ce8f1be4f4606b419d33d4fe3576549c1d84d94f0b066c2340ce7d5cd3a1ccf
+size 103415
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_installation_overview.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_installation_overview.png
new file mode 100755
index 00000000000..0bc32745e13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_installation_overview.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:244e0f8ed10b65d003dc70652c02054ad9d517c53b4ea07285d55c9018c76e53
+size 149105
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report.png
new file mode 100755
index 00000000000..353d0964aea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:690bf9d3fbe7467bd1b5a546b50581bf36d92ff6dda57420187a4ba5c70a2c0d
+size 202054
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_finish.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_finish.png
new file mode 100755
index 00000000000..1e4fc9f92a4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_finish.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e909925b113d8ec0a3d85932dd79a438fd64ce93330826f365501e817443614d
+size 82957
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_options.png
new file mode 100755
index 00000000000..6564f5e6b4f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_report_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48d2d1a5b5eb7e8dd568cac12a893f4cf628de832c73f0a7c2772616338edf0f
+size 133355
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_analyzers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_analyzers.png
new file mode 100755
index 00000000000..923bef71b3c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_analyzers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a6380909855dda06e40174abac40a63908fc64145467673abda846376ab060d
+size 128638
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_servers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_servers.png
new file mode 100755
index 00000000000..a3bc8510cfa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_select_servers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2f31ad22ebb0ab8c01725885679170c6b85af6c4ec02d74d3e56d75978b0b87
+size 96083
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_welcome.png
new file mode 100755
index 00000000000..04e2e826bf7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_analysis_expert_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b5041353a425ea2b55a927a3eb2e9ffe8569cbed180d76ffe19e69a1f6a7648
+size 94765
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_view.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_view.png
new file mode 100644
index 00000000000..1b9dc32ee0c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_log_view.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bc55e280fc50f15406609878cec18e31df32cf9c9bd2051ede77d3ee1d5a544
+size 90869
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_login.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_login.png
new file mode 100755
index 00000000000..e4f5bafe5c1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_login.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9767815f8f7a9ddc36f459630531a47d81d1e46073d5d30bc8a85711caf750c6
+size 143385
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_logon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_logon.png
new file mode 100755
index 00000000000..6a513493a8b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_logon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:619ad4c84a901dff9fae95777c8431341108ae15c25f294ddda4f8c2b21c30a8
+size 107698
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts.png
new file mode 100755
index 00000000000..8f904ce62f6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a37c39928adfe32542764ab99e849c08557c32c246788600af70bf94957b42e4
+size 126230
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_completed.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_completed.png
new file mode 100755
index 00000000000..921c05c8394
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_completed.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb1773151a3167aa848b8fb2ebafdd38091bd1ecbbdb005bd3b7b6d9e3bb1b84
+size 69458
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_custom_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_custom_chart.png
new file mode 100755
index 00000000000..a2bfdf6e709
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_custom_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae2dba698237de09388c36c5ceb2b74e9016107ab94e12b11770acb8693e454a
+size 58675
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_metrics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_metrics.png
new file mode 100755
index 00000000000..3ffda1cfa0c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_metrics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe427822ca9fd1cf9808211dcdece2c8ef0f41ffdeb879542c42fd83d117ff43
+size 194729
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_options.png
new file mode 100755
index 00000000000..3cacd6602be
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:227c56d63dfd1888d673088c533a4a2af52fb56a1f151d0f6a37a5d136b53c2e
+size 113311
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_permissions.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_permissions.png
new file mode 100755
index 00000000000..4d591501a33
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_permissions.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6348afd4fba79ec13c1a56738be6351bf448b839a0b9e61d70c9128cad376b1d
+size 91014
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_template.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_template.png
new file mode 100755
index 00000000000..ec6fe2f49c9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_imported_template.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fddc3090d980dba90aca603d1140e0ee172ebf3354f912bb6bce6aa35dbba79c
+size 96930
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_set_permissions.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_set_permissions.png
new file mode 100755
index 00000000000..cec1f66bd17
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_charts_set_permissions.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9506bf8146b88e1e0d034104ae30fe2a558d1b42525fc15e37a69c836b7b93d
+size 80734
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_dashboards_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_dashboards_tab.png
new file mode 100644
index 00000000000..58374e9dbbc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_dashboards_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62e81d394ddccdaa86db4e08a98aa2c369f454cc46a260d95661b33d175e3397
+size 131189
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_import_charts_completed.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_import_charts_completed.png
new file mode 100644
index 00000000000..fc9da9952e8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_import_charts_completed.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8606a61a051395d6ecd689022bef9c5cab00898e746685575f0c4f2add469f70
+size 50079
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_probes_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_probes_tab.png
new file mode 100755
index 00000000000..12dc3682ec5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_manage_probes_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ead0a814ee3c537253595d9eb6962fafca6ed90140f2b2b7ae24fe85cef482b2
+size 410987
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_management_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_management_menu.png
new file mode 100755
index 00000000000..a1e9ab0887b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_management_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:506b1e7990f97d3db5c893e04664f9887de6b2c4c6f47ba71014ae1838c6780f
+size 134644
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_object_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_object_menu.png
new file mode 100755
index 00000000000..acc86366414
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_object_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a2fa70428510c37902d6a30f5f97c7fbdef413ebfcbad8eadae8c4f3d0afcd2
+size 117329
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_online_help.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_online_help.png
new file mode 100755
index 00000000000..c35b59049c2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_online_help.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee1a77b0783eca97780d42f6685aa1ab6a62467ca2763b639d18e9cdc120093c
+size 281162
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pg_hba.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pg_hba.png
new file mode 100755
index 00000000000..54e494dddcf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pg_hba.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:793359b1b6429a7d8dffe31b028f438d8ce5a7aec30bba4420dc002261de50a8
+size 77236
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_with.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_with.png
new file mode 100644
index 00000000000..b21a36177fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_with.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86b13fdb915adfb9c9234ac04fa1cb1e5b6b8500df0f0f7b7df89bb9dc91ca0e
+size 197095
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_without.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_without.png
new file mode 100644
index 00000000000..fd42f4ed4fd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_pgbouncer_without.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a45cc7dcbda0d12702917b6819a1bfa53675efd7932999d995ace96a3b432e6c
+size 180375
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_roles_membership_example.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_roles_membership_example.png
new file mode 100644
index 00000000000..1b9906f212f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_roles_membership_example.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:491d07c6e7e8ea2da910da6d813e5a70fc119dc69c949681c33f722ab239c6ad
+size 98780
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_rpm_installation_agent.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_rpm_installation_agent.png
new file mode 100755
index 00000000000..619d13080cb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_rpm_installation_agent.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ad2fe6169d26c20620299cf45d66075fa7902a43adef00703710311a482bb06
+size 231300
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_details.png
new file mode 100644
index 00000000000..eda5a788a56
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cbadd6f8808c03669fc3eec9457b610b3c954da7d9f411433fd5afd1ba5629d
+size 116784
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_steps.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_steps.png
new file mode 100644
index 00000000000..a751b483990
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_steps.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3f4ec8fbdac5981cf5869000bd8e42d86b876687acf3c91d00c02c99a5360e5
+size 144595
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_tab.png
new file mode 100644
index 00000000000..41fa9fe3e7f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_scheduled_task_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9591f7de77f3c473e2ea6cb0505269046bbfb538a82553938162ee603a93755
+size 108895
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server.png
new file mode 100644
index 00000000000..2233553aefd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:425892a109affcfa446d2fd903c6aafbf256e08a59076aa39769fda2b7d36e54
+size 232269
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_config.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_config.png
new file mode 100755
index 00000000000..80c74ade571
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_config.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35768822fa7063e3e14e44dd7cbae7d14a7e02955ef385cad8d0cc6f8b91f0c9
+size 131670
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_administrators_password.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_administrators_password.png
new file mode 100755
index 00000000000..076c067566c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_administrators_password.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d49ce7561bb709dd468592687eac750e6fc6570d2376642b830b8f3a18687d15
+size 118243
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_advanced_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_advanced_options.png
new file mode 100755
index 00000000000..2122cf7be59
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_advanced_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de19ee9ef0a9ee893fdf340ce215f4fda04fcd84e276bc2c345c0e9b51ac6708
+size 76410
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_agent_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_agent_details.png
new file mode 100755
index 00000000000..bd01232928d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_agent_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f78a5d9c2c667ee87a48813d86bd80aba295302bb4a78179984128fa7f580b5
+size 91246
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_database_server_selection.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_database_server_selection.png
new file mode 100755
index 00000000000..c60da7f2135
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_database_server_selection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89a48b47d4c3244be30638545532d202c2c468a9f882e6c3f93b1bfdae08c55e
+size 133316
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_begins.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_begins.png
new file mode 100755
index 00000000000..4227dda5994
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_begins.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bec885aac500c11ab5969be3730dae6c194e02f0b54fa7cd8554ff0cfbee4f60
+size 63622
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_complete.png
new file mode 100644
index 00000000000..1d8be91b97c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc2dc5a2e1b4bcf0c4df423860578d52e43f2d29a162737fd3690ee5ffe88ff7
+size 200366
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_db_server_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_db_server_details.png
new file mode 100755
index 00000000000..fe01e704550
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_db_server_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f46f2fea02e09fcf8c698cbf1caf9fcbc616cf8cadd1e3b6c7d047dad8f11c7b
+size 97310
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_directory.png
new file mode 100755
index 00000000000..a7ab83c221c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b423fc9ed54958a6e01fe3b9a3674a4932fe41faeb6959f5b323bfeca189efef
+size 90431
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_in_progress.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_in_progress.png
new file mode 100755
index 00000000000..8310522c045
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_installation_in_progress.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1716a9796709c4b4b05f6d3347c078421c5dbbb00ea74534929c02361f7a6ec8
+size 86475
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_license_agreement.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_license_agreement.png
new file mode 100755
index 00000000000..56acaba079d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5158be3c9166113a8f53665cc682ed54dcb3927c4c647ed3052dea4439aaed56
+size 287278
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_network_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_network_details.png
new file mode 100755
index 00000000000..028d7408047
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_network_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fa8e0b32e3a8ebb6cb56a6cbf36ecf8e308d42641ba7d2d73d8384abc973d7a
+size 97243
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_pem_db_created.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_pem_db_created.png
new file mode 100755
index 00000000000..e0f570813f1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_pem_db_created.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdb275a6c62b033f422d45f27a0e3f35e081358959b4b678d02daefe5851bcca
+size 112333
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_welcome_wizard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_welcome_wizard.png
new file mode 100644
index 00000000000..089e04d2012
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_existing_pg_welcome_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72c94874da0e1ccfb5749872a412c21bbb958720e56877947802727756a19015
+size 168220
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_agent_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_agent_details.png
new file mode 100755
index 00000000000..33d496e9152
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_agent_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7ed9d946e878b87362fe748521389d00387cc67b369500c213f32b19ec70259
+size 97492
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_db_pem_created.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_db_pem_created.png
new file mode 100644
index 00000000000..8457b47457a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_db_pem_created.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89ca24c8a48cf006e338b546b5aa9125d03e26d4e4c76c3831496894e149e82c
+size 118535
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_begins.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_begins.png
new file mode 100755
index 00000000000..dc16920462e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_begins.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3603bb5a231cc2c9e05700570623447378395feb382086131d0fe47d3ad4708
+size 70189
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_complete.png
new file mode 100644
index 00000000000..1d8be91b97c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc2dc5a2e1b4bcf0c4df423860578d52e43f2d29a162737fd3690ee5ffe88ff7
+size 200366
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_directory.png
new file mode 100755
index 00000000000..6dbc65cf0b3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d6ecbc44c81b6fac11764b1a32bdd2ee2f5b0edd84ba1bc01a5898b2a7ea736
+size 92033
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_in_progress.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_in_progress.png
new file mode 100644
index 00000000000..d94e9eecdb1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_installation_in_progress.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae4a16ffbb9a9835965056cea6f167a12375e58e32f7cef84f0e6c4f8bfc4c69
+size 91907
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_license_agreement.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_license_agreement.png
new file mode 100755
index 00000000000..67e23b3867c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61057219f849dbeeb775437bbd9a0be0c80a97e8c981036d55471d2b53565062
+size 293662
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_network_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_network_details.png
new file mode 100755
index 00000000000..ef1ccdf47b0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_network_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a48d4b85b6f22fc20516c4251a970a8df21aed4954814d576a396f783d99228b
+size 106266
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pemagent_service_account_password.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pemagent_service_account_password.png
new file mode 100755
index 00000000000..ab30c319ed0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pemagent_service_account_password.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2d06b6ab7e8f3f8dd5206f95b70a1d3f5778e7d39ddc8825edea09a1cc59663
+size 121793
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pgsql_credentials.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pgsql_credentials.png
new file mode 100644
index 00000000000..5ac7c146ea3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_pgsql_credentials.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85887eeaae77b363ce7e3f5ef3fdd77c077f2345ff858bcfaefda357d61d52af
+size 97934
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_prerequisites_checks.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_prerequisites_checks.png
new file mode 100644
index 00000000000..f486d6a0bc6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_prerequisites_checks.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8974fd28724974ccb887d6a7a2733e7bf1013c1709fc8c7e736d22310db2160f
+size 138580
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_welcome_wizard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_welcome_wizard.png
new file mode 100644
index 00000000000..089e04d2012
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_same_host_welcome_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72c94874da0e1ccfb5749872a412c21bbb958720e56877947802727756a19015
+size 168220
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_PEM_httpd_installation_wizard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_PEM_httpd_installation_wizard.png
new file mode 100644
index 00000000000..28ee5e23966
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_PEM_httpd_installation_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1797aa3dbeda2932f0d24169690c80fe7b2b80f4268d75d56ec8edd3caf896a1
+size 152364
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_advanced_options_dialog_select_database.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_advanced_options_dialog_select_database.png
new file mode 100755
index 00000000000..31bdc435e71
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_advanced_options_dialog_select_database.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a311c3017949d9ec9ea77525e73d60b0af62c9a48eff4a21e112d2ea9b80a85
+size 76012
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_agent_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_agent_details.png
new file mode 100755
index 00000000000..e0cbe5516df
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_agent_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a540bba57213f0836051752ad5a65701e0f33e46f41e73430bcd4d66be92773
+size 99621
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_installation_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_installation_details.png
new file mode 100755
index 00000000000..efd4fad62ad
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_installation_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e9bda1811f9881386e403f431b5d340b22c71ba6a4391c59c1d01d68b141ea6
+size 95904
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_selection.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_selection.png
new file mode 100755
index 00000000000..fc33762628f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_database_server_selection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c03841c64c4cdf0271164f3d67576245cf0a9429c322276d7af46e725d2cbbd
+size 121374
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_begins.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_begins.png
new file mode 100755
index 00000000000..71ed6efa81d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_begins.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd1edb8bcc18b9a2dc16dc6c75a8fec6536f1a70939964a7bb7e4cfcabc59ffc
+size 70634
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_complete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_complete.png
new file mode 100644
index 00000000000..1d8be91b97c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc2dc5a2e1b4bcf0c4df423860578d52e43f2d29a162737fd3690ee5ffe88ff7
+size 200366
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_directory.png
new file mode 100755
index 00000000000..a7ab83c221c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b423fc9ed54958a6e01fe3b9a3674a4932fe41faeb6959f5b323bfeca189efef
+size 90431
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_in_progress.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_in_progress.png
new file mode 100755
index 00000000000..c9258686990
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installation_in_progress.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fc6d4415a66f1b9cf80f1c6f170e0de843f8aa4e95560bf6049977cc12da568
+size 78815
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_advanced_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_advanced_options.png
new file mode 100755
index 00000000000..ac266b423ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_advanced_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5f3e0d5482d167c27ee17ef0ded63f62a6910c80bf2b9b6f9ae20b3f4863bb3
+size 76365
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_installing_missing_dependency_languagepack.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_installing_missing_dependency_languagepack.png
new file mode 100755
index 00000000000..37214aa7691
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_installing_web_services_installing_missing_dependency_languagepack.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c608f6d9782feb3efa75be986ea3df4a36a8470cc1f9b47c4fda3939a4307f47
+size 129123
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_license_agreement.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_license_agreement.png
new file mode 100755
index 00000000000..56acaba079d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5158be3c9166113a8f53665cc682ed54dcb3927c4c647ed3052dea4439aaed56
+size 287278
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_network_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_network_details.png
new file mode 100755
index 00000000000..28e9cea2794
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_network_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bf4ca5d2044cc8190d3a48c5f14e1ddd29afd5d71579f43a08eab25ae08a30d
+size 107014
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_pem_db_created.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_pem_db_created.png
new file mode 100755
index 00000000000..5670ad04eb8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_pem_db_created.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce702705f8dd21b233f4a602eee73ad218e7d890759180c7bef2fcbc437eee31
+size 99589
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_and_database.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_and_database.png
new file mode 100755
index 00000000000..893751059a0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_and_database.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:072f9806e16d188ab1bd04478d2a86e8bc25c205e92909245e40abaf14777b32
+size 76036
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_checking_components.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_checking_components.png
new file mode 100755
index 00000000000..0cbe509659c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_web_services_checking_components.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0f3acd60c536e5a59637a5215421fb6a430b720e17991013543f99e69ed2484
+size 99810
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_webservices_installing_database_server.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_webservices_installing_database_server.png
new file mode 100755
index 00000000000..a4d49118927
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_webservices_installing_database_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a16819212f594b179a1b528a1ad0128554df456add7c21f1aa950ad84394ef9e
+size 115139
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_welcome_wizard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_welcome_wizard.png
new file mode 100644
index 00000000000..089e04d2012
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_host_welcome_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72c94874da0e1ccfb5749872a412c21bbb958720e56877947802727756a19015
+size 168220
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_pem_agent_service_account.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_pem_agent_service_account.png
new file mode 100755
index 00000000000..020b014b19f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_on_separate_pem_agent_service_account.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b905cb61cca30eb897166cadc919e8dc9081810172f65c71a5b7d73a5339e96
+size 121854
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_tools_menu_queue_server.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_tools_menu_queue_server.png
new file mode 100755
index 00000000000..1b7235e501a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_server_tools_menu_queue_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7e8366b8713b33de9e5a0484cf3794c14aac0091d0b16f94adda715b41480a2
+size 159272
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_httpd.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_httpd.png
new file mode 100755
index 00000000000..f61d25990b3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_httpd.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd73f7142070639c470957422d357152dcfd8338e9a11a4dd2344c960f942054
+size 52561
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_windows_server_agent.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_windows_server_agent.png
new file mode 100755
index 00000000000..905beef89c5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_services_windows_server_agent.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a894cfc81591ee32aecf0e6a39c7e0697b13e044b7d7055c85e9f1751f94b8fd
+size 52930
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_task_view.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_task_view.png
new file mode 100644
index 00000000000..a508ef36acf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_task_view.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:079f59183b5e16da95496f7cc413a63c6f9f3a385a2f2bf1b04000e384d81b14
+size 80992
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_tool_menu.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_tool_menu.png
new file mode 100644
index 00000000000..f6b311f91e5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_tool_menu.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49b28650e989a6682837149bfc84ac201e278a024899ea7d282fe67ad0ad1539
+size 224123
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_toolbar.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_toolbar.png
new file mode 100644
index 00000000000..75ccd1169f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_toolbar.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99abeaab3f4f1bbbeed84ffc08721a069f8bf0eb578cace92f7e41e3e258d7ce
+size 150288
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_existing_installation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_existing_installation.png
new file mode 100755
index 00000000000..1c551cf487a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_existing_installation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1956285f6480e03761368f76cc2fe2fd056cd1961fbe6f1694137c4fbd2c2939
+size 87734
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_finish.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_finish.png
new file mode 100644
index 00000000000..9ab505484ea
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_finish.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a35ca3cc9b9bebcc22f6b69128fc7bd675176fa7de83776d415ea5a4f44fb13
+size 192252
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_license.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_license.png
new file mode 100755
index 00000000000..0206bc3373e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_license.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0a55b292615826802b0438aacc24333f676d27f6ebc5ffdb0567e628b186fd7
+size 297522
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_pemAgent_service_account.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_pemAgent_service_account.png
new file mode 100755
index 00000000000..0919360e8d2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_pemAgent_service_account.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73de2f67a31ebd8c7aa7cec9f7e0a939dcc226dab808a58f5b8a3cdbb828957d
+size 94391
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_ready_install.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_ready_install.png
new file mode 100755
index 00000000000..202b4f99615
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_ready_install.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6583a8ca9caaa8e8892675a4907fb4fe2b267b10790e28942256236a0b60f992
+size 77506
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_restart_pop_up.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_restart_pop_up.png
new file mode 100755
index 00000000000..60fec896d13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_restart_pop_up.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7006ad134c9305b440822c0d3b2f8e212f3750a06c1119594b1180acdb3bb2c
+size 44564
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_welcome.png
new file mode 100644
index 00000000000..afd4543cd13
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_agent_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77b5a5e3f3178229671721c80b2b9a8720f181322294a15b1831810ec1680dd7
+size 168049
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_DB_installation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_DB_installation.png
new file mode 100644
index 00000000000..437d22bb9d7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_DB_installation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c67c27e7fa2f1370b9727860039eef0d11c177a67775dd83a13e1fb906eb1dc8
+size 101448
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_dependency_missing.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_dependency_missing.png
new file mode 100644
index 00000000000..b72f6341768
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_dependency_missing.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ccc8d662dcb97be52d5a44e68dde1a520afac273961b50fe01f31adfa799aa8
+size 103012
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_error.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_error.png
new file mode 100755
index 00000000000..cd00eb6d200
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_error.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c54245af2d4006d8540ba9904f7bf246f45feee0d38b6a9a286323ad05ef1281
+size 268335
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_existing_installation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_existing_installation.png
new file mode 100644
index 00000000000..2cf3ab94b4b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_existing_installation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfa1fcf9967f3620c2e931fbb1a5a19d1a2295a5019cda3de804388dc2c2658d
+size 86566
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_finish.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_finish.png
new file mode 100644
index 00000000000..930f791aa4c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_finish.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:585c86de37e8270a46ec943f2f10e137c1a4bfb314bbacbc6f83bf348e34363c
+size 201508
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_installing.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_installing.png
new file mode 100644
index 00000000000..0c8b47b1ad7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_installing.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:457d2e99e346f2799564a9aee6ce729aae79e7a910da57d49e2047fe6d64144e
+size 98174
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_license.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_license.png
new file mode 100644
index 00000000000..cb96fdf8e8e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_license.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02d733ff5e1092f9cb50e98c732a2c90cccfaafa56f37a2c1835b299cb37d4a9
+size 297850
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pemAgent_service_account.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pemAgent_service_account.png
new file mode 100644
index 00000000000..de1aeaace4a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pemAgent_service_account.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef17bd65fb5333afc27a4b179ff382599ba80340cfea3c8d3ec6edae1b41b0a8
+size 92231
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pop_up.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pop_up.png
new file mode 100644
index 00000000000..df079654544
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_pop_up.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3d93a94e862dffa159ec3fdf6ea6f26f7859549ea96922870a9b863ddbc2089
+size 121756
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_ready_install.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_ready_install.png
new file mode 100644
index 00000000000..1c1b1362380
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_ready_install.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36e2728f7e1c73462768e935fac2b775c9abe99cacc35710dbd7e8068ea67627
+size 77820
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_webservice_configure.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_webservice_configure.png
new file mode 100644
index 00000000000..78f9a1b3b68
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_webservice_configure.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1fe8b1834b5eba54e41f1207f778573fa8654a058170caa9900f87ee1d2ff16
+size 122360
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_welcome.png
new file mode 100644
index 00000000000..0cb2cc561ca
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_upgrade_server_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:179e05f47ac62dbfb368fcc7d98b2e203222c7f7bd13bdb21b42c53612549311
+size 166999
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_web_interface.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_web_interface.png
new file mode 100755
index 00000000000..27f40f839c3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pem_web_interface.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c60114d1a3248122a7e0cbd150ff70dc612c53c9851b65f32abcf15ee994f2b
+size 224584
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_chart_legends.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_chart_legends.png
new file mode 100644
index 00000000000..22f18113246
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_chart_legends.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eea7a04e2d5c5db2d0cdb24bb0186c4f52bdfc59bbf668711533478b59093250
+size 184897
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_datetime_selection.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_datetime_selection.png
new file mode 100644
index 00000000000..64b3419cf5b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_datetime_selection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08794e38411df7720cadd420e31f8ea5dc205e688d451fe30f9fcb311a82f384
+size 248557
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_error.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_error.png
new file mode 100644
index 00000000000..df220c0edd9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_error.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1db77b9aff79bd38a72cef37c7b4ddbbb7194bae404ba762682d86da6921f1af
+size 36623
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_intro.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_intro.png
new file mode 100644
index 00000000000..2b04e03d99f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_intro.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d9cfab3a78c3f3ff39fc13752149f9eb95f60a9ea8d0a50b4bba128f47b0d5e
+size 262269
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_query_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_query_dashboard.png
new file mode 100644
index 00000000000..b5a5ac58e80
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_query_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac36d8d36abe3f1a2d1152db04cd130f25dd01cc17c8e1a195480a9fb5237d0d
+size 297855
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_table_filter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_table_filter.png
new file mode 100644
index 00000000000..fcf826ccb07
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_table_filter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7057c733c3176299094cdc7d88fb92989e1fbdd7c2d1c763a7cb9ea1661f88f
+size 68550
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_timeseries_selection.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_timeseries_selection.png
new file mode 100644
index 00000000000..399e2b3f59c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_timeseries_selection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f66fc98ea2d030f5a6df5ad9b81dee0a81ac7d35eed407f2e82861d2d371615
+size 319525
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_users_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_users_table.png
new file mode 100644
index 00000000000..0f35ed73f62
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_users_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ac894619285e501bc5d72582b6c16af298abac215ea482b7b36f988ddfa62c6
+size 42842
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_wait_events.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_wait_events.png
new file mode 100644
index 00000000000..265ade52708
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/performance_diagnostic_wait_events.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d900777b3c902723ab32e558e9d656677763d22ad707fc1e00c8cfcc40541a9
+size 38871
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/personalize_chart.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/personalize_chart.png
new file mode 100755
index 00000000000..e732b03a1da
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/personalize_chart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28e713048aa91068b8440793ff5746fad540f9ebcc884c2cfe1109672916d1db
+size 37738
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_general.png
new file mode 100644
index 00000000000..67dcc88424c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7bbadfb56e26236106ace948a9e1411e138cb04542a6933b51e0615e6ba2171
+size 97047
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_properties.png
new file mode 100644
index 00000000000..d255af81b27
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba267a22b69f352ecbea5429ebc810190b3f875076e028162170a63bfb78eb66
+size 58876
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_definition.png
new file mode 100644
index 00000000000..b8761f335cc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84fe9f95527aea4a1b76e30550e444f836280354a922df66dcbd0a55a5b5e94c
+size 96901
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_exceptions.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_exceptions.png
new file mode 100644
index 00000000000..9cad8d33d69
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_exceptions.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be401b66f2d0aff13516c43f91ebe921dacf0cb63c48460bd7ed45e83aa36745
+size 76105
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_repeat.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_repeat.png
new file mode 100644
index 00000000000..bc2734f2923
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedule_repeat.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d37950a128677bc45c12a6a5eb7bd029766ac0bff771f3d1087ea6bf32e3082c
+size 133047
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails1.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails1.png
new file mode 100644
index 00000000000..8dfed4219eb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails1.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4e826f6fe65a73d2874ab3042d017da59a3f4bcb6631c726349680cf270b24a
+size 107419
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails2.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails2.png
new file mode 100644
index 00000000000..72b9aaba4a9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e86610d3bdcd765922463b2755036cca85509b2099ba85eead9ff15b73f8e238
+size 308296
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails3.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails3.png
new file mode 100644
index 00000000000..c46f14dd1c0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduledetails3.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f469115b914973a74357a06f519d19b9db5883cffef4c6141f7e5237f1d978da
+size 78644
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduleproperties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduleproperties.png
new file mode 100644
index 00000000000..e515a681eac
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_scheduleproperties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77cd10940d907b4ea56144124f2ff9ac265667cc14ecffbdbac14ea735a8235a
+size 48220
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedules.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedules.png
new file mode 100644
index 00000000000..8fa25d8005e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_schedules.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a072fb338e2c7754867bb1b96e6c62a0b792ebf62e5bfdc98a288b3fcda5d057
+size 60286
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_sql.png
new file mode 100644
index 00000000000..882fcc72536
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ecd10961b884cb42e0cf98307bdd52291c405d6a96b541d1f0d2caf407502420
+size 162622
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition.png
new file mode 100644
index 00000000000..3b9ee644e18
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:821f6440ce6b54a7413719be8d34cedd09df4d7635cf7625c068f4af1d24e551
+size 161538
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition_code.png
new file mode 100644
index 00000000000..e69f52f9501
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_step_definition_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a3401be2f7c8c7fa8b91aa7ecb89700e92d908f11479a3f81659caa80d91454
+size 67200
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepdetails.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepdetails.png
new file mode 100644
index 00000000000..cc59713d795
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepdetails.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f84aad75a5c7d61dae077af13d19596f8aa18044c80bcc2317201ce64383426
+size 130553
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_steps.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_steps.png
new file mode 100644
index 00000000000..eb05b99a9c1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_steps.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fab19f8e0f3f42bc1af30584bdcc485cc8f8ca4ee5b0128dba7ea0dcfd9e3e0f
+size 56765
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepstats.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepstats.png
new file mode 100644
index 00000000000..1140f6026b3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/pgagent_stepstats.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:276b4462e2da80d4ddc2c4ac98cf3991ff0a538e73d0a313199a01876426d913
+size 39830
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_bart_servers_nodes.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_bart_servers_nodes.png
new file mode 100644
index 00000000000..9ba8f85e087
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_bart_servers_nodes.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8760f28878cbac9703cf72721bb290596aacd3809c5cfe8f481a3c971c570dda
+size 83099
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_display.png
new file mode 100644
index 00000000000..7a408f288fb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33eb2bf003567cffadc6a8c11c5b8f8bc6dd13e5834ead6ebf179280d51d0af6
+size 181829
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_keyboard_shortcuts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_keyboard_shortcuts.png
new file mode 100644
index 00000000000..0015a85008b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_keyboard_shortcuts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74e9b7c98725ba30389178d782ed221fcfa6e3493f80be97dce636723e7834dd
+size 180622
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_nodes.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_nodes.png
new file mode 100644
index 00000000000..046806aec29
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_nodes.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4151e6fd83f6a1ce43c5aa2786b49e309cd0b240292f1df872efb7bdc2d96844
+size 125728
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_properties.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_properties.png
new file mode 100644
index 00000000000..232f0606bf1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_properties.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fef55bedb9181e878cd576092e78c1b22edf464692c28002291227081ecb659
+size 100046
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_tab_settings.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_tab_settings.png
new file mode 100644
index 00000000000..560d983fe04
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_browser_tab_settings.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e69ec9c2cb34cab250441696a8271a6e6fc7645336fc94d4acb00fb86e75d3a
+size 302196
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_display.png
new file mode 100644
index 00000000000..7eba881d9c1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8baedc365fd2e55eda279174b18b1c29a126876d3f183089038a938840829d13
+size 143189
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_graphs.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_graphs.png
new file mode 100644
index 00000000000..6ea1ffb6a25
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_dashboard_graphs.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f2a1ccff8abc3c0d89745c02bea7b7bdf2003972e9827bf7e8fce857cddc646
+size 151777
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_display.png
new file mode 100644
index 00000000000..c416692593d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:956915366e0b1e0c86a33940d8522359792d4d58d85dcadf13a38970514500f6
+size 150246
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_keyboard_shortcuts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_keyboard_shortcuts.png
new file mode 100644
index 00000000000..87c6f9b15ba
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_debugger_keyboard_shortcuts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d908dd23ca3784574599f5dbc7597f1c850fe160635523a1fc61725361652a48
+size 169155
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_themes.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_themes.png
new file mode 100644
index 00000000000..455b6d9ba53
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_themes.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62b44890fbf371403bd216f5f1b9aa34216da803bfc3327f131ff31acc432115
+size 116047
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_user_language.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_user_language.png
new file mode 100644
index 00000000000..3136d9cb539
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_misc_user_language.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2c015ff7077240bdbb25d19a8294aa9ba5abec42a32c1dfa987d82b97b035ae
+size 81365
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_binary.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_binary.png
new file mode 100644
index 00000000000..2469482f5ec
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_binary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89f0cf543229a5d2a40f8b2a35122ced862ac699479dca1d708c0ebc479be7ed
+size 165305
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_help.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_help.png
new file mode 100644
index 00000000000..b52b4e9602f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_paths_help.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51fb78c3185ad71455b146f95e7f89f69435c6a9a4ded27226b4161111dc9acf
+size 149437
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_performance_diagnostic_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_performance_diagnostic_display.png
new file mode 100644
index 00000000000..e56ae5ddf61
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_performance_diagnostic_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d0bfb13f8da59242860848496fcb53c3ac9b68a34b1047e4b7c9b51e127a6d5
+size 95543
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_scheduled_tasks_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_scheduled_tasks_options.png
new file mode 100644
index 00000000000..35e9431d828
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_scheduled_tasks_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab37725e80a6af1cd7c67f2835619f072707b973410466ff618f92dfbfe5876b
+size 95247
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_schema_diff.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_schema_diff.png
new file mode 100644
index 00000000000..a3aa784bf89
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_schema_diff.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f4abb68034e041c35962b85d12809df88e445a67184161d8415d7a187233229
+size 157266
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_auto_completion.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_auto_completion.png
new file mode 100644
index 00000000000..af9fe95e7dd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_auto_completion.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da3db48ed4b4d5f611ecba6f2ecd4c34911097e2da1f17532241a5d575d91c8c
+size 107325
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_csv_output.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_csv_output.png
new file mode 100644
index 00000000000..d236ef5054b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_csv_output.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8374271ad4ccd8818821f3ab0a2605182b5be10ba6228ab9cfd07b0e136bcb30
+size 128279
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_display.png
new file mode 100644
index 00000000000..40fd5d93f50
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1eaf490132defd8e6e89053264af34dfdaf19d0d69c2108f97c5690a8a110a4
+size 174697
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_editor.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_editor.png
new file mode 100644
index 00000000000..2601cd31834
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_editor.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9db1ec2663adf5c48af70b25ba66d96719bd38a6744c3d13099981ded4dba795
+size 232097
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_explain.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_explain.png
new file mode 100644
index 00000000000..e0601d49f4d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_explain.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d75a6cad7b8b04decb505f4cb418ccdfde925d2270b54437f5609887a9298d6
+size 90928
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_formatting.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_formatting.png
new file mode 100644
index 00000000000..ee989255c89
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_formatting.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8437e220b59079a0db0cba638509d82dad264edcfffaa4afd264280bddaf974
+size 204180
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_keyboard_shortcuts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_keyboard_shortcuts.png
new file mode 100644
index 00000000000..6785cc5a11e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_keyboard_shortcuts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:707ba6f960ad5bd6ed6d7bf7d79af9317f97c71c7193b5a72983d333287f716a
+size 111850
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_options.png
new file mode 100644
index 00000000000..0f0c06f5357
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ee17cd453aa38663f38aa5ca2a4c6cfe3d25ec2e0fba29faca832e2dffc212b
+size 237964
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_display.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_display.png
new file mode 100644
index 00000000000..f6100b4117a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_display.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f1f7f929bc6e0f728ed6fbb2b490b9e5e231430e7316114d80db35956d62415
+size 83919
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_keyboard_shortcuts.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_keyboard_shortcuts.png
new file mode 100644
index 00000000000..c889c71e0c5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_profiler_keyboard_shortcuts.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3fac5da15d4e248ada418307fa86239022f209a8592be8e31b43701db92149d
+size 107257
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_results_grid.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_results_grid.png
new file mode 100644
index 00000000000..626804d5c87
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_sql_results_grid.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62119a36ae1372c8e02b8e2f80edf9ea86e212d03c07abdb35a124cf3e0c71c6
+size 87001
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_storage_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_storage_options.png
new file mode 100644
index 00000000000..dc80c04c052
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/preferences_storage_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4472b218165caee9fea0584450e460b2e8da41d6f7940865500395243b544b7
+size 91063
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_definition.png
new file mode 100644
index 00000000000..93090d43b3c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:406cf35f6f7b259c9578106443810ff5cc2a1aaca4f03bde842351c4bede1b5d
+size 90325
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_general.png
new file mode 100644
index 00000000000..ac2df4cae3e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5540c4c976bfbc6cbd09e681e93981a3a932216feb2024ee2a53721b1c8389b2
+size 57042
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_sql.png
new file mode 100644
index 00000000000..a0d2418c78b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/primary_key_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3c23f3cf71049faf0efe06947a85aaa744c8e70ab9a1ad3bbbdd123b2397940
+size 67970
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/probe_log_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/probe_log_analysis.png
new file mode 100644
index 00000000000..081a81f2ac7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/probe_log_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acba92296e62761d3dbd8e393a261167fb2dddf6d6ade3a7160f685c5e3d7868
+size 329432
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_code.png
new file mode 100644
index 00000000000..2558a4c738f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb9032cfe1c6075c11b9c94aa8c812bd432dd04d598c1e5e0af5ee35ded2f3fa
+size 53727
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_definition.png
new file mode 100644
index 00000000000..39b462aa993
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80a4df4992fdc78ea0761ce698bb9c9921ebeeb015600dc3bc2d710dd53484ef
+size 53531
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_general.png
new file mode 100644
index 00000000000..630fee0c033
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c6382d97db4069ed0387f6440c0e87fe5c84677e508aec9936e6ef83f81e60b
+size 54938
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_options.png
new file mode 100644
index 00000000000..4c640805afb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fdf80d2d9e4ad00e7edc889e47cf5755b987391edc12cde31027376609848a76
+size 51894
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_parameters.png
new file mode 100644
index 00000000000..c6ad6a62e95
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99db6e907d649aaebc69275664602e5999400b371dbf572487ff461b6864dce1
+size 47923
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_security.png
new file mode 100644
index 00000000000..75a8213da06
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbd7acb3317e635e08c5738ce98eb2209a08a893a2615c78ccb2f3b318bced70
+size 61931
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_sql.png
new file mode 100644
index 00000000000..e709af03d33
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/procedure_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:051e95c7c5a806782b38f9b5253ad78deed3d246e7b0c749ac46fbb532f1e38c
+size 92534
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/process_watcher_storage_manager.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/process_watcher_storage_manager.png
new file mode 100644
index 00000000000..7adf4139f8d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/process_watcher_storage_manager.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a6f4d779f40e1fe01b3673ef0c2e161f97f2fcbe041ea3e695dbfa745f413ba
+size 196407
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_autocomplete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_autocomplete.png
new file mode 100644
index 00000000000..dae58e10d26
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_autocomplete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ff058cc376046ad1a93c62a243b111a2c1437a8f5406d194f703dc65838cc8c
+size 78208
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_execute_section.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_execute_section.png
new file mode 100644
index 00000000000..873661b49a7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_execute_section.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ebf16f2f330d85131a1d761a7cb33d799a91b991a359614a48ac993dbb1b6f5
+size 132114
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_statistics.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_statistics.png
new file mode 100644
index 00000000000..0e2ea419423
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_statistics.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b10c8ea8841c8ba1fc35f7539dc5a05924fc4754182c061f4e8e149ad65d2fd
+size 265839
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_table.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_table.png
new file mode 100644
index 00000000000..e65ceb51698
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_explain_analyze_table.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d78fa172694789b5e055105913545099c29bb12d73581b50eb551cf987761459
+size 279631
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_data.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_data.png
new file mode 100644
index 00000000000..4f5978d6b5f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_data.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:991689f5d267b5665e1cd94f2f76af4e1550fa32c46ef0c7e8e4beb1b6889198
+size 132475
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_error.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_error.png
new file mode 100644
index 00000000000..6b1a481d8a4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_error.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc8c2d430501dc8beea730c3d4ea515f24c5224a24f89e7fe936ae0490c3823c
+size 86112
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_explain_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_explain_details.png
new file mode 100644
index 00000000000..cccd10a3b2b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_explain_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57ddaf635262b6af00d57f5925c878afb5e5f60688a4f7eff3ae1d0cd2188326
+size 155410
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_history.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_history.png
new file mode 100644
index 00000000000..f2b1e6dd1cc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_history.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2512ca5a67cdf3c85a472f4487e64df9c7ebf9323825233f34c11b8a1e6fa55c
+size 222921
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_messages.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_messages.png
new file mode 100644
index 00000000000..e6123b15f2e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_messages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3748914c01ba6fab0f4411787de69f58add1dc948e1d82f089f2778e2cd2186
+size 205783
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_notifications.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_notifications.png
new file mode 100755
index 00000000000..213fbc3ca77
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_output_notifications.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d536dd16c2a17fd7f95064d24f89d1bccedeb17c1451de8fce17dde0ce759ca
+size 53654
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_sql_editor.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_sql_editor.png
new file mode 100644
index 00000000000..2259b4644b2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_sql_editor.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffcddc606a5ef7ab6f2eeec405cbbe0a9ee76c0514aebf323fc94da12d4b00e6
+size 54579
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool.png
new file mode 100644
index 00000000000..bb351cdf423
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8cc3868cb4f395661deb60520979b452f8d9c8ed548f24c5d7c38c20f3b9a3f
+size 158824
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status.png
new file mode 100755
index 00000000000..b35131de2bc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffba4a8e27925d6a6b994fdc153596742195655510ac7980ee14804beb8c4d23
+size 85539
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status_error.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status_error.png
new file mode 100755
index 00000000000..e5aeaefb026
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_connection_status_error.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05719c59788bd4e3c2afc424d9033716ef6feb67dadfc7717bc5231b9b65b0b7
+size 10529
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_editable_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_editable_columns.png
new file mode 100644
index 00000000000..3545e898dce
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_editable_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:954840261456cbb5288f55f47481f1656340b80202d1433bf0aa17df93617b61
+size 104849
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_all.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_all.png
new file mode 100644
index 00000000000..74edf29373a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_all.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ff0033a2666b639b603c70412d933865113dcfc51717391ca05101c24427c5b
+size 124888
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_confirmation.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_confirmation.png
new file mode 100644
index 00000000000..b2ccbc7270c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_confirmation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:955aaee0052a8114cef105c4b2a74a9a39ef0bd0d7d3a1a426e59a322888ece4
+size 127783
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_row.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_row.png
new file mode 100644
index 00000000000..3ec14f31abf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_clear_row.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae42279356abbbedfafbd459f7777a86cd9e6e032528ad2ece29960e9380d745
+size 120902
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_execution.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_execution.png
new file mode 100644
index 00000000000..e8fbb47c284
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_macros_execution.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2e1040e2215973ae718d7406fb529fc2240c45328e045b2357b7c8a8b801344
+size 100552
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros.png
new file mode 100644
index 00000000000..b2db39fce53
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99b0d83d96fbb32e320f9313556b1dfba14f9af59ecfe806860bc3a050b8ae90
+size 81858
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros_dialog.png
new file mode 100644
index 00000000000..286a013d616
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_manage_macros_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67916ab6b25d77ca4163c52a78febbee6db96c18917803f733ddeef18f87d5bd
+size 120843
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_message.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_message.png
new file mode 100644
index 00000000000..344d84baf7b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_tool_message.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03cd69621f5fdfd31a68f13d91a88e2352f6ce61da9bd4c8901baa23d9b0652f
+size 59950
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar.png
new file mode 100644
index 00000000000..1f95458d233
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c350ad8bd13be86821e4eca18456d6de22e73c0d078ce4d9e1581b93ca5135d9
+size 25402
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar_explain.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar_explain.png
new file mode 100644
index 00000000000..087bace5e25
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/query_toolbar_explain.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c6da165c454904f0c0ac60d2f31f2d5572c2d7d54103e7562ee28d8c8d247a2
+size 72007
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/recursive_union_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/recursive_union_icon.png
new file mode 100644
index 00000000000..b55996d91ec
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/recursive_union_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a77e689fe0191da13a86043bad2bf45f7041c4168e55e6c0e0ddd1df94223eb
+size 1128
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/refresh.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/refresh.png
new file mode 100644
index 00000000000..d0829bb5f3e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/refresh.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:736e55eb5c8303103020d2f13857e2609ba5156c9b31096223b8958a1c7a92f0
+size 6160
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_general.png
new file mode 100644
index 00000000000..dc433368d0e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09d76b2f6d79dba6d3ea87876fd04aeee3b550ee440840314e7818849c8f6e41
+size 64437
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_sql.png
new file mode 100644
index 00000000000..fea2ab7fc6d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/resource_group_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a560fee9508b24103e70d40f64d2a272a94b8829cd322173b678b8f10d9f1b0a
+size 92328
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_disable.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_disable.png
new file mode 100644
index 00000000000..540bc5e0b41
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_disable.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9162003b4da7718ac9630d820e4c988b7dcb349c54c8e446da03ddbc4b1693b
+size 51253
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_do_not_save.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_do_not_save.png
new file mode 100644
index 00000000000..900ab9c7fc3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_do_not_save.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3df1127d9fdca7b7974637116deeddb4993824629c45a5842bccd545be335753
+size 53811
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_general.png
new file mode 100644
index 00000000000..af63515ea3c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c83812e1d9cc97e21f1834706fdfedf75c5c1dd0c11544ffef6b5053eb21f22
+size 66257
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_messages.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_messages.png
new file mode 100644
index 00000000000..1fc961a4fc2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_messages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58c4219eadbb93618f9bdeee112b8e3f78f3e6ca4b84e4ba38538a739a79e6f8
+size 72190
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_miscellaneous.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_miscellaneous.png
new file mode 100644
index 00000000000..f465d6ce50e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_miscellaneous.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d3156063b099ccf7c04b211da1ce5cbea71f0f2fb7500f7dcf6d6c3c4e5b74
+size 68825
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_objects.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_objects.png
new file mode 100644
index 00000000000..8d8a52a07e0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_objects.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fab390d142d7fdd69f1a4f1847d3f0b636a3b32ae88aef347b65a84991bed6f7
+size 47426
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_process_watcher.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_process_watcher.png
new file mode 100644
index 00000000000..0d15a2e6e2c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_process_watcher.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f3abc91e8dafd8fde229bf26b498248c3545c866d95170d19b2ba1290ad713d
+size 133486
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_queries.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_queries.png
new file mode 100644
index 00000000000..88f79d5adf2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_queries.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c628002c26116ea0e6841e6fed3cfec302bb3830c0f53e2ade45c520c15d0b3
+size 65267
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_sections.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_sections.png
new file mode 100644
index 00000000000..d1390f4704f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/restore_sections.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4209f1f2bdb8b9981bfeaffa1e3f7adaaa11250643900456a0cc1ef15f7638c9
+size 53262
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/result_set_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/result_set_icon.png
new file mode 100644
index 00000000000..e3836522d29
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/result_set_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f594e2903d5ce40b69d07367cce6cbc5d269518bb7d0ef36da88442c4054d29
+size 1165
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_commands_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_commands_tab.png
new file mode 100644
index 00000000000..46d01424bf8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_commands_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53079b7013a1cf2213b69ebaf6125cce29f0a6ab2542d2b72c307b8d33f945c
+size 291520
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_general_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_general_tab.png
new file mode 100644
index 00000000000..a554470b4a6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_general_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ebdd856844a560b9c6cc7df3962fd452d548607f6923a0a85304d9a309ace4b8
+size 72395
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_sql_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_sql_tab.png
new file mode 100644
index 00000000000..1231c8db209
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rls_policy_sql_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:915cadd0d03c881a353afc966d4b2693344cc26376f179472265f498d4958634
+size 81266
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_definition.png
new file mode 100644
index 00000000000..0277ee33515
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f05bba77d0fe44855b4ddfa2e9c45410299b079b6b960e8e4311ca9c76eda2d
+size 55189
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_dialog_membership.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_dialog_membership.png
new file mode 100644
index 00000000000..b863d34009c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_dialog_membership.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc7731696ccabdfd0ad9a9d3cc3e66686ffd376a5dc530375414a25252773efb
+size 84983
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_general.png
new file mode 100755
index 00000000000..f9ccfd958d1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c17c83cf6713bae0f6e6685e2410608a933356b0147b96104cd8d42f96ee96e
+size 47621
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_membership.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_membership.png
new file mode 100755
index 00000000000..d262fdba588
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_membership.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:396338d3f2fa6192567bd3a377375fc48bcd4c6bc4ebf085e4e66835737d8a4d
+size 58363
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_parameters.png
new file mode 100644
index 00000000000..ef0da3cec39
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d75ad9e8824ebc04e0c3fca19613d5d33c00059fbe6147e2445ebb80333264a8
+size 47410
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_privileges.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_privileges.png
new file mode 100644
index 00000000000..345fc295767
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_privileges.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2184cbd416e6271519f9d6820221a4ee0dd9f2e77279d20c61326924219da223
+size 75312
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_security.png
new file mode 100644
index 00000000000..1486f47d305
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfc30c2f776c8d23e5028785ae566147b7796e9723fba37774731fd58baa9915
+size 50107
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/role_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_sql.png
new file mode 100755
index 00000000000..9fc9531e0dd
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/role_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f08a7791ad4612a9f1fe2361b69a51472fec9e526f08c191958167cee309726b
+size 72595
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_commands.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_commands.png
new file mode 100644
index 00000000000..83e20c0318b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_commands.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a45ae8d613a1e8ee2557615494f1787fccd209ba7b32d79d47dda718b2bf6520
+size 59082
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_condition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_condition.png
new file mode 100644
index 00000000000..97e972debff
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_condition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a41a3a1d482e38b788bc0d78f99db46233c6df24114be9d139ac5b5811e0eff
+size 46887
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_definition.png
new file mode 100644
index 00000000000..4d09086bb98
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:367801d38adf9c9ab81bf58b11f35f7625f0dfb8f08ba0dba129a966c9535f4b
+size 56319
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_general.png
new file mode 100644
index 00000000000..1bc40e0b371
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03b9119f0e662edf44a47017b88b74477dc8cf228091e9de24579d1cad2ff9f5
+size 56990
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_sql.png
new file mode 100644
index 00000000000..0ba296667d4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/rule_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:204558ec7f6fa93827a44a9c6be4ebf5704c5a6f73ac59f560d476efceefc12a
+size 86113
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/save_capacity_manager_template.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/save_capacity_manager_template.png
new file mode 100755
index 00000000000..bbb5c5fe1a3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/save_capacity_manager_template.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:812b51ec259bdd60ffb56f717029d910d3217524e42350eccdd02a46179de7bc
+size 37503
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_default_privileges.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_default_privileges.png
new file mode 100644
index 00000000000..f7d4262eba9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_default_privileges.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee84b31b5e0d24ff5fc0f2bd2764bc300fb2b19027f14c33a64cf8d0851909f7
+size 142129
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_DDL_comparison.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_DDL_comparison.png
new file mode 100755
index 00000000000..c0aee5d0716
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_DDL_comparison.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:106583822b5c7da74ac3d162c5e0e77f8a5934cdd93f0c211db2c71b84dc59c4
+size 254644
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_compare_button.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_compare_button.png
new file mode 100755
index 00000000000..a8556001d26
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_compare_button.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b56a0885d840c64044e31053f0edd1d06799d001aa70863403b0b74911ecbad7
+size 66441
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_comparison_results.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_comparison_results.png
new file mode 100755
index 00000000000..c590d6bb3ae
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_comparison_results.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f64f2de4db2c93c9bde78653bd0729550e00207400a125b7d512141c12cbd500
+size 150900
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_dialog.png
new file mode 100755
index 00000000000..9365dae2441
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2359faaf833c330fedfacb024b0ae29340f574a931f846c050268308c9a0a981
+size 255329
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_filter_option.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_filter_option.png
new file mode 100755
index 00000000000..1ece30cefdf
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_filter_option.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddc51ee90a86101ccdefd7d61b021f88767da471e89e5ca98260571105ecd7cc
+size 147446
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script.png
new file mode 100755
index 00000000000..c3638420a90
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3afb7d2059ad4858b3031da5d2980a7c03c8377160d3ffc1900080699db2
+size 257990
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script_query_editor.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script_query_editor.png
new file mode 100755
index 00000000000..41e448775f4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_diff_generate_script_query_editor.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfb0658936c5b9794a6e3dde6ac17a1b7981b3d0799294cf2eba3f4e1d6302f3
+size 155324
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_general.png
new file mode 100644
index 00000000000..26adc2ab0c0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2960e0f36413bc60dce9639d5660f97461a1eb2d650cd3c61f479da7555d2c9
+size 58280
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_security.png
new file mode 100644
index 00000000000..8d2abb42499
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cefd7427e3889a9496371845df1bce6e5dd259d1f1261cbf39fac62091921944
+size 103708
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_sql.png
new file mode 100644
index 00000000000..9474509db77
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/schema_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:702e10e3f9e4c1c29e3ffa450b1da684a695d435013af4610849252356c04548
+size 95502
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/search_objects.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/search_objects.png
new file mode 100644
index 00000000000..5c64a4f54b8
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/search_objects.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:315f49e396417401d983f23d8bd764d97483f20b745ca88451aeff760f602275
+size 299975
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/seek_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/seek_icon.png
new file mode 100644
index 00000000000..dff23ffa11b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/seek_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7658b23837dd0e71128784e2cca03b17d4b037c1841e4c15f4a00e8d0bd26a01
+size 1350
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/seq_scan_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/seq_scan_icon.png
new file mode 100644
index 00000000000..15999c86b01
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/seq_scan_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d40b8fb1e2d6adec00663225c67c4133c650e6972581bb4b8f9253e3ce5f55c
+size 903
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_definition.png
new file mode 100644
index 00000000000..8c9145786c3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:885b42c3dfd8e06cf9605072421a92a9c5af753d5b33b4e4fa4622f1a26722ee
+size 69587
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_general.png
new file mode 100644
index 00000000000..67ce197e67d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05dbe0e5ec7247fc9536a9dbe8a7e947a4f4044e41940a10795a43f8e979ec02
+size 69148
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_security.png
new file mode 100644
index 00000000000..020efd91703
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59e56a33c82b39def6e12c956e69a0d528d736efb42e66482b4d10b7573cec20
+size 108938
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_sql.png
new file mode 100644
index 00000000000..708b248ef05
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sequence_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:385c5ea5ee9a89260025824fc04ad1f6a08356cd90843836580d86b2f3171a5c
+size 104020
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/server_analysis.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_analysis.png
new file mode 100644
index 00000000000..9e51ee3eb4e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_analysis.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6e33bf49493cdbfad389c82c1f5a2e933668878efa9264173bd1aff1f551acb
+size 489504
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_dashboard.png
new file mode 100755
index 00000000000..0aa429d8a36
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61e2314bb1bd5a91fa296a0433aec72382983fe5a6e503c23a31750642b5bc50
+size 397169
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_filter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_filter.png
new file mode 100755
index 00000000000..dfce0cce66d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/server_log_analysis_filter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c11382e5f1ad292e4f5b5bfa1bfe47fd49f4de5d01997fa376c6d0bb56368a1c
+size 76249
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/session_activity_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/session_activity_analysis_dashboard.png
new file mode 100644
index 00000000000..6693a1e5e9e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/session_activity_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfc8960674d211d4e58229096e680d94f6aec9738183e19147524820872d6d61
+size 365119
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/session_waits_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/session_waits_dashboard.png
new file mode 100644
index 00000000000..11fc99287d7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/session_waits_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71993a1c9aa53c3695931ab3e154bf999d96d9f43697e7b2a8d9ba84ea74717d
+size 134583
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/set_operator_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/set_operator_icon.png
new file mode 100644
index 00000000000..7f119d618b5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/set_operator_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b53a10bf3cc743af1fb1abfe5c7d4c12fda1c83f9abd5d75acf72d32b3b6a2d
+size 1048
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sm_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sm_icon.png
new file mode 100644
index 00000000000..f60877f58de
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sm_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c68255a3a3a91f4c83139f8f5838f4efc2385deee326a168600b2bc197ef28e7
+size 5788
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sort_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sort_icon.png
new file mode 100644
index 00000000000..336a41d1c1f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sort_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b307a33a8f72fc94a8dc2232fad551e4a31538c8d9527a132e82822fc24888de
+size 1086
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace.png
new file mode 100755
index 00000000000..8450a7bc561
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a936dd0c390a1412b10f00e65726d035c0b1fbc6636e6b9b8c3c9a96469198d
+size 52160
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_executed.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_executed.png
new file mode 100755
index 00000000000..e2939eb6fcc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_executed.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46c2af2c97e298a5b97df3d44aff6897e83b8d7c38dd4422c9df17895452bcad
+size 203217
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_periodic_job.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_periodic_job.png
new file mode 100755
index 00000000000..7b222be0af0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_periodic_job.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d41258258054f0f3a592875a84a8388dd9322c45463a1de96fae77ecc13a88c
+size 96249
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_schedule.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_schedule.png
new file mode 100755
index 00000000000..341b4a0c51c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_create_new_trace_schedule.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7d64724e240287df971320d2e63023531864aa1273ad39d47e4c65d6493d410
+size 43141
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_delete_trace.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_delete_trace.png
new file mode 100755
index 00000000000..a37bc6a1339
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_delete_trace.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d83d91bf10d79ac4390169ca2656c55d3b8b07a3421a19b5a3f59b8f23eb7978
+size 39602
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_open_existing_trace.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_open_existing_trace.png
new file mode 100755
index 00000000000..0a45fa69076
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_open_existing_trace.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28d3332250f00070b6c4a1daad2486915450b48ab1c8c49777e493f696e0249c
+size 38688
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_scheduled_traces.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_scheduled_traces.png
new file mode 100755
index 00000000000..a6350693b08
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_scheduled_traces.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee3600c7d757edaf2246a54eaacaeb4d341eb464dc97d891c5c5433ebe1d1dc0
+size 61439
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_sql_profiler_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_sql_profiler_tab.png
new file mode 100644
index 00000000000..7beaff8d328
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_sql_profiler_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d89c0c4b4c5cb6439c96495633677a8ebb89fa95e1cd77b9532d44cc0e3cbf0
+size 173704
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_toolbar.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_toolbar.png
new file mode 100644
index 00000000000..e483dcbddd1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_toolbar.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db926e7bfe74aaf8bbc2bac8f9cb026bef20842b02c24790b48c799ac2125836
+size 11038
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_details.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_details.png
new file mode 100644
index 00000000000..a8c54f58b47
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_details.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ec5888538250207047bb7a1b6a63512015b4fd631103691da6c024e1c40413b
+size 101000
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_filter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_filter.png
new file mode 100644
index 00000000000..b32e218a442
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sp_trace_filter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a64aca39c508df7e72ecfb96a0a27a8222af6fe70f24eb2f7f6623f452fc0414
+size 46090
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/sqlprofiler_upgrade.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/sqlprofiler_upgrade.png
new file mode 100644
index 00000000000..2c8f0705a82
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/sqlprofiler_upgrade.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8542f1cf94cf152e32de14648a28d3d01eb4cb764d801514a50198b93189e5cc
+size 260142
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_analysis_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_analysis_dashboard.png
new file mode 100644
index 00000000000..e5d77e55db7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_analysis_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd88028a6f453ff5e4943e389fcb3a2b24c93e6c5b8482795ece53369b9232a4
+size 403086
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_manager.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_manager.png
new file mode 100644
index 00000000000..3e3a9c39fe9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/storage_manager.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0349d2b83381d4b9485d5e235bc2e3d2dc0547781f7d26ac9d1d2386b93a041
+size 121186
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_primary.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_primary.png
new file mode 100644
index 00000000000..95c006837c5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_primary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8779228d0cdf2fca5d4b42e9856c9d4512686a0a97a15f92fe99e49fe105271
+size 131418
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_replica.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_replica.png
new file mode 100644
index 00000000000..e726ccec08c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/str_replication_dashboard_replica.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3d830236fb9a38e680620886093edd58c127c3ac2898bf1af3788760fadeaf8
+size 143984
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/subplan_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/subplan_icon.png
new file mode 100644
index 00000000000..1464ddc277d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/subplan_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8fa5b8ac014a50bd07ab0fadeadbf9736d3b293143ed0ff8d90fef2d12574c8
+size 1335
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_general.png
new file mode 100644
index 00000000000..03460e34b22
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66570664f9a9027228efcdb29d09173748373626bf0258096cd9f7984a5b4b29
+size 56757
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_sql.png
new file mode 100644
index 00000000000..5ddf351f77e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/synonym_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90d10d641c279a244de05c624d746eb917ebf69077a5bf550e43b847f2eda055
+size 59453
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_agents.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_agents.png
new file mode 100755
index 00000000000..4b9aeb37401
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_agents.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce3e74c83882faccefd34a81bf35d75bed4a959074ef84a91d53f49de587b7aa
+size 219091
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_server_directory.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_server_directory.png
new file mode 100755
index 00000000000..65cb74d9eb3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_server_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fff2bfbbd0478a872a134154d22774c9edfa442c0c3cdb243e5f71be81b7057
+size 197602
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_summary_and_summary.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_summary_and_summary.png
new file mode 100755
index 00000000000..4f13ec1830f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_configuration_report_pem_summary_and_summary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68e93a525b157647f8618765b9c3a735fd5407bca04d36752d4c41dcf4aa48d5
+size 129751
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/system_waits_dashboard.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_waits_dashboard.png
new file mode 100644
index 00000000000..3f7c321ed26
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/system_waits_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0b81f7be162fecafb4717d4b9e7ca153da74baff44dfdea51c94c21dc134f1d9
+size 129196
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_advanced.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_advanced.png
new file mode 100644
index 00000000000..8780e638703
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_advanced.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c31b6207e76c0f11d8ce4701e4af2f780e73735b82a0c99bf3fda006a154c896
+size 118760
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_definition.png
new file mode 100644
index 00000000000..96d1fc81bad
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65b70a16ec5d704ff74bf14e777452a98e141388ef9e2dcdc27511925b4119d8
+size 75677
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_general.png
new file mode 100644
index 00000000000..e062d6e1407
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_check_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:662366526b697b70213270338c322803fec472065d1ad2b79cc4c46f9c6aa7ff
+size 69526
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_columns.png
new file mode 100644
index 00000000000..303d8c9616e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a10e9b114b33c66b3c94bc10b3219c1cbaf6f9338d3e10be58394f302a368fa
+size 121734
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_columns.png
new file mode 100644
index 00000000000..9efe95b93b3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b6d546a0fc28ad10d27d71310a6721220810851fbbdba99329b41e8c6351ab3
+size 99572
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_definition.png
new file mode 100644
index 00000000000..04599253258
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64626973e2b5ba03d83cd2365b89a43e551708295472a9688d797128ae0492b1
+size 88645
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_general.png
new file mode 100644
index 00000000000..82939613564
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_exclusion_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:953ce03293abf3295bd02cf73103fc68c561400170aae329e5c6dea32ab6080c
+size 71893
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_action.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_action.png
new file mode 100644
index 00000000000..f6ab76fff81
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_action.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bffba9a12bb699c2a43593ae23e32b760e36627d0b3ea9e63acad63c20dab6bd
+size 74292
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_columns.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_columns.png
new file mode 100644
index 00000000000..66b6d6521a6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_columns.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3cb637751e4dee7cb662702999a7796b63cc89fa7ff793a55a133d139b19c27
+size 101461
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_definition.png
new file mode 100644
index 00000000000..c3839e452ad
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf27af11c9123d74b5cb1c66c1810c932509ef80e724ebd2396d6d22828ffa3c
+size 85064
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_general.png
new file mode 100644
index 00000000000..f590371feaa
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_foreign_key_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5548c2db7f7b0a4467fce98516b013a30d1541f8eb4d990f700d0817741b85c1
+size 73506
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_general.png
new file mode 100755
index 00000000000..82e50d9dc25
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea4494fbe5b713cb088f70c62165dedd15e8d5520a1139b96803e7b46eaede1e
+size 63791
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_parameter.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_parameter.png
new file mode 100644
index 00000000000..e40e96c95b7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_parameter.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ee096b7c80048e8381b8893b7bd34d7f82acdb5c27620dd7195c60e4d942c8a
+size 130177
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition.png
new file mode 100644
index 00000000000..a68d117e606
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a52c72d117ffbf9ceec7bc1ce79280e942bdc981c1eed7b8b63d96e08758ba0
+size 245323
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition_tree.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition_tree.png
new file mode 100644
index 00000000000..7cfd9b7035b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_partition_tree.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:084f5b05101dbc601dd82770c5aef2947456eac5ee35dfa76a473b6b9dc677de
+size 31952
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_constraints_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_constraints_general.png
new file mode 100644
index 00000000000..144cc8f9359
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_constraints_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0afa9c55b9966e3341fa85f563b0773d61478e2d546fd6df8f71d32028f5b97c
+size 69137
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_key_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_key_definition.png
new file mode 100644
index 00000000000..a1f1cc322c6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_primary_key_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3cdda4a0e6ede231fde57607050ced3c69d7a30d732ac638e7340265e3596d0
+size 92608
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_security.png
new file mode 100644
index 00000000000..ec826df4152
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e1e8ae655486402050eb66492d25f18fa96b9b7d5a3b892be69d77769a878cf
+size 58663
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_sql.png
new file mode 100644
index 00000000000..00b1e9a756c
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:558fd4cb3b59a3990af3956bcee0e34bc376f1184d67db47219d41bec32a2f98
+size 164478
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_definition.png
new file mode 100644
index 00000000000..dafd29b7c75
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8a6a5cbb9fe38c7e35a96c057235b7bee89524ee1e626e16845b2b14cbfd75e
+size 94623
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_general.png
new file mode 100644
index 00000000000..b935bbeba74
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/table_unique_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff2f507dc1787d18b1057dc5ae1eb57256dd0fe92761abe29cd61bdec4cbb88f
+size 72139
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_definition.png
new file mode 100644
index 00000000000..84ba8e23ace
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7693fbf3da086dc7c0c6586744091195479b3aa5f8c12569796f66d9eafd463
+size 53181
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_general.png
new file mode 100644
index 00000000000..38714fefe75
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9cba9739bdc6aa077058ffb76f3df140681da8435682b2c596060ba5f73f1f9b
+size 64607
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_parameters.png
new file mode 100644
index 00000000000..f5eb9118b21
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f100109c9a20665cc1a7bd25e145e109b926204248cc3b1be9ac469a261141e
+size 58369
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_security.png
new file mode 100644
index 00000000000..158c19ca31a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16a070252570a19616ada8d68d418c312918bec953d75616d017d79ec6a86d58
+size 67837
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_sql.png
new file mode 100644
index 00000000000..3d1c19c2300
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tablespace_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b55f2fcf132c44b7ccfa312d33df71a8ca29f2df8c94883c0674b3e21d05620
+size 100012
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tableview.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tableview.png
new file mode 100644
index 00000000000..d1fd1510062
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tableview.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c693c5bad17a07ebdcf78b26f397911b8430568afc3d14474f6b3c27cfff49d
+size 5168
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/title_edb_postgress_image.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/title_edb_postgress_image.png
new file mode 100755
index 00000000000..6a691ee8e28
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/title_edb_postgress_image.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3d3462fce07c6bc0ff7f6548da748be96a3e9796878bd0378e43cd9f544536b
+size 192288
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_code.png
new file mode 100644
index 00000000000..3be1abca854
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da3d021afc195b38c2341815f8dd6fe07d52e1d24cfff1d1837f675578a1fbd3
+size 44715
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition.png
new file mode 100644
index 00000000000..dfa7a564a7b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22a21ecbcb9b97c55f8913a78392e6e542b54995443c4ee0241cce47f3066953
+size 84707
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition_enabled.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition_enabled.png
new file mode 100644
index 00000000000..2caf45aa55e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_definition_enabled.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5360743df33cc7a16dd961d06e9df30840d1287139e504783fd0f3d5a4cdabf
+size 97662
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_events.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_events.png
new file mode 100644
index 00000000000..7a2e9dfc1f7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_events.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1318b5696eb900035372fef15320a502dc29bb4c0fd78e1dd088141b9ec3007
+size 85271
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_code.png
new file mode 100644
index 00000000000..c54c2929a57
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ae61bf988b786175653d5f5416217fe15cc88d4a9121415c748d9acaaa13635
+size 55076
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_definition.png
new file mode 100644
index 00000000000..479391e01e4
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ab7429e28bc6e3ada6d9dd990af603c8e346288b1f4baa697142c33317b1298
+size 60840
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_general.png
new file mode 100644
index 00000000000..d8660a210fb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b98d90ccc9cb080e64fb3feb5a88ad42804c94e8a161f72ad6e47c1974b6929b
+size 74992
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_options.png
new file mode 100644
index 00000000000..037511a8ead
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f0c92d6529af9bd98cf61efa63b31e85a35bfd3d68a4155922e7f017931c099
+size 98364
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_parameters.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_parameters.png
new file mode 100644
index 00000000000..c1eaba30c59
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_parameters.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4df92a366057e25481e4bcb4e6fb695cd58d00bbc10492da6edcbe14ec1d816
+size 63701
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_security.png
new file mode 100644
index 00000000000..1669a2213d2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03cc78bf2051e2f31900af472f16128109ba2cb03e1b6b31fa40968c8f835415
+size 74833
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_sql.png
new file mode 100644
index 00000000000..7091558a422
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_function_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5864e9a542af2b5b6c2f394aac33e03a47d7a84fa1eb8d2be38716c169651f12
+size 121090
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_general.png
new file mode 100644
index 00000000000..8654c687d14
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a0187bce04af8cbf9ec169c4358243c2c06ba20a891e2db3b30f655f1df8f42
+size 54615
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_sql.png
new file mode 100644
index 00000000000..ff238560be2
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/trigger_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c70273fec4a8fd8a01efd0ab0a67604d48492d283fdd8c4f0ec6547fc10c0e7
+size 89273
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_apply_changes.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_apply_changes.png
new file mode 100755
index 00000000000..587cb9aec5b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_apply_changes.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d16234ff35f1b9bb28100852e6cbdfe6e2c08569fb7c5e168165cad405c4362c
+size 83566
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_changes_sum.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_changes_sum.png
new file mode 100755
index 00000000000..e6c41845e29
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_changes_sum.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3e52ad00378169239c306477306195c66bb3f8274c5289dd44870c168961f7b
+size 91950
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_configuration.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_configuration.png
new file mode 100755
index 00000000000..34228ad42d6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_configuration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d969b5f3b8e2840559b70b89f6f3b2e51a5aa07301d725124ea2cb3e54d1e5d
+size 85749
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_confirm_chg.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_confirm_chg.png
new file mode 100755
index 00000000000..ca96967b95e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_confirm_chg.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c066930f24ab492c149f10d0cdf62439b3cc7aaf0c1cb612f50f812c0f30f430
+size 192598
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_generate_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_generate_report.png
new file mode 100755
index 00000000000..d259c5ce92a
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_generate_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03b6d9717b8a6519dc838f333cc5dab064bff95616eda901e99ee878a3082bbf
+size 83856
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_report.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_report.png
new file mode 100755
index 00000000000..aaf6f9707bc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_report.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b875e657ac0042444b3a8c00f95e99eeca4b7b4628e10f36c9d81857cb4cfc7
+size 128008
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_server_sel.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_server_sel.png
new file mode 100755
index 00000000000..5d509fcdda5
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_server_sel.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2684b3fbc0ca356bdbd4f9d4967a33c56b4ee701d1305392a44727808ee061d7
+size 79814
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_welcome.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_welcome.png
new file mode 100755
index 00000000000..cc960dafc01
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuning_wiz_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce5dd00cb3912fae71aa895f14cdd20adb9937a1e8eb7e78f98c931fe506de13
+size 80616
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/tuple_id_scan_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuple_id_scan_icon.png
new file mode 100644
index 00000000000..96e6643ad37
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/tuple_id_scan_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfc27cd173fe5b02022c769edb4c1dc99f44c86a55c76943f9544ae49dfc3b33
+size 992
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_composite.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_composite.png
new file mode 100644
index 00000000000..232ad6ea583
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_composite.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:353a0f3b55c073be87013107e21fc2c1a0611208372383f377194cfb2da1d248
+size 78493
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_enumeration.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_enumeration.png
new file mode 100644
index 00000000000..7ff1c19b236
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_enumeration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa3d782a604abc40d90ad30e2895e3179ef9f956364f88bfd3d5ff2a91e31849
+size 66503
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_external.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_external.png
new file mode 100644
index 00000000000..7fba8ecb51e
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_external.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:462988b3ea7c909d57787f0e9a2cd5c416649d5975e5d3183f90f91297004b29
+size 77207
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_general.png
new file mode 100644
index 00000000000..2d1d8c650bb
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0a3a62cc15c2770d361d6500450aa212b1a815f5eb0648e60721ae9ee0740eb
+size 68796
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_range.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_range.png
new file mode 100644
index 00000000000..885ccf93d41
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_range.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b19dd445dfc8e04fbfdaa5e150035b855d96892f3553de3e679a15c56dc79ab3
+size 89741
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_security.png
new file mode 100644
index 00000000000..b55d1c73521
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9fb6d51ffeda68397c276088cf19b13fedae17b84c53d127194011f381e6bda
+size 85355
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_shell.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_shell.png
new file mode 100644
index 00000000000..eaa4b105146
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_shell.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ce5b0c0f27bcd42f2389ddf0c9ed32c53be25ef88badf61e453dd553b733887
+size 50396
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/type_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_sql.png
new file mode 100644
index 00000000000..b4e1c1dbc2d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/type_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8625659b098a52e622ee32787bc144e934fde1d18598fb498e2ebdd416b4589e
+size 90905
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_definition.png
new file mode 100644
index 00000000000..0aa75155f26
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:643124ad55b7be2ca433dc2a62af543e8f7e9a0e3b4c2b937e7063387da7ec1f
+size 92307
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_general.png
new file mode 100644
index 00000000000..35c7a7821d0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3ccc758e51793d67570321fe566d80091c3d4cbe5e201d7067dd9fc5a4092ef
+size 55703
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_sql.png
new file mode 100644
index 00000000000..22d8f9e2fa9
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_constraint_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e24ad9e23ce24c0832b189c9859bdd1cce16a47124ea66cebc1c3cb4e9427688
+size 66297
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_icon.png
new file mode 100644
index 00000000000..88f15a6f358
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/unique_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdb82d15d8986697c3683c32188e1cc6f249aae05b9a122cef4cc8a4f1b2643a
+size 1228
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/uparrow.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/uparrow.png
new file mode 100644
index 00000000000..beca2f08b9f
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/uparrow.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ec31087576665fdbf71caabfb01f884f46d144af46e9737ffe5ad403a77f88a
+size 5042
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backendDB_permission_Windows_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backendDB_permission_Windows_security.png
new file mode 100755
index 00000000000..a7cc9454ccc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backendDB_permission_Windows_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e805c573e98f09b38afda4aae302d19c4518a4cb4e45cbd057d43df59cc6de75
+size 18225
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backingDB_permission_Windows_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backingDB_permission_Windows_security.png
new file mode 100755
index 00000000000..a7cc9454ccc
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/upgrade_backingDB_permission_Windows_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e805c573e98f09b38afda4aae302d19c4518a4cb4e45cbd057d43df59cc6de75
+size 18225
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/upload.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/upload.png
new file mode 100644
index 00000000000..d6c008554b7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/upload.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c7f626aa14249a2e59784601cbd7cae4c107b006116a35ed7d07fb31fd78834
+size 5717
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_general.png
new file mode 100644
index 00000000000..5106bf27419
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d4b00ba3be040d4b586e8aef1381fc0322d63904cde397fb1ec8d8285b9bab5
+size 50192
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_options.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_options.png
new file mode 100644
index 00000000000..3d296a0d784
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_options.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab1096928b7dab9004ecb81574eed28dce412cfe87e360d63499d991db0fa6d5
+size 62856
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_sql.png
new file mode 100644
index 00000000000..26c5f72b6a0
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/user_mapping_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5ef511d3b6b2f4e2ff0b7b0b53f80faef399c5e2ce5142574ef2ac7bbe35cac
+size 74761
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/view_code.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_code.png
new file mode 100644
index 00000000000..eb729521826
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_code.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa4885c7de1d329724b141532e9accb79db76bf8aa6d699d0729153cf6889898
+size 55472
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/view_definition.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_definition.png
new file mode 100644
index 00000000000..182e3b25c9d
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_definition.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96704905f40d1639fc2629522992b5371b1b8646e0e5f76b8e512059a538a99d
+size 54023
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/view_general.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_general.png
new file mode 100644
index 00000000000..b89433f4700
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_general.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:caed8064005ace5e3fb3af6c5c5789fefd805b47fd5cfc565b41c084f3ac2a27
+size 65185
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/view_security.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_security.png
new file mode 100644
index 00000000000..a0706aecd42
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_security.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ec23705d0fc55ab2db7e2e23d820691c805ee95d4b65685d59a1041ffc80f5c
+size 141182
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/view_sql.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_sql.png
new file mode 100644
index 00000000000..1fb0fe8d765
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/view_sql.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39e6170788dadadd72ea55fec60e955118b514c8ee1a9b0a9bbff4c0d0c1beb8
+size 105195
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/viewdata_filter_dialog.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/viewdata_filter_dialog.png
new file mode 100644
index 00000000000..33830a43874
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/viewdata_filter_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84267400179e66a911401944e2d91acbe221ef1353320844396b53f701bcdb5f
+size 60113
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add.png
new file mode 100644
index 00000000000..8df722c5ff6
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08fd771c1070fb619e1acf1ad22190b69ddf2c6a048fd6f32f0313d881552f32
+size 125003
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_headers.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_headers.png
new file mode 100644
index 00000000000..b8501c8ebc3
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_headers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a9f3b98818f8a1859b236e8f8adf6ed68265e8f06b87ce95afa84c937c6bcf5
+size 72893
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_notification.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_notification.png
new file mode 100644
index 00000000000..9b818359114
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_notification.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:937b312917d83a9017b470d8072f506d7c8282f1ff86b1828f416eaa84d28d66
+size 109010
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_payload.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_payload.png
new file mode 100644
index 00000000000..d7f4bee4972
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_add_payload.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b8ccec9f083cc2d485c67fb44a6990cf695aacd0bb1981af64151aa22f5b30f
+size 162038
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_delete.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_delete.png
new file mode 100644
index 00000000000..00068fc5253
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_delete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be14be8aae549dc7f49f4afc170679b6a3c649674023513a99e4e37c28ca4c20
+size 58675
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config.png
new file mode 100644
index 00000000000..5dc58bd3645
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88b5452907361555d8a183cdc133b5d127a85d08179b7cfee00c9545e8078c4a
+size 82903
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config_windows.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config_windows.png
new file mode 100644
index 00000000000..9b18bdc7ff7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhook_ssl_config_windows.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4153987c9f3eea4c339827288e5c4d0c0bc9c148836cb0fea72f74204facf93d
+size 70814
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/webhooks_tab.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhooks_tab.png
new file mode 100644
index 00000000000..d61236a4a16
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/webhooks_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cba31a2102cb3c9a98348318334e82acb80e5a03e1af5bf2f7a3cd19130c3054
+size 80046
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/images/window_aggregate_icon.png b/product_docs/docs/pem/8.0.1/pem_online_help/images/window_aggregate_icon.png
new file mode 100644
index 00000000000..aa5354dcc67
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/images/window_aggregate_icon.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7cf3cb6c2c92c9db773b76cea4c922c5ceead0dfd6f43c020cb215aedae3677d
+size 1085
diff --git a/product_docs/docs/pem/8.0.1/pem_online_help/index.mdx b/product_docs/docs/pem/8.0.1/pem_online_help/index.mdx
new file mode 100644
index 00000000000..c95c7569a62
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_online_help/index.mdx
@@ -0,0 +1,19 @@
+---
+title: "Postgres Enterprise Manager"
+---
+
+
+
+Welcome to Postgres Enterprise Manager (PEM). Postgres Enterprise Manager (PEM) consists of components that provide the management and analytical functionality for your EDB Postgres Advanced Server or PostgreSQL database. PEM is based on the Open Source pgAdmin IV project.
+
+pgAdmin is the leading Open Source management tool for Postgres, the world's most advanced Open Source database. pgAdmin IV is a comprehensive [database](http://www.postgresql.org) design and management system. pgAdmin 4 is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance and use of database objects.
+
+Contents:
+
+
+
+toc\_pem\_getting\_started toc\_pem\_agent toc\_pem\_client toc\_pem\_features toc\_pem\_management\_basics toc\_pem\_bart\_management toc\_pem\_sql\_profiler toc\_pem\_developer\_tools toc\_pem\_configure\_pgbouncer pgagent appendices release\_notes
+
+
+
+`Help` buttons in the lower-left corner of each dialog will open the online help for the dialog. You can also access help by navigating through the `Help` menu, and selecting the name of the resource that you wish to open.
diff --git a/product_docs/docs/pem/8.0.1/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx b/product_docs/docs/pem/8.0.1/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx
new file mode 100644
index 00000000000..cb9281d7931
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx
@@ -0,0 +1,18 @@
+---
+title: "The PEM Server - PEM Agent Connection Management Mechanism"
+---
+
+Each PEM Agent connects to the PEM database server using the SSL certificates for each individual user. For example, an Agent with `ID#1` connects to the PEM database server using the `agent1` user.
+
+
+
+Prior to PEM version 7.5, the following limitations disallowed the use of the connection pooler between the PEM Server and PEM Agent:
+
+- The PEM Agent uses an SSL Certificate to connect the PEM database server.
+- It uses an individual user identifier when connecting to the PEM database server.
+
+EDB has modified the PEM Agent to allow the agent to use a common database user (instead of the dedicated agent users) to connect the PEM database server.
+
+
+
+We recommend using PgBouncer versions equal to or later than version 1.9.0 as the connection pooler. Versions 1.9.0 or later support `cert` authentication; PEM Agents can connect to pgBouncer using SSL certificates.
diff --git a/product_docs/docs/pem/8.0.1/pem_pgbouncer/02_preparing_the_pem_database_server.mdx b/product_docs/docs/pem/8.0.1/pem_pgbouncer/02_preparing_the_pem_database_server.mdx
new file mode 100644
index 00000000000..fe90bbb67b7
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_pgbouncer/02_preparing_the_pem_database_server.mdx
@@ -0,0 +1,66 @@
+---
+title: "Preparing the PEM Database Server"
+---
+
+You must configure the PEM database server to work with PgBouncer; the following example demonstrates the steps required to configure the PEM database server.
+
+1. Create a dedicated user named `pgbouncer` on the PEM database server. For example:
+
+ ```text
+ pem=# CREATE USER pgbouncer PASSWORD 'ANY_PASSWORD' LOGIN;
+ CREATE ROLE
+ ```
+
+2. Create a user named `pem_admin1` (a non-super user) with `pem_admin` and `pem_agent_pool role` membership on the PEM database server. For example:
+
+ ```text
+ pem=# CREATE USER pem_admin1 PASSWORD 'ANY_PASSWORD' LOGIN
+ CREATEROLE;
+ CREATE ROLE
+ pem=# GRANT pem_admin, pem_agent_pool TO pem_admin1;
+ GRANT ROLE
+ ```
+
+3. Grant `CONNECT` privileges to the `pgbouncer` user on the `pem` database. For example:
+
+ ```text
+ pem=# GRANT CONNECT ON DATABASE pem TO pgbouncer ;GRANT USAGE ON
+ SCHEMA pem TO pgbouncer;
+ GRANT
+ ```
+
+4. Grant `USAGE` privileges to the `pgbouncer` user for the `pem` schema on the pem database. For example:
+
+ ```text
+ pem=# GRANT USAGE ON SCHEMA pem TO pgbouncer;
+ GRANT
+ ```
+
+5. Grant `EXECUTE` privileges to the `pgbouncer` user on the `pem.get_agent_pool_auth(text)` function in the `pem` database. For example:
+
+ ```text
+ pem=# GRANT EXECUTE ON FUNCTION pem.get_agent_pool_auth(text) TO
+ pgbouncer;
+ GRANT
+ ```
+
+6. Use the `pem.create_proxy_agent_user(varchar)` function to create a user named `pem_agent_user1` on the PEM database server. For example:
+
+ ```text
+ pem=# SELECT pem.create_proxy_agent_user('pem_agent_user1');
+ create_proxy_agent_user
+ -------------------------
+ (1 row)
+ ```
+
+ The function will create a user with the same name with a random password, and grant `pem_agent` and `pem_agent_pool` roles to the user. This allows pgBouncer to use a proxy user on behalf of the agent.
+
+7. Add the following entries to the start of the `pg_hba.conf` file of the PEM database server; this will allow pgBouncer user to connect to the pem database using the md5 authentication method. For example:
+
+ ```text
+ # Allow the PEM agent proxy user (used by
+ # pgbouncer) to connect the to PEM server using
+ # md5
+
+ local pem pgbouncer,pem_admin1 md5
+ ```
diff --git a/product_docs/docs/pem/8.0.1/pem_pgbouncer/03_configuring_pgBouncer.mdx b/product_docs/docs/pem/8.0.1/pem_pgbouncer/03_configuring_pgBouncer.mdx
new file mode 100644
index 00000000000..d1ef42c44ec
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_pgbouncer/03_configuring_pgBouncer.mdx
@@ -0,0 +1,120 @@
+---
+title: "Configuring PgBouncer"
+---
+
+You must configure PgBouncer to work with the PEM database server. In our example, we will run PgBouncer as the `enterprisedb` system user. The following steps outline the process of configuring pgBouncer (version >= 1.9).
+
+1. Open a terminal window and navigate into the pgBouncer directory.
+
+2. Change the owner of the `etc` directory for pgBouncer (where `pgbouncer.ini` resides) to `enterprisedb`, and change the directory permissions to `0700`. For example:
+
+ ```text
+ $ chown enterprisedb:enterprisedb /etc/edb/pgbouncer1.9
+ $ chmod 0700 /etc/edb/pgbouncer1.9
+ ```
+
+3. Change the contents of the `pgbouncer.ini` or `edb-pgbouncer.ini` file as follows:
+
+ ```text
+ [databases]
+ ;; Change the pool_size according to maximum connections allowed
+ ;; to the PEM database server as required.
+ ;; 'auth_user' will be used for authenticate the db user (proxy
+ ;; agent user in our case)
+
+ pem = port=5444 host=/tmp dbname=pem auth_user=pgbouncer
+ pool_size=80 pool_mode=transaction
+ * = port=5444 host=/tmp dbname=pem auth_user=pgbouncer
+ pool_size=10
+
+ [pgbouncer]
+ logfile = /var/log/edb/pgbouncer1.9/edb-pgbouncer-1.9.log
+ pidfile = /var/run/edb/pgbouncer1.9/edb-pgbouncer-1.9.pid
+ listen_addr = *
+ ;; Agent needs to use this port to connect the pem database now
+ listen_port = 6432
+ ;; Require to support for the SSL Certificate authentications
+ ;; for PEM Agents
+ client_tls_sslmode = require
+ ;; These are the root.crt, server.key, server.crt files present
+ ;; in the present under the data directory of the PEM database
+ ;; server, used by the PEM Agents for connections.
+ client_tls_ca_file = /var/lib/edb/as11/data/root.crt
+ client_tls_key_file = /var/lib/edb/as11/data/server.key
+ client_tls_cert_file = /var/lib/edb/as11/data/server.crt
+ ;; Use hba file for client connections
+ auth_type = hba
+ ;; Authentication file, Reference:
+ ;; https://pgbouncer.github.io/config.html#auth_file
+ auth_file = /etc/edb/pgbouncer1.9/userlist.txt
+ ;; HBA file
+ auth_hba_file = /etc/edb/pgbouncer1.9/hba_file
+ ;; Use pem.get_agent_pool_auth(TEXT) function to authenticate
+ ;; the db user (used as a proxy agent user).
+ auth_query = SELECT * FROM pem.get_agent_pool_auth($1)
+ ;; DB User for administration of the pgbouncer
+ admin_users = pem_admin1
+ ;; DB User for collecting the statistics of pgbouncer
+ stats_users = pem_admin1
+ server_reset_query = DISCARD ALL
+ ;; Change based on the number of agents installed/required
+ max_client_conn = 500
+ ;; Close server connection if its not been used in this time.
+ ;; Allows to clean unnecessary connections from pool after peak.
+ server_idle_timeout = 60
+ ```
+
+4. Use the following command to create and update the `/etc/edb/pgbouncer1.9/userlist.txt` authentication file for PgBouncer.
+
+ ```text
+ pem=# COPY (
+ SELECT 'pgbouncer'::TEXT, 'pgbouncer_password'
+ UNION ALL
+ SELECT 'pem_admin1'::TEXT, 'pem_admin1_password'
+ TO '/etc/edb/pgbouncer1.9/userlist.txt'
+ WITH (FORMAT CSV, DELIMITER ' ', FORCE_QUOTE *);
+
+ COPY 2
+ ```
+
+ !!! Note
+ A super user cannot invoke the PEM authentication query function `pem.get_proxy_auth(text)`. If the `pem_admin` user is a super user, you must add the password to the authentication file (`enterprisedb in the above example`).
+
+5. Create an HBA file `(/etc/edb/pgbouncer1.9/hba_file)` for PgBouncer that contains the following content:
+
+ ```text
+ # Use authentication method md5 for the local connections to
+ # connect pem database & pgbouncer (virtual) database.
+ local pgbouncer all md5
+ # Use authentication method md5 for the remote connections to
+ # connect to pgbouncer (virtual database) using enterprisedb
+ # user.
+
+ host pgbouncer,pem pem_admin1 0.0.0.0/0 md5
+ ```
+
+ ```text
+ # Use authentication method cert for the TCP/IP connections to
+ # connect the pem database using pem_agent_user1
+
+ hostssl pem pem_agent_user1 0.0.0.0/0 cert
+ ```
+
+6. Change the owner of the HBA file `(/etc/edb/pgbouncer1.9/hba_file)` to `enterprisedb`, and change the directory permissions to `0600`. For example:
+
+ ```text
+ $ chown enterprisedb:enterprisedb /etc/edb/pgbouncer1.9/hba_file
+ $ chmod 0600 /etc/edb/pgbouncer1.9/hba_file
+ ```
+
+7. Enable the PgBouncer service, and start the service. For example:
+
+ ```text
+ $ systemctl enable edb-pgbouncer-1.9
+
+ Created symlink from
+ /etc/systemd/system/multi-user.target.wants/edb-pgbouncer-1.9.service
+ to /usr/lib/systemd/system/edb-pgbouncer-1.9.service.
+
+ $ systemctl start edb-pgbouncer-1.9
+ ```
diff --git a/product_docs/docs/pem/8.0.1/pem_pgbouncer/04_configuring_the_pem_agent.mdx b/product_docs/docs/pem/8.0.1/pem_pgbouncer/04_configuring_the_pem_agent.mdx
new file mode 100644
index 00000000000..e7d2ee05a2b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_pgbouncer/04_configuring_the_pem_agent.mdx
@@ -0,0 +1,98 @@
+---
+title: "Configuring the PEM Agent"
+---
+
+You can use an RPM package to install a PEM Agent; for detailed installation information, please see the [PEM Linux Installation Guide](https://www.enterprisedb.com/docs/pem/latest/pem_inst_guide_linux/).
+
+Please note that PEM Agent which is responsible for sending SNMP notifications should not be configured with pgBouncer. For example, if the default PEM Agent installed along with PEM Server is used for SNMP notifications, then it should not be configured with pgBouncer.
+
+## Configuring a New PEM Agent (Installed via RPM)
+
+After using an RPM package to install the PEM agent, you will need to configure it to work it against a particular PEM database server. Use the following command:
+
+```text
+$ PGSSLMODE=require PEM_SERVER_PASSWORD=pem_admin1_password
+/usr/edb/pem/agent/bin/pemworker --register-agent --pem-server
+pem_agent_user1 --display-name "Agent Name"
+
+Postgres Enterprise Manager Agent registered successfully!
+```
+
+In above command, the `--pem-agent-user` argument instructs the agent to create an SSL certificate and key pair for the `pem_agent_user1` database user in `/root/.pem` directory.
+
+For example:
+
+```text
+/root/.pem/pem_agent_user1.crt
+
+/root/.pem/pem_agent_user1.key
+```
+
+The keys will be used by the PEM agent to connect to the PEM database server as `pem_agent_user1`. It will also create an agent configuration file named `/usr/edb/pem/agent/etc/agent.cfg.`
+
+You will find a line mentioning the agent-user to be used in the `agent.cfg` configuration file.
+
+For example:
+
+```text
+$ cat /usr/edb/pem/agent/etc/agent.cfg
+[PEM/agent]
+pem_host=172.16.254.22
+pem_port=6432
+agent_id=12
+agent_user=pem_agent_user1
+agent_ssl_key=/root/.pem/pem_agent_user1.key
+agent_ssl_crt=/root/.pem/pem_agent_user1.crt
+log_level=warning
+log_location=/var/log/pem/worker.log
+agent_log_location=/var/log/pem/agent.log
+long_wait=30
+short_wait=10
+alert_threads=0
+enable_smtp=false
+enable_snmp=false
+enable_webhook=false
+max_webhook_retries=3
+allow_server_restart=true
+allow_package_management=false
+allow_streaming_replication=false
+max_connections=0
+connect_timeout=-1
+connection_lifetime=0
+allow_batch_probes=false
+heartbeat_connection=false
+```
+
+## Configuring an Existing PEM Agent (Installed via RPM)
+
+If you are using an existing PEM agent, you can copy the SSL certificate and key files to the target machine, and reuse the files. You will need to modify the files, adding a new parameter and replacing some parameters in the existing `agent.cfg` file:
+
+Add a line for agent_user to be used for the agent. For example:
+
+```text
+agent_user=pem_agent_user1
+```
+
+Update the port to specify the pgBouncer port. For example:
+
+```text
+pem_port=6432
+```
+
+Update the certificate and key path locations. For example:
+
+```text
+agent_ssl_key=/root/.pem/pem_agent_user1.key
+agent_ssl_crt=/root/.pem/pem_agent_user1.crt
+```
+
+Please note: as an alternative, you can run the agent self registration script, but that will create a new agent id. If you do run the agent self-registration script, you must replace the new agent id with existing id, and disable the entry for the new agent id in the `pem.agent` table. For example:
+
+```text
+pem=# UPDATE pem.agent SET active = false WHERE id =
+
+the_pem_server_pem_agent_connection_management_mechanism preparing_the_pem_database_server configuring_pgBouncer configuring_the_pem_agent conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_security_best_practices/01_apache_httpd_security_configuration.mdx b/product_docs/docs/pem/8.0.1/pem_security_best_practices/01_apache_httpd_security_configuration.mdx
new file mode 100644
index 00000000000..863e22df384
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_security_best_practices/01_apache_httpd_security_configuration.mdx
@@ -0,0 +1,220 @@
+---
+title: "Apache HTTPD Security Configurations"
+---
+
+On a Windows system, Apache HTTPD is named PEM HTTPD, and the Apache httpd configuration file (`pme.conf`) is located in the `
+
+apache_httpd_security_configuration pem_application_configuration conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx b/product_docs/docs/pem/8.0.1/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx
new file mode 100644
index 00000000000..37fad844ec1
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx
@@ -0,0 +1,113 @@
+---
+title: "Installing the SQL Profiler Plugin"
+---
+
+You must install the plugin on each server on which you wish to use SQL Profiler. For example, if you have a host running PostgreSQL 9.6 and PostgreSQL 10, you must install two versions of the plugin, one for each server.
+
+Follow the installation steps listed below to install the plugin for PostgreSQL before continuing to the `Configuration` section. If you are using Advanced Server, you can skip installation and move ahead to the `Configuration` section.
+
+You can use the graphical installer to install any version of SQL Profiler on the Windows platform. On Linux, use an RPM package to install the SQL Profiler. For detailed information about configuring the EDB repository for your host platform, see the [PEM Linux Installation Guide](https://www.enterprisedb.com/docs/pem/latest/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux/).
+
+## Installing SQL Profiler on Windows
+
+To invoke the SQL Profiler graphical installer, assume `Administrator` privileges, navigate into the directory that contains the installer, and double-click the installer icon. The SQL Profiler installer welcomes you to the Setup Wizard.
+
+
+
+Click `Next` to continue to the `License Agreement`.
+
+
+
+Carefully review the license agreement before highlighting the appropriate radio button and accepting the agreement; click `Next` to continue to the `Installation Directory` dialog.
+
+
+
+Specify an alternate location for the installation directory, or accept the default location and click `Next` to continue.
+
+
+
+The wizard is now ready to install the SQL Profiler plugin. Click `Next` to continue.
+
+
+
+The SQL Profiler plugin installer displays progress bars as it copies files to your system.
+
+
+
+When the installation is complete, the SQL Profiler plugin is ready to be configured.
+
+## Using an RPM Package to Install SQL Profiler
+
+!!! Note
+ You may be required to add the `sslutils` package to your PostgreSQL database servers before installing SQL Profiler.
+
+If you have already configured the EDB repository on your system, you can use `yum` or `dnf` to install SQL Profiler:
+
+```text
+yum install postgresql
+
+installing_the_sql_profiler_plugin using_sql_profiler uninstalling_sql_profiler conclusion
+
+
diff --git a/product_docs/docs/pem/8.0.1/pem_upgrade/01_upgrading_pem_installation/01_upgrading_pem_installation_windows.mdx b/product_docs/docs/pem/8.0.1/pem_upgrade/01_upgrading_pem_installation/01_upgrading_pem_installation_windows.mdx
new file mode 100644
index 00000000000..257d2f7b02b
--- /dev/null
+++ b/product_docs/docs/pem/8.0.1/pem_upgrade/01_upgrading_pem_installation/01_upgrading_pem_installation_windows.mdx
@@ -0,0 +1,194 @@
+---
+title: "Upgrading a PEM Installation on Windows Host"
+---
+
+To upgrade PEM component software on Windows hosts, simply invoke a newer version of the PEM component installers in the following order:
+
+1. Invoke the PEM agent installer on each monitored node `except` the PEM Server host.
+2. Invoke the PEM Server installer; this installer will upgrade `both` the PEM Server and the PEM Agent that resides on the PEM Server host.
+
+During an installation, the component installer will automatically detect an existing installation, and perform an upgrade. After upgrading the PEM Agent and Server, you can upgrade SQL Profiler if required; this step is platform-specific.
+
+The following sections will walk you through the upgrade process on a Windows host, step-by-step.
+
+## Upgrading a PEM Agent on a Windows Host
+
+To upgrade a system that is currently monitored by a PEM agent to a more-recent PEM agent, simply download and invoke a newer version of the PEM Agent installer on the system that the agent is monitoring.
+
+You can invoke the installer by right-clicking on the downloaded installer's icon, and selecting `Run as Administrator`. The `PEM Agent Setup Wizard` opens, welcoming you.
+
+
+
+Read and accept the `License Agreement` before clicking `Next` to continue.
+
+
+
+The setup wizard will automatically detect an existing agent, and upgrade the installed version. Click `Next` to continue.
+
+
+
+The `pemAgent service account` dialog may prompt you for the password of the account under which the PEM Agent service runs.
+
+
+
+If prompted, provide the password, and click `Next` to continue.
+
+When the `Ready to Install` dialog informs you that the installation is about to begin, click `Next` to continue. It will upgrade your PEM Agent to the latest version.
+
+
+
+The setup wizard displays progress bars to inform you of each component that is being installed.
+
+The `PEM Agent Setup Wizard` will inform you when the installation completes. Click `Finish` to exit the wizard and close the window.
+
+
+
+After the installation completes, a window pops-up to restart the machine. Click `Yes` to restart the machine and the PEM Agent.
+
+
+
+## Upgrading the PEM Server on a Windows Host
+
+The PEM Server installer facilitates upgrading directly between major versions of the PEM Server; you can upgrade directly from version 5.0 to version 7.16 without first upgrading to version 6.0.
+
+You can invoke the installer by right-clicking on the downloaded installer's icon, and selecting `Run as Administrator`.
+
+
+
+The `PEM Server Setup Wizard` welcomes you, as shown in the image. Click `Next` to continue to the `License Agreement`.
+
+The `PEM Server setup wizard` will prompt you to accept the `License Agreement`. After reviewing the license agreement, check the radio button next to `I accept the agreement`, and click `Next` to continue to the `Existing installation dialog`.
+
+
+
+The wizard will check the PEM Server host for an existing PEM Server installation; if the wizard locates an installation, it will perform an upgrade. Click `Next` to continue.
+
+
+
+Before upgrading the PEM Server, the wizard will confirm that the requirements of the new PEM Server are present. If any supporting components are missing, or are a version that will not support the new PEM installation, the PEM installation wizard will inform you that it must upgrade the dependencies, and will invoke the required installers.
+
+
+
+When the installation wizards complete the dependency upgrades, then a window pops-up asking whether you want to restart the machine or not.
+
+
+
+Click on `No` to continue the upgrade process.
+
+The wizard then opens the `Database Server Installation Details` dialog, prompting you for connection credentials for the database superuser of the PEM backend database. Provide:
+
+- The name of the database superuser in the `User` field.
+- The password associated with the database superuser in the `Password` field.
+
+Click `Next` to continue.
+
+
+
+The `pemAgent service account` dialog may prompt you for the password of the account under which the PEM agent service runs.
+
+
+
+If prompted, provide the password, and click `Next` to continue.
+
+
+
+The `Ready to Install` dialog will inform you that the setup wizard is ready to perform the installation. Click `Next` to start the installation.
+
+During the installation, progress bars will keep you informed of the progress of the update.
+
+
+
+After upgrading the PEM Server (and the agent that resides on the same host as the PEM server) and configuring the web service, the PEM setup wizard notifies you of the port on which the service is listening. Use this port number when connecting to the PEM Server with the PEM client.
+
+
+
+Click `OK` to close the `Info` popup. The PEM server setup wizard informs you that the installation is complete.
+
+
+
+If the window pops-up asking to restart the machine, then click on `Yes` to restart the machine and hence the `httpd` service.
+
+If you have installed the PEM backend database server and PEM-HTTPD on different hosts, then you must run the PEM Server installer twice – once on each host. Extract the language pack installer, and install it on the host of PEM-HTTPD before invoking the PEM installer. Include the following keywords when invoking the installer to extract the language pack:
+
+`--extract-languagepack