Bridge Specifications
| Vendor | Meta Integration Technology, Inc. |
| Tool Name | Meta Integration Repository (MIR) for Model Bridge (MIMB) |
| Tool Version | 11.x |
| Tool Web Site | http://metaintegration.com/Products/MIMB/ |
| Supported Methodology | [Metadata Management] 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 Profiling XML File |
SPECIFICATIONS
Tool: Meta Integration Technology, Inc. / Meta Integration Repository (MIR) for Model Bridge (MIMB) version 11.x via Profiling XML File
See http://metaintegration.com/Products/MIMB/
Metadata: [Metadata Management] 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: MetaIntegrationProfilingXml version 11.2.0
OVERVIEW
This export bridge generates the metadata under a MIR metamodel profile specific to the source technology / tool metamodel. The exported metadata can be in XML format (by default) or CSV files (one per metadata object).
The Meta Integration Repository (MIR) Metamodel is an evolution of the standard OMG CWM (Common Warehouse Metamodel) designed to support today's data technology and tools. The MIR metamodel is used as the neutral metadata format between any import bridge and any export bridge. The MIR metamodel is developed and maintained as a UML Class diagram but that is just the metamodel aspect which does not include the thousands of business rules used by any import bridge to populate the metadata, and any export bridge to forward engineer the metadata. In addition to its complexity, the MIR metamodel is neutral, therefore the metadata instances (e.g. a Snowflake, Talend or Tableau model) are difficult to comprehend for any data catalog / data governance end user because it does not look like their original metadata from many aspects: not only the metadata names are different, but the organizational aspect (grouping hierarchy) is different. This is why any import bridge has an associate MIR Profiles for each supported technology / tool.
These MIR profiles are metamodels representing each technology / tool metamodel matching as much as possible the original metadata. These MIR profiles are also developed and maintained as UML class diagrams, obviously derived (semantically mapped) from the MIR metamodel. The generated MIR profiles per technology/tool are delivered as directories containing XML files within
conf/MIRProfiles/profiles/.
Most export bridge have their own MIR profile because of their unique proprietary custom metamodel, that this the case of most BI (like BusinessObjects, Cognos, PowerBI, Qlik, Tableau, and DI/ETL/ELT (PowerCenter, Talend, etc.) tools. However, some MIR profiles are shared on common technology, in particular relational database profile which is used for all RDBMS databases (like Oracle, SQLServer, PostgreSQL, Snowflake, DataBricks, etc.).
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 | ||
| Output Directory | Specify the output directory where to save the profiling output. If this is a single model, then there would be one file model.xml and if its a multi-model, then there would be multiple files with a main.xml for the directory structure. | DIRECTORY | Mandatory | ||||
| Output Format | Select the output format. | ENUMERATED |
|
XML | |||
| Profile ID | Specify the profile identifier to use. If this is empty, then the export bridge will decide based on the input model. | NUMERIC | |||||
| 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 METAINTEGRATION PROFILING EXPORT OPTIONS -ProfiledObjectIdentity To generate object identity according to the Profile. -profiler.new To use a new Profiler implementation for database multimodels -profiler.cache.size 10 To control the size of memory cache, how many models are loaded, staged in memory -connection.dissolve To skip stitching links to external connection models -skip.lineage To skip all lineage links -lineage.summary.skip To skip summary lineage links -lineage.detailed.skip To skip detailed lineage links |
STRING |
Bridge Mapping
Mapping information is not available