This section explains how to configure and personalize several aspects of the tool. It covers the following topics:

These parameters are global for all the users of the tool.

Elements Shown to the Users

You can specify which elements from the catalog the users are allowed to see:

  • Only Views

  • Only Web Services

  • Both

It affects the results shown in the following sections:

  • Databases browsing

  • Search (the user could only search in the catalog, not in the metadata)

  • Saved Queries (only saved queries from allowed elements are shown)

Browse Configuration

You can choose whether to Allow users to browse by Databases/Folders or not. If this option is disabled, users will not be able to access the Databases/Folders panel. In this case, you can also choose to Hide uncategorized views and web services from users (uncategorized views and web services will not appear in search results or when browsing by Categories or Tags).

User Interface

You can customize this tool to adapt it to the branding of your company. You can change the following:

  • The logo displayed on the top left.

  • The image displayed on the background of the Login page.

  • The image displayed on the background of the Welcome page.




Maximum size for uploaded images is 5MB.

Informative Message

You can add an informative message that will be displayed to all users when they access the Data Catalog. It will show up at the top of the page.

It can be used to display a welcome message, inform users when the service is expected to be down for maintenance, legal disclaimers, etc.

Informative Message Set-Up

Informative Message Set-Up

To enter the message in HTML, click Source in the editor, enter the HTML and click Source again. The Save button is disabled while in Source mode.

Informative Message

Informative Message

Allow HTML Descriptions and Properties

In this section, there is an option for specifying if user can create HTML properties and add HTML descriptions for categories, tags, databases, views, web services, groups and properties.

If HTML inputs are not allowed, element descriptions will always be displayed as plain text and existing HTML type properties will be converted to Long Text type. In addition, it will not be allowed to create HTML type properties.

Allow HTML inputs section

Allow HTML inputs section

Export Format Configuration

Regarding the exportation of the results of the queries of views and queries of web services, the administrator can configure:

  • The available export formats, among: CSV, HTML, Excel, Tableau (.tde) and Tableau (.hyper) (the section below explains how to enable the exports to Tableau). All enabled by default.

  • If by default, Data Catalog will generate these files with a header. This only applies to CSV, HTML and Excel files. When exporting to Tableau (.tde and Hyper), the files always include the header.

  • The maximum number of rows using each of the available formats.

  • If only the users with the role data_catalog_exporter in Virtual DataPort can export the results of the queries using each of the available exporters.

  • The default field delimiter character when exporting to a CSV file. As a delimiter character you can choose comma, pipeline, semicolon, space, tab or a user-defined delimiter character.


