Fine Tuning EP60 SP2 Performance

8/7/2019 Fine Tuning EP60 SP2 Performance

1/24

How to

Fine-Tune Performance ofEnterprise Portal 6.0

Enterprise Portal 6.0

Public

Applicable Releases: EP 6.0 SP2

January 2004

.


2/24

Table of Contents1 Introduction .................................................................................................................................... 22

Tuning the Operating System.......................................................................................................3

2.1General Requirements ..............................................................................................................32.2Solaris 8: Tuning TCP/IP Connection Handling ........................................................................3

3 Tuning the Java Virtual Machine..................................................................................................43.1Related Information on JVM settings ........................................................................................43.2Configuring JVM settings for SAP J2EE Engine .......................................................................43.3Using JIT Server Compiler ........................................................................................................53.4Configuring the Heap Size and Garbage Collection Properties................................................ 5

3.4.1 The JVM Garbage Collection (GC) Mechanism ...........................................................53.4.2 Monitoring Garbage Collection .....................................................................................6

3.5JVM Settings for the SAP J2EE Engine With the Portal ...........................................................74 Configuring SAP J2EE Engine Cluster 6.20.............................................................................. 10

4.1Thread Manager Settings........................................................................................................124.2Adjusting SAP J2EE Engine Log Files ....................................................................................12

4.2.1 SAP J2EE Engine system.log and default.trc .............................................................124.3Enabling HTTP Compression for SAP J2EE Engine 6.20 ......................................................134.4Using the SAP J2EE Engine Monitoring Server......................................................................14

5 Tuning the Portal Platform.......................................................................................................... 155.1Adjusting Portal Logging..........................................................................................................155.2Turning Off Portal Monitoring ..................................................................................................16

5.2.1 Disable Collecting Monitoring Data.............................................................................165.3Configuring Yahoo! Settings....................................................................................................165.4Optimizing Content Catalog Administration ............................................................................175.5Using and Adjusting PCD SQL Tracer logging ......................................................................175.6PRT Configuration ...................................................................................................................175.7Optimizing the Client Framework Script for Portal Pages .......................................................185.8Adjust User Management Connection Pooling (LDAP) ..........................................................18

6 Tuning the System Database...................................................................................................... 206.1Updating Classes12.jar ...........................................................................................................20

7 Tuning the Browser .....................................................................................................................217.1Setting the Browser for Compression......................................................................................21

2003SAPAG 1


3/24

1 IntroductionFine tuning SAP Enterprise Portal is a continuous process aimed at increasing the performance ofprocesses in the portal environment.

The goal of this document is to provide tuning guidelines for SAP Enterprise Portal to partners,consultants, and implementers.

It describes configuration settings, and provides procedures on how to set various parameters foryour operating system, Java virtual machine (JVM), SAP J2EE Engine, the portal database, thebrowser, and the LDAP directory service, in order to increase the performance of processes in theclustered portal environment.

Settings are presented as independent configurations, and modifying each configuration separatelyleads to an increased performance of processes within an area of the portal.

For maximum increase in performance, it is recommended that you implement all modificationsdiscussed in this document.

In different environments and systems, you may have different needs and expectations, andin addition, obtain different results. We highly recommend that you monitor the improvementsachieved after making the configuration changes.

Furthermore, tests to increase the performance of the portal processes are continuously in progress.Therefore we recommend that you visit our Web site for up-to-date information on tuning guidelinesfor SAP Enterprise Portal at:

service.sap.com >SAPEnterprise Portal 6.0 > Documentation & More > How-To Guides

2003SAPAG 2


4/24

2 Tuning the Operating System

2.1 General Requirements

Thread management changes are highly dependent on operating system (OS) resources. These

changes bring about different results in different machine configurations.

To achieve optimal performance, you must configure each operating system with its required set ofparameters.

