Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Trace J2ee_admin user lock

Former Member
0 Kudos

Hi ,

In our production WAS 7.0 server, J2ee_admin user is getting locked frequently and everytime we need to unlock the user from abap engine . From SUIM(user change records) its showing as the userid got locked by J2EE_ADMIN itself.

I have searched the user actions from sm20 and j2ee security log (from /usr/sap/sid/DVEBMGS*//j2ee/cluster/server0/log/system), but didn't get any useful result.

Do we have a tool/method available in J2ee engine which is equvalent to sm21 security audit log? Basically i need to find the terminal/program which is locking the j2ee_admin userid.

Thanks

Aby

1 ACCEPTED SOLUTION

former_member432219
Active Participant
0 Kudos

When the UME is configured to use the ABAP system as its datasource, when users logon to applications such as Enterprise Portal for example, the user change logs in SM20 will not show the userID of the user that logged on. The user that will be recorded in SM20 for this logon to the java application is the UME communication user. This is the user that is specified for ume.r3.connection.master.user

See: http://help.sap.com/saphelp_nw2004s/helpdata/EN/84/10594aecd3e1408845e66c432b955e/content.htm

This user should be 'sapjsf'. However if you have mistakenly set J2EE_ADMIN as the value for

ume.r3.connection.master.user this would explain what you see in the SM20

4 REPLIES 4

Former Member
0 Kudos

This message was moderated.

former_member432219
Active Participant
0 Kudos

When the UME is configured to use the ABAP system as its datasource, when users logon to applications such as Enterprise Portal for example, the user change logs in SM20 will not show the userID of the user that logged on. The user that will be recorded in SM20 for this logon to the java application is the UME communication user. This is the user that is specified for ume.r3.connection.master.user

See: http://help.sap.com/saphelp_nw2004s/helpdata/EN/84/10594aecd3e1408845e66c432b955e/content.htm

This user should be 'sapjsf'. However if you have mistakenly set J2EE_ADMIN as the value for

ume.r3.connection.master.user this would explain what you see in the SM20

0 Kudos

Hi Patrick,

Thanks for the reply. We have already given a communication userid in the parameter "ume.r3.connection.master.user".

The reson for me to suspect the lock is happening from the j2ee engine side, is due the unavailabilty of J2EE_ADMIN information in abap seucrity log(sm20).

Do we have any other methods to find the cause of the lock?

Thanks in Advance

Aby

Former Member
0 Kudos

I had a simular issue with J2ee_admin locking on our solman system and I had changed the ABAP and secure store passwords.

My issue was fixed when I realised someone had set the SLD user to J2ee_admin in a remote system.

Basically: TX. sldapicust shows you the user to connect to the SLD, (which is on our soman box). and you can set the password here.

When I changed that, it stopped locking.

Not sure if your issue is exactly the same, but worth checking out non the less.