cancel
Showing results for 
Search instead for 
Did you mean: 

How does SAP Handle the protocols for different set of data transfer?

Former Member
0 Kudos

Hi,

It seems that SAP handles different set of data transfer through different TCP port numbers,

such as:

SAP System Dispatcher Port 32xx

SAP System Dispatcher Security Port 47xx

SAP System Gateway Central Instance Port 33xx

SAP System Gateway Security Port 48xx

SAP message server services 36xx

GUI Client and STEAM Agent 49xx

and there is no default TCP port for any type of the data transfering.  How does the SAP client initiate the connection to the SAP server? Does all the above data transfering types use the same protocol? or each type of data transfering uses different protocol? Is there any standard protocol for the SAP connection negotiation?

I would truly appreciate your help!

June

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member181879
Active Contributor
0 Kudos

Hallo June,

I read your message once, twice. I searched through it. I spell-checked it. But I could not find the magic three characters "BSP". 😞  In this forum we do only (mostly?) BSP work. The exception to the rule was Suresh with his Java problem, and Christoph who was at least nice enough to also answer his question.

With that said and done, I am not sure I under your question. So allow me to shoot some sentences in the dark. Maybe it helps. Otherwise I will recommend you ask in another forum (maybe Web Application Server?).

First: Ports are a concept of the TCP level of the protocol stack. TCP is used to build an end to end connection from one computer to another computer, and ensure a reliable communication channel. TCP, per se, does not say anything about the actual its actual payload. You can running anything inside a TCP connection. (From univerity studies years ago.)

However, in the world, it is standard and common to run exactly one, and usually a known, protocol inside one TCP connection. These ports, and their numbers, are well defined, and published all over the Internet. For example, port 21 for FTP, port 25 for SMTP, port 110 for POP3, port 119 for NNTP, etc. There are really hunderds of these definitions.

The reason that the protocol and the port number must be know, is that it is nearly impossible to auto detect an incoming protocol. So once the bytes arrive at the server, you must know what protocol it is, and what application is going to handle it.

So this is the reason that services (accessed via protocols) are mapped onto ports which are known beforehand.

For HTTP, the default port number is usually 80. However, many people also like to use 1080, or 8080.

I know that this does not really answer your questions, but maybe it helps. Maybe on another forum you find the colleagues with indepth knowledge on this aspect.

bye, brian (returning to BSP development)

Former Member
0 Kudos

Hello Brian,

You are right that the TCP applications are well defined with thier own port numbers for the server to know which protocol the traffic belongs to and, what application is going to handle it, such as the ftp client has to initiate a connection with server through TCP port 21 although the data transfering port can be negotiated according to FTP protocol.

HTTP is a good example of initiating a connection without using its default TCP well know port  80, the connection negotiation relies on the HTTP protocol.

TCP applications have thier own protocols. E.g. FRC 765 for FTP and  RFC 2068 for HTTP(1.1). Is there any way that I can learn the SAP protocol?

Thanks!

June

former_member181879
Active Contributor
0 Kudos

Hallo June,

Yes the stuff about the ports and the protocols we now have under control.

I spend today running around and whispering "the SAP protocol" into all ears. The ears twitched. But the eyes told the true story: "what?". This was quickly followed by a wave of hands, a short excuse about been late, a rush of air, and there I stood: just whispering in the wind....the SAP protocol...

Nobody would accept responsibility for "the SAP protocol".

There was the guy who talked about RFC, another mentioned DIAG, and then a number talked about XML inside something or another, for example XRFC or SOAP. And of course there is HTTP, HTTPS and SMTP directly into ICM.

Which brings us back to the central point: This is not a BSP question! However, as you have now warmed our forum with your presence, and we are now very interesting in finding the true SAP protocol, we ask that you tell us more! We will make you nr3 with off-topic questions.

What is this "the SAP protocol"? Where have you seen or heard about it? Where is it used, where do you want to go with it? Maybe even a port on which you know it is listening. Anything more to help us in our search?

brian (puzzled)

former_member181879
Active Contributor
0 Kudos

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents

           /a1-8-4/RFC%20Series%20Part%202%20-%20Mining%20R%203%20with

          %20the%20RFCSDK%20-%20RFC,%20the%20Gory%20Details