SAP R/3 Data Source (SAP Library

SAP R/3 Data Source

The properties listed below are set for the following SAP Systems:

· SAP Systems that are used as a user data store

In this case, the default value for <adapterID> is master. You can change it by assigning a different value to the property ume.logon.r3master.adapterid.

· SAP Systems to which user data is replicated

In this case <adapterID>must be the same adapter id as you specified in ume.replication.adapters.index_<index>.

Note

Allowed values for <adapterID> are 001. 002, and 003.

Required Properties

Property	Value	Description
ume.r3.connection. <adapterID>.ashost *		Application server host address, for example, server02.mycompany.com.
ume.r3.connection. <adapterID>.client		SAP System client, for example 100.
ume.r3.connection. <adapterID>.group *		Name of message server group, for example, PUBLIC.
ume.r3.connection. <adapterID>.msghost *		Message server host address, for example, server01.mycompany.com.
ume.r3.connection. <adapterID>.passwd		Password of the above user.
ume.r3.connection. <adapterID>.r3name *		Three-character code for SAP System, for example ABC. This is used to do a lookup in the sapmsg.ini file on the server to find the message server host address and message server group.
ume.r3.connection. <adapterID>.sysnr *		SAP System number, for example, 12.
ume.r3.connection. <adapterID>.user		User ID in SAP System with which the connection to the SAP System is set up. This user must have authorizations to use RFC, and to create/change/delete users in the SAP System. We recommend using the user ID SAPJSF. For details, see Requirements for Service User Used to Connect to SAP Systems.

* Enter one of the following combinations of entries for the SAP System:

· If you have a loadbalanced SAP System and the file sapmsg.ini is available on every portal server:

¡ ume.r3.connection.<adapterID>.r3name

¡ (optional) ume.r3.connection.<adapterID>.group

· If you have a loadbalanced SAP System and sapmsg.ini is not available on every portal server:

¡ ume.r3.connection.<adapterID>.r3name

¡ ume.r3.connection.<adapterID>.msghost

¡ ume.r3.connection.<adapterID>.group

· If the SAP System is not loadbalanced:

¡ ume.r3.connection.<adapterID>.ashost

¡ ume.r3.connection.<adapterID>.sysnr

Optional Properties

Property	Value	Description
ume.logon.r3master.adapterid	Default value is master.	Name of adapter ID that identifies a SAP System used as a user data store.
ume.r3.connection. <adapterID>.gwhost		Gateway host.
ume.r3.connection. <adapterID>.gwserv		Gateway service.
ume.r3.connection. <adapterID>.lang	Country code in upper-case.	Language with which the service user is logged on to the SAP system in the backend. This should be the same language that an administrator would use when logging on to the backend system using a SAP GUI. Defaults to SAP system user’s value. This setting is particularly important if the backend 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 backend system would not be displayed correctly in the UME user interfaces.
ume.r3.connection. <adapterID>.poolmaxsize	Default value is 10.	Maximum number of open connections in connection pool. The number of connections is limited by the memory size in the SAP system. Refer to the SAP Java connector documentation for details.
ume.r3.connection. <adapterID>.poolmaxwait	Default value is 10,000.	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. In this case the number should be increased.
ume.r3.mastersystem	For SAP Enterprise Portal, this value must be the system alias of the system object defined as reference system.	SAP reference system used for SAP user IDs in SAP logon ticket. Required for Single Sign-On with logon tickets to SAP Systems.
ume.r3.mastersystem. uid.mode	Default value is 1. 0 = Mapped user ID is used. If no mapped user ID is available, no value for the SAP user ID is written in the SAP logon ticket. 1 = Mapped user ID is used. If no mapped user ID is available, the portal user ID is written in the SAP logon ticket. 2 = Mapped user ID is used. If no mapped user ID is available, a user ID is generated and stored in the user mapping data.	Mode used to compute SAP user ID in SAP logon ticket. Only relevant for Single Sign-On with SAP logon tickets

Properties Required for Secure Network Communications (SNC)

Property	Value	Description
ume.r3.connection. <adapterID>.snc_lib		Path to library that provides SNC service.
ume.r3.connection. <adapterID>.snc_mode	0 = SNC disabled. 1 = SNC enabled.
ume.r3.connection. <adapterID>.snc_myname	p:<distinguished_name_ of_UME_SNC_PSE>	SNC name of SAP User Management Engine.
ume.r3.connection. <adapterID>.snc_partnername	p:<distinguished_name_ of_R/3_SNC_PSE>	SNC name of SAP System.
ume.r3.connection. <adapterID>.snc_qop	Value between 1 and 9	SNC level of security.

Properties Required If You Are Using Custom BAdis (Replication only)

Property

Value

Description

ume.r3.connection.
<adapterID>.receiverid

(Optional).

The BAdi implementation is mapped to this ID in the SAP system. See Configuring SAP R/3 System.

If you do not specify a value, the system uses the <adapterID> that you assigned to the SAP system.

ume.r3.connection.
<adapterID>.receiverid_guest

(Optional).

Use this property if you wish a separate BAdi implementation to be used for guest users. The BAdi implementation is mapped to this ID in the SAP system. See Configuring SAP R/3 System.