Configuring the PEM Agent to use pgBouncer v7
You can use an RPM package to install a PEM Agent; for detailed installation information, please see the PEM Installation Guide, available from the EnterpriseDB website
Please note that PEM Agent which is responsible for sending SNMP notifications should not be configured with pgBouncer. For Example - If default PEM Agent installed along with PEM Server is used for SNMP notifications, then it should not be configured with pgBouncer.
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:
In above command, the command line argument --pem-agent-user instructs the agent to create an SSL certificate and key pair for the pem_agent_user1 database user in /root/.pem directory. For example:
They will be used by the PEM agent to connect to the PEM database server as pem_agent_user1. It will also create /usr/edb/pem/agent/etc/agent.cfg.
You will find a line mentioning the agent-user to be used in the agent.cfg configuration file. For example:
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
Add a line for agent_user to be used for the agent. For example:
Update the port to specify the pgBouncer port. For example:
Update the certificate and key path locations. For example:
Please note: as an alternative, you can run the agent self registration, but that will create a new agent id. If you do run the agent self-registration, you must replace the new agent id with existing id, and disable the entry for the new agent id in the pem.agent table. For example:
Please keep a backup of the existing SSL certificate, key file, and agent configuration file.