SAP Connector > Part III: Connections > SAP connections > SAP ODP Extractor connections
  

SAP ODP Extractor connections

Use the SAP ODP Extractor Connector to connect to SAP S/4HANA on-premise solutions. You must create the connection to the SAP system before designing the mapping or mapping task.
You can use SAP ODP Connector to create an application server connection or a load balancing connection to connect using the SAP user name and password. You can also use create a Secured Network Application (SNC) application server connection or a load balancing connection to connect to SAP S/4HANA using the SNC parameters.
You must create the connection to the SAP system before designing the mapping or mapping task.

SAP ODP Extractor connection properties

Select the SAP ODP Extractor connection type and configure the connection properties.
The following table describes the SAP ODP Extractor connection properties:
Connection property
Description
Runtime Environment
Runtime environment that contains the Secure Agent that you want to use to access SAP S/4HANA.
SAP Server Connection Type
The SAP server connection type to use.
Select from the following options:
  • - Application Server Connection. Connect to an SAP Application Server using the SAP user name and password.
  • - Application Server SNC Connection. Connect to an SAP Application Server using the secured network connection:
    • - With X.509 Certificate. You do not need to specify the SAP user name and password explicitly. You must provide the path of the x.509 certificate file.
    • - Without X.509 Certificate. You must provide the SAP user name.
  • - Load Balancing Server Connection. Connect to an SAP Application Server with the least load at run time.
  • - Load Balancing Server SNC Connection. Connect to an SAP Application Server using SNC with the least load at run time.
Note: Before you use an SNC connection, you must verify that SNC is configured both on the SAP Server and the machine where the Secure Agent runs.
The following table describes the properties that must configure when you select Application Server Connection as the connection type:
Connection property
Description
SAP Client Number
The client number of the SAP Server.
SAP Language
Language code that corresponds to the SAP language.
SAP Application Server
The host name of the SAP Application Server.
SAP System Number
The system number of the SAP Server to connect.
SAP Username
The SAP user name with the appropriate user authorization.
SAP Password
The SAP password.
Subscriber Name
A name which defines the Secure Agent as a unique subscriber in the SAP system. SAP uses this name to define unique operational delta queue (ODQ) in case of delta read from ODP.
Additional Parameters
Additional SAP parameters that the Secure Agent uses to connect to the SAP system.
For example, to generate SAP JCo and SAP CPIC trace, specify the following properties:
jco.client.trace="1";
jco.client.cpic_trace="3";
During the runtime, the JCo and CPIC traces file are generated in the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>\ICS\main\bin\rdtm
During the design time, the CPIC traces are generated in the tomcat.out files at the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>tomcat.out
The following table describes the properties that must configure when you select Load Balancing Server Connection as the connection type:
Connection property
Description
SAP Client Number
The client number of the SAP Server.
SAP Language
Language code that corresponds to the SAP language.
SAP Message Server
Host name of the SAP Message Server.
SAP System ID
The system ID of the SAP Message Server.
SAP Group
The login group name, for example, PUBLIC.
SAP Username
The SAP user name with the appropriate user authorization.
SAP Password
The SAP password.
Subscriber Name
A name which defines the Secure Agent as a unique subscriber in the SAP system.
SAP uses this name to define unique operational delta queue (ODQ) in case of delta read from ODP.
Additional Parameters
Additional SAP parameters that the Secure Agent uses to connect to the SAP system.
For example, to generate SAP JCo and SAP CPIC trace, specify the following properties:
jco.client.trace="1";
jco.client.cpic_trace="3";
During the runtime, the JCo and CPIC traces file are generated in the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>\ICS\main\bin\rdtm
During the design time, the CPIC traces are generated in the tomcat.out files at the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>tomcat.out
The following table describes the properties that must configure when you select Application Server SNC Connection as the connection type:
Connection property
Description
SAP Client Number
The client number of the SAP Server.
SAP Language
Language code that corresponds to the SAP language.
SAP Application Server
The host name of the SAP Application Server.
SAP System Number
The system number of the SAP Server to connect.
SNC My Name
Optional. The Informatica client Personal Security Environment (PSE) or certificate name.
Default length is 256.
SNC Partner Name
The Informatica client PSE or certificate name.
Default length is 256.
SNC Quality of Protection (QoP)
Specifies the SAP PSE or certificate name.
You can select from the following options:
  • - 1 - Apply authentication only.
  • - 2 - Apply integrity protection (authentication).
  • - 3 - Apply privacy protection (integrity and authentication).
  • - 8 - Apply the default protection.
  • - 9 - Apply the maximum protection.
