Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.5.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Domains
  3. Managing Your Account
  4. Using Informatica Administrator
  5. Using the Domain View
  6. Domain Management
  7. Nodes
  8. High Availability
  9. Connections
  10. Connection Properties
  11. Schedules
  12. Domain Object Export and Import
  13. License Management
  14. Monitoring
  15. Log Management
  16. Domain Reports
  17. Node Diagnostics
  18. Understanding Globalization
  19. Appendix A: Code Pages
  20. Appendix B: Custom Roles
  21. Appendix C: Informatica Platform Connectivity
  22. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Back Next

Teradata Parallel Transporter Connection Properties

Teradata Parallel Transporter Connection Properties

Use a Teradata PT connection to access Teradata tables. The Teradata PT connection is a database type connection. You can create and manage a Teradata PT connection in the Administrator tool or the Developer tool.
The order of the connection properties might vary depending on the tool where you view them.
The following table describes Teradata PT connection properties:
Property
Description
Name
Name of the connection. The name is not case sensitive and must be unique within the domain. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description
Description of the connection. The description cannot exceed 765 characters.
Location
Domain where you want to create the connection.
Type
Connection type. Select Teradata PT.
User Name
Teradata database user name with the appropriate read and write permissions to access the database.
Password
Password for the Teradata database user name.
Driver Name
Name of the Teradata JDBC driver.
Connection String
Connection string used to access metadata from the database.
Use the following connection string:
jdbc:teradata://<hostname>/database=<database name>,tmode=ANSI,charset=UTF8
The following table describes the properties for data access:
Property
Description
TDPID
Name or IP address of the Teradata database machine.
Database Name
Teradata database name.
If you do not enter a database name, Teradata PT API uses the default login database name.
Data Code Page
Code page associated with the database.
When you run a mapping that writes data to a Teradata target, the code page of the Teradata PT connection must be the same as the code page of the Teradata target.
Default is UTF-8.
Tenacity
Number of hours that Teradata PT API continues trying to log on when the maximum number of operations run on the Teradata database.
Must be a positive, non-zero integer. Default is 4.
Max Sessions
Maximum number of sessions that Teradata PT API establishes with the Teradata database.
Must be 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.
Must be a positive integer between 1 and the
Max Sessions
 value. Default is 1.
Sleep
Number of minutes that Teradata PT API pauses before it retries to log on when the maximum number of operations run on the Teradata database.
Must be a positive, non-zero integer. Default is 6.
Use Metadata JDBC URL for TDCH
Indicates that the Teradata Connector for Hadoop (TDCH) must use the JDBC URL that you specified in the connection string under the metadata access properties.
Default is selected.
Clear this option to enter a different JDBC URL that TDCH must use when it runs the mapping.
TDCH JDBC Url
Enter the JDBC URL that TDCH must use when it runs a Teradata mapping. Use the following format:
jdbc:teradata://<hostname>/database=<database name>,tmode=ANSI,charset=UTF8
This field is available only when you clear the
Use Metadata JDBC URL for TDCH
 option.
Data Encryption
Enables full security encryption of SQL requests, responses, and data on Windows.
Default is disabled.
Additional Sqoop Arguments
This property is applicable if you use a Hortonworks or Cloudera cluster, and run a Teradata mapping on the Blaze or Spark engine through Sqoop.
Enter the arguments that Sqoop must use to process the data. For example, enter
--method split.by.amp
. Separate multiple arguments with a space.
See the Hortonworks for Teradata Connector and Cloudera Connector Powered by Teradata documentation for a list of arguments that you can specify.
If you use Hortonworks for Teradata Connector, the --split-by argument is required if you add two or more source tables in the read operation. If you use Cloudera Connector Powered by Teradata, the --split-by argument is required in the source connection if the source table does not have a primary key defined.
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.
Default is Native.
0 COMMENTS
We’d like to hear from you!