For detailed information on how to implement the OS dependencies, refer to SAP Software on UNIX:OS Dependencies, at the Web site: service.sap.com/netweaver and follow the link SAP NetWeaverin Detail > Solution Life-Cycle Management > Installation > Installation & Upgrade Guides > SAPWeb Application Server > Release 6.20

Check also SAP Note 492222, SAP Software on UNIX: OS Dependencies, for updated kernelparameters. You can find the SAP Notes in SAP Service Marketplace (service.sap.com/notes).

2.2 Solaris 8: Tuning TCP/IP Connection Handling

You may need to enhance performance of your Solaris operating system by tuning how TCP/IPrequests are handled, although Solaris demands minimal tuning.

For additional information on TCP/IP parameters that apply to Solaris 8, refer to the topic TCP/IPTunable Parameters in Solaris Tunable Parameters Reference Manual, at:docs.sun.com/db/doc/816-0607

When handling a large number of TCP/IP requests, Solaris opens connections for all the requests.When the opened connections are no longer used by browsers and Web servers, they are stillopened.

You must trace the number of connections and modify the settings for them.

To trace and modify the number of TCP connections:

1. At the command line, type following the commands: netstat

ndd get /dev/tcp tcp_conn_hash

If the number of TCP connections is still very high, for example greater than 5,000, then modify the/etc/system file, by setting the following parameters:

2. Set the table size to 32K entries (default is 512k)

set tcp:tcp_conn_hash_size=32768

3. Set the "wait interval" to 60 seconds, the minimum value.This value is also applicable to Solaris 9.

set tcp:tcp_time_wait_interval=60000

2003SAPAG 3


5/24


6/24


7/24

Since the garbage collection process is single threaded, no other requests are processed duringthe collection cycle. For this reason GC tuning is highly recommended.

3.4.2 Monitoring Garbage Collection

You need to monitor GC activity in order to optimize the performance of the Java application. Thefollowing JVM option produces text information to standard output (stdout) about GC activity on theheap:

-verbose:gc

Add this option to your JVM settings in order to monitor all GC activities. The following areexamples of the output produced by this JVM option:

For a regular GC cycle: [GC 325816K->83372K(776768K), 0.2454258 secs]

For a full GC cycle: [Full GC 267628K->83769K(776768K), 1.8479984 secs]

From the example, both lines indicate the amount of memory before and after the collection,showing the efficiency of the GC, and the duration of the collection.

During high activity of the system (or during a load test) monitor the frequency and duration of the GCcycles.

Important: Prevent the system from performing full GC cycles, as these take longer anddoes not allow the system to respond to other requests.

You can prevent full GC cycles by applying the following:

Set an initial value for the NewSize and PermSize that is large enough, since any change in theirsize during run-time triggers a full GC.

This is evident during portal startup. If you have not set an initial NewSize or PermSize value,

you will have a series of full GCs that may increase your startup time by ~15 seconds.

Keep a ratio of 1:3 between the NewSize value and the total heap size.

If the NewSize value is too small, it leads to frequent GC cycles (filling up fast).

If the NewSize value is too large, there is not enough memory for the rest of the heap. ANewSize larger then half the heap size is counterproductive, as the contents of the NewSize ismoved to the preserved space for older generations after a regular GC cycle.

Monitor the efficiency of the GC. For detailed information, refer Soft references policy in thetable below.

If you continue to have frequent GC cycles after fine tuning the JVM settings, you must increasethe heap size.

If you increased the heap size and frequent GC cycles continues to occur, use Java profilingtools to locate the source of the problem.

2003SAPAG 6


8/24

3.5 JVM Settings for the SAP J2EE Engine With the Portal

The table below shows the parameters on heap size and garbage collection (GC) to modify in theJVM configuration files for SAP J2EE Engine server.

Settings Actions and Notes

Heap Size(Server only)

The heap size used by the Java virtual machine is a function of the number ofrunning and cached objects an application needs to use, and the availableamount of memory to the machine.

