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

MIMB Bridge Documentation

MIMB Import Bridge from MongoDB NoSQL Database

Bridge Specifications

Vendor MongoDB
Tool Name NoSQL Database
Tool Version 3.2
Tool Web Site
Supported Methodology [NoSQL Database] Multi-Model, Data Store (NoSQL / Hierarchical, Physical Data Model) via Java API

Tool: MongoDB / NoSQL Database version 3.2 via Java API
Metadata: [NoSQL Database] Multi-Model, Data Store (NoSQL / Hierarchical, Physical Data Model)
Component: MongoDB version 11.1.0

This bridge requires internet access to download third-party libraries:
- such as to download open source third-party libraries,
- and more sites for other third-party software such as database specific jdbc drivers.

The downloaded third-party libraries are stored into $HOME/data/download/MIMB/
- If https fails, the bridge then tries with http.
- If a proxy is used to access internet, you must configure that proxy in the JRE (see the -j option in the Miscellaneous parameter).
- If the bridge does not have full access to internet, that $HOME/data/download/MIMB/ directory can be copied from another server with internet access where the command $HOME/bin/ (or .bat) -d can be used to download all third-party libraries used by all bridges at once.

By running this bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third-party software libraries.

This bridge establishes a connection to the MongoDB server using native Java driver in order to extract the physical metadata.

Bridge will assign a data type for each JSON attribute according to following samples:
{ "$oid": "50a9c951300493f64fbffdb6" } STRING (SQL_VARCHAR)

{ "$date" : "2014-01-01T05:00:00.000Z"} DATE_8 (SQL_DATE)

{ "$date" : 1491461103897 } DATE_8 (SQL_DATE)

{ "$timestamp" : { "t" : 1412180887, "i" : 1 } } TIMESTAMP (SQL_TIMESTAMP)

"Thu Apr 06 2017 09:41:51 GMT+0300 (FLE Standard Time)" STRING (SQL_VARCHAR)

{ "$numberLong": "7494814965" } LONG_8 (SQL_BIGINT)


"some text" STRING (SQL_VARCHAR)

2.99792458e8 DOUBLE_10_5 (SQL_DOUBLE)



3.141592653589793238462643383279 DOUBLE_10_5 (SQL_DOUBLE)

"9007199254740992" STRING (SQL_VARCHAR)

"2.99792458e8" STRING (SQL_VARCHAR)

[1, 2, 3] array (SQL_ARRAY)


null undefined



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
Connection string This parameter overrides all other connection settings. It works in conjunction with the password parameter. Five stars in a row (*****) are used as a placeholder for the password, the actual password will be provided to the driver under the hood.

Example: mongodb+srv://testuser:*****

Please consult with the documentation here
Host Server URIs separated by commas. If port is not specified with a colon the default port assumed.

- Examples:
User The MongoDB user name on whose behalf the connection is being made.
If not specified, anonymous will be used.
Password The MongoDB user's password on whose behalf the connection is being made. PASSWORD      
Replica Set Replica Set name. STRING      
Authentication database Specify user authentication database. STRING   admin  
Databases Specify a list of MongoDB databases to be imported.

The list can have one or more database names separated by semicolons,
e.g. database1; database2
When the list is empty - all accessible databases are imported.
Collections The subset of collections to import expressed as a semicolon separated list of collections, e.g.
collection1; collection2

All Collections are imported if that list is empty.

Collection name patterns using a SQL like expression syntax:

- Inclusion syntax:
using '%, e.g.
A%; %B; %C%; D
- start with A or
- end with B or
- contain C or
- equal D

- Exclusion syntax:
using 'NOT", e.g.
A%; %B; NOT %SYS; NOT 'SYS%'
- where (name like A% or name like %B)
- and (name NOT like %SYS)
- and (name NOT like 'SYS%')

- Special characters:
using single quote, e.g.
OneWord%; 'Two Words%'
Number of sample documents Number of sample documents to be randomly drawn from each collection. The default value is 10. NUMERIC      
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"

-zip <filepath>

Folder to store MongoDb documents as Json files.


key1=val1;key2=val2 to manualy set hadoop configuration options.


Use it when do not want to provide data values, but metadata only.


Bridge Mapping

Meta Integration Repository (MIR)
(based on the OMG CWM standard)
"MongoDB NoSQL Database"
MongoDB (Database)
Mapping Comments
Attribute Column, Partition Column Columns which are part of the partition on the table.
Comment Comment  
Description Description  
ExtraConstraint Constraint  
InitialValue Initial Value  
Name Name  
NativeId Native Id  
Optional Nullable  
Position Position  
CandidateKey Object Identifier  
Description Description  
Name Name  
Class Document  
Comment Comment  
Description Description  
Name Name  
NativeId Native Id  
NativeType Native Type  
ClassDiagram Diagram  
Description Description  
Name Name  
ClassType Reference  
Description Description  
Name Name  
DatabaseSchema Connection  
Description Description  
Name Name  
DesignPackage Subject Area, Collection  
Comment Comment  
Description Description  
Name Name  
NativeId Native Id  
Index Index  
Description Description  
Name Name  
Join Logical Relationship  
Description Description  
Name Name  
StoreModel MongoDB Model  
Author Author  
Comment Comment  
CreationTime Creation Time  
Description Description  
ModificationTime Modification Time  
Modifier Modifier  
Name Name  
NativeId Native Id  
StoreType Store Type  
SystemMajorVersion System Major Version  
SystemMinorVersion System Minor Version  
SystemReleaseVersion System Release Version  
SystemType System Type  
SystemTypeOld System Type Old  

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.