Show TOC

Setting the SNC ParametersLocate this document in the navigation structure

SAP NetWeaver AS for Java uses the Java Connector (JCo) to communicate with SAP NetWeaver AS for ABAP. The JCo needs the information as shown in the table below to be able to use SNC for the connection.

Caution

The SNC name is not the same as the Distinguished Name you used when creating the PSE. The SNC name has the syntax p:<Distinguished_Name>.

Table 1: SNC Information
Information Description Example Comment

SNC mode

Flag for activating SNC.

1 (on)

Required.

SNC library path

Specifies the path and file name of the external library.

C:\SAPNW_AS_Java \SAPCryptolib\ sapcrypto.dll

Optional.

The default is the system-defined library as defined in the environment variable SNC_LIB .

The Destination service uses the property snc/gssapi_lib on SAP NetWeaver AS for Java.

Level of protection

Specifies the level of protection to use for the connection.

3

Optional.

Possible values:

1: Authentication only

2: Integrity protection

3: Privacy protection (default)

8: Use the value from snc/data_protection/use on the application server

9: Use the value from snc/data_protection/max on the application server

Default value = 3

My SNC name

Specifies the SNC name of SAP NetWeaver AS for Java.

p:CN=AS Java, O=MyCompany, C=US

Although this parameter is optional, we do recommend setting it to make sure that the correct SNC name is used for the connection.

For the Destination service, set it in the property snc/identity/as on SAP NetWeaver AS for Java.

SNC Name of the partner

Specifies the SNC name of SAP NetWeaver AS for ABAP.

p:CN=ABC, O=MyCompany, C=US

Required.

You can find the application server's SNC name in the profile parameter snc/identity/as on SAP NetWeaver AS for ABAP.

Setting the SNC Parameters

The various applications that use the JCo to set up the connection have their own methods for setting these parameters. Therefore, see the documentation for the application to determine how to set these parameters correctly.

Example

The primary source of connection information for the JCo is the Destination service. For the corresponding configuration, see Maintaining RFC Destinations.

The user management engine (UME) sets the SNC parameters in the UME properties as described in Configuring SNC Between the UME and an ABAP-Based System.

Another example is setting up SNC for Java iViews in SAP Enterprise Portal. In this case, you set the SNC parameters in the system object associated with a Java iView. For more information, see Configuring SNC Between a Java iView and an ABAP System.