Putting MDM metadata into InfoSphere Information Server

The MDM Workbench Export wizard is used to collect metadata (definitions) from virtual and physical MDM projects. The resulting data files can then be imported into and used by InfoSphere® Information Server applications. You can choose to export an MDM model for either virtual or physical MDM or to export an extension model for physical MDM depending upon the version of InfoSphere Information Server that you are using.

The following illustration shows the file types that are created by each export type and the InfoSphere Information Server applications that support that file type.

Hover and click the icons to learn more, or replay the animation.

Image shows the flow of metadata export and the IIS applications that use the MDM metadata. The Export wizard in MDM Workbench is used to package your MDM project metadata, which must then be imported into InfoSphere Information Server. If you are using InfoSphere Information Server version 11.3 or later, an MDM model export results in a single .xmi file. For virtual MDM, the file contains information about members, attributes, and entities. For physical MDM, it contains objects, transactions, and tables. You can also export both virtual and physical MDM models if you have both project types configured in MDM Workbench. A dual export also results in a single .xmi file. Virtual MDM metadata is used by InfoSphere DataStage to create the base model and project configuration for jobs that use the MDM Connector stage. InfoSphere DataStage is the ETL tool that is used for virtual MDM implementations. You can configure DataStage jobs that use the MDM Connector stage. This stage provides integrated MDM APIs that search, read, and write member data. Physical MDM exports are used to create data files from tailored or untailored services projects, and to export business glossary information. After the definitions are imported to InfoSphere Information Server, use InfoSphere Metadata Asset Manager to manage the assets and share the data with other InfoSphere Information Server applications. You can also opt to export and XML file. If you are using InfoSphere Information Server version 9.1, you can export a physical MDM extension model. This choice results in two .csv files that contain information about database mappings, service, and object definitions of a physical MDM project. Virtual MDM and physical MDM project metadata is stored in a single .xmi file. Use the InfoSphere Master Data Management bridge in Metadata Asset Manager to import the model into InfoSphere Information Server. The .xml file for a physical MDM model is used specifically to view physical MDM business glossary information. If you are using InfoSphere Information Server version 9.1, you can import the model into InfoSphere Business Glossary. For InfoSphere Information Server 11.4, you use the model in InfoSphere Information Governance Catalog. The extension model export generates two comma-separated value (.csv) files in the format expected by InfoSphere Information Server. InfoSphere Metadata Workbench is used to import the extension. InfoSphere Metadata Asset Manager is used to import metadata from design tools, business intelligence tools, databases, and files into the metadata repository of InfoSphere Information Server. Use the InfoSphere Master Data Management bridge in Metadata Asset Manager to import the model into InfoSphere Information Server. InfoSphere DataStage is a data integration tool for designing, developing, and running jobs that move and transform data. IBM InfoSphere Information Governance Catalog is an interactive, web-based tool used to create, manage, and share an enterprise vocabulary and classification system in a central catalog. This tool is available with InfoSphere Information Server version 11.3 or later. IBM InfoSphere Business Glossary is an interactive, web-based tool used to create, manage, and share an enterprise vocabulary and classification system. Business Glossary is available with InfoSphere Information Server version 9.1. Import your MDM tailored service project into InfoSphere Metadata Workbench and use the files to graphically represent how each MDM service is mapped to physical MDM database schemas, tables, and fields. Learn more about InfoSphere Information Server 11.3 Learn more about InfoSphere Information Server 9.1

Last updated: 23 October 2014