Throughout this guide, the term Postgres refers to either a PostgreSQL or an Advanced Server installation, where either is appropriate.Language pack installers contain supported languages that may be used with EDB Postgres Advanced Server and EnterpriseDB PostgreSQL database installers. The language pack installer allows you to install Perl, TCL/TK, and Python without installing supporting software from third party vendors. For more information about installing and using Language Pack, please see the EDB Postgres Language Pack Guide, available from the EnterpriseDB Website.
1.1 What's New
In the following descriptions a term refers to any word or group of words that are language keywords, user-supplied values, literals, etc. A term’s exact meaning depends upon the context in which it is used.
The PEM Agent installer creates two executables: the PEM worker (pemworker.exe) and the PEM agent (pemagent.exe). Each PEM worker has a corresponding PEM agent that you can use to start or stop the PEM worker. The PEM agent will also restart the PEM worker should it terminate unexpectedly.The PEM worker log file contains information related to PEM worker activity (probe activities, heartbeat responses, etc.), and is stored in /var/log/pem/worker.log.
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.For information about modifying the pg_hba.conf file, see the PEM Getting Started Guide, available at:Before installing the PEM Server on a system that is running SELinux, you must set SELinux to permissive mode.The following example works on Redhat Enterprise Linux, Fedora Core or CentOS distributions; use comparable commands that are compatible with your Linux distribution to set SELinux to permissive mode during installation and return it to enforcing mode when installation is complete.Before installing the PEM agent on a CentOS 7.x host, you must ensure that the host contains the wxBase and epel-release packages. To install the packages, open a command line, assume root privileges, and invoke the commands:If you are installing PEM components on Windows, you may be required to invoke the PEM installers with Administrative privileges. To invoke an installer using Administrator privileges, right click on the installer icon and select Run as Administrator from the context menu.At this time, 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.
The PEM server graphical installer installs and configures the PEM server, a PEM agent, and the software required to connect to the PEM web interface with your choice of browser. 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 PEM functionality on servers monitored by a remote agent may be limited. For detailed information about using the PEM server graphical installer, see Section 3.1.You can use an RPM package on a RHEL 7 host to install the PEM server; for detailed information about using the installer, see Section 3.2.
The PEM server backend database may be an EnterpriseDB distribution of the PostgreSQL or Advanced Server database server, or an existing Postgres server installed from another source. The Postgres backing database server must be version 9.3 or later, and will contain a database named pem, which is used by the PEM server as a repository.
On a Windows system, right click the installer icon and select Run as Administrator. The installer displays a Welcome dialog (shown in Figure 3.2).Carefully review the license agreement (see Figure 3.3) before highlighting the appropriate radio button and accepting the agreement. Click Next to continue to the Installation Directory dialog.Use the Installation Directory dialog (shown in Figure 3.4) to specify the location of the PEM server:
3.1.2.1 Specifying a Database HostSelecting the Database option on the Advanced options dialog (Figure 3.17) allows you to specify connection information for the host on which the PEM server backend database (named pem) will reside.Use the drop-down listbox on the Database Server Selection dialog (see Figure 3.18) to select a host for the PEM server backend database. You can:
3.1.2.2 Installing Web ServicesSelecting the Web Services radio button on the Advanced options dialog (Figure 3.26) instructs the PEM server installer to either install PEM-HTTPD on the current host or update an existing PEM-HTTPD installation.
You can use an existing Postgres server (version 9.3 or later) to host the PEM server and the pem database. Postgres installers and pre-requisite software extensions are freely available from the EnterpriseDB website at:The following versions of Postgres are pre-configured to contain the sslutils extension and a service script; no additional preparation is required to use the following Postgres versions as a PEM backend database server:3.1.3.1 Preparing the Postgres Server
SET GETTEXTPATH=path_to_gettext
SET OPENSSLPATH=path_to_openssl
SET PGPATH=path_to_pg_installation_dir
SET ARCH=x86
REM Set ARCH x64 for 64 bit
msbuild sslutils.proj /p:Configuration=Releasepath_to_pg_installation_dir specifies the location of the Postgres installation.
The installer displays a Welcome dialog (shown in Figure 3.31).Carefully review the license agreement (see Figure 3.32) before highlighting the appropriate radio button and accepting the agreement; click Next to continue to the Installation Directory dialog.Use the Installation Directory dialog (shown in Figure 3.33) to specify the location of the PEM server, and access the Advanced options dialog:
The pg_hba.conf file on the backing database must be configured to use trust authentication for connections. For information about modifying the pg_hba.conf file, visit:Before installing the PEM server, you must create the repository configuration file (edb.repo). The repository configuration file contains connection and authentication information for the EnterpriseDB repository. To prepare your system to perform an RPM installation, assume superuser privileges and use yum to create the repository configuration file:Please note: If you are a Red Hat Network user you must also enable the rhel-x-server-optional-rpms repository to use EPEL packages, where x specifies the version of RHEL on the host. You can make the repository accessible by enabling the RHEL optional subchannel for RHN-Classic. If you have a certificate-based subscription, please see the Red Hat Subscription Management Guide. You must also enable the rhel-x-server-extras-rpms repository, where x specifies the version of RHEL on the host.After creating the repository configuration file, use your choice of editor to enable the repository entries from which you will install packages. The repository configuration file is named edb.repo, and resides in /etc/yum.repos.d. To enable a repository, change the value of the enabled parameter to 1 and replace the username and password placeholders in the baseurl specification with your user name and the repository password.Run following commands to install rh-python36:Before installing the PEM server, you must disable SELinux; use the command:
The Setup… page opens, welcoming you to the PEM Agent installer (as shown in Figure 3.43).Carefully review the license agreement (see Figure 3.44) before highlighting the appropriate radio button and accepting the agreement; click Next to continue to the Installation Directory dialog.By default, the PEM agent is installed in the /home/opt/PEM directory. You can accept the default installation directory, or modify the contents of the Installation Directory field (see Figure 3.45), specifying an alternate installation directory for the PEM agent.By default, the PEM agent installer places a certificate in ~root/.pem (on Linux) or in the Administrator’s %APPDATA%\pem directory (on Windows). Check the Show advanced options box to indicate that you would like the PEM agent installer to include a dialog that allows you to specify an alternate path for the certificate file.Check the box next to Register now? to instruct the installer to register the newly installed PEM agent with the PEM server.Enter the connection details for the PEM server on the PEM server installation details dialog (see Figure 3.46):
On a Linux system, you can use the yum package manager to install a PEM agent. Please note that before using a package manager to install the PEM agent, the host must contain the following packages:
3.3.4 Registering an AgentEach PEM agent must be registered with the PEM server. The registration process provides the PEM server with the information it needs to communicate with the agent. The PEM agent graphical installer supports agent self-registration, but you can use the pemworker utility to register the agent if you skip PEM agent registration during a graphical installation or use an RPM package to install a PEM agent.The RPM installer places the PEM agent in the /usr/pem/agent/bin directory. To register an agent, include the --register-agent keywords along with registration details when invoking the pemworker utility:
Before invoking the installer, you must disable SE Linux; for more information, see Section 2.3. You must be a superuser to install the PEM server../edb-languagepack-version-linux-x64.run --mode unattended
./pem-httpd-version-linux-x64.run --mode unattended
./postgresql-version-linux-x64.run --mode unattended./pem-server-7.x.x-linux-x64.run --mode unattended
--existing-user registered_edb_user --existing-password edb_user_password --pgport port --pguser postgres
--pgpassword postgres -–cidr-address cidr_address_rangeregistered_edb_user specifies the name of a registered EnterpriseDB user. To register, visit the EDB website at: https://www.enterprisedb.com/user/registeredb_user_password specifies the password associated with the EDB user account.port specifies the port used by the backing PostgreSQL database; by default, the PostgreSQL database uses port 5432.cidr_address_range specifies the address range that will be added to the pg_hba.conf file of the PEM server's backing database to allow connections from the agents that will be monitored by the server. You may wish to specify a network range (for example, 192.168.2.0/24) to provide server access to agents that reside on the same network.Please note: when invoked in unattended mode, the PostgreSQL installer creates a user named postgres, with a password of postgres.In our example, the files are extracted to the C:\ directory. After extracting the files, you must install each program. Navigate into the directory that contains the files (in our example, C:\), and enter:edb-languagepack-version-windows-x64.exe --mode unattended
pem-httpd-version-windows-x64.exe --mode unattended
postgresql-version-windows-x64.exe --mode unattendedpem-server-7.x.x-windows-x64.exe --mode unattended
--existing-user registered_edb_user --existing-password edb_user_password --pgport port --pguser postgres
--pgpassword postgres -–cidr-address cidr_address_range
--agent_description pem-agent --systempassword windows_password
--agent-crt-path C:\edbregistered_edb_user specifies the name of a registered EnterpriseDB user. To register, visit the EDB website at: https://www.enterprisedb.com/user/registeredb_user_password specifies the password associated with the EDB user account.port specifies the port used by the backing PostgreSQL database; by default, the PostgreSQL database uses port 5432.cidr_address_range specifies the address range that will be added to the pg_hba.conf file of the PEM server's backing database to allow connections from the agents that will be monitored by the server. You may wish to specify a network range (for example, 192.168.2.0/24) to provide server access to agents that reside on the same network.windows_password specifies the password associated with the Windows Administrator's account.Please note: when invoked in unattended mode, the PostgreSQL installer creates a user named postgres, with a password of postgres.
--pghost pem_server_host_address --pgport pem_server_port
--pguser postgres --pgpassword pguser_password
--agent_description agent_namepem_server_port specifies the port used by the backing PEM database; by default, the database uses port 5432.pguser_password specifies the password associated with the PEM database superuser.agent_name specifies a descriptive name for the PEM agent.
--pghost pem_server_host_address --pgport pem_server_port
--pguser postgres --pgpassword pguser_password
--agent_description agent_namepem_server_port specifies the port used by the backing PEM database; by default, the database uses port 5432.pguser_password specifies the password associated with the PEM database superuser.agent_name specifies a descriptive name for the PEM agent.
Before invoking the installer, you must disable SE Linux; for more information, see Section 2.3. You must be a superuser to install the PEM server../edb-languagepack-version-linux-x64.run --mode unattended
./pem-httpd-version-1-linux-x64.run --mode unattended
./postgresql-version-linux-x64.run --mode unattendededb-languagepack-version-windows-x64.exe --mode unattended
pem-httpd-version-windows-x64.exe --mode unattended
postgresql-version-windows-x64.exe --mode unattended----------------------------------------------------------------
Welcome to the Postgres Enterprise Manager (PEM) Server Setup Wizard.
----------------------------------------------------------------
Before installing the PEM server, you must review and accept the terms of the PEM license agreement:Please read the following License Agreement. You must accept the terms of this agreement before continuing with the installation.
Review the license agreement; when prompted, accept the agreement, and press Return.
Do you accept this license? [y/n]: y
----------------------------------------------------------------
After accepting the license agreement, you will be prompted for the name and address of a registered EnterpriseDB user; provide the information when prompted:Email address []:
Password :
----------------------------------------------------------------
Next, you will be prompted for an installation directory; you can use the default installation directory, or specify an alternate location.Enter a Y after Show advanced options to access menu options that allow you to use a pre-existing Postgres server installation or PEM-HTTPD installation with the PEM server.Please specify user and password for the local server - 'PostgreSQL 10' installation running on port 5432.
User [postgres]:
Password :
----------------------------------------------------------------
When prompted, provide the network address or range that will be added to the pg_hba.conf file of the PEM server host; this will allow PEM agents on monitored hosts to contact the server:Network address [127.0.0.1/32]:
----------------------------------------------------------------
Use the Agent Details fields to specify a descriptive name for the agent and the location of the agent certificate:
Before invoking the installer, you must disable SE Linux; for more information, see Section 2.3. You must be a superuser to install the PEM agent.-----------------------------------------------------------------
Welcome to the Postgres Enterprise Manager (PEM) Agent Setup Wizard.
-----------------------------------------------------------------Before installing the PEM server, you must review and accept the terms of the PEM license agreement:By default, the PEM agent installer places a certificate in ~root/.pem (on Linux) or in the Administrator’s %APPDATA%\pem directory (on Windows). Enter a Y after Show advanced options to access menu options that allow you to specify an alternate path for the certificate file.
Where ip_address_of_PEM_host specifies the IP address of the host of the PEM server. The Postgres Enterprise Manager Web Login window (shown in Figure 4.1) opens:Use the fields on the Postgres Enterprise Manager Login window to authenticate yourself with the PEM server:
Follow the installation steps listed below to install the plugin for PostgreSQL before continuing to the Configuration section. If you are using Advanced Server, skip ahead to the Configuration section.
Carefully review the license agreement before highlighting the appropriate radio button and accepting the agreement; click Next to continue to the Installation Directory dialog (shown in Figure 5.3).Specify an alternate location for the installation directory, or accept the default location and click Next to continue.The wizard is now ready to install the SQL Profiler plugin (as shown in Figure 5.4). Click Next to continue.
