You are on page 1of 10

Sizing Guide

Sizing SAP
NetWeaver
Knowledge
Management and
Collaboration,
Release 2004s
Released for SAP Customers and Partners

Document Version 1.0, April 2007

Released for SAP Customers and Partners

Copyright 2007 SAP AG. All rights reserved.

contained in this document serves informational purposes


only. National product specifications may vary.

No part of this publication may be reproduced or


transmitted in any form or for any purpose without the

These materials are subject to change without notice.

express permission of SAP AG. The information

These materials are provided by SAP AG and

contained herein may be changed without prior notice.

its affiliated companies ("SAP Group") for informational


purposes only, without representation or warranty of any

Some software products marketed by SAP AG and its

kind, and SAP Group shall not be liable for errors or

distributors contain proprietary software components of

omissions with respect to the materials. The only

other software vendors.

warranties for SAP Group products and services are those


that are set forth in the express warranty statements

Microsoft, Windows, Outlook, and PowerPoint are

accompanying such products and services, if any.

registered trademarks of Microsoft Corporation.

Nothing herein should be construed as constituting an


additional warranty.

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,

Disclaimer

Intelligent Miner, WebSphere, Netfinity, Tivoli, and

Some components of this product are based on Java.

Informix are trademarks or registered trademarks of IBM

Any code change in these components may cause

Corporation in the United States and/or other countries.

unpredictable and severe malfunctions and is therefore


expressively prohibited, as is any decompilation of these

Oracle is a registered trademark of Oracle Corporation.

components.

UNIX, X/Open, OSF/1, and Motif are registered

SAP Library document classification: CUSTOMERS &

trademarks of the Open Group.

PARTNERS

Citrix, ICA, Program Neighborhood, MetaFrame,

Documentation in the SAP Service Marketplace

WinFrame, VideoFrame, and MultiWin are trademarks or

You can find this documentation at the following address:

registered trademarks of Citrix Systems, Inc.

http://service.sap.com/sizing

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

SAP AG

Released for SAP Customers and Partners

TABLE OF CONTENTS

INTRODUCTION......................................................................................................................................... 2
1.1
FUNCTIONS OF SAP KNOWLEDGE MANAGEMENT AND COLLABORATION ............................................... 2
1.1.1
Knowledge Management ................................................................................................................. 2
1.1.2
Collaboration .................................................................................................................................. 3
1.2
ARCHITECTURE OF SAP KNOWLEDGE MANAGEMENT AND COLLABORATION ......................................... 4
1.3
FACTORS THAT INFLUENCE PERFORMANCE ............................................................................................. 5

INITIAL SIZING FOR KNOWLEDGE MANAGEMENT AND COLLABORATION ....................... 6


2.1
ASSUMPTIONS .......................................................................................................................................... 6
2.2
SIZING GUIDELINE ................................................................................................................................... 6
2.2.1
Requirements for CPU and Memory ............................................................................................... 6
2.2.2
Disk Requirements for Document Management and Collaboration ............................................... 7
2.2.3
Frontend Network ........................................................................................................................... 7

MISCELLANEOUS...................................................................................................................................... 8

COMMENTS AND FEEDBACK ................................................................................................................ 8

SAP AG

Sizing SAP KMC - SAP Customers and Partners

1 Introduction
Sizing is the process of translating business requirements into overall hardware requirements, such as
the physical memory, the CPU processing power, and the network capacity needed to implement
Knowledge Management and Collaboration (KMC) on top of SAP NetWeaver Portal.
This document provides guidelines for sizing the load created by KMC on top of the portal and the
database server(s). That is, the net KMC requirements on top of the standard portal usage. The guide
details the factors that influence portal performance and affect the hardware requirements.
The sizing information in this guide is intended as a guideline for initial sizing. It is not absolute
because it cannot include all use patterns and load patterns possible with Knowledge Management
and Collaboration. For more information about sizing TREX, LDAP, and other software used in the
landscape, see the respective sizing guidelines at http://service.sap.com/sizing Sizing General
Sizing Procedures or the Quick Sizer, SAPs online sizing tool, at http://service.sap.com/quicksizing.

