Test Data Migration Server

  • 2,483 views
Uploaded on

 

More in: Business
  • 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,483
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
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 Test Data MigrationServer (TDMS) 4.0Scrambling &Performance TipsTuran TekçiçekSAP Netweaver Technology Consultant@tekciceklinkedin.com/in/tekcicek
  • 2. SAP approach to ALMSAP aims for ALM to bridge gaps within IT teams Implementation ALM Operations Gain greater value from your software with lower TCO© 2011 SAP AG. All rights reserved. 2
  • 3. Application Lifecycle ManagementITIL Based approach – Single Source of Truth© 2011 SAP AG. All rights reserved. 3
  • 4. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 4
  • 5. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 5
  • 6. Customer Situation and Challenges Are you facing…  Large and quickly growing SAP systems?  The need to test and validate in-house developments?  The challenge to scramble sensitive data?  Multiple parallel IT projects?  Demand to simulate new business scenarios?  Unplanned downtimes due to program errors? Consider implementing a solution that helps you to create lean and consistent development, testing, quality assurance, and training environments based on real business data© 2010 SAP AG. All rights reserved. / Page 6
  • 7. Invest to Reduce Unplanned Downtime Reduce causes of production downtimes through early development testing using real production data!© 2010 SAP AG. All rights reserved. / Page 7
  • 8. Challenges with Full System Copy Challenges Consequences Production systems are becoming larger and  Administration of large data volume larger  Increased storage expenses  Interfaces need to be changed or closed After each copy, settings need to be readjusted  Users need to be set up or changed  Authorizations need to be adjusted  Saved objects need to be copied back ( CATTS) Developments need to be stopped (before  Transports need to be closed, released and system rebuild) reimported New developments can only be tested in Q/A  Objects need to be transported to Q/A system system, tested, corrected in DEV system, and transported again to Q/A, etc. Data in non production system is completely  Repository Objects loose their transport replaced by production data history when copied from production Sensitive data in test systems  Need to implement complex authorization concept© SAP 2009 / Page 8
  • 9. SAP TDMS – Data Selection Options© 2010 SAP AG. All rights reserved. / Page 9
  • 10. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 10
  • 11. The Solution - SAP TDMS With SAP TDMS you can:  Reduce data volume  Simulate production environment  Automate system refreshes  Selectively refresh individual clients  Extract data based on business objects, time slice, or a combination of organizational unit and time slice  Scramble sensitive data SAP Test Data Migration Server is a high-speed data extraction tool that populates your development, test, quality assurance, and training systems with SAP business data from your live productive environment.© 2010 SAP AG. All rights reserved. / Page 11
  • 12. SAP TDMS – Functionality for ERP and HCM Data Extraction Scenarios for ERP  TDMS Shell Creation - Repository and client-indep. data only  TDMS for ERP Classic:  Master and configuration data only  Master and configuration data in addition to time slice of transactional data  Master and configuration data in addition to time slice of transactional data for specific company code(s)  TDMS Business Process Library (BPL) - Predefined business objects and process data Data Extraction Scenarios for HCM  Personnel Administration (PA) data only  Combination of Personnel Administration (PA) and Organizational Management (OM) data  Payroll comparison functionality© 2010 SAP AG. All rights reserved. / Page 12
  • 13. SAP TDMS – Functionality for BW and CRM Data Extraction Scenarios for BW  Shell Creation - Repository and client-independent data only  Master data and time slice of transactional data Data Extraction Scenarios for CRM  Shell Creation - Repository and client-dependent data only  TDMS for CRM Classic:  Master and configuration data only  Master and configuration data in addition to time slice of transactional data© 2010 SAP AG. All rights reserved. / Page 13
  • 14. © 2010 SAP AG. All rights reserved. / Page 14
  • 15. © 2010 SAP AG. All rights reserved. / Page 15
  • 16. SAP TDMS - High-Level Architecture Sender System SAP TDMS Receiver System© 2010 SAP AG. All rights reserved. / Page 16
  • 17. Solution Approach - TDMS Client DB Assumption  80 - 90% of the production data is stored in 10 - 20% of client-dependent tables Data volume reduction 80% Transaction Data *  In order to reduce the overall volume, only few tables need to be reduced  All other tables (master and configuration data) are migrated entirely  Customer-individual tables are transferred entirely or can 10% Master Data * be reduced via e.g. time criteria  Some tables are excluded from transfer by default: 7% Config. Data *  E.g. change documents, user tables, etc. 3 % Admin- Data* (customizable) * Estimate based on project experience© 2010 SAP AG. All rights reserved. / Page 17
  • 18. SAP TDMS for HCM: Architecture – Data Scrambling Control System Production System Test System TDMS Server HR original HR Data scrambled Scrambling Data HR scrambled Data (Cluster) IMPORTANT: 1. Sensitive Data does NOT leave Production 2. TDMS for HCM can scramble data in cluster tables© 2010 SAP AG. All rights reserved. / Page 18
  • 19. SAP TDMS for HCM - Details Scrambling:  ANY HCM data can be scrambled (also data in cluster tables)  Content dependencies are taken into account  Grouping of content absolutely freely possible  Scrambling templates available for 20+ countries Customizing:  Option to customize specific target number range per user  Option to exclude specific employees from transfer  Option to set maximum number of objects per user  Option to exclude objects and info types of a table from transfer  Option to include customer-specific info types/tables© 2010 SAP AG. All rights reserved. / Page 19
  • 20. Scrambling© SAP 2007 / Page 20© SAP 2008 / SAP TechEd 08 / LCM272 Page 20
  • 21. Stand-Alone Scrambling© SAP 2007 / Page 21© SAP 2008 / SAP TechEd 08 / LCM272 Page 21
  • 22. Scrambling Workbench – One UI for All Scrambling Customizing© SAP 2008 / SAP TechEd 08 / LCM272 Page 22
  • 23. Scrambling Workbench – Integration with Project and Package© SAP 2008 / SAP TechEd 08 / LCM272 Page 23
  • 24. Scrambling – Workbench UI Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 24
  • 25. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 25
  • 26. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 26
  • 27. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 27
  • 28. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 28
  • 29. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 29
  • 30. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 30
  • 31. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 31
  • 32. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 32
  • 33. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 33
  • 34. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 34
  • 35. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 35
  • 36. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 36
  • 37. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 37
  • 38. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 38
  • 39. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 39
  • 40. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 40
  • 41. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 41
  • 42. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 42
  • 43. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 43
  • 44. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 44
  • 45. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 45
  • 46. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 46
  • 47. Scrambling – Examples© SAP 2008 / SAP TechEd 08 / LCM272 Page 47
  • 48. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 48
  • 49. SAP TDMS – Value Drivers IMPROVED Improve quality of development and training activities by using QUALITY business-relevant and up-to-date test data INCREASED Increase development efficiency by reducing the administrative efforts EFFICIENCY and time required to manage your development and test systems HIGHER Support independent project schedules by selectively refreshing single FLEXIBILITY clients of your development, test and quality assurance systems DECISION Effectively simulate new business situations in your test environments SUPPORT using up-to-date data before taking critical business decisions REDUCED Reduce your disk space by decreasing the data volume in your INFRASTRUCTURE development, test, quality assurance and training systems EXPENDITURES Reduce testing expenses by outsourcing those activities to low-cost OUTSOURCING countries while keeping sensitive data anonymous thus ensuring legal compliance. confidential
  • 50. SAP TDMS – Reduces the Overall StorageUsage confidential
  • 51. Use Cases – General Typical SAP TDMS Use Cases:  Create separate TDMS client in development environment  Create a slim test system with a reduced set of data for upgrade testing purposes  Business Process Library: quickly populate maintenance systems with small data sets based on business objects  Allow HCM business users to transfer specific employee data and scramble (anonymize) the data before transfer  Create multiple TDMS clients with differing data volumes in DEV as master clients to supply test or training systems recurringly, e.g. for resetting purposes  Create initial master shell and place in transport path to be used as starting point for target system build© 2010 SAP AG. All rights reserved. / Page 51
  • 52. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 52
  • 53. Reasons for Performance Problems Utilization of the capacity of the database – Sender (DIA) Utilization of the capacity of the server (CPU, memory) – Central (BTC) Program error – Repeat Data volume – Data sets Lock situation - RFCs Intense I/O - SELECT Every BTC process in receiver system needs an active DIA process in central system© 2010 SAP AG. All rights reserved. / Page 53
  • 54. SAP TDMS – Sizing Facts and Figures  System Recommendations  SAP WebAS 6.20, 6.40 or 7.00  Minimum 4000 SAPS, 20 GB hard drive  Additional ApplicationServers  Note 916763 – “TDMS performance composite SAP note”  Note 890797 - "TDMS - Required and recommended system settings“  Note 893522 - "TDMS corrections (composite SAP note)"  Most recent version of the programs  Transaction – DTLMON  Throughput – 1,5 GB/Hour  Supported Releases  ERP: 4.6C, 4.7, 5.0, 6.0  BW: 3.5, 7.0  CRM: 4.0, 5.0, 6.0, 7.0  Resources SAP TDMS on sap.com www.sap.com/tdms SAP TDMS on SAP Service Marketplace http://service.sap.com/tdms© 2010 SAP AG. All rights reserved. / Page 54
  • 55. Performance Monitoring & Suggested Parameters  TCODE: MWBMON, MWB_TRANSFER_PERFORM  REPORT: CNV_MBT_TRACK_TRANSFER_PROGRES  SQLNET.ORA: TCP.NODELAY = YES  BTC & DIA: Minimum 25 processes each  DB: Increase UNDO size  PARALLELLISM: "Troubleshooter for CKMLMV004“  "Adjust parameter for execution"  P_CLU & P_PARA© 2010 SAP AG. All rights reserved. / Page 55
  • 56. Migration Strategies  Production System with closed Database Consistency Downtime required  Production System with open Database No downtime required Inconsistencies  Snapshot of Production Storage Consistency, no downtime required Additional hardware, additional license fees for snapshot solution  Copy of Production System Consistency, no downtime required Additional hardware cost  Quality Assurance System Consistency Downtime required© 2010 SAP AG. All rights reserved. / Page 56
  • 57. Agenda SAP TDMS Overview 1. Customer Situation and Challenges 2. Solution Approach and Technology 3. Benefits & Use Cases 4. Facts and Figures 5.Questions & Answers© 2010 SAP AG. All rights reserved. / Page 57
  • 58. Questions & Answers© 2010 SAP AG. All rights reserved. / Page 58
  • 59. Thank You! Turan Tekçiçek SAP Netweaver Technology Consultant turan.tekcicek@gmail.com +90 533 429 21 12© 2010 SAP AG. All rights reserved. / Page 59