Start establishing a connection to PostgreSQL in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration flow, you can add an application to a flow simply by clicking + Add source or + Add destination.
In the resulting Application list, click PostgreSQL.
At this point, you’re presented with a series of options for modifying the PostgreSQL authentication.
- Name (required): Name the connection. Be sure to provide a clear and distinguishable Name as soon as the connection is created. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
- Mode (required): Select Cloud if you are connecting to an application on the cloud, and it is publicly accessible (for example, Salesforce or NetSuite). Select On-Premises if you are connecting to a server that is publicly inaccessible and has the integrator.io agent installed on it (for example, Production, AWS, VPC, or MySQL server).
- Agent (required, if On-premise selected for Mode; otherwise disabled): Select an agent from the list that you have created inside integrator.io. If you have not yet created an agent, see Integrate data through firewall with on-premise agent. To connect to an on-premise application, integrator.io requires that you install an agent on a networked computer. An agent is a small application that allows you to connect to data behind your firewall. When installing an agent, you will specify a unique access token, which then populates the Agent drop-down list. The installed agents connect to integrator.io and establish a reverse SSH tunnel that allows secure communication without the need to whitelist integrator.io’s IP addresses in your firewall settings. Multiple connections can use the same agent.
- Host (required): Enter the hostname or IP address of the server to connect to. These values were created during PostgreSQL server setup.
Note: You can find the hostname within the PostgreSQL user interface.
Right-click PostgreSQL 9.0 (localhost:5432) and select Properties.
- Database Name (required): Provide the database name created during PostgreSQL Server setup.
- Username (required): Enter the username created by the PostgreSQL Server administrator for this account.
- Password (required): Enter the password created by the PostgreSQL Server administrator for this account.
- Port (required): Enter the TCP port for the database engine, which is 5432 by default in PostgreSQL Server. Port 5432 is also the official Internet Assigned Number Authority (IANA) socket number for PostgreSQL Server, and PostgreSQL Server Management Studio (SSMS) uses it to manage PostgreSQL Server instances across the network.
- Use SSL (optional): Check this checkbox if you want to establish a secure connection to the database. This ensures that data in transit is encrypted.
- Certificate Authority (optional): This is an optional field if the database uses a certificate that doesn't match or chain to one of the known CAs. Use the CA option to provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA and therefore must be provided.
- Key (optional): Provide the optional private key in PEM format. This is necessary only if database server is using client certificate authentication.
- Certificate (optional): Provide optional cert chain in PEM format. This is necessary only if the database server is using client certificate authentication.
- Passphrase (optional): Provide an optional passphrase. This is used to decrypt the Key field. This is necessary only if database server is using client certificate authentication.
- Configure Properties (optional): By default, all data flowing through a connection record will get submitted to the respective endpoint application at the concurrency level configured for that connection record. Some use cases require multiple connections to share the same concurrency level, and this field allows you to specify that a connection should borrow concurrency from another connection such that the data flowing through both connections will get submitted to the endpoint application together via a shared concurrency model. For example, you might have three separate NetSuite connection records in your integrator.io account (for the purpose of isolating different permissions for different integrations), but you only want to provision one concurrent request for all three NetSuite connection records to share. To implement this use case, you would set up one of the three connections with a concurrency level 1, then set up the other two NetSuite connections to borrow concurrency from the other.