Please note: You must ensure the
pg_hba.conf file of the server to be registered allows connections from the host of the PEM client. For information about modifying the
pg_hba.conf file, please see
Section 8.1.
To open the New Server Registration dialog, click on the
Add Server button on the client toolbar, or select
Add Server from the
File menu.
Use fields on the Properties Tab (shown in Figure 4.6) to enter the connection details for the new server.
•
|
Use the Service field to specify the name of a service configured in the pg_service.conf file.
|
•
|
Specify the Username that the new server will use when connecting to the database; the specified user must have membership in the pem-admin role.
|
•
|
Check the box next to Store password to instruct the PEM client to store the password for future connections.
|
•
|
Check the box next to Store on PEM Server to instruct the PEM client to store the definition of the server on the PEM server.
|
If the connecting role is not a member of pem_admin (they are connected using the read-only pem_user role), or the user has not logged in to the PEM server, the server definition is stored for the current user only.
•
|
Use the Team field to specify a PostgreSQL role name. Only PEM users who are members of this role, who created the server initially, or have superuser privileges on the PEM server will see this server when they log on to PEM. If this field is left blank, all PEM users will see the server.
|
Tip: Do not click
OK (yet) if you wish to register the server as a managed server. To register the server as a managed server, you must complete the
PEM Agent tab, binding the server to a PEM agent.
•
|
If applicable, use the Server Root Certificate File field to access a file browser, and specify the location of the server root certificate.
|
•
|
If applicable, use the Server Certificate Revocation List field to access a file browser, and specify the location of the certificate revocation list.
|
•
|
If applicable, use the Client Certificate File field to access a file browser, and specify the location of the client certificate.
|
•
|
If applicable, use the Client Key File field to access a file browser, and specify the location of the client key file.
|
Use the fields on the SSH Tunnel tab (shown in Figure 4.8) to implement SSH tunneling to the new server; check the box next to
Use SSH tunneling to enable the fields:
•
|
Check the box next to Use SSH tunneling to instruct PEM to use SSH tunneling to communicate with the monitored server.
|
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.
Use the fields on the Advanced tab (shown in Figure 4.9) to specify connection information for the new server:
•
|
Check the box next to Connect now to instruct the PEM client to negotiate a connection for the new server after you have completed the New Server Registration form and clicked OK.
|
•
|
Check the box next to Restore env? to instruct PEM to restore the browser environment when you reconnect to this server. If you regularly use different databases on the same server you may want to deselect this option.
|
•
|
If you specify a role name in the Rolename field, PEM will connect to the server using the identity specified on the Properties tab; after establishing a connection with the server, the client will assume the identity and permissions of the role specified in the Rolename field. The role specified on the Properties tab must be a member of the role specified on the Advanced tab.
|
•
|
Specify an SQL restriction in the DB restriction field to limit the databases displayed in the PEM client. For example, enter: 'live_db', 'test_db' to display only live_db and test_db in the PEM browser.
|
Use fields on the PEM Agent tab (shown in Figure 4.10) to create a
binding between the new server and a PEM agent. A binding provides the link between the PEM server and the PEM agent that allows the PEM server to monitor and manage that agent. The binding also provides the connection parameters that the agent uses when connecting to the PEM server.
•
|
Check the box next to Remote monitoring ? to indicate that the PEM agent does not reside on the same host as the monitored server. When remote monitoring is enabled, agent level statistics for the monitored server will not be available for custom charts and dashboards, and the remote server will not be accessible by some PEM utilities (such as Audit Manager, Capacity Manager, Log Manager, Postgres Expert, and Tuning Wizard).
|
Please Note: You may wish to specify a different Host address on the PEM agent tab than the address used on the
Properties tab. For example, you can configure the PEM agent to connect via a Unix socket to the monitored server, while the client connects using an SSL connection to a forwarded port on an external firewall (that is not appropriate for the agent).
•
|
Use the Database field to specify the name of the database to which the agent will initially connect.
|
•
|
Use the Allow takeover option to specify whether or not the monitoring of the server may be taken over by another agent in a High Availability environment.
|