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 7.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 7.0 via JDBC API
Metadata: [Relational Database] Multi-Model, Data Store (Physical Data Model, Stored Procedure Expression Parsing)
Component: Denodo version 11.0.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 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.

-m <Java Memory's maximum size>
1G by default on 64bits JRE or as set in conf/, e.g.
-m 8G
-m 8000M

-j <Java Runtime Environment command line options>
This option must be the last one in the Miscellaneous parameter as all the text after -j is passed "as is" to the JRE, e.g.
-j -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.
-j -Dhttp.proxyHost= -Dhttp.proxyPort=3128 -Dhttps.proxyHost= -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-jre <Java Runtime Environment full path name>
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-v <Environment variable value>
None by default, e.g.
-v var1=value1 -v var2="value2 with spaces" <model name>
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.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.

Import system objects that are skipped by default.


Bridge Mapping

Mapping information is not available

Last updated on Fri, 25 Sep 2020 17:37:51

Copyright © Meta Integration Technology, Inc. 1997-2020 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.