Table of Contents Previous Next

2 Postgres Enterprise Manager™ - Overview
2 Postgres Enterprise Manager™ - Overview
Postgres Enterprise Manager™ (PEM) is comprised of a number of individual components that must be installed in order to make full use of all the features of PEM:
•
PEM Server: The PEM server is used as the data repository for monitoring data and as a server to which both agents and clients connect. The PEM server consists of an instance of PostgreSQL and an associated database for storage of monitoring data, and a server providing web services for the client.
•
PEM Client: The PEM client is a graphical client application that allows you to manage your Postgres server, and access monitoring data on the PEM server. This program may reside on the PEM server host, or other machines for more convenience.
•
PEM Agent: PEM agents are responsible for executing tasks and reporting statistics from the host and monitored Postgres instances to the PEM server. A single PEM agent can monitor multiple installed instances of Postgres on each host.
•
SQL Profiler plugin: This plugin to the Postgres server is used to generate the monitoring data used by the SQL Profiler tool within the PEM client. Installation of the SQL Profiler plugin is optional, but the plugin must be installed into each instance of Postgres you wish to profile. The SQL Profiler may be used with any supported version of an EnterpriseDB distribution of a PostgreSQL server or a Postgres Plus Advanced Server (not just those managed through the PEM server). See Chapter 5 for details and supported versions.
The architectural diagram below (Figure 2.1) illustrates the relationship between the various servers and workstations involved in a typical PEM installation.
PEM Component Architecture
Figure 2.1 - A typical PEM installation.
2 Postgres Enterprise Manager™ - Overview

Table of Contents Previous Next