Source connections
Configure a source connection for each data source that you want to read data from. Configure source connections on the Configure Source page.
The way in which you configure source connections varies based on whether your organization administrator has configured Enterprise Data Catalog integration properties in Administrator:
- •If Enterprise Data Catalog integration properties are configured and you select a source object from Enterprise Data Catalog, you can import the source connection when you select the object.
- •If Enterprise Data Catalog integration properties are not configured or if the source object is not in Enterprise Data Catalog, you configure the source connection manually.
The following image shows the Configure Source page when Enterprise Data Catalog integration properties are configured:
The page displays the total number of table, view, and flat file assets in the catalog. Use the search field to search for objects in the catalog, or click Configure Connection to configure a source connection manually.
The following image shows the Configure Source page when Enterprise Data Catalog integration properties are not configured or when you click Configure Connection:
The page lists the source types and connection details for each source type. It also displays information about each source connector. The version displayed in the connector information is the connector version, not the data source version.
To create a source connection, select the source type, enter the connection details, and then click Save. To test the connection, click Test Connection.
If the source type you need is not listed on the page, click Find additional connector types. This link opens the Add-On Connectors page in Administrator where you can install additional source connectors. After you install the connector, create a connection to the data source on the Connections page in Administrator. For more information about installing add-on connectors and creating connections, see the Administrator help.
Importing connections for Enterprise Data Catalog sources
If Enterprise Data Catalog integration properties are configured in Administrator, you can select an Enterprise Data Catalog asset as the source for an Azure data sync task. When you select an Enterprise Data Catalog asset as a source, you can import the source connection if it does not already exist.
How you select an asset as the source for an Azure data sync task varies based on whether the connection exists in Data Accelerator for Azure:
- •If the connection already exists, you can select the asset as the source when you create an Azure data sync task. Alternatively, you can search for the asset on the Configure Source page. When you select the asset, Data Accelerator for Azure creates an Azure data sync task with the selected asset as the source.
- •If the connection does not exist, search for the asset on the Configure Source page. When you select the asset in the search results, Data Accelerator for Azure prompts you to import the source connection.
Searching for Enterprise Data Catalog assets
Use the search on the Configure Source page to find an Enterprise Data Catalog asset. Enter the asset name, part of the name, or keywords associated with the asset in the Search field, and then click the search icon. Data Accelerator for Azure returns all tables, views, and flat files in the catalog that match the search criteria.
You can use the * and ? wildcard characters in the search string. For example, to find assets that start with the string "Cust", enter Cust* in the Search field.
You can also enter keyword searches. For example, if you enter tables with order in the Search field, Data Accelerator for Azure returns tables with "order" in the name or description, tables that have the associated business term "order," and tables that contain columns for which the "order" data domain is inferred or assigned.
For more information about Enterprise Data Catalog searches and search results, see the Enterprise Data Catalog documentation.
The following image shows an example of search results when you enter "tables with order" as the search string:
- 1. Filter search results.
- 2. Show asset details.
- 3. Sort search results.
- 4. Use the asset as the source for an Azure data sync task.
You can perform the following actions on the search results page:
- Filter search results.
- Use the filters to filter search results by asset type, resource type, resource name, number of rows, and date last updated.
- Show asset details.
- To display details about the asset, click Show Details.
- Sort results.
- Use the Sort icon to sort results by relevance or name.
- Open an asset.
- To open an asset in Enterprise Data Catalog, click the asset name. To view the asset, you must log in to Enterprise Data Catalog with your Enterprise Data Catalog user name and password.
- Select an asset as the source for an Azure data sync task.
To select the asset, click Use as source. You can select an asset if your organization has the appropriate connector license and if the asset is a valid source type for Azure data sync tasks. For example, you can select an Oracle table to use as a source, but you cannot select a Hive table.
When you select the source asset, Data Accelerator for Azure prompts you to import the source connection if it does not exist. Connection properties vary based on the source type. Data Accelerator for Azure imports most connection properties from the resource configuration in Enterprise Data Catalog, but you must enter other required properties such as the connection name and password.
After you configure the connection or if the connection already exists, Data Accelerator for Azure creates a new Azure data sync task and selects the asset as the source object.
Flat file connections
Configure a flat file connection to read data from flat files that are stored in the same directory. Data Accelerator for Azure can read data from delimited flat files. The delimiter character must be a comma (,), the text qualifier must be double quotation marks ("), and the files must use the same date format.
The following table describes the flat file connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the flat files. |
Directory | Directory where the flat files are stored. Note: Do not include the name of the flat file. You specify the file name when you create the task. |
Date Format | Date format for date fields in the flat files. |
Code Page | Code page of the system that hosts the flat files. Select one of the following code pages: - - MS Windows Latin 1. Select for ISO 8859-1 Western European data.
- - UTF-8. Select for Unicode data.
- - Shift-JIS. Select for double-byte character data.
- - ISO 8859-15 Latin 9 (Western European)
- - ISO 8859-2 Eastern European
- - ISO 8859-3 Southeast European
- - ISO 8859-5 Cyrillic
- - ISO 8859-9 Latin 5 (Turkish)
- - IBM EBCDIC International Latin-1
- - Japanese Extended UNIX Code (incl.JIS X 0212)
- - Japanese EUC (with \ <-> Yen mapping)
- - IBM EBCDIC Japanese
- - IBM EBCDIC Japanese CP939
- - PC Japanese SJIS-78 syntax (IBM-942)
- - PC Japanese SJIS-90 (IBM-943)
- - MS Windows Traditional Chinese, superset of Big 5
- - Taiwan Big-5 (w/o euro update)
- - Chinese EUC
- - ISO 8859-8 Hebrew
- - PC Hebrew (old)
- - PC Hebrew (w/o euro update)
- - EBCDIC Hebrew (updated with new sheqel, control characters)
Note: When you use a flat file connection with the Shift-JIS code page and a UTF data object, be sure to install fonts that fully support Unicode. |
Microsoft SQL Server connections
Configure a Microsoft SQL Server connection to read data from a Microsoft SQL Server data source. You can use a Microsoft SQL Server connection to connect to Microsoft Azure SQL databases.
The following table describes the Microsoft SQL Server connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the Microsoft SQL Server data source. |
SQL server version | Microsoft SQL Server database version. |
Authentication mode | Authentication method to access Microsoft SQL Server. Select one of the following methods: - - Windows Authentication: Use Microsoft Windows authentication to access Microsoft SQL Server. This option is available when you access Data Accelerator for Azure using Microsoft Windows. When you choose this option, you do not need to enter credentials to access Microsoft SQL Server. To use Windows authentication in an SQL Server connection, ensure that the user account that starts the Secure Agent service is available in the Microsoft SQL Server database.
Note: Windows authentication is not certified for Microsoft SQL Server 2017 version hosted on Linux. - - SQL Server: Enter your Microsoft SQL Server user name and password to access Microsoft SQL Server.
- - Active Directory Password: Enter the Azure Active Directory user name and password to authenticate and access Microsoft Azure SQL Database.
|
User name | User name for the database login. Does not apply if you use Windows authentication mode to access Microsoft SQL Server. The user name cannot contain a semicolon. Specify the username in the following format to connect to Microsoft Azure SQL databases: username@host |
Password | Password for the database login. Does not apply if you use Windows authentication mode to access Microsoft SQL Server. The password cannot contain a semicolon. |
Host | Name of the machine hosting the database server. Specify the fully qualified host name to connect to Microsoft Azure SQL databases. For example: vmjcmwxsfboheng.westus.cloudapp.azure.com |
Port | Network port number used to connect to the database server. Default is 1433. |
Instance name | Instance name of the Microsoft SQL Server database. |
Database name | Database name for the Microsoft SQL Server target. Database name is case sensitive if the database is case sensitive. Maximum length is 100 characters. Database names can include alphanumeric and underscore characters. |
Schema | Schema used for the connection. |
Code page | The code page of the database server. |
Encryption method | The method that the Secure Agent uses to encrypt the data sent between the driver and the database server. You can use the encryption method to connect to Microsoft Azure SQL databases. |
Crypto protocol version | Cryptographic protocols to use when you enable SSL encryption. |
Validate server certificate | When set to true, the Secure Agent validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, the Secure Agent also validates the host name in the certificate. When set to false, the Secure Agent does not validate the certificate that is sent by the database server. |
Trust store | The location and name of the trust store file. The trust store file contains a list of Certificate Authorities (CAs) that the driver uses for SSL server authentication. |
Trust store password | The password to access the contents of the trust store file. |
Host name in certificate | Host name of the machine that hosts the secure database. If you specify a host name, the Secure Agent validates the host name included in the connection with the host name in the SSL certificate. |
Netezza connections
Configure a Netezza connection to read data from a Netezza database. Data Accelerator for Azure uses the Netezza ODBC driver to connect to the Netezza database.
To configure a Netezza connection to use as a source in Data Accelerator for Azure, perform the following tasks:
- 1. Configure Netezza.
- 2. Configure the Netezza connection properties in Data Accelerator for Azure.
Configuring Netezza
Before you can create a Netezza connection, you must install the Netezza client, configure database privileges, and configure the Netezza ODBC driver.
Perform the following tasks:
- Install the Netezza client.
- Install the Netezza client on Windows or Linux.
- Verify database privileges.
Verify that you have the following privileges on the Netezza database:
- - CREATE TABLE
- - CREATE EXTERNAL TABLE
- - DELETE
- - DROP
- - INSERT
- - LIST
- - SELECT
- - TRUNCATE
- - UPDATE
- Configure the driver.
After you install the Netezza client, perform the following tasks for the Netezza ODBC driver based on the operating system:
- - On Windows, verify that the NetezzaSQL driver appears in the ODBC Data Source Administrator driver list.
- - On Linux, add the driver entries in the odbcinst.ini file in the Secure Agent installation directory:
The following code shows a sample entry:
[NetezzaSQL]
Driver = /data/home/adputf_9/cloud_td/Netezza/installer/linux64/lib64/libnzodbc.so
Setup = /data/home/adputf_9/cloud_td/Netezza/installer/linux64/lib64/libnzodbc.so
APILevel = 1
ConnectFunctions = YYN
Description = Netezza ODBC driver
DriverODBCVer = 03.51
DebugLogging = true
LogPath = /tmp
UnicodeTranslationOption = utf8
CharacterTranslationOption = all
PreFetch = 256
Socket = 16384
Netezza connection properties
Configure the Netezza connection properties on the Configure Source page of Data Accelerator for Azure.
The following table describes the Netezza connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the Netezza data source. |
Database | Name of the Netezza database. |
Schema name | Schema used for the Netezza data source. |
Server name | Netezza database host name. |
Port | Network port number used to connect to the database server. |
Driver | Netezza ODBC driver used to connect to the Netezza database. |
Runtime additional connection configuration | Additional run-time attributes required to fetch data. For example: -securityLevel=preferredUnSecured;caCertFile = |
Metadata additional connection configuration | The values to set the optional properties of the ODBC driver to fetch the metadata. |
User name | Database user name with the appropriate read permissions to access the database. |
Password | Password for the database user name. |
ODBC connections
Configure an ODBC connection to read data from any ODBC compliant database.
To configure an ODBC connection to use as a source in Data Accelerator for Azure, perform the following tasks:
- 1. Configure ODBC.
- 2. Configure the ODBC connection properties in Data Accelerator for Azure.
Configuring ODBC
Before you can create a ODBC connection, you must install the ODBC client, ODBC driver, and create a system DSN.
Perform the following tasks:
- Install the ODBC client.
- An ODBC client is a front-end application installed in your machine. You use the ODBC client application to connect to databases.
- Install the ODBC driver.
- An ODBC driver is a back-end application installed on a computer that is used to store data for access by several users. An ODBC driver processes ODBC function calls, submits SQL requests to a specific data source, and returns results to the client application. Choose a database driver that is compatible with the database to which you want to connect.
- Create a system DSN.
- Before you configure an ODBC connection in Data Accelerator for Azure, you must also create a system Data Source Name (DSN).
Any ODBC client can access any database for which there is an ODBC Driver.
ODBC connection properties
Configure the ODBC connection properties on the Configure Source page of Data Accelerator for Azure.
The following table describes the ODBC connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the ODBC data source. |
User name | User name for the database login. |
Password | Password for the database login. The password cannot contain a semicolon. |
Data source name | System DSN. |
Schema | Schema used for the source. |
Code page | The code page of the database server or flat file defined in the connection. Select one of the following code pages: - - MS Windows Latin 1. Select for ISO 8859-1 Western European data.
- - UTF-8. Select for Unicode data.
- - Shift-JIS. Select for double-byte character data.
- - ISO 8859-15 Latin 9 (Western European).
- - ISO 8859-2 Eastern European.
- - ISO 8859-3 Southeast European.
- - ISO 8859-5 Cyrillic.
- - ISO 8859-9 Latin 5 (Turkish).
- - IBM EBCDIC International Latin-1.
- - Japanese Extended UNIX Code (incl. JIS X 0212)
- - Japanese EUC (with \<-> Yen mapping)
- - Japanese EUC (Packed Format)
- - IBM EBCDIC Japanese
- - IBM EBCDIC Japanese CP939
- - Japanese EBCDIC Fujitsu
- - HITACHI KEIS Japanese
- - NEC ACOS JIPSE Japanese
- - UNISYS Japanese
- - MITSUBISHI MELCOM Japanese
- - Japanese EBCDIC-Kana Fujitsu
- - HITACHI KEIS-Kana Japanese
- - NEC ACOS JIPSE-Kana Japanese
- - UNISYS-Kana Japanese
- - MITSUBISHI MELCOM-Kana Japanese
- - EBCDIC Japanese
- - EBCDIK Japanese
- - PC Japanese SJIS-78 syntax (IBM-942)
- - PC Japanese SJIS-90 (IBM-943)
- - EBCDIC Japanese Katakana SBCS
- - EBCDIC Japanese Katakana (w/ euro)
- - EBCDIC Japanese Latin-Kanji (w/ euro)
- - EBCDIC Japanese Extended (DBCS IBM-1390 combined with DBCS IBM-1399)
- - EBCDIC Japanese Latin (w/ euro update)
- - EBCDIC Japanese Katakana SBCS (w/ euro update)
- - MS Taiwan Big-5 w/ HKSCS extensions
- - MS Windows Traditional Chinese, superset of Big 5
- - Taiwan Big-5 (w/ euro update)
- - Taiwan Big-5 (w/o euro update)
- - PC Chinese GBK (IBM-1386)
- - Chinese EUC
- - Simplified Chinese (GB2312-80)
- - Hong Kong Supplementary Character Set
- - ISO 8859-8 Hebrew
- - PC Hebrew (old)
- - PC Hebrew (w/o euro update)
- - PC Hebrew (w/ euro update)
- - MS Windows Hebrew (older version)
- - MS Windows Hebrew (w/o euro update)
- - Lotus MBCS encoding for Windows Hebrew
- - EBCDIC Hebrew (updated with sheqel, control characters)
- - EBCDIC Hebrew (w/ euro)
- - EBCDIC Hebrew (updated w/ euro and new sheqel, control characters)
- - Israeli Standard 960 (7-bit Hebrew encoding)
|
ODBC subtype | Categorizes the type of the connection so that pushdown optimization support can be enabled. Specify any one of the following subtypes: - - Azure DW. When you read from or write to Microsoft Azure SQL Data Warehouse, select Azure DW.
- - Google BigQuery. When you read from or write to Google BigQuery, select Google BigQuery.
- - Redshift. When you read from or write to Amazon Redshift, select Redshift.
- - Snowflake. When you read from or write to Snowflake, select Snowflake.
- - Other. When you read data from or write data to any other databases, select Other. For example, to connect to other databases such as Microsoft Access, IBM DashDB, NetSuite, Microsoft Excel, and Teradata, you must select Other. Default is Other.
Default is Other. |
Driver manager for Linux | When you create a new ODBC connection on Linux platform, you can select a driver manager for the Linux Secure Agent. Select one of the following driver managers: - - Data Direct
- - unixODBC2.3.0
- - unixODBC2.3.4
The default driver manager is UnixODBC2.3.0. To connect to Teradata, you can use only Data Direct as the driver manager on Linux. |
Oracle connections
Configure an Oracle connection to read data from an Oracle data source. You can create connections for Oracle version 10g, 11g, and 12c databases. You can connect to Oracle 12c databases that provide multitenancy and in-memory features.
Note: Oracle connections do not support the BLOB data type.
To configure an Oracle connection to use as a source in Data Accelerator for Azure, perform the following tasks:
- 1. Configure Oracle.
- 2. Configure the Oracle connection properties in Data Accelerator for Azure.
Configuring Oracle
Before you can create a Oracle connection, you must create a trust store certificate and key store certificate.
Perform the following tasks:
- Create a trust store certificate.
You must create a trust store certificate that contains all the certificates trusted by the client to establish a secure Oracle connection.
To create a trust store certificate, perform the following steps:
- 1. From the Oracle database, run the following keytool command to enable the SSL certificate:
keytool -import -trustcacerts -alias ca -file <server certificate with path> -keystore <name of truststore to be generated with extension> -storepass <password for truststore> -storetype <store type>
- 2. Add the server certificate to client certificates trust store.
- Create a key store certificate.
You must create a key store certificate that contains all the client certificates to establish an Oracle connection.
To create a key store certificate, perform the following steps:
- 1. Download and install the Oracle client from the Oracle website.
- 2. Run the following command to create an Oracle wallet:
orapki wallet create -wallet <Path where wallet is to be created> -auto_login -pwd <wallet password>
- 3. Run the following command to create a self-signed client certificate:
orapki wallet add -wallet <Path where wallet is to be created> -dn "CN=<common name>, OU=<organization unit>, O=<organization>, L=<locality>, ST=<state>, C=<country>" -keysize <key size in bits> -self_signed-validity <number of days> -pwd <wallet password>
You must specify the values of the common name, organization unit, organization, locality, state, country, key size, self-signed validity days, and wallet password from the server certificate.
- 4. Run the following orapki command to export the self-signed client certificate:
orapki wallet export -wallet <wallet path> -dn "CN=<common name>, OU=<organization unit>, O=<organization>, L=<locality>, ST=<state>, C=<country>" -cert <Name of the exported certificate with path>
The -dn command identifies the client certificate uniquely as server wallet contains multiple client certificates installed.
- 5. Install the self-signed client certificate in the server Oracle wallet.
Note: The client authentication fails if you do not add the self-signed client certificate to the server database Oracle wallet.
- 6. Add the server certificate as a trusted certificate to the Oracle wallet.
Run the following command to add the server certificate:
orapki wallet add -wallet <wallet path> -trusted_cert -cert <Name of the server certificate with path> -pwd <wallet password>
Oracle connection properties
Configure the Oracle connection properties on the Configure Source page of Data Accelerator for Azure.
The following table describes the Oracle connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the Oracle data source. |
User name | User name for the database login. The user name cannot contain a semicolon. |
Password | Password for the database login. The password cannot contain a semicolon. |
Host | Name of the machine that hosts the database server. |
Port | Network port number used to connect to the database server. Default is 1521. |
Service name | Service name or System ID (SID) that uniquely identifies the Oracle database. Specify the SID in the following format to connect to Oracle databases: SID:<ORACLE_SID> |
Schema | Schema used for the Oracle connection. |
Code page | Code page of the database server. |
Encryption method | Method that the Secure Agent uses to encrypt the data exchanged between the Secure Agent and the database server. |
Crypto protocol version | Cryptographic protocols to use when you enable SSL encryption. |
Validate server certificate | Validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, the Secure Agent also validates the host name in the certificate. |
Trust store | Location and name of the trust store file. |
Trust store password | Password to access the contents of the trust store file. |
Host name in certificate | Host name of the machine that hosts the secure database. If you specify a host name, the Secure Agent validates the host name included in the connection with the host name in the SSL certificate. |
Key store | Location and file name of the key store. |
Key store password | Password for the key store file required for secure communication. |
Key password | Password for the individual keys in the key store file required for secure communication. |
Connection retry period | Number of seconds that the Secure Agent tries to reconnect to the Oracle database after the initial connection attempt fails. If a connection cannot be established within the retry period, the Azure data sync task fails. The default is 0, which disables connection retries. |
Metadata advanced properties | Optional properties for the JDBC driver to fetch the metadata. If you specify more than one property, separate each key-value pair with a semicolon. For example, ConnectionRetryCount=2;ConnectionRetryDelay=20 To connect to an Oracle database enabled for advanced security, you can specify the Oracle advanced security options for the JDBC driver. For example, EncryptionTypes=AES256;EncryptionLevel=accepted;DataIntegrityLevel=accepted;DataIntegrityTypes=SHA1 |
Runtime advanced properties | Optional properties for the ODBC driver for running mappings. If you specify more than one property, separate each key-value pair with a semicolon. For example, charset=sjis;readtimeout=180 To connect to an Oracle database enabled for advanced security, you can specify the Oracle advanced security options for the ODBC driver. For example, EncryptionTypes=AES256;EncryptionLevel=1;DataIntegrityLevel=1;DataIntegrityTypes=SHA1;DataIntegrityTypes=SHA1 |
Teradata connections
Configure a Teradata connection to read data from a Teradata data source. Data Accelerator for Azure uses the Teradata Parallel Transporter Application Programming Interface (Teradata PT API) for data extraction.
To configure a Teradata connection to use as a source in Data Accelerator for Azure, perform the following tasks:
- 1. Configure Teradata.
- 2. Configure the Teradata connection properties in Data Accelerator for Azure.
Configuring Teradata
Before you can create a Teradata connection, you must install the Teradata Parallel Transporter utilities, set environment variables, and verify the database privileges.
Perform the following tasks:
- Install the Teradata Parallel Transporter utilities.
Install the Teradata Parallel Transporter utilities on the machine where the Secure Agent runs.
The Teradata Parallel Transporter utilities for versions 15.10x and 16.10.x includes the following utilities:
- - Teradata Parallel Transporter Base
- - Teradata Parallel Transporter Stream Operator
- - Teradata CLIv2
- - Teradata Generic Security Services
- - Shared ICU Libraries for Teradata
- Set environment variables.
The following table describes the environment variables you must set on Linux:
Environment Variable | Value |
|---|
THREADONOFF | Set this variable to 1 to enable multithreading support for Teradata processes. |
NLSPATH | Set this variable to the location of the opermsgs.cat file. For example: /opt/teradata/client/15.10/msg/%N |
You must also set the shared library environment variable based on the operating system.
The following table describes the shared library variables for each operating system:
Operating System | Value |
|---|
Windows | PATH |
Linux | LD_LIBRARY_PATH |
For example, use the following syntax for Linux:
- - Using a Bourne shell:
export LD_LIBRARY_PATH="/opt/teradata/client/15.10/lib64:${LD_LIBRARY_PATH}"
- - Using a C shell:
LD_LIBRARY_PATH="/opt/teradata/client/15.10/lib64:${LD_LIBRARY_PATH}
After you set the environmental variables, you must restart the Secure Agent.
- Verify the database privileges.
Verify that you have the following database privileges:
- - Read permission to read data from Teradata.
- - Write permission to write data to Teradata.
- - Select privileges on DBC.Tables, DBC.Columns, DBC.UDTInfo, and DBC.Databases.
For information about select privileges, see the Teradata JDBC Driver documentation.
Teradata connection properties
Configure the Teradata connection properties on the Configure Source page of Data Accelerator for Azure.
The following table describes the Teradata connection properties:
Property | Description |
|---|
Name | Name of the connection. |
Description | Optional description for the connection. |
Runtime environment | Name of the Secure Agent group that will be used to read data from the Teradata data source. |
TDPID | The name or IP address of the Teradata database machine. |
Tenacity | Amount of time, in hours, that the Teradata PT API continues trying to log on when the maximum number of operations runs on the Teradata database. Specify a positive integer. Default is 4. |
Database name | The Teradata database name. If you do not enter a database name, the Teradata PT API uses the default login database name. |
Code page | Code page associated with the Teradata database. Select one the following code pages: - - MS Windows Latin 1. Select for ISO 8859-1 Western European data.
- - UTF-8. Select for Unicode and non-Unicode data.
When you run a task that extracts data from a Teradata source, the code page of the Teradata PT API connection must be the same as the code page of the Teradata source. |
Max sessions | Maximum number of sessions that the Teradata PT API establishes with the Teradata database. Specify a positive, non-zero integer. Default is 4. |
Min sessions | Minimum number of Teradata PT API sessions required for the Teradata PT API job to continue. Specify a positive integer between 1 and the Max Sessions value. Default is 1. |
Sleep | Amount of time, in minutes, that the Teradata PT API pauses before it retries to log on when the maximum number of operations runs on the Teradata database. Specify a positive, non-zero integer. Default is 6. |
Data encryption | Enables full security encryption of SQL requests, responses, and data. Set this property to 1 to enable full security encryption or to 0 to disable full security encryption. |
Block size | Maximum block size, in bytes, that the Teradata PT API uses when it returns data to the Secure Agent. Minimum is 256. Maximum is 64,000. Default is 64,000. |
Authentication type | Method to authenticate the user. Select one of the following authentication types: - - Native. Authenticates your user name and password against the Teradata database specified in the connection.
- - LDAP. Authenticates user credentials against the external LDAP directory service.
- - KRB5. Authenticates to the Teradata database through Kerberos.
Default is Native. |
Kerberos artifacts directory | Directory that contains the Kerberos configuration files named krb5.conf and IICSTPT.keytab. Applicable when you select KRB5 as the authentication type. |
Metadata advanced connection properties | Optional JDBC driver properties for fetching the metadata. For example: tmode=ANSI. |
Enable metadata qualification | Enables the Teradata connection to read reserved words used as table or column names from the Teradata database. By default, this option is disabled, and the Secure Agent does not read reserved words from Teradata. |
User name | Database user name with the appropriate read and write database permissions to access the database. If you select KRB5 as the authentication type, you must specify the Kerberos user name. |
Password | Password for the database user name. If you select KRB5 as the authentication type, you do not need to specify the Kerberos user password. |
