- optimize performance in your km implementation[1]. with invaluable tips for trex sizing, scalin

8/7/2019 - Optimize performance in your KM implementation[1]. with invaluable tips for TREX sizing, scalin

http://slidepdf.com/reader/full/-optimize-performance-in-your-km-implementation1-with-invaluable-tips-for 1/79

perfo rm anc e in your K Mimp lementa t ion

Nicholas HolshouserSAP

Opt imize

with invaluable tips for TREX sizing,

scaling, and administration



Practical Tips and Tricks

TREX Configuration and ScalabilityAdministration, Monitoring, and Analysis

KM Performance and Optimization

Planning and Implementing Knowledge Management(KM) and TREX

Infrastructure OverviewWhat We’ll Cover …



©SAP AG 2005, 3

Objec t ive

Today’s discussion will focus on important concepts inperformance tuning and system management

Specific tuning tips are difficult to generalize; every

implementation is unique

The most important thing to take away from this presentation isan understanding of the foundations of tuning and optimizationand the awareness that tuning and optimization are processes,

not activities

You will periodically see this graphic

It is used to highlight a tip, trick, or useful take-away



©SAP AG 2005, 4

Tunab le In f ras t ruc t u re

We will review the infrastructure with a focus on the aspects thatare important for performance and tuning

Again I will stress – think about the elements of the infrastructurein the context of how they use system resources and how we canmodify (or tune) their configuration such that the resourceutilization is optimal



©SAP AG 2005, 6

Web App lic a t ion Server – J 2EE

Web Application Server – J2EE Perspective

Central Instance

J2EE

Dispatcher

SDM

IGS

Server Processes

J2EE SCHEMA

SAPCCMSRSAPOSCOL

Central ServicesInstance (SCS)

Message Server

Enqueue Server

Dispatcher consumes

memory and CPU, ownsthe network connections

Server consumesmemory and CPU

SDM consumes

memory and CPU

Message Server andEnqueue server are OS-

level processes



©SAP AG 2005, 7

Web App l ic at ion Server – ABAP/J 2EE ADD-IN

Web Application Server – ABAP-J2EE ADD-IN Perspective

SAPCCMSRSAPOSCOL

ABAP SCHEMA

J2EE SCHEMA

Central Instance

ABAP

Dispatcher

Gateway

Enqueue Server

Message Server

SAP ccm4x

Work Processes

J2EE

Dispatcher

SDM

Server Processes

IGS

ICM

Central ServicesInstance (SCS)

Message Server

Enqueue Server

ICM manages clientconnectivity



©SAP AG 2005, 8

Web Appl ic a t ion Server – J 2EE Engine

Common Infrastructure for bothServer and Dispatcher nodes ofthe J2EE Engine

The SAP Enterprise Portal is aJ2EE application deployed ontothe servlet engine (servlet_jspservice) of the server node

Everything is inside theJ2EE containers



©SAP AG 2005, 9

Ent erpr ise Por t a l – Request Flow

The framework is reallythe engine and all of itsservices



©SAP AG 2005, 10

Por t a l Fram ew ork

How the framework is implementedand used determines how theenvironment performs



©SAP AG 2005, 11

Ent erpr ise Por t a l



©SAP AG 2005, 12

K M

Security impacts overall performance

Crawlers impact network performance

KM uses CPU andmemory, performanceimpacts user experience



©SAP AG 2005, 13

TREX

Network protocolrequirements

CPU and Memory

Key componentfor HA capabilities

CPU and Memoryintensive, optimize the I/Ousing shared storage




TREX Configuration and Scalability

Administration, Monitoring, and Analysis


Planning and Implementing KM and TREXWhat We’ll Cover…

Infrastructure Overview



©SAP AG 2005, 15

In f rast ruc t ure Plann ing Considerat ions

Security Requirements and Constraints – requirements such asSSL and network layout

Hardware, Software, Support Requirements – physical, software

and support infrastructure should be carefully considered fortheir performance impacts

Network and Storage Requirements – don’t expect performancebeyond your budget, but don’t think all performance is expensive.

Making the right choices requires considering how to balanceperformance and costs

Integrating applications is only the beginning … performance is also significantly impacted by how well you integrate the people and their connection to the landscape



©SAP AG 2005, 16

Secur i ty

SAP Security

http://service.sap.com/security

SAP Security Roadmap

https://websmp206.sap-ag.de/

~sapidb/011000358700001321182003E/HOME.HTM



