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

README for Release Notes, Installation & Setup

Table of Contents

1. Overview

The Meta Integration® Model Bridge (MIMB) software provides solutions for:
  • Metadata Harvesting required for Metadata Management (MM) applications, including metadata harvesting from live databases (or big data), Data Integration (DI, ETL and ELT) , and Business Intelligence (BI) software.
  • Metadata Integration required for tool integration in the software development life cycle, including all necessary forward and reverse engineering steps to update each other tools: for example between Data Modeling (DM), Data Integration (DI), and Business Intelligence (BI) design tools.
  • Metadata Conversion required for legacy migration from an older design tool to a new one.

2. Copyright Notice

3. Release Changes

Disclaimer on Beta Bridges::
As part of its continuous research and development, MITI may develop prototypes of new bridges. Such bridges may be provided as beta bridges [i.e. marked as "(beta)" or "beta bridge"] to the MIMB OEM Software for the sole purpose of proof of concepts and customer feedback. Such beta bridges are not officially supported, and MITI reserves the rights to discontinue such beta bridges.

v10.1.0 (12/31/2019 - WARNING: Actual release date and features are subject to changes)

 

v10.0.1 (04/24/2019)

 

v10.0 (09/21/2018)

 

v9.1.0 (04/24/2017)

 

v9.0.2 (05/26/2016)

 

v9.0.1 GA (12/15/2015)
v9.0.0 GA (11/23/2015)

v8.0.3 GA (05/19/2015)
v8.0.2 LA (03/31/2015)

v8.0.1 (12/02/2014)

v7.2 (11/01/2013)

v7.1 (04/05/2013)

v7.0.4 (RC 09/15/2012 > LA 10/05/2012 > GA 10/12/2012)

v7.0.3 (RC 03/31/2012 > LA 04/30/2012 > GA 05/31/2012)

v7.0.2 GA (1/4/2012)

v7.0.1 GA (10/6/2011)

v7.0.0 LA (5/6/2011)


Limited Availability (LA) to OEM Partners for their metadata import/export of Data Modeling and design tools
(Note that version 7.0 was initially labeled as version 6.3, with Beta Early Access for OEM partners on 3/31/2011)

v6.2 (10/15/2010)

v6.1.0 (05/14/2010)

v6.0.6 (12/04/2009)

v6.0.5 (09/28/2009)

v6.0.4 (06/02/2009)

v6.0.3 (01/28/2009)

v6.0.2 (10/31/2008)

v6.0.1 (07/22/2008)

v6.0.0 (05/31/2008)

v5.2.5 only as incremental patches (XX/XX/2008)

v5.2.4 last GA release of 5.x (03/14/2008)

v5.2.3 (12/21/2007)

v5.2.2 (10/01/2007)

v5.2.1 (07/31/2007)

v5.2.0 (06/08/2007)

v5.1.1 (03/23/2007)

v5.1.0 (12/13/2006)

5.0.6 (10/31/2006)

5.0.5 (09/06/2006)

5.0.4 (08/01/2006)

5.0.3 (07/07/2006)

v5.0.2 (06/02/2006)

v5.0.1 (04/21/2006)

v5.0.0 (03/28/2006)


General improvements: Other improvements:

v4.3.0 (10/21/2005)

v4.2.4 (09/30/2005)

v4.2.3 (08/30/2005)

v4.2.2 (07/18/2005)

v4.2.1 (06/29/2005)

v4.2.0 (05/27/2005)

v4.1.6 (1/07/2005)

v4.1.5 (12/01/2004)

v4.1.4 (11/24/2004)

v4.1.3 (10/08/2004)


WARNING: all libraries have been recompiled because of improvements related to the bridge Manager library

v4.1.2 (08/27/2004)


WARNING: The Meta Integration v4.1.2 tools now run on virtually any versions of Windows and Unix operating systems (currently packaged for Sun Solaris and Linux). Consequently, the source code has been upgraded for C++ 98 compliance, and therefore all libraries and executable have been recompiled (even when no modifications were performed).

v4.1.1 (08/16/2004)

v4.1.0 (07/23/2004)

v4.1.0 Release Candidate 1 (07/03/2004)

v4.1.0 Beta3 (06/17/2004)

v4.1.0 Beta 2 (05/14/2004)

v4.1.0 Beta 1 (05/03/2004)

v4.0.9 (04/09/2004)

v4.0.8 (03/23/2004)

v4.0.7 (03/12/2004)

v4.0.6 (03/08/2004)

v4.0.5 (02/06/2004)

v4.0.4 (01/23/2004)

v4.0.3 (12/19/2003)

v4.0.2 (12/15/2003)

v4.0.1 (11/21/2003)

v4.0.0 (10/24/2003)

v3.1.2 (06/19/2003)

v3.1.1 (05/29/2003)

v3.1.1 Beta (05/22/2003)

v3.1.0 (04/30/2003)

v3.1.0 RC1 (04/25/2003)

