POWERDESGINER 16.5 SP2
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

POWERDESGINER 16.5 SP2

  • 2,721 views
Uploaded on

You can do reverse-enginering and create PDM for your existing SAP Implementation including HANA models. Great

You can do reverse-enginering and create PDM for your existing SAP Implementation including HANA models. Great

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,721
On Slideshare
2,721
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
65
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SAP Sybase PowerDesigner 16.5 Support Pack 2 Overview SAP Sybase PowerDesigner V16.5 SP02 Overview David Dichmann, Product Manager, SAP HANA NA Product Management.
  • 2. © 2012 SAP AG. All rights reserved. 2 Agenda PowerDesigner Overview  Quick Product Overview Upgrading to SP02  General Upgrading Considerations  Upgrading from 32-bit to 64-bit  Post-upgrade Considerations Supporting SAP Business Suite Data Models  Business Suite Data Modeling Overview  Importing from SAP Business Suite  Generating an SAP HANA Data Model Other Enhancements  Additional Enhancements Delivered with PowerDesigner V16.5 SP02 Q&A
  • 3. © 2012 SAP AG. All rights reserved. 3 PowerDesigner Overview
  • 4. © 2012 SAP AG. All rights reserved. 4 Capture Design Communicate Define current environment Document Existing Systems Describe the interaction Model business & technical artifacts with related metadata SAP Sybase PowerDesigner Overview: Product Definition Design & plan for future “As-is” and “to-be” modeling Streamline implementation Generate Change Integrate all aspects Tie business & technical viewpoints across the enterprise Realize impact of change Graphical, bi-directional understanding from architecture to execution Collaborate Central repository to communicate, report and share
  • 5. © 2012 SAP AG. All rights reserved. 5 SAP Sybase PowerDesigner Overview: HANA Studio Integration SAP Sybase PowerDesigner SAP HANA Studio Designtime,Open,Heterogeneous End-to-endDevelopmentStudio From Business Architecture to Technology Implementation
  • 6. © 2012 SAP AG. All rights reserved. 6 SAP Sybase PowerDesigner Overview: Information Steward Integration Designtime,createnewenvironment Operationaltime,applytogivenlandscape SAP Sybase PowerDesigner SAP Information Steward From Discovery, Quality and Monitoring to Architecture Driven Change
  • 7. © 2012 SAP AG. All rights reserved. 7 Upgrading to SP02 General Upgrade Requirements, and Migrating from 32-bit to 64-bit Clients
  • 8. © 2012 SAP AG. All rights reserved. 8 Upgrading PowerDesigner – General Considerations Repository Branching Change Impact  Prior to v16.1, the repository browser only supported displaying a single branch at a time. When you upgrade an existing repository to v16.1 or higher, all branches will become, by default, visible for all users.  You may wish to simplify viewing the repository by:  Deleting documents and branches that are no longer used  Using permissions to hide certain branches from specific users or groups  Migrating active models to a new repository  As part of the branch simplification, you should remove the unnecessary branches prior to upgrading from 16.0 and earlier Office add-ins Version Limitation  Though PowerDesigner v15.x and v16.x can be installed together on the same workstation, after the installation of v16.x, the add-ins supporting importing from MS Word and Visio will only function for v16.x.
  • 9. © 2012 SAP AG. All rights reserved. 9 Upgrading PowerDesigner – General Considerations Resource Files – Handling Modified and New Shared Resources  DBMS, language definitions and other resource files provided are constantly evolving. If you have not edited the resource files delivered with a previous version of PowerDesigner, then the upgrade to the latest version will be automatic  If you have previously edited a definition file or other resource file  It will continue to work after the upgrade  Use the Compare tool on the resource file list to review the differences between your file and the new file  Merge modified and new resources files to obtain bug fixes or new features  If you have stored standard resource files from a previous version in the repository then they will not automatically be updated.  Check in the newly-delivered versions manually
  • 10. © 2012 SAP AG. All rights reserved. 10 Upgrading when using the Repository Proxy The PowerDesigner repository proxy  An optional program that runs as a service on or near the repository server  Translates SQL requests from client workstations into a more efficient proprietary format  The proxy can considerably improve performance If clients will be connecting over a WAN or complicated LAN environment When dealing regularly with larger (15MB+) models  The proxy simplifies the client connection to the repository Users do not need to know details of the database hosting the repository The repository proxy is available in 32-bit and 64-bit versions, and both versions can support connections from 32-bit and 64-bit clients If you upgrade a 32-bit proxy installation to 64-bit, then you must upgrade its ODBC or other connections to the repository from 32-bit to 64-bit as well
  • 11. © 2012 SAP AG. All rights reserved. 11 Upgrading from 32-Bit to 64-Bit PowerDesigner Requirements to Upgrade:  Upgrade your ODBC and other connections to the repository and databases from 32-bit to 64-bit versions  If the 32-bit client is already installed, the setup will uninstall the 32-bit client  If the upgrade is performed by an administrator who is not the PowerDesigner user, the user may need to manually modify PowerDesigner resource file paths (to files such as DBMS and language definition files, user profiles and model extensions)  Other defaults and preferences will be correctly copied to the new installation. Repository Considerations  A single repository can support connections from 32-bit and 64-bit PowerDesigner clients  The repository proxy is available in 32-bit and 64-bit versions  Both proxy versions can support connections from 32-bit and 64-bit PowerDesigner clients
  • 12. © 2012 SAP AG. All rights reserved. 12 Performing the Upgrade from 32-bit to 64-bit 1. Open the 32-bit PowerDesigner client and select Repository > Repository Definitions to review your repository connections.  If you connect to the repository using a:  Proxy connection – No action is needed and you will be able to connect immediately after upgrading to 64-bit.  Direct connection – You will need to modify the connection, after the upgrade, to use 64-bit ODBC or other compatible connectivity 2. If you use PowerDesigner to connect databases, you will need to modify their connections to 64-bit ODBC or other connectivity:  Open a PDM and select Database > Configure Connections  Review the connections on the ODBC Machine Data Sources, ODBC File Sources, and Connection Profiles tabs  Note those that you will want to recreate for 64-bit.
  • 13. © 2012 SAP AG. All rights reserved. 13 Performing the Upgrade from 32-bit to 64-bit 3. Exit all instances of any running 32-bit PowerDesigner client on the selected workstation 4. Start PowerDesigner 64-bit client setup & follow the setup instructions  The installer will install the 64-bit client and remove the 32-bit client. 5. Open the 64-client and re-create or modify database connections  Update the data source of the repository definitions with 64-bit client, ODBC  Update other database connections to use 64-bit ODBC or other compatible connectivity
  • 14. © 2012 SAP AG. All rights reserved. 14 Performing the Upgrade from 32-bit to 64-bit 6. Correct any paths to resource files  If an administrator has performed the upgrade on your behalf, and resource files are not stored in the repository:  Installer will not have been able to modify the paths to resource files  The 64-bit client is installed in a different default location  To make the default resource files visible: 1. Open the resource file list. For example, to open the list of DBMSs, select Tools > Resources > DBMS. 2. Click the Path tool and then click the Add a Directory tool, navigate to the resource file location (for example, C:Program FilesSybasePowerDesigner xResource FilesDBMS) and click OK to add it to the path list. 3. Click OK to return to the resource file list. The standard resource files will now be present. 4. Repeat these steps for each type of resource file.
  • 15. © 2012 SAP AG. All rights reserved. 15 Resource File Storage Changes for V16.5 and Beyond To comply with recent Microsoft recommendations  You may no longer save modifications to resource files in “Program Files”  PowerDesigner will recommend an alternative location if you try  PowerDesigner adds the selected directory to the list of paths If you have previously created or modified resource files inside Program Files  Your files may no longer be available  Windows Vista or Windows 7 actually store them in a virtual mirror  To restore these files to your lists  Move them to a visible path, & add their location to your list using the Path tool Please read the README.html file for more information on virtualization for Program Files under Windows Vista and Windows 7
  • 16. © 2012 SAP AG. All rights reserved. 16 SAP Business Suite Reverse Engineer Data Structures from SAP Business Suite Generate SAP HANA Data Structures
  • 17. © 2012 SAP AG. All rights reserved. 17 SAP Business Suite To create a PDM with support for features specific to the SAP Business Suite  Create a New Model with the New Model dialog  Select the DBMS on which your ERP installation is running & click OK  Supported RDMBS families are IBM/DB2/CS, MSSQL, Oracle & Sybase ASE  Select Tools > SAP Business Suite > Import SAP Business Suite Data Dictionary Note: An extension is added to the Physical Data Model after the import, defining ERP specific capabilities.  To view these extensions to the PowerDesigner metamodel in the Resource Editor (after running an import)  Select Model > Extensions  Select the SAP Business Suite extension & click the Properties tool  Expand the Profile node
  • 18. © 2012 SAP AG. All rights reserved. 18 SAP Business Suite – Extended Metadata The “Data Dictionary” Tab  Appears on Many Objects  Can be used in filters, sorts, reports, etc.  Configures SAP-Specific Details  Should not be Altered before generating an SAP HANA Database
  • 19. © 2012 SAP AG. All rights reserved. 19 Importing an SAP Business Suite Data Dictionary SAP Business Suite has a complex database structure with thousand tables and a large numbers of extensions PowerDesigner allows you to  Browse the application component and packages in the hierarchy  Import them and their supporting logical objects  Perform analysis, comparison, & merging of data dictionaries
  • 20. © 2012 SAP AG. All rights reserved. 20 Importing an SAP Business Suite Data Dictionary To Import a SAP Business Suite Data Dictionary: 1. Create a new PDM targeting the DBMS hosting your Business Suite server  For a server running SAP MaxDB, use the SAP HANA DBMS. 2. Select Tools > SAP Business Suite > Import SAP Business Suite Data Dictionary 3. Click Next on the Welcome page. 4. Enter your Business Suite connection parameters & click Next 5. Use the tools to the right of the Connection name field: 1. Create a new connection profile, review the properties of the existing profile, or delete it  Business Suite connection profiles are stored in the registry. 6. Select application components and packages in the left pane 7. Add their tables and views to the import & click Next.
  • 21. © 2012 SAP AG. All rights reserved. 21 Importing an SAP Business Suite Data Dictionary Select a component or package to import  Supporting tables & views are in subtabs in right pane  Total number of tables and views is updated  Tables are selected for import by default, views are not  Select or deselect tables & views for import ERP systems can contain thousands of tables. You should import only a limited subset of components or packages at a time. You can re-launch the wizard as many times as desired
  • 22. © 2012 SAP AG. All rights reserved. 22 Importing an SAP Business Suite Data Dictionary 8. Review the objects that will be imported and then click Finish.  Technical name into Code field  Intuitive short description as the name  For example, the table SCMATRANSACT in the data dictionary is displayed as “Schedule Manager: Registered SAP Transactions”  Each component & package contains a diagram showing objects it contains: Not all packages contain tables.  To view the structure of only those components and packages with diagrams that do contain tables, right-click the model in the Browser or a diagram background and select View ABAP Diagrams Containing Tables . Select a diagram in the tree and click OK to open it.
  • 23. © 2012 SAP AG. All rights reserved. 23 Importing an SAP Business Suite Data Dictionary 9. Review the imported metadata  Configurable and filterable lists of each type of object are available from the Model menu.  For example, display the List of Data Elements, select Model > Data Elements: To view lists of global objects  Double-clicking the Top-Level Component Diagram to be sure you have the right context To view all the components, packages, or tables in the model  Ensure that you are at root  Open the list  Click the Include Sub-Packages tool in the list toolbar
  • 24. © 2012 SAP AG. All rights reserved. 24 Optional Steps to Complete Import Process 10. Perform a new import to enrich your model.  You can perform as many imports as necessary, and delete components, packages, or other objects as appropriate, to simplify your model and focus on the areas that interest you. 11. Compare two or more Business Suite installations  Import each one into its own PDM, and select Tools > Compare Models. 12. Merge Multiple Business Suite PDMs and generation HANA  Provide the basis for establishing a business intelligence environment for reporting on your Business Suite transactional data
  • 25. © 2012 SAP AG. All rights reserved. 25 Generating SAP Business Suite Data Dictionary to HANA PowerDesigner can help you prepare a HANA table structure to allow consolidated reporting on one or more SAP Business Suite installations
  • 26. © 2012 SAP AG. All rights reserved. 26 Generating SAP Business Suite Data Dictionary to HANA 1. Create a PDM for each SAP Business Suite installation 2. Import the logical tables needed for your warehouse reporting 3. Analyze and purify your models  Delete components, packages, tables, columns not of interest  To ensure integrity of the HANA Schema:  Do not edit the properties of Business Suite objects  You MAY edit the Comment field & Notes tab  Do not create new objects, in order to ensure the integrity of the metadata that will be generated to the HANA schema. 4. Select a model to act as the core warehouse 5. Select Tools > Merge Models and merge all models into it one  This creates a superset of all the components, packages, tables, & columns to generate to HANA
  • 27. © 2012 SAP AG. All rights reserved. 27 Generating SAP Business Suite Data Dictionary to HANA 6. Select Tools > SAP Business Suite > Generate HANA Physical Data Model.  PowerDesigner generates a new PDM targeting the HANA DBMS  PowerDesigner generates the Business Suite component and package structure to the HANA PDM  This structure does not represent HANA packages, and your tables will all be exported to the HANA catalog 7. Export your tables to your HANA server 8. Implement loading of your transactional data to your HANA warehouse using your standard ETL solution
  • 28. © 2012 SAP AG. All rights reserved. 28 Other Enhancements General Enhancements to SAP Sybase PowerDesigner delivered in V16.5SP02
  • 29. © 2012 SAP AG. All rights reserved. 29 Porting a Repository from One DBMS to Another  Retaining all your repository folder and branch structure and version histories 1.Create a new repository 2.Use the Import Repository command  Copies an existing repository into the new one  Deletes any existing repository data in the destination database The repository to be imported must have been updated to the latest version before beginning the import. To update a repository, connect to it with an administrator account and follow the instructions. Porting the Repository to a Different DBMS
  • 30. © 2012 SAP AG. All rights reserved. 30 1. Create a database on new the DBMS server & Create a repository definition for it Warning! If the target repository database does not use the same character encoding as the repository database to be imported, then the import may fail if it encounters long strings that would need to be truncated to fit into the reserved size in the new database. 2. Select Repository > Connect 3. Install the repository tables 4. Select Repository > Administration > Import Repository 5. Confirm that you want to proceed. 6. Select the repository data source to import 7. Enter database user & password 8. Connect to begin the import. • PowerDesigner copies tables to the new repository, which may take considerable time. A progress bar indicates data copied. The Browser Repository tab will not update during the import • PowerDesigner disconnects when the import completes Porting the Repository Database to a New Server
  • 31. © 2012 SAP AG. All rights reserved. 31 Other Features Show shortcuts (general option)  Allows you to enable or disable the shortcuts display in the Browser Apply profiles (repository general option)  Automatically reapplies UI preference and general preference profiles  User will refresh profile at their next repository connection  Helps to ensure modeling user experience consistency (enforce standards) Compare models that target different DBMS or language definitions  Example  Compare a PDM targeting Oracle with a PDM targeting SAP® Sybase® ASE Duplicate Code in Glossary Terms  Allows multiple terms to have the same code  Useful for when Code is used for standard abbreviations of business terms  Often two terms can have the same abbreviation  Customer or Customs = CUS
  • 32. © 2012 SAP AG. All rights reserved. 32 SAP HANA Enhancements Generate and Reverse Engineering of SAP HANA® v1.0 SP05 and SP06  Now support table partitioning The following extensions are available on the Partitions tab:  Type: Specifies the partition scheme type:  Hash - Distributes rows to partitions equally for load balancing and to extend data sets beyond 2 billion rows. An expression lists the columns to partition and the number of partitions to create. You may specify a second scheme of type Hash or Range.  Range - Partition for specific values or value ranges. Specify an expression and range.  RoundRobin - Distributes rows to partitions equally without specifying partitioning columns. Specify the number of partitions to create. You may specify a second scheme of type Range.
  • 33. © 2012 SAP AG. All rights reserved. 33 SAP Solution Manager Enhancements Importing & exporting SAP® Solution Manager v7.1 SP07 and SP08  Import and edit scenario flow diagrams  Importing additional logical components from system landscapes  Improved documentation handling  Allow import of document types & statuses  Allow creation of new “URL type” project documentation
  • 34. © 2012 SAP AG. All rights reserved. 34 Solution Manager Scenario Flow Diagramming A scenario may include a scenario flow diagram  Shows the processes in the scenario as swimming pools  Has message flows between steps in different processes To prepare your scenario flow diagram: 1.Import a scenario flow diagram for the scenario from the server 2.Right-click the scenario and select Show Scenario Flow Diagram 3.Drag and drop processes from the Browser to model message exchanges 4.Right-click the scenario and select Update Scenario Flow Diagram Layout  Shows steps and other sub-objects in process symbols. 5.Using the Flow tool, draw messages between process steps
  • 35. © 2012 SAP AG. All rights reserved. 35 Solution Manager: Document Types & Statuses PowerDesigner will import:  Document Types  Provide standard types to categorize documents.  Document Statuses  You must configure the advanced configuration parameters  Provide standard status names to categorize documents.  If the parameters are not set or no statuses are defined, default “Copy Editing, In Processing, Released, and Review” statuses will be used URL project documentation type  Click the Create an Object tool on the Project Documentation tab  Supported in scenario, process, or process steps  To add existing documentation to an object, use the Add Objects tool. You cannot create general documentation or documentation types and statuses, but you can associate existing instances of these objects with your scenarios, processes, and process steps.
  • 36. © 2012 SAP AG. All rights reserved. 36 Add Large Object dimension details  By default (deselected), excludes blob columns when generating the universe business layer  When used, specifies that dimension attributes are created for columns of type blob (which commonly contain images, audio, or other binary data)  If this option is deselected, these columns will still appear in the data foundation, but will not be visible in the business layer. Note: you must have SAP® BusinessObjects™ SBOP BI Platform Clients 4.0 SP04 Patch 3 (v14.0.4.819) or higher installed on your workstation. On Windows Vista or Windows 7 machines, if PowerDesigner fails to recognize a valid BusinessObjects installation, it may be necessary launch the Universe Design tool once with administrator privileges to enable the BusinessObjects SDK. SAP BusinessObjects Enhancements
  • 37. © 2012 SAP AG. All rights reserved. 37 New or Enhanced DBMS Support The following DBMS vendor/versions have been added or Improved:  SAP HANA® v1.0 SP6 (see New SAP Platform Features v16.5 SP02)  SAP® Sybase® IQ v16  IBM DB2 UDB v10  Teradata v14
  • 38. © 2012 SAP AG. All rights reserved. 38 Dimensional Modeling: New Modify Cubes Wizard A new wizard helps you update existing cubes to reflect changes  Changes made to operational tables  Add or remove dimensions, measures, or attributes. Modifying Cubes: 1. Select the cube fact in the multidimensional diagram to update 2. Select Tools > Modify Cube to start the wizard 3. Select operational tables from which to build dimensions around the facts & click Next  By default, PowerDesigner selects only tables that have previously been selected as dimensions 4. Select fact table columns as measures or attributes for the facts & click Next  By default, PowerDesigner uses previous choices  You can drag and drop columns between the Candidates, Measures, & Attributes trees 5. Review the objects that will be generated & click Finish to begin the generation  The wizard updates your multidimensional diagram to reflect your new choices.
  • 39. © 2012 SAP AG. All rights reserved. 39 Technical Architecture Modeling (TAM) The SAP Technical Architecture Model (TAM)  Technical Architecture Modeling is an SAP standard for architecture modeling and combines elements of FMC and UML.  PowerDesigner now supports TAM, including block diagrams
  • 40. © 2012 SAP AG. All rights reserved. 40 Q&A
  • 41. © 2012 SAP AG. All rights reserved. 41 SAP Sybase PowerDesigner On-Line Documentation SAP Sybase PowerDesigner Online Documentation (User Guides) • Business Process Modeling > Process Language Definition Reference > SAP Solution Manager Further Reading & Exploration SAP D&T Academy YouTube Channel for PowerDesigner http://www.youtube.com/results?search_query=PowerDesigner+D%26T Or: www.youtube.com and search “PowerDesigner D&T”