cancel
Showing results for 
Search instead for 
Did you mean: 

Warning when logon to user management.

Former Member
0 Kudos

Hi

I installed NW2004S abap+java. I know UME is automatically set to use the ABAP. When I access ume from the java side I always receive this message.

"A check if users can be created failed. The UME configuration might be inconsistent. Check your Security Policy settings (Especial "Maximum Length of Logon ID") and your Persistence Configuration"

Did anymore experience the same behavior ??

it's only a warning but how can I fix this ??

regards

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi guys

Sorry but both tips didn't worked....it was already set like that.

There is no real problem with the UME, I just want to remove this error when I logon.

any other tips ??

regards

former_member185864
Active Participant
0 Kudos

Hi Luc De,

Just follow below steps:

In case of ABAP+ Java stack; you should follow below steps:

1. Open Config tool:

C:\usr\sap\<SYSTEM ID>\JCxx\j2ee\configtool --> configtool.bat

Example: C:\usr\sap\Y76\JC03\j2ee\configtool --> configtool.bat

2. In Config tool: cluster-data>Global Server configuration>services--> com.sap.security.core.ume.service

3. set the values for below ume properties:

ume.persistance.data_source_configuration = dataSourceConfiguration_abap.xml

r3.connection.master.ashost = <backend system hostname>(ex: ls4079.wdf.sap.corp)

r3.connection.master.client = <enter clint number> (ex: 000)

r3.connection.master.sysnr = <system number>(ex: 09)

r3.connection.master.user = <comuser>(the sapjsf or communication user which we created in backend system)

r3.connection.master.password = <enter comuser password> ((it is the password of the comuser which is in the backend system)

ume.login.guest_user.uniqueids = <J2EE_GUEST>

login.ticket_portalid = yes (If administrator id length is more than 12 charcters ex: administrator)

: No (If administrator id length is less than 12 charcters ex: j2ee_admin)

Notes:

Creating users

J2EE_ADMIN,J2EE_GUEST and communication user(called as comuser).

User Name: -


User Type:

J2EE_ADMIN -


Diallog user

J2EE_GUEST -


Diallog user

COMUSER -


Communication user

-


NOTE 2:

User Name: -


Roles

J2EE_ADMIN -


SAP_BC_AI_ADMIN

J2EE_GUEST -


SAP_J2EE_GUEST

COMUSER -


SAP_BC_JSF_COMMUNICATION;SAP_BC_JSF_COMMUNICATION_RO

I think it is more helpfull for you; Please let me know if you have any doubts on this.

Thansk,

Nagaraju Parlapalli

Former Member
0 Kudos

Hi Luc,

I also faced the same problem. This would be the case if you have SPS 10 for your Java System.

The solution is as below:

1. Logon to the ABAP system, which the portal ume source is pointing to.

2. go to su01 and change user SAPJSF.

3. Add the role SAP_BC_JSF_COMMUNICATION and save it.

4. Restart the J2EE Engine.

After you execute the above steps, you will not be facing the problem.

Thanks and Regards,

Sailesh K

Former Member
0 Kudos

Hi,

go to http://xxx:5yyyy/useradmin

user this you have user managment consistency check

execute this

this give clear picture regarding UME conectivity

i think your issue is not serious issue

i guess some one has changed the configtool UME setings

Samrat