To connect to a specific ODBC-compliant endpoint, you need to perform certain prerequisite tasks to install the database or data warehouse-specific ODBC driver and ODBC client on the Secure Agent machine to connect to your database or data warehouse.
Additionally, when you use Kerberos authentication to connect to DB2 or SAP Sybase ASE, you need to complete Kerberos authentication prerequisites.
Configure the ODBC driver
To use an ODBC connection, you'll need to set up a system Data Source Name (DSN) for the database or data warehouse-specific ODBC driver, and then install the ODBC driver and ODBC client on the Secure Agent machine.
An ODBC client can access any database and data warehouse for which you install an ODBC driver. Ensure that the ODBC driver you install complies with the ODBC-compliant endpoint to which you want to connect.
An ODBC connection uses only the system DSN. You can't use the user DSN when you configure an ODBC driver. When you set up the system DSN, you need to specify the data source name and connection string.
This section provides instructions to configure the ODBC driver on Windows and Linux machines that host the Secure Agent. You can use these instructions to set up your endpoint-specific ODBC driver. In certain cases, you might need to set environment variables after the driver configuration. You can refer to the examples to help you set up your driver.
Configure the ODBC driver on Linux
Before you establish an ODBC connection to connect to an ODBC-compliant database or data warehouse on Linux, configure the ODBC driver.
1Download the ODBC drivers from the database or data warehouse-specific website.
Note: To get the DB2 ODBC 64-bit driver and SAP IQ ODBC 64-bit driver, contact Informatica Global Customer Support.
2Install the ODBC drivers on the Secure Agent machine.
3Add entries for the data sources in the odbc.ini file.
You can use the odbc.ini file for configuring data sources when you create an ODBC connection.
This section provides sample entries for certain ODBC connection types in the odbc.ini file. You can refer to these samples to specify connection entries for your specific endpoint.
Microsoft Azure SQL Data Warehouse ODBC connection
Create this connection to connect to the Microsoft Azure SQL Data Warehouse endpoint.
The following sample shows a connection entry for the Microsoft Azure SQL Data Warehouse data sources in the odbc.ini file:
Before you establish an ODBC connection to connect to an ODBC-compliant database or data warehouse on Windows, configure the ODBC driver.
1Download the ODBC drivers from the database or data warehouse-specific website.
Note: To get the DB2 ODBC 64-bit driver and SAP IQ ODBC 64-bit driver, contact Informatica Global Customer Support.
2Install the ODBC drivers on the Secure Agent machine.
3Open the folder in which ODBC data source file is installed.
4Run the odbcad32.exe file.
The ODBC Data Source Administrator dialog box appears.
5Click System DSN.
Note: An ODBC connection uses only system DSNs. You can't use user DSNs when you configure an ODBC driver.
6Select the system data source that you want to use, and click Add.
The Create New Data Source dialog box appears.
7Select an ODBC driver for which you want to set up a data source.
8Click Finish.
A dialog box appears for setting up the selected driver.
9Specify the required connection properties for the driver.
10Click OK to save the changes for the configured ODBC driver.
Note: If you configure the DB2 ODBC driver, click Test Connect to test the connection that you configured, specify the credentials of the DB2 database in the Logon to DB2 Wire Protocol dialog box, and then save the changes.
Prepare for Kerberos authentication
You can use Kerberos authentication to connect to DB2 or SAP Sybase ASE databases by placing the required configuration files on the Secure Agent machine. You can also use Kerberos authentication to connect to SSL-enabled DB2 or SAP Sybase ASE databases.
When you configure Kerberos authentication to connect to DB2 or SAP Sybase ASE, consider the following guidelines:
•You can't use the Hosted Agent or serverless runtime environment.
•Ensure that the Secure Agent and database server that you use are registered in the KDC server.
•You can't add more than one KDC to a krb5.conf file.
•You can't generate a credential cache file for more than one Kerberos principal user.
Configure Kerberos authentication
Before you use Kerberos authentication to connect to DB2 or SAP Sybase ASE on Linux or Windows, the organization administrator needs to perform the prerequisite tasks.
1To configure the krb5.conf file, perform the following tasks:
aCreate a krb5.conf file on the Secure Agent machine.
bAdd the details of the Key Distribution Center (KDC) and admin server to the krb5.conf file in the following format:
[realms] <REALM NAME> = { kdc = <Location where KDC is installed> admin_server = <Location where KDC is installed> } [domain_realm] <domain name or host name> = <Domain name or host name of Kerberos> <domain name or host name> = <Domain name or host name of Kerberos>
2Set the following environment variables on the Secure Agent machine.
4To generate the credential cache file on the Secure Agent machine and use Kerberos authentication to connect to the selected ODBC subtype, perform the following tasks:
aOn the Secure Agent machine, run the following command and specify the user name and realm name of the selected ODBC subtype:
Kinit <user name>@<realm_name>
bWhen prompted, enter the password for the Kerberos principal user.
Set environment variables
To use Kerberos authentication to connect to DB2 or SAP Sybase ASE, you need to set the required environment variables on the Secure Agent machine.
•setenv KRB5CCNAME <Absolute path and file name of the credentials cache file>
•setenv KRB5_CONFIG <Absolute path of the Kerberos configuration file>\krb5.conf
After you set the environmental variables, you need to restart the Secure Agent.
Alternatively, you can add the environment variables when you create an ODBC connection with the subtype as DB2 or SAP Sybase ASE.
Enter the KRB5_CONFIG and KRB5CCNAME details in the Kerberos Connection Properties field in the ODBC connection.
For example, add the properties in the following format:
KRB5_CONFIG=<Absolute path of the Kerberos configuration file>\krb5.conf;KRB5CCNAME=<Absolute path of the credential cache file>/<File name>
Note: Ensure that you separate each key-value pair with a semicolon.