06/2008 - Meta Integration releases new Web 2.0 enabled MIMB 6.0

Meta Integration® Repository (MIR)
Software Development Kit (SDK)

README

Table of Contents

1. Copyright Notice
2. Release Changes
3. Installation
   1. C++ SDK requirements
   2. Java SDK requirements
4. Documentation
5. How to access the Java SDK
   1. On Windows 2000, XP, or 2003 Server
   2. On Unix / Linux
6. How to access the C++ SDK
   1. On Windows 2000, XP, or 2003 Server
   2. On Unix / Linux x86
7. Frequently Asked Questions
8. Technical Support

1. Copyright Notice

Copyright © Meta Integration Technology, Inc. 1997-2006.
All Rights Reserved.
Meta Integration® Model Bridge (MIMB), Works (MIW), Repository (MIR), Repository SDK (MIRSDK), and Database SDK (MIDBSDK) are trademarks 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

• v5.2.2 (10/01/2007)
  • No change
• v5.2.0 (06/08/2007)
  • No change
• v5.1.1 (03/23/2007)
  • no change
• v5.1.0 (12/13/2006)
  • SDK: improved repository and model browsing with MIRElement::nativeType and MIRElement::nativeId properties
  • SDK: improved repository management with MIRRepositoryObject::modifier and MIRRepositoryObject::lastModificationTime
  • SDK: improved configuration management with MIRConfigurationFormat and link to MetadataFormat
  • SDK: improved datamodeling with updated MIRSQLViewEntity, MIRSQLViewAssociation
  • SDK: improved datamodeling with MIRGeneralization::complete and MIRGeneralization::exclusive
  • SDK: improved OLAP modeling with MIRLevel default link to MIRLevelAttribute
  • SDK: improved BI modeling with MIRReportAxis, MIRReportBlock, MIRPrompt, MIRPromptAnswer, MIRReportItem reference link, MIRReport classifier link, MIRReportItem condition link, MIRReportAttribute::usage and MIRDataAttribute::usage properties
  • SDK: improved ETL modeling with MIRTransformation::transformationType property
• v5.0.6 (10/31/2006)
  • no change
• v5.0.5 (09/06/2006)
  • no change
• v5.0.4 (08/01/2006)
  • no change
• v5.0.3 (07/07/2006)
  • no change
• v5.0.1 (04/21/2006)
  • no change
• v5.0.0 (03/10/2006)
  • NEW: MIMB (XML based) Service Oriented Architecture (SOA) for add-on (or OEM built-in) metadata import/export menu integration.
