Specifying the ABAP Engine Information in the UME Properties (SAP Library)

Specifying the ABAP Engine Information in the UME Properties

Procedure

In this step, you specify the ABAP Engine’s connection information in the UME properties. There are two variants: using logon groups or using the host name and system number. See the tables below.

Properties When Using Logon Groups

Property	Value	Comment
ume.persistence.data_source_ configuration	dataSourceConfiguration_ r3_roles_db.xml
ume.r3.connection.master.user	<Communication_user>	Default= SAPJSF
ume.r3.connection.master.passwd	<Communication_user_ password>
ume.r3.connection.master.client	<ABAP_Engine_client>
ume.r3.connection.master.msghost	<ABAP_Engine_message_ server_host_name>
ume.r3.connection.master.r3name	<ABAP_Engine_SID>
ume.r3.connection.master.group	<ABAP_Engine_logon_group>	Default= PUBLIC
ume.login.guest_user.uniqueids	J2EE_GUEST	Specify the user ID to use for the guest user.

Properties When Using Host Name and System Number

Property	Value	Comment
ume.persistence.data_source_ configuration	dataSourceConfiguration_ r3_roles_db.xml
ume.r3.connection.master.user	<Communication_user>	Default= SAPJSF
ume.r3.connection.master.passwd	<Communication_user_ password>
ume.r3.connection.master.client	<ABAP_Engine_client>
ume.r3.connection.master.sysnr	<ABAP_Engine_system_ number>
ume.r3.connection.master.ashost	<ABAP_Engine_application_ server_host_name>
ume.login.guest_user.uniqueids	J2EE_GUEST	Specify the user ID to use for the guest user.

After changing the properties, stop and restart the SAP J2EE Engine.

For more information about the properties, see the UME properties for Structure link SAP R/3 Data Source in the Reference Manual.

Example

The following example shows the corresponding sections of the UME property file using logon groups. The logon group is PUBLIC, the message server host is msg01. The system ID is ABC and the client is 100. The user to use for the connection is SAPJSF whose password is jsfpass for this example. The guest user is J2EE_GUEST.

Note

This is only a subset of the UME parameters contained in the UME property file.

Sample UME Property File

##xml file that configures the persistence, roles are coming from the pcd
ume.persistence.data_source_configuration=dataSourceConfiguration_r3_roles_db.xml

###############################################################################
#    R/3 settings (for use as Master datasource)
###############################################################################

### Start of Required keys for R/3 connection
ume.r3.connection.master.client=100
ume.r3.connection.master.user=SAPJSF
ume.r3.connection.master.passwd=jsfpass
ume.r3.connection.master.sysnr=
ume.r3.connection.master.useXML=false
## R/3 application name (only CRM and EBP are supported)
ume.r3.connection.master.application=
### End of required keys

### Start of required-optional keys
### One of following 3 options is required:
### Option 1: application host name

ume.r3.connection.master.ashost=

### Option 2:  (name used to map to the sapmsg.ini file.)
#ume.r3.connection.master.r3name=ABC
### Option 3: message server
ume.r3.connection.master.msghost=msg01
### Required when options 2 and 3 are used  (e.g. PUBLIC)
ume.r3.connection.master.group=PUBLIC

### End of required-optional keys

### Start of optional keys
ume.r3.connection.master.lang=en

### number of connections to create in the connection pool
ume.r3.connection.master.poolmaxsize=10

### Time in milliseconds to wait for available connection before error
ume.r3.connection.master.poolmaxwait=10000

ume.superadmin.activated=true

### Comma-separated list of guest users that are supported.
These users must exist with this unique ids in the user repository.
This parameter does only take effect if ume.login.anonymous_user.mode=1

ume.login.guest_user.uniqueids = J2EE_GUEST

Continue with Activating the UME Administrator and Deactivating SAP*.