©SAP AG 2005, 17

Hardw are, Sof t w are, Suppor t

SAP NetWeaver ’04 Installationsand Upgrades on the ServiceMarketplace

http://service.sap.com/instguidesNW04



©SAP AG 2005, 18

Prot oco ls and Net w ork s

SAP Technical Infrastructure

http://service.sap.com/network

Technical Guides are available for Network Integration of SAP

Servers, TCP/IP Ports used by SAP Applications, and TechnicalInfrastructure of SAPGUIs



©SAP AG 2005, 19

Imp lem ent ing fo r Per fo rmanc e

Planning the implementation is only the beginning...

You need a performance mind-set to implement a high-performinglandscape

The key elements are:

Sizing

Prototyping

Test and Validation



©SAP AG 2005, 20

Syst em s Engineer ing and Sizing

Systems Engineering cannot begin without detailed requirementsregarding system capacity, security constraints, availability, andperformance

Systems engineering reacts to the requirements but is proactivein its recommendations – providing an architecture that can scaleto future requirements, adapting the security requirements andintegrating them into an established network infrastructure, andensuring processes and capabilities that align with availability

requirements

Apply your knowledge of existing systems



©SAP AG 2005, 21

Proto typ ing

Prototyping key aspects of your implementation providessignificant benefits at very early stages of the project lifecycle

A well-designed prototype can point out opportunities for costsavings in infrastructure, support, development, and projecttimelines

Prototyping is an excellent way to bring in new technologies andintroduce them to your IT and business communities

Get early feedback and buy-in from your key audiences!



©SAP AG 2005, 22

Test ing and Val idat ion

Testing and Validation are critical activities

We test to gather data about the system and to enable analysis ofsystem behavior

Validation includes not only functional (does it work) aspects, butalso performance and sizing aspects

Having designed an infrastructure, we can validate the design

(and thus provide confidence regarding future systemsengineering activities) as it relates to performance and scalability

These activities must be integrated into routine operations



©SAP AG 2005, 23

St ar t w i t h the Mast er Gu ides

SAP NetWeaver provides important information about theinstallation sequence and the components to be installed

It links to all other documents that are required for theimplementation of a specific scenario

The Master Guides are the starting point for all SAP NetWeaver

implementations



©SAP AG 2005, 24

Review t he Planning and Operat ions Guides

The planning guides provide a scenario-based overview of theinstallation process. They include detailed information on systemrequirements as well as comprehensive technical architecturedetails

Operations Guides are intended to provide an overview of basicoperations activities and how-to information

There are operations guides available for patching and upgrading,

SLD configuration, security, and other topics



©SAP AG 2005, 25

Unders t and SAP Sizing






KM Performance and OptimizationWhat We’ll Cover …

Planning and Implementing KM and TREX




©SAP AG 2005, 28

K M in Det a i l – Per formanc e Perspect ives

KM comprises both Content Management (CM) and Search andClassification (TREX)

As an integrated solution, the Content Management configurationis based on technical components of the portal infrastructure

KM performance cannot be better than the underlying portalperformance. You must understand the foundation componentsrunning underneath KM in order to optimize the performance



©SAP AG 2005, 29

Components rely on implementations of Web Application Server andSAP Enterprise Portal capabilities, which in turn, rely on underlyingphysical performance factors, i.e., CPU, memory, and I/O

Crawlers consume network resources and can load other internalservers during their operation. They also use underlying Enterprise

Portal services

Searching and indexing consumes resources across a variety of systemsin the landscape

K M in Det a i l – Per formanc e Perspect ives (cont . )

P f P i



©SAP AG 2005, 30

Availability is a critical performance perspective

Configuration of components such as TREX for improved availability,as well as regular monitoring of status impacts availability

Ultimately your KM performance resolves to the capacity and performanceof the underlying Enterprise Portal and Web Application Server

K M in Det a i l – Per formanc e Perspect ives (cont . )

P t i P f



©SAP AG 2005, 31

Perspec t ives on Per formanc e

KM Monitoring Tools

The Enterprise Portal interface is the most commonly usedperspective. The CCMS perspective should not be overlooked

What are the key monitoring aspects? Availability, Configuration, System Resource Utilization

CCMS provides all perspectives critical for system operation

The Enterprise Portal has a complete management andconfiguration perspective

T i P t i



©SAP AG 2005, 32

Trac ing Perspec t ive

