Configuring SNC Between a Java iView and an
ABAP System
Use
You can configure Secure Network Communication (SNC) between Java iViews and an ABAP-based system where the iViews connect to the ABAP system using RFC and Java Connector (JCo) technology. If the iViews retrieve sensitive data, such as personal data, from the ABAP system, we strongly recommend that you secure the connection with SNC.
The following
procedure can be used to configure SNC for Java iViews that connect to the
ABAP system using RFC and Java Connector (JCo). It cannot be used for iViews
that integrate Business Server Pages (BSPs), Internet Application Components
(IACs), MiniApps, BW reports, or transactions from ABAP systems. All of these
iViews use HTTP or DIAG to connect to the ABAP system. For information on how
to configure SNC in these cases, see Secure Network
Communications (SNC). This procedure also cannot be used for iViews that
integrate Web Dynpro applications. For information about how to configure SNC
for Web Dynpro applications, see the Web Dynpro documentation at
Creating JCo
Destinations.
Prerequisites
● A system object exists in the portal for the system to which the iView connects.
● You have configured Single Sign-On (SSO) to the ABAP system. This can either be SSO with logon tickets or with user ID and password (user mapping).
Procedure
...
1. Set up the SNC connection between the SAP NetWeaver Application Server (AS) Java on which the SAP NetWeaver Portal runs and the ABAP system as described in Configuring SNC (SAP J2EE Engine ® ABAP Engine).
2. When you get to the step in which you set the SNC parameters, proceed as follows:
a. Find out which system object the iView uses.
You can find
this out by looking at the value of the iView property System Alias and then finding the system object with this
system alias. For more information, see
System
Landscape.
b. Create a copy of the system object, change the ID of the copied object, and define a new system alias for the copied object.
c. Open the copied system object for editing and set values for the following properties:
These properties are all in the property category Connector.
Property Name |
Description |
SNC Mode |
Flag for activating SNC. To activate SNC, set this to 1. |
SNC Library Path |
Path and file name of the SNC library. |
SNC Name |
SNC name of the AS Java on which the portal runs. |
SNC Partner Name |
SNC name of the ABAP system. |
SNC QOP (Security Level) |
Level of protection to use for the connection. |
For more information about all of these properties, see Setting the SNC Parameters.
d. Test whether the connection to the system works as follows:
i. In the System Landscape editor, choose Display Connection Tests.
ii. Select Connection Test for Connectors.
iii. Choose Test.
The test results show whether the SNC connection to your system works.
e. Once the SNC connection is working, assign your iView to the copy of the system object that you created as follows:
i. In the Portal Content Studio, open the iView for editing.
ii. In the iView property editor, change the value of the System Aliasproperty to the system alias of the modified system object.
iii. Save your changes
Result
All iViews that use the system object you changed now connect to the ABAP back-end system with SNC and as the user currently logged on to the portal.
Troubleshooting
If you experience problems with the SNC connection, you can enable tracing by setting the property Trace Mode in the system object to 1. When you set this property, you can then find trace files called dev_jrfc.trc and jrfcxxxxx_xxxxx.trc at the following location: <j2ee_installation_directory>\j2ee\cluster\server0.