IA363 PowerDesigner Advanced Tips and Techniques

1. IA363PowerDesigner Advanced Tips and Techniques Jay Stevens Design Tools Support Manager Internet Application Division stevensj@sybase.com

2. PowerDesigner - Advanced Tips and Tricks • Topics • Migrating from PD 6 to PD 7 • Submodels vs Diagrams and Packages • Understanding the merge screen • Database Definition Editor • Miscellaneous Tips

3. Migrating from PD6 to PD7 • Migration Topics • General conversion of models • CDM / PDM synchronization • Triggers • Extended Attributes • DEF file modifications • Customized Reports • Metaworks

4. Migrating from PD6 to PD7 • General conversion of model • Step 1 - migrate current models to PD 6.1.5 • Free maintenance release for PD 6.1.x users • Step 2 - backup all your files, just in case • Step 3 - open PD 6 models in latest PD 7 release • Step 4 - Save • Once saved as PD 7 models you cannot go back to PD 6 (that is why we made a backup) • PD 7 does have a save as PD 6 function, but this is there for compatibility with ProcessAnalyst and WarehouseArchitect, not all information is saved.

5. Migrating from PD6 to PD7 • CDM / PDM synchronization • If you had synchronized CDM / PDM pairs in PD 6, that synchronization is now broken. • From PD 7 CDM, generate a new PDM • Select new PDM and select Tools > Merge Model • Select your migrated PDM as the source model • Select all merge actions including delete actions which are not selected by default

6. Migrating from PD6 to PD7 • CDM / PDM synchronization

7. Migrating from PD6 to PD7 • Triggers • PD 6 Triggers were a generation option • PD 7 Triggers are objects • Allows us to select RI implementation by reference instead of the model • Pd 7 Converts user-defined triggers • Modified trigger templates in PD 6 are not converted

8. Migrating from PD6 to PD7 • Extended Attributes • PD 6 extended attributes are not converted

9. Migrating from PD6 to PD7 • DEF file modifications • PD 6 DEF file modification are not converted • Will discuss in Database Definition Editor section

10. Migrating from PD6 to PD7 • Customized Reports • PD 6 Custom reports are not converted • Must be reformated manually

11. Migrating from PD6 to PD7 • Metaworks migration • Due to the totally new design • Object ID has totally changed • Extract all models from PD 6 Metaworks • Consolidate into PD 7.5 Metaworks after CDM / PDM synchronization process

12. Submodels vs Diagrams and Packages • PD6 Submodels • Architecture originally designed for alternate model graphics • Fudged to handle subject areas and object selection • Could never be done properly because submodels were only a collection of graphic symbols • Many objects did not have a graphic symbol • Object selection was simulated by filtering based on associations to graphic objects in a submodel • Could never properly deal with object ownership

13. Submodels vs Diagrams and Packages • PD7 re-architected • Diagrams to handle the need for alternate graphic displays • Representation of high level vs detail views • Sub-division of large subject area to ease graphical modeling • Packages to handle the need for subject areas and object ownership • Shortcuts added to reference objects in other packages or models

14. Submodels vs Diagrams and Packages • Migrating - Submodels to Diagrams/Packages • First need to decide why you used submodels • By default 6 to 7 migration moves submodels to diagrams • PD would need to make too many guesses to move submodels to packages • Most effective way is to move them manually using the diagram to package wizard • Make sure you do the steps to synchronize the CDM and PDM prior to moving diagrams to packages

15. Submodels vs Diagrams and Packages • Migrating - Submodels to Diagrams/Packages • Convert Diagram to Package wizard • Easy way to move objects from a diagram to a package - including graphics • Alternative is manually by object and this will lose some graphics

16. Submodels vs Diagrams and Packages • Migrating - Submodels to Diagrams/Packages • For a few models, a direct conversion from submodels to packages is possible • Models with very few common objects between submodels • This function can be invoked by creating the following registry entry • [HKEY_CURRENT_USER\Software\Sybase\PowerDesigner 7\ModelOptions\Tool] • "ConvertOnImport"="1” • Try this option at your own risk!

17. Submodels vs Diagrams and Packages • Migrating - Submodels to Diagrams/Packages • Assumptions must be made when using this method • Object only in Main - Object created in main • Object only in submodel - Object created in resulting package • Object in multiple submodels - Object created in main, shortcuts in packages • Object in main and only one submodel - Object created in resulting package and shortcut created in main diagram