Activity – monitoring a flow of actions

Component – monitoring a component across all of its activities

SQL – sql call tracing which can be filtered by session, use,

component, etc.

User – tracing a user across all components and activities

KM is a collection of actions across multiple components.Tracing is a valuable tool for identifying and analyzing problems because it can span multiple contexts

Opt im i a t ion Proc ess



©SAP AG 2005, 33

Opt im izat ion Proc ess

Lather, Rinse, Repeat …

Optimization is the process of continued (iterative) tuning whichyields a positive result

We test to gather data and record the state of a system withpredefined/known inputs

We analyze the data to discern problem areas

We record and archive the data so it is available for futurereference and correlation

We provide tuning recommendations and retest to validate that

they are positive changes

Cont inuous Improvement of Operat ions



©SAP AG 2005, 34

Cont inuous Improvement o f Operat ions

There are several keys to continuous improvement ofcomputer operations

Gather performance data regularly and archive the data for

time-based (historical) analysis Understand the system dynamics that drive performance

(infrastructure and architecture or the application)

Maintain a consistent testing framework to ensure historical datagathered during testing can be correlated over time

Maintain a consistent data gathering and archiving framework toensure that historical operations data can be correlated over time

Tips for Suc c ess



©SAP AG 2005, 35

Tips for Suc c ess

Implementation milestones should include technical aspects

Timelines should ultimately be driven by technical considerations – meaning implementation is driven by readiness, not eagerness



Practical Tips and TricksTREX Configuration and Scalability

Administration, Monitoring, and AnalysisWhat We’ll Cover …




New Feat ures and Capabi l i t ies



©SAP AG 2005, 37


Centralized Monitoring Aggregating the monitoring perspectives for all

integrated applications

CCMS and Central System Monitoring (CEN) Implementing a common infrastructure for data reporting as

well as centralized physical infrastructure and processes

TREX Admin and Monitoring Integration of a common interface for TREX configuration and

monitoring, and improved extension of monitoringcapabilities to the CEN

Moni t o r ing In f ras t ruc t u re – Aggregat ion



©SAP AG 2005, 38

Moni t o r ing In f ras t ruc t u re Aggregat ion

Monit o r ing K M – CEN c apab i l i t ies



©SAP AG 2005, 39

Monit o r ing K M CEN c apab i l i t ies

System Status, Configuration,Alerting

Availability and GRMG

Por ta l – K M Conf igura t ion



©SAP AG 2005, 40

Por ta l K M Conf igura t ion

Repor t ing for Paramet ers and Vers ions



©SAP AG 2005, 41

p g

Copy the file TrexCCMS.dll (Windows) or TrexCCMS.so/TrexCCMS.sl (UNIX) from the directory<TREX_directory> to the SAPCCMSR directory:

Windows: \\<host>\usr\sap\prfclog\sapccmsr

UNIX: /usr/sap/tmp/sapccmsr

Edit the file TrexCCMS.ini in the directory /<TREX_directory>/CCMS.In the section [INSTALLATION] change the entry directories= to the directory /usr/sap/trex_02

Change the SAPCCMSR configuration file sapccmsr.ini in the SAPCCMSR directory asfollows:

Windows: \\<host>\usr\sap\prfclog\sapccmsr

UNIX: /usr/sap/tmp/sapccmsr

Add the entry "PlugIn"

PlugIn /usr/sap/tmp/sapccmsr/TrexCCMS.so

Restart the SAPCCMSR service.sapccmsr -stop (stops the service)

sapccmsr -DCCMS (starts the service)

http://help.sap.com/saphelp_nw04/helpdata/en/40/a9a1b5258d66f9e10000000a114cbd/content.htm

Look for the demo on SDN!

Conf igurat ion Moni t or ing



©SAP AG 2005, 42

g g

Start transaction RZ20

The screen containing the CCMS Monitor Sets appears

Expand the node SAP CCMS Monitors for Optional Components

Double-click on the entry TREX

A node tree with the entries TREX Server Configuration, TREX ServerHeartbeat, and TREX Log files is displayed

Expand the TREX Server Configuration node

A node tree containing the available TREX hosts is displayed

If you expand the node of one of the TREX hosts, a node tree with the entriesGlobal, Index Server, Queue Server, Preprocessor Server, Name Server, and

Web Server is displayed

If you expand these nodes, you can view information on the TREX

SAP_RETRIEVAL_PATH, TREX version, and TREX configuration files


