Importing Extensions¶

Importing a JDBC Driver¶

To import a JDBC driver, follow these steps:

1. Click the menu File > Extensions management.

2. Click the tab Libraries and then, click Import.

3. In the new dialog, in Resource type, select jdbc.

4. In Version, select the driver you are going to upload. For example, if you are going to upload the driver of MySQL 5, select mysql-5.

5. Click Add and select the file(s). To select more than one file, hold the key Ctrl and select each file.

6. Click Ok to upload the file(s) to Virtual DataPort.

Importing a JDBC Driver for a Database that is not Listed¶

Occasionally, you may need to connect to a database for which there is not a specific adapter:

1. When connecting to a database for which Denodo does not provide an adapter (you have to use the Generic JDBC adapter).

2. Or, Denodo provides an adapter for the database but for an older version. In this case, depending on the database, you may or may not need to import a new driver. For example, for Oracle you can use the driver of an older version to connect to a newer version. But for other databases, you do need to use the driver of the new version.

In this case, follow these steps:

1. Click the menu File > Extensions management.

2. Click the tab Libraries and then, click Import.

3. In the new dialog, in Resource type, select jdbc_other.

4. In Custom version, enter a name of this driver. This is the name you will select in the dialog to configure the JDBC data source. For example “mysql-8”.

5. Click Add and select the file(s) of the driver. To select more than one file, hold the key Ctrl and select each file.

6. Click Ok to upload the file(s) to Virtual DataPort.

7. Open the data source. If your already had it open, close it and open again to refresh the list of drivers.

8. In the configuration of the JDBC data source, in Database adapter, select this:

   1. Generic if you are connecting to a database for which Denodo does not provide an adapter.

   2. To connect to a database that is listed here but the version you are connecting to is newer than the versions listed here, select the most recent adapter for this database.

   Then, in Driver class path, select the driver you just uploaded.

Importing Other Types of Elements¶

Options available in the Resource type list of the dialog Import resources (tab Libraries):

• jdbc: for the JDBC driver of a database for which Denodo has a connector but does not include its JDBC driver.

• jdbc_other: for the JDBC driver for a database that is not listed in this dialog or whose version is not listed. You will also have to enter a Custom version.

• essbase: to import the driver for Oracle Essbase.

• jar: to import a jar file that is not a JDBC driver.

  Note

  To import a custom function, a custom policy, a custom wrapper or a Denodo stored procedure, use the tab Extensions. If the extension depends on other jars, upload the dependencies - not the extension itself - as an element of type “jar”.

• library: to import “dll” files or a “so” files.

• sapjco: to install the files of the SAP Java Connector (JCo).

• vault: to import the files required by the credentials vault.

importResources -t resource-type [-v resource-version] -p path-to-resource

importResources --type <resource-type>
                [--version <resource-version>]
                --path <path-to-resource>

importResources --type jdbc --version mysql-5 --path /my-drivers/mysql/mysql-connector-java-5.1.49-bin.jar

importResources --type jdbc_other --version my-mysql-8 --path /my-drivers/mysql/mysql-8/

importResources --type kerberos --version keytab --path /my-kerberos-conf/denodo.keytab