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.

v8.1.0 (scheduled for 09/31/2015)

(Warning: some of the proposed features below are under development and may not be released as GA)

v8.0.3 (GA scheduled for 05/15/2015)
v8.0.2 (LA scheduled for 03/31/2015)

v8.0.1 (12/02/2014)

7.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 ressources 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:

Note that the highly graphical features such as arachitecture diagrams (configuration manager), data model diagrams, data or semantic lineage trace are now based on HTML5 which must be supported by your browser However some limited other feature may still depend on the Adobe Flash plugin until the next version.

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

Assuming a default installation on Windows with bundled Tomcat as follows:
   ${MIMB_VENDOR} = Meta Integration
   ${MIMB_PRODUCT} = Model Bridge
   ${MIMB_PROGRAMS} = C:\Program Files (x86}\Meta Integration
   ${MIMB_DATA} = C:\ProgramData\Meta Integration

Getting started with the following steps:

  1. Run the installer (based on InstallShield) by right-clicking and selecting "Run as Administrator" (where available),
    and then follow the steps and instructions.
  2. Start the license manager using:
    Start -> All Programs -> ${MIMB_VENDOR} -> ${MIMB_PRODUCT} -> ${MIMB_PRODUCT} License Manager.
    (You will need a License Key for your Host Id)
  3. Start the application server using:
    Start -> All Programs -> ${MIMB_VENDOR} -> ${MIMB_PRODUCT} -> ${MIMB_PRODUCT}.
    (Note that the application server can also be started as a service, more on that later)
  4. Connect to the server using your internet browser to open by default:
    (Note that the port numbers can be changed in ${MIMB_PROGRAMS}\data\tomcat\conf\server.xml)

It is recommended to set the application as a service with the following steps:

  1. Configure the user running the MIMB services in order to have full access rights to the needed files and applications. For example, the MIMB bridges involved in the metadata harvesting may need to invoke the SDK of third party software such as the COM based API of CA ERwin, or SAP BusinessObjects Universe Designer.
    In order to set such access rights, go to the services manager of Windows, right-click on the ${MIMB_VENDOR} ${MIMB_PRODUCT} service. Then, go to the "Log On" tab to define an account by name under which the service will run.
  2. Configure the memory usage (and limitations) used by the MIMB services in order to increase to cache more metadata in the server's memory (instead of database access), and therefor improving performance.
    You may configure for the app server by going to:
    Start -> All Programs -> ${MIMB_VENDOR} -> Configure Server as a Service, and go to the Memory tab.
    Note that the above step increases the memory of the MIMB application server for caching, but does not increase the memory used by MIMB bridges for harevesting, refer to Metadata Harvesting (MIMB) Setup.
  3. The ${MIMB_VENDOR} ${MIMB_PRODUCT} service, can be started, stopped, or set as automatic in the services manager of Windows.
    Alternatiely, such services can also be stopped or resteartd using entry menus in:
    Start -> All Programs -> ${MIMB_VENDOR} -> ${MIMB_PRODUCT}

6. Model Bridge (MIMB) Metadata Harvesting Setup

The Metadata Integration or Metadata Harvesting from third party databases, data modeling, data integration or business intelligence tools is performed by the integrated Meta Integration® Model Bridge (MIMB) software. By default, the installer software deploys and configures both MIMM and MIMB on the same Windows machine, where the MIMM Web Application Server accesses the MIMB Web Services locally. MIMB can also be installed and configured as a remote MIMB Agent on another machine: for example on a Windows machine where a Windows only third party software is needed by an MIMB bridge (such as SAP BuinessObjects universe).

Customize the following files using the embedded instructions (in comments):

Recommended customizations include:

7. User Interface Look & Feel Customization

Customize the following files and directories using the embedded instructions (in comments):

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