Prerequisites, frequently asked questions, and parameter information for the Sybase PowerDesigner LDM bridge.
The Sybase PowerDesigner LDM bridge imports logical data models in LDM XML files that are created by Sybase PowerDesigner versions 15 and 16. LDM files in binary format are not supported.
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 create an LDM file to import. Transfer the import file to the local computer or the metadata interchange server that you are using for the import.
To create an LDM file for import, open a logical data model in Sybase PowerDesigner and save it as Logical Data Model (xml) (*.ldm).
The Sybase PowerDesigner LDM bridge uses the following import configuration parameters.
Required. Specify the LDM file to import.
Specify whether to filter invalid binary characters from the file before the LDM XML file is parsed.
This option is a workaround for a bug in PowerDesigner, which sometimes generates a file with binary characters that does not conform to the XML specification.
The filter might remove some Unicode national characters. If the filter removes Unicode national characters, remove the check mark from the selection.
The default behavior is to remove invalid binary characters.
A UDP (user-defined property) is usually defined with a property definition object that has a default value. The objects that the property applies to might also specify an explicit value or no value at all for this property, in which case the default value of the property definition applies.
InfoSphere® Information Server supports importing UDPs only by appending the property name and value to the description property of the object. To append the property name and value, even if implicit, to the description property of an object, select In description, migrate default values. If you select any other value for this parameter, the UDP information is not imported.
Select whether to import volumetric information (the number of occurrences) and append it to the description property. By default, the volumetric information is not imported.
Select this option. InfoSphere Information Server does not support the display of RTF text in descriptions.
Select this option if you want the bridge to swap (reverse) the role names for each relationship in the model. By default, the role names are not reversed.
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.