Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
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.

Information note

You can also use Amazon RDS for MySQL files as a source. For more information, see Using the Qlik Replicate file channel.

To add an Amazon RDS for MySQL source endpoint to Qlik Replicate:

  1. In the Qlik Replicate Console, click Manage Endpoint Connections to open the Manage Endpoints Connections dialog box. Then click the New Endpoint Connection button. 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 endpoint. 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 Amazon RDS for MySQL database. This is optional.
  4. Select Source as the endpoint role.

  5. From the Type drop-down list, select Amazon RDS for MySQL.

    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. In the Server field, enter the host name or IP address of the computer on which the Amazon RDS for MySQL database is installed.
  7. Optionally, change the default port (3306).
  8. Type the Amazon RDS for MySQL authentication information (Username, Password) for the authorized user for this Amazon RDS for MySQL database. If you do not know this information, see your Amazon RDS for MySQL database Administrator (DBA).

    Information note

     

    • The User Name, Password are case sensitive.

    • Passwords containing curly brackets are not supported i.e. {}.

    Information note

    Make sure that the Amazon RDS for MySQL user entered in the Amazon RDS for MySQL Authentication section has the correct access privileges. For information on how to provide the required privileges, see Permissions.

SSL authentication options

In the Security section, you can configure Replicate to connect to the Amazon RDS for MySQL database using SSL.

  • SSL Mode: Select one of the following:
    • Preferred - Establishes an encrypted connection if the server supports encrypted connections, falling back to an unencrypted connection if an encrypted connection cannot be established.
    • None - Connect with a surname and password only.
    • Required - 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.
  • CA path - The path to the Certificate Authority (CA) that issued the client certificate file in PEM format.
  • Secret key path - The path to the client private key file in PEM format.
  • Client certificate path - The path to the client certificate requested by the server.

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!