The MDM Workbench export wizard is used to export metadata for virtual and physical MDM models, or a physical MDM extension model.
Choosing to export an MDM model creates a single .xmi file that contains information about virtual members, attributes, entities, as well as physical objects, transactions, and tables that are used for operational integration with InfoSphere® Information Server.
For virtual MDM, the project definitions (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. Virtual MDM export results are captured in a single .xmi file.
On the physical MDM side, the export can be used to create data files from tailored or untailored services projects, and to export business glossary information. After the physical MDM definitions are imported to InfoSphere Information Server, you can use InfoSphere Metadata Asset Manager to manage the imported assets and share the data with other InfoSphere Information Server applications.
You can also opt to 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.
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 to understand business language and the business meaning of information assets like databases, jobs, database tables and columns, information governance policies and rules, and reports.
Use the Master Data Management bridge in InfoSphere Metadata Asset Manager to import the files into InfoSphere Information Server.
Choosing to export an MDM extension model creates two .csv files that contain information about database mappings, service, and object definitions of a physical MDM project. These definitions are used for documentation in InfoSphere Information Server version 9.1. The data files can then be used by the InfoSphere Metadata Workbench to graphically represent how each InfoSphere MDM service is mapped to physical MDM database schemas, tables, and fields. Lineage analysis provides information about which services in InfoSphere MDM use which data structures and tables, and which other services use those same data structures and tables.