Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • INFACore
  • All Products

Table of Contents

Search

  1. Preface
  2. Connections to source and target endpoints

Connections for INFACore

Connections for INFACore

Back Next

SAP ADSO

SAP ADSO

Create an SAP ADSO connection to read from or write to SAP ADSO.

Feature snapshot

Operation
Support
Read
Yes
Write
Yes

Connection properties

The following table describes the SAP ADSO Writer connection properties:
Connection property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
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.
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.
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
The IP address or the 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.
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 username for which SNC is configured in SAP Server.
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
The IP address or the 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 the SAP Server.
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
0 COMMENTS
We’d like to hear from you!