In order to build an SAP RFC E2E Server, the following components must be defined:

• The configuration component RFCServer holding all services we want to deploy
• Within the configuration we have one or more SAP RFC services with the stereotype <<E2ESAPRFCService>>. In the current simple example we define the SAPRFCService.
• Each service holds one or more classes that define the interface of the service. with the stereotype <<E2ESAPRFCModule>> The activity diagrams assigned to the class operations define the implementation of the operations. In our example, the activity diagram Z_RFC_ADD implements the operation Z_RFC_ADD of the class Z_RFC_SERVICES. Z_RFC_ADD is also the function name used within SAP ABAP programs to call the operation Z_RFC_ADD. See also the comment attached to the Z_RFC_ADD operation.
• Further, we have to define the SAPRFCGateway  .The reason is, that each RFC server must register itself at a SAP  gateway. This gateway is modeled as component having the stereotype <<SAPRFCGateway>>  .

The components are manifested by their artifacts, which instantiating the components and annotating all configuration information to run these components on their target systems.
The component artifact contained in the RFCServerExample contains one SAP RFC service being registered on the SAP gateway.
Modeling RFC services follows the same rules as modeling tRFC servers with two exceptions: the protocol tagged value must be rfc and there exists no <<SAPTRFCCallback>>  interface.

Figure: RFC Service Components of E2E Builder Version 5.1

Image Removed