Know-How Network: Experiences from Large Data Warehouse Implementations: the 60 Terabyte Showcase. Ron Silberstein Platinum Consultant, SAP

Transcription

1 Know-How Network: Experiences from Large Data Warehouse Implementations: the 60 Terabyte Showcase Ron Silberstein Platinum Consultant, SAP

2 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

3 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

4 Putting Things Into Perspective: PoC Rationale Proof of Concept on customer s request Are SAP and IBM able to provide a hardware and software environment which can handle future requirements of a large Consumer Goods customer? Future requirements mainly defined by rapid data growth due to the company s world-wide adoption of new markets Current size of customer data Customer has three operational BW systems (EUR, Americas, APA) All three systems among the top 5 productive SAP BW systems worldwide Each system currently holds 20+ TB worth of data Size in GB Size in GB BW - Database Size (GB) BW - Database Size (GB) Week Week Example: data growth of EUR BW system over 15 months Currently Allocated: ~23 TB Used: ~20 TB Growth rate: ~ 8 TB / year Allocated Used Allocated Used SAP AG 2007, SAP TechEd 07 / BI209 / 4

5 Putting Things Into Perspective: PoC Rationale Data volume growth in near future Size projection given by customer Based on assumption that new markets will be integrated Steady state by archiving not before 2010 Migration of existing ODS data to Corporate Memory Imagine total storage ~ 80 TB per system 3 Systems Mirrored disks! Two data centers! Not counting test and QA systems Concerns (BW and infrastructure) Feasibility Manageability Performance Database Used size (TB) Database Used size (TB) EUR DB Growth to 2010 EUR DB Growth to Year Ending Year Ending Example: EUR BW system growth without Corporate Memory Database Used size (TB) Database Used size (TB) EUR DB Growth to 2010 EUR DB Growth to Year ending Year ending Example: EUR BW system growth with Corporate Memory 2007 Markets Markets Markets Markets Markets 2005 Markets Corporate Memory Corporate Memory ODS / PSA / Cubes ODS / etc PSA / Cubes etc SAP AG 2007, SAP TechEd 07 / BI209 / 5

6 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

7 Project Outline Proof of Concept Project Joint project set up at IBM Customer Center P.S.S.C in Montpellier Two phase approach: Phase 1 Prove existing landscape to be able to handle 20 TB Determine requirements of 60TB landscape Start with tests on production system copy (7 TB) Grow data to 20 TB and rerun tests Same system environment as at customer site Phase 2 Hardware architecture derived from Phase 1 experience Baseline comparison (20TB) with Phase 1 architecture Grow data from 20 TB to 60 TB and rerun tests Phase 1 Phase 2 Time Line 02/06 03/06 04/06 05/06 06/06 07/06 08/06 09/06 10/06 11/06 12/06 01/07 02/07 03/07 04/07 05/07 Prepare environment Restore cutomer syst. Tapes received Data restored DB2 Reorg, storage opt., Load calibration Detailed context analysis 7TB, prepare and complete 20TB 20 TB results: detailed analysis Lessons learned Phase 2 hardware setup Customer workshop Base line Phase 1 sign-off Data 20 TB 60 TB hardware adjustments : Hardware release Prepare and complete 60 TB SAP AG 2007, SAP TechEd 07 / BI209 / 7

8 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

9 Test Requirements : SAP BW Focus KPI Targets Mixed Load Scenario: Data Load from ODS Objects into InfoCubes Aggregates Roll Up Reporting with limited avg. Response time Size of Fact Table for "ad hoc" queries 250 Loading Rollup Query Million Rows KPIA KPID KPIG SAP AG 2007, SAP TechEd 07 / BI209 / 9

10 Test Requirements : Infrastructure Focus KPI Targets 20 TB 60 TB Architecture Requirements: Data availability business critical Fixed maintenance windows despite growing data volume Minimum disaster recovery times 7 TB Recovery of a day s work: < 8 h Disaster Recovery: < 24 h Daily tape backup: < 12 h Daily backup to disk: < 8 h Impact of online DB tape backup: < 20 % Index recreation: < 2 h SAP AG 2007, SAP TechEd 07 / BI209 / 10

11 Data Model Objects and data provided by customer Two ODS objects with anonymized data ~35 million records Two different InfoCubes Profitability Analysis: 14 dimensions, 108 key figures, 10 aggregates Sales Statistics: 16 dimensions, 107 key figures, 21 aggregates Complex update rules 10 Queries 80% on aggregates, 20% selectively on fact tables 50% using OLAP cache, 50% not using OLAP cache Data model for tests 50 copies of each InfoCube (100 InfoCubes total) 4 copies of each ODS object (8 ODS objects total) Copies of update rules, InfoPackages, SAP AG 2007, SAP TechEd 07 / BI209 / 11

