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), CentOS, and Fedora.

Minimum Linux Versions

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

OS	Min. Version
Ubuntu	11.04
Debian	7
RHEL	6.9
CentOS	6.9
Fedora	13
SUSE	12.1

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/CentOS/Fedora:
  

  yum install glibc libstdc++ zlib libgcc

Here are the corresponding libraries required by the driver:

Debian/Ubuntu Package	RHEL/CentOS/Fedora Package	File
libc6	glibc	linux-vdso.1
libc6	glibc	libm.so.6
libc6	glibc	librt.so.1
libc6	glibc	libdl.so.2
libc6	glibc	libpthread.so.0
libc6	glibc	libc.so.6
libc6	glibc	ld-linux-x86-64.so.2
libstdc++6	libstdc++	libstdc++.so.6
zlib1g	zlib	libz.so.1
libgcc1	libgcc	libgcc_s.so.1

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

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

rpm -ivh /path/to/driver/MarketoODBCDriverforUnix.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-marketo/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 Marketo

Marketo supports two APIs: REST and SOAP. To specify the API to be used, configure the Schema property to either REST or SOAP.

REST API

The REST API uses OAuth to authentication to validate the user's access. To set up access to Marketo via the REST API:

1. Create a custom service.
2. Obtain the appropriate OAuth credentials.
3. Configure the connection variables.

Creating a Custom Service

This procedure creates a new role with REST API privileges, assigns that role to an existing or new user, and creates a new service. It must be executed by a user with Admin privileges.

1. Navigate to the Marketo application's Admin area.
2. Navigate to the Security section.
3. Click Users & Roles.
4. Create a new role for API Access:
   1. Select the Roles tab.
   2. Click New Role.
   3. Specify a Role Name and select Role permissions. Specify Access API permissions that are specific to the REST API.
5. Assign or create a new User to execute API Access:
   1. Select the Users tab.
   2. To assign a new user the role you just created, click Invite New User.
   3. Enter the new user information, and assign them the role you just created with REST API access. To denote the user as an API Only user, select the API Only option.
6. Create the new service:
   1. Navigate to Admin > Integration and click the LaunchPoint option.
   2. Click New Service.
   3. Specify the Service Type of Custom.
   4. Enter a display name and description for the service.
   5. Assign the user you just created, to the service.

Marketo creates a new REST API service designed for connecting and authenticating to Marketo. It also generates the OAuth-based authentication credentials required for validating user access to the REST API.

Obtaining OAuth Credentials

To obtain and record the new service's OAuth credentials, return to the Marketo Admin area and navigate to the LaunchPoint option.

Click the View Details link for the service you just created. Marketo displays a window that shows the authentication credentials. These credentials provide the values for OAuthClientId and OAuthClientSecret.

Setting Connection Variables

After you have set the following connection variables, you are ready to connect via the REST API:

• Schema: REST.
• OAuthClientId: The OAuth Client ID associated with your custom service.
• OAuthClientSecret: The OAuth Client Secret associated with your custom service.
• RESTEndpoint: The URL of the REST Web service endpoint, as found in the Admin area. Navigate to the REST API Integration > Web Services section to find this URL. Leave Identity Endpoint blank.

SOAP API

After you have set the following connection variables, you are ready to connect via the SOAP API:

• Schema: SOAP.
• UserId: The client access ID, found in the Integration section of the Marketo Admin SOAP API panel.
• EncryptionKey: The Marketo SOAP API Encryption Key, generated on the Admin page of the Marketo website.
• SOAPEndpoint: The URL of the SOAP Web service endpoint, provided on the Admin page of the Marketo website.

Installing Dependencies for OAuth Authentication

The OAuth authentication standard requires the authenticating user to interact with Marketo, using a web-browser. If the first OAuth interaction is to be done on the same machine the driver is installed on, for example, a desktop application, the driver needs access to the xdg-open program, which opens the default browser.

To satisfy this dependency, install the corresponding package with your package manager:

Debian/Ubuntu Package	RHEL/CentOS/Fedora Package	File
xdg-utils	xdg-utils	xdg-open

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

[Driver]
AnsiCodePage = 932