XI_Sizing

1

Performance, Data Management & Scalability

Bill Adams, SAP AG

Sizing Exchange Infrastructure

© SAP AG 2005, XI 3.0 Quicksizing / 2

Agenda

SAP Exchange Infrastructure

Introduction to XI

Using XI in the Quick Sizer

Best practices

Exercise

2


Mission

SAP XI is an integration platformfor SAP and non-SAP applications

for A2A and B2B scenarios

for a Service Oriented Architecture

for cross-component Business Process Management

SAP XI


In a Nutshell: Process Integration with XI 3.0

Adapter Framework (JCA-based)Integrate application systems and

business partners via resource adapters

Adapter Software Development KitCertification of 3rd party adapters

B2B EnablementCollaboration partner data in the

Integration DirectoryPartner Connectivity Kit B2B security

Industry Standards SupportPlatform for process modellingAdapters, e.g. RosettaNet (RNIF 2.0)

Cross-Component Business Process Management

Design, execute and monitor automated processes across applications and systems

Graphical ModelerBPEL support

Full Platform SupportSame Unicode platforms as SAP Web

AS

Integration with Central SAP Monitoring Infrastructure

Drill down to individual process stepsUse of SAP Web AS Alert Framework

3


Supported Protocols

Adapter Engine (J2EE)SMTP, IMAP4XIALL, XIPayloadMail

Adapter Engine (J2EE)HTTP/SRNIF 1.1CIDX

Adapter Engine (J2EE)HTTP/SRFC-XMLSAP BC

Adapter Engine (J2EE)Business PartnerHTTP/SRNIF 2.0RosettaNet

Adapter Engine (J2EE)MarketplacesHTTP/S, JMSMMLMarketplace

Adapter Engine (J2EE, J2SE)Queuing-SystemVarious JMS-Providers (e.g. SonicMQ, MQSeries, WebMethodsMQ)

JMSJMS

Adapter Engine (J2EE, J2SE)DB-SystemJDBC 2.0XML/SQL, native SQLJDBC

Adapter Engine (J2EE, J2SE)File-System,FTP-Server

File, FTPFile, File/Content C.File / FTP

Adapter Engine (J2EE, J2SE)3rd Party SystemHTTP, SMTPSOAP 1.1SOAP

Adapter Engine (J2EE)SAP System, EDI Subsystem

RFCRFC (RFC-XML)RFC

Integration ServerSAP SystemIDocIDocIDoc

Integration Server3rd Party SystemHTTP/SHTTPPlain HTTP

Integration ServerSAP System, Business Partner

HTTP/SXI 2.0, XI 3.0Native XI message protocol

Located inTarget SystemTransport Protocol

Message ProtocolAdapter


Agenda

SAP NetWeaver Exchange Infrastructure

Introduction to XI


Best practices

Exercise

4


Initial Remarks

Software ComponentsIntegration Server, Adapter Engine

Main factors that influence the performanceNumber and size of messages the Integration Server (IS) processes in a given time period

Size of messages in XML because of mapping

Processing synchronous or asynchronous Same or different file formats in and outFor asynchronous processing: acknowledgement required?

Type of adapters usedContent-based routingNumber and type of mappings


Sizing XI – Influencing Factors: BPM

BPM SizingDepends on complexity of Business Process Management (BPM) process

designBPE executes workitems (process steps) to execute actions and hold statesNumber of process steps is a key information about process complexitySizing is based on BPM Patterns Only outgoing messages from Integration Server are counted

for a split scenario count n messages for 1:n split; add BPM Factor nfor a collect scenario count 1 message for n collected messages; add BPM Factor n

5


Sizing XI – Assumptions

AssumptionsXI scenarios do not influence each other – allows to compute resource

consumption based on single scenarios and componentsAsynchronous messages use 2 persist steps in Integration Server part

– if data is persisted more than twice, additional disk space is neededQuality of Service EO and EOIO (async. processing) have similar resource

consumptionEOIO is serialized

J2EE based XI Adapters have a similar resource consumptionContent based routing means evaluation of XPATH expressions (payload

access)One mapping for BPMMapping refers to execution of

XSLT mappings within the XI Mapping Runtimemappings generated by the XI Mapping Toolself-written java code

We only consider “direct communication”. Possible proxy servers tunneling messages to and from the Integration server are not considered.


