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/DynamicsGPODBCDriverforUnix.deb 

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

rpm -ivh /path/to/driver/DynamicsGPODBCDriverforUnix.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-dynamicsgp/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 Microsoft Dynamics GP

To connect set URL to the Web services endpoint; for example, http://{servername}:{port}/Dynamics/GPService. Additionally, set CompanyId to the unique identifier of the company you are connecting to. You can obtain this value by querying the Company table and leaving the property empty.

Authenticating to Microsoft Dynamics GP

The Microsoft Dynamics GP data source supports the following authentication methods:

• Anonymous Authentication
• WS-Security (WSS) Authentication
• Basic Authentication
• NTLM User Authentication
• Digest
• Negotiate (Kerberos)

Anonymous Authentication

In some situations, you can connect to Microsoft Dynamics GP without setting any authentication connection properties. To do so, set the AuthScheme to None, and you are ready to connect.

WS-Security (WSS)

Set the User and Password to connect and set AuthScheme to WSS.

Note: WSS Authentication is the default authentication scheme.

Basic

Set the User and Password to connect and set AuthScheme to Basic.

Windows (NTLM)

Set the Windows User and Password to connect and set AuthScheme to NTLM.

Digest

Set the User and Password to connect and set AuthScheme to Digest.

Kerberos

See Using Kerberos for details on how to authenticate with Kerberos.

Fine Tuning Data Access

The driver returns data summaries by default to save performance. Set LookupIds to true to return details such as line items; however, note that entities must be retrieved one at a time.

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-dynamicsgp/lib/cdata.odbc.dynamicsgp.ini':

[Driver]
AnsiCodePage = 932