Quicksizing SAP NetWeaver XI

Holger Faulhaber
SAP NetWeaver RIG XI SAP AG

Content: Quicksizing XI 1. Using Quick Sizer for XI

1. Demo and Examples 2. Collecting Data 3. Exercise: Quicksizing 4. Sizing: Non-Central Adapter Engine

2. Finding Hardware for SAPS Numbers 3. Itemfield Conversion Agent Sizing 4. TRex Sizing for Indexing XI Messages 5. Finding Message Sizes 6. Good Message Sizes 7. Quicksizing Limitations

SAP AG 2005, XI 3.0 Quicksizing / 2

Entering Quick Sizer http://service.sap.com/quicksizer Choose Start the Quick Sizer.

If you do not have a valid customer number, use 188213. Enter a project name of your choice, for example: Sizing1 To start a new sizing, choose Create Project.

In the Tree of elements, navigate to: SAPNetweaver -> SAPNetweaver -> Exchange Infrastructure

SAP AG 2005, XI 3.0 Quicksizing / 3

First Steps in Quick Sizer Change the Peak load setting from 12:00 - 13:00 to 00:00 - 24:00. For XI-specific help and information, choose Help.

SAP AG 2005, XI 3.0 Quicksizing / 4

Initial Sizing: First guess of 50,000 messages a day Example: 50,000 messages of 100 KB a day, without peak Enter:

Choose Calculate result. Sizing result:

SAP AG 2005, XI 3.0 Quicksizing / 5

Advanced Sizing Initial throughput and three detailed scenarios:

Result:

Graphic:

SAP AG 2005, XI 3.0 Quicksizing / 6

Sizing Data for Database and Application Server If you select Software component as the Result level, Quick Sizer calculates SAPS and RAM requirements separately for:
Database Application

SAP AG 2005, XI 3.0 Quicksizing / 7

Notes for XI Sizing with Quick Sizer The size of a message is the XML size at the XI server outbound channel. Example: IDoc-XML size, message size after data enrichment. The number of messages is the number of outgoing messages. Example: If you send 100 messages to 3 receivers, the number of messages is 300 messages. Weekly, monthly, annual, and single initial load peaks cannot be modeled directly in XI Quick Sizer. They must be included in the total amount.

SAP AG 2005, XI 3.0 Quicksizing / 8

Very Advanced Sizing Example ~ Shortly Before Go-Live

Extract of input to Quick Sizer:

Result as graphic:

Total:

SAP AG 2005, XI 3.0 Quicksizing / 9

Sizing: Non-Central Adapter Engine 5,000 SOAP messages of 70 KB between 00:00 and 20:00 Note: Do NOT make entries in Table 1 or Table 2.

Sizing result:
SAP AG 2005, XI 3.0 Quicksizing / 10

DB groth rate for long Message Retention Time

For simplification: 100 MB * 40 days = 4 Gig Aditional to Basis database size

SAP AG 2005, XI 3.0 Quicksizing / 11

Exercise 1: Quick Sizer (30 Minutes)

Calculate the required number of SAPS and define the peak hour(s). http://service.sap.com/quicksizer -> Quick Sizer Create project Group<xy> with customer number 188213, where <xy> is your group number.

Scenario data: 1. File -> IDoc, 20,000 messages of 120 KB a day 2. IDoc -> JMS, JDBC, and IDoc, 3,000 messages/hr of 100 KB between 06:00 and 09:00 3. SOAP <-> JDBC, 500 messages of 20 KB between 08:00 and 18:00 All scenarios include content-based routing and Java mapping No scenario works with acknowledgments
SAP AG 2005, XI 3.0 Quicksizing / 12

Exercise 2: Find Hardware for SAPS Numbers Find hardware (from vendor of your choice) for 3,000 SAPS.

http://service.sap.com/sizing -> Standard Application Benchmarks -> SD two-tier results

SAP AG 2005, XI 3.0 Quicksizing / 13

Itemfield Conversion Agent Sizing If you use Itemfield Conversion Agent, additional SAPS are required to process the transformations. Below are the SAPS requirements for Excel, PDF, HL7, and HL7 Serializer transformations:
http://help.sap.com/ -> Documentation -> SAP NetWeaver -> SAP NetWeaver 2004 -> Process Integration -> SAP Exchange Infrastructure -> Runtime -> Connectivity -> Conversion Agent -> Conversion Agent Operations Manual -> Chapter: Sizing

