on 11-28-2013 2:45 PM
Hi
With the old JCO arfc connections it was possible to change the default jco destination by passing the application parameter (in the iview) sap-wd-arfc-useSys. So we could use the same WDJ application with different backendsystems... for example the default destination was WD_MODELDATA_RFC, we created a destination WD_MODELDATA_RFCB for a other logical system and set the iview parameter sap-wd-arfc-useSys=WD_MODELDATA_RFC:B (same thing for the metadata connection).
Now, after migrate the application from 7.0 to 7.31 the new rfc model arfc2 is used and we can not switch the destination. To set the application parameter has no effect and the default destination is choosen evermore.
How can we change the default destination of an arfc2 model?
Thanks in advance.
Regards David
Hi David,
Did you get the solution for it? W are also having the same issue. We wanted to call the destinations at runtime and hence we are using 'new Model(system, client)' . But it is strange that the application is looking for default destinations. If we configure the default destinations then the above model constructor works fine. But we do not want to call the default destination.
Please let us know if you have any suggestion on this.
Thanks
Shankha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shankha
Instancing the model with "new Model(system, client)" didn't worked for us neither.
But we found a solution with the following configuration that work for us.
set following iView parameter:
"Application Parameters" = rfc_system=X&rfc_client=999
create JCO Destinations as followed:
WD_ELOWF_METADATA_DEST_X999
WD_ELOWF_MODELDATA_DEST_X999
I hope it works also for you.
Kind Regards
David
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.