The Design Studio incorporates the Meta Integration Model Bridge (MIMB) feature, also known as the MITI Bridge. This bridge transforms proprietary physical data models, such as ERwin, Rational Rose®, and Sybase models, to the native SQL model format that is used in the DB2® Warehouse Design Studio. By importing and transforming an existing model, you avoid the need to re-create the model natively in the Design Studio. You can use the transformed model transparently as a metadata source for your data flows and mining flows.
For general information about this feature, go to: http://www.metaintegration.net/Products/MIMB/
For example, assume that your database design team routinely uses ERwin to do physical data modeling. A new data mart or star schema has been physically designed in ERwin by someone in the team, and the SQW developer wants to use that model to design some data flows. The model designer does not want to re-create the model in the Design Studio "SQL model" format, and the data flow developer does not have access to the actual database. (Maybe the actual database has not been created yet, or the ERwin model contains changes that have not been deployed to the database yet.) In this type of scenario, the solution is to import the ERwin model, transform it to the SQL model format that the Design Studio uses, and let the SQW developer work from that. The .dbm file that results from a successful MITI Bridge transform is visible as metadata when the flow designer creates table sources, table targets, and other operators.
Procedure
To import a physical data model:To export a physical data model that exists in a data warehousing project or data design project, use the .