Failure in Model Create Step: com.sap.mw.jco.JCO$Exception: Missing R3NAME=

Question

Hi,
I am running NW04sp10 and am trying to connect my WebDynPro to my R/3 backend app server - am running through the FlightChecking example using DevStudio 2.0.10.
Have successfully created my meta + app data JCo's, they test and ping OK from the Content Manager.  SLD is fine, connecting happily to the NW and R/3 boxes.  One is message server, one central instance.
When the 'create model' wizard tries to build the java proxies though, it comes back with this:
[Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
Can anyone help?
Cheers guys,
Andy

Answer 1

Hi Wael,
I'm using the tutorial 'Handling Transactions with BAPIs in Web Dynpro' [part of SAP Online Help].
The BAPI does work in se37, it's just a standard SAP delivered BAPI, and I've tried a few different ones to make sure it wasn't a BAPI specific problem.
In the content admin I've navigated through the local/FlightChecking/Applications/FlightCheckingComp and then used the wizard to add the 2 JCOs [I've kept the default names for now after your previous advice]
The data is like this:
WD_MODELDATA_DEST:
Name                  WD_MODELDATA_DEST
Client                800
J2EE Cluster Name     NW1 on chippy
USER                  USER1
Password              <password>
Application Server    nero
System ID             00
WD_RFC_METADATA_DEST:
Name                  WD_RFC_MODELDATA_DEST
Client                020
J2EE Cluster Name     NW1 on chippy
USER                  USER1
Password              <password>
Application Server    chippy
System name           NW1
Logon Group           PUBLIC
My landscape here is of 2 servers:
'Nero'    SAP r/3 4.7 Application Server System ID ACI
'Chippy'  SAP WebAS640 NW04 System ID NW1 ABAP+J2EE stack
The JCOs 'test' and 'ping' successfully.  My WD_RFC_METADATA_DEST connection is to a message server, the WD_MODEL_DEST is to a central instance.
Here's the full log from the create model wizard [I used a random BAPI for testing, BAPI_GET_PAYSLIP, so don't worry about that]:
[Warning]:     Creating a connection with Metamodel language <en_GB> failed.  Continuing with language <EN>
[Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
[Info]:     Creating Model: FlightChecking
[Info]:     Creating Model Class: Bapi_Get_Payslip_Input
[Info]:     Creating Model Class: Bapi_Get_Payslip_Output
[Info]:     Creating Model Class: Bapireturn1
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Return
[Info]:     Creating Model Class Property: Type
[Info]:     Creating Model Class Property: Id
[Info]:     Creating Model Class Property: Number
[Info]:     Creating Model Class Property: Message
[Info]:     Creating Model Class Property: Log_No
[Info]:     Creating Model Class Property: Log_Msg_No
[Info]:     Creating Model Class Property: Message_V1
[Info]:     Creating Model Class Property: Message_V2
[Info]:     Creating Model Class Property: Message_V3
[Info]:     Creating Model Class Property: Message_V4
[Info]:     Creating Model Class Property: Employeenumber
[Info]:     Creating Model Class Property: Payslipvariant
[Info]:     Creating Model Class Property: Sequencenumber
[Info]:     Creating Model Class: Bapi7004_Payslip
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Payslip
[Info]:     Creating Model Class Property: Format_Col
[Info]:     Creating Model Class Property: Text_Col
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Payslip
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Output:Bapi_Get_Payslip_Output
So it seems to actually be able to retrieve the metadata for the BAPIs, but not to make the relevant JCo's.  I've not gone on and completed the tutorial, assuming it won't work until I can sort out the above 'fatal' error.
Thanks again for all of your good advice.
Cheers,
Andy