Page History
Div | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
...
...
tRFC Service Components of 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 ... |
---|
Each <<E2ESAPRFCService>> that utilizes tRFC contains at least two residents: One and only one <<E2ESAPTRFCCallbacks>> class holding operations to control transactional behavior (for instance the TRXLogging class beneath) and one or more <<E2ESAPRFCModule>> classes containing operations called by the SAP system to exchange data. For instance, see the IDocInterface class depicted in the deployment diagram beneath. The implementation of these operations is similar to the implementation of standard RFC operations. The only difference results from the asynchronous nature of tRFC operations - they handle input only.
Figure: tRFC Service Component Diagram
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 tRFCServiceDeployment has the following tagged values:
...
Basically, tRFC server components must be registered at the so-called SAP gateway. For example, the artifact tRFCServiceDeployment is registered at the gateway-artifact sapgw00 via the program ID E2E_RFC_ZERTIFI_SERVER_ID.
The program ID must be defined on the SAP system in transaction SM59. This transaction enables the user to define TCP/IP connections (connection type T). Each such connection has an associated program ID that must be exactly the same string as used for the tagged value programID on the <<Register>> dependency. Note, that this string is case sensitive. The <<Register>> dependency points to a component artifact having the name of the SAP gateway the server registers on. This name is given by: sapgw + system number of the SAP system.
...
icon | false |
---|
...
...