IBM DB2 Cube Views bridge reference

About this bridge

The bridge imports metadata from IBM DB2 Cube Views, Version 8. The imported metadata includes business intelligence (BI) models and related implemented data resources such as database schemas and tables.

Prerequisites

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

Import parameters

You specify values for the following parameters during imports.

File location

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

File

Required. Specify the name and path of an XML import file that was exported from IBM DB2 OLAP Center.

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.

Dimensional model object names mapping

Accept the default mapping to import both the name and the business name of OLAP objects.

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.