12 Data Model 2 Reporting Data Load MP01 MP02 IC001 IC002 IC003. IC024 IC025 ODS1 ODS2 MP01 MP02 IC026 IC027 IC028. IC049 IC050 ODS1 ODS2 MP01 MP02 IC051 IC052 IC053. IC074 IC075 ODS1 ODS2 MP01 MP02 IC076 IC077 IC078. IC099 IC100 ODS1 ODS2 Logical Group 1 Logical Group 2 Logical Group 3 Logical Group 4 Sales Statistics Profitability Analysis Controlling SAP AG 2007, SAP TechEd 07 / BI209 / 12

13 Data Model 3 Data Load Scenarios KPI-A: Parallel load by ~35 dialog processes per extractor IC1 IC2 IC3 IC4 IC5 IC6 IC7 IC8 Multiple extractors running at the same time KPI-D, KPI-G: Split Scenario: two extractors per ODS object with disjoint datasets IC1 IC2 IC3 IC4 IC5 IC6 IC7 IC8 Optimization goal: load throughput (number of records loaded into InfoCubes per hour) SAP AG 2007, SAP TechEd 07 / BI209 / 13

14 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

15 System Environment Phase 1 Parallel testing and risk mitigation Three identical copies of customer system set up One system to remain on 7 TB - reconfiguration, - functional verification - baseline performance One system to grow data to 20 TB (online tests) One system cloned at 20 TB (infrastructure tests) Each system with its own DS8000 storage subsystem Blade based injectors with Mercury LoadRunner for query load generation 16 LTO3 tape drives SAP AG 2007, SAP TechEd 07 / BI209 / 15

16 System Environment Phase 1 SAP BW AS SAP BW AS Database Architecture for PoC to 20TBs 1 x p5-p595 for DB server 1 x DS8k Storage Server SYS-2: 7 TB LoadRunner load injectors Server SAP BW (CI, AS) IBM p595 DB2 part0 DB2 64 CPUs p6.. 1,9 GHz DB2 p GB RAM SYS-3: DB2 p TB 29 DB2 p SAN IBM DS8K 384 / 640 disks 30 / 51 TB gross Storage SAP BW AS SAP BW AS SYS-1: 20 TB Tape Library SAP AG 2007, SAP TechEd 07 / BI209 / 16

17 System Environment Phase 2 Database Architecture for PoC to 60TBs SAP BW CI, AS 5 x p5-p595 4 x DS8300 Storage Mercury LoadRunner load injectors Server (5 * p595, power5+) DB2 part0 SAP BW AS DB2 part6 DB2 part13 SAP BW AS DB2 part14 DB2 part21 SAP BW AS DB2 part22 DB2 part29 TSM SAN Storage (4 * DS8300 turbo) SAP BW AS DB2 part30 DB2 part37 SYS-1: 60 TB Tape Library SAP AG 2007, SAP TechEd 07 / BI209 / 17

18 PoC System Architecture Phase II MCP16H MCP16I MCP16J MCP16K MCP16L MCP16M MCP16G Sys1db0 Sys1db1 Sys1db2 Sys1db3 Sys1db4 deats005 nim Sys1ci test torontoci Sys1onl0 Sys1btc0 Sys1ext0 Sys1sta0 Sys1onl1 Sys1onl2 Sys1onl3 Sys1onl4 Sys1btc1 Sys1btc2 Sys1btc3 Sys1btc4 PoC Infrastructure footprint : Sys1sta1 Sys1sta2 Sys1sta3 Sys1sta4 Sys2db0 Sys2db1 Sys2db2 Sys2db3 4 FC 4 FC 8 FC Name : sw10 IP : I Sys2as05 8 FC 8 FC 16 FC Sys2as04 Sys2as03 Sys2ci Name : sw FC 98 FC 2.3 GHz IP : p CPUs 4 FC 4 FC 12 FC 12 FC 8 FC 8 FC 8 FC 8 FC 8 FC 8 FC 8 FC 8 FC Sys2as06 16 FC 16 FC 16 FC FC 8 TeraBytes FC 8 FC 8 FC Disk Space 8 FC 8 FC TeraBytes Server Server RAM RAM GHz p5 CPUs 100 Name : brocade2 100 Gbit network IP connections : Fiber channel connections 16 FC 4 FC 4 FC 4 FC 4 FC Name : brocade1 IP : Up Up to to 3 parallel landscapes for for concurrent testing Sys2db4 10 FC 10 FC 68 FC 20 FC 176 FC Name : sw12 IP : DPFG & disks 75-DNXD disks 75-DPFL disks 75-DPF disks 75-DNHV TSM pool + SYS2 (6-37) 640 disks 68 LTO3 Drives SAP AG 2007, SAP TechEd 07 / BI209 / 18

