Setting optional RFC connection parameters for the adapter

To enable the adapter to use Secure Network Communication to communicate with SAP NetWeaver AS ABAP, you must add parameters to the service form.

Procedure

Add these parameters on one line to the Optional RFC Connection Parameters field in the service form:

snc_mode=1|snc_partnername=as_abap_snc_name|
snc_qop=3|snc_myname=adapter_snc_name|snc_lib=path_to_snc_lib

Where:

snc_mode

Secure Network Communication activation indicator. Use these values:

0: Secure Network Communication is disabled.
1: Secure Network Communication is activated.

snc_partnername

Secure Network Communication name of the communication partner (SAP NetWeaver AS ABAP).

snc_qop

Quality of protection level.

1: Secure authentication only.
2: Data integrity protection.
3: Data privacy protection.
9: Use the value from snc/data_protection/max.

snc_myname

Secure Network Communication name of the adapter.

For example (on one line):

snc_mode=1|snc_partnername=p:CN=GC8,OU=IdM,O=IBM,C=US|snc_qop=3|
snc_myname=p:CN=adapter,OU=IdM,O=IBM,C=US|snc_lib=C:/usr/sap/sapcrypto.dll

Note: For securing multiple SAP systems with single Secure Network Communication certificate, pass same path value for snc_lib in the service forms of all the SAP systems.

Note: These parameters directly correspond to SAP JCO properties for Secure Network Communication except that they do not have the jco.client. prefix. The adapter automatically prepends the string jco.client. before the adapter passes these parameters to SAP JCO.

For more information about the Secure Network Communication parameters, see the SAP Help Portal.