• v4.3.0 (10/21/2005)
• v4.2.1 (6/30/2005)
• added new "Configuration" type of Product
• v4.2.0 beta (4/15/2005)
• extended MIR metamodel with support of ETL, Reporting, Expression, and improved OLAP and Data modeling
• v4.0.0 (10/24/2003)
• Metamodel extensions for support of OLAP, BI and ETL concept.
• v3.1.1 (05/30/2003)
• No change
• v3.1.0 (04/30/2003)
• C++ SDK: Class MIROption: removed definition of MIROptionInfo as this class is for internal use only
• v3.1.0 Beta (04/22/2003)
• C++ SDK: added support for internationalization of messages
• C++ SDK: added methods in Class MIROption for internationalization
• C++ SDK: improved implementation of MIRDate comparison methods
• C++ SDK: added a Class MBBridgeDlls for easier integration in partner's tools
• v3.0.10 (02/24/2003)
• No change
• v3.0.9 (01/13/2003)
• C++ SDK: Updated for OEM integration.
• v3.0.7 (11/22/2002)
• C++ SDK: validation of MIRForeignKey: Relaxed the validation rules, Improved the error messages
• C++ SDK: validation of MIRTypeValue: an empty value is now valid if linked to a MIRPropertyType, to represent empty UDP enumerated value
• C++ SDK: fixed errors in the MIRDate comparison operators.
• v3.0.4 (09/06/2002)
• C++ SDK: added a function retrieveMIMBLicenseKey() for better OEM integration.
• v3.0.3 (07/12/2002)
• Java SDK: added a method getUUID() to MIRObject, because hashCode() is not enough to uniquely identify a MIRObject in a container
• C++ SDK: changed the interface of the methods used to load/save objects into the repository.
• v3.0.1 (05/17/2002)
• C++ and Java SDK: links from SQLViewAssociation to a source SQLviewEntity were created incorrectly
• MIRStd C++ API: added a method resize() on MIRVector. Added a method stringCompareNoCase() on MIRString.
• v3.0.0 (04/29/2002)
• C++ SDK: Fixed the validation of PresentationElement, ForeignKey and TypeValue objects.
• v3.0.0 Beta3 (03/22/2002)
• New method: getParent() on the C++ SDK objects
• New object: ClassMapMember has a position property and is a generalization of the AttributeMap and KeyMap classes
• New links: a ClassMap object can be linked to source and destination Attribute objects.
• New property: a ClassMap now has an operation property
• The MIRModelObject::PhysicalID is now a string property.
• v3.0.0 Beta2 (02/13/2002)
• Bug fixes in Property objects (PropertyType and PropertyValue) code.
• v3.0.0 Beta1 (10/12/2001)
• Object removed: PhysicalProperty
• New objects: PropertyElementTypeScope, PropertyType and PropertyValue (replaces PhysicalProperty and add support for user-defined properties)
• Added a property to Model: targetDatabase (this information was previously stored in a PhysicalProperty)
• Added a property to Index: generate
• New object: Schema (support for the notion of database schema)
• New links: between SQLViewAssociation and SQLViewEntity and between SQLViewAttribute and SQLViewAttribute (for support of Views defined from other Views).
• v2.5.1 (10/12/2001)
• No change.
• v2.5.0 (07/30/2001)
• No change.
• v2.5.0 Beta (06/29/2001)
• The link between Operation and AttributeMap has been removed
• The following properties have been moved from Element to ModelObject: physicalID, physicalName, status, comment, designLevel and stereotype
• A PhysicalObject was associated to an Element. It is now associated to a ModelObject
• C++ SDK: the validation of the Stored Procedure was sometimes incorrect.
• The schema of the underlying database has been modified to rename some columns because 'position', 'type' and 'password' are reserved keywords in NCR Teradata.
• v2.4.6.3 (04/24/2001)
• No change
• v2.4.6 (04/13/2001)
• Windows: C++ SDK is now compiled with VC++ 6.0
• C++ SDK: the method "setDate(MIRString& newDate)" in the Class MIRDate recognizes now more input string formats
• C++ SDK: fixed some errors when retrieving objects from the database
• v2.4.5 (10/30/2000)
• No change
• v2.4.4 (08/28/2000)
• Updated the validation of the Grouping objects
• Added a property to Grouping: multiplicity
• Added an optional link between SQLViewAttribute and Type
• Added ClassType, a subtype of Type, to represent classes used as Types. Renamed the ClassType enumeration to ClassCategory
• Moved the link between Class and CandidateKey to the level of Key. The links to AssociationRole and Generalization are no longer aggregation links
• Added a property to Attribute: extraConstraint
• Added a property to Index: clustered
• Added two subtypes of Operation: Trigger and StoredProcedure. Moved the sqlTableTrigger attribute to the Trigger class. Renamed the SQLTableTriggerMode to TriggerMode. Added an enumerated type: TriggerType
• Added a property to SQLViewAttribute: expression. Made the link to Attribute optional
• Added a property to Projection: fontStyle.
• v2.4.3 (06/12/2000)
• SDK: Added a position property to Operation
• SDK: Added a userDefined property to Package
• SDK: Added a link between Class and Association to model AssociationClasses
• SDK: The link between Attribute and AssociationRole is now an Aggregation link
• SDK: The link from PresentationElement to ModelElement now goes to ModelObject instead. A role name has been added to avoid a name clash
• SDK: The grouping modelisation has been modified.
• v2.4.2 (03/17/2000)
• C++ SDK: The validation was issuing an incorrect message when an named object had no name.
• v2.4.2 beta (02/25/2000)
• No change
• v2.4.1 beta1 (01/21/2000)
• No change
• v2.4.0 (12/20/99)
• UPDATE: SDK to reflect MIR metamodel modifications:
  • Graphical information
  • XML Grouping information
  • New objects: Repository Object, Model Object, Mapping Object
  • Renamed the Key Map to Key Map link from Primary/Foreign to Parent/Child