19 Evolution of the Database DB Architecture: DB2 DPF Phase1 Phase2 Customer Clone DB2 DPF Partitions 0-5 Single LPAR DB2 Partition 0 (1-5 dormant) DB2 Partitions 6-13 DB2 Partition 0 (1-5 dormant) DB2 Partitions 6-13 DB2 Partitions DB2 Partitions DB2 Partitions DB2 Partitions DB2 Partitions DB2 Partitions Single DB LPAR with 6 DB2 DPF partitions 6->33 Partitions Redistribution of data over 33 DB2 DPF partitions and 5 x p5 LPARs Phase2 Scalability: DB2 distributed over 5 p595s. Final phase is p5 virtualization: shared processor pool SAP AG 2007, SAP TechEd 07 / BI209 / 19

20 Evolution of DS8k Storage Server(s) Phase1 Single Server Phase2 60TB Design Redistribute Redistibute DB2 (33 Partitions) Non Shared Resources 7TB KPIA Grow to 20TB DS8300 Turbo Upgrade 20TB KPID Grow to 60TB 4 * DS8300 Turbo 60TB KPIG SAP AG 2007, SAP TechEd 07 / BI209 / 20

21 Evolution of System p5 Baseline KPIA KPID KPIG 64 CPUs 128 CPUs 224 CPUs 320 CPUs LPAR0 (DB2) partition0 AS01 (sysxas03/sysxas05) 32 cpu AS01 (sysax03) 32 cpu DB Svr APS Svr Load APS Svr Online Storage Agent LPAR1 (DB2) partition6 - partition13 LPAR2 (DB2) partition14 - partition21 LPAR3 (DB2) partition22 - partition29 LPAR4 (DB2) partition30 - partition37 AS02 (sysxas04/sysxas06) 32 cpu Move CI AS02 (sysax04) 32 cpu AS03 (sysax05) 32 cpu AS04 (sysax06) 32 cpu 5 x p595(64cpus) = 320 total avail. LPAR5 (SAP) CI 00 APP 01 APP 02 Expand DB to 64 CPUs CI 00 APP 01 Batch APP 02 Online Shared Processor Pool 64CPU End of Phase 1 Phase 2 SAP AG 2007, SAP TechEd 07 / BI209 / 21

22 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

23 Test Description KPI-A/D/G Data load and aggregate roll-up Data load and roll-up of aggregates using a subset of InfoCubes, controlled by process chains Fine tuning by adapting Number of concurrent aggregates in rollup Number of extractors to optimize usage of available work processes Size of data packages Number of parallel work processes spawned per extraction process Number of target InfoCubes to be filled by one extractor Query Load Generic Mercury LoadRunner script calling all 10 queries sequentially Query selection criteria varied with each iteration Selection values read from control files as provided by the customer SAP AG 2007, SAP TechEd 07 / BI209 / 23

24 Test Results KPI-A/D/G Data Load Target KPI Targets and Actuals 140 Data Load Actual Aggregate Rollup Target Aggregate Rollup Actual Query Throughput Target Query Throughput Actual 2,50 All targets (over-) achieved Million records / h ,00 1,50 1,00 0,50 Queries / s Resource Consumption SAPS DB2 SAPS BW Linear (SAPS DB2) Linear (SAPS BW) 0 KPI A KPI D KPI G 0, Load Factor CPU Scaling for Load Factor 5: Total: 2.88 DB2: 2.22 BW: 3.18 CPU (SAPS) Load Factor RAM (GB) SAP AG 2007, SAP TechEd 07 / BI209 / 24

25 Test Results for Infrastructure KPIs KPI Objective Targets Results 20 TB Results 60 TB 1 Flashback and roll forward of 500 GB < 8 hours 4:20 (1 x DS8300) 02:40 (4 x DS8300) 2 DB restore and roll-forward of 2TB logs; start SAP BW < 18/24 hours 12:20 (16 drives) 10:00 (34 drives) 3a Tape backup and flashcopy < 8/12 hours 6:35 (16 drives) 6:10 (34 drives) 3b Flashcopy under online load (25 nav. steps / minute, 25 million records data load) < 8 hours 0:30 hours 3c Tape backup and flashcopy under online load (25 nav. steps / minute, 25 million records data load) < 8 hours with performance degradation < 20% 6:58 hours, < 15% 06:58 < 15% 4 Rebuild 3TB of indexes in DB2 < 2 hours 1:05 SAP AG 2007, SAP TechEd 07 / BI209 / 25

