SAP PowerDesigner LDM 15.x to 16.x - Import - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor SAP
Tool Name PowerDesigner LDM (Logical Data Modeling)
Tool Version 15.x to 16.x
Tool Web Site https://www.sap.com/products/powerdesigner-data-modeling-tools.html
Supported Methodology [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout via LDM XML File
Multi-Model Harvesting
Incremental Harvesting
Data Profiling
Remote Repository Browsing for Model Selection

SPECIFICATIONS
Tool: SAP PowerDesigner LDM (Logical Data Modeling) version 15.x to 16.x via LDM XML File
See https://www.sap.com/products/powerdesigner-data-modeling-tools.html
Metadata: [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout
Bridge: SybasePowerDesignerLdm15 version 11.0.0

OVERVIEW
This bridge imports data models from a PowerDesigner .LDM (logical data model) file with Entities, Attributes, Domains. This bridge also imports all relationships and their implementation (e.g. PK/FK) as well as the graphical layout (diagrams).

REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
Q: How do I handle LDM XML files which contain shortcuts to external entities?
A: LDM XML model files may contain relationships which refer to entities defined as shortcuts, which are references to external entities. Unfortunately, in this case the LDM XML file does not contain sufficient information to reconstruct the PK/FK relationships properly. If this is the case with the imported file, there will be a message in the log like:
This model may have shortcut dependencies on external model: 'file:///...' and, by default, the bridge will not attempt to reconstruct those PK/FK relationships to shortcuts.

However, the source tool has the capability to merge these files together so that the shortcuts are resolved. To do so:

- Refer to the log for all the files with shortcuts
- Open the tool and go to the Tools > Merge Models
- Create a new merged model
- Save the new model as a LDM XML and import

Q: I see warnings or errors in the log, How can I validate the model before importing?
A: PowerDesigner allows checking of the model for modeling inconsistencies.
Please use menu Tools > Check Model and take necessary corrective actions to resolve detected issues.

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

LDM files in binary format are not supported.

SUPPORT
Provide a trouble shooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Imports LDM XML files. If you do not have the model saved as a LDM XML file already:

1. Logical Data Model is opened in Sybase PowerDesigner.
2. Choose 'Save As' from the 'File' menu.
3. In the 'Save as type' list, select 'Logical Data Model (XML) (*.LDM)'.
4. Enter the file name and select a directory to save the file in.
5. Click 'Save'.

The bridge will use the generated LDM XML file as input.
FILE *.ldm   Mandatory
Apply binary characters filter Specifies if invalid binary characters should be filtered out of the file as a pre-process before parsing the LDM XML file. This option is a workaround for a bug in the PowerDesigner tool which sometimes generates a file that does not conform with the XML specification (contains binary characters).

Warning: Applying this filter may remove some unicode national characters.
BOOLEAN   True  
Import UDPs A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects that the property applies to may have an explicit value for this property. They may instead have no value assigned at all in which case the default value of the property definition (implicit value) applies.

Control how property definitions and values are imported:

'As metadata'
Import the explicit value as the property value. Implicit values are not imported. The default value is kept on the property type only.

'As metadata, migrate default values'
Import the explicit or implicit values as property value.

'In description, migrate default values'
Append the property name and value, even if implicit, to the object's description property. This allows you to export the UDP values to another tool which does not support the notion of UDP.

'Both, migrate default values'
Import the UDP value, even if implicit, both as metadata and in the object's description.
ENUMERATED
As metadata
As metadata, migrate default values
In description, migrate default values
Both, migrate default values
As metadata  
Append volumetric information to the description field Import and append the volumetric (number of occurrences) information to the description property. BOOLEAN   False  
Remove text formatting PowerDesigner stores annotations as plain text or Rich Text Formatting (RTF). Remove Rich Text Formatting (RTF) from annotations:

'False'
Target tool is capable of displaying RTF text.

'True'
Target tool is not capable of displaying RTF text.
BOOLEAN   True  
Reverse role names Swap relationship rolenames for each model:

'False'
Do not swap rolenames.

'True'
Swap rolenames.
BOOLEAN   False  

 

Bridge Mapping

Mapping information is not available