Hi,
I'll try to explain my situation as best as I could:
I've an ECC5.0 ABAP test system, and I have installed EP on a standalone Java using Rapid Installer. During the installation, rapid installer installed the BP for ess. At that time, rapid installer created the ess user (which I named as ess_user) in the Java UME db, corresponding to an user with the same userid (ess_user) in the ABAP backend (which I have created prior to the installation) for SSO.
After I've installed the portal on a standalone Java. I suddenly wanted to change its user management datasource configuration to use the ABAP backend instead of the Java UME db.
After I changed the datasource, there are two users with the identical 'ess_user' id: one existing in the Java UME db and the other existing in the ABAP backend. I know that if I use the ABAP datasource configuration, having two users with the same userid on both the Java UME and the ABAP will result in an user authentication failure if I try to login to the j2ee (and the portal) with that userid. So I must delete one or the other.
1) Will this work:
I will delete ess_user from the Java UME, and then using the portal user administration, I will assign the ABAP ess_user portal roles that were originally assigned to the Java ess_user.
Then, I will configurate the JCo connections using the Web Dynpro Content Administrator to connect to the systems via SSO.
Now, when I login to the portal using ess_user (from the ABAP), it will be logged in as a portal user (with its portal roles), and at the same time (from SSO), sees itself as it's own backend user. Will ess work if the user configurations are set this way? Or is there a better way?
2) Just to double-check, what ABAP roles/profiles should the ess user of the backend have?
this is quite urgent, points will be generously awarded
Thanks,
Charles