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 configure the CDP Private Cloud target endpoint in 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 endpoint. This can be any name that will help to identify the endpoint being used.
3. In the Description field, type a description that helps to identify the CDP Private Cloud endpoint. This is optional.
4. Select CDP Private Cloud as the endpoint Type.

5. In the Security section, do the following:

1. To encrypt the data between the Replicate machine and HDFS, select Use SSL. In order to use SSL, first make sure that the SSL prerequisites described in Prerequisites been met.

   In the CA path field, specify one of the following items:

   • The directory containing the CA certificate.

   • The full path to a specific CA certificate.

2. Select one of the following authentication types:

   • User name - Select to connect to the CDP Private Cloud cluster with only a user name. Then, in the User name field, specify the name of a user authorized to access the CDP Private Cloud cluster.

   • User name and password - Select to connect to the CDP Private Cloud NameNode or to the Knox Gateway (when enabled - see below) with a user name and password. Then, in the User name and Password fields, specify the required user name and password.

   • Kerberos - Select to authenticate against the CDP Private Cloud cluster using Kerberos. Replicate automatically detects whether Qlik Replicate Server is running on Linux or on Windows and displays the appropriate settings.

     Information note

     Note  In order to use Kerberos authentication on Linux, the Kerberos client (workstation) package should be installed.

     Qlik Replicate Server on Linux:

     When Qlik Replicate Server is running on Linux, provide the following information:

     • Realm: The name of the realm in which your CDP Private Cloud cluster resides.

       For example, if the full principal name is john.doe@EXAMPLE.COM, then EXAMPLE.COM is the realm.

     • Principal: The user name to use for authentication. The principal must be a member of the realm entered above.

       For example, if the full principal name is john.doe@EXAMPLE.COM, then john.doe is the principal.

     • Keytab file: The full path of the Keytab file. The Keytab file should contain the key of the Principal specified above.

     Qlik Replicate Server on Windows:

     When Qlik Replicate Server is running on Windows, provide the following information for accessing your Active Directory KDC:

     Information note

     When the Replicate KDC and the CDP Private Cloud KDC are in different domains, a relationship of trust must exist between the two domains.

     • Realm: The name of the realm/domain in which your CDP Private Cloud cluster resides (where realm is the MIT term while domain is the Active Directory term).
     • Principal: The user name to use for authentication. The principal must be a member of the realm/domain entered above.
     • Password: The password for the principal entered above.

     If you are unsure about any of the above, consult your IT/security administrator.

     For additional steps required to complete setup for Kerberos authentication, see Using Kerberos authentication on Windows.

6. If you need to access the Hortonworks CDP Private Cloud distribution through a Knox Gateway, select Use Knox Gateway. Then provide values for the following fields:

   Information note

   To be able to select this option, first select Use SSL and then select Username and Password from the Authentication type drop-down list.

   • Knox Gateway host - The FQDN (Fully Qualified Domain Name) of the Knox Gateway host.
   • Knox port - The port number to use to access the host. The default is "8443".

   • Knox Gateway path - The context path for the gateway. The default is "gateway".

     Information note

     The port and path values are set in the gateway-site.xml file. If you are unsure whether the default values have been changed, contact your IT department.

   • Cluster name - The cluster name as configured in Knox. The default is "cdp-proxy-api".

7. In the HDFS Access section, enter the following information:

   • In the NameNode field, specify the IP address or hostname of the NameNode.

     Information note

     This is the Active node when High Availability is enabled (see below).

   • Replicate supports replication to an HDFS High Availability cluster. In such a configuration, Replicate communicates with the Active node, but switches to the Standby node in the event of failover. To enable this feature, select the High Availability check box. Then, specify the FQDN (Fully Qualified Domain Name) of the Standby NameNode in the Standby NameNode field.

   • In the Port field, optionally change the default port (9870).

   • In the Target Folder field, specify where to create the data files on HDFS.

   Information note

   The Target folder name can only contain ASCII characters.

8. In the Hive Access section, do the following:

   1. From the Access Hive using drop-down list, select one of the following options:

      Information note

      When the Use Knox Gateway option is selected or when No Access is selected, the Host and Port fields described below are not relevant (and are therefore hidden).

      • ODBC - Select this option to access Hive using an ODBC driver (the default). Then continue from the Host field.

      • No Access - When this option is selected, after the data files are created on HDFS, Replicate will take no further action.
   2. In the Host field, specify the IP address of the Hive machine.
   3. In the Port field, optionally change the default port (10000).
   4. In the Database field, specify the name of the Hive target database.