Versions Compared

Old Version 2

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version 3

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WBRIDGE and version 21.1

...

In the simple example in the current UML model we show only how to use the transaction mechanism offered by SAP. The proper transaction control is implemented elsewhere (cf. the E2E SAP module). The next section gives an overview of the components required to build a tRFC client.

...

AdapterDescription
<<SAPTRFCCreateTransaction>>

This adapter tries to get a transaction ID from the SAP system.

  • In case of error, the RFC client must reconnect later and try to repeat this call.
  • In case of success, the following adapter can use the resulting transaction ID as input.
    In this case, the transaction ID will be logged as correlation ID to the transaction log (see Contents of the Transaction Log)
<<SAPTRFCAdapter>>

The tRFC Adapter takes all input data and the current transaction ID and sends them to the SAP system using the tRFC protocol.

Possible input parameters are import and tables. Output parameters are not support because the tRFC protocol is asynchronous. In all other respects, the <<SAPTRFCAdapter>> works like the <<SAPRFCAdapter>>.
This adapter is used in the TestSimpleTypes activity diagram of the example (see Calling_ABAP_Functions_via_RFC). In this diagram, the general RFC interface is explained and the possible tagged values of such adapters. These adapters have import and tables input parameters. The import and tables input parameters must have base types of stereotype <<SAPParameters>> respectively <<SAPTables>>. For details see the class diagram describing the input tables for IDOC_INBOUND_ASYNCHRONOUS.

  • If an error occurs, the tRFC adapter has to reconnect later and must try to repeat the call. In this case, it has to use the old transaction ID and must not get a new transaction ID using  the <<SAPTRFCreateTransaction>> adapter. Otherwise, it is not guaranteed that the RFC function call will be executed exactly once in the SAP system.
  • After a successful execution of this call, the transaction is completely terminated in the SAP system. The tRFC client must update its own transaction ID management and call <<SAPTRFCConfirmTransaction>>. However, this logic is not implemented in the current simple example but in the E2E SAP module.
<<SAPTRFCConfirmTransaction>>

This adapter confirms the successful termination of a transaction. It must be called only if no errors occurred during execution of the <<SAPTRFCAdapter>>.
The transaction ID will be logged as correlation ID to the transaction log (see Contents of the Transaction Log)

...

NameDescription
ALIAS_USERAn alias user name, could used instead of user or even together with USER. If both USER and ALIAS_USER are used, than they have to be match.
EXTIDDATAContains valid external user's ID of an external authentification system. User name is optional. External ID is to be defined in the backend (SAP-System).
EXTIDTYPEDefines the kind of external identity. Valid only with EXTIDDATA. Follow values are not allowed: ID, NT; DN, CA, X, HX. Additionally, RFC Library provides the feature to retrieve MYSAPSSO2 certificate from the backend after successful logon.
GETSSO2Request to create a cookie version 2 using given password and user name. If the value is 1, the cookie will be generated from user and password values given by USER=user and PASSWORD=password in the same connect_param string. Instead, user and password X.509 certificate could be used. If the RfcOpenEx call ended successfully, the generated SAP cookie version 2 can be retrieved via RfcGetTicket API.
MYSAPSSOSAP Cookie Version 1. Will be used instead of user and password for logon to backend
MYSAPSSO2SAP Cookie Version 2. Will be used instead of password for logon to backend. In this case, user name is optional.
X509CERTAn X.509 certificate will be used instead of password to logon to SAP System. In this case, user name is optional.

tRFC Client Components of E2E Builder Version 5.1

Deprecated since E2E Builder 6.0

...

titleClick here to read the documentation of the component diagram used in E2E Builder releases before 6.0 ...

The components depicted in the figure below send IDocs from the frontend via tRFC to SAP. The frontend interface is SOAP. Therefore, the configuration holds a SOAP service component, namely tRFCClientService. This component contains a SOAP IDocInterface whose operations do the actual calling of the SAP tRFC interface. This interface (IDocInterface) has the stereotype <<SAPRFCModuleInterface>> and it is resident in a <<SAPRFCService>> component (tRFCService).

Figure: tRFC Client Component Diagram

Image Removed

...

is

...

optional

...

Info
iconfalse

systemNumber and routerString are found in the SAP GUI logon panel.

Like for every other adapter there must be a dependency between the composite using the tRFC adapter and the interface accessed by the adapter. This dependency must have the following tagged values:

...

.

...