diff --git a/product_docs/docs/bdr/3.7/camo_clients.mdx b/product_docs/docs/bdr/3.7/camo_clients.mdx index bccc628f9cd..c831143c122 100644 --- a/product_docs/docs/bdr/3.7/camo_clients.mdx +++ b/product_docs/docs/bdr/3.7/camo_clients.mdx @@ -1,8 +1,8 @@ --- -navTitle: 'Appendix D: CAMO Reference Clients' -title: 'Appendix D: CAMO Reference Client Implementations' +navTitle: 'Appendix C: CAMO Reference Clients' +title: 'Appendix C: CAMO Reference Client Implementations' originalFilePath: camo_clients.md --- - + diff --git a/product_docs/docs/bdr/3.7/credits.mdx b/product_docs/docs/bdr/3.7/credits.mdx deleted file mode 100644 index caddd0e8950..00000000000 --- a/product_docs/docs/bdr/3.7/credits.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -navTitle: Credits and License -title: Credits and Licence -originalFilePath: credits.md - ---- - -BDR3 has been designed, developed and tested by this team: - -- Petr Jelinek -- Craig Ringer -- Markus Wanner -- Pavan Deolasee -- Tomas Vondra -- Simon Riggs -- Nikhil Sontakke -- Pallavi Sontakke -- Amruta Deolasee -- Rahila Syed -- Ashutosh Bapat -- Abhijit Menon-Sen -- Florin Irion -- Oliver Riggs - -Copyright © 2018-2020 2ndQuadrant Ltd -Copyright © 2021 EnterpriseDB UK Ltd - -BDR3 is provided under EDB usage licenses. - -The reproduction of these documents is prohibited. diff --git a/product_docs/docs/bdr/3.7/index.mdx b/product_docs/docs/bdr/3.7/index.mdx index 08407366c52..10adfb19744 100644 --- a/product_docs/docs/bdr/3.7/index.mdx +++ b/product_docs/docs/bdr/3.7/index.mdx @@ -28,7 +28,6 @@ navigation: - functions - isolation_details - known-issues - - licenses - camo_clients title: BDR (Bi-Directional Replication) directoryDefaults: diff --git a/product_docs/docs/bdr/3.7/libraries.mdx b/product_docs/docs/bdr/3.7/libraries.mdx deleted file mode 100644 index 7c5ba472ce4..00000000000 --- a/product_docs/docs/bdr/3.7/libraries.mdx +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: 'Appendix D: Libraries' -originalFilePath: libraries.md - ---- - -In this section we list the libraries used by BDR3, with the -corresponding licenses. - -| Library | License | -| :------ | :--------------------------------- | -| LLVM | BSD (3-clause) | -| OpenSSL | SSLeay License AND OpenSSL License | -| Libpq | PostgreSQL License | - -## LLVM - -Copyright © 1994 The Regents of the University of California. All -rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. Neither the name of the University nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS \`\`AS IS'' -AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS -BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR -CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF -SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR -BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, -WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE -OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN -IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - -## OpenSSL - -==================================================================== - -Copyright © 1998-2004 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: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - -2. 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. - -3. 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. ( - -4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to - endorse or promote products derived from this software without - prior written permission. For written permission, please contact - openssl-coreopenssl.org. - -5. Products derived from this software may not be called "OpenSSL" - nor may "OpenSSL" appear in their names without prior written - permission of the OpenSSL Project. - -6. Redistributions of any form whatsoever must retain the following - acknowledgment: - "This product includes software developed by the OpenSSL Project - for use in the OpenSSL Toolkit ( - -THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT \`\`AS IS'' AND ANY -EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR -ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT -NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; -LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, -STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) -ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED -OF THE POSSIBILITY OF SUCH DAMAGE. - -==================================================================== - -This product includes cryptographic software written by Eric Young -(eaycryptsoft.com). This product includes software written by Tim -Hudson (tjhcryptsoft.com). - -## Original SSLeay Licence - -Copyright © 1995-1998 Eric Young (eaycryptsoft.com) -All rights reserved. - -This package is an SSL implementation written -by Eric Young (eaycryptsoft.com). -The implementation was written so as to conform with Netscapes SSL. - -This library is free for commercial and non-commercial use as long as -the following conditions are aheared to. The following conditions -apply to all code found in this distribution, be it the RC4, RSA, -lhash, DES, etc., code; not just the SSL code. The SSL documentation -included with this distribution is covered by the same copyright terms -except that the holder is Tim Hudson (tjhcryptsoft.com). - -Copyright remains Eric Young's, and as such any Copyright notices in -the code are not to be removed. -If this package is used in a product, Eric Young should be given attribution -as the author of the parts of the library used. -This can be in the form of a textual message at program startup or -in documentation (online or textual) provided with the package. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. All advertising materials mentioning features or use of this software - must display the following acknowledgement: - "This product includes cryptographic software written by - Eric Young (eaycryptsoft.com)" - The word 'cryptographic' can be left out if the rouines from the library - being used are not cryptographic related :-). -4. If you include any Windows specific code (or a derivative thereof) from - the apps directory (application code) you must include an acknowledgement: - "This product includes software written by Tim Hudson (tjhcryptsoft.com)" - -THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND -ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE -ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE -FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS -OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT -LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY -OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -The licence and distribution terms for any publically available version or -derivative of this code cannot be changed. i.e. this code cannot simply be -copied and put under another distribution licence -[including the GNU Public Licence.] - -## PostgreSQL License - -PostgreSQL Database Management System -(formerly known as Postgres, then as Postgres95) - -Portions Copyright © 1996-2020, The PostgreSQL Global Development Group - -Portions Copyright © 1994, The Regents of the University of California - -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose, without fee, and without a written agreement -is hereby granted, provided that the above copyright notice and this paragraph -and the following two paragraphs appear in all copies. - -IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR -DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING -LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, -EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, -BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, -AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, -SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. diff --git a/product_docs/docs/bdr/3.7/licenses.mdx b/product_docs/docs/bdr/3.7/licenses.mdx deleted file mode 100644 index 20cf726efaa..00000000000 --- a/product_docs/docs/bdr/3.7/licenses.mdx +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: 'Appendix C: Licenses' -originalFilePath: licenses.md - ---- - -In this section we list the libraries used by BDR3, with the -corresponding licenses. - -| Library | License | -| :------ | :--------------------------------- | -| LLVM | BSD (3-clause) | -| OpenSSL | SSLeay License AND OpenSSL License | -| Libpq | PostgreSQL License | - -## LLVM - -Copyright © 1994 The Regents of the University of California. All -rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. Neither the name of the University nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS \`\`AS IS'' -AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS -BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR -CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF -SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR -BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, -WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE -OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN -IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - -## OpenSSL - -==================================================================== - -Copyright © 1998-2004 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: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - -2. 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. - -3. 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. ( - -4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to - endorse or promote products derived from this software without - prior written permission. For written permission, please contact - openssl-coreopenssl.org. - -5. Products derived from this software may not be called "OpenSSL" - nor may "OpenSSL" appear in their names without prior written - permission of the OpenSSL Project. - -6. Redistributions of any form whatsoever must retain the following - acknowledgment: - "This product includes software developed by the OpenSSL Project - for use in the OpenSSL Toolkit ( - -THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT \`\`AS IS'' AND ANY -EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR -ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT -NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; -LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, -STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) -ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED -OF THE POSSIBILITY OF SUCH DAMAGE. - -==================================================================== - -This product includes cryptographic software written by Eric Young -(eaycryptsoft.com). This product includes software written by Tim -Hudson (tjhcryptsoft.com). - -## Original SSLeay Licence - -Copyright © 1995-1998 Eric Young (eaycryptsoft.com) -All rights reserved. - -This package is an SSL implementation written -by Eric Young (eaycryptsoft.com). -The implementation was written so as to conform with Netscapes SSL. - -This library is free for commercial and non-commercial use as long as -the following conditions are aheared to. The following conditions -apply to all code found in this distribution, be it the RC4, RSA, -lhash, DES, etc., code; not just the SSL code. The SSL documentation -included with this distribution is covered by the same copyright terms -except that the holder is Tim Hudson (tjhcryptsoft.com). - -Copyright remains Eric Young's, and as such any Copyright notices in -the code are not to be removed. -If this package is used in a product, Eric Young should be given attribution -as the author of the parts of the library used. -This can be in the form of a textual message at program startup or -in documentation (online or textual) provided with the package. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. All advertising materials mentioning features or use of this software - must display the following acknowledgement: - "This product includes cryptographic software written by - Eric Young (eaycryptsoft.com)" - The word 'cryptographic' can be left out if the rouines from the library - being used are not cryptographic related :-). -4. If you include any Windows specific code (or a derivative thereof) from - the apps directory (application code) you must include an acknowledgement: - "This product includes software written by Tim Hudson (tjhcryptsoft.com)" - -THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND -ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE -ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE -FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS -OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT -LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY -OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -The licence and distribution terms for any publically available version or -derivative of this code cannot be changed. i.e. this code cannot simply be -copied and put under another distribution licence -[including the GNU Public Licence.] - -## PostgreSQL License - -PostgreSQL Database Management System -(formerly known as Postgres, then as Postgres95) - -Portions Copyright © 1996-2020, The PostgreSQL Global Development Group - -Portions Copyright © 1994, The Regents of the University of California - -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose, without fee, and without a written agreement -is hereby granted, provided that the above copyright notice and this paragraph -and the following two paragraphs appear in all copies. - -IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR -DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING -LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, -EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, -BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, -AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, -SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. diff --git a/product_docs/docs/bdr/4.0/camo_clients.mdx b/product_docs/docs/bdr/4.0/camo_clients.mdx index 1087d828bdf..11fc9d3327f 100644 --- a/product_docs/docs/bdr/4.0/camo_clients.mdx +++ b/product_docs/docs/bdr/4.0/camo_clients.mdx @@ -1,8 +1,8 @@ --- -navTitle: 'Appendix E: CAMO Reference Clients' -title: 'Appendix E: CAMO Reference Client Implementations' +navTitle: 'Appendix D: CAMO Reference Clients' +title: 'Appendix D: CAMO Reference Client Implementations' originalFilePath: camo_clients.md --- - + diff --git a/product_docs/docs/bdr/4.0/index.mdx b/product_docs/docs/bdr/4.0/index.mdx index 2819fee9124..f3db6e66998 100644 --- a/product_docs/docs/bdr/4.0/index.mdx +++ b/product_docs/docs/bdr/4.0/index.mdx @@ -30,7 +30,6 @@ navigation: - feature-matrix - isolation_details - known-issues - - licenses - camo_clients title: BDR (Bi-Directional Replication) directoryDefaults: diff --git a/product_docs/docs/bdr/4.0/licenses.mdx b/product_docs/docs/bdr/4.0/licenses.mdx deleted file mode 100644 index dd98c1f85f1..00000000000 --- a/product_docs/docs/bdr/4.0/licenses.mdx +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: 'Appendix D: Licenses' -originalFilePath: licenses.md - ---- - -In this section we list the libraries used by BDR4, with the -corresponding licenses. - -| Library | License | -| :------ | :--------------------------------- | -| LLVM | BSD (3-clause) | -| OpenSSL | SSLeay License AND OpenSSL License | -| Libpq | PostgreSQL License | - -## LLVM - -Copyright © 1994 The Regents of the University of California. All -rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. Neither the name of the University nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS \`\`AS IS'' -AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS -BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR -CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF -SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR -BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, -WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE -OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN -IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - -## OpenSSL - -==================================================================== - -Copyright © 1998-2004 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: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - -2. 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. - -3. 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. ( - -4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to - endorse or promote products derived from this software without - prior written permission. For written permission, please contact - openssl-coreopenssl.org. - -5. Products derived from this software may not be called "OpenSSL" - nor may "OpenSSL" appear in their names without prior written - permission of the OpenSSL Project. - -6. Redistributions of any form whatsoever must retain the following - acknowledgment: - "This product includes software developed by the OpenSSL Project - for use in the OpenSSL Toolkit ( - -THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT \`\`AS IS'' AND ANY -EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR -ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT -NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; -LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, -STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) -ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED -OF THE POSSIBILITY OF SUCH DAMAGE. - -==================================================================== - -This product includes cryptographic software written by Eric Young -(eaycryptsoft.com). This product includes software written by Tim -Hudson (tjhcryptsoft.com). - -## Original SSLeay Licence - -Copyright © 1995-1998 Eric Young (eaycryptsoft.com) -All rights reserved. - -This package is an SSL implementation written -by Eric Young (eaycryptsoft.com). -The implementation was written so as to conform with Netscapes SSL. - -This library is free for commercial and non-commercial use as long as -the following conditions are aheared to. The following conditions -apply to all code found in this distribution, be it the RC4, RSA, -lhash, DES, etc., code; not just the SSL code. The SSL documentation -included with this distribution is covered by the same copyright terms -except that the holder is Tim Hudson (tjhcryptsoft.com). - -Copyright remains Eric Young's, and as such any Copyright notices in -the code are not to be removed. -If this package is used in a product, Eric Young should be given attribution -as the author of the parts of the library used. -This can be in the form of a textual message at program startup or -in documentation (online or textual) provided with the package. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -1. Redistributions of source code must retain the copyright - notice, this list of conditions and the following disclaimer. -2. 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. -3. All advertising materials mentioning features or use of this software - must display the following acknowledgement: - "This product includes cryptographic software written by - Eric Young (eaycryptsoft.com)" - The word 'cryptographic' can be left out if the rouines from the library - being used are not cryptographic related :-). -4. If you include any Windows specific code (or a derivative thereof) from - the apps directory (application code) you must include an acknowledgement: - "This product includes software written by Tim Hudson (tjhcryptsoft.com)" - -THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND -ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE -ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE -FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS -OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT -LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY -OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -The licence and distribution terms for any publically available version or -derivative of this code cannot be changed. i.e. this code cannot simply be -copied and put under another distribution licence -[including the GNU Public Licence.] - -## PostgreSQL License - -PostgreSQL Database Management System -(formerly known as Postgres, then as Postgres95) - -Portions Copyright © 1996-2020, The PostgreSQL Global Development Group - -Portions Copyright © 1994, The Regents of the University of California - -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose, without fee, and without a written agreement -is hereby granted, provided that the above copyright notice and this paragraph -and the following two paragraphs appear in all copies. - -IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR -DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING -LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, -EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGE. - -THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, -BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, -AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, -SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx index cd72911f2b3..bd919830ea2 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx @@ -25,16 +25,8 @@ Not all database configuration parameters are supported by BigAnimal. Some param 2. Enter the new value in the parameter value field. See [Parameter Names and Values](https://www.postgresql.org/docs/current/config-setting.html#CONFIG-SETTING-NAMES-VALUES) for more information on the types of values parameters accept. - !!! note - You can't decrease the values of the following parameters: - - max_connections - - max_locks_per_transaction - - max_prepared_transactions - - max_wal_senders - - max_worker_processes - - !!! Danger - Parameters identified with a yellow exclamation point icon trigger a restart when you save your changes. The restart terminates all open connections and takes a few minutes to complete. It takes a few more seconds for the new connection to establish. During this process, it isn't possible to connect to the database. - !!! + !!! Danger + Parameters identified with a yellow exclamation point icon trigger a restart when you save your changes. The restart terminates all open connections and takes a few minutes to complete. It takes a few more seconds for the new connection to establish. During this process, it isn't possible to connect to the database. + !!! 3. Save your changes. diff --git a/product_docs/docs/pem/8/pem_admin/01_overview/01_pem_architecture.mdx b/product_docs/docs/pem/8/pem_admin/01_overview/01_pem_architecture.mdx index e16814e1661..f60328c819f 100644 --- a/product_docs/docs/pem/8/pem_admin/01_overview/01_pem_architecture.mdx +++ b/product_docs/docs/pem/8/pem_admin/01_overview/01_pem_architecture.mdx @@ -1,5 +1,5 @@ --- -title: "PEM Architecture" +title: "PEM architecture" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/pem_architecture.html" @@ -27,7 +27,7 @@ The following architectural diagram illustrates the relationships between the PE ![PEM Architecture](../../images/pem_architecture.png) -## The PEM Server +## The PEM server ![PEM Server](../../images/pem_server.png) @@ -55,7 +55,7 @@ The instance of Postgres (a database server) and an instance of the Apache web-s 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 ![PEM Agent](../../images/pem_agent.png) @@ -86,13 +86,13 @@ The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in t To see more information about these parameters see [Server Configuration](../../pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options/). -## The PEM Web Client +## 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 +## 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. diff --git a/product_docs/docs/pem/8/pem_admin/01_overview/02_installing_pem_overview.mdx b/product_docs/docs/pem/8/pem_admin/01_overview/02_installing_pem_overview.mdx index d7092183db9..d162a97bfca 100644 --- a/product_docs/docs/pem/8/pem_admin/01_overview/02_installing_pem_overview.mdx +++ b/product_docs/docs/pem/8/pem_admin/01_overview/02_installing_pem_overview.mdx @@ -1,13 +1,15 @@ --- -title: "Installing PEM - Overview" +title: "Installing PEM - overview" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/installing_pem_overview.html" --- -For detailed instructions about installing PEM, please consult the `PEM Installation Guides`, available at: +For detailed instructions about installing PEM, see: + +[Installing on Linux](pem_inst_guide_linux) +[Installing on Windows](pem_inst_guide_windows) - The basic steps involved in the PEM installation process are: diff --git a/product_docs/docs/pem/8/pem_admin/01_overview/03_using_pem_web_interface.mdx b/product_docs/docs/pem/8/pem_admin/01_overview/03_using_pem_web_interface.mdx index 89cf0f52fbd..51155b8dacb 100644 --- a/product_docs/docs/pem/8/pem_admin/01_overview/03_using_pem_web_interface.mdx +++ b/product_docs/docs/pem/8/pem_admin/01_overview/03_using_pem_web_interface.mdx @@ -1,5 +1,5 @@ --- -title: "Using the PEM Web Interface" +title: "Using the PEM web interface" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/using_pem_web_interface.html" @@ -27,7 +27,7 @@ The PEM web interface opens, displaying the `Global Overview` Dashboard. The `Browser` pane displays a tree control that provides access to information about 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. -## The PEM Menu Bar +## The PEM menu bar The PEM menu bar provides access to commands and features that you can use to manage your database servers and the objects that reside on those servers. If an option is disabled: @@ -39,7 +39,7 @@ The PEM menu bar provides access to commands and features that you can use to ma Context-sensitive menus across the top of the PEM web interface allow you to customize your environment and provide access to the enterprise management features of PEM. -### The File Menu +### The File menu ![The File Menu](../../images/pem_file_menu.png) @@ -52,7 +52,7 @@ Use the `File` menu to access the following options: | Server Configuration | Click to open the Server Configuration dialog and update your PEM server configuration settings. | | Reset Layout | If a workspace panel is popped out by mistake or intentionally it can be reset back to default using Reset Layout. | -### The Object Menu +### The Object menu ![The Object Menu](../../images/pem_object_menu.png) @@ -76,7 +76,7 @@ The `Object` menu is context-sensitive. Use the `Object` menu to access the foll | Truncate | Click to remove all rows from a table (Truncate) or to remove all rows from a table and its child tables (Truncate Cascade). | | View Data | Click to access a context menu that provides several options for viewing data. | -### The Management Menu +### The Management menu ![The Management Menu](../../images/pem_management_menu.png) @@ -123,7 +123,7 @@ Use the context-sensitive `Dashboards` menu to access dashboards: | Streaming Replication | Click to open the Streaming Replication Analysis Dashboard for the selected node. | | System Wait | Click to open the System Wait Analysis Dashboard for the selected node. | -### The Tools Menu +### The Tools menu ![The Tools menu](../../images/pem_tool_menu.png) @@ -147,7 +147,7 @@ Use the options on the `Tools` menu to access the following features: | Grant Wizard... | Click to access the Grant Wizard tool. | | Schedule Backup | Click to access the Schedule Backup dialog for BART backups. | -### The Help Menu +### The Help menu ![The Help menu](../../images/pem_help_menu.png) @@ -160,7 +160,7 @@ Use the options on the `Help` menu to access the online help documents or to rev | EDB Website | Click to open the EDB website in a browser window. | | About Postgres Enterprise Manager | Click to locate versioning and user information for Postgres Enterprise Manager. | -## Controlling and Customizing Charts, Graphs and Tables +## Controlling and customizing charts, graphs and tables Use the icons in the upper-right corner of each graphic on a dashboard to control and customize the charts, graphs and tables displayed in the PEM client for your current user session. @@ -179,7 +179,7 @@ The following table gives the information about icons: For more information about customizing the graphics displayed on the PEM dashboards, please see the PEM client online help. -## Online Help and Documentation +## Online help and documentation PEM contains built-in help that provides assistance in using the tool. To access the online help for PEM, select `Online Help` from the `Help` option on the `Help` menu. diff --git a/product_docs/docs/pem/8/pem_admin/01_overview/index.mdx b/product_docs/docs/pem/8/pem_admin/01_overview/index.mdx index 2b60e7a6a62..efe69f1a426 100644 --- a/product_docs/docs/pem/8/pem_admin/01_overview/index.mdx +++ b/product_docs/docs/pem/8/pem_admin/01_overview/index.mdx @@ -1,5 +1,5 @@ --- -title: "PEM Overview" +title: "PEM overview" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/overview.html" diff --git a/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx b/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx index cb94f88f6d9..b4d38934527 100644 --- a/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx +++ b/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx @@ -1,5 +1,5 @@ --- -title: "Registering a Server" +title: "Registering a server" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/registering_server.html" @@ -7,7 +7,7 @@ legacyRedirectsGenerated: Before you can manage or monitor a server with PEM, you must register the server with PEM, and bind an agent. A server may be bound to a remote agent (an agent that resides on a different host), but if the agent does not reside on the same host, it will not have access to all of the statistical information about the instance. -## Manually Registering a Server +## Manually registering a server To manage or monitor a server with PEM, you must: @@ -182,7 +182,7 @@ Use the fields on the `Misc` tab under `BART` tab to describe the miscellaneous To view the properties of a server, right-click on the server name in the PEM client tree control, and select the `Properties…` option from the context menu. To modify a server's properties, disconnect from the server before opening the `Properties` dialog. -## Automatic Server Discovery +## Automatic server discovery If the server you wish to monitor resides on the same host as the monitoring agent, you can use the `Auto Discovery` dialog to simplify the registration and binding process. @@ -218,7 +218,7 @@ When you've finished specifying the connection properties for the servers that y After clicking the `OK` button, the newly registered server is displayed in the PEM tree control and is monitored by the PEM server. -## Using the pemworker Utility to Register a Server +## Using the pemworker utility to register a server You can use the `pemworker` utility to register a server for monitoring by the PEM server or to unregister a database server. During registration, the `pemworker` utility will bind the new server to the agent that resides on the system from which you invoked the registration command. To register a server: @@ -260,7 +260,7 @@ Set the environment variable `PEM_MONITORED_SERVER_PASSWORD` to provide the pass Failure to provide the password will result in a password authentication error. The PEM server will acknowledge that the server has been registered properly. -### Using the pemworker Utility to Unregister a Server +### Using the pemworker utility to unregister a server You can use the `pemworker` utility to unregister a database server; to unregister a server, invoke the `pemworker` utility: @@ -285,7 +285,7 @@ Use the `PEM_SERVER_PASSWORD` environment variable to provide the password for t Failure to provide the password will result in a password authentication error. The PEM server will acknowledge that the server has been unregistered. -## Verifying the Connection and Binding +## Verifying the connection and binding Once registered, the new server will be added to the PEM `Browser` tree control, and be displayed on the `Global Overview`. diff --git a/product_docs/docs/pem/8/pem_admin/02a_pem_remote_monitoring.mdx b/product_docs/docs/pem/8/pem_admin/02a_pem_remote_monitoring.mdx index 9d558476d7e..7480c3f66d0 100644 --- a/product_docs/docs/pem/8/pem_admin/02a_pem_remote_monitoring.mdx +++ b/product_docs/docs/pem/8/pem_admin/02a_pem_remote_monitoring.mdx @@ -1,5 +1,5 @@ --- -title: "Remote Monitoring" +title: "Remote monitoring" --- Remote monitoring is monitoring your Postgres cluster using a PEM Agent residing on a different host. diff --git a/product_docs/docs/pem/8/pem_admin/03_pem_define_aws_instance_connection.mdx b/product_docs/docs/pem/8/pem_admin/03_pem_define_aws_instance_connection.mdx index 2bfd57f92ab..0538202dcba 100644 --- a/product_docs/docs/pem/8/pem_admin/03_pem_define_aws_instance_connection.mdx +++ b/product_docs/docs/pem/8/pem_admin/03_pem_define_aws_instance_connection.mdx @@ -1,5 +1,5 @@ --- -title: "Defining and Monitoring Postgres clusters on AWS" +title: "Defining and monitoring Postgres clusters on AWS" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/pem_define_aws_instance_connection.html" @@ -10,7 +10,7 @@ There are two scenarios in which you can monitor a Postgres cluster on an AWS ho - Postgres cluster running on AWS EC2 - Postgres cluster running on AWS RDS -## Monitoring a Postgres Cluster Running on AWS EC2 +## Monitoring a Postgres cluster running on AWS EC2 After creating a Postgres cluster on AWS EC2, you can use the PEM server to register and monitor your cluster. The following scenarios are currently supported: @@ -25,6 +25,6 @@ Since the PEM Agent is on a different host from the PEM Server, register the PEM After you register the PEM Agent with the PEM Server and bind the PEM Agent to the Postgres cluster while adding to the PEM Server, you can monitor your Postgres cluster using PEM. -## Monitoring a Postgres Cluster Running on AWS RDS +## Monitoring a Postgres cluster running on AWS RDS While creating an AWS RDS database, choose `PostgreSQL` when prompted for `Engine options`. See [Remote Monitoring](../pem_admin/02a_pem_remote_monitoring) for next steps. \ No newline at end of file diff --git a/product_docs/docs/pem/8/pem_admin/04_managing_certificates.mdx b/product_docs/docs/pem/8/pem_admin/04_managing_certificates.mdx index 90a6f274c5d..8ebc3dff019 100644 --- a/product_docs/docs/pem/8/pem_admin/04_managing_certificates.mdx +++ b/product_docs/docs/pem/8/pem_admin/04_managing_certificates.mdx @@ -1,5 +1,5 @@ --- -title: "Managing Certificates" +title: "Managing certificates" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/managing_certificates.html" @@ -25,7 +25,7 @@ When you uninstall an agent, the certificate associated with that agent will be The following sections contain detailed information about manually replacing certificate files. -## Replacing SSL Certificates +## Replacing SSL certificates The following steps detail replacing the SSL certificates on an existing PEM installation. If you plan to upgrade your server to a new version at the same time, invoke all of the PEM installers (first the server installer, then agent installers) before replacing the SSL certificates. Then: @@ -172,7 +172,7 @@ The following steps detail replacing the SSL certificates on an existing PEM ins systemctl restart postgresql-x ``` -## Updating Agent SSL Certificates +## Updating agent SSL certificates For each agent that interacts with the PEM server, you must: diff --git a/product_docs/docs/pem/8/pem_admin/05_managing_configuration_settings.mdx b/product_docs/docs/pem/8/pem_admin/05_managing_configuration_settings.mdx index b35bf4998dc..0824e454511 100644 --- a/product_docs/docs/pem/8/pem_admin/05_managing_configuration_settings.mdx +++ b/product_docs/docs/pem/8/pem_admin/05_managing_configuration_settings.mdx @@ -1,5 +1,5 @@ --- -title: "Managing Configuration Settings" +title: "Managing configuration settings" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/managing_configuration_settings.html" diff --git a/product_docs/docs/pem/8/pem_admin/06_managing_pem_server.mdx b/product_docs/docs/pem/8/pem_admin/06_managing_pem_server.mdx index c5417794dae..f65a934a9ad 100644 --- a/product_docs/docs/pem/8/pem_admin/06_managing_pem_server.mdx +++ b/product_docs/docs/pem/8/pem_admin/06_managing_pem_server.mdx @@ -1,5 +1,5 @@ --- -title: "Managing a PEM Server" +title: "Managing a PEM server" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/managing_pem_server.html" @@ -9,7 +9,7 @@ legacyRedirectsGenerated: The sections that follow provide information about tasks related to PEM server such as restarting the PEM server and agent, controlling the PEM server or PEM agent, controlling the HTTPD service on Linux and Windows, controlling the HTTPD server, managing PEM authentication and security, modifying the `pg_hba.conf` file, modifying PEM to use a proxy server etc. -## Starting and Stopping the PEM Server and Agents +## Starting and stopping the PEM server and agents The PEM server starts, stops and restarts when the Postgres server instance on which it resides starts, stops or restarts; use the same commands to control the PEM server that you would use to control the Postgres server. On Linux platforms, the command that stops and starts the service script will vary by platform and OS version. @@ -23,7 +23,7 @@ Use the `Stop`, `Pause`, `Start`, or `Restart` buttons to control the state of t Please note that any user (or client application) connected to the Postgres server will be abruptly disconnected if you stop the service. For more information about controlling a service, please consult the [*EDB Postgres Advanced Server Installation Guide*](https://www.enterprisedb.com/docs/epas/latest/), available from the EDB website. -## Remotely Starting and Stopping Monitored Servers +## Remotely starting and stopping monitored servers PEM allows you to startup and shutdown managed server instances with the PEM client. To configure a server to allow PEM to manage the service, complete the Server registration dialog, registering the database server with a PEM agent and: @@ -40,7 +40,7 @@ After connecting to the server, you can start or stop the server by highlighting ![The Tools menu of a managed server](../images/pem_server_tools_menu_queue_server.png) -## Controlling the PEM Server or PEM Agent on Linux +## Controlling the PEM server or PEM agent on Linux On Linux platforms, the name of the service script that controls: @@ -69,7 +69,7 @@ Where: - `restart` to stop and then start the service. - `status` to check the status of the service. -## Controlling the PEM Server or PEM Agent on Windows +## Controlling the PEM server or PEM agent on Windows The Windows operating system includes a graphical service controller that displays the server status, and offers point-and-click server control. The registered name of the service that controls: @@ -89,7 +89,7 @@ Use the `Pause the service` option to instruct Postgres to reload a service's co Use the `Start the service` option to start a service. -## Controlling the HTTPD Server +## Controlling the HTTPD server On Linux, you can confirm the status of the `PEM-HTTPD` service by opening a command line, and entering the following command: @@ -115,7 +115,7 @@ On Windows, you can use the `Services` applet to check the status of the `PEM HT The `Status` column displays the current state of the server. Click the `Start` link to start `PEM HTTPD` if the service is not running. -## Modifying the pg_hba.conf File +## Modifying the pg_hba.conf file Entries in the `pg_hba.conf` file control network authentication and authorization. The `pg_hba.conf` file on the PEM server host must allow connections between the PEM server and PEM-HTTPD, the PEM agent, and the monitored servers. @@ -153,7 +153,7 @@ Before you can connect to a Postgres server with PEM, you must ensure that the ` If you receive this error when connecting to the database server, modify the `pg_hba.conf` file, adding an entry that allows the connection. -## Creating and Maintaining Databases and Objects +## Creating and maintaining databases and objects Each instance of a Postgres server manages one or more databases; each user must provide authentication information to connect to the database before accessing the information contained within it. The PEM client provides dialogs that allow you to create and manage databases, and all of the various objects that comprise a database (e.g. tables, indexes, stored procedures, etc.). @@ -175,7 +175,7 @@ PEM provides similar dialogs for the creation and management of other database o Each object type is displayed in the tree control; right click on the node that corresponds to an object type to access the `Create` menu and create a new object, or select `Properties` from the context menu of a named node to perform administrative tasks for the highlighted object. -## Managing PEM Authentication +## Managing PEM authentication Postgres supports a number of authentication methods: @@ -203,7 +203,7 @@ The password file is usually named `~root/.pgpass` on Linux systems, or `%APPDAT For more information about the authentication methods supported by Postgres, see the [PostgreSQL core documentation](http://www.postgresql.org/docs/current/client-authentication.html). -## Editing the PEM Server Configuration +## Editing the PEM server configuration You can use the PEM client to graphically manage the configuration parameters of the PEM server to enable features or modify default settings. To open the `Server Configuration` dialog, select `Server Configuration…` from the `Management` menu. @@ -211,11 +211,11 @@ You can use the PEM client to graphically manage the configuration parameters of To modify a parameter value, edit the content displayed in the `Value` field to the right of a parameter name. Click the `Save` button to preserve your changes, or click the `Close` button to exit the dialog without applying the changes. Use the `Reset` button to return the parameters to their original value. -## Managing Security +## Managing security PEM provides a graphical way to manage your Postgres roles and servers. -### Login Roles +### Login roles When you connect to the PEM server, you must provide role credentials that allow access to the database on which the PEM server stores data. By default, the postgres superuser account is used to initially connect to the server, but it is strongly recommended (for both security and auditing purposes) that individual roles are created for each connecting user. You can use the PEM Query Tool, the PEM web interface `Create – Login/Group Role` dialog, or a command line client (such as psql) to create a role. @@ -233,13 +233,13 @@ To modify the properties of an existing login role, right click on the name of a For more complete information about creating and managing a role, see the [PostgreSQL online documentation](http://www.postgresql.org/docs/current/sql-createrole.html). -### Group Roles +### Group roles Group roles can serve as containers, used to dispense system privileges (such as creating databases) and object privileges (e.g. inserting data into a particular table). The primary purpose of a group role is to make the mass management of system and object permissions much easier for a DBA. Rather than assigning or modifying privileges individually across many different login accounts, you can assign or change privileges for a single role and then grant that role to many login roles at once. Use the `Group Roles` node (located beneath the name of each registered server in the PEM tree control) to create and manage group roles. Options on the context menu provide access to a dialog that allows you to create a new role or modify the properties of an existing role. You can find more information about creating roles [here](http://www.postgresql.org/docs/current/sql-createrole.html). -### Using PEM Pre-Defined Roles to Manage Access to PEM Functionality +### Using PEM pre-defined roles to manage access to PEM functionality 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. @@ -279,7 +279,7 @@ You can use PEM pre-defined roles to allow access to the functionality listed in | pem_comp_audit_manager | pem_component | Role to run the Audit Manager. | | pem_comp_tuning_wizard | pem_component | Role to run the Tuning Wizard. | -### Using a Team Role +### Using a team role When you register a server for monitoring by PEM, you can specify a *Team* that will be associated with the server. A Team is a group role that can be used to allow or restrict access to one or more monitored servers to a limited group of role members. The PEM client will only display a server with a specified Team to those users who are: @@ -289,7 +289,7 @@ When you register a server for monitoring by PEM, you can specify a *Team* that To create a team role, expand the node for the server on which the role will reside in the PEM tree control, and right-click on the `Login/Group Roles` node to access the context menu. Then, select `Login/Group Role…` from the `Create` menu; when the `Create - Login/Group Role` dialog opens, use the fields provided to specify the properties of the team role. -### Object Permissions +### Object permissions A role must be granted sufficient privileges before accessing, executing, or creating any database object. PEM allows you to assign (`GRANT`) and remove (`REVOKE`) object permissions to group roles or login accounts using the graphical interface of the PEM client. @@ -297,7 +297,7 @@ Object permissions are managed via the graphical object editor for each particul The PEM client also contains a `Grant Wizard` (accessed through the `Tools` menu) that allows you to manage many object permissions at once. -## Managing Job Notifications +## Managing job notifications You can configure the settings in PEM console for sending the SMTP trap on success or failure of a system-generated job (listed under scheduled tasks) or a custom-defined agent job. These email notification settings can be configured at following three levels (in order of precedence) to send email notifications to the specified user group: @@ -305,7 +305,7 @@ You can configure the settings in PEM console for sending the SMTP trap on succe - Agent level - PEM server level (default level) -### Configuring Job Notifications at Job Level +### Configuring job notifications at job level You can configure email notification settings at job level only for a custom-defined agent job in one of the following ways: @@ -319,7 +319,7 @@ Use the fields on the `Notifications` tab to configure the email notification se - 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. -### Configuring Job Notifications at Agent Level +### Configuring job notifications at agent level Select the agent in the tree view, right click and select *Properties*. In the `Properties` dialog, select the *Job notifications* tab. @@ -332,7 +332,7 @@ Use the fields on the Job notifications tab to configure the email notification - 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. -### Configuring Job Notifications at Server Level +### Configuring job notifications at server level You can use the *Server Configuration* dialog to provide information about your email notification configuration at PEM server level. To open the Server Configuration dialog, select *Server Configuration...* from the PEM client's Management menu. @@ -345,7 +345,7 @@ Four server configuration parameters specify information about your job notifica - Use the `job_retention_time parameter` to specify the number of days that non-recurring scheduled tasks should be retained in the system. - Use the `job_status_change_notification` switch to specify if you want to send email notification after each job status change, irrespective of its status being a failure, success, or interrupted. -## Managing PEM Scheduled Jobs +## Managing PEM scheduled jobs 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. diff --git a/product_docs/docs/pem/8/pem_admin/07_managing_pem_agent.mdx b/product_docs/docs/pem/8/pem_admin/07_managing_pem_agent.mdx index ec0bc11b5fb..ff73033d8b4 100644 --- a/product_docs/docs/pem/8/pem_admin/07_managing_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_admin/07_managing_pem_agent.mdx @@ -1,5 +1,5 @@ --- -title: "Managing a PEM Agent" +title: "Managing a PEM agent" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/administrators-guide/8.0/managing_pem_agent.html" @@ -7,7 +7,7 @@ legacyRedirectsGenerated: The sections that follow provide information about the behavior and management of a PEM agent. -## Agent Privileges +## 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. @@ -54,7 +54,7 @@ You can view probe-related errors that occurred on the server in the `Probe Log` On Windows, log information is available on the `Event Viewer`. -## Agent Configuration +## Agent configuration A number of user-configurable parameters and registry entries control the behavior of the PEM agent. You may be required to modify the PEM agent's parameter settings to enable some PEM functionality. After modifying values in the PEM agent configuration file, you must restart the PEM agent to apply any changes. @@ -135,7 +135,7 @@ The registry contains the following entries: | WebhookSSLCaCrt | The complete path to the webhook's SSL ca certificate file. | | | AllowInsecureWebhooks | When set to true, allow webhooks to call with insecure flag. | false | -## Agent Properties +## 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. diff --git a/product_docs/docs/pem/8/pem_agent/01_pem_architecture.mdx b/product_docs/docs/pem/8/pem_agent/01_pem_architecture.mdx index 17b814e4c27..e66948c707a 100644 --- a/product_docs/docs/pem/8/pem_agent/01_pem_architecture.mdx +++ b/product_docs/docs/pem/8/pem_agent/01_pem_architecture.mdx @@ -1,5 +1,5 @@ --- -title: "PEM Architecture" +title: "PEM architecture" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/agent-user-guide/8.0/pem_architecture.html" @@ -29,7 +29,7 @@ The following architectural diagram illustrates the relationships between the PE PEM Architecture -## The PEM Server +## The PEM server ![PEM Server](../images/pem_server.png) @@ -55,7 +55,7 @@ The instance of Postgres (a database server) and an instance of the Apache web-s 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 ![PEM Agent](../images/pem_agent.png) @@ -86,13 +86,13 @@ The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in t To see more information about these parameters see [Server Configuration](../pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options/). -## The PEM Web Client +## 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 +## 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. diff --git a/product_docs/docs/pem/8/pem_agent/02_registering_agent.mdx b/product_docs/docs/pem/8/pem_agent/02_registering_agent.mdx index 60b21765565..0d4ec1ff6bc 100644 --- a/product_docs/docs/pem/8/pem_agent/02_registering_agent.mdx +++ b/product_docs/docs/pem/8/pem_agent/02_registering_agent.mdx @@ -1,5 +1,5 @@ --- -title: "Registering an Agent" +title: "Registering an agent" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/agent-user-guide/8.0/registering_agent.html" @@ -43,7 +43,7 @@ You can use the `PEM_SERVER_PASSWORD` environment variable to set the password o 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 +## 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: @@ -63,7 +63,7 @@ The service will confirm that it is starting the agent; when the agent is regist 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 +## 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: diff --git a/product_docs/docs/pem/8/pem_agent/03_managing_pem_agent.mdx b/product_docs/docs/pem/8/pem_agent/03_managing_pem_agent.mdx index 233b390d322..3d922368583 100644 --- a/product_docs/docs/pem/8/pem_agent/03_managing_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_agent/03_managing_pem_agent.mdx @@ -1,5 +1,5 @@ --- -title: "Managing a PEM Agent" +title: "Managing a PEM agent" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/agent-user-guide/8.0/managing_pem_agent.html" @@ -7,7 +7,7 @@ legacyRedirectsGenerated: The sections that follow provide information about the behavior and management of a PEM agent. -## Agent Privileges +## 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. @@ -54,7 +54,7 @@ You can view probe-related errors that occurred on the server in the `Probe Log` On Windows, log information is available on the `Event Viewer`. -## Agent Configuration +## Agent configuration A number of user-configurable parameters and registry entries control the behavior of the PEM agent. You may be required to modify the PEM agent's parameter settings to enable some PEM functionality. After modifying values in the PEM agent configuration file, you must restart the PEM agent to apply any changes. @@ -135,7 +135,7 @@ The registry contains the following entries: | WebhookSSLCaCrt | The complete path to the webhook's SSL ca certificate file. | | | AllowInsecureWebhooks | When set to true, allow webhooks to call with insecure flag. | false | -## Agent Properties +## 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. diff --git a/product_docs/docs/pem/8/pem_agent/04_pem_agent_troubleshooting.mdx b/product_docs/docs/pem/8/pem_agent/04_pem_agent_troubleshooting.mdx index 07d2922a4fd..61d7fcae8e7 100644 --- a/product_docs/docs/pem/8/pem_agent/04_pem_agent_troubleshooting.mdx +++ b/product_docs/docs/pem/8/pem_agent/04_pem_agent_troubleshooting.mdx @@ -1,11 +1,11 @@ --- -title: "PEM Agent Troubleshooting" +title: "PEM agent troubleshooting" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/agent-user-guide/8.0/pem_agent_troubleshooting.html" --- -## Restoring a Deleted PEM Agent +## Restoring a deleted PEM agent If an agent has been deleted from the `pem.agent` table then you cannot restore it. You will need to use the pemworker utility to re-register the agent. @@ -25,7 +25,7 @@ If an agent has been deleted from PEM Web client but still has an entry in the ` The deleted agent will be restored again. However, the servers that were bound to that particular agent might appear to be down. To resolve this issue, you need to modify the PEM agent properties of the server to add the bound agent again; after the successful modification, the servers will be displayed as running properly. -## Using the Command Line to Delete a PEM Agent with Down or Unknown Status +## Using the command line to delete a PEM agent with down or unknown status Using the PEM web interface to delete PEM agents with `Down` or `Unknown` status may be difficult if the number of such agents is large. In such a situation, you might want to use the command line interface to delete `Down` or `Unknown` agents. diff --git a/product_docs/docs/pem/8/pem_agent/index.mdx b/product_docs/docs/pem/8/pem_agent/index.mdx index f281ee41dd8..069233f265f 100644 --- a/product_docs/docs/pem/8/pem_agent/index.mdx +++ b/product_docs/docs/pem/8/pem_agent/index.mdx @@ -12,10 +12,6 @@ PEM is composed of three primary components: PEM server, PEM agent, and PEM web For information about the platforms and versions supported by PEM, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#pem). -For information about the installation, uninstallation, or upgrading of a PEM Agent, visit the EDB website at: - - - This document provides information that is required to work with PEM agents. The guide will acquaint you with the basic registering, configuration, and management of agents. The guide is broken up into the following core sections: - **Postgres Enterprise Manager - Overview** - This section provides an overview of PEM architecure. diff --git a/product_docs/docs/pem/8/pem_bart/01_managing_bart.mdx b/product_docs/docs/pem/8/pem_bart/01_managing_bart.mdx index 9d98997aa76..8b9063c9d5b 100644 --- a/product_docs/docs/pem/8/pem_bart/01_managing_bart.mdx +++ b/product_docs/docs/pem/8/pem_bart/01_managing_bart.mdx @@ -1,5 +1,5 @@ --- -title: "Managing a BART Server" +title: "Managing a BART server" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/bart-management-features-guide/8.0/managing_bart.html" @@ -26,7 +26,7 @@ From PEM version 7.10 onwards, you can manage a BART server through PEM console. - To take a backup of the replica database servers, you must ensure that the latest *pg_basebackup* utility is installed on the database server that you want to manage through BART. -## Configuring a BART Server +## Configuring a BART server You can use the `Create–BART server` dialog to register an existing BART server with the PEM server. To access the dialog, right-click on the `BART Servers` node and select `Create-BART Server`. @@ -80,7 +80,7 @@ Use the fields on the `Misc` tab to describe the backup-related properties of th - Use the `Workers` field to specify the number of parallel worker processes required to stream the modified blocks of an incremental backups to the restore host. -## Associating the BART Server with a Database Server +## Associating the BART server with a database server After configuring the BART server, you must associate it with the database server whose backup you wish to manage with BART. You can do one of the following: @@ -144,7 +144,7 @@ Use the fields on the `Misc` tab to describe the miscellaneous properties of the - Use the `Workers` field to specify the number of parallel worker processes required to stream the modified blocks of an incremental backups to the restore host. -## Viewing the BART Server Details on a PEM Dashboard +## Viewing the BART server details on a PEM dashboard After associating the BART server with a database server, you can review the backup and restore details for that server on the PEM Dashboard. You can also perform operations such as restoration or deletion of a backup that is listed on the dashboard. @@ -166,7 +166,7 @@ A pin in the first column under `Actions` indicates that a backup can be marked You can delete all the `Obsolete` backups by clicking the `Delete Obsolete` button. You can also refresh the list of backups by clicking the `Refresh` button. -## Scheduling BART Backups +## Scheduling BART backups To create or manage a backup, select `Schedule Backup` from the `Tools` menu. The dialog header displays general execution information about the backup: @@ -245,7 +245,7 @@ Use the fields on the `Notifications` tab to specify the email notification sett - Use the `Email group` field to specify the email group that should receive the email notification. -## Scheduling BART Obsolete Backups deletion +## Scheduling BART obsolete backups deletion Use the `Schedule Obsolete Backup Deletion` dialog to schedule or modify a BART obsolete backup deletion. @@ -274,7 +274,7 @@ Use the fields within the `Times` box to specify the times at which the schedule - Use the `Hours` field to select the hour at which the schedule will execute. - Use the `Minutes` field to select the minute at which the schedule will execute. -## Restoring BART Backups +## Restoring BART backups You can restore the backups that you have earlier created using BART server on a target remote host. When you select a particular BART server, all the associated backups are listed in the Dashboard under `Initiated Server Backups`. diff --git a/product_docs/docs/pem/8/pem_bart/index.mdx b/product_docs/docs/pem/8/pem_bart/index.mdx index 6a574bb7960..34d2f09a6de 100644 --- a/product_docs/docs/pem/8/pem_bart/index.mdx +++ b/product_docs/docs/pem/8/pem_bart/index.mdx @@ -1,5 +1,5 @@ --- -navTitle: BART Management Features +navTitle: BART management features title: "PEM BART Management Guide" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -12,8 +12,4 @@ This guide will acquaint you with the dialogs that are built into the Postgres E This document uses `Postgres` to mean either the PostgreSQL or EDB Postgres Advanced Server database. -
-managing_bart conclusion - -
diff --git a/product_docs/docs/pem/8/pem_ent_feat/02_pem_query_tool.mdx b/product_docs/docs/pem/8/pem_ent_feat/02_pem_query_tool.mdx index 6132b87f3a3..42c66f4b847 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/02_pem_query_tool.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/02_pem_query_tool.mdx @@ -1,5 +1,5 @@ --- -title: "The PEM Query Tool" +title: "The PEM Query tool" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/pem_query_tool.html" @@ -56,7 +56,7 @@ Hover over an icon to display a tool-tip that describes the icon's functionality | `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 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. @@ -82,13 +82,13 @@ Options on the `Edit` menu offer functionality that helps with code formatting a 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 The `Data Output` panel displays data and statistics generated by the most recently executed query. ![Query Tool - Data output tab](../images/query_output_data.png) -### Data Output Tab +### Data Output tab The `Data Output` tab displays the result set of the query in a table format. You can: @@ -119,7 +119,7 @@ If any errors occur during saving (for example, trying to save a NULL into a col 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 +### Explain tab To generate the `Explain` or `Explain Analyze` plan of a query, click on `Explain` or `Explain Analyze` button in the toolbar. @@ -131,7 +131,7 @@ 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 +### 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. @@ -143,7 +143,7 @@ Use the download button on top left corner of the `Explain` canvas to download t The query plan that accompanies the `Explain analyze` is available on the `Data Output` tab. -### Analysis 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. @@ -165,7 +165,7 @@ If the planner has misestimated the number of rows (actual vs planned) by: ![Query Tool - Explain tab - Analysis tab](../images/query_explain_analyze_table.png) -### Statistics Tab +### Statistics tab The `Statistics` tab displays information in two tables: @@ -174,7 +174,7 @@ The `Statistics` tab displays information in two tables: ![Query Tool - Explain plan tab - Statistics tab](../images/query_explain_analyze_statistics.png) -### Messages Tab +### Messages tab Use the `Messages` tab to view information about the most recently executed query: @@ -184,7 +184,7 @@ If the server returns an error, the error message will be displayed on the `Mess ![Query Tool - Messages tab](../images/query_output_messages.png) -### Notifications Tab +### Notifications tab Use the `Notifications` tab to view the notifications using PostgreSQL `Listen/Notify` feature. For more details, see [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-listen.html). @@ -205,7 +205,7 @@ Example: ![Query Tool - Output Notifications panel](../images/query_output_notifications_panel.png) -## Query History Panel +## Query History panel Use the `Query History` tab to review activity for the current session: @@ -226,7 +226,7 @@ To erase the content of the `Query History` tab, select `Clear history` from the 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 +## Connection status Use the `Connection status` feature to view the current connection and transaction status by clicking on the status icon in query tool: diff --git a/product_docs/docs/pem/8/pem_ent_feat/03_pem_schema_diff_tool.mdx b/product_docs/docs/pem/8/pem_ent_feat/03_pem_schema_diff_tool.mdx index 5723e4f627a..c14c641c8bd 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/03_pem_schema_diff_tool.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/03_pem_schema_diff_tool.mdx @@ -1,5 +1,5 @@ --- -title: "The PEM Schema Diff Tool" +title: "The PEM Schema Diff tool" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/pem_schema_diff_tool.html" @@ -27,7 +27,7 @@ Use the `Preferences` dialog to specify if `Schema Diff` should open in a new br The `Schema Diff` panel is divided into two panels; an `Object Comparison panel` and a `DDL Comparison panel`. -## The Schema Diff Object Comparison Panel +## 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. @@ -54,7 +54,7 @@ In the upper-right hand corner of the object comparison panel is a `Filter` opti 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 +## Schema Diff DDL comparison panel The `DDL Comparison` panel displays three columns: diff --git a/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx b/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx index b34764579ff..51f2b187ba3 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx @@ -1,5 +1,5 @@ --- -title: "The ERD Tool" +title: "The ERD tool" --- !!! tip "New Feature " @@ -24,7 +24,7 @@ The **ERD Tool** toolbar uses context-sensitive icons that provide shortcuts to ![ERD Tool - Toolbar](../images/erd_tool_toolbar.png) -## File Options +## File options | Icon | Behavior | Shortcut | | ----------- | -------------------------------------------------------------------------------------------------------------- | ---------------- | @@ -32,14 +32,14 @@ The **ERD Tool** toolbar uses context-sensitive icons that provide shortcuts to | `Save` | Click the `Save` icon to perform a quick-save of a previously saved diagram, or to save the diagram to a file. | Ctrl + S | | `Save as` | Click the `Save As` to open a new browser dialog and specify a new location to save the diagram. | Ctrl + Shift + S | -## Export Options +## Export options | Icon | Behavior | Shortcut | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | `Generate SQL` | Click the `Generate SQL` icon to generate the DDL SQL for the diagram and open a query tool with the generated SQL ready for execution. | Option + Ctrl + S | | `Download image` | Click the `Download image` icon to save the ERD diagram in a image format. | Option + Ctrl + I | -## Editing Options +## Editing options | Icon | Behavior | Shortcut | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | @@ -48,7 +48,7 @@ The **ERD Tool** toolbar uses context-sensitive icons that provide shortcuts to | `Clone table` | Click this button to clone the complete table structure, name it with a auto generated name and put it in the diagram. | Option/Alt + Ctrl + C | | `Drop table/link` | You can drop a table or link using this button. You need to select a table or link and click on this button to drop it. | Option/Alt + Ctrl + D | -## Table Relationship Options +## Table relationship options | Icon | Behavior | Shortcut | | ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | @@ -63,7 +63,7 @@ The **ERD Tool** toolbar uses context-sensitive icons that provide shortcuts to | `Auto align` | Click this button to auto align all tables and links to make it look more cleaner. | Option/Alt + Ctrl + L | | `Show details` | Click this button to toggle the column details visibility. It allows you to show few or more column details. | Option/Alt + Shift + D | -## Zoom Options +## Zoom options | Icon | Behavior | Shortcut | | ------------- | ---------------------------------------------------------------------------------- | ------------------------ | @@ -71,7 +71,7 @@ The **ERD Tool** toolbar uses context-sensitive icons that provide shortcuts to | `Zoom in` | Click this button to zoom in the diagram. | Option/Alt + Shift + "+" | | `Zoom out` | Click this button to zoom out the diagram. | Option/Alt + Shift + "-" | -## Table Dialog +## Table dialog ![ERD Tool - Table Dialog](../images/erd_table_dialog.png) @@ -81,7 +81,7 @@ The table dialog allows you to: - It can be used edit an existing table or add a new one. - Refer [Table dialog](../pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog) for information on different fields. -## Table Node +## Table node ![ERD Tool - Table Node](../images/erd_table_node.png) @@ -94,7 +94,7 @@ The table node shows table details in a graphical representation: - You can click on the node and drag to move on the canvas. - Upon double click on the table node or by clicking the edit button from the toolbar, the table dialog opens where you can change the table details. Refer [Table dialog](../pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog) for information on different fields. -## The One to Many Link Dialog +## One to many link dialog ![ERD Tool - One to Many Dialog](../images/erd_1m_dialog.png) @@ -106,7 +106,7 @@ The one to many link dialog allows you to: - `Referenced Table` is the table that is being referred and has the `one` end point. - `Referenced Column` is the column that is being referred. -## The Many to Many Link Dialog +## Many to many link dialog ![ERD Tool - Many to Many Dialog](../images/erd_mm_dialog.png) @@ -119,7 +119,7 @@ The many to many link dialog allows you to: - `Right Table` is the second table that is to be linked. It will receive the `one` endpoint of the link with the new relation table. - `Right Column` is the column of the second table, that will always be a primary key. -## The Table Link +## Table link ![ERD Tool - Table Link](../images/erd_table_link.png) @@ -130,7 +130,7 @@ The table link shows relationship between tables: - If one of the columns that is being referred or that refers is removed from the table then the link will get dropped. - You can click on the link and drag to move on the canvas. -## The Table Notes +## Table notes ![ERD Tool - Table Notes](../images/erd_table_note.png) diff --git a/product_docs/docs/pem/8/pem_ent_feat/05_performance_monitoring_and_management.mdx b/product_docs/docs/pem/8/pem_ent_feat/05_performance_monitoring_and_management.mdx index 77ad56d499d..770ca34faca 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/05_performance_monitoring_and_management.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/05_performance_monitoring_and_management.mdx @@ -1,5 +1,5 @@ --- -title: "Performance Monitoring and Management" +title: "Performance monitoring and management" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/performance_monitoring_and_management.html" @@ -11,7 +11,7 @@ PEM contains built-in functionality that implements enterprise-wide performance 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 +## 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. @@ -111,7 +111,7 @@ Use fields on the `Dashboard Configuration` dialog to control attributes of the Please note that settings specified on the `Dashboard Configuration` dialog are applied only to the current user's session. -## Managing Custom Dashboards +## 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. @@ -123,7 +123,7 @@ To modify an existing dashboard, click the edit icon to the left of a dashboard 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 +### 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. @@ -179,7 +179,7 @@ To add another chart to your dashboard, click the add icon (+) in the section he To exit without saving your changes, click the `Cancel` button. -### Creating an Ops Dashboard +### 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. @@ -222,7 +222,7 @@ Use icons to the left of a charts name in the `Custom Charts` table to manage a - 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 +### 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. @@ -351,7 +351,7 @@ When you've finished defining the chart, click `Finish` to save your edits and a 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. -### System Probes +### System probes Unless otherwise noted, Postgres Enterprise Manager enables the probes listed in the table below: @@ -410,7 +410,7 @@ Unless otherwise noted, Postgres Enterprise Manager enables the probes listed in -### BDR Probes +### BDR probes To monitor the BDR Group via BDR dashboards, the following probes must be enabled. All these probes are configured at server level. @@ -435,7 +435,7 @@ All the following probes works with `BDR Enterprise Edition`. | BDR Workers | This probe returns information about workers in BDR node. The stored information includes:
The PID of the worker process
The worker query start timestamp
The worker state change timestamp
The worker wait event type
The worker wait event
The worker state
The worker role name
The worker commit timestamp
The worker local timestamp
The name of the origin node
The receive LSN
The receive commit LSN
The last exact replay LSN
The last exact flush LSN
The last exact replay timestamp
The worker query | Yes | Yes | | BDR Work Errors | This probe returns information aboutthe work errors in BDR node. The stored information includes:
The process id of the worker causing the error
The name of the BDR Group the node is part of
The name of the origin node
The name of the source node