Moni t or ing Log Fi les – Proc edure for t he Conf igurat ion



©SAP AG 2005, 43

g g g

Edit every */*logmon.ini file in the <TREX_directory>/CCMSdirectory:Daemon_logmon.iniIndexServer_logmon.iniNameServer_logmon.iniPreprocessor_logmon.iniQueueServer_logmon.iniWebServer_logmon.ini Change the parameter for the area DIRECTORY= to the directory

<TREX-directory>/trace in every */*logmon.ini file.Copy the configuration files from <TREX_directory>/CCMS/ to thefollowing places:Windows: \\<host>\usr\sap\prfclog\logmon\

UNIX: /usr/sap/tmp/logmon/

http://help.sap.com/saphelp_nw04/helpdata/en/40/a9a1eb258d66f9e10000000a114cbd/content.htm


Moni t or ing Log Fi les – Proc edure for Moni tor ing



©SAP AG 2005, 44

Procedure for Monitoring...Start transaction RZ20The screen containing the CCMS Monitor Sets appearsExpand the node SAP CCMS Technical Expert Monitors Double-click on the entry System/All Monitoring Segments/All Monitoring Contexts A list of entries for various hosts (SAP_CCMS_<hostname>) that

are monitored by the CCMS monitor appearsChoose the node of your host (for example, SAP_CCMS_p74368)and expand itA list of available TREX trace files appears

Choose Open Alerts The open alerts are displayed. Click on an entry for an open alertin order to display detailed information


Moni t or ing Proc esses – Proc edure for the Conf igurat ion



©SAP AG 2005, 45

Go to the following directory:Windows: <TREX_directory>\CCMS\W2KUNIX: <TREX_directory>/CCMSCopy the file dev_proc, which is located in the SAPOSCOLdirectory.Windows: \\<host>\usr\sap\prfclog

UNIX /usr/sap/tmpRestart SAPOSCOL.

Enter the following commands in a prompt to do this:saposcol - k (stops (kills) SAPOSCOL)

saposcol - l (starts SAPOSCOL)

http://help.sap.com/saphelp_nw04/helpdata/en/40/a71e2f0f0c66fbe10000000a114cbd/content.htm


Moni t or ing Proc esses – Proc edure for Moni t or ing



©SAP AG 2005, 46

Start transaction RZ20The screen containing the CCMS Monitor Sets appearsExpand the node SAP CCMS Technical Expert Monitors Double-click on the entry System/All Monitoring Segments/All Monitoring Contexts

A list of entries for various hosts (SAP_CCMS_<hostname>) thatare monitored by the CCMS monitor appearsChoose the node of your host (for example, SAP_CCMS_p74368)and expand it

Choose the node <hostname> and expand itChoose Operating System → Monitored Processes A list of currently active processes is displayedExpand a node to see more detailed information


Moni t or ing TREX



©SAP AG 2005, 47

TREX Administrator

Queues

Indexes

Preprocessors

Landscape

Name Server

Web Server

Moni t or ing Queues



©SAP AG 2005, 48

Moni t or ing Index es



©SAP AG 2005, 49

Moni t or ing Preprocc esors



©SAP AG 2005, 50

Monit o r ing the Landscape – Perspec t ives



©SAP AG 2005, 51

Por t a l Perspect ive



©SAP AG 2005, 52

ABAP Perspec t ive



©SAP AG 2005, 53

AvailabilityMonitoring




TREX Configuration and ScalabilityWhat We’ll Cover …








©SAP AG 2005, 55

Improved Scalability and HA Capabilities Master/Slave Concept

Master/Backup Concept

Shared Slaves

Specialized Hosts (Task Oriented)

Central Administration Tool – TREXADMIN

Integration with R/3 and CCMS

Optimized Indexing and Delta Index Integration

TREX and K M Per form anc e



©SAP AG 2005, 56

KM performance is impacted by TREX performance to the extentthat KM utilizes TREX services

TREX performance is typically considered separate from KMperformance with respect to physical infrastructure as it uses

dedicated hardware

You must consider both with respect to the whole system

You must consider them together when you consider the user

experience or perspective

You must often consider them separately with respect to tuningfor optimal performance



New : Shared Slaves



©SAP AG 2005, 58

Filer

QueueServerMaster

QueueServerMaster

RFC

Server

RFC

Server

RFC

Server

WebServerWeb

ServerWeb

Server

PreprocessorPreprocessorPreprocessor

