[294] in SAPr3-news
Re: SAP-GUI network question
daemon@ATHENA.MIT.EDU (Frank Fischer)
Tue Jul 4 03:37:18 1995
To: sapr3-news@MIT.EDU
Date: Tue, 4 Jul 1995 07:25:19 GMT
From: frank.fischer@sap-ag.de (Frank Fischer)
In article <3svnar$47e@ixnews5.ix.netcom.com>, ejp1@ix.netcom.com (Elmer Phillippi) says:
>
>Pardon my lack of German. I am working with an SAP system, and
>my documentation indicates that all communications from the client
>on the PC (WIN3.1) to the SAP server (UNIX) uses RFC, which is a
>version of Remote Procedure Call (RPC). I get the impression that
>SAP hs its own custom version of rpcbind (or portmap). Is this correct?
>Any information would be helpful. Feel free to respond in German or
>English.
>
>Thank you.
>Elmer
>--
>==================================================
>Elmer Phillippi ejp1@ix.netcom.com
>==================================================
Elmer,
Your assumption is not correct.
The communication between SAPGUI and the R/3 Application Servers is
based on native TCP/IP. On The WINDOWS side, we use the WINSOCKET API
to access the TCP/IP stacks (so we are quite independent of the used
TCP/IP stack, although we have a list of tested stacks).
The RFC (Remote Function Call) is an API for Interprocess communication
in the SAP environment. This API is formed according to the RPC paradigm
but allows to call not only C-Language subroutines but also R/3 Function
Modules (that's why a standard RPC would not work)
Best Regards,
Frank Fischer /SAP Marketing