SAP Enterprise Portal 6.0 (server node) requires a minimum heap size of512MB.

In production environments, the recommended heap size is 1.5GB, andabove.

Make sure that the following properties have the same heap size value. Ifthese have not been defined, add them to the JVM configuration files:

-Xms

-Xmx

For example: -Xms1536M

The maximum heap size that should be configured on 32 bit UNIX, orNT systems is 1.5GB. In 64 bit UNIX systems, the maximum value isaround 3GB.

The installation program for SAP Enterprise Portal 6.0 SP2,automatically configures this JVM setting according to the heap sizespecified during the installation process.

Heap Size(Dispatcher)

The heap size for the dispatcher should be set to

-Xms64M

Increasing dispatchers heap size does not increase the performance of it.

Heap Size withMultiple VMs

(on the samehost)

When a machine has enough CPU power and memory to host more than oneserver node, add more SAP J2EE Engine server nodes in order to fullyoptimize the capacity of the system.

For information on the portal infrastructure, refer to the guide SAP EnterprisePortal Technical Infrastructurein the zipped package, EP6.0 SP2 InstallationGuide (Portal, CM, TREX, Unification), at: service.sap.com >SAPEnterprisePortal 6.0 > Documentation & More > Installation.

2003SAPAG 7


9/24


New Size

(server only)

This parameter configures the size of a new generation in the JVM memoryheap.

Objects that populate the new generation have not gone through a garbagecollection cycle yet. Objects that go through several collections and survive are

moved to the old generation, leaving room for newer objects.

The value for a new size is related to the value for the heap size you havedefined.

For best performance the new size must be a third of the heap size.

The installation program for SAP Enterprise Portal 6.0 SP2,automatically configures this JVM setting for the SAP J2EE Engineserver.

Perm Size(server only)

This parameter configures the size of the permanent memory space that isallocated outside the JVM memory heap.

Objects in this memory space never go through the garbage collection cycle,as the space is used during JSP compilation.

Portal applications, such as Content Management (CM), need a large numberof permanent objects in memory at runtime.

The recommended initial Perm Size is 128MB.

Configure the perm size by adding the following parameters to the JVMconfiguration files:

-XX:PermSize=

For example: -XX:PermSize=128M


Disable explicitgarbagecollection

(server only)

Explicit calls invoking the garbage collector should be disabled in a productionenvironment. However, on tests systems, this functionality may be required byexternal Java profilers.

Do not set VM Parameter XX:+DisableExplicitGC

If you want to disable Explicit GC, add the following parameter to the JVMconfiguration files:

-XX:+DisableExplicitGC


2003SAPAG 8


10/24


Soft ReferencePolicy

(server only)

The portal cache mechanism uses objects that are kept as soft references,cached objects. These objects are cleared at the discretion of the garbagecollector in response to memory demands.

This parameter configures the number of soft references that can stay alive on

the heap. When this value is reduced, the soft references are moreaggressively removed from the heap to make room for new objects.

The default value for this parameter is 1000.

A value higher than the default, makes cache more effective but leaves lessavailable memory on the heap.

A value less than the default makes the cache less effective but leaves morememory on the heap.

Do not set the parameter -XX:SoftRefLRUPolicyMSPerMB

Tune this value based on the following:

The number of objects cached with Soft Reference increases when more

users log-in, since each login caches the user objects.

When more users are logged on to a single SAP J2EE instance, lessmemory is available on the heap.

Monitor the ratio of the memory that is cleared during garbage collection.

You can detect an inefficient collection cycle when less than 50% of theheap is cleared during a cycle.

When the system is not able to clear enough memory on the heap in atimely manner, the collections become more frequent and finally lead tomultiple full GCs and an OutOfMemory exception.

If this happens, reduce the value for Soft references to 1, in order to allowthe garbage collector to aggressively remove soft references from theheap.

