on 06-24-2014 10:34 AM
Hello,
I am using following piece of code to make a RFC call from a JSPDynpage to back-end SAP R/3 system: -
JCoDestination wdModelDataDest = JCoDestinationManager.getDestination("WD_MODELDATA_MYAPPLICATION");
JCoRepository repository = wdModelDataDestFixedUser.getRepository();
JCoFunction function = repository.getFunction(RFC_NAME);
JCoParameterList importparams = function.getImportParameterList();
importparams.setValue("USERNAME", "A007");
function.execute(wdModelDataDest);
JCoParameterList exportParams = function.getExportParameterList();
String gbuName = exportParams.getString("GBU");
Could you please let me know how to ensure that connection is 'disconnected' after RFC call?
Portal version : CE7.3 EHP1 SP9
Thanks & Regards,
Amey Mogare
Hi Amey,
In the new JCo 3.0 API, connection management is no longer a task for the individual application, but
is managed centrally by a destination model.
Mahesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mahesh,
Thanks a lot for prompt & very helpful replies.
I want to know more about "Pool settings" and "Adavnce settings" properties of a RFC Destination that we create in NWA > Configuration > Security > Destinations.
Currently we are facing issues in our prod backend SAP R/3 system that many connections of this RFC destination's technical user are remaining open.
Need to know how to fine tune these (or any other) parameters/properties?
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.