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

MIMB Bridge Documentation

MIMB Export Bridge to IBM InfoSphere Information Governance Catalog (IGC) - Vendor Internal Bridge

Bridge Specifications

Vendor IBM
Tool Name InfoSphere Information Governance Catalog (IGC)
Tool Version 11.x
Tool Web Site http://www.ibm.com/software/products/en/infosphere-information-governance-catalog
Supported Methodology [Metadata Management] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model, Logical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), OLAP/ROLAP/MOLAP, BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage), BI Report (Relational Source, Dimensional Source, Report Structure) via Eclipse Java API on XML File

SPECIFICATIONS
Tool: IBM / InfoSphere Information Governance Catalog (IGC) version 11.x via Eclipse Java API on XML File
See http://www.ibm.com/software/products/en/infosphere-information-governance-catalog
Metadata: [Metadata Management] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model, Logical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), OLAP/ROLAP/MOLAP, BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage), BI Report (Relational Source, Dimensional Source, Report Structure)
Component: IbmWisCm9XmlExport.IbmIgc version 11.2.0

OVERVIEW
Generates XML file for IBM InfoSphere Information Server from the source metadata.

REQUIREMENTS
Requires the path to the IBM InfoSphere Information Server installation directory or the /ASBNode/lib/java directory where the IBM JAR files reside.

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
IBM InfoSphere Information Server version Specify version of IBM InfoSphere Information Server ENUMERATED
11.3
11.5
113  
File Output file name. FILE *.xml   Mandatory
IBM InfoSphere Information Server installation directory The full path to the IBM InfoSphere Information Server installation directory or the /ASBNode/lib/java directory where the IBM JAR files reside. If the installation directory is specified, it should contain the /ASBNode/lib/java directory with JAR files that the bridge depends on. DIRECTORY     Mandatory
Import joins Select this option to import joins from Business Intelligence (BI) tools. When the option is selected, joins that are defined in the BI model are imported. By default, joins are not imported. BOOLEAN
False
True
False  
Import levels Select this option to import levels and hierarchies from Business Intelligence (BI) tools. When the option is selected, levels and hierarchies that are defined in the BI model are imported. By default, they are not imported. BOOLEAN
False
True
False  
Qualify table names Select this option to add the owner name to the table name, in the form owner_name.table_name. The owner name is added only for those tables where an owner name has been specified in the source file. BOOLEAN
False
True
False  
Model namespace Overwrites LogicalModel and/or PhysicalModel namespace in the repository if not empty. STRING      
Host system name Type the name of the computer that hosts the actual database that the design is for. This value is important for reconciling the identity of the object in the repository. The name that you enter is used if it cannot be determined from the import. STRING   Unknown  
Database name Type the name of the actual database that the design is for. This value is important for reconciling the identity of the object in the repository. STRING   Unknown  
Replace incorrect or missing database name If you specify a value for the 'Database name' parameter, choose one of the following options:
'Use database name to override bridge value'
Replaces any value returned by the bridge with the database name that you specify.
'Use database name if bridge value is empty'
Uses the database name that you specify only if the bridge has returned no value for 'Database name'.

'Use database name to override bridge value'
If selected and the import includes more than one database, the database name that you specify is used only to replace empty values.

'Use database name to override bridge value'
If selected but you specify no value for 'Database name', the bridge value is not changed.
ENUMERATED
Use database name to override bridge value
Use database name if bridge value is empty
Override  
Schema name Type the name of the actual database schema that the design is for. This value is important for reconciling the identity of the object in the repository. STRING   Unknown  
Replace incorrect or missing schema name If you specify a value for the 'Schema name' parameter, choose one of the following options:
'Use schema name to override bridge value'
Replaces any value returned by the bridge with the schema name that you specify.

'Use schema name if bridge value is empty'
Uses the schema name that you specify only if the bridge has returned no value for 'Schema name'.

'Use schema name to override bridge value'
If selected and the import includes more than one schema, the schema name that you specify is used only to replace empty values.

'Use schema name to override bridge value'
If selected but you specify no value for 'Schema name', the bridge value is not changed.
ENUMERATED
Use schema name to override bridge value
Use schema name if bridge value is empty
Override  
DBMS name Select the name of the DBMS (database management system) that hosts the actual database that the design is for. If you select 'Other', type the name of the DBMS in the 'Other DBMS name' field. STRING      
Replace incorrect or missing DBMS name If you specify a value for the 'DBMS name' parameter, choose one of the following options:
'Use DBMS name to override bridge value'
Replaces any value returned by the bridge with the DBMS name that you specify.

'Use DBMS name if bridge value is empty'.
Uses the DBMS name that you specify only if the bridge has returned no value for 'DBMS name'.

'Use DBMS name to override bridge value'
If selected and the import includes more than one DBMS, the DBMS name that you specify is used only to replace empty values.

'Use DBMS name to override bridge value'
If selected, but you specify no value for 'DBMS name', the bridge value will not change.
ENUMERATED
Use DBMS name to override bridge value
Use DBMS name if bridge value is empty
Override  
DBMS server instance name If applicable, type the name of the DBMS server instance that hosts the actual database that the design is for. STRING      
Connections When importing metadata that connects to databases (and files) you can use this parameter to reconcile these connections with the actual database that the design is for.

You can instruct the bridge to resolve connections against databases and files directly by specifying their details, like database and DBMS names in the following format:

"Connection_name"="Database Name"."DBMS Name" When you specify multiple connections separate them with "," comma, e.g.
"c1"="sample db"."DB2","c2"="localhost"."ORACLE"

When you leave the parameter empty (default) the bridge creates Data Connections that you can reconcile manually by going to Lineage Administration/Data Connection Mappings.

You can request the bridge to output all available connections in the log by specifying the "?" value.
STRING      
Skip duplicate expressions Select this option to skip duplicate objects, based on having identical expressions. BOOLEAN
False
True
True  
Miscellaneous
-pbi.folder <folder name>

Override the folder name for single model, e.g.
-pbi.folder "NewName"

STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Wed, 9 Jul 2025 17:42:13

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