Configure this size by adding the following parameter to the JVM configurationfiles: -XX:SoftRefLRUPolicyMSPerMB=

This JVM setting is not configured automatically by the installationprogram.

2003SAPAG 9


11/24

4 Configuring SAP J2EE Engine Cluster 6.20This section describes procedures on how to tune SAP J2EE Engine to make sure that the portalruns in a highly optimized environment. As SAP J2EE Engine is a separate platform on which SAPEnterprise Portal runs, you must configure it to increase the performance of the processes used by

SAP Enterprise Portal.For additional information on tuning SAP J2EE Engine 6.20, refer to the document How to Tune SAPJ2EE Engine 6.20 v3.0 available at: service.sap.com/webas > Tools & Demos > How-To Guides.

The portal cluster environment depends on the proper setup and configuration of SAP J2EE Engine.You can configure properties of SAP J2EE Engine in the SAP J2EE Engine Config Tool window.

To open the SAP J2EE Config Tool window:

Run the file configtool(config.batin Windows) in the folder:/usr/sap//j2ee/j2ee_/configtool.

The settings described in this section are suitable for implementing a portal cluster based on a SAPJ2EE Engine cluster.

There are several ways to setup and configure SAP J2EE Engine cluster for the portal. Forthat reason, the SAP J2EE Engine cluster settings can be configured to suit a customersneeds.

For information on the portal landscape and cluster infrastructure, refer to the guide SAP EnterprisePortal Technical Infrastructurein the zipped package, EP6.0 SP2 Installation Guide (Portal, CM,TREX, Unification), at: service.sap.com > Enterprise Portal 6.0 > Documentation & More >Installation.

The following properties should be configured on each machine running SAP J2EE Engine:

Property Actions and Notes

ClusterHosts Defines a list of other cluster elements (dispatchers or servers), thatshould be contacted by the element when it starts.

The entries in this list are processed one after another in the specifiedorder.

To modify the list of clusters:

1. In the SAP J2EE Engine Config Tool window, open:

Dispatcher managers ClusterManager

ClusterHosts resp. Server managers

ClusterManager ClusterHosts

Dispatcher ClusterHostssettings:This line should contain

The Join Ports of all server nodes residing on the same host.

The Join Port of all other dispatcher nodes, residing on otherhosts

Server ClusterHostssettings:This line should contain

o The Join Port of the dipatcher on the same machine.

During installation, only a newly installed server is configured according.Already existing cluster elements are not updated during the Installation,and must therefore be manually configureds.

2003SAPAG 10


12/24

Property Actions and Notes

RepeatToConnect This property takes a true or false value.

When the value is false the cluster node creates the cluster after failingto connect to an already running SAP J2EE cluster by contacting allcluster elements specified in the ClusterHosts property.

When the value is true, it does not create any cluster, but continues itsattempts to connect to the J2EE cluster.

In the SAP J2EE Engine Config Tool window:

Dispatcher managers ClusterManager

RepeatToConnect resp. Server managers

ClusterManager RepeatToConnect

It is used together with the property ClusterHosts. The twoproperties, RepeatToConnect and ClusterHosts, can guaranteeconsistent connection and failover recovery of the cluster. This jointaction is effective when starting the cluster; afterwards, the clusterconnectivity is everyone-to-everyone.

LocalLoadBalancing This property takes a true or false value.

When the value is false, SAP J2EE Engine enables the particulardispatcher to distribute the load (of HTTP requests) on all server nodesin the cluster.

A value of true limits load balancing to servers running on the samehost.

In the SAP J2EE Engine Config Tool window, set the value to true:

Dispatcher managers ServiceManager LocalLoadBalancing

DependentElement This property defines the server node synchronization method of the

DBMS service to be either primary, or nonprimary.This property takes a true or false value.

When the value is false, the synchronization method for the DBMSservice of the particular server node is flagged as primary. This allowsthe server node to keep a local copy of the SAP J2EE Enginedeployment database. All other server nodes can either reference thedatabase without keeping a local copy, or update their local copies ofthe database after recovering from a failure.

