IBM DB2 Warehouse Manager (via CWM XMI) bridge reference

About this bridge

The IBM DB2 Warehouse Manager (via CWM XMI) bridge imports implemented data resources and business intelligence models in XML files that are created by IBM DB2 Warehouse Manager, Version 7.2 to 8. The XML files must be compliant with the Object Management Group (OMG) Common Warehouse Metamodel (CWM) XML Metadata Interchange (XMI) file format.

Prerequisites

To use the latest version of the bridge, you must install the prerequisite software.

You must create an XML file that is compliant with the OMG CWM XMI file format.

Import parameters

The IBM DB2 Warehouse Manager (via CWM XMI) bridge uses the following import configuration parameters.

File location

Select whether the file that you specify for the File parameter is on the metadata interchange server or on the local computer.

File

Required. Browse to select an XML file that is produced by your source tool and is compliant with the OMG CWM XMI file format.

Source tool

Select the tool or method that was used to generate the model that you want to import, or select Auto-detect if the tool is not listed.

Options

• Auto-detect. The bridge automatically detects which tool generated the file.
• IBM DB2 Warehouse Manager. The file was generated by IBM DB2 Warehouse Manager.
• OMG CWM. The file conforms to the OMG CWM standard document type definitions (DTDs).
• Oracle Warehouse Builder. The file was generated by Oracle Warehouse Builder.
• SAS ETL Studio. The file was generated by SAS ETLStudio.

Auto-correct

CWM files that are produced by some source tools might contain a slightly incomplete or incorrect model. By default, the bridge attempts to fix the model, which might require deleting some model elements. The bridge logs warnings about the changes.

If you remove the check mark from Auto-correct, the bridge does not modify the model. If the model is invalid, the import fails.

Top package

Type the name of the special package that stores objects that are not explicitly associated to a package. The default is Logical view.

The repository metamodel requires that all model elements (for example, classes, or associations) belong to a package. Whenever an object is not explicitly associated to a package it is stored in a special package. If there is a single top-level package by that name in the model, the bridge marks the package as optional. Packages that are marked as optional do not appear in the destination model if the destination tool does not require all objects to be in a package.

Import UUIDs

The bridge ignores this option regardless of which selection you make. InfoSphere® Information Server does not support importing native IDs.

Table design level

Specify whether you want the bridge to create logical entities from the physical tables.

If you select Logical and physical, logical entities and a logical data model are created and imported with the physical tables that implement them. If you accept the default Physical, no logical entities are created.

If you are importing from IBM DB2 Warehouse Manager, accept the default value of Physical, because no logical entities are created regardless of which choice you select.

Dimensional model reverse engineering

Accept the default setting, Disabled.

Import joins

You can import joins that are defined in the BI model. By default, joins are not imported.

Import levels

You can import levels and hierarchies. When the option is selected, levels and hierarchies that are defined in the BI model are imported. By default, levels and hierarchies are not imported.

Metadata consistency check

Perform a consistency check on the selected metadata before it is imported into the metadata repository. It is possible to save metadata in source tools in ways that cause problems when the assets are imported into the metadata repository or used in other tools. For example, a foreign key might have no connection to a primary key or to an alternate key. In some cases, the metadata might be so semantically inconsistent that the bridge cannot import it.

The metadata consistency check returns warnings and errors in the log file.

Basic check

The default. Performs the minimum consistency checks necessary to validate the metadata, including checking for missing relationships and foreign keys that are not connected to primary or alternate keys.

In some cases, the basic check might be more rigorous than necessary and you can ignore certain errors or warnings.

Detailed check

Performs the basic check plus more advanced semantic checks specific to the type of metadata that is imported. This level can be used when the source tool does not have the ability to validate the metadata.

No check

Use with extreme caution. Selecting this option could result in the import of duplicates or invalid identities and might cause serious problems with your use of suite tools and the metadata repository.

If an asset description already exists

Specify what action to take if an imported asset matches an existing asset in the metadata repository. You can keep the existing description, or overwrite the existing description with the description of the imported asset.

If either description is null, the non-null description is used, regardless of which option you specify. The default behavior is to replace the existing description.