Skip to Content
0
Former Member
Apr 15, 2005 at 12:09 AM

Problem of accessing R/3 BAPI_FLIGHT_GETLIST because RFC Metadata was retri

35 Views

When I run the flight web dynpro application to access BAPI on R/3 IDES client, I get this error bellow.

Accessing System ER2 is not possible because RFC Metadata was retrieved using System X01. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!

I have checked SLD connection is OK, and JCO destinations OK in web dynpro content administrator.

ER2 is my version 4.7 enterprise R/3 system and X01 is XI 3.0 system. ER2 runs on ABAP Web AS 6.20, while X01 is running on dual stack ABAP/Java Web AS 6.40 and J2EE 6.40.

In the beginning I configure JCO destinations using XI client in connection property. Later I find out no flight data loaded in XI client. So I use R/3 IDES client which has flight data. Thus I modify the connection properties of JCO destinations.

Then I rebuild the web dynpro application and re-deploy it. Finally I get the error message

Accessing System ER2 is not possible because RFC Metadata was retrieved using System X01. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!

So it seems JCO setting still remember old FRC Metadata which is connected to XI client, rather than reflect new R/3 IDES client. So how to refresh the JCO to let SAP system know the new JCO for web dynpro application?

Moreover, in JCO general data and first screen of editing the JCO, I need to type in a J2EE cluster name. Here I choose XI instance X01, which has a J2EE 6.40 engine. It is also the place I will deploy my web dynpro flight application. On my R/3 V4.7 ER2 system, it has only ABAP Web AS 6.20, no J2EE engine. So is this a problem because R/3 client is not on J2EE cluster server X01?

Should the BAPI client reside on J2EE cluster server?

Thanks!

Thomas