Tuning composite applications (Tuning Guide 6.1.x) 

For the Composite Application Infrastructure scenario, we started with the tuning given in the Base Portal Scenario above. However, the Composite Application Infrastructure scenario accesses a large number of applications, and therefore a large number of pages and portlets. Therefore there is higher demand on some of the caches in IBM® WebSphere® Portal; to improve performance in this scenario, we modified the sizes of some of the caches in WebSphere Portal.

Contents

     Cache Manager Service Properties
     Composite Applications Best Practices

Cache Manager Service Properties

The following values were specified in CacheManagerService.properties in addition to the parameters changed in the Base Portal tuning. We recommend that you monitor the caches in your environment to determine which caches might need tuning.

Table 25: Cache Manager Serivce Properties for Application Infrastructure

Parameter	Value
cacheinstance.com.ibm.wps.resolver.friendly.cache.size	8000
cacheinstance.com.ibm.wps.ac.ProtectedResourceCache.size	10000
cacheinstance.com.ibm.wps.ac.PermissionCollectionCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.AccessControlUserContextCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ProtectedResourceCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.OwnedResourcesCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.RolesCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ParentResourceRoleMappingCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ResourceRoleMappingCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ChildEntitlementsCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.SingleEntitlementsCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.CONTENT_NODE.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.WEB_MODULE .lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.APPLICATION_RO LE.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.PORTLET_APPLIC ATION_DEFINITION!PORTLET_DEFINITION.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.USER_GROUP .lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.VIRTUAL.li fetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.WSRP_PRODUCER< /i>.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.ICM_CONTENT.lifetime	28800
cacheinstance.com.ibm.wps.ac.ExternalOIDCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ApplicationRoleOIDCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ApplicationRoleDescriptorCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.ApplicationRolesForPrincipalCache.lifetime< /tt>	28800
cacheinstance.com.ibm.wps.ac.ApplicationRoleChildrenCache.lifetime< /td>	28800
cacheinstance.com.ibm.wps.ac.ContainedRolesCache.lifetime	28800
cacheinstance.com.ibm.wps.ac.AuthLevelConfigurationCache.lifetime	28800
cacheinstance.com.ibm.wps.ai.rt.impl.service.ActiveApplicationOIDCache.l ifetime	28800

Composite Applications Best Practices

As with other components of WebSphere Portal, the way in which teamspaces are used will influence the performance of the site. Based on our experience and analysis, the following tips can help you achieve better performance with teamspaces:

• As the preceding measurements show, the number of teamspaces on the system influences the capacity of the system. However, the key determining factor is not the total number of teamspaces, but rather the number of teamspaces visible to each user. For example, a site with 1,000 teamspaces visible to all users could have a capacity lower than a site with 5,000 teamspaces where the typical user can see no more than 50 of those.


• One way to exploit the observation above is to not make teamspaces public by default. Public teamspaces are visible to all users, so a large number of public teamspaces will increase the average number of teamspaces visible to each user.


• To paraphrase Albert Einstein, “keep teamspaces as simple as possible, but no simpler”. In implementing this, consider both the number of pages as well as the number of portlets on each page. Adding additional pages or portlets to a teamspace increases the overhead associated with that teamspace. While this is not a great overhead when considering an individual teamspace, when aggregated across thousands of teamspaces, the overhead can become significant. In addition, the more portlets are on each page, the more work will required to render that page.


• Another area to consider regarding teamspace complexity is the number of application roles. For many teamspaces, two roles (manager and user) are adequate. Do not create additional roles unless they are really needed.


• When assigning membership to a teamspace, the best performance will be seen when membership is assigned by groups rather than by individual users. For example, WebSphere Portal will cache permissions based on the way permissions are assigned, giving the chance for more cache hits if permissions are assigned by groups.


• Memory demand increases with the number of teamspaces on the system. Therefore, if you expect to use large numbers of teamspaces, a 64-bit JVM will probably provide better capacity than a 32-bit JVM.

Also refer to the section regarding Use of Dynamic Content Features. Experiments in our lab showed a reduced demand for memory, and thus an improvement in capacity, in the application infrastructure scenario when disabling dynamic content support.

For the Composite Application Infrastructure scenario, we started with the tuning given in the Base Portal Scenario above. However, the Composite Application Infrastructure scenario accesses a large number of applications, and therefore a large number of pages and portlets. Therefore there is higher demand on some of the caches in IBM® WebSphere® Portal; to improve performance in this scenario, we modified the sizes of some of the caches in WebSphere Portal.