Index ServerBackup

Index ServerBackup

Index ServerMaster

SETM AE

Index ServerMaster

Index ServerMaster

Index ServerSlave

SETM AE

Index ServerCohort

Index ServerCohort

Index ServerSlave

SETM AE

Index ServerCohort

Index ServerCohort

Index ServerSlave

SETM AE

NameServerMaster

NameServerMaster

Name

ServerMaster

Filer

Queue

ServerMaster

Filer

If using a file server (SAN/NAS),all slaves can share a singlecopy of the read-only index



New : Spec ia l ized Host s



©SAP AG 2005, 60

Index Server

SETM AE

WebSvr.

RFCSvr.

NameServer

Index Server

SETM AE

Web

Svr.

RFC

Svr.

NameServer

Name

ServerBackup

Queue

ServerBackup

Index ServerBackup

SETM AE

Preprocessor

WebSvr.

RFCSvr.

Preprocessor

Index ServerMaster

Name

ServerMaster

Queue

ServerMaster

SETM AE

WebSvr.

RFCSvr.

Standard + High availability + Complex docs + Replication for Scalability

Indexing and Searching Searching

Preprocessor

Preprocessor

Preprocessor

Preprocessor

NameServer

Preprocessor

Index ServerMaster

NameServer

Master

QueueServerMaster

SETM AE

WebSvr.

RFCSvr.

NameServer

Backup

QueueServerBackup

Index ServerBackup

SETM AE

Preprocessor

WebSvr.

RFCSvr.

Index Server

SETM AE

WebSvr.

RFCSvr.

NameServer

Multiple hosts can havedifferent roles

New : Log ic a l Index



©SAP AG 2005, 61

MasterNameServer

Logical Index Server

NameServer

Host

Physical Index Server

SETM AE

NameServer

Host


SETM AE

NameServer

Host


SETM AE

NameServer

Host

Index Part 1 Index Part 2 Index Part 3

Index Administration

Index Metadata

Document keys are

hashed (mod n) in

logical IS for splitinto n index parts,or distributed bylanguage

Benef i ts :

Overcome 2 GB index limit Good load balancing

Rest r ic t ion:

No text mining

New : Fast Index Updat e



©SAP AG 2005, 62

Index Server

Index Index Index

∆ ∆ ∆

Benef i ts :

Smaller files updated

Faster replication

Search requests Index updates

TM RE AE

Merge deltaindexes asmanual orscheduled

background job

TREX for High Avai lab i l i t y and Per form anc e



©SAP AG 2005, 63

High Availability is achieved by using Master and Backup servers

Performance is enhanced by using a distributed configuration toprovide for load distribution to multiple hosts using Master andSlave servers

Master Server – primary for server for a task (index, search,naming, queue, etc.)

Slave Server – provides for load distribution of tasks

(search, naming)

Backup Server – provides for improved availability in case offailure of Master Server (index, naming, queue, etc.)



TREX – Dis t r ibuted Syst em Conf igurat ions



©SAP AG 2005, 65

The server component is based on a flexible architecture thatsupports a distributed installation

A distributed system has the following advantages:

• Load balancing You can distribute the search and indexing load among several hosts

• High availability

You can make searching and indexing highly available

Per formance AND High Ava i lab i l i t y



©SAP AG 2005, 66

PerformanceDistributed configuration allows for balanced loading acrossmultiple hosts

Logical Indexes improve search speed

Improved Delta Indexing reduces processing time andreplication time

Availability

Distributed configuration improves availability by introducingbackup hosts for the masters and multiple slave hosts for

processing searches.

TREX Sc alabi l i t y



Practical Tips and TricksWhat We’ll Cover …



KM Performance and OptimizationPlanning and Implementing KM and TREX


The T ip J ar



©SAP AG 2005, 70

Remember these tips in today’s

presentation ...

Slide 15 – Integrating includes both what and who

Slide 21 – Get early feedback and buy-in from your key audiences!

Slide 23 – The Master Guides are the starting point for all

SAP NetWeaver implementations

Slide 32 – The tracing perspective

Slide 35 – Tips for success

Slide 55 – Improved Scalability and HA Capabilities

KISS is still a good idea

7 K ey Po in ts t o Tak e Hom e



©SAP AG 2005, 71

TREX and KM are improved in both features and functions

TREX can scale out and grow with your needs

KM uses system resources to run the application components

such as TREX and Crawling