A value of true configures the node to be a dependent DBMS servicenode, which reads the deployment database directly from a primarynode.

In the SAP J2EE Configuration Tool window, set the value of thisproperty to false in all server nodes:

Server managers ClusterManager DependentElement

2003SAPAG 11


13/24

4.1 Thread Manager Settings

This section describes the recommended changes to the Thread Manager settings of SAP J2EEEngine.

The How to Tune SAP J2EE Engine 6.20 v3.0document recommends that you change theThread Manager settings. Refer to the document How to Tune SAP J2EE Engine 6.20 v3.0available at: service.sap.com/webas > Tools & DemosHow-To Guides.

Follow the guidelines below when changing the Thread Manager settings for the portal cluster:

The number of threads that each machine is capable of supporting depends on the amount ofavailable memory, CPU, and other system resources.

You need to conduct performance tests, to obtain the correct settings for a specific machine,as the settings in the document, How to Tune SAP J2EE Engine 6.20 v3.0, are not optimizedfor every machine.

The portal itself contains a portal runtime (PRT) setting called loadlimit.requests. Thisproperty controls the maximum number of concurrent requests from the browser to the portal,

at a time.The value of this property must be the same as the value of the MaxThreadCount propertyof the SAP J2EE Engine thread manager. Both are set to 100 by default.

4.2 Adjusting SAP J2EE Engine Log Files

Log files enable you to track possible unstable conditions of the portal during development andtesting stages. An out-of-the-box portal installation has various log files containing portal runtimeinformation.

In a production environment, these log files occupy portal resources, and can have an effect on theoverall performance of the portal. Therefore, we recommend that you re-configure the log settings toa level, which only logs errors or warnings.

To change SAP J2EE Engine log levels:

1. Run the file configtool(configtool.batin Windows) in the SAP J2EE Engine folder at:/usr/sap//j2ee/j2ee_/configtool.

In the SAP J2EE Engine Config Tool window, change the following parameters:

Dispatcher managers LogManager LogLevel = 3

Server managers LogManager LogLevel = 3

Server services http EnableLoging = false

Server services PRTBridge EnableLoging = false

2. From the Filemenu, select Applyto save changes.

4.2.1 SAP J2EE Engine system.log and default.trc

A major performance improvement is achieved by disabling log files, system.logand default.trc.These files are written to the following directory:/cluster/server/services/log

2003SAPAG 12


14/24

To disable system.log:

1. Edit the saplogging.configfile in the following directory:/cluster/server/services/log/work/

2. Change the value /System.severity to NONE.

3. Change the value /Applications.severity to NONE

4. Change the line .logs = log[defaultTrace] to .localLogs = log[defaultTrace]

Reducing the application logs output level as described in this section also reduces the output tothe default.trcfile.

Monitor the folder /cluster/server/log/ to make sure that these log files arenot created.

4.3 Enabling HTTP Compression for SAP J2EE Engine 6.20

The SAP J2EE Engine contains an HTTP compression feature that improves performance byreducing network traffic.

Use this feature to disable compression for portal pages that need to work without

compression.

Important: To use this feature with an installation of Enterprise Portal 6.0, you need SAPJ2EE Engine Cluster 6.20 Patch Level 12 or higher, because it supports conditionalcompression.

To configure HTTP compression:

Run the file configtool. For more information on how to run the configtool, see the sectionConfiguring SAP J2EE Engine Cluster 6.20 on page 10.

The following are the properties to edit in SAP J2EE Engine Config Tool window:


HTTP ServiceCompression

Change the values of the following properties as follows:

Server services servlet_jsp EnableZippedResponse = true

Server services http EnableZippedResponse = true

Change the values of the following property:

Server services http NotZippedFiles