26 Example: Disaster Recovery Restore 60 TB DB from Tape, reapply 2TBs of Logs Backup Duration: 5hours, 27 minutes Restore Duration: 6 hours, 40 minutes Restore per DB2 Partition 800,00 700, GB/h => 133 MB/sec. 600,00 500,00 GB/hour 400,00 300,00 200,00 100,00 0, Partition Number SAP AG 2007, SAP TechEd 07 / BI209 / 26

27 Example: Rollforward of 2TB Logs 60 TB Tape Restore 250 Rollforward Recovery per Partition Taking full advantage of partitoned database 200 Logfiles recovered (GB) Partition 0 32 in parallel Restore Duration: 2hours, 52 minutes 0 0:00:00 03:30:00 01:00:00 04:30:00 02:00:00 05:30:00 03:00:00 06:30:00 Elapsed Time SAP AG 2007, SAP TechEd 07 / BI209 / 27

28 Overview of Final InfoCube Sizes 450 InfoCube Sizes Number of records (million) ZGTFC001 ZGTFC002 ZGTFC003 ZGTFC004 ZGTFC005 ZGTFC006 ZGTFC007 ZGTFC008 ZGTFC009 ZGTFC010 ZGTFC011 ZGTFC012 ZGTFC013 ZGTFC014 ZGTFC015 ZGTFC016 ZGTFC017 ZGTFC018 ZGTFC019 ZGTFC020 ZGTFC021 ZGTFC022 ZGTFC023 ZGTFC024 ZGTFC025 ZGTFC026 ZGTFC027 ZGTFC028 ZGTFC029 ZGTFC030 ZGTFC031 ZGTFC032 ZGTFC033 ZGTFC034 ZGTFC035 ZGTFC036 ZGTFC037 ZGTFC038 ZGTFC039 ZGTFC040 ZGTFC041 ZGTFC042 ZGTFC043 ZGTFC044 ZGTFC045 ZGTFC046 ZGTFC047 ZGTFC048 ZGTFC049 ZGTFC050 ZGTFC051 ZGTFC052 ZGTFC053 ZGTFC054 ZGTFC055 ZGTFC056 ZGTFC057 ZGTFC058 ZGTFC059 ZGTFC060 ZGTFC061 ZGTFC062 ZGTFC063 ZGTFC064 ZGTFC065 ZGTFC066 ZGTFC067 ZGTFC068 ZGTFC069 ZGTFC070 ZGTFC071 ZGTFC072 ZGTFC073 ZGTFC074 ZGTFC075 ZGTFC076 ZGTFC077 ZGTFC078 ZGTFC079 ZGTFC080 ZGTFC081 ZGTFC082 ZGTFC083 ZGTFC084 ZGTFC085 ZGTFC086 ZGTFC087 ZGTFC088 ZGTFC089 ZGTFC090 ZGTFC091 ZGTFC092 ZGTFC093 ZGTFC094 ZGTFC095 ZGTFC096 ZGTFC097 ZGTFC098 ZGTFC099 ZGTFC100 InfoCube Name Total number of records in 100 InfoCubes: 29,908,216,067 minimum: 118,996,691 maximum: 464,369,201 SAP AG 2007, SAP TechEd 07 / BI209 / 28

29 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

30 Lessons Learned: Partitioning and Architecture Matter!... SAP BW 3.5 App. Server SAP BW 3.5 App. Server SAP BW 3.5 App. Server SAP BW 3.5 App. Server Phys. Resources DB2 part0 LPAR 0 p595 I / O Resources R D B M S : I B M D B 2 9 D P F TS3 TS3 TS3 TS1 TS2 TS1 TS2 TS1 TS2 part0 part0 DB2 part8 DB2 part16 DB2 part24 part0 DB2 part24 part32 part0 LPAR 1 LPAR 2 LPAR 3 LPAR 4 p595 p595 p595 p595 DS8300 DS8300 DS8300 DS8300 SAP AG 2007, SAP TechEd 07 / BI209 / 30

