Introduction
There is currently a lot of documentation available on this topic but the goal of this wiki is to pull all the information into one place and hopefully after reading this wiki you will have all the knowledge you need to configure your SAP Netweaver JAVA system (AS Java) to use an R/3 (ABAP) system as a user store.
Firstly I should point out though that if your current user store is not the internal ume store it is not supported. (I should also say that it is possible if you follow this wiki but its still not supported). See SAP Note 718383 for more details.
I have chosen to use the offline method as it is very straight forward as detailed in the following help documentation:
Step 1: Creating the J2EE_ADMIN, J2EE_GUEST and SAPJSF on the R/3 client
Log on to the R/3 client and run the SU01 transaction. Here create the user's and give them the following roles:
User
|
User Type
|
Role
|
|---|---|---|
J2EE_ADMIN
|
dialog
|
SAP_J2EE_ADMIN
|
J2EE_GUEST
|
dialog
|
SAP_J2EE_GUEST
|
SAPJSF
|
system
|
SAP_BC_JSF_COMMUNICATION
|
If the roles SAP_J2EE_ADMIN and SAP_J2EE_GUEST do not exist simply create them, they do not contain any ABAP authorizations so you do not need to generate their profiles. For SAP_BC_JSF_COMMUNICATION you have to insure its profiles been generated (Transaction PFCG) . See the following link for more information:
Step 2: Editing the Ume parameters via the Configtool
Next we need to point the AS Java system to the relevant ABAP client and let it know the user and password needed to communicate with the ABAP system. There are several ways of doing this, I will use the direct connection method. You can't use a mixture of methods so I will recommend setting some parameters to default even if they appear empty. The exact ume parameters that need set:
No comments:
Post a Comment