Prerequisites and parameter information for the SAS Data Integration Studio (via CWM XMI) bridge.
The SAS Data Integration Studio (via CWM XMI) bridge imports implemented data resources and business intelligence models in XML files that are created by SAS Data Integration Studio, Version 9. The XML files must be compliant with the Object Management Group (OMG) Common Warehouse Metamodel (CWM) XML Metadata Interchange (XMI) file format.
Contact the vendor to obtain the exact version of the supported CWM metamodel and XMI format. More details on the valid combinations of metamodels and XMI formats are available at http://www.omg.org.
To use the latest version of this bridge, you must install the prerequisite software: http://www.ibm.com/support/docview.wss?uid=swg27038230.
You must export an XML file from SAS Data Integration Studio that is compliant with the OMG CWM XMI file format.
Transfer the file to the metadata interchange server or the local computer that you are importing the metadata from.
The SAS Data Integration Studio (via CWM XMI) bridge uses the following import configuration parameters.
Required. Browse to select an XML file that is produced by your source tool and is compliant with the OMG CWM XMI file format.
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.
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.
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.
The bridge ignores this option regardless of which selection you make. InfoSphere® Information Server does not support importing native IDs.
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.
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.