1.1

Functions of SAP Knowledge Management and Collaboration

This section provides an overview of the Knowledge Management and Collaboration functions.

1.1.1

Knowledge Management

With its Knowledge Management capabilities, SAP NetWeaver provides a central, role-specific point of
entry to unstructured information from various data sources. This unstructured information can exist in
different formats, such as text documents, presentations, or HTML files. Workers in an organization
can access information from different sources such as file servers, their corporate intranet, or the
World Wide Web. A generic framework integrates these data sources and provides access to the
information contained in them through the portal.
The Knowledge Management capabilities allow you to structure information and make it available to
the correct target audience. You can use the different functions on all content of integrated data
sources as long as the technical prerequisites are met.
Knowledge Management includes the following main functions:

Integration of repositories
Unstructured information is stored in various types of repository, such as file servers or document
management systems. You can use preconfigured repository managers to integrate repositories
and make their content accessible through a central entry point in the portal. Open programming
interfaces (APIs) allow customers and partners to develop repository managers for other storage
systems. You can also store documents in one of KMs own repositories.

Navigation in folders
Portal users can navigate in the folders of all integrated repositories and access the documents
they contain. Access to folders and documents is controlled using permissions. The user interface
for navigating in folders can be configured flexibly and modified to suit various roles. Portal users
can personalize the presentation of the user interface. Open interfaces allow you to extend the
user interface by integrating your own functions in the standard system.

Search
The search function finds documents in all integrated repositories. In the results list, the system
displays only documents for which the current user has read permission. You can also use Web
crawlers to include the content of Web sites in your indexes. This information is then also
available through the search function in your portal.

Taxonomies and classification


A taxonomy is a hierarchical structure of categories in which you classify documents according to
content, organization, or other criteria. Documents that are stored in different repositories can be
included in the same category. Taxonomies allow portal users to navigate in a uniform structure
throughout an organization even if information is stored in heterogeneous storage locations. After
completion of the initial configuration, the system automatically classifies new and changed
documents.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

Knowledge Management services


Knowledge Management services enable functions that you can use on the content of all
connected repositories as long as the technical prerequisites are met. These services include
subscriptions, ratings, public reviews, feedback, and personal notes. Users can also import
documents from external sources into KM repositories using the content exchange service.

Document creation and publishing


Every portal user can create information in the portal, provided he or she has the necessary
permissions. They can upload documents that they created using a PC application directly to a
KM folder. They can also use forms to create information directly in the Web browser. The
publishing process is supported by various functions such as the approval workflow. Users can
assign metadata to documents and other items to make the knowledge available within the
company more usable.

1.1.2

Collaboration

With its Collaboration capabilities, SAP NetWeaver allows communication and collaboration in the
portal. This allows SAP NetWeaver to bring together members of project groups regardless of their
time zone and geographic location. Users can use virtual rooms for common access and organization
of documents, applications, and ideas.
Collaboration includes the following main functions:

Virtual rooms
Based on predefined templates, you can create virtual rooms for collaboration within teams and
project groups. A room allows the members access to shared data and services independent of
their location.

Groupware integration
For collaboration in the portal, you can integrate the e-mail and scheduling services (Microsoft
Exchange, Lotus Domino) used in your company.

Asynchronous collaboration
For asynchronous collaboration, the following functions are available:

Online discussions

Online management of tasks, sessions, and documents

Online entry of feedback, ratings, and comments

Integration of third-party services


You can integrate third-party collaboration services that are already used in your organization, for
e-mail or calender connectivity, as well as Web conferencing and instant messaging.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

1.2 Architecture of SAP Knowledge Management and


Collaboration
The figure below shows the technical Knowledge Management and Collaboration components. Users
access the Knowledge Management and Collaboration functions through the portal.
Portal

Knowledge
Knowledge Management
Management

Collaboration
Collaboration

