IBM WebSphere Portal 6.1.x性能调优指南

需积分: 4 152 浏览量更新于2024-08-02 收藏 1.08MB PDF 举报

"IBM WebSphere Portal 6.1.X Performance Tuning Guide，由IBM WPLC Performance Team于2009年3月发布，版本2.1，是截至09年5月最新的调优手册，专注于提升Portal性能。" 在IBM WebSphere Portal 6.1.X的性能调优过程中，有几个关键领域需要关注，这些都详细地记录在这份调优指南中： 1. **环境考虑**：调优开始前，必须考虑运行环境的因素，包括32位与64位系统的差异以及硬件多线程技术（如Intel的Hyper-Threading）的影响。这些因素会直接影响到Portal软件的性能表现。 2. **基础Portal调优**：这部分涉及对Portal服务器的基础设置调整，以优化其性能。例如，调整应用服务器的参数对于整体性能至关重要。 3. **应用服务器调优**：应用服务器的调优主要围绕Java虚拟机（JVM）进行，包括设置JVM的初始堆大小和最大堆大小，以确保内存分配得当。此外，使用大型页（Large Page）技术可以提高JVM性能。 4. **JVM堆区大小**：新区域大小的配置影响垃圾收集的效率，需根据系统负载进行适当调整。 5. **其他SUN JVM参数**：除了基本的JVM参数外，可能还需要添加额外的参数来优化特定的性能特性。 6. **Session超时**：设置合适的会话超时值可以防止内存泄漏，同时平衡用户体验和服务器资源使用。 7. **Web容器线程池大小**：线程池大小的调整能控制并发请求处理能力，避免过度消耗系统资源。 8. **安全属性传播**：优化安全属性的传播机制可以提高处理速度，减少不必要的开销。 9. **VMM上下文池化**：有效管理虚拟内存管理器（VMM）的上下文池，有助于减少内存访问的延迟。 10. **ORB服务调优**：特别是针对z/OS平台，优化ORB（对象请求代理）服务可以提升远程对象交互的性能。 11. **WebSphere Portal服务**：包括Navigator Service、Registry Service和Cache Manager Service等，每个服务的调优都对整体性能有显著影响。 12. **数据库调优**：对数据源进行调优，如针对DB2和Oracle的具体建议，以及对其他数据库的一般性考虑，以确保数据库操作的高效性。 13. **目录服务器调优**：目录服务器的优化可以提高用户身份验证和授权的速度。 14. **Web服务器调优**：Web服务器的配置调整，如Apache或IHS，可以提升HTTP通信的性能。 15. **操作系统调优**：针对不同的操作系统，如AIX、Linux、Windows 2003、Solaris和z/OS，都有特定的调优策略。 16. **必要的补丁修复**：保持系统更新，应用必要的性能修复补丁，以消除已知的性能问题。 17. **Web 2.0主题调优**：考虑到Web 2.0功能的性能需求，需要对JVM的初始和最大堆大小进行特殊考虑。这份调优指南提供了全面的步骤和建议，帮助管理员深入理解并优化IBM WebSphere Portal 6.1.X的性能，确保系统的稳定性和高效运行。

VMM CONTEXT POOLING

Tune VMM Context Pooling to improve the performance of concurrent access to an LDAP

server.

We changed the following Context Pooling settings line in:

<wp_profile_root>/config/cells/<cellname>/wim/config/wimconfig.xml

<config:contextPool enabled="true" initPoolSize="10" maxPoolSize="0"

poolTimeOut="0" poolWaitTime="3000" prefPoolSize="30"/>

You can also set them via the administrative console as described in

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websph

ere.base.doc/info/aes/ae/uwim_ldapperfsettings.html

Table 3: VMM Context Pool Setting

Context Pool Setting Default Value Value

initPoolSize

1 10

prefPoolSize

3 30

Number of open connections to maintain to

LDAP server.

maxPoolSize

20 0.

A value of 0 allows the pool to grow as large

as needed. If access to the LDAP server is

shared by many systems, this setting may

allow an excessive number of connections to

the LDAP server; in such a case, set the

maximum pool size to a value appropriate to

your environment.

ORB SERVICE TUNING FOR Z/OS

In the WAS Admin Console, set the ORB Service to be "pass by reference" instead of

"pass by value" (default) for both server1 and WebSphere_Portal

How to Set:

- ServersÆ Application ServersÆ server1Æ Orb Service

- check box for "Pass by Reference"

- ServersÆ Application Servers ÆWebSphere_Portal Æ Orb Service

- check box for "Pass by Reference"

WEBSPHERE PORTAL V6.1 TUNING GUIDE

WebSphere Portal Services

WebSphere Portal has a number of configurable “services”; each service has several

parameters available to it. This section describes which services we tuned, the tuning values

used, and the rationale for those changes.

How to Set:

1. Edit <wp_profile_root>/PortalServer/config/properties/xxxService.properties

2. uncomment the line, then change the size.

3. run <wp_profile_root>/ConfigEngine/ConfigEngine.sh update-properties

The changes should appear on WAS Console -> Resource Environment Providers ->

WP_xxxService -> Custom properties

NAVIGATOR SERVICE

The navigator service manages the content model for unauthenticated users, which controls

the pages those users are able to see. This content model is periodically reloaded by

WebSphere Portal; new pages which are visible to unauthenticated users will not be

available until the next reload occurs. Our environment assumes a low rate of change for

pages, so we set this reload to only occur once per hour. In a production environment where

new pages for unauthenticated users are rarely created, setting this reload time to an hour

or more will give better performance. In a test or staging environment where updates to

unauthenticated pages need to be seen more often, a lower reload time is more appropriate.

This service also controls the HTTP cache-control headers which will be sent on

