Introducing the RFC Adapter on Edge Integration Cell
The SAP Integration Suite has taken a significant step forward with the introduction of the RFC receiver adapter on the Edge Integration Cell (EIC) runtime. This enhancement allows seamless migration from PI/PO to SAP Integration Suite, leveraging its diverse capabilities.
What is RFC?
Remote Function Call (RFC) is a protocol used to communicate between SAP systems and external applications. It enables the execution of functions in a remote system, facilitating integration and data exchange.
Key Features of the RFC Adapter
Direct Connection: The RFC adapter now allows direct connection to backend systems via local BTP destinations, eliminating the need for SAP Cloud Connector. Secure Communication: Secure Network Communication (SNC) is supported, offering authentication, integrity, and confidentiality protection. Java Connector (JCo) Integration: Utilizes JCo Standalone 3.1 library for transforming remote-enabled Function Module (RFM) calls.
How it works on Edge Integration Cell runtime?
SAP Cloud Integration can directly access the virtual systems exposed by the Cloud Connector, via RFC destinations. With this new enhancement, now, Edge Integration Cell allows direct connection to backend systems (without using the SAP Cloud Connector), via local BTP destinations (which can run without internet but needs periodic sync from Cloud) and SNC. Thus, the RFC Sender adapter running on Edge Integration Cell can benefit from native RFC (CPI-C) communication through an SAP Gateway.
The adapter uses the Java Connector (JCo) Standalone 3.1 library to receive and transform remote-enabled Function Module (RFM) calls from SAP or external (JCo-based) systems and applications. RFC Metadata is used for the transformation from native RFC to RFC-XML and vice versa.
The adapter uses the Java Connector (JCo) Standalone 3.1 library to receive and transform remote-enabled Function Module (RFM) calls from SAP or external (JCo-based) systems and applications. RFC Metadata is used for the transformation from native RFC to RFC-XML and vice versa.
This blog explains how to use and establish the setup for RFC adapter in EIC runtime.
Prerequisites for using the RFC Receiver Adapter
The remote systems that RFC adapter connects to can be on-premise or in the cloud. Typically, Cloud Integration can directly access the virtual systems exposed by the Cloud Connector, except for the RFC channel. In Cloud Integration and for its Edge Integration runtime, for the RFC channel it’s necessary to configure a destination in SAP BTP Cockpit.
For full help documentation regarding the use of the Destinations Editor (and other methods to maintain destinations), as well as the setup of the different destination types, see SAP BTP Connectivity – Initial Setup. For step by step visual instructions, follow this blog. Set up SNC on Edge Integration Cell for productive use of the RFC Adapter. For more information, see Set Up SNC on Edge Integration Cell. For step by step visual instructions, follow this blog.
Prerequisites for using the RFC Sender Adapter
In addition to the prerequisite mentioned for the receiver adapter, following additional settings are needed:
Create a new destination of TCP/IP type in the ABAP system to establish a connection in the sender system. Note that this prerequisite step is only applicable to ABAP systems and does not apply to non-ABAP systems. For more information, see Setting Up an RFC Destination for the RFC Adapter.
Why SNC
RFC connections between SAP Edge Integration Cell and other SAP systems, or third-party systems can be secured with SNC (Secure Network Communication). SNC supports three levels of security protection:
Authentication only Integrity protection Confidentiality protection
To ensure secure communication, Secure Network Communications (SNC) should be enabled in Edge Integration Cell and configured for the RFC adapters. Enabling SNC when using the RFC adapter, especially productively, is strongly recommended.
Setting up New destination in BTP Cockpit ( Prerequisite)
For using the adapter in Edge Integration Cell runtime, choose Connectivity > Destinations (New). Choose Create. Choose From Scratch to create the destinations from scratch and adding all required details like Proxy and Authentication details. Choose From File to import a pre-configured destination.
If you choose From Scratch, enter the values in all required fields.
Enter the details for the parameters <Name>, <URL>, <User>, <Password>, and select <Type> as RFC.
Note
For setting up an RFC connectivity for ABAP environment using principal propagation. Select OnPremise from the value help and then for <Authentication>, select PrincipalPropagation. For using RFC adapter in Edge Integration Cell runtime, set Proxy Type as <Local>.Add the SNC propertied along with the following properties and assign appropriate values:
Java Connectivity Parameters (first four properties are mandatory)
Parameters
Description
Connection Parameters
jco.client.ashost
The IP address or hostname of the SAP application server.
Note
For runtimes other than Edge Integration Cell, the value provided for application server host (ashost) property is the access control value created in the Cloud Connector.
jco.client.client
The SAP client number.
jco.client.lang
The language for communication with SAP SAP (e.g., en for English)
jco.client.sysnr
The system number of the SAP instance (e.g., 27)
jco.client.user
The SAP username for authentication
jco.client.passwd
The password for the SAP user.
jco.destination.auth_type
While configuring for principal propagation the value for the property is “jco.destination.auth_type = PrincipalPropagation”.
Connection Pool Parameters
(optional) jco.destination.pool_capacity
The number of connections that are kept open in the connection pool for reuse.
(optional) jco.destination.peak_limit
The maximum number of concurrent connections allowed at peak times.
WebSocket Connection
jco.destination.auth_type
If you’re using principal propagation for authentication, for the property jco.destination.auth_type, specify the value as PrincipalPropagation. Don’t specify any additional credentials in the destination.
Location ID should correspond to the cloud connector name found in the master instance.
jco.client.client
The SAP client number
jco.client.tls_trust_all
jco.client.wshost
Host for websocket connection
jco.client.wsport
Port for websocket connection
jco.destination.repository_roundtrip_optimization
Set the value to 0 that helps you to minimizes the number of roundtrip calls made to the server
SNC parameters (Set the following parameters (mandatorily) to use the RFC adapter Edge Integration Cell runtime)
jco.client.snc_mode
Set the value to 1 to enable SNC.
jco.client.snc_partnername
SNC partner name. The format for SNC partner names is <p:<distinguished name>, where distinguished name comes from the public certificates of the trusted partners
jco.client.snc_qop
Protection levels for SNC, which ranges from 1 to 9, where 9 signifies the highest level of protection. By default, the value is 8.
Choose Create. You can further edit this destination by choosing Edit. See See: RFC Destinations.
Setting up SNC for RFC adapter on EIC (Prerequisites)
See Set Up SNC on Edge Integration Cell for step by step instructions on how to configure SNC for RFC adapter.
Adding SNC related properties when you are deploying an edge node solution
For step by step instructions on how to create the Edge Node as a Runtime Location in SAP Integration Suite, see Deploy the Edge Integration Cell Solution.
Ensure to set following additional properties to enable SNC for the adapter.
Enable SNC for RFC Adapter
Choose this option to set up SNC for secure communication over the RFC protocol. It is strongly recommended to enable this option if using the RFC adapter productively. For more information, see Set Up SNC on Edge Integration Cell.
SNC File System Storage Class (only visible if SNC for RFC Adapter is enabled)
Enter the storage class for the access mode ReadWriteMany and the binding mode Immediate
For more information on generating a key pair or uploading an existing one, downloading its public certificate, and importing the public certificates of the SNC partners, see Managing Keystore Entries.
After setting up SNC on Edge Integration Cell, you can now enable and configure SNC communication in the RFC Adapter. See:
By integrating the RFC adapter into your EIC runtime, you can enhance your system’s connectivity and security, paving the way for efficient and secure data exchange.
Feel free to reach out if you have any questions or need further assistance with the setup. Happy integrating!
Introducing the RFC Adapter on Edge Integration Cell The SAP Integration Suite has taken a significant step forward with the introduction of the RFC receiver adapter on the Edge Integration Cell (EIC) runtime. This enhancement allows seamless migration from PI/PO to SAP Integration Suite, leveraging its diverse capabilities. What is RFC? Remote Function Call (RFC) is a protocol used to communicate between SAP systems and external applications. It enables the execution of functions in a remote system, facilitating integration and data exchange. Key Features of the RFC Adapter Direct Connection: The RFC adapter now allows direct connection to backend systems via local BTP destinations, eliminating the need for SAP Cloud Connector. Secure Communication: Secure Network Communication (SNC) is supported, offering authentication, integrity, and confidentiality protection. Java Connector (JCo) Integration: Utilizes JCo Standalone 3.1 library for transforming remote-enabled Function Module (RFM) calls. How it works on Edge Integration Cell runtime? SAP Cloud Integration can directly access the virtual systems exposed by the Cloud Connector, via RFC destinations. With this new enhancement, now, Edge Integration Cell allows direct connection to backend systems (without using the SAP Cloud Connector), via local BTP destinations (which can run without internet but needs periodic sync from Cloud) and SNC. Thus, the RFC Sender adapter running on Edge Integration Cell can benefit from native RFC (CPI-C) communication through an SAP Gateway. The adapter uses the Java Connector (JCo) Standalone 3.1 library to receive and transform remote-enabled Function Module (RFM) calls from SAP or external (JCo-based) systems and applications. RFC Metadata is used for the transformation from native RFC to RFC-XML and vice versa. The adapter uses the Java Connector (JCo) Standalone 3.1 library to receive and transform remote-enabled Function Module (RFM) calls from SAP or external (JCo-based) systems and applications. RFC Metadata is used for the transformation from native RFC to RFC-XML and vice versa. This blog explains how to use and establish the setup for RFC adapter in EIC runtime. Prerequisites for using the RFC Receiver Adapter The remote systems that RFC adapter connects to can be on-premise or in the cloud. Typically, Cloud Integration can directly access the virtual systems exposed by the Cloud Connector, except for the RFC channel. In Cloud Integration and for its Edge Integration runtime, for the RFC channel it’s necessary to configure a destination in SAP BTP Cockpit. For full help documentation regarding the use of the Destinations Editor (and other methods to maintain destinations), as well as the setup of the different destination types, see SAP BTP Connectivity – Initial Setup. For step by step visual instructions, follow this blog. Set up SNC on Edge Integration Cell for productive use of the RFC Adapter. For more information, see Set Up SNC on Edge Integration Cell. For step by step visual instructions, follow this blog. Prerequisites for using the RFC Sender Adapter In addition to the prerequisite mentioned for the receiver adapter, following additional settings are needed: Create a new destination of TCP/IP type in the ABAP system to establish a connection in the sender system. Note that this prerequisite step is only applicable to ABAP systems and does not apply to non-ABAP systems. For more information, see Setting Up an RFC Destination for the RFC Adapter. Why SNC RFC connections between SAP Edge Integration Cell and other SAP systems, or third-party systems can be secured with SNC (Secure Network Communication). SNC supports three levels of security protection: Authentication only Integrity protection Confidentiality protection To ensure secure communication, Secure Network Communications (SNC) should be enabled in Edge Integration Cell and configured for the RFC adapters. Enabling SNC when using the RFC adapter, especially productively, is strongly recommended. Setting up New destination in BTP Cockpit ( Prerequisite) For using the adapter in Edge Integration Cell runtime, choose Connectivity > Destinations (New). Choose Create. Choose From Scratch to create the destinations from scratch and adding all required details like Proxy and Authentication details. Choose From File to import a pre-configured destination. If you choose From Scratch, enter the values in all required fields. Enter the details for the parameters <Name>, <URL>, <User>, <Password>, and select <Type> as RFC.Note For setting up an RFC connectivity for ABAP environment using principal propagation. Select OnPremise from the value help and then for <Authentication>, select PrincipalPropagation. For using RFC adapter in Edge Integration Cell runtime, set Proxy Type as <Local>.Add the SNC propertied along with the following properties and assign appropriate values: Java Connectivity Parameters (first four properties are mandatory) Parameters Description Connection Parameters jco.client.ashost The IP address or hostname of the SAP application server. Note For runtimes other than Edge Integration Cell, the value provided for application server host (ashost) property is the access control value created in the Cloud Connector. jco.client.client The SAP client number. jco.client.lang The language for communication with SAP SAP (e.g., en for English) jco.client.sysnr The system number of the SAP instance (e.g., 27) jco.client.user The SAP username for authentication jco.client.passwd The password for the SAP user. jco.destination.auth_type While configuring for principal propagation the value for the property is “jco.destination.auth_type = PrincipalPropagation”. Connection Pool Parameters (optional) jco.destination.pool_capacity The number of connections that are kept open in the connection pool for reuse. (optional) jco.destination.peak_limit The maximum number of concurrent connections allowed at peak times. WebSocket Connection jco.destination.auth_type If you’re using principal propagation for authentication, for the property jco.destination.auth_type, specify the value as PrincipalPropagation. Don’t specify any additional credentials in the destination. Location ID should correspond to the cloud connector name found in the master instance. jco.client.client The SAP client number jco.client.tls_trust_all jco.client.wshost Host for websocket connection jco.client.wsport Port for websocket connection jco.destination.repository_roundtrip_optimization Set the value to 0 that helps you to minimizes the number of roundtrip calls made to the server SNC parameters (Set the following parameters (mandatorily) to use the RFC adapter Edge Integration Cell runtime) jco.client.snc_mode Set the value to 1 to enable SNC. jco.client.snc_partnername SNC partner name. The format for SNC partner names is <p:<distinguished name>, where distinguished name comes from the public certificates of the trusted partners jco.client.snc_qop Protection levels for SNC, which ranges from 1 to 9, where 9 signifies the highest level of protection. By default, the value is 8. Choose Create. You can further edit this destination by choosing Edit. See See: RFC Destinations. Setting up SNC for RFC adapter on EIC (Prerequisites) See Set Up SNC on Edge Integration Cell for step by step instructions on how to configure SNC for RFC adapter.Adding SNC related properties when you are deploying an edge node solutionFor step by step instructions on how to create the Edge Node as a Runtime Location in SAP Integration Suite, see Deploy the Edge Integration Cell Solution. Ensure to set following additional properties to enable SNC for the adapter. Enable SNC for RFC Adapter Choose this option to set up SNC for secure communication over the RFC protocol. It is strongly recommended to enable this option if using the RFC adapter productively. For more information, see Set Up SNC on Edge Integration Cell. SNC File System Storage Class (only visible if SNC for RFC Adapter is enabled) Enter the storage class for the access mode ReadWriteMany and the binding mode Immediate For more information on generating a key pair or uploading an existing one, downloading its public certificate, and importing the public certificates of the SNC partners, see Managing Keystore Entries. After setting up SNC on Edge Integration Cell, you can now enable and configure SNC communication in the RFC Adapter. See: RFC Sender Adapter RFC Receiver adapter. By integrating the RFC adapter into your EIC runtime, you can enhance your system’s connectivity and security, paving the way for efficient and secure data exchange. Feel free to reach out if you have any questions or need further assistance with the setup. Happy integrating! Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
