The AS Java uses the Java Connector (JCo) to communicate with the AS ABAP. The JCo needs the information as shown in the table below to be able to use SNC for the connection:
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>.
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 |
Optional. The default is the system-defined library as defined in the environment variable SNC_LIB. |
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 AS Java’s SNC name. |
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. |
Partner’s SNC Name |
Specifies the AS ABAP’s SNC name. |
p:CN=ABC, O=MyCompany, C=US |
Required. You can find the application server’s SNC name in the profile parameter snc/identity/as. |
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.
For example, 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.
Other applications make use of the Destination service. In this case, see Destination Service and Options for RFC Destinations.