SIZING GUIDELINE

Sizing the SAP Web Dispatcher

SAP NetWeaver 7.1

Released for SAP Customers and Partners

May 2009
 Content

1. SAP Web Dispatcher Overview

2. SAP Web Dispatcher Features
3. "Messages per Second" Estimation
4. Sizing: CPU
5. Sizing: Memory

© SAP 2009 / Page 2

 SAP Web Dispatcher Overview

Configuration: Central Instance

Message
Single Access Server-Based Message
Point: One Server RDBMS
Address:Port
I AS ABAP
C
SAP M AS Java
Web
http://.... Dispatcher Dialog Instance
Client I AS ABAP
C
M AS Java

Session Dialog Instance

Persistence,
Load Balancing I AS ABAP
SSL
C
Support AS Java
M
SSL DMZ
© SAP 2009 / Page 3 Intranet
 SAP Web Dispatcher Features (I)

Supported Protocols
HTTP based protocols (HTTP, HTTPS)

Load Balancing
Client IP address-based
Static round robin
Weighted round robin
Dynamic load balancing

Performance
Optimized, lazy HTTP parser
HTTP proxy cache in Web Dispatcher
File access for static content

Security Features
SSL support for client and server connection
X.509 client certificate forwarding
HTTP log
Reverse invoke (no connections from outside the DMZ)

© SAP 2009 / Page 4

 SAP Web Dispatcher Features (II)

High Availability
MS cluster configuration
Integration into HA cluster software
Auto-restart on UNIX
MS service compatible

Zero Configuration
Retrieve server information from message server, group and URL info from AppServer
-bootstrap option for fast setup
-checkconfig option for configuration check

Monitoring
Web-based monitoring (threads, connections, status, …)
icmon for low-level monitoring

Misc
Logon group concept (app server separation) for Application Server ABAP and Java
Support of virtual hostnames and virtual hosts
User defined error pages
Header manipulation, URL rewriting
URL redirects
Registration in System Landscape Directory (SLD)

© SAP 2009 / Page 5

 Factors That Influence the Performance

The performance and resource consumption of SAP Web Dispatcher are influenced
by the following:
Scenario
No SSL
Termination of SSL
Termination and re-encryption of SSL
Creation of new SSL connections is expensive and can be reduced by persistent
connection (HTTP 1.1) and proper TCP time out
System load is characterized by
Messages per second
Message length (the typical, average message length of SAP applications is 16 Kbyte)
For optimal system configuration of SAP Web Dispatcher, refer to
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/99d142ee2b73e7e10000000a42189b/fr
ameset.htm

© SAP 2009 / Page 6

 How to Estimate the "Messages per Second"
for Your Application Scenario

Size the hardware for SAP Web Dispatcher to cover peak load situations. Use one of
the following approaches to estimate a realistic peak load in messages per second:
User-based sizing: Use if you can estimate or know:
Number of active, concurrent users during peak periods: N
Average think time between 2 successive user interaction steps: ThT
Average number of messages per user interaction step: m
MessagesPerSecond = N * m / ThT
Throughput-based sizing: Use if you can estimate or know:
Peak load duration: T
Number of transactions which are processed within the peak load duration: K
Average number of messages per transaction: n
MessagesPerSecond = K * n / T

The variables “m" and "n" can be customized, modified and personalized with the
SAP application software. For an accurate estimate, we recommend a network traffic
investigation of your application scenario. (How many messages are sent per user
interaction.)

© SAP 2009 / Page 7

 Examples for Estimation of "Messages per
Second"

User-based sizing
In a B2C (Business-to-Consumer) internet sales scenario, each user interaction step requires
an average of 2 messages. At peak time, 10,000 active users are in the system with an
average think time of 20 seconds
=> messages/sec = 10,000 * 2 / 20 = 1,000

Throughput-based sizing
A company with 100,000 employees implements a weekly ESS (Employee Self-Service)
scenario to record working time with 10 messages, for example, 5 user interaction steps with
2 messages. According to IT operation statistics, ca. 60% of all employees will execute the
ESS scenario in the peak time period on Friday afternoon between 15:30 and 16:00
=> messages/sec = 100,000 * 10 * 60% / 1800 = 333

© SAP 2009 / Page 8

 Sizing the SAP Web Dispatcher: CPU

CPU Sizing assumptions

The average message length = 16 Kbyte
For SSL, a new SSL connection must be set up for 10% of the messages
65% CPU utilization

SAPS for n messages per second

100 1000 5000
HTTP 120 1160 5790
HTTPS Termination 300 2900 14500
HTTPS Re-Encryption 350 3480 17500

© SAP 2009 / Page 9

 Sizing the SAP Web Dispatcher: Memory

Communication memory
Recommended configuration
– concurrent_conn = (users * req_per_dialog_step *conn_keepalive_sec)/
(thinktime_per_diastep_sec)
– communication Size (in MB) = (concurrent_conn * mpi/buffer_size)/(1024*1024)
With parameters
– mpi/buffer_size (Default: 64 Kbyte)
– mpi/total_size_MB (Default: 80 – recommended minimum: 500)
End-to-End SSL table
1.8 MB for 10,000 entries
Session table
1.9 MB for 10,000 entries
Static administration tables
Usually very small (90 Kbyte default, few MB for very large system)

© SAP 2009 / Page 10

 Copyright 2009 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.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and
associated logos displayed 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. 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. 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

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.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services
sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten
Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. 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 übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die 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.
Alle Rechte vorbehalten.

© SAP 2009 / Page 11