RFC from Web Dynpro through PI

[h_deleeuw]

We want to import a function module as an adaptive RFC model in a web dynpro application and route its call through the PI RFC adapter (sender communication channel).

The JCo connections which are created during the model generation are pointing to the abap stack, also it is not possible to enter the program id which is required in the RFC sender comm. channel.

Does anyone know if this is possible?

We already did this using a web service generated from a PI interface and the soap adapter.

Any suggestions will be highly appreciated.

[Former Member · Accepted solution]

Hi !

To do this, try to first create the RFC-XI-XXXX scenario in PI, using the RFC sender adapter and creating the "dummy" rfc function module in the ABAP stack of XI. Once it is working, then you should be able to call that dummy rfc from the webdynpro rfc adaptive model as this RFC is like any other in the abap stack of the application server.

Check these links for rfc sender scenarios

/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

for reference, what you should create is a function module like the one in the first blog, called "ZRFC_READ_TABLE_EOFM".

Regards,

Matias

ps: please award points if helpful.

[h_deleeuw · Accepted solution]

Hi,

Thanks for your reply, but the problem is that we want the web dynpro to direct its RFC call to the XI RFC sender communication channel.

When you import a function module as a model in WD, it generates 2 connections, 1 for the metadata and 1 to do the call, this call is executed on the abap stack. We want this call to be done to the RFC adapter.

[Former Member · Accepted solution]

Hi !

Calls cannot be made directly to the RFC sender adapter. You should create a dummy RFC function module within an abap stack (ECC or PI) and make the webdynpro call that one as if it is calling a standard BAPI. Then the RFC sender configuration will help to the detection of that the parameter data sent via the dummy RFC execution should be directed to PI and the data will enter the Integration Server.

You must create an RFC - XI - something scenario first to understand what I'm saying or read a complete walkthru abous this kind of scenario. Who is the "triggerer" of the RFC is another story, it could be a report in ABAP or a Webdynpro.

Regards,

Matias.

[h_deleeuw · Accepted solution]

"Calls cannot be made directly to the RFC sender adapter."

That's what we were afraid of.

We already thought about the other scenario's you mentioned and think that these are not very appealing.

Thank you for effort.