v3.1.0 Beta (04/22/2003)

v3.0.10 (02/24/2003)

v3.0.9 (01/27/2003)

v3.0.8 (01/03/2003)

v3.0.7 (11/22/2002)

v3.0.6 (11/06/2002)

v3.0.5 (10/18/2002)

v3.0.4 (09/06/2002)

v3.0.3 (07/12/2002)

v3.0.2 (06/12/2002)

v3.0.1 (05/17/2002)

v3.0.0 (04/29/2002)

v3.0.0 Beta3 (03/22/2002)

v3.0.0 Beta2 (02/11/2002)

v3.0.0 Beta (12/14/2001)

v2.5.1.5 (03/22/2002)

v2.5.1.4 (12/03/2001)

v2.5.1.3 (11/19/2001)

v2.5.1.2 (11/06/2001)

v2.5.1.1 (10/29/2001)

v2.5.1 (10/12/2001)

v2.5.0.4 (10/05/2001)

v2.5.0.3 (09/07/2001)

v2.5.0.2 (08/02/2001)

v2.5.0.1 (07/30/2001)

v2.5.0 (07/13/2001)

2.5.0 Beta2 (07/09/2001)

2.5.0 Beta (06/29/2001)

4. System requirements

4.1 Important preliminary disclaimer notice on all requirements

The following requirements only define the minimal requirements to run the application with reasonable performance based on the provided tutorial, or small business use cases. The actual requirements for enterprise wide use cases based on larger models and configurations do require significantly greater resources to obtain acceptable performance.

The following requirements are based on:

Any other hardware/software configurations are acceptable as long as they provide the same (or better) results on the provided performance benchmark. In such case, if any problem is discovered (e.g. scalability or performance issues), then the customer must be able to reproduce the issue using an environment that conforms to the minimum performance requirements as defined herein.

Potential known issues include (but are not limited to) the following:

4.2 Web Client requirements

Users only need an internet browser:

4.3 Web Application Server Requirements

Hardware Minimum Requirements (based on physical hardware performance, not a virtual environment):

Operating System Requirements:

Web Application Server Engine Requirements:

Java Runtime Environment (JRE):

5. Model Bridge (MIMB) Application Server Setup

5.1 Application Server Installation

The MIMB Application Server is installed as follows:

5.2 Application Server Configuration

Essential customizations (e.g. directories, memory) of the MIMB Application Server can be performed in the following configuration file:
   %MIMB_HOME%\conf\conf.properties

Recommended customizations include:

Additional customizations (e.g. port numbers, Windows service names) of the MIMB Application Server can be performed in the following configuration file::
   %MIMB_HOME%\tomcat\conf\tomcat.properties

5.3 Application Server Execution

The easiest way to start the MIMB Application Server is to go to the software home directory and use the RestartApplicationServer utility (.bat on Windows or .sh on Linux).

5.4 Application Server Usage