To enable script files compression, remove the CSS and JS referencefrom this line:NotZippedFiles = .zip, .cs, .rar, .arj, .z, .gz, .tar, .lzh, .cab, .hqx, .ace, .jar,.ear, .war, .css, .pdf, .js

Change maximum length to 1024MinimumGZipLength = 1024

Servlet_jsp ServiceCompression


Server services servlet_jsp

Change maximum length to 1024, MinimumGZipLength = 1024

2003SAPAG 13


15/24

HTTP Service

Content Expiration

Sets the expiration for the static content in seconds. The default value for thisproperty is 86,400 seconds, or 24 hours. The recommended value is 604,800seconds, or 7 days


Server services http CacheControl

Server services httpSapCacheControl

For example; CacheControl = 604,800

4.4 Using the SAP J2EE Engine Monitoring Server

SAP J2EE Engine contains a monitor server that provides valuable information of the state of thesystem at runtime. We recommend that you use this monitoring tool during fine tuning tests.

For detailed information on how to run the monitor server, refer to the SAP J2EE Engineadministration guide, installed with SAP J2EE Engine in the path:

\j2ee\j2ee_\docs\index.html

2003SAPAG 14


16/24

5 Tuning the Portal Platform

5.1 Adjusting Portal Logging

Various portal applications place information into different log files. We recommend that you set log

levels in production environments to WARNING or ERROR.

To configure the log levels for portal applications, edit the following files within each SAP J2EEEngine server node and restart the engine.

File Action and Notes

Logger.xml Portal applications are configured according to the logger.xmlconfiguration file.

Edit the logger.xmlfile by searching for the property isActive, and replacing its value ineach of the following directories, as follows:

isActive change it to isActive=true and level=WARNING or SEVERE

/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/system/xml/logger.xml

/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.runtime.admin.logadmin/ logger/logger.xml

/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.runtime.application.soap/logger/logger.xml

2003SAPAG 15


17/24

5.2 Turning Off Portal Monitoring

5.2.1 Disable Collecting Monitoring Data

The portal can connect to the SAP Computing Center Management System (CCMS) data collectionserver. If you are not using the CCMS to collect and monitor the portal data, you can disable the

property for it.To disable the monitor in a production environment:

1. Logon to the portal as an administrator.

2. In the top-level navigation bar, select System Administration > System Configuration.

3. From the Detailed Navigationpanel on the left, select Monitoring Configuration.

4. Under JARM, Java Application Responsetime Measurementin the Monitoring ConfigurationiView on the right, uncheck the following:

Collect monitoring data

Select Savein the iView.

5.3 Configuring Yahoo! Settings

If your portal works with content from Yahoo!, it is important to configure the Yahoo! settings to avoidunnecessary requests.

The integration of Yahoo! into SAP Enterprise Portal will be supported for existing customerswho have licensed MYEE content from SAP through the end of their current subscriptionterms and no later than December 31, 2004, whichever occurs first.

To open the iView that contains Yahoo properties:

1. Logon to the portal as an administrator.

2. In the top-level navigation bar, select System Administration > System Configuration.3. From the Detailed Navigationpanel on the left, select Service Configuration.

4. In the Portal Catalog, under Browse, select and expand the Java classcom.sap.portal.yahoo> Services, and right click yahoo> Edit.

The following are the settings in the Property List iView that are relevant to performance:


Enable Connectivity to Yahoo! Takes true or false.

Set it to false if you do not want connections to Yahoo.

Enable Persistent Heartbeat Pulses to

Yahoo!

Takes true or false.

Set it to false if you do not want connections to Yahoo.

Heartbeat Interval (in seconds) The default value is 120.

If you are connecting to Yahoo, you may want to increasethis value.

Heartbeat Time-out (in seconds) The default value is three.


2003SAPAG 16


18/24

Interval of Status Entry to Log File The default value is 50.


5.4 Optimizing Portal Catalog Administration

