Java 7.31 doesnt start because of UME-problem

[denny-k]

Hi experts.

After a simple systemcopy of one of our Abap-Systems the Java-system (using this ABAP as UME) cannot start anymore.

I recreated the communication-user SAPJSF_JAK in ABAP-System.

But get the message wrong password, wrong credentials..

   Return code: RFC_SYS_EXCEPTION(3)

    error group: 104

    key: RFC_ERROR_SYSTEM_FAILURE

Exception raised by HRK|saphrk

    message: Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)

    Return code: RFC_SYS_EXCEPTION(3)

    error group: 104

    key: RFC_ERROR_SYSTEM_FAILURE

Exception raised by HRK|saphrk

I found notes to edit the UME offline in configtool.

I choosed the following way in configtool:

Editmode -> cluster-config - system - custom global - cfg - services - com-sap.security.core.ume.service - propertysheet properties

Here i changed the password for

ume.r3.connection.master.PartnerLDAPAdminPassword

Is that correct? I changed it, saved it, but dont get success with it.

Thanks in advance

[divyanshu_srivastava3 · Accepted solution]

Refer;

UME Properties for an AS ABAP Data Source - Using Java - SAP Library

Also for ABAP as data source:

Always set:

○  ume.r3.connection.master.passwd

○  ume.r3.connection.master.user

connect to a specific application server:

○  ume.r3.connection.master.ashost

○  ume.r3.connection.master.sysnr

[denny-k · Accepted solution]

As it was a systemcopy of an abap-system and we didnt change something on the java-system i think i must only change the password?

[divyanshu_srivastava3 · Accepted solution]

Also,

Check:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c06489af-883f-2f10-318c-db80892b7...

Your data source is ABAP, not DB or LDAP, so adjust the parameters accordingly.

ume.persistence.data_source_configuration: dataSourceConfiguration_abap.xml
ume.login.guest_user.uniqueids: J2EE_GUEST
ume.r3.connection.master.client: < Backend client to which the J2EE has to be connected >
ume.r3.connection.master.msghost: <Message server of the R/3 server).
ume.r3.connection.master.r3name: <SID>of the R/3 server.
ume.r3.connection.master.user: SAPJSF (make sure that the SAP_BC_JSF_COMMUNICATION should
be assigned in the backend R/3 and in the right client).
ume.r3.connection.master.passwd: <password of the SAPJSF user

Divyanshu

[divyanshu_srivastava3 · Accepted solution]

The client in which your have SAPJSF(generally 001) is the source R3 system for JAVA.

Divyanshu

[denny-k · Accepted solution]

I dont have this entries.

[denny-k · Accepted solution]

Yes. SAPJSF is in our 010 and exists. After starting Java it is locked, so this works nearly 😉

[divyanshu_srivastava3 · Accepted solution]

Ok this means your java is 7.3 or above.

I am sorry, missed that

Now, you have to goto

Login to the Configtool-> switch to the configuration editor mode

(click on edit mode) ->configurations-> destinations -> RFC -> Propertysheet <Destination Name> and add the details of the backend server.

Refer that same link -

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c06489af-883f-2f10-318c-db80892b7...

Divyanshu

[denny-k · Accepted solution]

wow, amazing. Thanks for your help!

Also for your great help with the errors after the Reinstallation of DAA.

The only thing that still doesnt work ist the Byte Code Adapter Installation (Point 7, managed System configuration).

It still dont get the right directory.

[denny-k · Accepted solution]

Okay. I copied the directory from another java-system.

[Sriram2009]

Hi Dennis

1. Have you completed the post system copy steps?

2. For Java stack are you maintenance the 001 or any other client?

Regards

Sriram

[denny-k]

Yes. Everything works fine. We did many systemcopys of abap-system but this was the first with a connection to a java-system. So Im not sure what could also be effected.

Abap-system uses 010 and Java the standart client.

[divyanshu_srivastava3]

Hi Dennis,

Can you share the default and application trace ?

Divyanshu

[denny-k]

Hi Divyanshu,

you are everywhere, right? 🙂

can you tell me the filename of this traces?

thanks

[divyanshu_srivastava3]

Goto location:

/usr/sap/SID/JXX/j2ee/cluster/server0/logs.

here you will find the error logs in default trace and application logs.

Anyway, to configure UME from configtool use below parameters.

If your JAVA stack is UP and running then you can goto useradmin and configure UME.

However, when access to UME is denied JAVA won't start as core UME service is halted(check dev_server0 and std_server.our for error on this.)

Divyanshu

[divyanshu_srivastava3]

For properties in configtool:

Also for ABAP as data source:

Always set:

○  ume.r3.connection.master.passwd

○  ume.r3.connection.master.user

connect to a specific application server:

○  ume.r3.connection.master.ashost

○  ume.r3.connection.master.sysnr

Divyanshu