10 Integrating Metadata Using the Transfer Wizard

There are several utilities for sharing and/or integrating metadata with other tools and systems. This section discusses how to create collections that store definitions for a group of Warehouse Builder objects. It also discusses importing metadata stored in Object Management Group (OMG) Common Warehouse Model (CWM) formats, using the Transfer Wizard.

This section contains these topics:

Using the Transfer Wizard

The Transfer Wizard enables you to synchronize, integrate, and use metadata stored in OMG CWM formats. Use the Transfer Wizard to import selected metadata from OMG CWM compliant applications version 1.0 into the workspace. You can also import metadata that is stored in a proprietary format by integrating with MIMB (Meta Integration Model Bridges). For more information about the formats that MIMB can translate, see "Integrating with the Meta Integration Model Bridges (MIMB)".

The Transfer Wizard can be used only in single-user mode. This means that no other users can be connected to the workspace into which you are importing OMG CWM metadata. Before you use the Transfer Wizard to import OMG CWM metadata into a workspace, ensure that you are the only user connected to that workspace.

Integrating with the Meta Integration Model Bridges (MIMB)

Warehouse Builder enables you to integrate with Meta Integration Model Bridges (MIMB) that translate metadata from a proprietary metadata file or workspace to the standard CWM format. You can then import this metadata using the Oracle Warehouse Builder Transfer Wizard. After integrating with MIMB, you can also import metadata from CA ERwin, Sybase PowerDesigner, and many other sources through these bridges.

MIMB integration enables you to import metadata from the following sources:

  • OMG CWM 1.0: Database Schema using JDBC 1.0/2.0

  • OMG CWM 1.0: Meta Integration Repository 3.0

  • OMG CWM 1.0: Meta Integration Works 3.0

  • OMG CWM 1.0: XML DTD 1.0 (W3C)

  • OMG CWM 1.0: XML DTD for HL7 3.0

  • Acta Works 5.x

  • Adaptive Repository

  • ArgoUML

  • Business Objects Crystal Reports

  • Business Objects Data Integrator

  • Business Objects Designer


  • CA ERwin

  • CA ParadigmPlus

  • Cognos Impromptu 7.1

  • Cognos ReportNet Framework Manager

  • Hyperion Application Builder

  • IBM DB2

  • IBM Rational Rose

  • Informatica PowerCenter

  • Merant AppMaster Designer 4.0

  • Microsoft SQL Server

  • Microsoft Visio

  • Microsoft Visual Studio

  • MicroStrategy

  • NCR Teradata

  • Oracle Designer

  • Popkin System Architect

  • ProActivity 3.x & 4.0

  • SAS ETL Studio

  • Select SE 7.0

  • Silverrun RDM

  • Sybase Power Designer

  • Unisys Rose

  • Visible IE Advantage 6.1

  • Various XML/XMI versions


The list of sources is not exhaustive and does not include the product versions. For a list of all the supported sources, see the MIMB documentation at http://www.metaintegration.net.

Follow these steps to integrate with MIMB.

Download the Meta Integration Model Bridge

After you download the MIMB on your system, the installation is automatically recognized and the new import options are displayed on the Metadata Source and Target Identification Page of the Transfer Wizard.

To download MIMB:

  1. Download the Model Bridge (personal) product from the following Web site: http://www.metaintegration.net/.

  2. Install the MIMB by running the setup on your system.

  3. During installation, select Typical with Java Extensions as the installation type from the Setup Type page.

    If the set up program is not able to find a JDK on your computer, you must provide the JNI library directory path name. Your path environment variable must contain the metaintegration directory. If not, you need to add it to the path: c:\program files\metaintegration\win32.

  4. Enable MIMB by starting the Transfer Wizard from the Design Center. For more information about importing metadata using this wizard, see "Importing Metadata".

Importing Metadata

The Transfer Wizard enables you to import OMG CWM metadata. Perform the following steps to import metadata:

  1. Run the Transfer Wizard.

    The Transfer Wizard converts the OMG CWM compliant metadata and stores it in an MDL file. For more information about using the Transfer Wizard, see "Running the Transfer Wizard".

  2. Import the MDL file created in Step 1 using the Metadata Loader Import Utility.

    For more information importing the MDL file, see "Importing the MDL File".

Running the Transfer Wizard

From the Design menu of the Design Center, select Import, and then Bridges. Warehouse Builder displays the Welcome page of the Transfer Wizard. This page lists the steps you perform while using the Transfer Wizard. If you want to display version information about the wizard, click About Oracle OWB Transfer Tool. For version information about the individual bridges, press the Bridge Versions button from the About Oracle OWB Transfer Tool dialog box. Click Next to proceed.

Provide details on the following pages of the Transfer Wizard:

Metadata Source and Target Identification Page

Use this page to specify the format of the source data.

The From field automatically identifies your metadata source as OMG CWM 1.0. You can import metadata from many other sources if you choose to integrate with the Meta Integration Model Bridge (MIMB). When you integrate with MIMB, the From field displays a list of other sources from which you can import metadata. For details, see "Integrating with the Meta Integration Model Bridges (MIMB)".

The To field contains the value OWB mdl and you cannot edit this value. The Oracle Warehouse Builder Transfer Wizard converts the source metadata into an .mdl file that can processed by the Metadata Loader Utility.

Use the Description field to enter an optional description of the metadata to be transferred. This description displays in the progress bar during the transfer process.

Transfer Parameter Identification Page

This page lists the parameters used during the transfer process. Table 10-1 describes the transfer parameters used by the Transfer Wizard.

