Importing Extensions

To import any of the following elements, use the dialog Extensions management:

To open this, click the menu File > Extension Management. Then, depending on the element you are going to import, go to one tab or the other:

  • Tab Extensions: to import a Denodo stored procedures, custom functions, custom wrappers and custom policies.

  • Tab Libraries: to import any other resource.

When you import an extension, the file is uploaded to the installation of Virtual DataPort where you are connected. In addition, if you configured Virtual DataPort to store the catalog on an external database, the extensions will also be stored on this database and it will become available to the Virtual DataPort servers that share the same database.

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.

To import a JDBC driver for a database that is not listed in this dialog or whose version is not listed, in Resource type, select jdbc_other and enter a value for Custom version.

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.

Using a Script to Upload Extensions

Note

We recommend to stop Virtual DataPort server before executing this script (mandatory using Apache Derby as catalog database)

Instead of uploading these extensions using the Administration Tool, you can do it using the script “importResources”. This script is located in the directory <DENODO_HOME>/bin.

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

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

Options available in the parameters --type and --version (if applies):

  • essbase: to import the driver for Oracle Essbase. Versions available ‘11’ and ‘9’.

  • jar: to import a jar file.

  • jdbc: for the JDBC driver of a database for which Denodo has a connector but does not include its JDBC driver. Requires parameter --version with one of the known drivers. For example, 'mysql-5'

  • jdbc_other: for the JDBC driver for a database that is not listed in this dialog or whose version is not listed. Requires parameter --version with a custom version name.

  • kerberos: to import Kerberos files. Requires parameter --version with value keytab for importing the keytab file, or krbconf for importing the configuration file used for server authentication with Kerberos.

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

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

  • vault: to import extensions associated with Credentials Vault. Requires parameter --version and only cyberark is supported by now.

Parameters of the importResources script

Parameter Name

Description

-t

--type <resource-type>

Type of the resource to import.

-v

--version <resource-version>

Version or type of the resource to import.

-p

--path <path-to-resource>

Path to a file or to a directory. In case of directory, all files inside are imported.

Examples

Example 1:

Uploads a JDBC resource associated with version ‘mysql-5’.

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

Example 2:

Uploads a JDBC_OTHER resource associated with custom version ‘my-mysql-8’. All files at path are imported.

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

Example 3:

Uploads a new keytab for kerberos authentication.

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