unauthenticated pages. While our environment did not exploit HTTP page caching,

increasing these cache lifetimes in a production environment can reduce load on the portal.

For more discussion of the use of HTTP cache-control headers with WebSphere Portal,

refer to the “Caching” section of the “Tuning” topic in the WebSphere Portal V6.1 InfoCenter.

Table 4: Navigation Service Settings

NavigatorService.properties

Parameter

Default

Value

Used

Definition

public.expires (seconds)

60 3600 Determines cache expiration time for caches

outside of WebSphere Portal and for

unauthenticated portal pages only. If the setting

remote.cache.expiration is also set to a value

greater than or equal to 0, the smaller one of the

two values is used.

public.reload (seconds)

60 3600 Determines cache expiration time for the portal

internal cache for unauthenticated pages

remote.cache.expiration

(seconds)

60 28800 Determines cache expiration for caches outside

of portal server for authenticated as well as for

unauthenticated pages

WEBSPHERE PORTAL V6.1 TUNING GUIDE

CACHE MANAGER SERVICE

The cache manager service in WebSphere Portal is used to cache a wide variety of types of

information in memory. These caches are somewhat similar to the registries maintained by

the registry service, as each type of information gets its own cache. The key differences are:

 The information stored in the cache manager service’s caches tends to be more

dynamic than the information stored in the registry service’s registries.

 The caches used by the cache manager service are limited in size, and entries will

be discarded when the caches become full. The registries used by the registry

service are not size-limited; they contain all entries of the specific data type.

 Expiry times are managed individually for each entry in the cache, managed by the

cache manager service. In contrast, when the reload time is reached for a registry,

the entire contents of that registry are reloaded.

Each cache has several configurable options. A full discussion of these options, along with a

list of the caches in WebSphere Portal V6.1, is given in chapter 2. Table 5 lists the changes

which we made to the cache manager service configuration file. Size values are specified in

“number of objects” and lifetime values are specified in “seconds”.

Table 6: Cache Manager Service Settings

CacheManagerService.properties

Cache Name

Default Value Value Used

com.ibm.wps.model.factory.ContentModelCache.live.size 1000 2500

com.ibm.wps.ac.ExplicitEntitlements Cache.USER_GROUP.size 1000 2000

com.ibm.wps.model.factory.Navigation

SelectionModelCache.live.size

1000 2500

com.ibm.wps.ac.OwnedResourcesCache.enabled true false

com.ibm.wps.ac.ProtectedResourceCache.lifetime 5000 14400

com.ibm.wps.datastore.services.Identification.SerializedOidString

Cache.size

2500 5000

com.ibm.wps.puma.DN_OID_Cache.size 500 5000

com.ibm.wps.puma.DN_User_Cache.size 500 3000

com.ibm.wps.puma.DN_Group_Cache.size 500 1500

com.ibm.wps.puma.OID_DN_Cache.size 1500 3000

com.ibm.wps.puma.OID_User_Cache.size 1500 3000

com.ibm.wps.puma.OID_Group_Cache.size 1500 5000

com.ibm.wps.ac.groupmanagement.NestedGroupCache.enabled true False

com.ibm.wps.ac.RolesCache.enabled true False

com.ibm.wps.ac.ChildResourcesCache.lifetime 7200 28800

com.ibm.wps.policy.services.PolicyCacheManager.lifetime 7780 43200

WEBSPHERE PORTAL V6.1 TUNING GUIDE

Database Tuning

DATASOURCE TUNING FOR DB2

Multiple databases are used to hold information in WebSphere Portal V6.1. We used six

separate DB2 databases, each representing a separate database domain and having their

own datasources. These are:

Table 7: DB2 Database Domains

Database Database name Datasource name

Release

release reldbDS

Community

community commdbDS

Customization

custom cusdbDS

Feedback

fdbkdb fdbkdbDS

Likeminds

Lmdb lmdbDS

JCR

jcrdb jcrdbDS

All datasources are configured in a similar manner by logging on to the WebSphere

Application Server administrative console. For the prepared statement cache size, the path

is Resources → JDBC Providers → provider name → Data Sources → datasource name.

The provider name and datasource name are based on the names selected for that

database during the database transfer step. Look for the parameter Statement cache size.

For the connection pool settings, the path in the WebSphere Application Server

administrative console is Resources → JDBC Providers → Provider name → Data Sources

→ Datasource name → Connection Pools. The settings are Minimum connections and

Maximum connections.

The default settings were used for the prepared statement cache size, and connection pool

minimum and maximum sizes.

DB2 DATABASE SERVER TUNING

WebSphere Portal V6.1 uses database servers for core functionality. In our measurement

environment, we used DB2 database server for the Portal application. The LDAP server,

IBM Tivoli Directory Server also included a DB2 database as a repository, but it is largely

unseen and was operated as an out of box configuration.

We recommend using a remote database server for the largest capacity. For our

measurements we used IBM DB2 Enterprise Edition V9.1 fixpack 5 as our database server.

WebSphere Portal V6.1 uses the concept of Database domains to designate either groups

of tables belonging to one domain, or even entirely separate databases to store the data

specific to each domain.

WEBSPHERE PORTAL V6.1 TUNING GUIDE

剩余96页未读，继续阅读

sunxingtao

粉丝: 11
资源: 35

IBM WebSphere Portal 6.1.x性能调优指南

Ibm websphere Portal 6.1调优手册

websphere portal开发手册

IBM WebSphere Portal v6.0 安装 启用Domino操作手册

tia portal v17 - 中文编程手册

sap portal 怎么开发

arcgis portal10.5授权

华为s5700portal配置

portal 怎麽使用

Portal 怎麽使用

tia portal 高级编程 pdf

最新资源

IBM WebSphere Portal v6.0 安装启用Domino操作手册