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

[an error occurred while processing this directive]

MIMB Bridge Documentation

MIMB Export Bridge to Meta Integration Metadata Management (MM) Semantic Hub Model (SHL) - Vendor Internal Bridge

Bridge Specifications

Vendor Meta Integration Technology, Inc.
Tool Name Meta Integration Metadata Management (MIMM)
Tool Version 11.x
Tool Web Site http://metaintegration.com/Products/MIMB/
Supported Methodology [Semantic Catalog] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model, Logical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), ETL/EAI/EII (Source and Target Data Stores, Transformation Lineage, Expression Parsing, Expression Conversion), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing, Expression Conversion), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure), Graphical Layout via MIR XMI File

SPECIFICATIONS
Tool: Meta Integration Technology, Inc. / Meta Integration Metadata Management (MIMM) version 11.x via MIR XMI File
See http://metaintegration.com/Products/MIMB/
Metadata: [Semantic Catalog] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model, Logical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), ETL/EAI/EII (Source and Target Data Stores, Transformation Lineage, Expression Parsing, Expression Conversion), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing, Expression Conversion), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure), Graphical Layout
Component: MirToSemanticCatalog version 12.0.0

OVERVIEW
This bridge exports a MIR model to a file in Meta Integration MSL format.

REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html

SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).


Bridge Parameters

Parameter Name Description Type Values Default Scope
File The bridge generates an YAML file, which is an representation of the imported MIR model. DIRECTORY     Mandatory
Miscellaneous INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="MICROSOFT 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.
ETL/Miscellaneous.txt

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

1G by default on 64bits JRE or as set in conf/conf.properties, 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 https://repo.maven.apache.org/maven2/ 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=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Wed, 26 Aug 2026 17:52:45

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