Skip to main content Skip to complementary content

Setting general connection properties

This section describes how to configure general connection properties. For an explanation of how to configure advanced connection properties, see Setting advanced connection properties.

To add a PostgreSQL endpoint source database to Qlik Replicate:

  1. In the Qlik Replicate console, click Manage Endpoint Connections to open the Manage Endpoint Connections dialog box. For more information on adding an endpoint to Qlik Replicate, see Defining and managing endpoints.
  2. In the Name field, type a name for your PostgreSQL database. This can be any name that will help to identify the database being used.
  3. In the Description field, type a description that helps to identify the PostgreSQL database. This is optional.
  4. Select Source as the database role.
  5. Select PostgreSQL as the database Type.

    Information note

    When this endpoint is used as a duplicated source in a Log Stream Staging setup, select the Read changes from log stream staging folder check box and then select the relevant Log Stream Staging task from the drop-down list.

    For information on setting up and managing Log Stream Staging tasks, see Using the Log Stream.

  6. Type the Server name. This is the name or IP address of the computer with the PostgreSQL database that you want to access.
  7. Optionally, change the default port (5432).
  8. Enter the PostgreSQL database authentication information (User name, Password) of an authorized PostgreSQL user.

    Information note

    Consider the following:

    • This information is case sensitive.

    • To determine if you are connected to the database you want to use or if the connection information you entered is correct, click Test Connection.

      If the connection is successful a message in green is displayed. If the connection fails, an error message is displayed at the bottom of the dialog box.

      To view the log entry if the connection fails, click View Log. The server log is displayed with the information for the connection failure. Note that this button is not available unless the test connection fails.

  9. Type the Database name or browse for a source database.

SSL authentication options

In the Security section, you can configure Replicate to connect to the PostgreSQL database using SSL.

  • SSL Mode: Select one of the following:
    • disable - Connect with a surname and password only.
    • allow - Establish an encrypted connection if requested by the server.
    • prefer - Establishes an encrypted connection if the server supports encrypted connections, falling back to an unencrypted connection if an encrypted connection cannot be established.
    • require - Establishes an encrypted connection if the server supports encrypted connections. The connection attempt fails if an encrypted connection cannot be established.
    • verify-ca - Similar to Required, but also verifies the server Certificate Authority (CA) certificate against the configured CA certificates. The connection attempt fails if no valid matching CA certificates are found.
    • verify-full - Similar to Verify CA, but also performs host name identity verification by checking the host name the client (i.e. Replicate) uses for connecting to the server against the identity in the certificate that the server sends to the client. The client checks whether the host name that it uses for connecting matches the Common Name value in the server certificate. The connection fails if there is a mismatch.
  • Client certificate path - The path to the client certificate requested by the server.
  • Secret key path - The path to the client private key file in PEM format.
  • CA path - The path to the Certificate Authority (CA) that issued the client certificate file in PEM format.
  • CRL path - The path to the CRL certificate. This file contains certificates revoked by certificate authorities. If the server certificate appears in this list, the connection will fail.
  • SSL compression -Select this option to compress the data before it is encrypted.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!