Exception by Configuring UME

[Former Member]

Hello,

I am using CE 7.1 SP5. Today I tried configuring the UME of my local system to use an AS ABAP as data source.

I want to do this, because my SSO between my local system (which should be a producer portal) and the consumer portal is still not working. Consumer Portal is using ABAP as data source for UME. So I will need this ABAP data source in my local UME too. Is this correct?

But when I tried configuring the UME I got the following exception:

"Guest user ids are not unique, found multiple objects for Guest -- UACC.PRIVATE_DATASOURCE.un:Guest - UACC.R3_DATASOURCE1710375.GUEST"

How can I correct this mistake?

Best Regards,

Iris

[ravi_joseph]

fpn requires same user data source,

can u rename the guest user id (in the Abap datasource) and try configuring,

jo

[Former Member]

Hello Ravi,

I can´t rename the guest-id in the ABAP-Source because I haven´t administration rights in this SAP-System which contains the ABAP-Source. And I didn´t know if this would be very smart, because there are many other systems which also use this ABAP-Source.

But I have searched for the guest-ids in the ABAP-Source. There are only two of them: one with the name GUEST and an another with the name J2EE_GUEST. On my local system I have only GUEST. Now I have tried a way out of this problem simple by deleting the GUEST-User-Id in my local system.

But I still got the same exception. Could the J2EE_GUEST-id in the ABAP-Source be responsible for this?

Regards,

Iris

[ravi_joseph]

by deleting the GUEST-User-Id in my local system.

you are not supposed to delete the guest id in the local system as some of the portal services will be accessed by guest user,

http://help.sap.com/saphelp_nw04s/helpdata/en/9f/d770424edcc553e10000000a1550b0/frameset.htm

I suggest you to play with the ABAP source guest user id.

jo

[Former Member]

Hello Jo,

ok now I have found an inconsistency in the ABAP-Source. (One attribute there has to been deleted.)

I have corrected this and after a second check now there are no more inconsistencies in the ABAP-source.

But when I change the configuration of the Identity-Management on my local system, I still get an

exception.

Now it is: "Validation failed. Configuration not saved. Technical Details"

But there is not explained where I can find this technical details? And so I have no idea why validation failed again.

Do you have an idea which can cause such an exception?

Regards,

Iris

[ravi_joseph]

u have ur guest user back in ur local system? and u can check this details in the defaulttrace files of the system, pls post the error.

check this link accordingly

http://help.sap.com/saphelp_nw70/helpdata/DE/8f/67d27676ace84080964d4c4223bb3c/frameset.htm

Jo

[MichaelShea]

Hi Iris,

I would suggest going through this procedure:

http://help.sap.com/saphelp_nw04s/helpdata/en/9e/fdcf3d4f902d10e10000000a114084/frameset.htm

-Michael

[Former Member]

Hello Michael,

your link is exactly the procedure I was going through. This procedure has caused the described exception as result.

Sorry, but this link doesn´t help.

Regards,

Iris

[Former Member]

Hello Jo,

yes I have my guest-user back. And I checked your link already yesterday. Every requirement for the System User for UME-ABAP Communication is configurated correctly.

But thank´s for the hint with the trace file. I am new in SAP development and haven´t think about this before.

The error in the trace file is:

" Cannot get aliases for application.

The error is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/tc_lmitsam_coui_xichannel~wd is not deployed on cluster element get its aliases and it is not possible to .00123FB5BB32001B0000005E00000EA00111C7EF7A01A516"

A few minutes ago one colleague told me that XI is down today. Maybe this could be the reason for this exception?

Regards,

Iris

[MichaelShea]

Hi Iris,

The first problem you ran into was because you did not follow the ´prerequisites regarding existing users. The guest user defined by ume.login.guest_user.uniqueids existed simultaneously in the database and in the back-end ABAP system. So it is obvious that you did not follow all of the steps of the procedure as laid out. OK, you solved that by deleting the guest user in your local system.

Now you have encountered another error. Odds are that your connection data is incorrect (wrong client, wrong system user for communication data, target system is down, network connection problems).

As I am writing this, you found the default trace suggested by Jo. Is this XI system the one you want to connect to? If the system is down, then the configuration cannot be successful with the UI. There is an offline configuration method, but I would not recommend it if you are new to the AS Java. You can make your system unstartable. But then again, since the guest user no longer exists in your system and the ABAP system you want to connect to might be down, your system is unstartable anyways.

Offline Configuration of the UME for AS ABAP

-Michael

[MichaelShea]

You can restart your system with the emergency user SAP* and readd the guest user until you have the ABAP system back up.

[Activating the Emergency User|http://help.sap.com/saphelp_nw04s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm]

-Michael