Every Xtract IS component needs a connection manager to establish access to the SAP system. To create a new connection manager, please right-click in the area of the data flow task where the connection managers are located and choose New connection. The dialog shown below will then appear.
Select XTRACT from the list and click Add…
To configure the SAP connection, please double-click the connection manager icon.
The form must be filled in as shown below. Please fill in the text boxes with the logon data (user name, client, language, password). If you need to log on to a single application host, fill in the fields Host and System Number. If you want log on by load-balancing, the message server field, the logon group and SID must be entered.
If you don’t know what values to fill in, you may find that information by taking a look at the entries in your SAP logon pad. Otherwise please ask your SAP Basis team for help.
If everything is filled out correctly, try to establish a connection to SAP by clicking the Test Connection button. If the connection is ok, you can start using the Xtract IS components now.
Both RFC libraries are supported: Classic RFC and NetWeaver RFC library. Note: When using the NetWeaver RFC library with DeltaQ or OHS extractions, the RFC destination in SM59 must be set to Unicode.
You also have the option to log debug information. If you want to log debug information you have to enter a valid directory path into the Log Directory field in the connection manager.
Please note that the logging usually should only be activated when requested by the Theobald Software support team. There is plenty of information that will be collected. This can decrease the capacity of your hard drives dramatically. Please note that the default logging is independent of the debug logging settings. The default logging will be accessed even if the trace directory entry in the connection manager is left blank.
see also SAP Connection with SNC
Enable SNC(Secure Network Connection) for data encryption between SAP and Xtract IS.
Requires respective settings on the SAP side, as well. Please contact your SAP Basis team for support.
SNC Library (32 Bit, Visual Studio)
Path to 32 bit version of encryption library used (when running the package in debug mode in VS/SSDT).
SNC Library (64 Bit)
Path to 64 bit version of encryption library used (when running the deployed package on SSIS server).
SNC partner name
Quality of Protection
Defines the SNC level of protection.
Since 09.2017, SAP connection parameters are no longer stored as a single connection string but as properties.
There is a property for each component of the connection string. See Screenshot below.
This allows for using a sensitive environment variable for the password in the Integration Services catalog.
The connection string (see legacy mode below) did not support sensitive environment variables.
This provides stronger encryption than password obfuscation (see below).
You can either use connection properties or a connection string, not both.
Legacy storage mode (connection string)
SAP connection parameters are set via a single connection string (default in XIS versions pre 09.2017).
Obfuscates SAP connection password so it’s not stored in clear text. Switched on per default when activating Legacy storage mode.
Force Codepage in Strings (deprecated)
Data from non-unicode SAP systems is converted into a codepage that is as close as possible to the original codepage of the source system (e.g. 1250 for Central Europe). This parameter enables to override the automatic codepage with a custom codepage.
Alternate BAPI for Internal Table Queries (deprecated)
Our products use the remote function RFC_READ_TABLE to perform look-ups and read metadata from SAP, but the execution of this function module may be prohibited in some SAP systems . This option allows to define an alternate remote function, e.g. Z_XTRACT_IS_TABLE.