KM Applications

Room Infrastructure

Navigation

Search

People Centric Components

KM Services
Index
management

Subscription

Asynchronous Tools &


Components

Synchronous Collaboration
Framework

KM Repository Framework
Repository
manager

Repository
manager

Repository
manager

WebDAV

HTTP

File system

Groupware Framework

Search and Classification (TREX)

Figure 1: Components of KMC

The table below describes the technical components in more detail.

KM Technical
Component

Description

Repository framework

The repository framework is the physical storage location for documents. It


provides a range of basic functions for documents and folders. It enables the
integration of documents in a virtual hierarchy and a namespace. The
documents can be stored on different systems (Windows, WebDAV, or
HTTP). Repository managers are used to access these systems. There are
internal repositories and external repositories, depending on the system.

Repository services
(KM services)

The repository services connect individual repositories with services, such


as indexing, subscription, and status management.

Global services (KM


services)

Global services are responsible for many tasks required by all repository
managers of applications. Using the index management service, the SAP
NetWeaver stand-alone engine Search and Classification (TREX) accesses
the content of the connected repositories through the repository framework
to index, classify, and search through it. Global services also allow you to
create subscription, caches, and properties.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

KM Technical
Component

Description

KM applications

You can use KM applications to access documents and administration tools.


You use the Navigation iView to navigate in repositories and folders, find the
documents you need, open them, and edit them with the appropriate
application. In addition, you can use the search to find documents. Functions
such as navigation and search can also be used in virtual rooms.

Search and
Classification (TREX)

The SAP NetWeaver stand-alone engine Search and Classification (TREX)


enables various types of search and classification operations.

People-centric
components

These components provide iViews that can be used in Collaboration and


Knowledge Management applications for the collaboration of portal users
through services. The People Picker provides a standard user interface for
searching for portal users, user groups, and roles. The People Renderer
provides a standard user interface for displaying portal users in applications.
This includes displaying the availability status (using icons), detailed data on
users, and services for collaboration.

Room infrastructure

This component controls the lifecycle of rooms. It is contained in both the


portal layer and the KM layer. The Room Infrastructure offers functions for
editing rooms, such as creating, changing, and deleting them.

Asynchronous tools
and components

This component provides the technical prerequisites for functions that allow
asynchronous collaboration between portal users. This includes online
discussions and online management of tasks and documents, such as
feedback, rating, and comments services.

Synchronous
collaboration
framework

This component provides the technical prerequisites for the integration of


synchronous services from third-party providers, such as WebEx.

Groupware framework

This component allows the integration of e-mail and scheduling services


such as Microsoft Exchange and Lotus Domino.

1.3

Factors That Influence Performance

There are a number of factors that influence the performance of KMC.


Persistency mode: One major influence on performance is the selection of a persistency mode
for the document store. The cheapest in terms of CPU requirements is the file system store
because this saves the complete database processing time and database driver communication.
Repository services. Another factor that impacts performance is the number and type of
repository services selected, such as feedback, rating, and so on. These can have up to 10%
overhead.
Permission access checks. The performance also greatly depends on the organization of
content for minimal permission access checks. We recommend organizing documents with
restricted accesses in separate subfolders and so on. This reduces the number of permission
checks during a search and significantly improves performance.
Frontend network. Because KMC users work a lot with documents of various sorts and sizes,
network traffic is intensive for Knowledge Management and Collaboration and a slow network will
have a significant impact on the end-user experience with regard to performance.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

2 Initial Sizing for Knowledge Management and


Collaboration
2.1

Assumptions

There are as many ways to use Knowledge Management and Collaboration services as there are
customers. Therefore, the sizing procedure is based on the following assumptions, which are derived
from SAPs experience in a number of customer installations.
Data volume and size
Some customers use a low number of virtual rooms to organize a huge amount of content. Other
customers choose a larger number of virtual rooms, which each organize a small amount of
content. With the first approach, operations such as entering a room and browsing content,
especially when there is a range of different permission assignments for the different users,
significantly impact performance. With the second approach, operations such as registering new
rooms, deleting existing rooms, listing rooms, and so on may impact performance and the
entering of a room and browsing content does not significantly impact performance.
For the sizing guideline, we assume the following:

Customers maintain up to 1000 virtual rooms.

In each room, the average number of documents in a folder or subfolders in a folder is 200.

The total number of documents in each room does not exceed 2000.
The size of the documents impacts the performance mainly in the frontend network area because
this is the only factor that slows down the display of the document.

Typical size of documents is considered to be up to 1 MB.


Number of users assigned to each room
Typically, rooms have up to 50 members assigned because this is average for regular project
teams, with only a few exceptions for the corporate rooms to which all employees have access.

2.2

Sizing Guideline

2.2.1

Requirements for CPU and Memory

As stated in the introduction, the scope of this guide is to provide guidelines for the portal and
database used by Knowledge Management and Collaboration. That is, the net KMC requirements on
top of standard portal usage. For more information about sizing TREX, LDAP, and other software used
in the landscape, see the respective sizing guidelines at http://service.sap.com/sizing.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

You can find the numbers for the initial sizing of Knowledge Management and Collaboration in the
table below.

Category

Up to Concurrent
Users
(30 seconds think
time1)

CPU (SAPS2)

Physical Memory
for Portal in GB3

Portal

Database

Small

200

2200

400

Medium

500

5500

1000

10

Large

1000

11,100

1900

20

Extra Large

1000+

2.2.2

Contact hardware vendor or SAP

Disk Requirements for Document Management and Collaboration

In addition to the physical size of the document itself, add 4 KB overhead for each document for its
properties and permission data, which are specific to the SAP implementation.
In the case of virtual rooms, allocate approximately 1 MB for each virtual room on top of the size of the
content in the room for maintenance of the room templates, room permissions, structure, and so on.

2.2.3

Frontend Network

The average throughput in Knowledge Management and Collaboration scenarios for the content
assumptions documented in section 2.1 is approximately 20 KB per request. The throughput also
greatly depends on the size and type of customer content organized on a single browser page. For
more information about sizing the frontend network bandwidth, see the document Frontend Network
Requirements of SAP Solutions at http://service.sap.com/sizing guidelines solutions.

Concurrent users are logged on to the system and perform activities. Think time is the time between
two user interaction steps executed by an individual user, for example, two navigation steps, for which
data is retrieved from the server. 30 seconds think time is that of a medium active user because not all
clicks trigger an interaction with the server.
2

SAPS is a hardware-independent unit used to describe the CPU-related performance characteristic


of a given hardware configuration. For more information about SAPS and their equivalent in hardware
performance, see http://sap.com/benchmark SAPS.

For more information about sizing the physical memory needed for the database, ask your database
provider.

SAP AG

Sizing SAP KMC - SAP Customers and Partners

3 Miscellaneous
There is some additional information available.
Performance, Benchmarks, and Sizing

Performance
Benchmarks
General sizing information
Quick Sizer

http://service.sap.com/performance
http://sap.com/benchmark
http://service.sap.com/sizing
http://service.sap.com/quicksizing

Master Guide and Technical Infrastructure Guide


Read the master guide to determine the installable units and SAP systems required for your IT
scenario and the installation sequence for them. Use the technical infrastructure guide to determine
the best distribution option for your system landscape, taking into account performance, robustness,
and scalability.
You can find both guides at http://service.sap.com/installnw2004s

How-To Guides
To achieve optimum performance, you should regularly take into account the latest performancetuning recommendations, which are published in SAP Note 739829 and in the Performance how-to
guide at https://www.sdn.sap.com/irj/sdn/howtoguides User Productivity Enablement How to
Tune the Performance of Knowledge Management (KM).

4 Comments and Feedback


Both are very welcome; please send them to Sylvia Delcheva at Sylvia.Delcheva@sap.com.

SAP AG

Sizing SAP KMC - SAP Customers and Partners