Optimizing Performance With the UME Cache 

Use

Use this procedure to improve the performance of the SAP NetWeaver Application Server (AS) Java, by changing the configuration properties of the cache of the user management engine (UME). Improper settings can impact system performance or affect how current the user data is on the server node. The UME cache uses the initial cache size to keep the cache current.

When the initial cache size is too small, the cache removes objects too quickly from the cache, reducing performance. When the initial cache size is too large, it reserves the memory needed by other applications. As a rule of thumb, configure the initial cache size to the maximum number of concurrent users you expect divided by the number of server nodes in the cluster. The more groups, roles, and other attachments, such as employee photos you associate with a given user, the larger each object entry is. The size of the object entry increases the memory footprint of the cache.

Prerequisites

This procedure requires you to restart the SAP NetWeaver Application Server (AS) Java, so you should plan for the required down time while the AS Java restarts.

Procedure

...

       1.      Start the config tool.

       2.      Choose  with the quick info text Switch to configuration editor mode.

       3.      In the Display Configuration tab, choose cluster_config ® system ® custom_global ® cfg ® kernel ® Cache ® cache-configuration.xml ® cache-configuration ® regions.

       4.      Choose  with the quick info text Switch between view and edit mode.

A warning appears to make sure the server and dispatcher nodes are shut down.

       5.      Choose Yes.

       6.      Choose a region.

There are regions for a number of different objects, such as user, account, group, and role objects. You can set each one independently. The table below lists the cache objects with the display name and the name of the region.

 

Some cache object have a pair of cache regions. Use the same settings for both regions. For example, the Group Cache is paired with the Group Mapping Cache for group objects.

Caches and Their Regions

Cache Object	Display Name	Region
ACL	ACL Cache	UME_Cache_com.sap.security.core.acl.imp. wcm.jdbc.JDBCAclManager_default_m_aclCache
ACL permission	ACLPermission Cache	UME_Cache_com.sap.security.core.acl.imp. wcm.jdbc.JDBCAclManager_default_m_permissionCache
Action	Action Cache	UME_Cache_com.sap.security.core.role.imp. ActionFactory_mCache
Group	Group Cache	UME_Cache_com.sap.security.core.imp. GroupFactory_mCache
Group	Group Mapping Cache	UME_Cache_com.sap.security.core.imp. GroupFactory_mUNCache
Permission	Permission Cache	UME_Cache_com.sap.security.core.role.imp. PermissionFactory_mCache
Principal	Principal Cache	UME_Cache_com.sap.security.core.imp. PrincipalFactory_mCache
Role	Role Cache	UME_Cache_com.sap.security.core.imp. RoleFactory_mm_roleCache
Role	Role Mapping Cache	UME_Cache_com.sap.security.core.imp. RoleFactory_mUNCache
User account	User Account Cache	UME_Cache_com.sap.security.core.imp. UserAccountFactory_mCache
User account	User Account Mapping Cache	UME_Cache_com.sap.security.core.imp. UserAccountFactory_mMappingCaches (ALL_DATASOURCES_)
User	User Cache	UME_Cache_com.sap.security.core.imp. UserFactory_mCache
User	User Mapping Cache	UME_Cache_com.sap.security.core.imp. UserFactory_mUNCache

 

       7.      Choose Propertysheet region-configuration and then  with the quick info text Edit the details of the selected node.

       8.      Enter data as required.

                            a.      Set a new value for _COUNT_UPPER_LIMIT_THRESHOLD.

                            b.      Set _COUNT_START_OF_EVICTION_THRESHOLD 500 lower than the upper limit threshold.

                            c.      Set _COUNT_CRITICAL_LIMIT_THRESHOLD 500 higher than the upper limit threshold.

       9.      Restart the AS Java.

More Information:

●      UME Cache  

●      Monitoring the Performance of the UME Cache  

●      Refreshing the User Caches of the AS Java