SAP NEWS-71-RFC documentation, setup help and usage info

Remote Function Call for Release 7.0, EhP2

1 Background RFC
2 Local Data Queue
3 SAP NetWeaver RFC SDK
4 RFC Connectivity in SAP Java Enterprise Edition (
Java EE )
5 basXML as new RFC protocol
6 Identification of Trusted System s

ABAP_MODIFICATION_1 Background RFC

With the new Background RFC
( bgRFC ) Remote Function Calls can be carried out safely in a transaction and in the call sequence. The calling application and the called application are connected asynchronously. bgRFC replaces the functions previously provided by tRFC and qRFC (but not qRFC No-Send ).
ABAP_MORE_INFO
Latest notes: SP 14 includes this change in Release 7.0 as well.

ABAP_MODIFICATION_2 Local Data Queue

The Local Data Queue ( LDQ ) is a persistence layer into which data can be placed. This data can only be read in the sequence that it is recorded in. This involves separation of data recording from data retrieval by the receiver like in an inbox. Since the access sequence is defined according to the First-In First-Out ( FIFO
) principle, we talk about queues that serve as the organizational element for the individual receivers. The LDQ replaces the functions previously provided by the qRFC No-Send scenario.
ABAP_MORE_INFO

ABAP_MODIFICATION_3 SAP NetWeaver RFC SDK

The new SAP NetWeaver RFC SDK replaces the classic RFC SDK
. It supports a revised API that can be used like the SAP Java Connector .
ABAP_MORE_INFO

ABAP_MODIFICATION_4 RFC Connectivity in SAP Java Enterprise Edition ( Java EE )

For the SAP Java Enterprise Edition ( Java EE ), the
SAP Java Resource Adapter ( SAP JRA ) for SAP JCo is provided. It provides connections to resources in accordance with
JCA 1.5 SAP JCo .
ABAP_MORE_INFO

ABAP_MODIFICATION_5 basXML as new RFC protocol

basXML format is supported as the new standard RFC protocol and replaces the previous formats.

ABAP_MODIFICATION_6 Identification of Trusted System s

In transaction SMT1 for maintaining RFC Trust Relationships creating trusted system s by entering the system ID (name of the AS ABAP ) now also uses the installation number. This applies for all trusted system s as of Releases 7.02, EhP2 and 7.2 (including 7.1).
When creating a trusted relationship as of Release 7.0, EhP2 , the trusting system checks the installation number of the calling system, if it is listed in transaction SMT1 . For trust relationships of this kind, the relevant authorizations need to be modified so that field
RFC_INFO in authorization object S_RFCACL contains the installation number of the calling system.

SAP NEWS-71-RFC documentation, setup help and example usage