Use this procedure to switch the data source of the user management engine (UME) from one ABAP system to another. You can also use this procedure to change the client used by the UME; however, if the new client is an exact copy of the old client you can use the shortened procedure.
More information: Changing the ABAP Client for the UME After a Client Copy.
Consider changing the back end only if you have not yet created assignments in the UME, or if you are sure that the new AS ABAP system contains those users that were already present in the old AS ABAP system. If there are users and roles in the old AS ABAP system, which do not exist in the new AS ABAP system, applications in the AS Java that refer to those users and roles may no longer function as expected.
We recommend that you plan carefully and install the UME with the AS ABAP system you intend to use the UME with, whenever possible. If this is not possible, try to change the back end as soon as possible after installation. This reduces the likelihood of inconsistencies due to changes to users and roles.
· This procedure requires you to restart the AS Java. Plan for the required downtime while the AS Java restarts.
· The new ABAP system must be SAP NetWeaver AS 6.20 Support Package Stack 38 and higher.
1. On the AS Java, use identity management determine the identity of the following users in the UME:
¡ Guest user
Use identity management to search the built-in user group anonymous users. The default logon ID is J2EE_GUEST.
¡ At least one administrator user
Use identity management to find a user with an administrator role.
More information: Identity Management.
2. Determine the identity of the system user for UME-ABAP communication.
View the logon data of the destination UMEBackendConnection. The default ID is SAPJSF.
More information: Maintaining RFC Destinations.
3. Determine if the users identified above appear in both the old and new ABAP systems.
Use transaction SU01 to determine if each of the users identified above appear in the new ABAP system. If the users appear in the new ABAP system, then make sure that the role assignments for the users are named exactly the same as in the old ABAP system.
If you configured the RFC destination UMEBackendConnectionForChanges, one of your administrator users should have the ABAP role SAP_BC_JSF_COMMUNICATION_NAMED in addition to any administrator roles.
4. Prepare the system user for UME-ABAP communication in the new system.
○ Ensure the password for the system user is the same in both ABAP systems.
If you cannot remember the password for the system user, create a new password in the new ABAP system and change the password in the RFC destination UMEBackendConnection of the AS Java.
○ Ensure that the roles assigned to the system user in old ABAP system are assigned and generated in the new ABAP system.
Use the transaction PFCG to check the status of the roles under Authorizations and User ® User comparison. The status indicators for these tabs should be green.
If a status indicator is not green you must regenerate the profile and perform a user comparison as needed.
5. On the AS Java, maintain the settings for the RFC destination UMEBackendConnection.
Survey the settings. Change the settings to connect to the new AS ABAP system. You are likely to need to change at least the following connection settings:
○ Application Server
○ System Number
If you configured the RFC destination UMEBackendConnectionForChanges, you must also maintain the connection settings for this destination.
6. Choose the Ping Destination pushbutton.
If the test fails, go back and reenter the connection data and test the connection until you are successful.
7. Save your entries.
8. Restart the AS Java.
The AS Java uses the new AS ABAP as the data source.
There may be other destination you want to reconfigure to point to the new AS ABAP, such as the RFC destination for time zone mapping I18NBackendConnection.
More information: User Management of Application Server ABAP as Data Source.