Defining UME
Data Source Properties in a Portal Tenant System 
Use
After you have created a portal tenant system (see Creating a Portal Tenant System), you need to define which SAP system the portal tenant will use for its user data. You define these settings in the object properties of the portal tenant system.
Prerequisites
· You have created a portal tenant system for your tenant.
· You are logged on to the portal as a system administrator.
· You have created a service user in the SAP system of the tenant's user store. You need a separate service user for each tenant.
This is needed to establish a connection between the ABAP client in the SAP system and the User Management Engine (UME). For detailed information, see Requirements for System User SAPJSF_<SID> in ABAP Systems.
Procedure
...
1. In the portal, navigate to System Administration ® System Configuration ® System Landscape. The System Landscape Editor is displayed.
2. In the Portal Catalog, locate the portal tenant system and open it.
3. In the Property Editor, display the properties in the User Management category.
4. Define the connection properties for the SAP system that the portal tenant will use for its user data. Certain properties are mandatory, other optional, and some depend on whether or not the SAP system is load balanced.
(i) Mandatory properties:
Property Name |
Description |
SAP client |
The client number of the SAP system, for example 100. |
Service logon user |
The user ID in SAP system with which the connection to the SAP system is set up. This user must have authorizations to use Remote Function call (RFC), and to create, change, and delete users in the SAP system. We recommend using the user ID SAPJSF_<client> or SAPJSF<logicalsystem>. For details, see Requirements for System User SAPJSF_<SID> in ABAP Systems. |
Service user’s logon password |
The password of the above user. |
(ii) Mandatory properties for a non- load balanced SAP system:
Property Name |
Description |
SAP application server |
The host address of the Application server, for example, server02.mycompany.com. |
SAP system number |
The number of the SAP system number, for example, 12. |
(iii) Mandatory properties for a load balanced SAP system:
Property Name |
Description |
Group of SAP application servers |
The name of the message server group, for example, PUBLIC. |
R/3 name |
The three-character ID of the SAP system, for example ABC. This is used to locate the host address and group of the message server in the sapmsg.ini file on the portal server. |
SAP message server host |
The message server host address, for example, server01.mycompany.com. |
SAP message server port |
Port of the message server. For detailed information on how to determine SAP message server ports, see the document TCP/IP Ports used by SAP Applications on SAP Service Marketplace at service.sap.com/network. Alternatively, you can look up the message server port in the services file on your machine. This file should contain an entry of the form: sapms<SID> <portnumber>/tcp, where <SID> is the three-character SAP system ID.
In Windows systems the services file is usually stored in the following location: <WinDir>\system32\drivers\etc\services. |
(iv) Optional properties (for both load balanced and non-load balanced systems):
Property Name |
Description |
Logon language used by the service user |
The country code in upper-case, for example EN. This is 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. It defaults to the 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. |
Debugging ABAP environment |
Provides debugging in the ABAP environment (SAP GUI) during an RFC call (for developer use only). |
Generates JCO traces for debugging purposes |
Specifies if JCo traces for debugging purposes are generated (for developer use only). |
Host name of the SAP gateway |
The gateway host. |
Maximum pool size for the connection pool |
The maximum number of open connections allowed in the connection pool. The number of connections is limited by the memory size in the SAP system. |
Maximum wait time for connection before timeout |
The maximum time in milliseconds that an incoming request waits for a connection before an exception is thrown. If an exception is 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. |
Path to library which provides SNC service |
The path to library that provides Secure Network Communications (SNC) service. |
Secure Network Connection (SNC) mode |
Specifies if SNC is enabled or not. Enter 0 or 1: · 0 = SNC disabled · 1 = SNC enabled |
Service number of the SAP gateway |
The gateway service. |
SNC level of security, 1 to 9 |
Specifies the SNC level of security. |
SNC name. Overrides default SNC partner |
Specifies the SNC name of the SAP UME (p:<distinguished_name_of_UME_SNC_PSE>). |
SNC partner, e.g. p:CN=R3,O=XYZ-INC,C=EN |
The SNC name of the SAP system (p:<distinguished_name_ of_SNC_PSE_of_ABAP_system>). |
5. Save your entries.
Result
You have created a system object for your portal tenant. Next, you need to create the tenant in the portal based on this system. See Creating a Portal Tenant.
At this point, the object properties in the Tenant category are empty. They will be assigned values automatically by the portal when you create the portal tenant.
Example
The following properties represent those required for a load-balanced SAP system:
Property |
Value |
Group of SAP application servers |
PUBLIC |
Logon language used by the service user |
EN |
R/3 name |
ABC |
SAP client |
100 |
SAP message server host |
abc.mycompany.com |
SAP message server port |
3610 |
Service logon user |
SAPJSFABC100 |
Service user’s logon password |
<password> |