For administration tasks in the Portal Catalog, it is recommended that you organize the content in afolder taxonomy.

Placing many objects in a single folder increases the time it takes for that folder to load. Therecommendation is that do place more than fifty (50) objects in a single folder.

5.5 Using and Adjusting PCD SQL Tracer logging

You can view and analyze PCD data using the PCD SQL Tracer. The PCD SQL Tracer utilityprovides the following information:

Executed SQL statements

Frequency of an SQL statement execution.

Number of connections in the internal connection pool

By default the SQL trace is switched off. You can switch it on and off by setting the propertyPcd.Pl.TraceLevel.Sql in the pcdStartup.installer.propertiesfile, in the folder:/global/config/pcd

To switch the SQL trace on or off:

Set the property Pcd.Pl.TraceLevel.Sql to 3 if you want to trace the SQL information to thepcd.logfile.

Set the property Pcd.Pl.TraceLevel.Sql to 1 if you want to show the SQL trace information inthe console in addition to saving it to the pcd.logfile.

You can modify the configuration parameters of the PCD at runtime, as follows:

Start the component com.sap.portal.pcd.admintools.configuration .

Modify the configuration parameters in the pcdStartup.template.propertiesfile.

Select the Reloadbutton.

5.6 PRT Configuration

The file prtDefault.propertiescontains various properties that can be configured for the PRT. You canfind the file in the folder:/cluster/server/services/servlet_jsp/ work/jspTemp /irj/root/WEB-INF/portal/system/properties

The following table shows the properties in the file prtDefault.properties, to configure for the PRT:

Setting Action and Notesloadlimit.requests This property defines a limit for concurrent threads opened by the PRT.

The value must reflect the expected number of concurrent users, as aconcurrent user consumes one thread:loadlimit.requests=100In addition, the value of the property, in the file prtDefault.propertiesmust be the same as the value of the property MaxThreadCount of theSAP J2EE Engine thread manager.

2003SAPAG 17


19/24

Setting Action and Notes

Async.Response.Pools.size The number of buffers that the Page Builder can use to processasynchronous rendering of pages.

async.response.pool.size=100

Each buffer is used during the rendering of a portal page. Increasingthis value increases the number of pages to be renderedasynchronously.

A large value can have significant effect on the system, as it is affectedby available system resources, such as memory.

PRT monitor A useful setting is to enable the PRT monitor. You enable this monitorto help identify bottlenecks in performance.

In productive environments, we recommend to set

monitor.off=true

To enable the monitor:

Change the line "monitor.off=true to monitor.off=false.To view the monitor output:

Log on to the portal as an administrator, and navigate to:

System Administration Monitoring Portal Components Overview

System Administration Monitoring Portal Threads Overview

5.7 Optimizing the Client Framework Script for Portal Pages

The Client Framework include JavaScripts installed out-of-the-box with SAP Enterprise Portal. In aproduction environment, you can change the configuration settings for the JavaScripts that aredelivered from the server to clients.

Change the configuration settings for the JavaScripts using the scriptsetproperty. This propertydefines the type of display for the JavaScript, so that based on the defined level for the ClientFramework, the suitable JavaScript Include is automatically integrated in each portal page.

The default configuration sets the Client Framework to contain comments and formats that are easyto read. Changing the default to Optimize, eliminates comments and unnecessary spaces that will bedisplayed.

For additional information on how to configure the Client Framework, go to the SAP Help Portal athelp.sap.com> SAP NetWeaver > SAP Enterprise Portal 6.0 SP2 > Administration Guide > PortalPlatform > Content Administration > iViews > Client Framework for Administrators > Configuration

5.8 Adjust User Management Connection Pooling (LDAP)SAP Enterprise Portal 6.0 uses an LDAP connection pool to recycle calls made to the directory. Thedefault connection pool property, ume.ldap.connection_pool.max_size, has a value,ume.ldap.connection_pool.max_size = 10, that enables 50 concurrent logins.

