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

Start the User Management Configuration as described in Configuring User Management .
Choose Open Expert Mode .
Choose Modify .
Filter for ume.cache .
Change the settings as required.
Save your entries.
Close Close Expert Mode .
Restart the AS Java.

Recommendation

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, the name of the region, and their properties.

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

Cache Object	Display Name	Key (Property)	Region
User	UME User Cache	ume.cache.user.default_caching_time Maximum time (in seconds) for which users remain in the cache (-1 means until the release algorithm removes the object). Default is 1 hour. ume.cache.user.initial_cache_size Initial size of the user cache measured in number of objects.	`UME_Cache_com.sap.security.core.imp. UserFactory_mCache`
User	UME User Mapping Cache	See UME User Cache.	`UME_Cache_com.sap.security.core.imp. UserFactory_mUNCache`
User account	UME User Account Cache	See UME User Cache.	`UME_Cache_com.sap.security.core.imp. UserAccountFactory_mCache`
User account	UME User Account Mapping Cache	See UME User Cache.	`UME_Cache_com.sap.security.core.imp. UserAccountFactory_mMappingCaches (ALL_DATASOURCES_)`
Group	UME Group Cache	ume.cache.group.default_caching_time Maximum time (in seconds) for which groups remain in the cache (-1 means until the release algorithm removes the object). Default is 1 hour. ume.cache.group.initial_cache_size Initial size of group cache measured in number of objects.	`UME_Cache_com.sap.security.core.imp. GroupFactory_mCache`
Group	Group Mapping Cache	See UME Group Cache.	`UME_Cache_com.sap.security.core.imp. GroupFactory_mUNCache`
Role	UME Role Cache	ume.cache.role.default_caching_time Maximum time (in seconds) for which roles remain in the cache (-1 means until the release algorithm removes the object). Default is 1 hour. ume.cache.role.default_caching_time Initial size of the role cache measured in number of objects.	`UME_Cache_com.sap.security.core.imp. RoleFactory_mm_roleCache`
Role	UME Role Mapping Cache	See UME Role Cache.	`UME_Cache_com.sap.security.core.imp. RoleFactory_mUNCache`
Action	UME Action Cache	ume.cache.action.default_caching_time Maximum time (in seconds) for which actions remain in the cache (-1 means until the release algorithm removes the object). Default is infinite. ume.cache.action.initial_cache_size Initial size of action cache measured in number of objects.	`UME_Cache_com.sap.security.core.role.imp. ActionFactory_mCache`
Permission	UME Permission Cache	ume.cache.permission.default_caching_time Maximum time (in seconds) for which permissions remain in the cache (-1 means until the release algorithm removes the object). Default is infinite. ume.cache.permission.initial_cache_size Initial size of permission cache measured in number of objects.	`UME_Cache_com.sap.security.core.role.imp. PermissionFactory_mCache`
Principal	UME Principal Cache	ume.cache.principal.default_caching_time Maximum time (in seconds) for which principals remain in the cache (-1 means until the release algorithm removes the object). Default is 1 hour. ume.cache.principal.initial_cache_size Initial size of the principal cache measured in number of objects.	`UME_Cache_com.sap.security.core.imp. PrincipalFactory_mCache`
ACL	UME ACL Cache	ume.cache.acl.default_caching_time Maximum time (in seconds) for which ACLs remain in the cache (-1 means until the release algorithm removes the object). Default is infinite. ume.cache.acl.initial_cache_size Initial size of ACL cache measured in number of objects.	`UME_Cache_com.sap.security.core.acl.imp. wcm.jdbc.JDBCAclManager_default_m_aclCache`
ACL permission	UME ACL Permission Cache	See UME ACL Cache.	`UME_Cache_com.sap.security.core.acl.imp. wcm.jdbc.JDBCAclManager_default_m_permissionCache`

More Information