XI Sizing Different XI Scenarios in the Quick Sizer

Initial sizingBallpark estimate if you are new to XI Number of messages and their size

Predefined scenario Idoc-Adapter including Mapping

Asynchronous processing is standardOptional: Estimate how many messages are triggered by BPM processesIntegration Server incl. Adapter Enging ("XI SERVER")

Advanced sizingCreate your own scenariosTwo servers, one result

XI ServerAdapter Engine (decentral, standalone J2EE)

6


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.


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:

7


Advanced Sizing

Initial throughput and three detailed scenarios:

Result: Graphic:


Sizing Data for Database and Application Server

If you select Software component as the Result level, Quick Sizercalculates SAPS and RAM requirements separately for:

DatabaseApplication

8


Notes for XI Sizing with Quick Sizer

The size of a message is the XML size at the XI server outboundchannel. 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 ofmessages 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.


Very Advanced Sizing Example

Extract of inputto Quick Sizer:

Resultas graphic:

Total:

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:


DB growth rate for long Message Retention Time

For simplification: 100 MB * 40 days = 4 Gig

Aditional to Basis database size

10


XI Sizing Inputs in the Quick Sizer

XI Server

Adapter Engine


XI Sizing Quick Sizer Results

XI Server and Adapter Engine results

11


Result of XI Sizing in the Quick Sizer

CPU in SAPS

Memory in MBFor hourly processingAdditional memory depends on no. of parallel messages and their size

Disk in MBDriven by temporary storage of messagesArchived daily

TipsAverage customer message sizes are between 50-100 KBA typical business process is:

R/3 sends sales order IDocs via RFCMapping Java to convert into flat fileFlat file is saved as XML message in legacy system


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

12


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 XI’s 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

Note: By activating „Fast Indexing“ on Trex the SAPS demand declines significantly by up to ~ 25%. Not possible with other TRex usages like KMC!


TRex Sizing for Indexing XI Messages: Example

Example:100,000 messagesWithin 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.

13


Agenda


Introduction to XI


Best practices

Exercise


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

14


Find Message Size on the Integration Server

To find your message, call transaction SXMB_MONI and chooseRunTime in the Call Adapter folder.

The total message size is displayed, and on the next line the messagepayload size.


Find Message Size in the Runtime Workbench

XI Runtime Workbench -> Performance Monitoring

To display individual message payload sizes, select Overview Individually.

15


“Good” Message Sizes

Throughput example:

Rules of thumb for high throughput:

Avoid small messages (less than 100KB)

Avoid large messages (greater than 2MB)

0,00

2,00

4,00

6,00

8,00

10,00

12,00

30 98 698 2.309 6.915

message size (kb)G

Byt

e / h

our

Measured throughput as Gbytes per hour


SAPS demand for different message sizes

Quicksizing results for:100.000 messages/hour of 4 KB

10.000 messages/hour of 40 KB

1.000 messages/hour of 400 KB

-> Get Larger Messages from Adapters/Applications!Possibilities to check:

Collect single messages of the same type and send together.

Use packages where possible.

“Append Files” and send together

16


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


XI Quicksizing FAQ:

Is there any message size limitation in XI? Yes, 2 Gig. Customer scenario I know: 260 MB, Max size tested: 1 Gig.

But: Always depends on used VM capacities!

Does SAP has pre calculated sizing for Small, Mid and enterprices in general? No. Companies and scenarios are much to different.

Average XI Sizing recommendation by SAP? No recommendation but: Minimum: Laptop, Starting point 2 CPU with 4 Gig Ram and 40Gig Disk.

What are you sizing if you know nothing? Nothing.

Do you size a dev. machine less than a production machine ? Yes, dependent on the number of scenarios and people working in parallel.

17


LINKS:

SDN Weblogs from Susanne Janssen regarding Quick Sizing:Efficient SAP Hardware Sizing: Quick SizerQuick Sizer 2005 - Getting startedInterpreting Quick Sizer Results

Sizing and Benchmarks on the SAP Service Marketplace:

http://service.sap.com/sizing

http://service.sap.com/benchmark

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


Agenda


Introduction to XI


Best practices

Exercise

18


Exercise : 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<xx> with customer number 188213, where <xx> 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


Questions?

Q&A

19


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


Copyright 2006 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, 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 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 Hotlinkszugreifen, 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.

Documents

XI_Sizing