You can connect to the server which can be simply achieved on Windows installation by opening Model Bridge link in the home directory.
In all cases, you can connect to the server using your internet browser to open by default:
http://localhost:19980/MIMB.
(Note that the above default port numbers may have been changed as defined in the section Application Server Configuration.

In addition to the above MIMB application Web UI, scripts can also be built using the MIMB command line utility (bin\MIMB.bat on Windows, and bin/MIMB.sh on Linux) which has the following parameters:

C:\MetaIntegration\bin\MIMB.bat -? [{ -? | --? | /? | --help }] Asking for help [{ -l | --logFile }] <string> log file: stderr by default [{ -r | --request }] <string> request XML File [{ -y | --reply }] <string> reply XML File [{ -i | --import }] <string> import bridge name: CaErwin3Erx, ... [{ -f | --from }] <string> file or directory to import from [{ -o | --importOption }]... <string> import bridge option: name=value [{ -e | --export }] <string> export bridge name: IbmRationalRose98, ... [{ -t | --to }] <string> file or directory to export to [{ -p | --exportOption }]... <string> export bridge option: name=value [{ -c | --consistency }] <int> validation level <Deprecated> : 0, 1 ,2 [{ -v | --validation }] <string> validation level: NONE, BASIC, ADVANCED [{ -m | --mapping }] <string> file to save the metamodel mapping to: xml or csv [{ -j | --join }] <string> metamodel mapping join type: INNER,OUTER_EXPORT,OUTER_IMPORT,FULL_OUTER [{ -X | --pid }] print process ID in the first output line of STDOUT </string> </string> </string> </Deprecated> </int> </string> </string> </string> </string> </string> </string> </string> </string> </string>

There are two ways to invoke MIMB from the command line. The first one is to explicitly provide parameters for the import and export, for example:

SET IMPORT=-i CaErwin9Xml SET IMPORT=%IMPORT% -o "File=c:\MetaIntegration\data\MIMB\MyErwinModel.xml" SET IMPORT=%IMPORT% -o "Import UDPs=As metadata, migrate default values" SET EXPORT=-e MetaIntegrationXml SET EXPORT=%EXPORT% -p "File=c:\MetaIntegration\data\MIMB\MyErwinModel.xlsx" call C:\MetaIntegration\bin\MIMB.bat %IMPORT% %EXPORT%

The above method has all the benefits of scripting with parameters, but has the disadvantage of fighting with encoding and special characters on the command line script. The alternative is to store all the MIMB import/export parameters within an MIMB request XML file.

These MIMB request XML files can be generated automatically from the MIMB application UI as follows. First, you need to edit c:\MetaIntegration\conf\conf.properties in order to uncomment/set M_CONVERSATION_DIRECTORY=c:\MetaIntegration\data\MIMB where the xml files will be generated (make sure the directory exists). Then, use the MIMB UI to perform the desired import and export.

The MIMB import request should have been saved as a file such as RunMimbExtendedRequest_19_8309388477083505776.xml which contains:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <RunMimbExtendedRequest commandLineFile="" language="" logLevel="" resetCache="" userIdentity="0-0-0-0-0-0-0-1_localhost" validationLevel="BASIC"> <Import bridgeDisplayName="CaErwin9Xml" bridgeIdentifier="CaErwin9Xml" disableLog="false" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="c:\MetaIntegration\data\MIMB\MyErwinModel.xml">c:\MetaIntegration\data\MIMB\MyErwinModel.xml</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import UDPs" clientSpecifiedText="As metadata, migrate default values">As metadata, migrate default values</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import relationship name" clientSpecifiedText="From relationship name">From relationship name</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import column order from" clientSpecifiedText="Physical order">Physical order</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import owner schemas" clientSpecifiedText="True">True</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import diagrams" clientSpecifiedText="Current view">Current view</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Move entities to subject areas" clientSpecifiedText="False">False</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Miscellaneous" clientSpecifiedText="" /> </Import> <Export bridgeDisplayName="MIMB Intermediate Step" bridgeIdentifier="MetaIntegrationXml" disableLog="true" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="">C:\MetaIntegration\bin\..\data\temp\tmp7589450715673988911_\mimb4731148277136809612.xml</BridgeParameter> </Export> </RunMimbExtendedRequest>

The MIMB export request should have been saved as a file such as RunMimbExtendedRequest_22_2010863314972480997.xml which contains:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <RunMimbExtendedRequest commandLineFile="" language="" logLevel="6" resetCache="" userIdentity="0-0-0-0-0-0-0-1_localhost" validationLevel="NONE"> <Import bridgeDisplayName="MIMB Intermediate Step" bridgeIdentifier="MetaIntegrationXml" disableLog="true" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="">C:\MetaIntegration\bin\..\data\temp\tmp7589450715673988911_\mimb4731148277136809612.xml</BridgeParameter> </Import> <Export bridgeDisplayName="MicrosoftExcel" bridgeIdentifier="MicrosoftExcel" disableLog="false" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="c:\MetaIntegration\data\MIMB\MyErwinModel.xlsx">c:\MetaIntegration\data\MIMB\MyErwinModel.xlsx</BridgeParameter> </Export> </RunMimbExtendedRequest>

Then a c:\MetaIntegration\data\MIMB\MyMIMBRequest.xml can be easily created by copying the import section of the first request and the export section of the second request as follows:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <RunMimbExtendedRequest commandLineFile="" language="" logLevel="6" resetCache="" userIdentity="0-0-0-0-0-0-0-1_localhost" validationLevel="NONE"> <Import bridgeDisplayName="CaErwin9Xml" bridgeIdentifier="CaErwin9Xml" disableLog="false" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="c:\MetaIntegration\data\MIMB\MyErwinModel.xml">c:\MetaIntegration\data\MIMB\MyErwinModel.xml</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import UDPs" clientSpecifiedText="As metadata, migrate default values">As metadata, migrate default values</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import relationship name" clientSpecifiedText="From relationship name">From relationship name</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import column order from" clientSpecifiedText="Physical order">Physical order</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import owner schemas" clientSpecifiedText="True">True</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Import diagrams" clientSpecifiedText="Current view">Current view</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Move entities to subject areas" clientSpecifiedText="False">False</BridgeParameter> <BridgeParameter bridgeParameterIdentifier="Miscellaneous" clientSpecifiedText="" /> </Import> <Export bridgeDisplayName="MicrosoftExcel" bridgeIdentifier="MicrosoftExcel" disableLog="false" userIdentity=""> <BridgeParameter bridgeParameterIdentifier="File" clientSpecifiedText="c:\MetaIntegration\data\MIMB\MyErwinModel.xlsx">c:\MetaIntegration\data\MIMB\MyErwinModel.xlsx</BridgeParameter> </Export> </RunMimbExtendedRequest>

Finally, run c:\MetaIntegration\bin\MIMB.bat -r myMIMBRequest.xml -y myMIMBReply.xml

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