UME Properties for an AS ABAP Data Source (SAP-Bibliothek

UME Properties for an AS ABAP Data Source

Use the properties in the following tables when you configure the User Management Engine (UME) to use the user management of an ABAP system as the data source.

Empfehlung

We recommend you connect to a specific SAP NetWeaver Application Server (AS) ABAP. However, you have the option to connect to a load balancing server group. Use the load balancing configuration when the UME has read-only access to the AS ABAP, and especially when more than one UME accesses the same system. In addition to the user and password settings, the required properties you need depend on the type of connection you make.

● Always set:

○ ume.r3.connection.master.passwd

○ ume.r3.connection.master.user

● To connect to a specific application server:

○ ume.r3.connection.master.ashost

○ ume.r3.connection.master.sysnr

● To connect to a load balancing server group

○ ume.r3.connection.master.group

○ ume.r3.connection.master.msghost

○ ume.r3.connection.master.r3name

Connection Properties

Property	Value	Description
ume.r3.connection. master.ashost		Application server host address, for example, server02.example.com.
ume.r3.connection. master.client		AS ABAP client, for example 100.
ume.r3.connection. master.group		Name of the message server group, for example, PUBLIC.
ume.r3.connection. master.msghost		Message server host address, for example, server01.example.com.
ume.r3.connection. master.passwd		Password of the user set in ume.r3.connection.master.user.
ume.r3.connection. master.r3name		Three-character code for the ABAP system, for example ABC. This is used to lookup the message server host address and message server group in the sapmsg.ini file on the server.
ume.r3.connection. master.sysnr		AS ABAP system number, for example, 12.
ume.r3.connection. master.user		Logon ID of the system user for UME-ABAP communication. This user must have authorizations to use RFC, and to create, change, or delete users in the AS ABAP. For more information, see Requirements for the System User for UME-ABAP Communication.

Optional Properties

Property	Value	Description
ume.logon. r3master.adapterid	Default value is master.	Name of adapter ID that identifies an AS ABAP used as the data source.
ume.r3.connection. master.gwhost		Gateway host.
ume.r3.connection. master.gwserv		Gateway service.
ume.r3.connection. master.lang	ISO language code	Language with which the service user is logged on to the ABAP system in the backend. This should be the same language that an administrator would use when logging on to the back-end system using a SAP GUI. The UME defaults to the ABAP system user’s value. This setting is particularly important if the back-end system uses characters outside the ASCII set, for example, a double-byte system with Japanese data. In this case, if the language is not configured properly, data coming from the back-end system is not displayed correctly in the UME user interfaces. See also SAP Note 866367.
ume.r3.connection. master.poolmaxsize	Default value is 10.	Maximum number of open connections in the connection pool. The number of connections is limited by the memory size in the ABAP system. Refer to the SAP Java connector documentation for details.
ume.r3.connection. master.poolmaxwait	Default value is 10000.	Maximum time in milliseconds that an incoming request waits for a connection before throwing an exception. If an exception gets thrown, this indicates that the number of connections allocated to the pool is not sufficient to handle the load. Increase the number of connections or the wait time.
ume.r3.connection. master.TimeZoneMapping		The AS ABAP and AS Java systems use different concepts for displaying time zones. AS ABAP uses generic regional designations, such as Central European Time (CET). AS Java designates time zones by region and city, such as Europe/Rome and Europe/Berlin. There is a default mapping of these two systems installed, which you cannot change, but you can override. To override the default mapping or add additional mappings, enter the time zone pairs in this property. Enter comma separated pairs. Each pair defines a mapping from an ABAP time zone to a Java time zone and the reverse, Java to ABAP. You can have multiple entries for the same time zone, but only the last entry is used at runtime. Suzanne Glenn made the following entries in the time zone mapping property: CET=Europe/Rome, CET=Europe/Berlin When she views a user in transaction SU01, who has the time zone set to Europe/Rome or Europe/Berlin in the AS Java database, she sees the value as CET, as both these values are mapped to CET. When Suzanne adds a user in transaction SU01 and sets the time zone to CET, when she later views the user in the UME, she sees the value as Europe/Berlin, because CET=Europe/Berlin is the last entry in the list. Since different numbers of time zones exist in the AS ABAP (delivered and custom) and in the AS Java (depending on the Java runtime environment version and manufacturer), the mapping cannot cover all scenarios. If you specify a Java time none that is not supported by the current Java runtime environment, the entry is ignored and a warning is written to the log file of the security component.
ume.r3.mastersystem		See User Mapping.
ume.r3.mastersystem. uid.mode		See User Mapping.

Properties for Secure Network Communications (SNC)

Property	Value	Description
ume.r3.connection. master.snc_lib		Path to library that provides SNC service.
ume.r3.connection. master.snc_mode	0 = SNC disabled. 1 = SNC enabled.
ume.r3.connection. master.snc_myname	p:<distinguished_name_ of_UME_SNC_PSE>	SNC name of the UME.
ume.r3.connection. master.snc_partnername	p:<distinguished_name_ of_SNC_PSE_of_ABAP_system>	SNC name of the ABAP system.
ume.r3.connection. master.snc_qop	Value between 1 and 9	SNC level of security.