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 Vertica 9, select vertica-9.

  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 import the SAP Java Connector (JCo).