31 Lessons Learned: Deployment of BI Accelerator Load Distribution Ratio: DB:Application Load Distribution Ratio DB:Apps KPIA 20TB Apps 6 DB 2 2 2, Load Aggregate Query KPI-A Observation: with growing data volume DB load increases significantly for aggregate Maintenance Load Profiles at 60TB KPID Recommendation: Apps DB 5,07 4,69 h 2,72 2, Load Agg Query KPIG BI Accelerator greatly disburdens DB during aggregates maintenance SAP AG 2007, SAP TechEd 07 / BI209 / 31

32 Lessons Learned: Deployment of BI Accelerator 2 DB Read / Write Distribution Ratio Load Distribution Ratio Read - Write Number of I/Os Average Query Load Aggregate KPI-A Read Write Observation: Queries impose high Read I/O rate (note: 20% of queries do not use aggregates!) Recommendation: BI Accelerator not only provides predictable response times, but also takes off read load from the database SAP AG 2007, SAP TechEd 07 / BI209 / 32

33 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

34 Further Steps - DB2 V9 Deep Compression Compression candidates and rates Type Number ODS 26 PSA 517 Fact 100 Disk storage Compession Rate 79% 64% 86% 48% Less disk space required Less IO for more data Increase data in memory improved buffer pool quality Improvement Aggregate throughput Query execution Query response time +15% +3.5 % -23% SAP AG 2007, SAP TechEd 07 / BI209 / 34

35 Further Steps - DB2 V9 Deep Compression: Read I/O Thousands Disk Read kb/s sys2db1 (1st 50) uncompressed IO Read Rates uncompressed :49 17:51 17:53 17:55 17:57 17:59 18:01 18:03 18:05 18:07 18:09 18:11 18:13 18:15 18:17 18:19 18:21 18:23 18:25 18:27 18:29 18:31 Thousands 18:33 18:35 18: Disk Read kb/s sys2db1 (1st 50) compressed :13 11:15 11:17 11:19 11:21 11:23 11:25 11:27 11:29 11:31 11:34 11:36 11:38 11:40 11:42 11:44 11:46 11:48 11:50 11:52 11:54 11:56 11:58 12:00 12:02 Significantly less IO with compression! SAP AG 2007, SAP TechEd 07 / BI209 / 35

36 Further Steps: Virtualization Goal: Reduce overall CPU requirement by processor sharing P595 N 1 to 4 : MAX CPU per P595 = 64 Resource Sharing Priority Policy Max CPU:48 Max 10 Max CPU:20 DB Online Upload Backup DB & Online servers Highest priority Set by relative weighting Batch servers Low priority but unlimited resource Able to use any free CPU cycles Backup servers Reliable behavior Limited but guaranteed resources SAP AG 2007, SAP TechEd 07 / BI209 / 36

37 Further Steps: Load Balancing LoadRunner load injectors Distribution of Query load via WebDispatcher Better Distribution over shared processor pools SAP WebDispatcher Online Online Online Online Online DB DB DB DB DB Aggregate Extractor Upload Upload Upload Upload SAP CI Backup Backup Backup Backup Backup SAP AG 2007, SAP TechEd 07 / BI209 / 37

38 Putting Things Into Perspective: PoC Rationale Project Outline Test Requirements and Data Model System Environment Test Description and Results Lessons Learned Next Steps Summary

39 Summary Scalability Real-world scenario with simulated growth over 5 years Customer driven KPIs for data load, maintenance, and query performance NO LIMITS - Results strongly indicate further scalability! Platforms Combination of SAP BW and IBM DB2 9 DPF proven to be industrialstrength platform for very large Data Warehouse solutions Massive Performance and scalability benefits from powerful DB2 9 DPF partitioning feature Largest SAP BI Data Warehouse World Wide so far! SAP AG 2007, SAP TechEd 07 / BI209 / 39

40 Further Information SAP Public Web: SAP Developer Network (SDN): Business Process Expert (BPX) Community: Related SAP Education and Certification Opportunities Related Project Material Extreme Business Warehousing: Experiences with SAP Netweaver BI at 20 Terabytes, IBM Redbook on Project Phase I IBM Redbook on Phase II in preparation SAP AG 2007, SAP TechEd 07 / BI209 / 40

41 Copyright 2007 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, System i, System i5, System p, System p5, System x, System z, System z9, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP AG 2007, SAP TechEd 07 / BI209 / 41

42 Copyright 2007 SAP AG. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint und SQL Server sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, System i, System i5, System p, System p5, System x, System z, System z9, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, POWER5+, OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation. Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern. ORACLE ist eine eingetragene Marke der ORACLE Corporation. UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group. Citrix, das Citrix-Logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP -Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. SAP AG 2007, SAP TechEd 07 / BI209 / 42