When you change the value of the property to ume.ldap.connection_pool.max_size = 20, youenable 100 concurrent logins.

2003SAPAG 18


20/24

To change the value of this property:

1. Open and edit the file sapum.properties, from the path:/usr/sap//j2ee/j2ee_/ume/.

2. Change the value of the property ume.ldap.connection_pool.max_size.

To support the required number of concurrent logins, the MaxThreadCount property in theThread Manager of the SAP J2EE Engine, must be equal to the number of concurrent loginsin the property, loadlimit.requests of the PRT, as one thread equals one concurrent request.

2003SAPAG 19


21/24

6 Tuning the System DatabasePresently, this section contains information on Oracle systems.

6.1 Updating Classes12.jar

Classes12.jarcontains the connectivity library for Oracle systems, and it must be updated to aspecific version.

You can locate the file, Classes12.jarin the following folder:/server/additonal-lib/com/sap/jdbc_driver_references

Do the following:

Check the timestamp of the MANIFEST.MF file inside the classes12.jarfile, by running thefollowing command:

>unzip -l classes12.jar | grep MANIFEST.MF

The timestamp should not be older than- 02-19-03 15:28

If the file is older than indicated, download an updated classes12.jarfile from Oracle Website, and replace the old one.

For more information, refer to the guide EP6.0 SP2 Installation Guide (Portal, CM, TREX,Unification), at: service.sap.com > SAPEnterprise Portal 6.0 > Documentation & More > Installation.

Check also SAP Note 580304 for updates on this JAR file.

2003SAPAG 20


22/24

7 Tuning the BrowserConfiguring the browser and front-end devices for the portal leads to increase performance in theprocesses of the portal.

7.1 Setting the Browser for CompressionWhen using the Microsoft Internet Explorer as client browser, you must activate the HTTP 1.1 settingfor the SAP Enterprise Portal compression filter to work.

To set the compression filter:

1. From the client browser menu bar, select Toolsand then Internet Options.

2. Choose the Advancedtab and scroll toHTTP 1.1 settings.

3. Make sure the Use HTTP 1.1checkbox is selected.

4. If your network operates with a proxy server, verify that Use HTTP 1.1 through proxy connectionsis also selected.

5. Click OK.The following table contains browser caching information:

Browser Settings Actions

MS Internet Explorer 5.0, 5.5, 6.0 Browser Caching

You can improve the browser response time by using the browsercache. This enables your browser to cache resource files such asimages, CSS, JS, txt, and many more.

For detailed information on browser caching, refer to the sectionon Accessing the Enterprise Portalunder the topic SettingInternet Browser Optionsin the End User Guideat:

http://help.sap.com> mySAP Enterprise Portal > SAP

Enterprise Portal .

To use the browser cache in Internet Explorer (IE):

1. From the Toolsmenu > Internet Options> Generaltab, clickSettings.

2. Under Check for newer versions of stored pages in theSettingsdialog box, select either Automatically or Every Timeyou start Internet Explorer.

Do not choose Every visit to page.

3. Click OKtwice to save the settings for the browser cache.

2003SAPAG 21


23/24

Browser Settings Actions

Netscape 6.x Browser Caching

In Netscape 6.x, you can improve the browser response time byusing the browser cache.

To use the browser cache in Netscape:1. From the Editmenu, select Preferences.

2. In Category, click Advanced Cache.

3. Under Document in cache is compared to document innetwork in the Cache pane, select either Neveror Once persession.

Do not choose Every time.

4. Click OKto save the settings for the browser cache.

2003SAPAG 22


24/24

Copyright No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registeredtrademarks ofMicrosoft 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 and Informix Dynamic ServerTM are trademarks of IBMCorporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide WebConsortium, 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 fortechnology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service namesmentioned are trademarks of their respective companies.

Documents

Fine Tuning EP60 SP2 Performance