Bridge Requirements
This bridge:is only supported on Microsoft Windows.
Bridge Specifications
| Vendor | SAP |
| Tool Name | PowerDesigner PDM (Physical Data Modeling) |
| Tool Version | 8.0 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), Graphical Layout via PDM XML File |
SPECIFICATIONS
Tool: SAP / PowerDesigner PDM (Physical Data Modeling) version 8.0 to 16.x via PDM XML File
See https://www.sap.com/products/powerdesigner-data-modeling-tools.html
Metadata: [Data Modeling] Data Store (Physical Data Model), Graphical Layout
Component: SybasePowerDesignerPdm version 11.2.0
OVERVIEW
This bridge generates a PowerDesigner .PDM (physical data model) file with tables, columns, data types, relationships and their implementation (e.g. PK/FK) as well as the graphical layout (diagrams).
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
Q: All the symbols are in the center of the screen?
A: In the tool, select 'Symbol->Auto-Layout', it will redraw the current diagram. Note that you will have to do this for each diagram.
Q: Some symbols seem to be missing?
A: In the tool, select 'Tools->Complete Links', it will draw the missing symbols. Note that you will have to do this for each diagram.
LIMITATIONS
When importing from a multi model source technology (e.g. a database server with multiple databases or schemas), only one model (e.g. schema) is exported. Therefore, limit the import scope to a single model (e.g. subset one schema of a database).
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
SUPPORT
Provide a troubleshooting 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Version | The version of Sybase Power Designer (PDM) file to generate. | ENUMERATED |
|
16.5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| File | The path name of the generated PDM file. In order to load the converted model, start PowerDesigner and: 1. Choose 'Open' from the File menu. 2. In the 'List files of type' list box select PowerDesigner Files. 3. Browse to the generated CDM file and select it from the file name list. 4. Click 'Open'. |
FILE | *.pdm | Mandatory | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Target Database | The target database. 'Auto Detect' means that this bridge will try to auto-detect the target database from the source model. A database prefixed with: 'Star (*)' Only available for PowerDesigner 10 or newer. 'Double star (**)' Only available for PowerDesigner 11 or newer. 'Triple star (***)' Only available for PowerDesigner 12 or newer. 'Fourfold star (****)' Only available for PowerDesigner 15 or newer. 'Fivefold star (*****)' Only available for PowerDesigner 16 or newer. 'Sixfold star (******)' Only available for PowerDesigner 16.5 or newer. |
ENUMERATED |
|
Auto Detect | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description | How to export the Description and Comment properties in PowerDesigner: 'Comment & Description' Export the comment property to the PowerDesigner comment field and the description property to the PowerDesigner description field. 'Comment' Export the comment property (or the description property, if any), to the PowerDesigner comment field. 'Notes/Description' Export the comment property (or the description property, if any), to the PowerDesigner description field. |
ENUMERATED |
|
Comment & Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| XML Indentation (pretty printing) | Controls the pretty printing of XML, for the purpose of opening the generated file in a text editor. E.g. 'space characters' Several space characters as indentation. 'tab key' Tab character as indentation. 'empty' No indentation which leads to a more compact file. |
STRING | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Reverse role names | Swap relationship rolenames for each model: 'False' Do not swap rolenames. 'True' Swap rolenames. |
BOOLEAN | False | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Connection | Allows selecting a connection by name, if the source model contains multiple database connections. If the source model contains multiple connections and this parameter value is left empty, the connection with the most objects is selected. |
STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"SAP PowerDesigner PDM 8.x to 16.x" Metamodel SybasePowerDesignerPdm07 |
Mapping Comments |
| Association | Reference | |
| Aggregation | . | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| ExtraConstraint | . | |
| PhysicalName | Code | Diagram Physical Name.Computed from the Name if not set |
| AssociationRole | Reference | |
| ExtraConstraint | Update constraint, Delete constraint | |
| Multiplicity | Cardinality | |
| AssociationRoleNameMap | Attribute/Index | |
| Attribute | Column | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| DesignLevel | . | |
| ExtraConstraint | Business Rule | |
| Optional | Mandatory | |
| PhysicalName | Code | Attribute Physical Name.Computed from the Name if not set |
| Position | The attributes are ordered by position in the PDM file | |
| BaseType | Domain, Attribute Data Type | See DerivedType |
| CandidateKey | Key | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| PhysicalName | Code | Key Physical Name.Computed from the Name if not set |
| UniqueKey | Primary Key | The primary key will be referenced in the <PKey> tag. |
| Class | Table | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| DimensionalRole | Dimensional Type | |
| PhysicalName | Code | Class Physical Name.Computed from the Name if not set |
| ClassDiagram | Physical Diagram | |
| Comment | Comment | |
| Description | Comment | |
| Name | Name | |
| PhysicalName | Code | |
| DatabaseSchema | User | Tables and objects belonging to a User are linked to a schema |
| Comment | Comment | |
| PhysicalName | Code | |
| DerivedType | Domain, Attribute Data Type | |
| Description | Comment | |
| Length | Length | |
| LowerBound | Minimum | |
| PhysicalName | Code | Type Physical Name.Computed from the Name if not set |
| Scale | Precision | |
| UpperBound | Maximum | |
| UserDataType | Data type | See datatype conversion array |
| UserDefined | Only user defined types are mapped to domain. | |
| ForeignKey | Join | |
| Generalization | Reference | |
| Comment | Comment | |
| Description | Comment | |
| PhysicalName | Code | Generalization Physical Name.Computed from the Name if not set |
| GeneralizationRole | Reference | |
| Comment | Comment | |
| Description | Comment | |
| PhysicalName | Code | Generalization Physical Name.Computed from the Name if not set |
| Identity | Identity | Identity column |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| PhysicalName | Code | Index Physical Name.Computed from the Name if not set |
| Position | The index members are ordered by position in the PDM file | |
| SortOrder | Sort | |
| Note | Annotation | |
| Projection | Symbol | Graphical Information |
| BackgroundColor | fill color | |
| FontColor | font color | |
| Height | height | |
| LineColor | line color | |
| Width | width | |
| X | x | |
| Y | y | |
| RelationshipProjection | Symbol | Graphical Information |
| FontColor | font color | |
| LineColor | line color | |
| SQLViewAssociation | View Relationship | |
| SQLViewAttribute | View Column | |
| Expression | SQL Query | The expression is put in the SQL field of the SQLViewEntity. |
| Position | The attributes are ordered by position in the PDM file | |
| SQLViewEntity | View | Views might be inconsistent if objects have been renamed. |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| PhysicalName | Code | View Physical Name.Computed from the Name if not set |
| WhereClause | SQL Query | |
| StoreModel | Model | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| PhysicalName | Code | Model Physical Name.Computed from the Name if not set |
| StoredProcedure | Stored Procedure | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| Semantics | Definition | |
| Trigger | Trigger | Create one trigger for each mode specified. |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| PhysicalName | Code | Trigger Physical Name.Computed from the Name if not set |
| Semantics | Trigger Code | |
| TypeValue | List of Values | All the values are listed in one tag |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| Value | Value |