Merge branch 'develop' into DOCS-1113-create-ai-accelerator-ga-documentation-section

Author: djw-m

advocacy_docs/edb-postgres-ai/cloud-service/index.mdx

@@ -3,7 +3,7 @@ title: EDB Postgres AI Cloud Service
 navTitle: Cloud Service
 description: An introduction to the EDB Postgres AI Cloud Service and its features.
 directoryDefaults:
-  displayBanner: "The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. Further updates will be provided as the removal progresses."
+  displayBanner: "Notice: EDB will no longer offer the  Hosted Cloud Service option for new customers. However, support will remain available for existing customers of the EDB Hosted plan. The associated documentation topics will soon be removed, and updates regarding the removal process will be shared as they become available. The 'Your Cloud Account' option will continue to be available."
 navigation:
 - getting_started
 - using_cluster

advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx

@@ -22,21 +22,21 @@ Using the retrieved subscription token, set an environmental variables (`EDB_SUB
 
 ```shell
 export EDB_SUBSCRIPTION_TOKEN=<your-repos-token>
-export EBD_SUBSCRIPTION_TYPE=<your-subscription-type>
+export EDB_SUBSCRIPTION_TYPE=<your-subscription-type>
 ```
 
 Depending on your operating system, run the following command to enable your system to enable package downloading from the EDB repositories:
 
 For RHEL-like or SLES:
 
 ```shell
-curl -1sSLf 'https://downloads.enterprisedb.com/$EDB_SUBSCRIPTION_TOKEN/$EDB_SUBSCRIPTION_TYPE/setup.rpm.sh' | sudo -E bash
+curl -1sSLf "https://downloads.enterprisedb.com/$EDB_SUBSCRIPTION_TOKEN/$EDB_SUBSCRIPTION_TYPE/setup.rpm.sh" | sudo -E bash
 ```
 
 For Debian or Ubuntu:
 
 ```shell
-curl -1sSLf 'https://downloads.enterprisedb.com/$EDB_SUBSCRIPTION_TOKEN/$EDB_SUBSCRIPTION_TYPE/setup.deb.sh' | sudo -E bash
+curl -1sSLf "https://downloads.enterprisedb.com/$EDB_SUBSCRIPTION_TOKEN/$EDB_SUBSCRIPTION_TYPE/setup.deb.sh" | sudo -E bash
 ```
 
 ## Install the beacon-agent package

advocacy_docs/edb-postgres-ai/console/using/projects/clusters.mdx

@@ -10,7 +10,7 @@ In the top right, is a **Create New** button that allows you to create a new clu
 
 ## Cluster actions
 
-To the right of the cluster's information is are a lock icon, a pen icon and an ellipsis menu button. The lock shows the credential information for the cluster, the pen icon takes you to the appropriate edit cluster page, and the ellipsis menu button which when selected provides the following options:
+To the right of the cluster's information are a lock icon, a pen icon and an ellipsis menu button. The lock shows the credential information for the cluster, the pen icon takes you to the appropriate edit cluster page, and the ellipsis menu button which when selected provides the following options:
 
 | Option                                       | Description                                      |
 |----------------------------------------------|--------------------------------------------------|

advocacy_docs/edb-postgres-ai/index.mdx

@@ -23,5 +23,5 @@ navigation:
 The home of all EDB Postgres® AI documentation.
 
 !!!note "Deprecation"
-    The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. Further updates will be provided as the removal progresses.
+   EDB will no longer offer the  Hosted Cloud Service option for new customers. However, support will remain available for existing customers of the EDB Hosted plan. The associated documentation topics will soon be removed, and updates regarding the removal process will be shared as they become available. The 'Your Cloud Account' option will continue to be available.
 

advocacy_docs/pg_extensions/pgvector/index.mdx

@@ -12,12 +12,10 @@ directoryDefaults:
 
 `pgvector` is an extension released as open source software under the PostgreSQL License. 
 
-`pgvector` provides vector similarity search capabilities and the ability to store embeddings for retrieval augmented generation.  
+`pgvector` provides vector-similarity search capabilities and the ability to store embeddings for retrieval-augmented generation.  
 
 For more information about `pgvector`, see:
 
 - [Installing pgvector](installing.mdx)
 - [Configuring pgvector](configuring.mdx)
 - [Using pgvector](using.mdx)
-
-

advocacy_docs/pg_extensions/pgvector/installing.mdx

@@ -64,8 +64,3 @@ For example, to install pgvector for EDB Postgres Advanced Server 15 on a RHEL 8
 ```shell
 sudo dnf -y install edb-as15-pgvector0
 ```
-
-
-
-
-

advocacy_docs/pg_extensions/pgvector/rel_notes/index.mdx

@@ -3,7 +3,7 @@ title: 'pgvector release notes'
 navTitle: "Release notes"
 indexCards: none
 ---
-The pgvector documentation describes the latest version of pgvector, including minor releases and patches. These release notes cover what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators in the content about the release that introduced the feature.
+The `pgvector` documentation describes the latest version of `pgvector`, including minor releases and patches. These release notes cover what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators in the content about the release that introduced the feature.
 
 |               Version               | Release Date |
 | ----------------------------------- | ------------ |

advocacy_docs/pg_extensions/pgvector/using.mdx

@@ -3,4 +3,4 @@ title: Using pgvector
 navTitle: Using
 ---
 
-For more information on using `pgvector`, see the [Getting Started](https://github.com/pgvector/pgvector?tab=readme-ov-file#getting-started) guide in the pgvector official documentation.
+For more information on using `pgvector`, see [Getting Started](https://github.com/pgvector/pgvector?tab=readme-ov-file#getting-started) in the `pgvector` official documentation.

advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx

@@ -0,0 +1,130 @@
+---
+title: Using Hosted Artifactory with EDB repositories
+navTitle: Hosted Artifactory
+description: How to use Hosted JFrog Artifactory with EDB repositories
+---
+
+To set up Hosted JFrog Artifactory with EDB repositories, you need to create remote repositories in Artifactory. This article shows how to use Hosted JFrog Artifactory with EDB repositories. The process is different for on-premises Artifactory.
+
+## Get the base URLs
+
+The process is requires a base URLs to access the EDB repositories.
+
+1. From your EDB account, [get your token](../../getting_started/with_cli/get_your_token).
+
+1. Make a note of your token, for our examples, the token will be `xyz123`.
+
+1. Select the repository you want to access, for example, `standard`. :
+
+1. Your base URL will is then formed as:
+
+    ```
+    https://downloads.enterprisedb.com/<token>/<repository>/
+    ```
+
+    For the `standard` with our token, the repository, the base URL will be:
+
+    ```
+    https://downloads.enterprisedb.com/xyz123/standard/
+    ```
+
+1. Append the appropriate path for the repository type. 
+   For example, for a Red Hat Enterprise Linux 9 on x86 architecture, append `rpm/el/9/x86_64/` and seperately append `rpm/el/9/noarch/` for the noarch packages, to create two base URLs. With our example, the base URLs will be:
+
+    ```
+    https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/
+    https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/noarch/
+    ```
+
+## Setup Artifactory remote repositories
+
+With your base URLs, you can now create the remote repositories in Artifactory.
+
+Use the Artifactory UI to create the 2 repositories (`x86_64` and `noarch`), one for each base URL. The `x86_64` repository will contain the `rpm` packages specifically for the `x86_64` architecture, and the `noarch` repository will contain the `rpm` packages which are for any architecture.
+
+Starting with the `x86_64` base URL:
+
+1. Select **Create Repository** and choose **Remote**.
+1. Choose **rpm** as the repository type.
+1. Enter a unique name for the repository key, for example, `edb-x86_64`.
+1. Fill in the URL as `https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/`.
+1. Select **Create Remote Repository**.
+
+At this point, a prompt to setup the `yum` client configuration appears. This client configuration is the configuration you use on your local server or VM to access the configured EDB repositories via Artifactory.
+
+6.  On your local RHEL 9 server or VM create the yum repository file `/etc/yum.repos.d/artifactory-edb.repo`.
+    
+7.  Add the text generated by Artifactory to the `/etc/yum.repos.d/artifactory-edb.repo` file. The generated text should resemble:
+    
+    ```
+    [Artifactory]
+    name=Artifactory
+    baseurl=https://username%40domain:{artifactory_token}@username.jfrog.io/artifactory/edb-x86_64/<PATH_TO_REPODATA_FOLDER>
+    enabled=1
+    gpgcheck=0
+    ```
+    
+    Remove the `<PATH_TO_REPODATA_FOLDER>` from the baseurl. It's not needed.
+
+    You should also edit the `Artifactory` name to be more descriptive and unique as there are multiple repositories to add. For example, append `-edb-x86_64` to the name to give:
+
+    ```
+    [Artifactory-edb-x86_64]
+    name=Artifactory-edb-x86_64
+    baseurl=https://username%40domain:{artifactory_token}@username.jfrog.io/artifactory/edb-x86_64/
+    enabled=1
+    gpgcheck=0
+    ```
+
+    Save the file.
+    
+8.  Repeat the process, steps 1-7, to create an Artifactory remote repository for the `noarch` repository. When you generate the **yum** configuration text, add that text to the `/etc/yum.repos.d/artifactory-edb.repo` file previously created. The file should now contain:
+
+    ```
+    [Artifactory-edb-x86_64]
+    name=Artifactory-edb-x86_64
+    baseurl=username%40domain:{artifactry_token}@username.jfrog.io/artifactory/edb-x86_64/
+    enabled=1
+    gpgcheck=0
+    
+    [Artifactory-edb-noarch]
+    name=Artifactory-edb-noarch
+    baseurl=username%40domain:{artifactry_token}@username.jfrog.io/artifactory/edb-noarch/
+    enabled=1
+    gpgcheck=0
+    ```
+
+## Check the configuration works
+
+On the local Linux server where the `/etc/yum.repos.d/artifactory-edb.repo` file resides, check that the repositories configuration is correct by running the following command:
+
+
+```bash
+dnf repolist | grep -i Art
+```    
+
+The output returned should be:
+
+```
+Artifactory-edb-noarch                   Artifactory-edb-noarch
+Artifactory-edb-x86_64                   Artifactory-edb-x86_64
+```
+    
+As you can see the two repositories are now configured. 
+
+You can now check for a specific package, such as `postgresextended` in the Artifactory repository, using the `dnf list` command. The package name for this example is `edb-postgresextended15-server` which is EDB Postgres Extended 15. To ensure that you don't get false positives from other repositories,  disable all repositories using `--disable-repo=*` and then only enable the `Artifactory-` prefixed repositories using `--enablerepo=Artifactory-*`:
+
+```bash
+dnf list edb-postgresextended15-server --disablerepo=* --enablerepo=Artifactory-*
+```
+
+If configured and working correctly the output should resemble:
+
+```
+Updating Subscription Management repositories.
+Last metadata expiration check: 0:01:58 ago on Thu 04 Jul 2024 06:00:31 EDT.
+Available Packages
+edb-postgresextended15-server.x86_64                                                                                     15.7-2.el9                                                                                     Artifactory-edb-x86_64
+```    
+
+The EDB package `edb-postgresextended15-server` is now available to install from the Artifactory repository.

advocacy_docs/repos/working_with_repos/integrating/index.mdx

@@ -4,9 +4,13 @@ navTitle: Integrating
 description: How to integrate EDB repositories with configuration management tools
 ---
 
-Content coming soon:
+In this section, you will find information on how to integrate EDB repositories with configuration management tools.
+
+  * [Hosted JFrog Artifactory](artifactory)
+
+<br/>
+<br/>
+<br/>
+
 
-  * JFrog Artifactory
-  * Satellite
-  * Nexus
 

product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx

@@ -10,7 +10,7 @@ legacyRedirectsGenerated:
 
 <div id="monitoring_efm_cluster" class="registered_link"></div>
 
-You can use either the Failover Manager `efm cluster-status` command or the PEM Client interface to check the current status of a monitored node of a Failover Manager cluster.
+You can use either the Failover Manager `efm cluster-status` command or the PEM client interface to check the current status of a monitored node of a Failover Manager cluster.
 
 ## Reviewing the cluster status report
 
@@ -62,7 +62,7 @@ Standby     172.19.12.163       UP        192.168.225.190
 Primary     172.19.14.9         UP        192.168.225.190*
 ```
 
-The asterisk (\*) after the VIP address indicates that the address is available for connections. If a VIP address is not followed by an asterisk, the address was associated with the node in the properties file, but the address isn't currently in use.
+The asterisk (\*) after the VIP address indicates that the address is available for connections. If a VIP address isn't followed by an asterisk, the address was associated with the node in the properties file, but the address isn't currently in use.
 
 Failover Manager agents provide the information displayed in the Cluster Status section.
 
@@ -76,9 +76,10 @@ Standby priority host list:
 172.19.12.163 172.19.10.2
 ```
 
-The `Promote Status` section of the report includes information related to promotion in the cluster. The LSN information is used, along with the `Standby priority host list`, when choosing a standby to promote. If there is a mismatch in replay LSNs, Failover Manager will not allow a switchover (though the promotion of a standby is always allowed).
+The `Promote Status` section of the report includes information related to promotion in the cluster. When choosing a standby to promote, the LSN information is used, along with the `Standby priority host list`. If there's a mismatch in replay LSNs, Failover Manager doesn't allow a switchover. However, the promotion of a standby is always allowed.
+
+The LSN information is the result of a direct query from the node on which you're invoking the `cluster-status` command to each database in the cluster. The query also returns the transaction log location of each database. Because the queries to each database return at different times, the LSNs might not match even if streaming replication is working normally for the cluster. To get the latest view of replication, connect to the primary database, and execute SQL command `SELECT * FROM pg_stat_replication;`.
 
-The LSN information is the result of a direct query from the node on which you are invoking the `cluster-status` command to each database in the cluster. The query also returns the transaction log location of each database. Because the queries to each database return at different times, the LSNs might not match even if streaming replication is working normally for the cluster. To get the latest view of replication, connect to the primary database, and execute SQL command `SELECT * FROM pg_stat_replication;`.
 ```text
 Promote Status:
 
@@ -89,7 +90,7 @@ Standby  172.19.12.163   0/4000638          0/4000638
 Standby  172.19.10.2     0/4000638          0/4000638
 ```
 
-If a database is down or if the database was restarted, but the resume command was not yet invoked, the state of the agent that resides on that host is idle. If an agent is idle, the cluster status report includes a summary of the condition of the idle node. For example:
+If a database is down or if the database was restarted but the resume command wasn't yet invoked, the state of the agent that resides on that host is idle. If an agent is idle, the cluster status report includes a summary of the condition of the idle node. For example:
 
 ```text
 Agent Type  Address             DB        VIP
@@ -103,23 +104,23 @@ The cluster status process returns an exit code based on the state of the cluste
 
 -   An exit code of `0` indicates that all agents are running, and the databases on the primary and standby nodes are running and in sync.
 
--   A nonzero exit code indicates that there is a problem. The following problems can trigger a nonzero exit code:
+-   A nonzero exit code indicates a problem. The following problems can trigger a nonzero exit code:
 
-    A database is down, unknown, or has an idle agent.
+    - A database is down, unknown, or has an idle agent.
 
-    Failover Manager can't decrypt the provided database password.
+    - Failover Manager can't decrypt the provided database password.
 
-    There's a problem contacting the databases to get WAL locations.
+    - There's a problem contacting the databases to get WAL locations.
 
-    There's no primary agent.
+    - There's no primary agent.
 
-    There are no standby agents.
+    - There are no standby agents.
 
-    One or more standby nodes aren't in sync with the primary.
+    - One or more standby nodes aren't in sync with the primary.
 
 ## Monitoring streaming replication with Postgres Enterprise Manager
 
-If you use Postgres Enterprise Manager (PEM) to monitor your servers, you can configure the Streaming Replication Analysis dashboard (part of the PEM interface) to display the state of a primary or standby node that is part of a Streaming Replication scenario.
+If you use Postgres Enterprise Manager (PEM) to monitor your servers, you can configure the Streaming Replication Analysis dashboard (part of the PEM interface) to display the state of a primary or standby node that's part of a Streaming Replication scenario.
 
 ![The Streaming Replication dashboard (Primary node)](images/str_replication_dashboard_master.png)