Bridge Specifications

Vendor	IBM
Tool Name	InfoSphere Information Server (IIS) Workbench
Tool Version	9.1
Tool Web Site	http://www.ibm.com/software/data/integration/info_server/
Supported Methodology	[Metadata Management] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model), ETL (Source and Target Data Stores, Transformation Lineage), OLAP/ROLAP/MOLAP via Eclipse Java API on XML and CSV File

SPECIFICATIONS
Tool: IBM / InfoSphere Information Server (IIS) Workbench version 9.1 via Eclipse Java API on XML and CSV File
See http://www.ibm.com/software/data/integration/info_server/
Metadata: [Metadata Management] Multi-Model, Metadata Repository, Data Store (Record Model, Xml Schemas, Object Model UML Class Diagrams, Physical Data Model), ETL (Source and Target Data Stores, Transformation Lineage), OLAP/ROLAP/MOLAP
Component: IbmImwMaps version 11.2.0

OVERVIEW
This export bridge generates mapping summaries from various complex Data Integration (ETL/ELT) jobs or SQL scripts into the IBM InfoSphere Information Server (IIS).

REQUIREMENTS
Prior to importing a mapping into IIS, the involved source and target data stores must already exist. In order to achieve that goal, the export bridge generates a MappingDataStoreDefinitions.xml file that specifies all the source and target data stores involved in this mapping. This file must be customized (see instructions below) to fully specify new data stores to be created, or reconnect to existing data stores already in the IIS Repository. Subsequent execution of the export bridge will detect the existence of a customized MappingDataStoreDefinitions.xml and regenerate a new MetadataWorkBench-MappingExtensions.csv with proper references to the specified data stores, as well as a new MetadataAssetManager-InformationServerCommonModel-DataStores.xml for the new data stores to be created or updated.

After the above customization process, the mapping can be imported into IIS using the following steps:

1- Use IBM InfoSphere Metadata Asset Manager to import the generated MetadataAssetManager-InformationServerCommonModel-DataStores.xml file into IIS in order to create the new data stores in IIS that are needed either as source or target of the mapping.

2- Use IBM InfoSphere Metadata Workbench to import the generated MetadataWorkBench-MappingExtensions-VendorNameToolName.csv file into IIS in order to create the new mapping in IIS with the proper connections to the existing data stores.

CUSTOMIZING MappingDataStoreDefinitions.xml

In order to better understand/recognize what each data store is, a "usage" flag indicates if that data store is involved as source or target of that mapping.

Both "usage" and "id" are system generated, and must not be changed/customized.

Each data store is generated within its own host by default, the first customization step is to fully define the actual hosts, and group (cut & paste) the data stores within each host.

If a data store is already fully defined in the IIS repository, then its "generate" flag should be set to 'False' in order to remove that data store from the MetadataAssetManager-InformationServerCommonModel-DataStores.xml file, and therefore prevent any update/change to that data store when importing that file with the Asset Manager.

Here is an example of the format:

<MappingHosts>
<Host name="Unknown Host for SourceDir">
<DataStore id="DataStore1" name="SourceDir" storeType="File" usage="Source" generate="True"/>
</Host>
<Host name="Unknown Host for Data Warehouse">
<DataStore id="DataStore2" name="Data Warehouse" schema="dbo" storeType="Relational" usage="Target" generate="True"/>
</Host>
<Host name="Unknown Host for TargetDir">
<DataStore id="DataStore3" name="TargetDir" storeType="File" usage="Source" generate="True"/>
</Host>
<Host name="Unknown Host for Stage DB">
<DataStore id="DataStore4" name="Stage DB" schema="admin" storeType="Relational" usage="Source, Target" generate="True"/>
</Host>
</MappingHosts>

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:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).

Bridge Parameters

Bridge Mapping

Mapping information is not available