Skip to Content
0
Former Member
Jan 25, 2010 at 09:29 AM

Ume-Connection set to an old value and to state "final" by Java-Patch

30 Views

Hi everyone,

i have got a very strange and also very hard to solve problem with a PI 7.10 non-central Adapter Engine. (DEV-System)

This System was installed very quick as the result of an emergency change, so i had very few time to read guides and notes.

I used a configuration guide by SAP as a hint and due to this, did try to refer the AE's UME to central PI's ABAP User Management. When i realized it did not work, having few time, i switched the user management back to JAVA UME.

When i installed QAS- and PROD-Systems, i did refer them to their local user management directly, so they dont suffer the problem.

Since this system was immedeatly needed, i had no chance to patch it right after installation.

Last week, i managed to get a downtime to implement some JAVA- and Kernel-Patches on this System.

After the patches where implemented, the system was started and seemed to be ok.

When i wanted to test the needed applications, i hit some problems with my personal User.

I managed to logon with the user "administrator", but had to notice the UME configuration was twisted and there was no user management possible on the system.

Using the config tool, i found out the User Management was refered to the central PI's ABAP Stack.

Furthermore, i could not change this configuration to local java.

Using the configuration editor mode, i figured out that not only the reference was changed, but also there was set a "final"-flag which i could not remove by any means.

I am aware of a sapnote which says its not possible to change an abap-reference back to local java user management, but since i did it without problems before, i thought maybe i could do it once again.

So now i am looking for a way to get rid of that "final"-flag, at best without having to recover the system.

Anyone got any hint for me?

Regards,

Jürgen