SAP RFC Server
Programming
Definition
To create an RFC server with the SAP .NET Connector, create a new project using SAP Connector Class. Select the object type Server Stub.
Within the proxy you have to provide the implementation for the function. The SAP system acts as the client, calling your implementation of the function. For example, if you had an RFC server that implemented BAPI_CUSTOMER_GETLIST you have to populate the customer address list and special data tables in the BAPI_CUSTOMER_GETLIST method of your generated server stub.
The generated server code has methods for calling the function as RFC or TRFC. The methods for TRFC processing are generated for you, for example CheckTransaction(RfcTID), CommitTransaction(RfcTID), ConfirmTransaction(RfcTID), RollbackTransaction(RfcTID).
The SAP Server object has a “host” container to manage one or many RFC Servers. Each RFC server can contain different connection properties (for example, system, gateway, program ID). In the case where the connection information is the same (for example, same program ID), the SAP system calls each RFC Server in a round-robin approach.
This makes it easy to create and manage a multi-threaded, highly responsive RFC server application. When your RFC server application is done, it often makes sense to deploy it as a Windows Service. The SAPServerHost object maps very closely to how Windows services are managed, for example, there is a start, stop and pause functionality provided in the SAPServerHost or alternatively on each individual server.
Further Information
For further information, click on one of the following links:
· Calling our RFC .NET Server from SAP Programs
· Monitoring and Debugging SAPServer Stubs