Changing the AS for ABAP Backend System (SAP Library

Changing the AS for ABAP Backend System

Use

Once you have installed the UME with ABAP user management, you cannot change the data source configuration anymore. (Exceptions exist for systems installed with data source configuration files from previous versions. See SAP Note 718383.) However, you can change which AS for ABAP system the UME connects to.

Caution

Consider such a switch only if you have not yet created assignments in the UME, or if you are sure that the new AS for ABAP system contains those users that were already present in the old AS for ABAP system. We recommend that you plan carefully and install the UME with the AS for ABAP system you intend to use the UME with, whenever possible.

Prerequisites

Note the values of the following UME configuration properties:

· ume.login.guest_user.uniqueids

· ume.login.r3master.adapterid

Default value is master.

The new AS for ABAP system must meet the following requirements:

· The system user for communication between the UME and the AS for ABAP system must be prepared.

The system user, whose name is entered in the property ume.r3.connection.<adapterid>.user, exists in the new AS for ABAP system, and has the correct password entered in the property ume.r3.connection.<adapterid>.password. In both cases, <adapterid> refers to the value of ume.login.r3master.adapterid. This user is assigned to the communication role, either SAP_BC_JSF_COMMUNICATION_RO or SAP_BC_JSF_COMMUNICATION. Check in the transaction SU01 under the tab Profiles, to see if the profile has been generated for this role.

· The guest user for the UME and the AS for ABAP system must be prepared.

The user, whose name is entered in the property ume.login.guest_user.uniqueids, exists in the new AS for ABAP system, and is assigned to the role SAP_J2EE_GUEST.

Caution

If any of these requirements are not met, the AS for Java server will not start after the change.

Procedure

Se...

1. Set the R3 connection properties to address the new AS for ABAP system. This usually requires changes to at least the following properties:

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

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

¡ ume.r3.connection.<adapterid>.client

¡ ume.r3.connection.<adapterid>.user

¡ ume.r3.connection.<adapterid>.password

The variable <adapterid> refers to the value of ume.login.r3master.adapterid. The user and password properties should already have been configured in the prerequisites.

2. Save the changes in the J2EE Engine Config Tool, and restart the J2EE Engine.

Result

All users in the new AS-ABAP system, who have been assigned to the role SAP_J2EE_ADMIN have administration rights for the J2EE engine.

If you already have made assignments of AS for ABAP users from the original system to UME roles or local UME groups, and these users do not exist in the new AS for ABAP system, the cross references in the UME are inconsistent. The UME system behavior is undefined when using these objects.