program-ID seebeyond eway integrator
Hi,
We are using seebeyond to talk to our SAP system.
when we create RFC destination in SAP system , we attach one program-ID to that RFC destination.
My question is ,
I have two BAPI in SAP system BAPI_A & BAPI_B.
I am calling seebeyond for both these BAPIs. same RFc destination.
For BAPi_A seebeyond need to do process-A and
For BAPi_B seebeyond need to do process-B.
Do seebeyond need different program-ID for diff BAPI , That means in this case 2 program -ID and also means that in SAP I will need to create 2 RFC destinations.
Please advise..
[616 byte] By [
Vaibhav_NZ] at [2007-11-26 10:54:35]
# 1
If you are using JCaps 5.1.x or ICAN 5.0.x, you will need to register both RFC server under different program ID's to ensure that the SAP call goes to the correct process so you will need two RFC destinations.
If you are using eGate 4.x you can use a single program ID for receiving calls to multiple RFC's
Regards,
Frederik
# 3
Chris,
The difference in ICAN/JCaps is that the receive of the SPA RFC call is managed in the connector and the connector then marshals the RFC call in the SAP Bapi OTD before your collaboration is triggered. If the connector cannot marshal the RFC call in the OTD it will throw an exception.
In the eGate 4.5 version, SAP calls were received by the connector but they RFC arguments were retreived from the connector by the collaboration. The collaboration was started using the get interval and it could then examine which of the RFC ETD's was called before retrieving the RFC call. This allowed it to receive multiple different RFC calls.
Regards,
Frederik
