SIZING GUIDE

Sizing SAP NetWeaver Information Lifecycle Management

Sizing SAP NetWeaver BW

Released for SAP Customers and Partners

Document Version 1.0, March 2010

Please make sure that you are always using the most current version of the sizing guideline!

 Copyright 2010 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.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Disclaimer IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. SAP Library document classification: CUSTOMERS & 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. PARTNERS Documentation in the SAP Service Marketplace You can find this documentation at the following address:
http://service.sap.com/sizin

Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.

Information Lifecycle Management

Hardware sizing of SAP NetWeaver BW
If you would like to use the Quick Sizer to size the SAP NetWeaver BW part of an Information Lifecycle Management retention warehouse, you can use the following guidelines and template. Create your own project and use the default values we provide below. For each table we also indicate where you have to enter your own values. Follow the steps as described: 1. Create a Quick Sizer project: https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/quicksizer/main.do a. For questions regarding the handling of the tool, please refer to the documentation Quick Sizer for beginners on the entry screen. b. Per default you will find your customer number. To create a project, type in a project name and choose create project.

Graphic 1: Initial entry screen of the Quick Sizer

2. On the left side, you find the QS navigation tree. In case of the SAP Net Weaver BW sizing for Information Lifecycle Management, the only relevant questionnaire that needs to be considered is the Business Warehouse questionnaire (highlighted in red on graphic 2).

Graphic 2: Navigation tree and corresponding questionnaire

SAP AG

Sizing SAP NetWeaver ILM - SAP Customers and Partners

3. Choose Business Warehouse, to open the questionnaire. The default values you will see are the values for regular SAP NetWeaver BW sizing in an online environment. Enter the template values we suggest for SAP NetWeave BW sizing in an Information Lifecycle Management environment as described in these steps and as shown in the graphics. In addition, where indicated adjust the entries based on your specific requirements. 4. The Quick Sizer SAP NetWeaver BW sizing questionnaire consists of five different tables. In case of Information Lifeycle Management, you only need to consider Tables 2, 3 and 5. The other tables can be ignored, due to the different parameters needed in an Information Lifecycle Management.

5. Table 2: Throughput User Groups: Reporting & Analysis: In SAP NetWeaver BW, the Quick Sizer distinguishes between user types according to their frequency of activity and the reporting they will normally do.
Example: adjust as needed

Graphic 3: User Groups: Reporting & Analysis

a. For Information Lifecycle Management, we suggest that you use the BW-Info user and the BW-Expert users. b. Specify the number of BW users and enter them in the table. Per default, you will have a distribution of 80/20 in regards to Report Viewing and OLAP Analysis. For ILM, change this to 100 for Data Exploration, as seen in Graphic 3. Also check the flag Web (Web JAVA Reporting).1 Note: This Table mainly influences memory requirements. 6. Table 3: Throughput Data Upload to SAP NetWeaver BW
Example: adjust as needed Example: adjust as needed

Graphic 4: Data Upload to SAP NetWeaver BW

a. Enter the number of data records that need to be uploaded within a peak time period, for example for one audit. To obtain a sizing for the largest possible use case, sum up all the records that are loaded during the periodic upload process in Table 5. b. Make sure you choose the right peak time (S.t. and E.t. columns = from/to upload period). The shorter the peak time, the higher the result (and consequently the required hardware resources). Define this peak time interval carefully, depending how fast the data records need to be available. In an Information Lifecycle Management scenario, we assume that you have more time for data upload than in an online SAP NetWeaver BW scenario. As a suggested value we therefore entered 24 hours in our sizing template. Note: This table has mainly an influence on the CPU requirements.

In SAP NetWeaver BW, reporting can be done either through the Excel based BEx Analyzer or through a Web browser. If you use Web reporting, you need to check the flag web.

SAP AG

Sizing SAP NetWeaver ILM - SAP Customers and Partners

7. Table 5: Throughput Definition of DataStore Objects

Default values: dont change them

Example values: use transaction SE16 to get the real values from your legacy system Default values: dont change them

Graphic 5: Definition of DataStore Objects

a. In Table 5, enter the DataStore Objects you use in your reporting. i. With the insert button, enter 22 lines (these represent the pre-delivered queries offered with Information Lifecycle Management. If you have created more queries in your project you must also enter them here). Copy the tables entered under Short text. ii. Copy the following template values shown in Graphic 5 into your own Quick Sizer project: NumFld (Numeric Field): number of numeric fields in the DSO TxtFlds (Text Field): number of text fields in the DSO CharLg (Character length): average length of character fields in bytes iii. Under Periodic Upload enter the number of records you upload into SAP NetWeaver BW. The best way to find out a realistic estimation of the entries here is to check the number of entries in the corresponding database tables in your legacy system. In your legacy system call transaction SE16 and enter a table from the list (e.g. ANLB, BKPF, etc.). Run the transaction to find out how many entries each table contains. Enter this number under Periodic Upload. iv. Under Period use the default value we have suggested in this template. Unlike in online BW scenarios, in Information Lifecycle Management there is just one upload to fill a DSO. b. If you have created additional DataStore Objects for your reporting, enter them as described before. You must then also figure out how many Numeric and Text fields and average Character length you have for each DSO. Master data uploads are also treated somewhat differently in an Information Lifecycle Management scenario and must be accounted for in the sizing. For this template we have accounted for three different types of master data. If possible, try to find out how many items each master data table contains and also enter it in Table 5.

SAP AG

Sizing SAP NetWeaver ILM - SAP Customers and Partners

Note: This table mainly influences disk requirements. 8. To get your final result, click on calculate results and you will see the corresponding number for your CPU (expressed in SAPS), memory (expressed in MB), and disk (expressed in MB)

SAP AG

Sizing SAP NetWeaver ILM - SAP Customers and Partners