Default is 3 - Apply privacy protection (integrity and authentication).
SAP Cryptographic Library Path
The path to the cryptographic library.
Specify sapcrypto.dll for Windows or libsapcrypto.so for Linux.
Use X509 Certificate
Specifies the quality of protection. Select to use X509 Certificate based SNC connection.
X509 Certificate Path or SAP Username
The path to the X509 certificate file.
If you select to use the X509 certificate, specify the path to the X509 certificate file with .crt extension. You do not need to specify the SAP user name and password.
If you do not want to use the X509 certificate, specify the SAP user name for which SNC is configured in SAP Server.
Subscriber Name
A name which defines the Informatica Secure Agent as a unique subscriber in the SAP system.
SAP uses this name to define unique operational delta queue (ODQ) when the Secure Agent reads delta data from ODP.
Additional Parameters
Additional SAP parameters that the Secure Agent uses to connect to the SAP system.
For example, to generate SAP JCo and SAP CPIC trace, specify the following properties:
jco.client.trace="1";
jco.client.cpic_trace="3";
During the runtime, the JCo and CPIC traces file are generated in the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>\ICS\main\bin\rdtm
During the design time, the CPIC traces are generated in the tomcat.out files at the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>tomcat.out
The following table describes the properties that must configure when you select Load Balancing Server SNC Connection as the connection type:
Connection property
Description
SAP Client Number
The client number of the SAP Server.
SAP Language
Language code that corresponds to the SAP language.
SAP Message Server
Host name of the SAP Message Server.
SAP System ID
The system ID of the SAP Message Server.
SAP Group
The login group name, for example, PUBLIC.
SNC My Name
Optional. The Informatica client PSE or certificate name generated on the Secure Agent machine.
Default length is 256.
SNC Partner Name
The Informatica client PSE or certificate name generated on the SAP Server.
Default length is 256.
SNC Quality of Protection (QoP)
Specifies the SAP PSE or certificate name.
You can select from the following options:
  • - 1 - Apply authentication only.
  • - 2 - Apply integrity protection (authentication).
  • - 3 - Apply privacy protection (integrity and authentication).
  • - 8 - Apply the default protection.
  • - 9 - Apply the maximum protection.
Default is 3 - Apply privacy protection (integrity and authentication).
SAP Cryptographic Library Path
The path to the cryptographic library.
Specify sapcrypto.dll for Windows or libsapcrypto.so for Linux.
Use X509 Certificate
Specifies the quality of protection. Select to use X509 Certificate based SNC connection.
X509 Certificate Path or SAP Username
The path to the X509 certificate file.
If you select to use the X509 certificate, specify the path to the X509 certificate file with .crt extension. You do not need to specify the SAP user name and password.
If you do not want to use the X509 certificate, specify the SAP user name for which SNC is configured in SAP Server.
Subscriber Name
A name which defines the Informatica Secure Agent as a unique subscriber in the SAP system.
SAP uses this name to define unique operational delta queue (ODQ) when the Secure Agent reads delta data from ODP.
Additional Parameters
Additional SAP parameters that the Secure Agent uses to connect to the SAP system.
For example, to generate SAP JCo and SAP CPIC trace, specify the following properties:
jco.client.trace="1";
jco.client.cpic_trace="3";
During the runtime, the JCo and CPIC traces file are generated in the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>\ICS\main\bin\rdtm
During the design time, the CPIC traces are generated in the tomcat.out files at the following location:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<DIS version>tomcat.out