CData Drivers

Alation is partnering with CData for the driver and license distribution since a large number of Alation Custom DB connectors use CData drivers to connect to data sources and extract metadata. This document provides information on how to obtain a CData license from Alation and place a CData driver onto an Alation instance based on different scenarios.

How to Get a CData Driver?

You can get a CData driver in three different ways described below. Alation does not provide CData licenses for POCs and pilot deployments of the Alation Catalog. For POCs, use the trial license that can be downloaded from the CData website together with the trial version of the driver (Scenario 1). Alation provides licenses to customers who intend to evaluate the driver before purchase (Scenario 2) or who are willing to buy the driver from Alation (Scenario 3).

Scenario 1

You require a CData driver for a POC or for a pilot stage review with Alation:

Steps

Activity

1

Download the driver from the CData website. The driver .jar is packaged with a license file that has a validity of 30 days.

2

Install the driver on the Alation server. Refer to Install CData Driver on the Alation Instance.

3

Once the license expires or in case of any CData driver-related issues, contact the CData team at support@cdata.in or support@cdata.com.

Scenario 2

You are an existing customer of Alation and require a CData driver for validation purposes:

Steps

Activity

1

Download the driver .jar from the CData website.

2

Contact your Customer Success Manager to get the development/test RTK (runtime key). The RTK is a replacement for the license file.

3

Install the driver on the Alation server. Refer to Install CData Driver on the Alation Instance.

4

Contact the Alation Support team if you encounter any issues with Alation functionality when using this driver.

Scenario 3

You have decided to buy a CData driver from Alation:

Steps

Activity

1

Contact your Customer Success Manager to get the driver .jar file and the production RTK.

The production RTK is valid for 90 days and this period is tracked by Alation. Alation will provide a new production RTK once the previous one expires after 90 days. After you receive a new RTK, update it in your Alation instance.

2

Add the driver to the directory /opt/alation/alation-<XXXX>/data1/site_data/custom_drivers/ (path outside the Alation shell). See Add CData Driver to Alation Instance.

RTK (Runtime Key)

The runtime key (RTK) is a unique key provided by Alation as a license key to the driver. The RTK will have to be changed for every driver version upgrade. This RTK has to be appended to the JDBC URI of the respective connectors.

Example:

mongodb://10.13.64.245:27017?RTK=444752465641454E5454F4E58064242370000

Install CData Driver on the Alation Instance

Note

The following steps are applicable only to Scenario 1 and Scenario 2.

Perform the following steps to install the CData driver on the Alation instance:

  1. Download the driver from the CData website.

  2. Extract the following files from the driver package:

    • setup.jar

    • readme.txt

  3. Copy the setup.jar to a directory on the Alation host, for example /tmp.

    scp <path to the driver> <your_username@alation_host>:/tmp/
    
  4. Use SSH to connect to the Alation server.

  5. Go to the directory /opt/alation/alation-<XXXX>/data1/site_data/custom_drivers/. <XXXX> stands for your alation version, for example:

    cd /opt/alation/alation-5.14.0.113546/data1/site_data/custom_drivers/
    
  6. Create a subdirectory, for example, cdata_install.

    sudo mkdir cdata_install
    
  7. Move the setup.jar to this directory:

    sudo scp /tmp/setup.jar .
    
  8. Enter the Alation shell:

    sudo /etc/init.d/alation shell
    
  9. Go to the /custom_drivers/cdata_install directory inside the shell:

    cd opt/alation/site/site_data/custom_drivers/cdata_install
    
  10. Run the driver installation command given below. Substitute <version> with the actual version you find in the java directory of your instance. Then follow the prompts in the console and provide valid credentials to complete the installation of the driver:

    • Releases V R4 (5.8.x) - V R7 (5.12.x):

      sudo /opt/java/jdk-<version>/bin/java -jar setup.jar
      
    • Release 2020.3.x and newer releases:

      sudo /opt/java/amazon-corretto-<version>-linux-x64/bin/java -jar setup.jar
      
  11. This command installs the driver and creates a ../custom_drivers/cdata_install/lib/ subdirectory with a number of files. You will need two of these files: the .jar with the driver and the license file:

    • cdata.jdbc.<Product>.jar

    • cdata.jdbc.<Product>.lic

  12. If you do not have the RTK from Alation, use the .lic file. Copy the .jar and the .lic files to the opt/alation/site/site_data/custom_drivers folder.

  13. If you have the RTK from Alation, only copy the .jar file to the ../custom_drivers folder. You do not need to copy the .lic file in this case.

  14. Set the driver file ownership to alation.

    sudo chown alation:alation <driver_file_name>.jar
    
  15. Restart Alation:

    alation_action restart_alation
    
  16. After the restart, the driver should become visible in the list of drivers in the Alation user interface.

  17. Exit the shell: exit

Add CData Driver to Alation Instance

Use these steps to add a CData driver to the Alation server if you have obtained the driver from Alation using Scenario 3. When you receive the CData driver .jar from Alation, the driver does not require installation.

Prerequisite

You have the CData driver cdata.jdbc.[product].jar that was provided by Alation.

Steps to Add the Driver

  1. Copy the cdata.jdbc.[product].jar to a directory on the Alation host, for example, /tmp:

    scp <path to the driver> <your_username@alation_host>:/tmp/
    
  2. SSH to the Alation server:

    ssh <alation_hostname>
    
  3. Move cdata.jdbc.[product].jar to the the /opt/alation/alation-<XXXX>/data1/site_data/custom_drivers/ folder (<XXXX> stands for your Alation version).

  4. Enter the Alation shell:

    sudo /etc/init.d/alation shell
    
  5. Go to the opt/alation/site/site_data/custom_drivers directory.

    cd opt/alation/site/site_data/custom_drivers
    
  6. Set the driver file ownership to alation:

    sudo chown alation:alation <driver_file_name>.jar
    
  7. Restart Alation. This makes the .jar visible in the list of drivers in the Alation user interface.

    alation_action restart_alation
    
  8. Exit the shell: exit