This is example shows how SAP calls remotely a function module running on the E2E Bridge. This function module takes two numbers and returns their sum.

...

RFC Service Components

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

• The E2E xUML composite RFCServerExample holding all services you want to deploy.
• Within the composite there are one or more SAP RFC services having the stereotype <<E2ESAPRFCService>>. In the current simple example it is the SAPRFCService.
• Each service holds one or more classes with stereotype <<E2ESAPRFCModule>> that define the interface of the service.  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.

Builder 6 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.

...

...

• Added in Builder 6.0

Figure: RFC Service Components

...

RFC Service Components of

...

Builder Version 5.1

...

Deprecated since Builder 6.0

Expand
title Click here to read the documentation of the component diagram used in E2E Builder releases before 6.0 ...
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

...