Technical Documentation : Connectors : Adding a Denodo Connection
Was this helpful?
Adding a Denodo Connection
Prerequisites
  • A user with sufficient permissions is required to establish a connection with Denodo.
  • Zeenea traffic flows towards the data source must be open.
Note: You can find a link to the configuration template in Zeenea Connector Downloads.
Supported Versions
The Denodo connector was developed and tested with version 8.0 and 9.0.
Denodo Connector requires Denodo Data Catalog. This feature is not available in all versions.
In case you don't have this feature in your version, please consider our Generic JDBC Connector instead.
Installing the Plugin
The Denodo plugin can be downloaded here: Zeenea Connector Downloads.
For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.
Declaring the Connection
Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner.
In order to establish a connection with a Denodo instance, specifying the following parameters in the dedicated file is required:
Parameter
Expected Value
name
The name that will be displayed to catalog users for this connection
code
Unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id
The type of connector to be used for the connection. Here, the value must be denodo and this value must not be modified.
connection.url
Denodo Data Catalog address. Example: http://host:9090/denodo-data-catalog.
connection.username
Username
connection.password
User password
connection.jdbc.username
Optional - see configuration template
connection.jdbc.password
Optional - see configuration template
connection.jdbc.class_name
Optional - see configuration template
filter
To filter datasets during the inventory. See Filters
tls.truststore.path
The Trust Store file path. This file must be provided in case TLS encryption is activated (protocol https) and when certificates of Denodo servers are delivered by a specific authority. It must contain the certification chain.
tls.truststore.password
Password of the trust store file
tls.truststore.type
Type of the trust store file (PKCS12 or JKS). Default value is discovered from the file extension.
proxy.scheme
Depending on the proxy, http or https
proxy.hostname
Proxy address
proxy.port
Proxy port
proxy.username
Proxy Username
proxy.password
Proxy account password
fingerprint.sampling_max_rows
Max number of lines sampled from fingerprinting
User Permissions
In order to collect metadata, the running user's permissions must allow them to access and read databases that need cataloging.
Filters
Since version 1.1.0 of the plugin, the Denodo connector benefits from the feature of rich filters in the configuration of the connector.
Read more: Filters
The filter can apply to the following criteria:
Criteria
Description
serverUrl
VDP Server URL
Example: //denodo.example.com:9999/admin
database
Database name
table
View name
type
View type
Possible values: derived, interface, and base
Data Extraction
To extract information, the connector runs the following requests on the Denodo Rest API:
  • GET: /public/api/configuration/servers
  • GET: /public/api/views
  • GET /public/api/view-details
Collected Metadata
Inventory
Will collect the list of Denodo-derived views accessible by the user.
Dataset
A dataset is a Denodo derived view.
  • Name
  • Source Description
  • Technical Data:
    • Display Name
    • Model Name
    • Modification Date: Last dataset configuration modification date
    • Path
    • Tags
    • Categories
Field
Dataset field.
  • Name
  • Source Description
  • Type
  • Can be null: Not supported. Default value false.
  • Multivalued: Not supported. Default value false.
  • Primary Key: Not supported. Default value false.
  • Technical Data:
    • Technical Name
    • Native type
Unique Identifier Keys
A key is associated with each item of the catalog. When the object comes from an external system, the key is built and provided by the connector.
More information about unique identification keys in this documentation: Identification Keys.
Object
Identifier Key
Description
Dataset
code/server identifier/database name/view name
- code: Unique identifier of the connection noted in the configuration file
- server identifier
- database name
- view name
Field
code/server identifier/database name/view name/field name
- code: Unique identifier of the connection noted in the configuration file
- server identifier
- database name
- view name
- field name
Last modified date: 11/28/2025