This section describes how to set up ODBC connectivity and configure DSNs on several Linux distributions: Debian-based systems, like Ubuntu, and Red Hat Linux platforms, like Red Hat Enterprise Linux (RHEL) and Fedora.

Minimum Linux Versions

Here are the minimum supported versions for Red Hat-based and Debian-based systems:

OS	Min. Version
Ubuntu	18.04
Debian	10
RHEL	8
Fedora	28
SUSE	15

Installing the Driver Dependencies

Run the following commands as root or with sudo to install the necessary dependencies:

• Debian/Ubuntu:
  

  apt-get install libc6 libstdc++6 zlib1g libgcc1

• RHEL/Fedora:
  

  yum install glibc libstdc++ zlib libgcc

Installing the Driver

You can use standard package management systems to install the driver.

On Debian-based systems, like Ubuntu, run the following command with root or sudo:

dpkg -i /path/to/driver/setup/SAPBusinessObjectsBIODBCDriverforUnix.deb 

On systems that support the RPM package format, run the following command with root or sudo:

rpm -ivh /path/to/driver/SAPBusinessObjectsBIODBCDriverforUnix.rpm 

Licensing the Driver

Run the following commands to license the driver. To activate a trial, omit the <key> input.

cd /opt/cdata/cdata-odbc-driver-for-sapbusinessobjectsbi/bin/
sudo ./install-license.sh <key>

Connecting through the Driver Manager

The driver manager loads the driver and passes function calls from the application to the driver. You need to register the driver with the driver manager and you define DSNs in the driver manager's configuration files.

The driver installation registers the driver with the unixODBC driver manager and creates a system DSN. The unixODBC driver manager can be used from Python and from many other applications. Your application may embed another driver manager.

Creating the DSN

See Using unixODBC to install unixODBC and configure DSNs. See Using the DataDirect Driver Manager to create a DSN to connect to OBIEE, Informatica, and SAS.

Connecting to SAPBusinessObjectsBI

To connect to your SAP BusinessObjects BI instance, you must set the following:

• Url: The SAP BusinessObjects BI REST API URL. To discover this:
  1. Log into the Central Management Console.
  2. Choose Applications from the combo box.
  3. Select RESTful Web Service. The Central Management Console displays the access URL, which is http://{Server-Name}:6405/biprws by default.

• AuthScheme: Set this to the type of authentication to use when connecting to SAP BusinessObjects BI.

Basic

To connect to SAP BusinessObjects BI using Basic authentication, set the AuthScheme to Basic, and set these properties:

• User: The username of your instance.
• Password: The password of your instance.

CyberArk

To connect to CyberArk, set the AuthScheme to CyberArk, and set these properties:

• User: The CyberArk login name (user@domain).
• Password: The CyberArk user's password.
• SSOLoginURL: The app's single sign on URL.
• SSOExchangeUrl: The url used for the exchange of the SAML token for SAP BusinessObjects BI credentials.

If you have configured MFA, you must use combinations of SSOProperties to authenticate using CyberArk. Set any of the following, as applicable:

• MFAType: If you have configured MFA, set this to the name of the mechanism that should be selected during authentication.
• MFAPassCode: If you have configured MFA, set this to a valid answer for the selected mechanism.
  If you set this to an empty or an invalid value, the driver initiates the out-of-band mechanism. The driver polls the API until the challenge is completed through user interaction before deciding on closing the connection.
• MFATimeout: If you have configured MFA, set this to the number of seconds the driver should continue polling the API until the challenge is completed through user interaction. By default, the driver polls the API for 60 seconds before closing the connection.
  

Example connection string:

AuthScheme=CyberArk;SSOLoginURL='https://abc1234.id.cyberark.cloud/run?appkey=00000000-0000-0000-0000-000000000000&customerId=ABC1234';User=cyberarkUserName;Password=cyberarkPassword;SSOExchangeUrl=http://myserver:8080/biprws/saml/SSO;

Set the Driver Encoding

The ODBC drivers need to specify which encoding to use with the ODBC Driver Manager. By default, the CData ODBC Drivers for Unix are configured to use UTF-16 which is compatible with unixODBC, but other Driver Managers may require alternative encoding.

Alternatively, if you are using the ODBC driver from an application that uses the ANSI ODBC API it may be necessary to set the ANSI code page. For example, to import Japanese characters in an ANSI application, you can specify the code page in the config file '/opt/cdata/cdata-odbc-driver-for-sapbusinessobjectsbi/lib/cdata.odbc.sapbusinessobjectsbi.ini':

[Driver]
AnsiCodePage = 932