18. Understanding the merge screen • Merge screen is used for everything • Generation into an existing model • with preserve - will suggest actions based on modifications • without preserve - delete and recreate, use same name, no merge screen is displayed • Synchronize to database • Modify database • Metaworks consolidation and conflict resolution

19. Understanding the merge screen • Merge Screen • Object Comparison portion - matching model trees • Source model on left side • Target model on right side • All actions selected on Target model side • Actions denoted by icons and colors • See PowerDesigner General Features Guide for details • Property Comparison portion - displays detailed properties of object selected in Object Comparison portion

20. Understanding the merge screen • Conflicts - object has been modified in both the source and target models • Generation with preserve • default actions favor modifications in the target model • Consolidation • default actions depend on latest modification

21. Understanding the merge screen • Moved Objects • Moved Only - Comparison will show two differences • Object moved with action selection • shortcut replacement with no action selectable • Moved and Modified - will show two actions • Modify action in original package • Move action in new package • Both must be checked to synchronize model

22. Understanding the merge screen • Permissions in the repository • Will affect whether actions are enabled • Sometimes changes will be made to objects in unauthorized packages if it is required to maintain model integrity • delete an object where you have permission • shortcuts in unauthorized packages will be deleted also

23. Understanding the merge screen • Manual Synchronization • How • Object renamed or modified external to PowerDesigner • Comparison will display two disconnected objects • Why • Synchronize moved or disconnected objects • De-synchronize objects that share common properties but should not be linked

24. Database Definition Editor • Topics • Tools Overview • Missing databases / importing DEF files • Key areas • DBMS Editor Walk-thru

25. Database Definition Editor • Editor Overview • > Tools > Resources > DBMS • changes for all models • > Database > Edit Current DBMS • Changes depend on Link or Local to Model setting • If link, changes are for all models • If Local, changes are saved in the model

26. Database Definition Editor • Editor Overview • General Tab, heart of the Database definition • Tree of objects in left window • Navigate to desired object • Make changes in area on right • Trigger Template and Trigger Template Items tab used for customizing default triggers for all models

27. Database Definition Editor • Editor Overview • Good news • We almost have full control over database generation and reverse engineering • Bad news • It is not well documented yet, but we are working on it

28. Database Definition Editor • Missing Databases • PD 6 supported 82 target database / versions • We suspect many of these were rarely used • We selected the most popular databases for PD 7 • If one you need is missing • First try to import the PD 6 DEF file • Check results, will vary based on how much PD 6 hardcoded as opposed to used ODBC • Submit a case to Support requesting a database

29. Database Definition Editor • Key areas • General - Identification and major flags • Script - Heart of the DBMS definition • SQL - Major SQL behavior • Objects - Details for each type of object • Datatype - Datatype conversion tables • ODBC - Same structure as Script, used if ODBC requires different commands • Extended Attributes - allows extension of PowerDesigner, sometimes used for special database support

30. Database Definition Editor • DBMS Editor Walk-Thru

31. Miscellaneous Tips • Mouse Roller Support • roll up: scroll to top • roll down: scroll to bottom • shift+roll up: scroll left • shift+roll down: scroll right • ctrl+roll up: zoom-in and center the view to the position of the mouse • ctrl+roll down: zoom-out and center the view to the position of the mouse

32. Miscellaneous Tips • List tips • Customize Columns and Filters button in toolbar - add or remove displayed columns • Multi-select to make same change to many objects • Ctrl-Up - First line in list • Ctrl - Down - Last line in list • Ctrl - Left - First column on row • Ctrl - Right - Last column on row

33. Miscellaneous Tips • Mouseless Property Sheet Navigation • Ctrl - Tab - Next tab page • Ctrl-Shift-Tab - Previous tab page • Ctrl-PgUp - Next sub tab, Notes Description or Annotations, text area must have focus • Ctrl-PgDn - Previous sub tab

34. Miscellaneous Tips • Copy Symbol Format • Applies object formatting information from one object to another(line styles, color, font, …) • Only accessible via format toolbar, or add to some other toolbar • two toolbar pieces • Get Format - Select source object and click • Apply Format - Select Target object and click

35. Miscellaneous Tips • More might be added if I discover them before the presentation

36. Conclusion QUESTIONS ???

37. IA363PowerDesigner Advanced Tips and Techniques Jay Stevens Design Tools Support Manager Internet Application Division stevensj@sybase.com