• UPDATE: Java SDK validation of Model and Mapping Objects
• Other minor additions to the Java SDK and C++ SDK APIs
• v2.4.0beta (10/29/99)
• UPDATE: SDK to reflect MIR metamodel modifications (Artificial Attribute, Index, Physical Object...)
• v2.3.0 (07/20/99)
• no new features (only minor bug fixes)
• v2.2.0 (06/01/99)
• UPDATE: SDK to reflect MIR metamodel modifications
• v2.1.1 (04/09/99)
• UPDATE: MIRComputedAttributeMap has been renamed MIRAttributeMap
• v2.1.0 (04/01/99)
• UPDATE: SDK to reflect MIR metamodel modifications
• UPDATE: changed the Documentation location.
• v2.0.0 (01/04/99)
• UPDATE: SDK to support new datatypes

3. Installation

3.1. C++ SDK requirements

The compressed Meta Integration SDK download is approximately 4 MB on Windows and 5 MB on Linux. After decompression and installation, Meta Integration SDK uses approximately 16 MB of hard disk space.

The minimum system requirements for using the Meta Integration C++ SDK on Windows are as follows:

• Windows 2000, XP, or 2003 Server
• Visual C++ 6.0 or higher

The minimum system requirements for using the Meta Integration C++ SDK on Linux are as follows:

• Unix/Linux x86
• gcc

3.2. Java SDK requirements

The minimum compiler requirements for the Java SDK are as follows:

• A Java™ 2 SDK, standard edition v 1.3
• The MIRSDK has been tested and works with both IBM's and Sun's implementations.

4. Documentation

The MIR metadata design schemas and the documentation of the Java SDK are provided in Meta Integration SDK installation directory.

The MIR metadata design schemas are in the Documentation/MetadataRepositorySDK/Metamodel subdirectory.

The Java SDK documentation is in the Documentation/MetadataRepositorySDK/JavaDoc subdirectory.

The C++ SDK include files are self explanatory.

5. How to access the Java SDK

5.1. On Windows 2000, XP, or 2003 Server

Setup your Java Development Environment to access the jar file:

• C:\Program Files\MetaIntegration\java\MIW.jar (within CLASSPATH)

C:\Program Files\MetaIntegration is the default installation directory, if you have chosen a different directory replace it with the pathname you chose.

5.2. On Unix / Linux x86

Setup your Java Development Environment to access the jar files:

• /opt/MetaIntegration/java/MIW.jar (within CLASSPATH)

/opt/MetaIntegration is the default installation directory, if you have chosen a different directory replace it with the pathname you chose.

6. How to access the C++ SDK

6.1 On Windows 2000, XP, or 2003 Server

Setup your C++ Development Environment to access the directories:

• C:\Program Files\MetaIntegration\include
• C:\Program Files\MetaIntegration\win32 (within PATH)

C:\Program Files\MetaIntegration is the default installation directory, if you have chosen a different directory replace it with the pathname you chose.

6.2. On Unix / Linux x86

Setup your C++ Development Environment to access the directories:

• /opt/MetaIntegration/include
• /opt/MetaIntegration/lib (within LD_LIBRARY_PATH)

/opt/MetaIntegration is the default installation directory, if you have chosen a different directory replace it with the pathname you chose.

7. Frequently Asked Questions

1. On Windows, 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 installtion 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 MIR version that you use, your platform and your database.

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