SIZING GUIDE

Sizing Enterprise Services Repository, Version 7.10

Released for SAP Customers and Partners

Document Version 1.0, April 2008

 Copyright 2008 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 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. 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 Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. SAP Library document classification: CUSTOMERS & PARTNERS Documentation in the SAP Service Marketplace You can find this documentation at the following address:
http://service.sap.com/sizing

SAP AG

Released for SAP Customers and Partners

TABLE OF CONTENTS

1 1.1 1.2 2 3 3.1 3.2 4 5

INTRODUCTION ................................................................................................................................. 2 FUNCTIONS OF ESR ............................................................................................................................. 2 ARCHITECTURE OF ESR ....................................................................................................................... 3 SIZING FUNDAMENTALS AND TERMINOLOGY.......................................................................... 5 INITIAL SIZING FOR ESR ................................................................................................................. 6 ASSUMPTIONS ..................................................................................................................................... 6 SIZING GUIDELINE ............................................................................................................................... 6 MISCELLANEOUS .............................................................................................................................. 6 COMMENTS AND FEEDBACK.......................................................................................................... 6

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners

1 Introduction
The Enterprise Services Repository is the central repository where enterprise service definitions are modeled, stored and maintained. It supports SAP's concept of building services based on the process component modeling methodology. ESR provides an integrated toolset and repository for the governed definition of SOA assets (such as service interfaces and process component models). It thus provides transparency into the business semantics exposed via enterprise services, for designers and developers of solutions on top of platform applications. It is open to managing non-SAP services (provided by customers and ISVs) in a customer landscape and thus provides the single source of truth of a companys SOA enabled IT Landscape. The ES Repository and Registry support widely adopted open standards including Web Services and UDDI. The ES Repository supports SAP-defined Global Data Types based on the Core Component Technical Specification standards.

1.1

Functions of ESR

The Enterprise Services Repository supports four key usage scenarios. Service Provisioning The Enterprise Services Repository provides unparalleled support for modeling services. Users can define all artifacts from Service Interfaces to individual Data Types and reuse artifacts at all levels. The ESR is delivered with pre-defined Global Data Types, basic building blocks created out of SAPs methodology, which provide a foundation for defining your services. Process Visibility In addition to service artifacts, ESR supports definition of high level models such as Process Component models and Scenario models that help contextualize the services that are delivered. For instance, the enterprise services delivered with SAP are delivered with these high level models that help a user drill down to services from a high level overview and do extensive gap analysis. Process Integration ESR provides support for classical A2A and B2B integration scenarios. This includes support for defining message mapping and executable business processes in an interactive graphical modeling environment. Consumption The Services Registry provides support to publishing services, discovery services and management services. Users can search services using keyword searches and based on classification. The Services Registry is pre-delivered with industry classifications which can be used to classify services. In addition, users can extend the classification meta model based on their needs. Across all these scenarios, ESR provides support for Design Time Governance, Unified Lifecycle Management and support for widely accepted standards.

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners

1.2

Architecture of ESR

The below figure depicts the high level architecture of ESR. ESR consists of 1. A server component which is based on the SAP NetWeaver Application Server Java (AS Java). 2. A client component which is based on Java Swing and is accessed via Java Web Start. The communication between the client and the server is done using Enterprise Java Beans. ESR is primarily a design time environment and provides the capabilities of state-of-the-art technology, such as versioning, change list management, and authorization support.

Generic Data

Type Specific Data

Figure 1: Enterprise Services Repository Architecture

Both the server and the client have respective frameworks which provide common functionality as shown in the figure above. It includes functionality such as versioning, locking, internationalization etc. As an example the functionality of adding an object into a change list when edited is provided by the framework.

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners

Each object type plugs into the framework (both on the client and the server) to provide object typespecific functionality. So different object types, such as Business Objects, Service Interfaces, Data Types, etc. have editors and the corresponding consistency checks when they are activated. On the client side, examples of object type-specific functionality are: a. Type specific editors b. Type specific context menus On server side, examples of object type specific functionality are: a. Serialization for transport b. Activation checks c. Persistence Data is persisted in a way that the generic data (handled by the server framework) is stored separately and the object type-specific data is stored separately. Among other things the generic data also consists of versioning information. The type-specific data in turn stores type-specific data for all historic versions as well.

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners

Sizing Fundamentals and Terminology

SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide, we assume that you are familiar with sizing fundamentals. For more information see http://service.sap.com/sizing Sizing General Sizing Procedures. This section explains the most important sizing terms, as these terms are used extensively in this document.

Sizing
Sizing means determining the hardware requirements of an SAP application, such as the network bandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components and the data load they put on the server must be taken into account.

Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks and scalability tests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizing recommendations to customers by placing a substantial load upon a system during the testing of new hardware, system software components, and relational database management systems (RDBMS). All performance data relevant to the system, user, and business applications are monitored during a benchmark run and can be used to compare platforms.

SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed order line items per hour. (For more information about SAPS, see http://www.sap.com/benchmark SAPS).

Initial Sizing
Initial sizing refers to the sizing approach that provides statements about platform-independent requirements of the hardware resources necessary for representative, standard delivery of SAP applications. The initial sizing guidelines assume optimal system parameter settings, standard business scenarios, and so on.

Expert Sizing
This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more detail on the sizing result. The main objective is to determine the resource consumption of customized content and applications (not SAP standard delivery) by comprehensive measurements. For more information, see http://service.sap.com/sizing Sizing Guidelines General Sizing Expert Sizing. Procedures

Configuration and System Landscaping

Hardware resource and optimal system configuration greatly depend on the requirements of the customer-specific project. This includes the implementation of distribution, security, and high availability solutions by different approaches using various third-party tools. In the case of high availability through redundant resources, for example, the final resource requirements must be adjusted accordingly. There are some "best practices" which may be valid for a specific combination of operating system and database. To provide guidance, SAP created the NetWeaver configuration guides (http://service.sap.com/instguides SAP NetWeaver).

Hardware Minimum Requirements

Unless otherwise indicated, the sizing guidelines specify the net requirements of the business application. The minimum requirements for installing an empty system are specified in the respective implementation guides (http://service.sap.com/instguides, in the section for hardware and software requirements). The same applies for front-end PC minimum and optimal requirements.

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners

3 Initial Sizing for ESR

3.1 Assumptions
The scenario considered to calculate the sizing details is based on the most common operations performed in Enterprise Services Repository. First you have the transactions regarding the object lifecycle like: Read objects Open the objects for edit Edit the objects Save the objects Activate the objects In addition you have some surrounding transactions like: Expand the navigation tree from the root to the object (navigate to object) Perform a cross reference check (check affected users) Search for an object with given name (F4 help)

3.2

Sizing Guideline

The table below indicates the sizing details for Enterprise Services Repository. Category Up to Concurrent Users (Think Time: 30 sec.) 50 100 500 1000 CPU (SAPS) Application Server 350 700 3500 6950 Database Physical Memory in GB

Small Medium Large Extra Large

40 80 400 800

1 3 13 26

FOR MORE THAN 10,000 SAPS CONTACT SAP HARDWARE VENDOR Minimal configuration to install ESR as a standalone system: 2-processor 2,4 GHZ which corresponds to a 2,500 SAPS machine 70 GB disk space 8 GB memory

4 Miscellaneous
Please note that this sizing information is our recommendation; a result observed at a certain environment.

5 Comments and Feedback

Both comments and feedback are very welcome. Please create a customer message with the following CSS component: BC-XI-IBD.

SAP AG

Sizing SAP Enterprise Services Repository - SAP Customers and Partners