Configuring the UME to Use an AS ABAP as Data
Source
Use
Use this procedure to change the data source of the user management engine (UME) to the user management of an Application Server (AS) ABAP. This enables you to make use of user data stored in the ABAP system. Choosing an AS ABAP as the data source is also possible during installation of the AS Java.
Prerequisites
Restart Required
This procedure requires you to restart the AS Java, so you should plan for the required downtime while the AS Java restarts.
AS ABAP Version
The AS ABAP must be SAP NetWeaver Application Server 6.20 SPS 25 or higher.
Existing Users
Existing users in the AS Java database remain in the database after you configure the AS ABAP as the data source. When you log on to the AS Java, the UME searches both data sources simultaneously. Before you configure UME to use the AS ABAP as the data source, make sure the AS ABAP user management does not include any users with the same logon ID as users in the AS Java database. The UME refuses to authenticate any user with a nonunique logon ID.
The guest user of the AS Java must not exist in the AS ABAP. If the guest user logon ID exists in both systems, the AS Java cannot start. The UME property ume.login.guest_user.uniqueids identifies the guest user.
Existing Groups
Existing groups in the AS Java database remain in the database after you configure the AS ABAP as the data source. Before you configure the UME to use the AS ABAP as the data source, use transaction PFCG to check that there is no ABAP role with the same name as a group in the AS Java database.
Procedure
...
1. On the AS ABAP, create the system user for UME-ABAP communication.
a. Use transaction SU01 to create a user of type System and assign it one of the following roles:
■ For read-only access from the AS Java to the ABAP system, choose the role SAP_BC_JSF_COMMUNICATION_RO.
■ For read-write access from the AS Java to the ABAP system, choose the role SAP_BC_JSF_COMMUNCIATION.
b. Ensure that the role is assigned and generated.
Use transaction PFCG to generate the authorization profile and assign the user. See under the tabs Authorization and Users ® User Comparison.
For more information about assigning ABAP roles and generating profiles, see Assigning Users and Generating Authorization Profiles.
2. On the AS Java, start user management configuration.
For more information, see Configuring User Management.
3. Choose the Data Sources tab.
4. Choose Modify Configuration.
5. From Data Source, select ABAP System.
6. Choose the ABAP Server tab.
7. Enter connection data as required.
The table below lists the settings for configuring the connection to the AS ABAP.
General Connection Settings
Field Name |
Description |
User ID |
User ID in the AS ABAP with which the connection to the AS ABAP is configured.
We recommend using the user ID SAPJSF_<SID>. For more information, see Requirements for the System User for UME-ABAP Communication. |
Password |
Password for the user ID given above. |
Client |
AS ABAP client, for example, 100. |
System Language |
The AS ABAP sends any messages to the UME, for example error messages, in this language. By default the UME uses the language configured for the system user for UME-ABAP communication. |
Connection Pool Size |
Optional. Default value is 10. Maximum number of open connections in connection pool. The limit to the connections is limited by the memory size in the ABAP-based system. Refer to the SAP Java connector documentation for details. |
Wait Time (ms) |
Optional. Maximum time in milliseconds that an incoming request waits for a connection before throwing an exception. Default value is 10,000. 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, you should increase the number of connections. |
8. Set the indicator Connection to a specific application server.
9. Enter the application server data.
Specific Application Server Connection
Field Name |
Description |
Application Server |
Application server host address, for example, server02.example.com. |
System Number |
System number of the AS ABAP, for example, 12. |
10. Choose Test Connection.
If the test fails, go back and reenter the connection data and test the connection until you are successful.
11. Choose Save All Changes.
12. Restart the AS Java.
Result
The UME uses the AS ABAP as the data source. For more information about limitations of the AS ABAP as data source, see User Management of Application Server ABAP as Data Source.
We recommend that you configure SNC between the AS Java and the AS ABAP. For more information, see the following:
■
Configuring SNC: J2EE
Engine > AS ABAP
■
Configuring SNC
Between the UME and an ABAP-Based System
See also: