Convert Oracle Designer to PowerDesigner Data (CDM) / Logical Data (LDM) / Physical Data (PDM)

Current version: 6.05

Important to know

The TOOLBUS Interface for Oracle Designer and PowerDesigner enables the migration of Entity – Relat ionship Models from Oracle Designer to Conceptual Data Models ( CDM ) or Logical Data Models (LDM) in Sybase PowerDesigner, and of Server Models from Oracle Designer to Physical Data Models ( PDM ) in PowerDesigner, and vice versa. T he migration of Process Mod els and Function Hierarchy Diagrams from Oracle Designer to BPMN 2.0 Diagrams and Process Hierarchy Diagrams in Business Pr ocess Models (BPM) is also supported. Conceptual Data Models : Entities, Relationships, Attributes, Identifiers, Domains and Value Set s are bi – directionally converted with their properties and textual descriptions. Logical Data Models : Entities, Relationships, Attributes, Identifiers, Domains and Value Sets are converted from Oracle Designer to PowerDesigner with their properties and te xtual descriptions (unidirectional interface), and Foreign Key Attributes are generated. Physical Data Models : Tables, Columns, Foreign Keys, Indexes, Databases, Tablespaces, etc. are bi – directionally converted with their properties and textual description s. The associations between Physical and Logical Objects (“Version Info” of PowerDesigner) are also convert ed. Process Models and Function Hierarchy Diagram s : Business Functions are converted with their properties and textual descriptions, and the sequence flows and sub – process hierarch ies are also migrated. Diagrams: Entity – Relationship, Server Model, Process Model and Function Hierarchy Diagrams are migrated from Oracle Designer to PowerDesigner with the includ ed objects (Entities, Tables, Relationships, Business Functions, Process Steps, Decision Points, Flows ). The PowerDesigner diagrams a re arranged in a standard layout, as reading the position of the symbols on the diagrams is not supported by the API functions of Oracle Designer. The layout of the ge nerated diagram s can be enhanced by the Auto – L ayout functions or PowerDesigner. External References: References to objects (Entities, Tables, Domains, etc.) contained in other Application Systems can be mapped to Shortcuts or Replicated Objects in PowerDes igner. User Defined Properties: The TOOLBUS interface offers 3 options for the migration of User Defined Properties (UDPs) from Oracle Designer to PowerDesigner: 1. UDPs can be stored in Annotation text (: ) in PowerDesigner. 2. Extended Model Defin itions (.xem files) can be generated automatically for the UDPs defined for Entity – Relationship Models and Server Models in Oracle Designer. 3. Existing Extended Model Definitions (.xem files) can be used.

Conversion Process

Migration Process: In order to migrate Entity – Relat ionship and Server Model from Oracle Designer to PowerDesigner, the TOOLBUS interface exports Application Systems from Oracle Designer into an internal TOOLBUS file, using the Oracle Designer API (Application Programmatic Interface). From the TOOLBUS file CDM, LDM and PDM files are generated for PowerDesigner. In order t o migrate Conceptu al and Physical Data Models from PowerDesigner to Entity – Relationship and Server Models for Oracle Designer, the TOOLBUS interface parses the PowerDesigner CDM (XML) and PD M (XML) file s, and it generate s an intermediate TOOLBUS file. The n t he TOOLBUS interface loads a new Application System, or updates the latest version of an existing Application System in Oracle Designer by the functions provided by the API of Oracle Desig ner, using the TOOLBUS file as input.

Platform

Platform: The TOOLBUS Interface for Oracle Designer and PowerDesigner requires Windows XP /Vista /7, and i t supports Oracle Designer 6.0 to 10g, and Sybase PowerDesigner 1 2.5 to 16. 5 SP03.

Request an offer