How to Configure the SAP Secure Network Communication Protocol in Informatica Cloud Data Integration®

How to Configure the SAP Secure Network Communication Protocol in Informatica Cloud Data Integration®

Configuring the SNC parameters in the connection properties

Configuring the SNC parameters in the connection properties

For SAP BAPI and SAP BW Connectors, you must configure the SNC parameters in the connection properties.
You can configure SNC for the following logon types in both the application and load balancing connections:
  • X.509 certificate: Log in with SNC encryption using the X.509 certificate.
  • Single sign on: Log in using the SAP credentials. The SAP user must be configured for SSO in the SAP server. When you use this log in type, you are not required to provide the SAP user password in the SAP connection.
  1. Open the connection.
  2. To enable the SNC protocol and secure communications between Cloud Data Integration and SAP, specify the parameters based on the connection type:
    1. To use the application connection with SNC and single sign on, specify the following parameters:
      • SNC_MODE = 1
      • SNC_QOP=3
      • SNC_MYNAME = p:CN=<common name>, OU=<organizational unit>. This is the SNC name of the machine on which the Secure Agent is installed.
      • SNC_PARTNERNAME = p:CN=<common name>, OU=<organizational unit>, OU=SAP Web AS, O=<organization>, C=<country>. This is the SNC name of the SAP system.
      • SNC_LIB = <Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows>
    2. To use the application connection with SNC and X.509 log on, specify the following parameters:
      • SNC_MODE = 1
      • SNC_QOP=3
      • SNC_MYNAME=p:CN=<common name>, OU=<organizational unit>, O=<organization>, C=<country> This is the SNC name of the machine on which the Secure Agent is installed.
      • SNC_PARTNERNAME= p:CN=<common name>, OU=<organizational unit>, OU=SAP Web AS, O=<organization>, C=<country>. This is the SNC name of the SAP system.
      • SNC_LIB =<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows>
      • X509CERT=MIIC8TCCAdkCCAogIAkiCAhIMA0GCSqGSIb3DQ (…)
    3. To use the load balancing connection with SNC and single sign on, specify the following parameters:
      • MSHOST= <Message server hostname>
      • GROUP=PUBLIC
      • R3NAME=SLT
      • SNC_MODE=1
      • SNC_QOP=3
      • SNC_MYNAME= p:CN=<common name>, OU=<organizational unit>, O=<organization>, C=<country> This is the SNC name of the machine on which the Secure Agent is installed.
      • SNC_PARTNERNAME= p:CN=<common name>, OU=<organizational unit>, OU=SAP Web AS, O=<organization>, C=<country>. This is the SNC name of the SAP system.
      • SNC_LIB =<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows>
    4. To use the load balancing connection SNC and X.509 log on, specify the following parameters:
      • MSHOST= <Message server hostname>
      • GROUP=PUBLIC
      • R3NAME=SLT
      • SNC_MODE=1
      • SNC_QOP=3
      • SNC_MYNAME= p:CN=<common name>, OU=<organizational unit>, O=<organization>, C=<country> This is the SNC name of the machine on which the Secure Agent is installed.
      • SNC_PARTNERNAME= p:CN=<common name>, OU=<organizational unit>, OU=SAP Web AS, O=<organization>, C=<country>. This is the SNC name of the SAP system.
      • SNC_LIB =<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows>
      • X509CERT=MIIC8TCCAdkCCAogIAkiCAhIMA0GCSqGSIb3DQ (…)
  3. Add the following entry for the SAP gateway service and message server that you want to use:
    • sapgw <system number> <port number of gateway service>/tcp
    • Sapms <System SID> <port number of gateway service>/tcp

0 COMMENTS

We’d like to hear from you!