Configuring SNC (SAP J2EE Engine
à ABAP Engine)
To connect to an SAP system application server, the SAP J2EE Engine uses the Java Connector and RFC. To secure such connections, use SNC.

In this documentation, we only describe the SNC configuration for a connection between the SAP J2EE Engine and an SAP system application server. For other connections, see the SNC User’s Guide, which is available on the SAP Service Marketplace at http://service.sap.com/security.
· The external security product is installed on the server.

In this documentation, we only describe the configuration when using the SAP Cryptographic Library. For more information, see Installing the SAP Cryptographic Library on the SAP J2EE Engine.
If you use a different security product, then see your security product’s documentation for any product-specific configuration steps.
· You are familiar with the SNC infrastructure. You know which Personal Security Environment (PSE) the application server uses for SNC and you know whether you are using a single PSE for both communication partners or individual ones. For more information, see Using the SAP Cryptographic Library for SNC in the SAP Library.
· SNC is activated on the application server.
...
1. Either create a Personal Security Environment (PSE) or copy the application server’s SNC PSE to the SAP J2EE Engine’s SECUDIR directory.
2. Create credentials for the SAP J2EE Engine.
3. If you are using individual PSEs, then exchange the two servers’ public-key certificates.
4. Set the SAP J2EE Engine’s SNC parameters.
5. Maintain the SNC system access control list on the application server.
The connection between the SAP J2EE Engine and the SAP System application server is protected with SNC.