Table 10-1 Transfer Parameters for OMG CWM File Import

Transfer Parameter Name Description

OMG CWM Input File

Specify the file containing the OMG CWM model you want to import. Click the Ellipsis button to browse for the file location.

OWB Project

Specify the name of the project into which the OMG CWM model will be imported.

Warehouse Builder MDL

Specify the name of the .mdl file that will store the converted source metadata.

Default Module Type

Select the type of module into which you want to import the metadata. The options are Source warehouse module and Target warehouse module. The Transfer Wizard will create the correct module and import the metadata into it.

When you select the Source warehouse module option, the names are case-sensitive. When you select Target warehouse module, all the object names are converted to uppercase.

Process OLAP Physical Representation

If you are importing metadata from a star schema, then you can select True if you want to maintain its physical representation or False to only import its logical definitions.

If you are importing a snowflake schema, its physical implementation is lost and only the logical definitions are imported.

Log Level

Log level to be assigned to the transfer: Errors, Information, and Trace.

Errors: lists the errors, if any, generated during the transfer.

Information: lists the transfer details about the metadata objects, including any errors.

Trace: produces a trace for debugging purposes, which also includes the errors and information log details. If you need assistance with the trace, contact Oracle World Wide Support. Trace type provides the most detailed log information.

When you integrate with MIMB, the Transfer Parameter Identification page displays additional parameters. The parameters displayed depend on the source you select in the From field of the Metadata Source and Target Identification page. The descriptions of these parameters display in the box at the bottom of the wizard page.

Summary Page

The Summary page displays the values that you selected for each field. Review your entries. If any entries are incorrect, click Back to return to the previous screen and make the necessary changes. Click Finish to transfer the metadata. The Oracle WB Transfer dialog box is displayed. For details about this dialog box, see "Oracle WB Transfer Dialog Box".

Oracle WB Transfer Dialog Box

This dialog box indicates the progress of the metadata transfer. The description you provide on the Metadata Source and Target Identification Page is appended to the title of the transfer window. For example, if you entered the description as My Metadata Transfer, the title of this dialog box will be Oracle WB Transfer - My Metadata Transfer. If you did not provide a description, a title does not display.

The transfer can require several minutes or an hour or more to complete, depending on the amount of metadata you transfer.

Do one of the following:

  • If the transfer completes successfully (100% displays), click OK. The Transfer Wizard displays a reminder informing you that you must import the .mdl file into the workspace.

  • If a transfer failure message displays, click View Log File and review the log. (You can also view the log of a successful transfer.)

    To save the log for reference, click Save As to open the Save dialog box. Select the folder where you want to store the log and click Save.

  • If you determine the cause of the failure from the Information Log, note the information requiring update. Close the log by clicking OK. On the Oracle WB Transfer dialog box, click Return to Wizard and update the incorrect information about the Transfer Parameter Identification Page. Then transfer the data again.

  • If you cannot determine the cause of the failure from the Information Log, you can create a Trace log. Close the current log by clicking OK. On the Oracle WB Transfer dialog box, click Return to Wizard and change the Log Level to Trace on the Transfer Parameter Identification Page. Then transfer the data again.

If the transfer is successful, the Transfer Wizard creates an .mdl file and stores it in the location you specified in the Warehouse Builder MDL parameter on the Transfer Parameter Identification Page. The version of the MDL file created by the Transfer Wizard is

Importing the MDL File

After the Transfer Wizard converts the source metadata and stores it in an .mdl file, you must import this .mdl file into the workspace. The Metadata Import Utility enables you to import an MDL file.

See Also:

""Importing and Exporting Using the Metadata Loader (MDL)" in the Oracle Warehouse Builder Installation and Administration Guide.

Use the following steps:

  1. From the Design menu, select Import, and then Warehouse Builder Metadata.

    The Metadata Import dialog box is displayed.

  2. In the File Name field, specify the name of the .mdl file created using the Oracle Warehouse Builder Transfer Wizard. You can also use the Browse button to select the .mdl file.

  3. Click Import.

    The Metadata Upgrade dialog box is displayed. The File Name field contains the name of the .mdl file that stores the upgraded metadata.

  4. Click Upgrade.

    The Metadata Import Progress dialog box is displayed. The text above the progress bar displays the status of the import.

    To display a detailed log of the import process, click Show Details. The Message Log panel displays the details. Click Show Statistics for information about the number and type of objects imported.

  5. Click Close.

Transfer Considerations

Before you transfer metadata into the workspace, you need to perform tasks within the source and target tools to ensure that the metadata can be transferred successfully.

This section lists the objects that are extracted from the source tool during the transfer and their corresponding objects.

Importing Metadata from an OMG CWM-Standard System

OMG stands for Object Management Group. An OMG CWM-standard system may have more than one implementation of a cube. In such cases, the Transfer Wizard imports the first implementation of the cube. The log file of the import contains the details of the version of the cube implementation that is imported.

Table 10-2 lists the object conversion from an OMG CWM file system into the workspace.

Table 10-2 Object Conversion from OMG CWM to OWB Workspace

Object in OMG CWM Object Imported to Warehouse Builder










Level Attributes






Cube Measure





Foreign Key

Foreign Key

Unique Constraint/Primary Key

Unique Key





Table 10-3 lists the data type conversion from an OMG CWM system to a workspace.

Table 10-3 Data Type Conversion from OMG CWM to OWB Workspace

Data type in OMG CWM Data type Imported to Warehouse Builder