Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Denodo Virtual DataPort

Bridge Specifications

Vendor Denodo
Tool Name Denodo Virtual DataPort
Tool Version 6.0 to 8.0
Tool Web Site
Supported Methodology [Relational Database] Multi-Model, Data Store (Physical Data Model, Stored Procedure Expression Parsing) via JDBC API

Tool: Denodo / Denodo Virtual DataPort version 6.0 to 8.0 via JDBC API
Metadata: [Relational Database] Multi-Model, Data Store (Physical Data Model, Stored Procedure Expression Parsing)
Component: Denodo version 11.1.0

Imports metadata from a DENODO Platform using JDBC.
The bridge imports the following data sources and views:
- data sources: JDBC, delimited file (data route: Local)
- views: base view, materialized view, derived views (join view, union view, minus view, intersection view, selection view, interface view)

User Privilege Requirements:
You can use any custom read only user with at least the following privileges:
- Connect, Metadata, and Read privileges are required to read metadata
- Admin privilege is required to read metadata about data sources that you did not create/own (without the data source metadata, the Denodo model cannot stitch views to their source models)
- Write privilege is required for Denodo version 7 (or newer) to obtain the SQL used to create a view (to execute the command DESC VQL VIEW etc.)

Java Requirements:
You may need to use the Miscellaneous parameter to specify a Java environment supported by Denodo Virtual DataPort, if the default JVM is not compatible (OpenJDK 11 instead of Oracle JVM 8) (e.g. -jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe").

Q: What Denodo patches must be applied?
A: For Denodo Platform 6.0 only, you must apply patch 20171205 or newer.

Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/ with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

Bridge Parameters

Parameter Name Description Type Values Default Scope
Driver location This parameter is optional.

The JDBC driver located in the directory <DENODO_HOME>/tools/client-drivers/jdbc/denodo-vdp-jdbcdriver.jar

The 'com.denodo.vdp.jdbc.Driver' JDBC driver with the 'Denodo Native Driver' name is required.
JDBC connection URL Syntax of the JDBC connection URL:
jdbc:vdb://<hostName>:<port>/<databaseName>[?<paramName>=<paramValue> [&<paramName>=<paramValue>]* ]
The name of the database is mandatory.
For example:
JDBC connection URL sample

If the name of the database contains non-ASCII characters, they have to be URL-encoded, e.g.
The name of the database is "ใƒ†ใ‚นใƒˆ", the connection URL to the database will be the following:
STRING     Mandatory
User The database user name on whose behalf the connection is being made. STRING      
Password The database user's password on whose behalf the connection is being made. PASSWORD      
Database Name of the database you would like to import. REPOSITORY_SUBSET      
Views Views you would like to import.
When this parameter is empty all available non-system Views are imported.
Use semicolons to separate View names in the list (e.g. view1;view2).

You can specify view name patterns using '%', '_' or 'NOT' keywords.
'%': represents a segment of text of any length, including an empty text.
'_': represents any character (only one character).

Patterns support inclusions and exclusions, e.g.
"A%; %B; %C%; D" that tries to get view names that:
- start with A or
- end with B or
- contain C or
- equal D

To exclude a pattern, prefix it with 'NOT', e.g.
"A%; NOT %test"
This imports views with name started with 'A' and not ended with 'test'
Miscellaneous INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.

-java.memory <Java Memory's maximum size> (previously -m)

1G by default on 64bits JRE or as set in conf/, e.g.
-java.memory 8G
-java.memory 8000M

-java.parameters <Java Runtime Environment command line options> (previously -j)

This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g.
-java.parameters -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access and exceptionally a few other tool sites) in order to download the necessary third-party software libraries.
Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it.
-java.parameters -java.parameters -Dhttp.proxyHost= -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass

-java.executable <Java Runtime Environment full path name> (previously -jre)

It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-java.executable "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-environment.variable <name>=<value> (previously -v)

None by default, e.g.
-environment.variable var2="value2 with spaces"


Override the model name, e.g. "My Model Name"

-prescript <script name>

The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"


Clears the cache before the import, and therefore will run a full import without incremental harvesting.

If the model was not changed and the -cache.clear parameter is not used (incremental harvesting), then a new version will not be created.
If the model was not changed and the -cache.clear parameter is set (full source import instead of incremental), then a new version will be created.

-backup <directory>

Full path of an empty directory to save the metadata input files for further troubleshooting.

Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following options allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs.

-connection.cast ConnectionName=ConnectionType

Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g.
-connection.cast "My Database"="SQL SERVER".
The list of supported data store connection types includes:

-connection.rename OldConnection=NewConnection

Renames an existing connection to a new name, e.g.
-connection.rename OldConnectionName=NewConnectionName
Multiple existing database connections can be renamed and merged into one new database connection, e.g.
-connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase

-connection.split oldConnection.Schema1=newConnection

Splits a database connection into one or multiple database connections.
A single database connection can be split into one connection per schema, e.g.
-connection.split MyDatabase
All database connections can be split into one connection per schema, e.g.
-connection.split *
A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g.
-connection.split MyDatabase.schema1=MySchema1 DestinationPath=SourcePath

Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file).
On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a HIVE table implemented (external) by the same file specified using a relative path with default file name and extension, e.g. hdfs://host:8020/users/user1/folder/file.csv=/user1/folder
On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g. /users/John=/data /users/paul=/data
On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g. M:\=C:\data N:\=C:\data

-connection.casesensitive ConnectionName

Overrides the default case insensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g.
-connection.casesensitive "My Database"


Import system objects that are skipped by default.

-datasource.double_quotes DataSourceName

Interprets the double quoted strings as identifiers in ANSI_QUOTES mode (e.g. MySql etc.).

-model.split (previously -multiModel)

Splits a large server model into multi models (e.g. one database per model).
Warning: this is a system option managed by the application calling this bridge and should not be set by users.


Bridge Mapping

Mapping information is not available

Last updated on Fri, 11 Nov 2022 17:39:50

Copyright © Meta Integration Technology, Inc. 1997-2022 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.