The definition of the system configuration (R3Config.dtd) for a SAP data source with SNC is extended with the following attributes:
<!ATTLIST r3system
…
snc_mode (true|false) "false"
snc_sso (true|false) "true"
snc_qop (1|2|3|8|9) "9"
snc_partnername CDATA #IMPLIED
snc_myname CDATA #IMPLIED
…
>
Attribute |
Description |
---|---|
snc_mode |
Enable/disable SNC Default: Disabled |
snc_sso |
SNC logon with user name and password (without single sign-on) Default: Use SSO |
snc_qop |
SNC service quality 1: Authentication only 2: Integrity protection 3: Confidentiality protection 8: Default specified by application server 9: Highest available security setting (default) |
snc_partnername |
SNC name of the application server (for example, p:CN=R3, O=XYZ-INC, C=US) |
snc_myname |
SNC name of the RFC client (for example, p:CN=Smith, O=XYZ-INC, C=EN) |
The user attribute previously required is now optional. Specifying the user name and password is not required for SNC unless it is specifically set using the snc_sso=false attribute.
The SNC configuration for PPM-2-SAP extractor data sources and for SAP data sources for PPM Data Analytics is identical.
Here is an example of a complete configuration when using SNC:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE r3systemconf SYSTEM "R3Config.dtd">
<r3systemconf>
<r3system configname="snc_connection"
appserver="xyz.com" systemnumber="00"
client="777" user="" snc_mode="true" snc_sso="true" snc_qop="9"
snc_partnername="p:CN=R3, O=XYZ-INC, C=US"
snc_myname="p:CN=Smith, O=XYZ-INC, C=DE"
language="" lastreaddate="19700101" lastreadtime="000000"
encryptpw="" />
</r3systemconf>