SAP AG 2005, XI 3.0 Quicksizing / 14

TRex Sizing for Indexing XI Messages Quick Sizer for TRex calculates using the number of competing dialog users. Quick Sizer gives no numbers for the indexing of documents, which is XIs main use of TRex. To estimate the SAPS for the XI usage case, use the sizing document. http://trex:1080 -> Documentation -> 6.1 -> Sizing -> Point 2.2.2

SAP AG 2005, XI 3.0 Quicksizing / 15

TRex Sizing for Indexing XI Messages: Example Example:

100,000 messages Within 24 hours Average message size: 100 KB

Volume calculation: 100,000 messages * 100 KB ~ 10 GB of data

Find SAPS in table: Row 24 hrs and column 10 GB Result = 500 SAPS for TRex indexing hardware with 2.5 GB RAM

Important: This is just a short example. For more information, read the whole TRex sizing document.

SAP AG 2005, XI 3.0 Quicksizing / 16

Message Sizes First Estimation Message Size on the Integration Server Mesage Size in the Runtime Workbench

SAP AG 2005, XI 3.0 Quicksizing / 17

Collect Relevant Sizing Data Rule of thumb: If all you know is the average message volume per day:

Number of expected messages per day with average message size of 100 KB per message with no peaks in 24 hours

As the first estimation!

SAP AG 2005, XI 3.0 Quicksizing / 18

Find Message Size on the Integration Server

To find your message, call transaction SXMB_MONI and choose RunTime in the Call Adapter folder. The total message size is displayed, and on the next line the message payload size.

SAP AG 2005, XI 3.0 Quicksizing / 19

Find Message Size in the Runtime Workbench XI Runtime Workbench -> Performance Monitoring To display individual message payload sizes, select Overview Individually.

SAP AG 2005, XI 3.0 Quicksizing / 20

Good Message Sizes Throughput example:

12,00 10,00 GByte / hour 8,00 6,00 4,00 2,00 0,00 30 98 698 message size (kb) 2.309 6.915

Measured throughput as Gbytes per hour

Rules of thumb for high throughput: Avoid small messages (less than 100KB) Avoid large messages (greater than 2MB)

SAP AG 2005, XI 3.0 Quicksizing / 21

Get Larger Messages from Adapters/Applications Collect single messages of the same type and send together. Use packages where possible. Append Files and send together.

SAP AG 2005, XI 3.0 Quicksizing / 22

Quicksizing Limitations No information on resource distribution for ABAP or J2EE Based on assumptions Tends to oversize

Ongoing evaluation as project develops: 1. Implement main or typical customer scenario 2. Measure it with RWB Performance Monitoring 3. Optimize settings 4. Recalculate overall SAPS demand

SAP AG 2005, XI 3.0 Quicksizing / 23

Further Information
SDN Weblogs from Susanne Janssen regarding Quick Sizing:
Efficient SAP Hardware Sizing: Quick Sizer Quick Sizer 2005 - Getting started Interpreting Quick Sizer Results

Sizing and Benchmarks on the SAP Service Marketplace: http://service.sap.com/sizing http://service.sap.com/benchmark Related topics: XI Troubleshooting Guide Note: 806546 XI 3.0 Tuningguide http://service.sap.com/instguides -> NW04 >Operations XI 3.0 Performance Check Note: 894509 AGS Services - http://service.sap.com/safeguarding -

SAP AG 2005, XI 3.0 Quicksizing / 24

Copyright 2005 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation. 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 2005, XI 3.0 Quicksizing / 25

Copyright 2005 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix und Informix Dynamic ServerTM sind Marken der IBM Corporation. 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 erwhnte Namen von CitrixProdukten 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 erwhnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Lndern 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 knnen lnderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrcklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorlufige Version, die nicht Ihrem gltigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankndigung gendert werden. SAP bernimmt keine Haftung fr Fehler oder Auslassungen in dieser Publikation. Des Weiteren bernimmt SAP keine Garantie fr die Exaktheit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht fr entstandene Schden. Dies gilt u. a. und uneingeschrnkt fr konkrete, besondere und mittelbare Schden oder Folgeschden, die aus der Nutzung dieser Materialien entstehen knnen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab.
SAP AG 2005, XI 3.0 Quicksizing / 26