Client Interfaces Guide > Connecting to TDV Server through ODBC > Adding a New System DSN
 
Adding a New System DSN
You can create a new System DSN to point ODBC clients to the appropriate data source published by TDV data services. If you plan to use Kerberos for integrated authentication, configure Kerberos following the instructions in the Kerberos topics in the TDV Administration Guide (in “Managing Security for TDV Resources” and “Configuring Kerberos Single Sign-On”).
To add a new system DSN
1. From the Windows Start menu, navigate to the ODBC Data Source Administrator window.
For example, under Windows 7, select Start > Control Panel > Administrative Tools, and double-click Data Sources (ODBC) from the list on the right. The ODBC Data Source Administrator window opens.
2. Select the System DSN tab and click the Add button.
 
The Create New Data Source window opens.
3. In that window, highlight the TDV driver you previously installed and click Finish.
The TDV <version> ODBC Driver Configuration window opens.
4. Configure the TDV Software ODBC driver by typing and selecting values as explained below.
Field
Description
DSN Name
A string for the client to use to address the data source.
Host
A DSN-designated name, or an IP octet, or localhost for a test client installed on the same computer as TDV.
Port
Number of the ODBC HTTP port (default 9401).
Encrypt
Check if you are using SSL authentication. If this is checked, the client will connect to the TDV server using the ODBC driver SSL port, (default 9403; the ODBC driver automatically uses base port + 2 for SSL client connections).
Integrated Authentication
Method for authenticating the ODBC connection: disabled (default), Kerberos, or NTLM.
Kerberos SPN
SPN for Kerberos to use to authenticate the ODBC connection. The text box is grayed out unless Kerberos is selected for Integrated Authentication.
User Name
TDV profile of the user connecting from the client. This should match a profile in either the Composite domain or a configured LDAP domain, unless anonymous or dynamic domain login is enabled.
Custom Java Procedures (CJP) can use Windows ODBC client user names in the TDV runtime. When a client running on Windows makes an ODBC connection to TDV, the TDV ODBC driver uses a Windows API to report the Windows user name from the current session on the client.
To retrieve the client user name within the CJP execution context /HOOK running on TDV, call ExecutionEnvironment.getProperty(loggedInUser).
TDV does not use the client’s Windows log-in user name for authentication.
Password
Password corresponding to user name.
Domain
Domain to which the user belongs.
Datasource
The TDV database name (the name of the database as it appears under Databases; no slashes) as published in the Databases node in the Studio resource tree.
For example, if you have published resources under test (shown as /services/databases/test in the tool tip), type just “test” in this field.
Catalog
Each data source can publish one or more catalogs. Use the Refresh button when all other fields are specified, and select a catalog.
Locale/Code Page
The locale/code page used by this ODBC client. Leave this blank if the ODBC driver should use the system default locale. Otherwise, choose a different locale/code page.
5. Click the Test button to try the connection.
If you do not get a message saying the connection test completed successfully, check the firewall and port setting to make sure the port is open for sending and retrieving messages.
6. Optionally, if you are using SSL security (you checked the Encrypt check box on the Basic tab), configure the Security tab for your Windows platform:
Field
Description
SSL Key ID
The subject (CN) of Windows private certificate. You can locate it using this procedure:
1. Run the certmgr.msc program to open the Windows Certificate Manager.
2. Under Personal/Certificates, double-click the private certificate to open the Certificate dialog.
3. Click the Details tab, then select the Subject field.
Enter the Subject CN value in the SSL Key ID field. This is the only parameter you need to specify for Windows.
SSL Key Cert
The absolute path of a PEM file that contains the public key certificate for an SSL connection. (Optional)
SSL Key File
The absolute path of a PEM file that contains private key certificate for an SSL connection. This private key should match public key in SSL Key Cert. (Optional)
SSL CA Cert
The PEM file that contains the trusted CA certificates in PEM format. (Optional)
SSL CA Path
The absolute path of the directory that contains the trusted CA files in PEM format. On the Linux platform, the default value is “/etc/ssl/certs”. The CA PEM file name in the CA path directory must equal the hash value for the CA PEM file name. (Optional)
Note that on the Windows platform, the ODBC driver loads all CA certificates from the system store ROOT/CA/TRUST, so this parameter is not used.
Validate Remote Certification
Check to validate the remote certifications.
Validate Remote Hostname
Check to validate the remote hostname.
7. Click OK back through the windows to save the new System DSN.
With these configurations, both the TDV Server and the 32-bit or 64-bit ODBC client should be ready for use.
Note: SQL statements generated by ODBC clients must enclose reserved keywords in double-quotes when they are used as column aliases. For a consolidated list of reserved keywords, see the TDV Reference Guide. Edit an auto-generated MS-Query by renaming a column name with an alias.