JRA Authentication Problems

[Former Member]

Hi,

I need to access some BAPIs from a J2EE Web Application. Because I have never worked with JCo so far, I decided to give JRA a try. I have worked my way through the <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/ea/62eaada93611d6b28600508b5d5211/frameset.htm">SAP Library</a> and the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d3ba4">JRA tutorial</a> but couldn't manage to get my test application to run properly.

The scenario is as follows.

I have a user on the "BAPI System", who has all necessary rights to access the BAPIs. The JRA Connector on the WebAS should always use this user, when a BAPI is called. I have tested the four authentication methods which are provided by JRA with different configurations, but none has worked so far.

The "best" error message I've got was like "Couldn't create ManagedConnection with . {jco.client.passwd=****, jco.client.lang=DE, jco.client.sysnr=53004, jco.client.client=001, jco.client.ashost=server, jco.client.user=User, jco.client.type=A, jco.client.jra_conn=true}" when I used "Configured Identity" as the authentication method.

I'd appreciate any help. It would be nice to be able to use JRA.

Tino

[Former Member]

Hi,

Refer this u will get some idea

/people/tarun.telang2/blog/2005/10/01/debugging-a-rfc-call-using-jco-api

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2a9dbe90-0201-0010-b283-a56f6453...

Regards,

Beevin.

[Former Member]

Tino,

Refer to the following guide.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d...

Rgds,

Amol

[Former Member]

Amol,

I have already read the JRA tutorial and followed the steps described in there. But it definitly doesn't work for me.

And I could not find any information about the JRA authentication process.

Tino

[former_member182294]

Hi Tino,

The system number you are passing is wrong, generally system name is two char length.

<i>{jco.client.passwd=****, jco.client.lang=DE, jco.client.sysnr=<b>53004</b>, jco.client.client=001, jco.client.ashost=server, jco.client.user=User, jco.client.type=A, jco.client.jra_conn=true}" when I used "Configured Identity" as the authentication method.</i>

And also make sure that you will be able login to SAP with the same system details mentioned above.

Regards

Abhilash

[Former Member]

Abhilash,

thank yor for your hint. I have changed the sysnr into 01 and the connection with JCo worked fine. I got access to the BAPIs I wanted.

But I'm stll not able access the SAP System by using JRA. The error message is still the same.

Tino

[former_member182294]

Tino,

The error is due to incorrect information only. Did you restart the server after chaning the system number? And also check all required host entries there in server host file.

Regards

Abhilash

[Former Member]

Abhilash,

I have restarted the server but the error message is still thrown. What do you mean with "server host file"? I have set the properties in "Managed Connection Factory" and couldn't find other configuration forms for the connection factory.

Thank you,

Tino

[Former Member]

you will either need to re-deploy a new Connection Factory instance i.e. redeploy JRA or reconfigure the existing one. Did you try the exisiting instance changes in Visual administrator?

[Former Member]

Amol,

I re-deployed and reconfigured the JRA Connection Factory but none has worked so far. How am I supposed to test the JRA instance in the Visual Administrator? I have checked that the instance is always running and that it uses the latest property values.

Thank you,

Tino

[Former Member]

Hi Tino,

I am also getting the same error. I followed all the steps for configuring JRA but it's giving same error. Did you able to solve the problem? If yes can you tell me what is the problem?

Thank you

cheers

Jayant

[Former Member]

Jayant,

I was not able to get JRA running so I had to switch JCo because the of time reasons. If you are able to fix this, please give us a note about it.

Bye,

Tino