However, it is not intended to be a complete documentation of all the mapping algorithms involved in migrating metadata from any tool to any other tool, as the algorithms includes expression parsing,Įxpression conversions and other complex operations which may not be expressed as a mapping specification.ģ - Potential Loss of Metadata from Tool A to Tool B Therefore, it can only be used to analyze the scope of the metadata covered by the bridge algorithms. The metadata mapping specifications are intended to define the scope of metadata captured (by an import bridge) or populated (by an export bridge) in the 3rd party tool or format (tool and metamodel naming).
(select/click on a bridge to get the full specifications including Such specifications are part of the MIMB online help, and are also published on Limited to the published model mapping specifications for each integrated tool. Transformations implemented by Meta Integration Model Bridge (MIMB) are
Solution is to fix the original model, and then import it again.Ģ - Metadata Import/Export is limited to the "Bridge Specifications" " ERRORS" that are fatal and will prevent the export to any tool. The original tool, but is not required to use the MIMB export bridges.Ĭonsistency checks will report (in the log) " WARNINGS" on the source model, or Sometimes used as a substitute to the lack of model validation capabilities in attributes of a PK cannot have a null value),
Plus more advanced semantic checks specific to the technology of the source model: This level includes a more verbose version of the above basic consistency checks, Therefore, the user should still run any model validation or consistency check available in the target technology/tool. Note 3: the basic consistency may not be complete enough to catch all the model validation tests of the target tools. Some of the warnings or errors can be ignored. The export bridge or target technology/tool that will be used. Note 2: the basic consistency check may be more rigorous than needed by Note 1: the source model may pass the model validation provided by the original tool,īut still may fail the basic consistency check which may include more substantial testing required by the target tools. The detection of disconnected relationships, foreign keys not connected to any primary or alternate key, etc. This level corresponds all minimal consistency checks required to export, including (but not limited to) Responsibility when consistency check is turned off. Or produce an invalid model that may break the target tool. To fix the source model), then the imported model may break the export bridge, If the user purposely decides to turn off all consistency check (e.g. The user has the choice of 3 levels of consistency check: Having a centralized model validation (or consistency check) between the import and export phases allows to continuously improve the consistency check algorithms,Īnd avoids having each export bridge retest for the same model validity issues. Therefore, MIMB import bridges may be dealing with semantically incorrect or incomplete models which the MIR repository can save, but they may break the export bridges. Indeed, some of these models may still be under development (not yet completed), or the model validation may be a separate step (design tool menu entry, separate tool, or part of the model publication).
1 - Consistency Check of the Source Modelĭata Modeling, Data Integration (ETL/DI), Business Intelligence (BI) and other design tools supported by MIMB may not always save Other product and company names (or logos) mentioned herein may be the trademarks of their respective owners. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. Metadata Conversion required for legacy migration from an older design tool to a new one.Ĭopyright © Meta Integration Technology, Inc.
Including all necessary forward and reverse engineering steps to update each other tools:įor example between Data Modeling (DM), Data Integration (DI), and Business Intelligence (BI) design tools.
Metadata Integration required for tool integration in the software development life cycle, Including metadata harvesting from live databases (or big data), Data Integration (DI, ETL and ELT), and Business Intelligence (BI) software. Metadata Harvesting required for Metadata Management (MM) applications, The Meta Integration® Model Bridge (MIMB) software provides solutions for: