2013 Aug 31 6:14 PM
Greetings Everyone!
I can't call an external RFC function from Abap, let it be in Java and located at the backend, on my local machine.
I've followed the steps from the JCo server programming example and faced with the RFC destination customizing issue, in SM59.
The problem is that I can't register a program at the Gateway interface. I'm not sure, but maybe I don't have enough rigths because
the test connection involving SERVER_EXEC was failed. I'm on SAP_BASIS 702 and NWDS 7.01
So, the questions are:
1. If it is possible in general to call external RFC function without registering it on the Gateway?
2. Is this the only way to call RFC module - using JCo?
3. I saw some examples using JCo and Java Resource Adapter from Java but how it is possible to use these connectors from Abap?
Maybe advise me a direction to move to.
Best regards,
Andriy
2013 Sep 01 6:13 AM
Greetings Everyone!
I can't call an external RFC function from Abap, let it be in Java and located at the backend, on my local machine.
I've followed the steps from the JCo server programming example and faced with the RFC destination customizing issue, in SM59.
The problem is that I can't register a program at the Gateway interface. I'm not sure, but maybe I don't have enough rigths because
the test connection involving SERVER_EXEC was failed. I'm on SAP_BASIS 702 and NWDS 7.01
So, the questions are:
1. If it is possible in general to call external RFC function without registering it on the Gateway?
2. Is this the only way to call RFC module - using JCo?
3. I saw some examples using JCo and Java Resource Adapter from Java but how it is possible to use these connectors from Abap?
Maybe advise me a direction to move to.
Best regards,
Andriy
2013 Sep 01 5:53 AM
Hi Andriy,
Check below Screen Shot ,are you maintain 'rfcexec' in program name ?
then test your RFC destination , you getting below message .
Check this link ...SAP Library - TREX - Configuration Documentation
Program Name : <disk_drive>:\usr\sap\ECC_<instance_number>\rfcexec.exe
Gateway Host : Host name (with domain name if necessary) or
the IP address of the host on which the gateway is installed.
Gateway Service: Name of the gateway in the form sapgw<instance_number>
Regard's
Smruti
2013 Sep 01 10:33 AM
Yes Smruti, program name is maintained.
But when checking connection I've got errors:
I can't go through the steps in link because don't have access to the server. But I've checked a gateway in transacrion SMGW and I can see a registered programs there, so I suppose it works
Regards,
Andriy
2013 Sep 01 6:13 AM
2013 Sep 01 12:20 PM
Hi, Arun,
It seems to me that this article is very close to my requirement but I see confusing parts. Maybe You have an idea. First, it's strange that it's stated "SAP JCo can be used for the internal communication of SAP NetWeaver AS".
Now, I've implemented a logic involving Java proxy for ABAP RFC FM, it calls Abap FM and it works fine. It's connected to the Abap by JCo, and here, I indicate system's connection properties as for common RFC connection. But in reverse way I suppose I should call a Java RFC FM and indicate some destination.
What destination/connection it should be? How system will know that some RFC-enabled Java FM is available on my local machine and call exactly this FM? I saw only one similar example where Java application listen to the inbound connections in a loop. Any ideas/suggestions?
Regards,
Andriy
2013 Sep 01 2:06 PM
hi Andriy
please check this post which has got the same error condition as yours.
http://scn.sap.com/thread/1694586
http://scn.sap.com/thread/3312184
You may also go to smgw and enable trace on CPIC to try and get more details.
Thanks and regards
Arun
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |