Home
News
Meta Integration June 2009 - Meta Integration releases
new MIMB 6.0.4
Site Map
Home < width=46 height=34>

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

< Supported Tools | Readme < Description | About Standards width=17 height=22>

README

Table of Contents

  1. Copyright Notice
  2. Release Changes
  3. Installation
    1. System Requirements
    2. Software Requirements
    3. Setup
    4. License Key
  4. Using Meta Integration Model Bridge
  5. License Management
  6. Web Server Management
    1. Advanced Setup
    2. Web Page Customization
    3. Security Considerations
    4. Frequently Asked Questions
    5. Technical Support

    1. Copyright Notice

    Copyright © Meta Integration Technology, Inc. 1997-2009
    All Rights Reserved.
    Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
    Other product and company names (or logos) mentioned herein may be the trademarks of their respective owners.
    http://www.metaintegration.com

    2. Release Changes

    v6.1.0 (scheduled 12/31/2009)

    v6.0.6 (scheduled 10/01/2009)

    v6.0.5 (scheduled 08/01/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)

    v5.0.6 (10/31/2006)

    v5.0.5 (09/06/2006)

    v5.0.4 (08/01/2006)

    v5.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)

  7. 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)

  8. v4.0.2 (12/15/2003)

    v4.0.1 (11/21/2003)

    v4.0.0 (10/24/2003)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    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)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v3.1.0 RC1 (04/25/2003)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v3.1.0 Beta (04/22/2003)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    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)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v3.0.0 Beta3 (03/22/2002)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v3.0.0 Beta2 (02/11/2002)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v3.0.0 Beta (12/14/2001)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    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)

    9. v2.5.0.1 (07/30/2001)

  9. v2.5.0 (07/13/2001)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v2.5.0 Beta2 (07/09/2001)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    v2.5.0 Beta (06/29/2001)
    LICENSE KEY: your current license key may no longer be valid with this version. If so, please contact our technical support.

    10. 3. Installation

    3.1. System Requirements

    Hardware Requirements:

    3.2. Software Requirement

    Operating System Requirements:

    Web Application Server Engine Requirements:

    Java Runtime Environment (JRE):

    Some bridges use and require their respective tool's API. Therefore, make sure to properly install these tools and the API before using MIMB.

    See the MIMB Known Limitations for details.

    3.3. Setup

    It is recommended to uninstall any previous version of Meta Integration Model Bridge before starting this installation.

    If you already have a License Key you can provide it during the installation. Also, refer to the License Key section of this Readme.

    You should use the "Typical" setup for most installations. However, if you want to install the Import Bridge from Meta Integration works(MIW), the Export Bridge to Meta Integration Works or the JDBC driver Import Bridge, you must use the "Typical with java extensions" setup.

    3.4. License Key

    MIMB can be provided with an evaluation license which allows you to evaluate the bridges capabilities. The evaluation license will allow you to import any model and view it with the integrated Model Viewer.
    The export capability is limited and the bridges will automatically subset the model according to the following rules:

    The model will be automatically subsetted as necessary but you can also subset it manually to make sure that the concepts of any given portion of your models are preserved.

    Once you have received the license key you can install it by following these steps:

    You may also wish to use a server license. Please refer to that section for how to setup and use a server license.

    4. Using Meta Integration Model Bridge

    MIMB is a web service based application. Thus, one connects using a URL provided by your system administrator. For reference, one may refer to the URL defined in the shortcut on the server machine where MIMB is installed in Start Menu -> All Program -> Meta Integration -> Metadata Integration.

    The directory "Samples/Models" in the installation directory contains some sample export files from different Design Tools. You can start using Meta Integration Model Bridge with these files.

    5. License Management

    The Meta Integration Model Bridge (MIMB) allows for an unlimited number of users, connected via the web. One machine acts as a Server and there are no other installations of MIMB. The server must have a valid license.

    To set the license key, refer to the shortcut in Start Menu -> All Program -> Meta Integration -> License Management. The file at Meta Integration\conf\MIRSetup.xmlalso contains the license information. The installation procedure and license manager initializes this file so that you should not have to modify it unless you want to change the location of the log file or use the server with specific parameters. The file is self-documenting. Each parameter is given an XML tag, definition, usage and examples within the text of the file.

    6. Web Server Management

    6.1. Advanced Setup

    1. By default Tomcat 5 will associate the mime-type "text/plain" to files with an unrecognized file extension. This means that the generated files with an unrecognized file extension will be opened in the browser instead of the specified application on the machine. It is possible to change this behaviour on a per file extension basis by adding entries in the web.xml configuration file located at
         C:\Program Files\MetaIntegration\MIMBWeb\WEB-INF\web.xml
      The following file extensions have already been defined: cdm,dat,erx,mdl,mim,pdm.
      You may also have to configure your web browser as most modern browsers check both the file extension and the mime-type returned by the server instead of just the mime-type.
    2. When running one of the following bridges:
      • CA ERwin 7.x Model Manager import bridges
      • Ibm / Telelogic / Popkin System Architect import and export bridges
      the bridge must interact with the desktop when running as a service. To resolve this issue, you must set the service parameter "Allow service to interact with desktop".
      • Open the 'Control Panel' -> 'Administrative Tools' -> 'Services'
      • Right-click on the Meta Integration Web service, select Properties
      • On the Log On tab, click the checkbox 'Allow service to interact with desktop'
      • finally, restart the service.
    3. Note, one may control the application log level using a web browser by specifying the following URL: http://localhost:19980/MIMBWebServices/?logLevel=6.
    4. When running the Microsoft Excel bridge on Windows Vista, the MIMB server is unable to communicate with Excel directly if run as a service. In this case, it is necessary to run the MIMB web service from the desktop. To do so for the default installation with Tomcat web services, stop the Meta Integration service and start Tomcat (installation directory/tomcat/bin) using Startup.bat.
    5. Recommended practices for the SAP BusinessObjects Repository import bridge:
      • The MIMB server (agent) which will run the bridge should be installed on a machine with the SAP/Business Object client installation only. It should not be installed on a SAP BusinessObjects Server machine.
      • Such an MIMB server should be run as a desktop application (not as a service), using the "Start -> All Programs -> Meta Integration -> Server Restart.
      • Execute these bridges using a web client directly, rather than via remote access technologies such as Microsoft Netmeeting, SharedView or Office LiveMeeting, as COM-based remote access technologies have been known to interfere with the SAP/Business Objects API's and thus bridge function.
      • Ensure that there are no firewall restrictions for access to the SAP BusinessObjects API. If the bridge is failing to connect properly, disable the firewall temporarily to ensure that it is not the cause of the failure.
      • Always use the SAP BusinessObjects user "Administrator" when using this bridge, as some of the API calls that the bridge uses provide complete information only if one connects as the user "Administrator".
      • Be sure that the latest SAP BusinessObjects service packs are installed, and that they are installed consistently on the server and client machines.

    6.2. Web Page Customization

    To customize the look of MIMBWeb, edit the properties in the "MIRWeb.properties" file. This file is located in the (installation)\conf directory.

    The following are different properties that can be customized:

    6.3 Security Considerations

    6.6.1 HTML encryption with SSL (https)

    Please follow the instructions in the Tomcat documentation on upgrading to SSL if you wish to do so, as it should not affect the MIMB Web Application.

    7. Frequently Asked Questions

    1. When launching the self extracting executable, an "Overwrite Protection" window appears: "The following file is already installed on your system".

    This is because you have launched this executable shortly after a previous installation and the previous InstallShield Setup has not yet finish its cleanup. Click on "Cancel" and restart the program. If you click on any other button, you may experience problem during the installation because some files would not have been copied correctly. Typically, an error (-113) will occur during the move data process. If you experience such an error, wait a few seconds then restart the installation.

    8. Technical Support

    The best way to get support is to send an email to with a detailed description of your problem, the MIMB version that you use and your platform.

    You can also get more information about our products by going to our Web Site, http://www.metaintegration.com or sending an email to .

    < Supported Tools | Readme < Description | About Standards width=17 height=22>

    Copyright © Meta Integration Technology, Inc. 1997-2009 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.
    http://www.metaintegration.com