KM drives system resource utilization by providing end-userservices such as repository access and workflow

KM is built on the services of the J2EE and Enterprise Portal

Monitoring and analysis of performance data over time is acritical component of optimization

Use the new capabilities offered with improved CCMS integration

Resources



©SAP AG 2005, 72

Publ ic Web:www.sap.com

SAP Developer Network: www.sdn.sap.com

SAP Customer Services Network: www.sap.com/services/

Relat ed SAP Educ at ion Tra in ing Opport uni t ies

www.sap.com/education/

Resourc es (c ont .)



©SAP AG 2005, 73

Relat ed Work shops/Lec t ures f rom SAP Tec hEd 2004ABAP353 Quick-Start on Performance Analysis

CI202 Performance and Scalability of SAP Business Solutions

JAVA201 Troubleshooting on the SAP Web AS for Java Developers

LCM151 Initial Setup of CCMS Monitoring InfrastructureLCM201 Software Lifecycle Management by SAP - An OverviewLCM204 Troubleshooting for Administrators: Problem Detection and Analysis for SAP

Web AS Java

LCM253 Monitoring Infrastructure for SAP Web Application Server Java: Setup and

UsageLCM255 SAP NetWeaver Availability Monitoring and Reporting with CCMS and BI

NW101 Introduction to SAP NetWeaver as an Integration Platform â€“ Across ITLandscapes

NW204 Performance Analysis and Tuning of SAP NetWeaver




©SAP AG 2005, 74

Relat ed Cont ent From SDN

http:/ /sdn.sap.com

Webina rs – https://www.sdn.sap.com/sdn/events.sdn?page=sdn_webinars.htm

SAP Web AS 6.40 Perform anc e Analy sis

Troubleshoot ing and Test ing Techniques

How To Analyze Perform anc e Problem s (EP6SP2)




©SAP AG 2005, 75

Relat ed Cont ent From SMP

http:/ /service.sap.com/NW04 al ias Docum enta t ion l ink

Mast er Guide – SAP Net Weaver ’04 (Plannin g)

Sec ur i t y Guide – SAP NetWeaver (Planning)

Tec hnic al Inf rastruc t ure Guide for the Ent erpr ise Por t a l (Planning)

Perform anc e Tuning Guide – SAP J 2EE Engine (Operat ions)

Suppor t abi l i t y Set up Guide for SAP Net Weaver ’04 (Operat ions)




©SAP AG 2005, 76

Service Marketplace – Notes

697949 TREX 6.1 Solution Management / Monitoring TREX

704349 Activating the CCMS monitoring for TREX

704170 Installation, configuration, availability dsrlib

701385 SAP J2EE Engine 6.30, 6.40 Release Information

710663 Central note for SAP J2EE Engine 630/640 bootstrap process

709140 Recommended JDK and VM Settings for the WebAS630/640 SP4

723909 Java VM settings for EP6 on J2EE 6.30/6.40

710146 How to change J2EE Engine JVM Settings

764417 Troubleshooting guide for 6.40710154 How to create a thread dump for the J2EE Engine 6.30

742395 Analyzing High CPU usage by the J2EE Engine

724719 How to enable HTTP tracing in SAP J2EE Engine 6.30/6.40

719778 Troubleshooting for dbpool service

Quest ions?



©SAP AG 2005, 77

Q& ANicholas Holshouser

SAP NetWeaverTM Foundation RIGSAP Labs, LLC

[email protected]

For More Inform at ion: Ac c ess t he SAP Developer N etw o rk – w w w .sdn .sap .c om

The central hub for the SAP technologycommunity



©SAP AG 2005, 78

community

Everyone can connect, contribute, andcollaborate – consultants, administratorsand developers

Focus around SAP NetWeaver and SAPxApps

High quality of technical resources

Articles, how-to guides, weblogs,collaborative areas, discussion forums,downloads, toolkits, and code-samples

A collaboration platform, not aone-way street

SAP experts from customers, partnersand SAP

SDN is powered by SAP NetWeaver™ Built on the SAP Enterprise Portal

Featuring collaboration capabilities of SAPKnowledge Management

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Copyr i ght 2005 SAP AG. Al l Right s Reser ved



©SAP AG 2005, 79

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware 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 registeredtrademarks 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 hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries 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 affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Groupshall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products andservices 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.

- optimize performance in your km implementation[1]. with invaluable tips for trex sizing, scalin

Documents