For details on modeling SAP structures see Parameters.
RFC Client Components
Added in Builder 6.0 The example above calls ABAP functions in a SAP system. The frontend interface is SOAP. Therefore, the composite holds a SOAP service component (RFCClientService). This component contains two SOAP Port Types:
Figure: RFC Client Component Diagram
On the composite, you can also set a service-wide SAP value padding: Never, Always and Mixed. See Frontend Components for more information.
RFC Client Components of E2E Builder Version 5.1
Deprecated since Builder 6.0
|title||Click here to read the documentation of the component diagram used in E2E Builder releases before 6.0 ...|
|The accessed SAP interfaces are modeled as interfaces having the stereotype <<SAPRFCModuleInterface>> (SystemInfoInterface, Z_RFC_SERVICES) and they are resident in a <<SAPRFCService>> component (SAPRFCService). The components are manifested by their artifacts, which instantiating the components and annotating all configuration to run these components on their target systems. The component artifacts contained in the RFCClientExample contains a SOAP service accessing the SAP system. This SAP system is modeled as component artifact having the stereotype <<SAPRFCServiceDeployment>>.Like for every other adapter there must be a dependency between the configuration using the tRFC adapter and the interface accessed by the adapter. The tagged value definitions used for RFC client protocol are the same as for tRFC communication as explained in the tRFC Client Deployment diagram (see section tRFC_Client Components). The tagged values itself do not differ with one exception: the protocol tagged value must be rfcFigure: RFC Client Component Diagram |