User Management Engine (UME) & Data Sources

AS Java ships three service providers (user stores) for storing user and group data. Which three, and which is chosen at installation?

Name the data source types the UME can store user data in, and say whether the local file system is one of them.

An application developer asks how the UME knows whether to read a user from the database, an LDAP server, or an ABAP system. Which UME layer answers that, and what does it hide?

What does UME data partitioning let an administrator do that a single data source cannot?

The UME offers three models for splitting data across sources. Give the three and one concrete split each produces.

At AS Java installation the UME data source is not chosen by the admin but derived from something else. From what, and which config file results?

Among the tools for UME configuration, one can only display settings and never change them. Which one, and which tool can reach all settings?

An admin finds UME parameters listed in the NWA Java System Properties view and edits a value there. Why is that the wrong place?

In the delivered UME mapping to the InetOrgPerson (X.500) schema, how is the FULLNAME field derived, and what is the telephone field called on the LDAP side?

Which single UME parameter tells you which data source is currently connected, and how?

The UME distinguishes several user types (security policy profiles). How many are there, and which one cannot log on to AS Java at all?

When the UME uses an ABAP system as its data source, how do the UME user types Default, Technical users, and Unknown map to ABAP user types?

Before changing the UME configuration, what safeguard does SAP say to perform first, and what is the resulting file good for (and not good for)?

A customer wants to switch their UME data source after go-live. For each of the three starting data sources, what change is actually supported?

In a heterogeneous landscape with both SAP and non-SAP systems, why is a directory service recommended as the primary store for user data, and how do ABAP users get there?

A team already runs UME with an LDAP directory and asks what SAP NetWeaver Identity Management would add on top. What is the answer?

The DBMS and UDDI providers implement open standards, yet SAP still sets up its own UME as the user store at every AS Java install. What is the reason?

When a directory service is a UME data source, why is attribute mapping usually necessary, and must it be one-to-one?