The name of the target node
The name of the subscription
The internal identifier of the role of this worker
The name of the role of this worker
The date and time of the error
The age of the error
The description of the error
he context in which the error happened
The remote relation id
The subscription writer id
The subscription writer name | Yes | Yes | -### Customizing Probes +### 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. @@ -462,7 +462,7 @@ To modify the properties associated with a probe, highlight the name of a probe, 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 +#### 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. @@ -556,7 +556,7 @@ If you select a database version, and leave the `Probe Code` column blank, PEM w 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. -#### Exporting or Importing a Probe +#### Exporting or importing a probe !!! Tip "New Feature" Export and import of probes to another PEM Server is available from 8.2.0 and later. @@ -593,7 +593,7 @@ If the checkbox is not selected and probe does not exist but the corresponding t !!! Note It is possible that probe is deleted and not listed on `Manage Custom Probe` tab, but still the table holding the data of that probe exists in the `pem` schema. -#### Deleting a Probe +#### Deleting a probe You may delete only user-defined probes. To delete a probe, select the probe name in the probes table, and select the `Delete` icon (located to the upper-right corner of the table). The probe history will persist for the length of time specified on the `History Retention` field in the probe definition. During the deletion the probe definition is deleted and any corresponding tables are dropped from the `pemdata` and `pemhistory` schemas. @@ -601,7 +601,7 @@ System probes are the built-in probes provided by PEM, and are part of the PEM s ![Attempting to delete a system probe](../images/delete_system_probe.png) -#### Copying a Probe +#### 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: @@ -617,7 +617,7 @@ When you have selected the target object or objects, click the `Configure Probes 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. -### Viewing the Alerts via Global Dashboard +### Viewing the alerts via Global dashboard 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. @@ -629,7 +629,7 @@ The PEM server includes a number of pre-defined alerts that are actively monitor 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. -### Viewing the Alerts via Alerts Dashboard +### Viewing the alerts via 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: @@ -643,7 +643,7 @@ The `Alert Details` table provides a list of the alerts that are currently trigg 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 +#### 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. @@ -658,7 +658,7 @@ Use fields on the Personalize chart configuration dialog to provide your display 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. -### Managing Alerts +### Managing alerts 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. @@ -675,7 +675,7 @@ Use the `Quick Links` toolbar to open dialogs and tabs that will assist you when Use the table in the `Alerts` section of the `Manage Alerts` tab to create new alerts or manage existing alerts. -#### Alert Templates +#### Alert templates 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. @@ -819,7 +819,7 @@ Use the tabs on the `Alert Templates` dialog to view detailed information about To delete an alert template, select the template name in the alert templates table, and click the `Delete` icon (located to the upper-right corner of the table). The alert history will persist for the length of time specified on the `History Retention` field in the template definition. -#### Audit Log Alerting +#### Audit log alerting PEM provides alert templates that allow you to use the `Alerting` dialog to create an alert that will trigger when an `ERROR` or `WARNING` statement is written to a log file for a specific server or agent. To open the `Alerting` dialog, highlight the name of the server or agent in the PEM client Object browser tree control, and select `Alerting...` from the `Management` menu. @@ -1013,7 +1013,7 @@ Check the `Ignore duplicates` radio button to prevent PEM from updating any exis Click the `Configure Alerts` button to proceed to copy the alerts from the source object to all objects of the same type in, or under those objects selected on the `Copy Alert Configuration` dialog. -#### Schedule Alert Blackout +#### Schedule an 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. @@ -1072,7 +1072,7 @@ Use the `Notification` tab to specify how PEM will behave if an alert is raised. Please note that you must configure the PEM Server to use an SMTP server to deliver email before PEM can send email notifications. -#### Creating an Email Group +#### Creating an email group 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. @@ -1117,7 +1117,7 @@ After creating the email group, you can use the `Manage Alerts` tab to set up th 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. -#### Creating Webhook +#### Creating a webhook 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. @@ -1141,7 +1141,7 @@ Use the `General` tab to define the basic details of the webhook: !!! 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. -#### Defining a Webhook SSL configurations +#### Defining 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 [PEM Agent Configuration Parameters](/pem/latest/pem_agent/03_managing_pem_agent/) section. If you add or remove any of the agent configuration parameters, you must restart the agent to apply them. @@ -1202,7 +1202,7 @@ 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 +#### 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. @@ -1214,7 +1214,7 @@ The delete icon acts as a toggle; you can undo the deletion by clicking the dele Please note that you must configure the PEM Server to send the notifications to an SNMP trap/notification receiver before notifications can be sent. Set the SNMP ver to v1, v2 or v3 to identify the SNMP version. -#### Example - Configure `SNMP V3` traps with `net-snmp` trap receiver. +#### Example - Configure `SNMP V3` traps with `net-snmp` trap receiver - Set `snmp_security_engine_id` to `PEM_SNMP_AGENT` in plain text format in the Server Configuration dialog. @@ -1275,7 +1275,7 @@ The PEM server uses the following rules to evaluate the service status: - 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 +#### 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` tab to specify that (when triggered), a given alert will send an alert notice to Nagios. @@ -1307,7 +1307,7 @@ Four server configuration parameters specify information about your Nagios insta After modifying parameter values, click the save icon (in the upper-right corner of the `Server Configuration` dialog) to preserve your changes. -#### Creating the hosts.cfg and services.cfg File +#### 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. @@ -1323,7 +1323,7 @@ Then, use the following command to create a `services.cfg` file that contains in 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 +#### 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: diff --git a/product_docs/docs/pem/8/pem_ent_feat/06_capacity_manager.mdx b/product_docs/docs/pem/8/pem_ent_feat/06_capacity_manager.mdx index 9bf4bdb3308..7147ba970e2 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/06_capacity_manager.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/06_capacity_manager.mdx @@ -74,7 +74,7 @@ When you have specified the report boundaries and selected the type and destinat Reports saved to file are stored in HTML format. You can review a Capacity Manager report with any web browser that supports Scalable Vector Graphics (SVG). Browsers that do not support SVG will be unable to display a Capacity Manager graph and may include unwanted characters. -## Capacity Manager Templates +## Capacity Manager templates After defining a report, you can save the 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: diff --git a/product_docs/docs/pem/8/pem_ent_feat/07_audit_manager.mdx b/product_docs/docs/pem/8/pem_ent_feat/07_audit_manager.mdx index e0475c4b865..9b7d7e31cff 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/07_audit_manager.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/07_audit_manager.mdx @@ -22,7 +22,7 @@ Audit logs may include the following activities: Once the audit logs are stored on the PEM server, you can use the Audit Log dashboard to review the information in an easy-to-read form. The Audit Log dashboard allows you to filter the log file by timestamp range (when an activity occurred), the database on which the activity occurred, the user performing the activity, or the type of command being invoked. -## Setting the Advanced Server Instance Service ID +## Setting the Advanced Server instance service ID To configure logging for an Advanced Server instance, the server must be a PEM-managed server with a bound agent, and the server registration must include the name of a service script. When registering a new server, include the service name in the Service ID field on the Advanced tab of the New Server dialog. @@ -41,7 +41,7 @@ The Service ID field allows the PEM server to stop and start the service. - The name of the PostgreSQL 9.6 service script is `postgresql-10`. - The name of the PostgreSQL 9.6 service script is `postgresql-9.6`. -## Setting the EDB Audit Configuration Probe +## Setting the EDB Audit Configuration probe Before configuring audit logging of Advanced Server servers, you must ensure that the EDB Audit Configuration probe is enabled. To open the `Manage Probes` tab and check the status of the probe, right click on the name of a registered Advanced Server server in the tree control, and select `Manage Probes...` from the `Management` menu. @@ -51,7 +51,7 @@ Ensure that the `Enabled` column in the `Probe Configuration` dialog is set to ` If EDB Audit Configuration is not enabled, use the `Enabled?` switch on the Manage Probes tab to enable it. -## Configuring Audit Logging with the Audit Manager +## Configuring audit logging with the Audit Manager To open the `Audit manager` wizard, select `Audit Manager...` from the `Management` menu. The `Audit manager - Welcome` dialog opens. @@ -162,7 +162,7 @@ The Audit Manager will schedule a job to apply the configuration to each server. You can use the `Scheduled Tasks` tab to review a list of Scheduled jobs. To open the `Scheduled Tasks` tab, highlight the name of a server or agent and select `Scheduled Tasks...` from the `Management` menu. -## Viewing the Log with the Audit Log Dashboard +## Viewing the log with the Audit Log dashboard Use the Audit Log dashboard to view the audit log from Advanced Server database instances. diff --git a/product_docs/docs/pem/8/pem_ent_feat/08_log_manager.mdx b/product_docs/docs/pem/8/pem_ent_feat/08_log_manager.mdx index 659893f6b58..c0d049a948d 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/08_log_manager.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/08_log_manager.mdx @@ -162,7 +162,7 @@ Note that when you apply the configuration changes specified by the Log Manager Click `Finish` to exit the wizard, and either restart the server, or schedule the server restart for the time specified on the scheduling dialog. -## Reviewing the Server Log Analysis Dashboard +## Reviewing the Server Log Analysis dashboard After invoking the Log Manager wizard, and importing your log files to PEM, you can use the `Server Log Analysis` dashboard to review the log files for a selected server. To open 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`. @@ -235,7 +235,7 @@ You can choose the default option and select `Finish` to view the Log Analysis E If you have specified that the report should be saved to a file, the report will be downloaded. -## Reviewing the Postgres Log Analysis Expert Report +## Reviewing the Postgres Log Analysis Expert report If you've elected to review the report immediately, the Postgres Log Analysis Expert report will be displayed in the PEM Client window. The report header displays the date and time that the report was generated, the time period that the report spans, and the aggregation method specified when defining the report. The name of the server for which information is displayed is noted at the start of each section of the report. diff --git a/product_docs/docs/pem/8/pem_ent_feat/09_sql_profiler.mdx b/product_docs/docs/pem/8/pem_ent_feat/09_sql_profiler.mdx index 98290430909..c0a02403b0d 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/09_sql_profiler.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/09_sql_profiler.mdx @@ -1,5 +1,5 @@ --- -title: "SQL Profiling and Analysis" +title: "SQL profiling and analysis" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/sql_profiler.html" @@ -29,11 +29,11 @@ Please note: if you have connected to the PEM server with the PEM client before -## Creating a New SQL Trace +## Creating a new SQL trace SQL Profiler captures and displays a specific SQL workload for analysis in a SQL trace. You can start and review captured SQL traces immediately, or save captured traces for review at a later time. You can use SQL Profiler to create and store up to 15 named traces; use menu options to create and manage traces. -### Creating a Trace +### Creating a trace You can use the `Create trace...` dialog to define a SQL Trace for any database on which SQL Profiler has been installed and configured. installed and configured. To access the dialog, highlight the name of the database in the PEM client tree control; navigate through the Management menu to the SQL Profiler pull-aside menu, and select Create trace.... @@ -74,7 +74,7 @@ When you've completed the `Create trace...` dialog, click `Create` to start the If you elect to execute the trace immediately, the trace results will display in the PEM client. -### Opening an Existing Trace +### Opening an existing trace To view a previous trace, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Open trace....` You can also use the `SQL Profiler toolbar` menu to open a trace; select the `Open trace...` option. The Open trace... dialog opens. @@ -82,7 +82,7 @@ To view a previous trace, highlight the name of the profiled database in the PEM Highlight an entry in the trace list and click Open to open the selected trace. The selected trace opens in the SQL Profiler tab. -### Filtering a Trace +### Filtering a trace A filter is a named set of (one or more) rules, each of which can hide events from the trace view. When you apply a filter to a trace, the hidden events are not removed from the trace, but are merely excluded from the display. @@ -108,7 +108,7 @@ When you've finished defining a rule, click the Add (+) icon to add another rule Click the `Save` button to save the filter definition to a file without applying the filter; to apply the filter, click `OK`. Select `Cancel` to exit the dialog and discard any changes to the filter. -### Deleting a Trace +### Deleting a trace To delete a trace, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Delete trace(s)....` You can also use the SQL Profiler toolbar menu to delete a trace; select the `Delete trace(s)...` option. The `Delete traces` dialog opens. @@ -116,7 +116,7 @@ To delete a trace, highlight the name of the profiled database in the PEM client Click the icon to the left of a trace name to mark one or more traces for deletion and click `Delete`. The PEM client will acknowledge that the selected traces have been deleted. -### Viewing Scheduled Traces +### Viewing scheduled traces To view a list of scheduled traces, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Scheduled traces...` You can also use the SQL Profiler toolbar menu to the list; select the `Scheduled traces...` option. @@ -132,7 +132,7 @@ The `Scheduled traces...` dialog displays a list of the traces that are awaiting - The `Next run` field displays the date and time of the next scheduled trace. - The `Created` field displays the date and time that the trace was defined. -## Using the Index Advisor +## Using the index advisor Index Advisor is distributed with Advanced Server 9.0 and above. Index Advisor works with SQL Profiler by examining collected SQL statements and making indexing recommendations for any underlying tables to improve SQL response time. The Index Advisor works on all DML (INSERT, UPDATE, DELETE) and SELECT statements that are invoked by a superuser. diff --git a/product_docs/docs/pem/8/pem_ent_feat/11_postgres_expert.mdx b/product_docs/docs/pem/8/pem_ent_feat/11_postgres_expert.mdx index 1bef078f465..8d23d20d44f 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/11_postgres_expert.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/11_postgres_expert.mdx @@ -1,5 +1,5 @@ --- -title: "Postgres Expert - Best Practice Enforcement" +title: "Postgres Expert - best practice enforcement" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/postgres_expert.html" @@ -13,7 +13,7 @@ The Postgres Expert utility provides expert advice on how to best configure your You can select specific rules for each Expert to analyze, or accept all rules, and then review Postgres Expert reports detailing any best practice issues that require your attention. -## Using the Postgres Expert Wizard +## Using the Postgres Expert wizard To use the Postgres Expert wizard select the `Postgres Expert` option from the `Management` menu in the PEM client. When the wizard's `Welcome` window opens, click `Next` to continue. @@ -47,7 +47,7 @@ Select or de-select the servers and databases that you would like Postgres Exper You can select the default option and click `Finish` to view an onscreen report from Postgres Expert, or check the box next to Download the report to save a copy of the report to an HTML file for later use. If you choose to save the report to a file, the download will begin immediately. The file will be saved in your default download directory. -## Reviewing Postgres Expert Recommendations +## Reviewing Postgres Expert recommendations Postgres Expert produces an easily navigated report that contains an analysis of the selected rules, categorized by high, medium, and low severities, for the selected servers. diff --git a/product_docs/docs/pem/8/pem_ent_feat/12_reports.mdx b/product_docs/docs/pem/8/pem_ent_feat/12_reports.mdx index 7192ea22d5d..22b910fac2d 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/12_reports.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/12_reports.mdx @@ -52,7 +52,7 @@ The `Group: PEM Server Directory`, provides details about: Please note that here `Group Server Name` depends on the group name to which the server is added. -## Core Usage Report +## Core Usage report The Core Usage report provides detailed information about number of cores specific to: diff --git a/product_docs/docs/pem/8/pem_ent_feat/13_monitoring_failover_manager.mdx b/product_docs/docs/pem/8/pem_ent_feat/13_monitoring_failover_manager.mdx index f9695171f7d..eb591081412 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/13_monitoring_failover_manager.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/13_monitoring_failover_manager.mdx @@ -40,7 +40,7 @@ The `Failover Manager Node Status` table displays information about each node of - 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. -## Replacing a Primary Node +## Replacing a primary node You can use the PEM client to replace the Primary node of a Failover Manager cluster with a replica node. To initiate the failover process, select `Replace Cluster Primary` from `Server` under the `Tools` menu. A dialog opens, asking you to confirm that you wish to replace the current primary node. @@ -52,7 +52,7 @@ Select `Yes` to remove the current primary node from the Failover Manager cluste 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 +## Switchover EFM cluster You can use the PEM client to replace 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. diff --git a/product_docs/docs/pem/8/pem_ent_feat/14_monitoring_xdb_replication_cluster.mdx b/product_docs/docs/pem/8/pem_ent_feat/14_monitoring_xdb_replication_cluster.mdx index fe936a828ee..52e894bdf14 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/14_monitoring_xdb_replication_cluster.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/14_monitoring_xdb_replication_cluster.mdx @@ -1,5 +1,5 @@ --- -title: "Monitoring an xDB Replication Cluster" +title: "Monitoring an xDB Replication cluster" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/enterprise-features-guide/8.0/monitoring_xdb_replication_cluster.html" diff --git a/product_docs/docs/pem/8/pem_ent_feat/16_reference.mdx b/product_docs/docs/pem/8/pem_ent_feat/16_reference.mdx index ac17d459096..34de52dcebe 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/16_reference.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/16_reference.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: The following sections are provided for reference; please note that the items referred to in the following tables are subject to change. -## PEM Server Configuration Parameters - Reference +## PEM server configuration parameters - reference You can use global configuration options to modify aspects of the PEM Server's behavior. Please note that the list of configuration parameters is subject to change. @@ -148,7 +148,7 @@ You can use global configuration options to modify aspects of the PEM Server's b | snmp_privacy_password | | Specifies the privacy password associated with security name mentioned in snmp_security_name. Used only for SNMPv3. | | webclient_help_pg | EDB hosted documentation | Specifies the location of the online PostgreSQL core documentation. | -## Capacity Manager Metrics - Reference +## Capacity Manager metrics - reference Please Note that the Capacity Manager metrics available will vary by platform, and are subject to change. The available metrics may include the metrics described in the table below. @@ -273,7 +273,7 @@ Please Note that the Capacity Manager metrics available will vary by platform, a !!! 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. -## PEM Probes – Reference +## PEM probes – reference 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 dashboard. 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. @@ -330,13 +330,13 @@ A probe is a scheduled task that retrieves information about the database object | 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 +## 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 +### Templates applicable on agent | Template Name | Description | | ---------------------------------------------------------------------- | --------------------------------------------------------------------------- | @@ -372,7 +372,7 @@ The tables that follow list the system-defined alert templates that you can use | 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 +### Templates applicable on server | Template Name | Description | | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -457,7 +457,7 @@ The tables that follow list the system-defined alert templates that you can use | 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 +### Templates applicable on database | Template Name | Description | | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | @@ -525,7 +525,7 @@ The tables that follow list the system-defined alert templates that you can use | View Count | Total number of views in database. | | Materialized View Count | Total number of materialized views in database. | -### Templates applicable on Schema +### Templates applicable on schema | Template Name | Description | | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | @@ -565,7 +565,7 @@ The tables that follow list the system-defined alert templates that you can use | 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 +### Templates applicable on table | Template Name | Description | | ----------------------------------------- | ---------------------------------------------------------------------------------------------- | @@ -590,7 +590,7 @@ The tables that follow list the system-defined alert templates that you can use | 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 +### Global templates | Template Name | Description | | ------------- | --------------------------------------------------- | diff --git a/product_docs/docs/pem/8/pem_ent_feat/17_monitoring_BDR_nodes.mdx b/product_docs/docs/pem/8/pem_ent_feat/17_monitoring_BDR_nodes.mdx index fe8db53841e..251e55cb2d8 100644 --- a/product_docs/docs/pem/8/pem_ent_feat/17_monitoring_BDR_nodes.mdx +++ b/product_docs/docs/pem/8/pem_ent_feat/17_monitoring_BDR_nodes.mdx @@ -1,5 +1,5 @@ --- -title: "Monitoring BDR Nodes" +title: "Monitoring BDR nodes" --- !!! Tip "New Feature " diff --git a/product_docs/docs/pem/8/pem_ha_setup/index.mdx b/product_docs/docs/pem/8/pem_ha_setup/index.mdx index 717bffc4df5..dc796f302b1 100644 --- a/product_docs/docs/pem/8/pem_ha_setup/index.mdx +++ b/product_docs/docs/pem/8/pem_ha_setup/index.mdx @@ -1,5 +1,5 @@ --- -navTitle: High Availability Set Up +navTitle: High availability set up title: "PEM High Availability Setup Guide" --- diff --git a/product_docs/docs/pem/8/pem_ha_setup/setup_ha_using_efm.mdx b/product_docs/docs/pem/8/pem_ha_setup/setup_ha_using_efm.mdx index 8a538097d77..cbea5e06116 100644 --- a/product_docs/docs/pem/8/pem_ha_setup/setup_ha_using_efm.mdx +++ b/product_docs/docs/pem/8/pem_ha_setup/setup_ha_using_efm.mdx @@ -1,5 +1,5 @@ --- -title: "High Availability Using Failover Manager" +title: "High availability using Failover Manager" --- Postgres Enterprise Manager (PEM) assists database administrators, system architects, and performance analysts in administering, monitoring, and tuning Postgres database servers. @@ -20,7 +20,7 @@ The following needs to use the VIP address: - Accessing the PEM Web Client - Accessing the Webserver services -# Initial Product Installation and Configuration +## Initial product installation and configuration 1. Install the following on the primary and one or more standbys: @@ -63,7 +63,7 @@ The following needs to use the VIP address: success ``` -# Set Up the Primary Node for Streaming Replication. +## Set up the primary node for streaming replication 1. Create the replication role using the following command. @@ -115,7 +115,7 @@ The following needs to use the VIP address: systemctl restart edb-as-13.service ``` -# Set Up the Standby Nodes for Streaming Replication +## Set up the standby nodes for streaming replication 1. Stop the service for EPAS 13 on all the standby nodes: @@ -248,7 +248,7 @@ systemctl disable httpd At this point you should have a PEM Primary Server and two standbys that are ready to take over from the primary whenever needed. -# Set Up EFM to Manage Failover on All Hosts +## Set up EFM to manage failover on all hosts 1. Prepare the Primary Node to support EFM: @@ -495,7 +495,7 @@ This status confirms that EFM is set up successfully and managing the failover f In case of failover, any of the standbys get promoted as the primary node. PEM Agents automatically connect to the new primary node. You can replace the failed primary node with a new standby using this procedure. -# Current Limitations +## Current limitations The current limitations include: - Web console sessions for the users are lost during the switch over. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx index a1a89ee77ff..1a29eafb7ac 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/02_pem_hardware_software_requirements.mdx @@ -1,5 +1,5 @@ --- -title: "PEM - Hardware and Software Requirements" +title: "PEM - hardware and software requirements" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/pem_hardware_software_requirements.html" @@ -7,7 +7,7 @@ legacyRedirectsGenerated: -## Hardware Prerequisites +## Hardware prerequisites For optimum performance when monitoring servers and rendering dashboards, we recommend installing PEM on a system with at least: @@ -17,13 +17,13 @@ For optimum performance when monitoring servers and rendering dashboards, we rec 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 +## Software prerequisites **Platforms and Versions Support** For information about the platforms and versions supported by PEM, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#pem). -**Modifying the pg_hba.conf File** +**Modifying the pg_hba.conf file** The `pg_hba.conf` file manages connections for the Postgres server. You must ensure that the `pg_hba.conf` file on each monitored server allows connections from the PEM server, the monitoring PEM Agent, and the host of the PEM-HTTPD server. @@ -31,10 +31,10 @@ For information about modifying the `pg_hba.conf` file, see the [PEM Administrat Information about managing authentication is also available in the [Postgres core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html). -**Firewall Restrictions** +**Firewall restrictions** Please note that you must adjust your firewall to allow communication between PEM components. -**Supported Locales** +**Supported locales** Currently, the PEM server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale, or a separator character other than a period may result in errors. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/03_pem_architecture.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/03_pem_architecture.mdx index 15a7e77db0f..ebd076d971c 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/03_pem_architecture.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/03_pem_architecture.mdx @@ -1,5 +1,5 @@ --- -title: "PEM Architecture" +title: "PEM architecture" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/pem_architecture.html" @@ -28,7 +28,7 @@ The following architectural diagram illustrates the relationships between the PE PEM Architecture -## The PEM Server +## The PEM server ![PEM Server](../images/pem_server.png) @@ -56,7 +56,7 @@ The instance of Postgres (a database server) and an instance of the Apache web-s 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 ![PEM Agent](../images/pem_agent.png) @@ -89,13 +89,13 @@ The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in t To see more information about these parameters see [Server Configuration](../pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options/). -## The PEM Web Client +## 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 +## 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. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx index e9b26d89932..65bdfd221c9 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx @@ -1,5 +1,5 @@ --- -title: "Prerequisites for Installing the PEM Server on Linux Platforms" +title: "Prerequisites for installing the PEM server on Linux platforms" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/prerequisites_for_installing_pem_server.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/02_installing_pem_server_and_apache_web_server_preferences.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/02_installing_pem_server_and_apache_web_server_preferences.mdx index 0a681ab9f6d..9afc44d16cc 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/02_installing_pem_server_and_apache_web_server_preferences.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/02_installing_pem_server_and_apache_web_server_preferences.mdx @@ -1,5 +1,5 @@ --- -title: "Web Server Hosting Preferences" +title: "Web server hosting preferences" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/installing_pem_server_and_apache_web_server_preferences.html" @@ -7,15 +7,15 @@ legacyRedirectsGenerated: During the PEM server installation, you can specify your hosting preferences for the Apache Web Server: -## To install the PEM Server and Apache Web Server on the same host +## To install the PEM server and Apache web server on the same host -1. Install the PEM Server, for steps see [Installing the PEM Server on Linux](03_installing_pem_server_using_edb_repository). -2. Run the configuration script, select the `Web Services and Database` option to install PEM Server and Apache Web Server on the same host, for steps see [Configuring the PEM Server on Linux Platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). +1. Install the PEM Server, for steps see [Installing the PEM server on Linux](03_installing_pem_server_using_edb_repository). +2. Run the configuration script, select the `Web Services and Database` option to install PEM Server and Apache Web Server on the same host, for steps see [Configuring the PEM server on Linux platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). ## To install the PEM Server and Apache Web Server on separate hosts -1. Install the PEM Server on both the hosts, for steps see [Installing the PEM Server on Linux](03_installing_pem_server_using_edb_repository). +1. Install the PEM Server on both the hosts, for steps see [Installing the PEM server on Linux](03_installing_pem_server_using_edb_repository). 2. Configure the PEM Server host by selecting the `Database` option on the first host. 3. Configure an Apache Web Server by selecting the `Web Services` option on the second host. -For detailed information about configuring a PEM Server, see [Configuring the PEM Server on Linux Platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). +For detailed information about configuring a PEM Server, see [Configuring the PEM server on Linux platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/index.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/index.mdx index 1ffada62d1e..ae95e611064 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/index.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_using_edb_repository/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PEM Server Using EDB Repository" +title: "Installing the PEM server using the EDB repository" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/installing_pem_server_on_linux.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network.mdx index 6c927849918..827583e2906 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network.mdx @@ -1,5 +1,5 @@ --- -title: "Creating a PEM Repository on an Isolated Network" +title: "Creating a PEM repository on an isolated network" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/creating_pem_repository_in_isolated_network.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/05_configuring_the_pem_server_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/05_configuring_the_pem_server_on_linux.mdx index 60438829e0c..a40e50a16c2 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/05_configuring_the_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/05_configuring_the_pem_server_on_linux.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Server on Linux Platforms" +title: "Configuring the PEM server on Linux platforms" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/configuring_the_pem_server_on_linux.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx index a68d53efe5f..e93378092cc 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Server to use Kerberos Authentication" +title: "Configuring the PEM server to use Kerberos authentication" --- !!! Tip "New Feature " @@ -18,7 +18,7 @@ title: "Configuring the PEM Server to use Kerberos Authentication" Follow the steps to configure the Kerberos Authentication for the PEM Server: -## 1. Install Kerberos, the PEM Server and the PEM Backend Database +## 1. Install Kerberos, the PEM server and the PEM backend database - Install the Kerberos on the machine that functions as the authentication server. @@ -26,7 +26,7 @@ Follow the steps to configure the Kerberos Authentication for the PEM Server: - Install the PEM Backend Database (Postgres/EDB Postgres Advanced Server) on same or different machine as PEM Server. For more information see the Installation guides on [EDB Docs Website](https://www.enterprisedb.com/docs). -## 2. Adding Principals on Kerberos Server +## 2. Adding principals on Kerberos server - Add the principals for the PEM Web application deployed under an Apache Web Server (HTTPD/Apache2) and the PEM Backend Database Server (PostgreSQL/EDB Postgres Advanced Server). @@ -40,7 +40,7 @@ Where, `HOSTNAME_OF_PEM_SERVER` must contain the `REALM` of the `Kerberos Server !!! Note - If the PEM Web Application and the PEM Backend Database Server are on different machines, then hostname for both will be different. -## 3. Extract Key Tables from Kerberos Server +## 3. Extract Key Tables from Kerberos server a. Extract the Key Tables from Kerberos for the PEM Web Application and the PEM Backend Database Server: @@ -75,7 +75,7 @@ chown enterprisedb /.keytab - `OS_USERNAME_ON_PEM_SERVER` is the name of the operating system user on the PEM Server. - `DATA_DIRECTORY_OF_POSTGRES` is the path of the data directory of the installed postgres (PostgreSQL/EDB Postgres Advanced Server). -## 4. Configure the PEM Backend Database Server +## 4. Configure the PEM backend database server - Add the Key Table location in `postgresql.conf` file @@ -137,7 +137,7 @@ It will display the principal along with the Kerberos ticket. !!! Note The `USERNAME@REALM` specified here must be a database user having the `pem_admin` role and `CONNECT` privilege on `pem` database. -## 6. Configure the PEM Server +## 6. Configure the PEM server - Run the PEM configure script on the PEM Server to use Kerberos Authentication @@ -189,7 +189,7 @@ It will display the principal along with the Kerberos ticket. If you are using PostgreSQL OR EDB Postgres Advanced Server 12 or later then you can specify connection type as `hostgssenc` to allow only gss encrypted connection. -## 7. Browser Settings +## 7. Browser settings Configure the Browser on the Client machine to access the PEM Web Client to use the `Spnego/Kerberos`. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_1_configuring_2fa_authentication.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_1_configuring_2fa_authentication.mdx index 0161122f5f6..f2f858a9d3f 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_1_configuring_2fa_authentication.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_1_configuring_2fa_authentication.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Server to use Two-Factor Authentication" +title: "Configuring the PEM server to use two-factor authentication" --- !!! Tip "New Feature " @@ -19,7 +19,7 @@ To enable 2FA, you can copy these settings from the `config.py` file to the `con | MFA_SUPPORTED_METHODS | Set to `email` to use the email authentication method (send a one-time code by email) or `authenticator` to use the TOTP-based application authentication method. | | MFA_EMAIL_SUBJECT | Set this to the subject of the email for email authentication. Default value is ` - Verification Code`. | -# Mail Server configuration +## Mail server configuration To use the email authentication method, you need to configure Mail Server Settings. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx index ac20779ff81..2576e69f85d 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Server to use Windows Active Directory Domain Services for Kerberos Authentication (SSPI)" +title: "Configuring the PEM server to use Windows Active Directory Domain Services for Kerberos authentication (SSPI)" --- - The Windows Active Directory Domain Services works with hostnames and not with `ip addresses`. To use single sign-on in PEM Server using `Active Directory Domain Services`, the following machines must be configured with hostnames using the DNS. @@ -11,7 +11,7 @@ title: "Configuring the PEM Server to use Windows Active Directory Domain Servic Follow the steps to configure the Kerberos Authentication for the PEM Server: -## 1. Install Active Directory, the PEM Server, and the PEM Backend Database Server +## 1. Install Active Directory, the PEM server, and the PEM backend database server - Install the Active Directory on the Windows Server (Domain Controller) that functions as the authentication server. Also, configure the Active Directory Domain Services to use Kerberos Authentication and it should be up and running. @@ -19,7 +19,7 @@ Follow the steps to configure the Kerberos Authentication for the PEM Server: - Install the PEM Backend Database (Postgres/EDB Postgres Advanced Server) on the same or different Linux machine as the PEM Server. For more information, see the Installation guides on [EDB Docs Website](https://www.enterprisedb.com/docs). -## 2. Create Users in Active Directory to map with Service Principals +## 2. Create users in Active Directory to map with service principals - Create user in Active directory of Windows Server to map with the HTTP Service Principal for the PEM Web Application. @@ -103,7 +103,7 @@ chown enterprisedb /pemdb.keytab - `OS_USERNAME_ON_PEM_SERVER` is the name of the operating system user on the PEM Server. - `DATA_DIRECTORY_OF_POSTGRES` is the path of the data directory of the installed postgres (PostgreSQL/EDB Postgres Advanced Server). -## 4. Configure the PEM Backend Database Server +## 4. Configure the PEM backend database server - Add the Key Table location in `postgresql.conf` file @@ -163,7 +163,7 @@ It will display the principal along with the kerberos ticket. !!! Note The `USERNAME@REALM` specified here must be a database user having the `pem_admin` role and `CONNECT` privilege on `pem` database. -## 6. Configure the PEM Server +## 6. Configure the PEM server - Run the PEM configure script on the PEM Server to use Kerberos Authentication @@ -214,7 +214,7 @@ It will display the principal along with the kerberos ticket. !!! Note You cannot specify connection type as `hostgssenc` as windows does not support gss encrypted connection. -## 7. Browser Settings +## 7. Browser settings Configure the Browser on the Client machine to access the PEM Web Client to use the `Spnego/Kerberos`. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_using_edb_repository/index.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_using_edb_repository/index.mdx index 5071de3589f..b1418b8d560 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_using_edb_repository/index.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_using_edb_repository/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PEM Agent Using EDB Repository" +title: "Installing the PEM agent using the EDB repository" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/installing_pem_server_on_linux.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx index d035dc243b8..11ef081dd6e 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx @@ -1,11 +1,11 @@ --- -title: "Registering and Unregistering a PEM Agent" +title: "Registering and unregistering a PEM agent" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/registering_a_pem_agent.html" --- -## Registering a PEM Agent +## Registering a PEM agent Each PEM Agent installed on a separate host (different from the PEM Server host) must be *registered* with the PEM Server. The registration process provides the PEM server with the information it needs to communicate with the Agent. You can use the `pemworker` utility to register the Agent if you use the package to install a PEM Agent. @@ -57,7 +57,7 @@ Before any changes are made on the PEM database, the connecting agent is authent 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. -## Unregistering a PEM Agent +## Unregistering a PEM agent You can use the pemworker utility to unregister a PEM Agent. To unregister an Agent, include the `--unregister-agent` keywords along with the details when invoking the `pemworker` utility: @@ -73,7 +73,7 @@ Append command line options to the command string when invoking the pemworker ut | `--config-dir` | Specifies the directory path where configuration file can be found. The default is the `"/../etc"`. | -## Setting PEM Agent Configuration Parameters +## Setting PEM agent configuration parameters The PEM Agent native package 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`). Modify the `agent.cfg` file, changing the following configuration parameter value to `true`: diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/index.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/index.mdx index c522ad97a92..a0299a1efc6 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/index.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/index.mdx @@ -9,14 +9,10 @@ The `edb-pem` package for Linux platforms installs the PEM Server, a PEM Agent, The PEM server uses a Postgres installation and backend database to manage data. The `pem` backend database is created when you configure PEM. -For detailed information about installing the PEM Server, see [Installing the PEM Server on Linux](03_installing_pem_server_using_edb_repository). For information about configuring a PEM Server see [Configuring the PEM Server on Linux](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). +For detailed information about installing the PEM Server, see [Installing the PEM server on Linux](03_installing_pem_server_using_edb_repository). For information about configuring a PEM Server see [Configuring the PEM server on Linux](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). -The PEM Agent that is installed with the PEM server is capable of monitoring multiple servers that reside on the same host, or on remote hosts. Please note that the PEM functionality on servers monitored by a remote Agent may be limited. For detailed information about remote monitoring functionality see the [PEM Agent Privileges](/pem/latest/pem_online_help/02_toc_pem_agent/05_pem_agent_privileges/). +The PEM Agent that is installed with the PEM server is capable of monitoring multiple servers that reside on the same host, or on remote hosts. Please note that the PEM functionality on servers monitored by a remote Agent may be limited. For detailed information about remote monitoring functionality see the [PEM agent privileges](/pem/latest/pem_online_help/02_toc_pem_agent/05_pem_agent_privileges/). -For detailed information about installing and configuring a PEM Agent, see [Installing the PEM Agent on Linux](08_installing_pem_agent_using_edb_repository). +For detailed information about installing and configuring a PEM Agent, see [Installing the PEM agent on Linux](08_installing_pem_agent_using_edb_repository). -
-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 configuring_the_pem_server_to_use_kerberos_authentication configuring_the_pem_server_to_use_windows_kerberos_server installing_pem_agent_on_linux registering_a_pem_agent - -
diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/05_the_pem_web_interface.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/05_the_pem_web_interface.mdx index 0f8c630a081..d1dda4e3edd 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/05_the_pem_web_interface.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/05_the_pem_web_interface.mdx @@ -1,5 +1,5 @@ --- -title: "The PEM Web Interface" +title: "The PEM web interface" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/the_pem_web_interface.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx index 6f0f0644543..89a641bafa4 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx @@ -1,5 +1,5 @@ --- -title: "Uninstalling Postgres Enterprise Manager Components" +title: "Uninstalling Postgres Enterprise Manager components" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/uninstalling_pem_components.html" @@ -12,7 +12,7 @@ If you uninstall the PEM server package from a host, the PEM Agent package insta !!! Note Before uninstalling the PEM Agent, you need to de-register the agent first. You can de-register the agent using the `pemworker` command-line utility. After that, you can proceed with the uninstallation steps. -## Uninstalling PEM components from CentOS or RHEL or Rocky Linux or AlmaLinux Hosts +## Uninstalling PEM components from CentOS or RHEL or Rocky Linux or AlmaLinux hosts You can use variations of the `rpm`, `yum remove`, or `yum erase` commands to remove the installed packages from CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx index 4e51946b014..324f6650192 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx @@ -1,5 +1,5 @@ --- -title: "Reference - Linux Service Script" +title: "Reference - Linux service script" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/linux-installation-guide/8.0/reference_linux_service_script.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx index 2cbcb3e7863..cdad003d3ef 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/02_pem_hardware_software_requirements.mdx @@ -1,11 +1,11 @@ --- -title: "PEM - Hardware and Software Requirements" +title: "PEM - hardware and software requirements" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/pem_hardware_software_requirements.html" --- -## Hardware Prerequisites +## Hardware prerequisites For optimum performance when monitoring servers and rendering dashboards, we recommend installing PEM on a system with at least: @@ -15,9 +15,9 @@ For optimum performance when monitoring servers and rendering dashboards, we rec 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 +## Software prerequisites -**Supported Platforms and Versions** +**Supported platforms and versions** For information about the platforms and versions supported by PEM, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#pem). diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/03_pem_architecture.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/03_pem_architecture.mdx index 32aff3e3697..7b9fd359000 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/03_pem_architecture.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/03_pem_architecture.mdx @@ -1,5 +1,5 @@ --- -title: "PEM Architecture" +title: "PEM architecture" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/pem_architecture.html" @@ -27,7 +27,7 @@ The following architectural diagram illustrates the relationships between the PE ![PEM Architecture](../images/pem_architecture.png) -## The PEM Server +## The PEM server ![PEM Server](../images/pem_server.png) @@ -53,7 +53,7 @@ The instance of Postgres (a database server) and an instance of the Apache web-s 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 ![PEM Agent](../images/pem_agent.png) @@ -84,13 +84,13 @@ The Alert processing, SNMP/SMTP spoolers, and Nagios Spooler data is stored in t To see more information about these parameters see [Server Configuration](../pem_online_help/04_toc_pem_features/02_pem_server_config/01_pem_config_options/). -## The PEM Web Client +## 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 +## 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. diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01.1_configuring_2fa_authentication.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01.1_configuring_2fa_authentication.mdx index 4963ccfd4fd..5e86a033281 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01.1_configuring_2fa_authentication.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01.1_configuring_2fa_authentication.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Server to use Two-Factor Authentication" +title: "Configuring the PEM server to use two-factor authentication" --- !!! Tip "New Feature " diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01_installing_pem_server_on_windows.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01_installing_pem_server_on_windows.mdx index f146af94a7a..34f866951cb 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01_installing_pem_server_on_windows.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/01_installing_pem_server_on_windows.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the PEM Server on Windows" +title: "Installing the PEM server on Windows" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/installing_pem_server_on_windows.html" @@ -28,7 +28,7 @@ You can use the web interface to review information about objects that reside on !!! Note If you are using the SSL certificates then make sure that all the SSL certificates are inside the data directory the backend database server. If the certificates are not inside the data directory then the PEM Server's configuration may fail as it looks in to the data directory while configuring the PEM Server. -## Installing the PEM Server and PEM-HTTPD on the Same Host +## Installing the PEM server and PEM-HTTPD on the same host The easiest PEM server installation configuration consists of a PEM backend database server (hosted on a PostgreSQL database installed with the PEM server installer) and a PEM-HTTPD service that reside on the same host. In this configuration, the PEM server installer will provide the pre-requisite software for the backend host register the service (on Windows). @@ -103,7 +103,7 @@ Click `OK` to acknowledge that the webservice has been configured, and that the ![PEM server Wizard - Installation Finish dialog](../../images/pem_server_on_same_host_installation_complete.png) -## Installing the PEM Server and PEM-HTTPD on Separate Hosts +## Installing the PEM server and PEM-HTTPD on separate hosts To use separate hosts for the PEM server backend database and PEM-HTTPD, you must: @@ -146,7 +146,7 @@ This option invokes the installation steps documented in [Installing Web Service After selecting an installation option, click `Next` to continue. -### Specifying a Database Host +### Specifying a database host Selecting the `Database` option on the `Advanced options` dialog allows you to specify connection information for the host on which the PEM server backend database (named `pem`) will reside. @@ -216,7 +216,7 @@ Click `OK` to acknowledge that the `pem` database has been created, and continue When the database portion of the PEM server installation is complete, you can invoke the PEM server on another host to install (or upgrade) PEM-HTTPD. -### Installing Web Services +### Installing web services Selecting the `Web Services` radio button on the `Advanced options` dialog instructs the PEM server installer to either install PEM-HTTPD on the current host or update an existing PEM-HTTPD installation. @@ -257,7 +257,7 @@ Use the fields on the `Database Server Installation Details` dialog to provide c Click `Next` to continue. Before completing the PEM server installation, the installer will contact the database host. The `pg_hba.conf` file on the PEM database host must be configured to accept connections from the host of the httpd server and the firewall must allow a connection for the installation to continue. The PEM server installer will complete the PEM server installation, adding only those items that must reside on the host of the PEM-HTTPD server. -## Installing the PEM Server on an Existing Postgres Server +## Installing the PEM server on an existing Postgres server You can use an existing Postgres server (version 11 or later) to host the PEM server and the `pem` database. Postgres installers and pre-requisite software extensions are freely available on the [EnterpriseDB website](https://www.enterprisedb.com/downloads). @@ -271,7 +271,7 @@ The following versions of Postgres are pre-configured to contain the `sslutils` - PostgreSQL 11 or later (as bundled with the PEM Server installer) - Advanced Server 11 or later -### Preparing the Postgres Server +### Preparing the Postgres server Before installing the PEM server on an existing Postgres server, you must: @@ -280,7 +280,7 @@ Before installing the PEM server on an existing Postgres server, you must: After preparing the server, you can use the PEM server installer to install PEM on the existing Postgres server. -### Installing the sslutils Extension +### Installing the sslutils extension The Postgres server on which the PEM server will reside must contain the `sslutils` extension. The `sslutils` package is freely available for download from the [EDB website](https://www.enterprisedb.com/downloads/modified-gpl-source-code) @@ -345,7 +345,7 @@ While specific details of the installation process will vary by platform and com COPY sslutils.dll "%PGPATH%\lib\" ``` -### Registering the Service +### Registering the service When you install a PostgreSQL or an Advanced Server database using an installer from EnterpriseDB, the installer will register the service for you. @@ -370,7 +370,7 @@ For more information about using the `pg_ctl` command and the available command [Postgres core documentation](http://www.postgresql.org/docs/current/static/app-pg-ctl.html) -### Invoking the PEM Server Installer +### Invoking the PEM server installer After preparing the existing Postgres server, invoke the PEM server installer. Assume Administrative privileges and navigate into the directory that contains the installer. Then, invoke the installer with the command: @@ -478,7 +478,7 @@ If you are using a PEM-HTTPD service that resides on a separate host, you must: - Modify the `pg_hba.conf` file on the Postgres server host to allow connections between the hosts. - Invoke the PEM server installer on the host of the PEM-HTTPD server. See [Installing Web Services](#installing-web-services) section for more information about installing PEM-HTTPD. -## Invoking the Server Installer from Command Line +## Invoking the server installer from the command line The command line options of the PEM server and PEM agent installers offer functionality in situations where a graphical installation may not work because of limited resources or system configuration. You can: @@ -486,7 +486,7 @@ The command line options of the PEM server and PEM agent installers offer functi Not all command line options are suitable for all platforms. For a complete reference guide to the command line options, include the `--help` option when you invoke the installer. -### Invoking the PEM Server Installer in Unattended Mode +### Invoking the PEM server installer in unattended mode You can perform an unattended PEM server installation by providing installation preferences on the command line when invoking the installer. Please note that the system on which you are installing the PEM server must have internet access. diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/02_installing_pem_agent_on_windows.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/02_installing_pem_agent_on_windows.mdx index a798655005d..28dfd92c9c9 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/02_installing_pem_agent_on_windows.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/04_installing_postgres_enterprise_manager/02_installing_pem_agent_on_windows.mdx @@ -1,5 +1,5 @@ --- -title: "Installing a PEM Agent on Windows" +title: "Installing a PEM agent on Windows" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/installing_pem_agent_on_windows.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/05_the_pem_web_interface.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/05_the_pem_web_interface.mdx index de2526544f7..67f78ce9593 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/05_the_pem_web_interface.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/05_the_pem_web_interface.mdx @@ -1,5 +1,5 @@ --- -title: "The PEM Web Interface" +title: "The PEM web interface" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/the_pem_web_interface.html" diff --git a/product_docs/docs/pem/8/pem_inst_guide_windows/06_uninstalling_pem_components.mdx b/product_docs/docs/pem/8/pem_inst_guide_windows/06_uninstalling_pem_components.mdx index f58e5eae4d9..3e19ddb765b 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_windows/06_uninstalling_pem_components.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_windows/06_uninstalling_pem_components.mdx @@ -1,5 +1,5 @@ --- -title: "Uninstalling Postgres Enterprise Manager Components" +title: "Uninstalling Postgres Enterprise Manager components" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/windows-installation-guide/8.0/uninstalling_pem_components.html" diff --git a/product_docs/docs/pem/8/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx b/product_docs/docs/pem/8/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx index f7d707c131c..d702186779f 100644 --- a/product_docs/docs/pem/8/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx +++ b/product_docs/docs/pem/8/pem_pgbouncer/01_the_pem_server_pem_agent_connection_management_mechanism.mdx @@ -1,5 +1,5 @@ --- -title: "The PEM Server - PEM Agent Connection Management Mechanism" +title: "The PEM server - PEM agent connection management mechanism" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/pgbouncer-configuration-guide/8.0/the_pem_server_pem_agent_connection_management_mechanism.html" diff --git a/product_docs/docs/pem/8/pem_pgbouncer/02_preparing_the_pem_database_server.mdx b/product_docs/docs/pem/8/pem_pgbouncer/02_preparing_the_pem_database_server.mdx index 8b765820f23..c6fafd8e9dd 100644 --- a/product_docs/docs/pem/8/pem_pgbouncer/02_preparing_the_pem_database_server.mdx +++ b/product_docs/docs/pem/8/pem_pgbouncer/02_preparing_the_pem_database_server.mdx @@ -1,5 +1,5 @@ --- -title: "Preparing the PEM Database Server" +title: "Preparing the PEM database server" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/pgbouncer-configuration-guide/8.0/preparing_the_pem_database_server.html" diff --git a/product_docs/docs/pem/8/pem_pgbouncer/04_configuring_the_pem_agent.mdx b/product_docs/docs/pem/8/pem_pgbouncer/04_configuring_the_pem_agent.mdx index 1e220438325..af4f93cbb4a 100644 --- a/product_docs/docs/pem/8/pem_pgbouncer/04_configuring_the_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_pgbouncer/04_configuring_the_pem_agent.mdx @@ -1,5 +1,5 @@ --- -title: "Configuring the PEM Agent" +title: "Configuring the PEM agent" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/pgbouncer-configuration-guide/8.0/configuring_the_pem_agent.html" @@ -9,7 +9,7 @@ You can use an RPM package to install a PEM Agent; for detailed installation inf 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) +## 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: @@ -66,7 +66,7 @@ allow_batch_probes=false heartbeat_connection=false ``` -## Configuring an Existing PEM Agent (Installed via RPM) +## 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: diff --git a/product_docs/docs/pem/8/pem_pgbouncer/index.mdx b/product_docs/docs/pem/8/pem_pgbouncer/index.mdx index c858da13e27..23b33d33067 100644 --- a/product_docs/docs/pem/8/pem_pgbouncer/index.mdx +++ b/product_docs/docs/pem/8/pem_pgbouncer/index.mdx @@ -1,6 +1,6 @@ --- -navTitle: pgBouncer Configuration -title: "EDB Postgres Enterprise Manager Configuring pgBouncer for Use with PEM Agents" +navTitle: pgBouncer configuration +title: "EDB Postgres Enterprise Manager configuring pgBouncer for use with PEM agents" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/pgbouncer-configuration-guide/8.0/genindex.html" diff --git a/product_docs/docs/pem/8/pem_rel_notes/index.mdx b/product_docs/docs/pem/8/pem_rel_notes/index.mdx index d8d460cbcd7..9eeddcede8f 100644 --- a/product_docs/docs/pem/8/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/8/pem_rel_notes/index.mdx @@ -1,5 +1,5 @@ --- -title: "Release Notes" +title: "Release notes" --- The Postgres Enterprise Manager (PEM) documentation describes the latest version of PEM 8 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced after 8.0.0 in a minor or patch release, there are also indicators within the content about what release introduced the feature. @@ -15,8 +15,4 @@ The Postgres Enterprise Manager (PEM) documentation describes the latest version Often only select issues are included in the upstream merges. The specific issues included in the merges are listed in the release note topics. -
-08_810_rel_notes 09_801_rel_notes 10_800_rel_notes - -
diff --git a/product_docs/docs/pem/8/pem_security_best_practices/01_apache_httpd_security_configuration.mdx b/product_docs/docs/pem/8/pem_security_best_practices/01_apache_httpd_security_configuration.mdx index 4014104b714..f52cd4589da 100644 --- a/product_docs/docs/pem/8/pem_security_best_practices/01_apache_httpd_security_configuration.mdx +++ b/product_docs/docs/pem/8/pem_security_best_practices/01_apache_httpd_security_configuration.mdx @@ -1,5 +1,5 @@ --- -title: "Apache HTTPD Security Configurations" +title: "Apache HTTPD security configurations" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/pem-security-guide/8.0/apache_httpd_security_configuration.html" @@ -25,7 +25,7 @@ By default, PEM adds the following lines to the SSL configuration file to allow `SSLProxyProtocol -All TLSv1.2` -## Secure httpd with SSL Certificates +## Secure httpd with SSL certificates EDB recommends having an additional layer of SSL security for the web application. @@ -50,7 +50,7 @@ You can also replace the httpd self-signed SSL certificates with trusted CA-sign -## Disable Web Server Information Exposure +## Disable web server information exposure EDB recommends disabling all web server signatures as part of web server security. The web server will expose a software signature; to disable the signature, add the following parameters to the Apache httpd configuration file. By default, PEM disables exposure of the information by adding the below parameters to the Apache httpd configuration file: @@ -64,7 +64,7 @@ The `ServerSignature` directive includes a footer for server-produced documents. You need to restart the web server to apply any changes to the Apache httpd configuration file. -## Disable Directory Listing +## Disable directory listing The directory listing can allow an attacker to view complete directory contents. By default, the web server enables this option, and an attacker can discover and view any file. This listing could lead to the attacker reverse engineering an application to obtain the source code, analyze it for possible security flaws, and discover more information about an application. @@ -74,7 +74,7 @@ To avoid this, you should disable the directory listing by setting the `Options` You need to restart the web server to apply the changes made to the configuration file. -## Restrict the Access to a Network or IP Address +## Restrict the access to a network or IP address Apache provides access control based on the client hostname or IP address. To view the application by specific IP address or network, a user can modify the Apache configuration file as shown below to provide your network address within the `Allow` directive: @@ -112,7 +112,7 @@ You can set a specific individual host address (based on the IP address) in the You need to restart the web server to apply the changes to the application configuration file. -## Cross-site Tracing +## Cross-site tracing There are two HTTP methods to debug the web server connections - TRACE and TRACK. When an HTTP TRACE request is sent to a web server that supports it, that server will respond, echoing the data passed to it, including any HTTP headers. We recommend disabling these methods within the Apache Configuration. @@ -128,7 +128,7 @@ To disable these methods for a specific virtual host, add the following lines fo `RewriteRule .\* - [F]` -## Run Web Server from a Non-privileged User Account +## Run web server from a non-privileged user account Running the Apache web server as a root user creates a security issue. We always recommend running the web server as a unique non-privileged user. This helps to secure other services running in the event of any security breaches. @@ -138,13 +138,13 @@ On Linux, the Apache web server starts as the root user, but the daemon processe By default the Apache services are registered to run as the system user (the `LocalSystem` account). -## Customize Security HTTP Headers in PEM WebServer +## Customize security HTTP headers in PEM web server PEM contains its own configuration file to fix the following security issues. We recommend overriding the configuration only of `config_local.py` and not of `config.py`. The `config_local.py` is not present on the systems in most of the cases; hence users need to create it to override the application-level configurations. Please note that during a PEM upgrade, `config_local.py` will not be overwritten, but changes in `config.py` and `config_distro.py` will be overridden. Users need to remove `config_local.py` after uninstalling the PEM. By default, `config_local.py` is located in `/usr/edb/pem/web` on Linux, and at `C:\ProgramFiles\edb\pem\server\share\web` on Windows. -## Host Header Injection Attacks +## Host header injection attacks HTTP host header attacks exploit vulnerable websites that handle the host header value in an unsafe way. If the server implicitly trusts the host header and fails to validate or escape it properly, an attacker may be able to use this input to inject harmful payloads that manipulate server-side behavior. The web applications typically don't know what domain they are deployed on unless specified in a configuration file during setup. When they need to know the current domain, for example, they may resort to retrieving the domain from the host header to generate an absolute URL. The host header is a potential vector for exploiting a range of other vulnerabilities, most notably web cache poisoning & SQL injections. @@ -199,7 +199,7 @@ This changes requires an Apache service restart in order to take effect For more detailed information on `config.py` file you can see [PEM Online Help](/pem/latest/pem_online_help/01_toc_pem_getting_started/03_pem_managing_configuration_settings/). -### Cookie Security +### Cookie security Cookies are small packets of data that a server can send to your browser to store configuration data. The browser automatically sends them along with all requests to the same server, so it’s important to know how to secure cookies. There are multiple configuration options provided by PEM to make cookies secure which you can refer to in `config.py` but the three that follow are most important. diff --git a/product_docs/docs/pem/8/pem_security_best_practices/02_pem_application_configuration.mdx b/product_docs/docs/pem/8/pem_security_best_practices/02_pem_application_configuration.mdx index 503014da8e4..16dfe93c245 100644 --- a/product_docs/docs/pem/8/pem_security_best_practices/02_pem_application_configuration.mdx +++ b/product_docs/docs/pem/8/pem_security_best_practices/02_pem_application_configuration.mdx @@ -1,11 +1,11 @@ --- -title: "PEM application Security Configurations" +title: "PEM application security configurations" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/pem-security-guide/8.0/pem_application_configuration.html" --- -## Session Timeout +## Session timeout Insufficient session expiration by the web application increases the exposure of other session-based attacks, as it allows time for the attacker to be able to reuse a valid session ID and hijack the associated session. The shorter the session interval is, the lesser the time an attacker has to use the valid session ID. We recommend setting the inactivity timeout for the web application to a low value to avoid this security issue. @@ -22,7 +22,7 @@ This changes requires an Apache service restart in order to take effect. For more detailed information on `config.py` file you can see [PEM Online Help](/pem/latest/pem_online_help/01_toc_pem_getting_started/03_pem_managing_configuration_settings/). -## RestAPI Header Customization +## RestAPI header customization You can customize the RestAPI token headers as per your requirements. The default values are not exposed by the `config.py` file; customize the following headers in the `config_local.py` file: @@ -64,7 +64,7 @@ This configuration option will allow you to change the PEM RestAPI token expiry This changes requires an Apache service restart in order to take effect. -## Role-based Access Control in PEM +## Role-based access control in PEM Role-based access control (RBAC) restricts application access based on a user’s role within an organization and is one of the primary methods for access control. The roles in RBAC refer to the levels of access that users have to the application. Users are only allowed to access the information necessary to effectively perform their job duties. Roles in PEM are inheritable and additive rather than subscriptive. In simple terms, as a PEM admin you need to grant the lowest level role to the user and then grant the roles which are required for the user to perform their respective tasks. For example, to give access only to SQL profiler: @@ -74,7 +74,7 @@ Role-based access control (RBAC) restricts application access based on a user’ For more detailed information on roles, you can see [PEM Roles](/pem/latest/pem_online_help/01_toc_pem_getting_started/04_pem_roles/). -## SQL/Protect Plugin +## SQL/Protect plugin Preventing a SQL injection attack is usually the responsibility of the application developer. The database administrator typically has little or no control over the potential threat. The difficulty for database administrators is that the application must have access to the data to function properly. @@ -87,7 +87,7 @@ There are several different techniques used to perpetrate SQL injection attacks. For more detailed information about the SQL Profiler plugin, see the [PEM Online Help - SQL Profiler](/pem/latest/pem_online_help/07_toc_pem_sql_profiler/). -## Password Management +## Password management One security tip for PEM administrative users is to change your PEM login passwords to something new regularly. Changing your password avoids a number of dangers including: @@ -96,7 +96,7 @@ One security tip for PEM administrative users is to change your PEM login passwo - prevents the use of saved passwords on a physically unsecured system - limits access gained by keystroke loggers -## Run pemAgent Jobs with a Non-root User +## Run pemAgent jobs with a non-root ser In most cases, `pemAgent` is installed as a root user, and runs as a daemon process with root privileges. By default, PEM disables running the scheduled jobs/task. PEM provides support for running scheduled jobs as a non-root user by changing the pemAgent configuration file. @@ -106,7 +106,7 @@ To invoke a script on a Windows system, set the registry entry for `AllowBatchJo `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent` -## Changing the pemAgent and PEM Backend Database Server Certificates +## Changing the pemAgent and PEM backend database server certificates By default, when you install PEM, the installer will generate and use self signed certificates for the pemAgent and PEM database server. PemAgent uses these certificates when connecting to the PEM database server. To use your own SSL certificate for the pemAgent and PEM database server, follow the steps mentioned in the `Managing Certificates` section of the `PEM Administrators's Guide`: diff --git a/product_docs/docs/pem/8/pem_security_best_practices/index.mdx b/product_docs/docs/pem/8/pem_security_best_practices/index.mdx index 7d07aaa47ec..98690418449 100644 --- a/product_docs/docs/pem/8/pem_security_best_practices/index.mdx +++ b/product_docs/docs/pem/8/pem_security_best_practices/index.mdx @@ -19,8 +19,4 @@ Some of the benefits of regularly applying security patches include: - Data protection from malware (like ransomware) - Avoid worm infections that use security loopholes to spread over the network -
-apache_httpd_security_configuration pem_application_configuration conclusion - -
diff --git a/product_docs/docs/pem/8/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx b/product_docs/docs/pem/8/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx index f08d6da4b0a..ca573dc6bb8 100644 --- a/product_docs/docs/pem/8/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx +++ b/product_docs/docs/pem/8/pem_sqlprofiler/01_installing_the_sql_profiler_plugin.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the SQL Profiler Plugin" +title: "Installing the SQL Profiler plugin" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/sql-profiler-configuration-guide/8.0/installing_the_sql_profiler_plugin.html" @@ -39,7 +39,7 @@ The SQL Profiler plugin installer displays progress bars as it copies files to y When the installation is complete, the SQL Profiler plugin is ready to be configured. -## Using an RPM Package to Install SQL Profiler +## 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. diff --git a/product_docs/docs/pem/8/pem_sqlprofiler/02_using_sql_profiler.mdx b/product_docs/docs/pem/8/pem_sqlprofiler/02_using_sql_profiler.mdx index d28c480182e..1061c3ff193 100644 --- a/product_docs/docs/pem/8/pem_sqlprofiler/02_using_sql_profiler.mdx +++ b/product_docs/docs/pem/8/pem_sqlprofiler/02_using_sql_profiler.mdx @@ -1,5 +1,5 @@ --- -title: "SQL Profiling and Analysis" +title: "SQL profiling and analysis" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/user-guides/sql-profiler-configuration-guide/8.0/using_sql_profiler.html" @@ -27,11 +27,11 @@ For each database monitored by SQL Profiler, you must: Please note: if you have connected to the PEM server with the PEM client before configuring SQL Profiler, you must disconnect and reconnect with the server to enable SQL Profiler functionality. For more detailed information about installing and configuring the SQL Profiler plugin, please refer to the [PEM Installation Guides](https://www.enterprisedb.com/docs/pem/latest). -## Creating a New SQL Trace +## Creating a new SQL trace SQL Profiler captures and displays a specific SQL workload for analysis in a SQL trace. You can start and review captured SQL traces immediately, or save captured traces for review at a later time. You can use SQL Profiler to create and store up to 15 named traces; use menu options to create and manage traces. -### Creating a Trace +### Creating a trace You can use the `Create trace...` dialog to define a SQL Trace for any database on which SQL Profiler has been installed and configured. installed and configured. To access the dialog, highlight the name of the database in the PEM client tree control; navigate through the Management menu to the SQL Profiler pull-aside menu, and select Create trace.... @@ -72,7 +72,7 @@ When you've completed the `Create trace...` dialog, click `Create` to start the If you elect to execute the trace immediately, the trace results will display in the PEM client. -### Opening an Existing Trace +### Opening an existing trace To view a previous trace, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Open trace....` You can also use the `SQL Profiler toolbar` menu to open a trace; select the `Open trace...` option. The Open trace... dialog opens. @@ -80,7 +80,7 @@ To view a previous trace, highlight the name of the profiled database in the PEM Highlight an entry in the trace list and click Open to open the selected trace. The selected trace opens in the SQL Profiler tab. -### Filtering a Trace +### Filtering a trace A filter is a named set of (one or more) rules, each of which can hide events from the trace view. When you apply a filter to a trace, the hidden events are not removed from the trace, but are merely excluded from the display. @@ -106,7 +106,7 @@ When you've finished defining a rule, click the Add (+) icon to add another rule Click the `Save` button to save the filter definition to a file without applying the filter; to apply the filter, click `OK`. Select `Cancel` to exit the dialog and discard any changes to the filter. -### Deleting a Trace +### Deleting a trace To delete a trace, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Delete trace(s)....` You can also use the SQL Profiler toolbar menu to delete a trace; select the `Delete trace(s)...` option. The `Delete traces` dialog opens. @@ -114,7 +114,7 @@ To delete a trace, highlight the name of the profiled database in the PEM client Click the icon to the left of a trace name to mark one or more traces for deletion and click `Delete`. The PEM client will acknowledge that the selected traces have been deleted. -### Viewing Scheduled Traces +### Viewing scheduled traces To view a list of scheduled traces, highlight the name of the profiled database in the PEM client tree control; navigate through the `Management` menu to the SQL Profiler pull-aside menu, and select `Scheduled traces...` You can also use the SQL Profiler toolbar menu to the list; select the `Scheduled traces...` option. diff --git a/product_docs/docs/pem/8/pem_sqlprofiler/03_uninstalling_sql_profiler.mdx b/product_docs/docs/pem/8/pem_sqlprofiler/03_uninstalling_sql_profiler.mdx index d0300f04054..490ba7b5e7b 100644 --- a/product_docs/docs/pem/8/pem_sqlprofiler/03_uninstalling_sql_profiler.mdx +++ b/product_docs/docs/pem/8/pem_sqlprofiler/03_uninstalling_sql_profiler.mdx @@ -9,7 +9,7 @@ legacyRedirectsGenerated: The process of uninstalling SQL Profiler is platform-specific. -## Uninstalling SQL Profiler from Windows Hosts +## Uninstalling SQL Profiler from Windows hosts If you are using SQL Profiler on a Windows host, Windows will lock any files that have been executed or loaded into memory. To release any locked files, you must stop the Postgres server before performing an uninstall. @@ -21,7 +21,7 @@ Delete the existing SQL Profiler query set on each node by invoking the `uninsta By default, the script resides in the `share\contrib` directory under your Advanced Server or PostgreSQL installation. -## Uninstalling SQL Profiler from CentOS or RHEL Hosts +## Uninstalling SQL Profiler from CentOS or RHEL hosts To uninstall a SQL Profiler installation that resides on a Linux host: diff --git a/product_docs/docs/pem/8/pem_sqlprofiler/index.mdx b/product_docs/docs/pem/8/pem_sqlprofiler/index.mdx index 42035fc7ac4..fdf1aa9c389 100644 --- a/product_docs/docs/pem/8/pem_sqlprofiler/index.mdx +++ b/product_docs/docs/pem/8/pem_sqlprofiler/index.mdx @@ -17,8 +17,4 @@ SQL Profiler is officially supported only on the EDB distributions of PostgreSQL Throughout this guide, the term `Postgres` refers to either a PostgreSQL or an Advanced Server installation, where either is appropriate. -
-installing_the_sql_profiler_plugin using_sql_profiler uninstalling_sql_profiler conclusion - -
diff --git a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx index 899d2d84c53..923ba850b9f 100644 --- a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading a PEM Native Package Installation on a Linux Host" +title: "Upgrading a PEM native package installation on a Linux host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/upgrade-migration-guide/8.0/upgrading_pem_installation_linux_rpm.html" @@ -17,11 +17,11 @@ During an installation, the component installation will automatically detect an The following sections will walk you through the upgrade process on a Linux host, step-by-step. -## Prerequisites to Upgrade a PEM Installation on Linux Host +## Prerequisites to upgrade a PEM installation on Linux host PEM is dependent on third-party components from the vendor repository, including the python3, libboost, openssl, snmp++, libcurl, etc. To ensure these components are up to date, you should update your operating system using following platform-specific commands. Minimum version require for openssl is 1.0.2k. If you are using a version of PostgreSQL or Advanced Server older than version 10, before the upgrade you must install the `libs` package for version 10 or above on the system where the PEM server is installed. Use the following platform-specific commands to install the `libs` version 10 or above on your host: -### Prerequisites to Upgrade a PEM Installation on a CentOS or RHEL Host +### Prerequisites to upgrade a PEM installation on a CentOS or RHEL host To upgrade packages on a CentOS or RHEL 7.x host @@ -51,7 +51,7 @@ yum install postgresql-libs Where `` is the PostgreSQL or Advanced Server version whose `libs` package you want to install. -### Prerequisites to Upgrade a PEM Installation on a Debian or Ubuntu Host +### Prerequisites to upgrade a PEM installation on a Debian or Ubuntu host To upgrade packages on a Debian or Ubuntu host @@ -74,7 +74,7 @@ apt-get install postgresql-libs Where `` is the PostgreSQL or Advanced Server version whose `libs` package you want to install. -### Prerequisites to Upgrade a PEM Installation on a SLES Host +### Prerequisites to upgrade a PEM installation on a SLES host To upgrade packages on a SLES host @@ -97,11 +97,11 @@ zypper install postgresql-libs Where `` is the PostgreSQL or Advanced Server version whose `libs` package you want to install. -## Upgrading a PEM Agent Native Package Installation +## Upgrading a PEM agent native package installation You can use native packages to upgrade existing PEM Agents initially installed using native packages. The upgrade process does not update the PEM agent configuration file. After installing the new agent, you must manually copy the configuration file of the existing agent to the new installation location. -### Upgrading the PEM Agent on a CentOS or RHEL Host +### Upgrading the PEM agent on a CentOS or RHEL host For CentOS or RHEL 7.x or RHEL 8.x: @@ -117,7 +117,7 @@ For Rocky Linux or AlmaLinux or RHEL 8.x, you can also use the following command dnf upgrade edb-pem-agent ``` -### Upgrading a PEM Agent on a Debian or Ubuntu Host +### Upgrading a PEM agent on a Debian or Ubuntu host To upgrade a PEM Agent, use the following command: @@ -125,7 +125,7 @@ To upgrade a PEM Agent, use the following command: apt-get upgrade edb-pem-agent ``` -### Upgrading a PEM Agent on a SLES Host +### Upgrading a PEM agent on a SLES host To upgrade a PEM Agent, use the following command: @@ -133,13 +133,13 @@ To upgrade a PEM Agent, use the following command: zypper update edb-pem-agent ``` -## Upgrading a PEM Server Native Package Installation +## Upgrading a PEM server native package installation If you initially used native packages to install your PEM server, you can use native packages to upgrade your PEM server. The commands to upgrade are platform-specific; please refer to your platform's section below. If you wish to upgrade a PEM server that is installed on a machine in an isolated network, you need to create a PEM repository on that machine before you upgrade the PEM server. For more information about creating a PEM repository on an isolated network, see [Creating a PEM Repository on an Isolated Network](../../pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network/). -### Upgrading a PEM Server on a CentOS, Rocky Linux, AlmaLinux, or RHEL Host +### Upgrading a PEM server on a CentOS, Rocky Linux, AlmaLinux, or RHEL host To use an RPM package to upgrade an existing RPM installation you must: @@ -160,7 +160,7 @@ dnf upgrade edb-pem After upgrading the PEM Server using `yum` or `dnf`, you must configure the PEM Server. For more detailed information see [Configuring the PEM Server](../01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm/#configuring-the-pem-server). -### Upgrading the PEM Server on a Debian or Ubuntu Host +### Upgrading the PEM server on a Debian or Ubuntu host You can use the `apt-get` package manager to upgrade the installed version of the PEM Server on supported versions of Debian or Ubuntu: @@ -170,7 +170,7 @@ apt-get upgrade edb-pem After upgrading the PEM Server with `apt-get`, you need to configure the PEM Server. For more detailed information see [Configuring the PEM Server](../01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm/#configuring-the-pem-server). -### Upgrading the PEM Server on a SLES Host +### Upgrading the PEM server on a SLES host You can use the `zypper` package manager to upgrade the installed version of the PEM Server on supported versions of SLES Host: @@ -181,7 +181,7 @@ zypper update edb-pem After upgrading the PEM Server using `zypper`, you need to configure the PEM Server. For more detailed information see [Configuring the PEM Server](../01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm/#configuring-the-pem-server). -## Configuring the PEM Server +## Configuring the PEM server After upgrading the PEM Server you can use the following command to configure the PEM Server: diff --git a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/06_upgrading_pem_installation_windows.mdx b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/06_upgrading_pem_installation_windows.mdx index 8b0b5e6221c..8b227c583e1 100644 --- a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/06_upgrading_pem_installation_windows.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/06_upgrading_pem_installation_windows.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading a PEM Installation on a Windows Host" +title: "Upgrading a PEM Installation on a Windows host" redirects: - ../01_upgrading_pem_installation_windows legacyRedirectsGenerated: @@ -16,7 +16,7 @@ During an installation, the component installer will automatically detect an exi 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 +## 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. @@ -52,7 +52,7 @@ After the installation completes, a window pops-up to restart the machine. Click ![The PEM Agent Installer - Restart pop-up](../../images/pem_upgrade_agent_restart_pop_up.png) -## Upgrading the PEM Server on a Windows Host +## 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. diff --git a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/index.mdx b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/index.mdx index 5290221c305..c0a1c3519a8 100644 --- a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/index.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/index.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading a PEM Installation" +title: "Upgrading a PEM installation" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/upgrade-migration-guide/8.0/upgrading_pem_installation.html" diff --git a/product_docs/docs/pem/8/pem_upgrade/02_upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/02_upgrading_backend_database.mdx index ddab591f8e3..38dbb1f0668 100644 --- a/product_docs/docs/pem/8/pem_upgrade/02_upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/02_upgrading_backend_database.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading the PEM Backend Postgres Database" +title: "Upgrading the PEM backend Postgres database" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/upgrade-migration-guide/8.0/upgrading_backend_database.html" diff --git a/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/01_upgrading_sql_profiler_linux.mdx b/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/01_upgrading_sql_profiler_linux.mdx index ed27731a0fc..1de5d98719e 100644 --- a/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/01_upgrading_sql_profiler_linux.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/01_upgrading_sql_profiler_linux.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading a SQL Profiler Native Package Installation on a Linux Host" +title: "Upgrading a SQL profiler native package installation on a Linux host" --- To upgrade a SQL Profiler installation that resides on a Linux host: diff --git a/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/02_upgrading_sql_profiler_windows.mdx b/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/02_upgrading_sql_profiler_windows.mdx index 56ec1cf0175..2a3d730cce3 100644 --- a/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/02_upgrading_sql_profiler_windows.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/02a_upgrading_sql_profiler/02_upgrading_sql_profiler_windows.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading a SQL Profiler Installation on a Windows Host" +title: "Upgrading a SQL Profiler installation on a Windows host" --- If you are using SQL Profiler on a Windows host, Windows will lock any files that have been executed or loaded into memory. To release any locked files, you must stop the Postgres server before performing an upgrade. diff --git a/product_docs/docs/pem/8/pem_upgrade/03_moving_pem_server.mdx b/product_docs/docs/pem/8/pem_upgrade/03_moving_pem_server.mdx index f62e2990db1..c7d9c734938 100644 --- a/product_docs/docs/pem/8/pem_upgrade/03_moving_pem_server.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/03_moving_pem_server.mdx @@ -1,5 +1,5 @@ --- -title: "Moving the PEM Server" +title: "Moving the PEM server" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/upgrade-migration-guide/8.0/moving_pem_server.html" diff --git a/product_docs/docs/pem/8/pem_upgrade/04_troubleshooting.mdx b/product_docs/docs/pem/8/pem_upgrade/04_troubleshooting.mdx index 5a44c1721a4..81e21176432 100644 --- a/product_docs/docs/pem/8/pem_upgrade/04_troubleshooting.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/04_troubleshooting.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: -## Reconfiguring the PEM Server +## Reconfiguring the PEM server In some situations you may need to uninstall the PEM server, install it again, and then reconfigure the server. Use the following commands in the given sequence: diff --git a/product_docs/docs/pem/8/pem_upgrade/index.mdx b/product_docs/docs/pem/8/pem_upgrade/index.mdx index fd946dfe541..0cf9507b52d 100644 --- a/product_docs/docs/pem/8/pem_upgrade/index.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/index.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrade and Migration" +title: "Upgrade and migration" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-enterprise-manager/installation-getting-started/upgrade-migration-guide/8.0/genindex.html" diff --git a/product_docs/docs/pglogical/3.7/credits.mdx b/product_docs/docs/pglogical/3.7/credits.mdx deleted file mode 100644 index 4fb8722351a..00000000000 --- a/product_docs/docs/pglogical/3.7/credits.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -navTitle: Credits and License -title: Credits and Licence -originalFilePath: credits.md - ---- - -pglogical has been designed, developed and tested by this team: - -- Petr Jelinek -- Craig Ringer -- Simon Riggs -- Peter Eisentraut -- Tomas Vondra -- Pallavi Sontakke -- Nikhil Sontakke -- Pavan Deolasee -- Umair Shahid -- Markus Wanner - -Copyright (c) 2021 EnterpriseDB UK Ltd diff --git a/product_docs/docs/pglogical/3.7/release-notes.mdx b/product_docs/docs/pglogical/3.7/release-notes.mdx index 74abb6c0364..83b8cf0e276 100644 --- a/product_docs/docs/pglogical/3.7/release-notes.mdx +++ b/product_docs/docs/pglogical/3.7/release-notes.mdx @@ -38,14 +38,6 @@ improvements as well as fixes for issues identified previously. - Fix replication of data types created during bootstrap (BDR-1784) -### Upgrades - -This release supports upgrading from following versions of pglogical: - -- 3.7.9 and higher -- 3.6.29 and higher -- 2.4.0 and 2.4.1 - ## pglogical 3.7.14 This is a maintenance release for pglogical 3.7 which includes minor