The double quote character (") cannot be set as a delimiter character.

Export Format Configuration

Export Format Configuration

Enabling Exports to Tableau

To enable the feature of exporting data to Tableau, you need to install the "Tableau Data Extract API" (for .tde format) or "Extract API 2.0" (for .hyper format) in the host where the Denodo Platform is installed. To do this, follow these steps:

  1. Go to the web site of the Tableau Data Extract API or Extract API 2.0.

  2. In this page, sign in and download the package C/C++/Java 64-bit version. Select Windows or Linux depending on the operating system where the Denodo server runs.

  3. Decompress the downloaded file.

  4. If the Denodo server runs on Windows, copy the files of the folder bin in the downloaded file to <DENODO_HOME>/jre/bin.

  5. If the Denodo server runs on Linux:

    1. Copy the files of the folder bin (for .tde) or bin/hyper (for .hyper) in the downloaded file to <DENODO_HOME>/jre/bin.

    2. Copy all the .so files of the folder lib64/dataextract (for .tde) or lib64/tableausdk (for .hyper) in the downloaded file to <DENODO_HOME>/jre/bin. Java subfolder files are no needed. For some Linux distributions, it is necessary to copy all the mentioned .so files to /lib directory of the Linux root folder.

  6. Restart the Data Catalog.

Database, View and Web Service Connection URIs

You can choose whether to display the Show Connection URIs button or not in the databases', views' and web services' details page. If you choose to show it, you can customize several parameters:

  • Introduction text of the connections panel: this will be shown in the panel instead of the default introduction.

  • URI Patterns: these describe how to access the server's databases through JDBC, ODBC, REST and OData. You may use the following variables in the pattern definitions: $vdp_host, $vdp_port, $odbc_port, $user_name, $database_name, $view_name, $webcontainer_port. These variables will be replaced by the appropriate values when showing the URIs to the user.

  • Option to configure whether to show or hide the Tableau data source connection button on the Summary tab of the views page.

Connection URIs

Connection URIs

Usage Statistics

The Data Catalog allows showing usage statistics of the views and web services by analyzing the usage data collected by Denodo Virtual DataPort. This feature requires some preparation steps, that will be explained later on this section.

When this feature is enabled, the details page of views and web services includes a new tab that shows some statistics about its usage (after they are collected and computed).

Steps to Configure the Gathering of Statistics

In order to show the Usage tab in the details page of views and web services, a user with administration privileges has to perform the following steps:

  1. Configure the Denodo Monitor to store the log of requests in a database (for instance, a table in Oracle). By default, Denodo Monitor saves the log information to a file. You need to modify this to use a database instead the log file.

    Edit <DENODO_HOME>/tools/monitor/denodo-monitor/conf/, search for the following text and follow the instructions of the file.

    # ================================================================================
    # Settings to store the output of the Virtual DataPort query monitor in a database
    # ================================================================================
  2. Do the following steps in Virtual DataPort:


    Due to license restrictions, you cannot use the Virtual DataPort server included in the Solution Manager.

    1. Create a database called denodo_logs. Although you could use a different name, if you do, you will have to modify the properties file of the Scheduler project that you will import in step #4.

    2. Create a JDBC data source that points to the database where Denodo Monitor will store the log of requests. If you already have this data source, you do not need to create a new one.

    3. Create a base view over the table request_notification of this data source. This is the table in which Denodo Monitor will store the requests log.

      This base view has to be called request_notification. Do not modify the names of the fields.

    4. Check that the cache engine of Virtual DataPort is enabled.

    5. Edit the file <DENODO_HOME>/resources/data-catalog/statistics/ and do these changes:

      • The properties ending with URL have to point to the Data Catalog. You may need to change them if the Tomcat server where the Data Catalog is running is not listening on the default port and/or is not resolvable as localhost from Virtual DataPort.

      • The properties ending with USER, PASSWORD, and PASSWORD.ENCRYPTED indicate the user name and password that will be used to call the REST API of the Data Catalog. By default, they are configured to use the default admin user with its default password.

      • The properties ending with TIMEOUT indicate the timeout (in milliseconds) of the calls to the Data Catalog API.

    6. Import the file <DENODO_HOME>/resources/data-catalog/statistics/usage-statistics.vql along with the properties files you just modified, into to database "denodo_logs".

      This will create a new FULL CACHE view, usage_statistics_src and associated objects.

  3. Enable the usage statistics in the Data Catalog. Follow these steps:

    • Configure the period to compute the usage statistics: Last day, Last month and/or All time.

    • Configure the elements over which to calculate the usage statistics: User, User Agent and/or Query.

    • Configure the connection details to the Virtual DataPort server containing the views over the Denodo Monitor requests log (needed to calculate the usage statistics), as explained before.

      • Database: the database where the views were created. If no value is specified in this field, the database of the Connection URI will be used.

      • View Name: the name of the view to query the usage statistics. The default value usage_statistics_src will be used if no value is specified in this field.

    Usage Statistics

    Usage Statistics

  4. Compute the statistics:

    At this point, the statistics need to be computed so Data Catalog can display them in the tab Statistics of the Data Catalog. To do this, there are two options:

    • Scheduled with Denodo Scheduler:

      1. Load the Denodo Incremental Cache Load stored procedure in Denodo Virtual DataPort.

      2. Create the INCREMENTAL_CACHE_LOAD stored procedure in Denodo Virtual DataPort.

      3. Import the file from <DENODO_HOME>/resources/data-catalog/statistics/ into Scheduler. It creates a project named data_catalog_statistics. This project contains:

        • A VDP data source. Edit it so it points to the VDP server and database configured in the step #1 (make sure to configure it with a user with enough privileges on that server and database).

        • A Scheduler job called load_cache_and_update_statistics. This is a job of type "VDP" that executes a view over the Data Catalog API to incrementally load the cache of the view usage_statistics_src and compute the usage statistics. Schedule this job to run periodically. We recommend scheduling it to run at least once a day (or more times if you desire to refresh the usage statistics more frequently).

    • Manually from the Data Catalog:

      You can compute the usage statistics by clicking the Compute usage statistics now button in the Data Catalog. The action dispatched with this button loads the cache with new data since the last time the cache was refreshed, and then computes the statistics (as Denodo Scheduler does, but in a scheduled way).


The recommended option to keep your statistics up to date is by using the Denodo Scheduler. You can modify the scheduling triggers according to your needs.

Add feedback