Table of Contents Previous Next

4 Adding Postgres Instances to PEM : 4.1 Logging on to the PEM server

The PEM client (installed with the PEM client installer) provides a convenient graphical interface that allows you to interact with the PEM server and managed (or unmanaged) Postgres instances. To start the PEM client, navigate through the Applications menu (on Linux) or Start menu (on Windows) to the Postgres Enterprise Manager™ menu, and select Postgres Enterprise Manager v5. The PEM client opens, as shown in Figure 4.1.
one
To open the PEM Server Logon dialog (shown in Figure 4.2), click the Server Logon button at the left-most end of the client toolbar, or navigate through the File menu to PEM Server Logon…
two
Use the fields on the PEM Server Logon dialog to provide connection details for the PEM server:
Enter the host name or IP Address where the Apache/PHP server is running, or use the Host drop-down listbox to select a server to which you have previously connected.
Please note: you can use the Delete button (located to the right of the Host field) to delete unwanted host addresses from the list displayed in the Host field.
By default, the Apache instance on the PEM server listens for encrypted connections on Port 8443. To disable SSL encryption, uncheck the box next to Use SSL?, and specify that the client should connect on Port 8080.

Note: The default certificate on the Apache server is self-signed. The PEM client may request additional user confirmation when connecting with SSL encryption enabled for the first time. If a PEM Server connection error dialog opens, use the options presented by the dialog to test the connection transport, confirming that you would like to accept the certificate. When you accept the certificate, the PEM client will allow the connection to the server.
We recommend that you add additional user accounts to the PEM server for everyday use, rather than using the postgres user account. You can create new users with the PEM client tool, or use the CREATE ROLE SQL statement; new users must be granted membership in the pem_admin role.
Check the box next to Login at startup? to instruct the PEM client to open the PEM Server Logon dialog when the client starts.
Use the fields on the SSH Tunnel tab (shown in Figure 4.3) to specify connection information for an SSH tunnel connection.
three
Check the box next to Use SSH tunneling to make the fields on the SSH Tunnel tab active. Then, provide connection information for the SSH tunnel host:
Specify the type of authentication that will be used when connecting to the tunnel host in the Authentication field. Select the radio button next to Password to specify that the PEM client will provide a password for authentication by the tunnel host. This is the default. Select the radio button next to Identity file to specify that the PEM client will provide a valid private key file when connecting.
If the tunnel host is expecting a private key file for authentication, use the Identity file field to specify the location of the key file.
If the tunnel host is expecting a password, use the Password/Passphrase field to specify a word or phrase that will be provided to the tunnel host for authentication.
Click OK to connect to the PEM server.
Tip: Apache/PHP must be running in order for the PEM client to connect to the PEM server. For detailed information about confirming the status of the Apache/PHP server, see Section 8.4, Controlling the Apache/PHP Server.
Once connected, the Global Overview monitoring dashboard is displayed (see Figure 4.4).
four
The example shown in Figure 4.4 shows that two agents are running (one on the PEM host itself, and one installed elsewhere), and one server is running (the PEM database server). Expanding the Agents node in the tree control displays the registered agents. Tables at the bottom of the Global Overview dashboard display the status of agents, database servers, and current alerts.

4 Adding Postgres Instances to PEM : 4.1 Logging on to the PEM server

Table of Contents Previous Next