Editing UME
Properties
Use
Use the config tool to edit user management engine (UME) properties offline for the service com.sap.security.core.ume.service. Editing the properties offline prevents user management data from becoming inconsistent in a running system because of changes made to UME properties with the config tool.
You can use UME configuration to edit properties in most cases. Only use the config tool if you cannot use an online tool. The UMEconfiguration reads and changes properties at the global level. UME configuration has no influence on custom values set at lower levels in the configuration structure.
You can use the SAP NetWeaver Administrator to view and edit properties at the template and instance level. Enter the quick link /nwa/sys-config. In the Services tab, select User Management Engine.
Do not edit undocumented properties without consulting SAP Support.
More Information:
Config Tool
Properties of the AS Java
You can set the properties of the SAP NetWeaver Application Server (AS) Java at different levels in the configuration structure. In an AS Java cluster, you can set properties at the following levels:
● Global
Values applies to all instances in the cluster
● Template
You can define configuration templates. Only a single template can be active in the cluster and all instances use the active template. You can define additional inactive templates. You can change the active template at, causing all instances inherit any custom values defined in newly activated template.
● Instance
The lower levels inherit the property values of the upper levels, unless you set a custom value for that level. Lower levels inherit the custom value of the property. The figure below illustrates how values are inherited.
Configuration Structure of the AS Java
Properties of the UME
UME properties fall into one of the following classes:
● Persistence properties
These properties control access to the data source among other functions. They are final (they can only be set at the global level) and require a restart of the AS Java. Changing these properties at lower levels or during runtime would cause inconsistent behavior and lead to users, groups, and roles appear and disappearing according to the instance you logged into or changes in the properties.
● Everything else
These properties control functions such as the security policy and e-mail notification. You can set these properties at lower levels or change their values online.
We recommend that you set all UME properties at the global level, but you may have a configuration where setting these properties at another level makes sense.
There are exceptions to these generalizations. There are persistence properties that can be modified online. From the nonpersistence properties there are properties that are final and properties that require restart. You can view the meta attributes of a property in the Config Tool to determine if it is final or online modifiable.
Prerequisites
This procedure requires you to stop the AS Java. Plan for the required downtime while the AS Java restarts.
Procedure
This procedure sets properties at the global level.
...
1. Start the Config Tool.
2.
Choose 
(Switch to configuration
editor mode).
3. On the Display Configuration tab page, choose cluster_config → system → custom_global → cfg → services → com.sap.security.core.ume.service → Propertysheet properties.
4.
Choose 
(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 
(Edit the details of the
selected node).
7. Double-click a property.
The Change PropertyEntry dialog box appears.
The dialog box also provides a description of the property.
8. Enter data as required.
For example, enter a custom value and choose the Apply custom pushbutton.
9. Choose the OK pushbutton.
10. Restart the AS Java.