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
  • Data Engineering Integration 10.2.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Big Data Management Administration
  3. Authentication
  4. Running Mappings on a Cluster with Kerberos Authentication
  5. Authorization
  6. Cluster Configuration
  7. Cloud Provisioning Configuration
  8. Data Integration Service Processing
  9. Connections
  10. Multiple Blaze Instances on a Cluster
  11. Monitoring REST API

Big Data Management Administrator Guide

Big Data Management Administrator Guide

Back Next

JDBC Connection Properties

JDBC Connection Properties

You can use a JDBC connection to access tables in a database. You can create and manage a JDBC connection in the Administrator tool, the Developer tool, or the Analyst tool.
The order of the connection properties might vary depending on the tool where you view them.
The following table describes JDBC connection properties:
Property
Description
Database Type
The database type.
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
The description of the connection. The description cannot exceed 765 characters.
User Name
The database user name.
Password
The password for the database user name.
JDBC Driver Class Name
Name of the JDBC driver class.
The following list provides the driver class name that you can enter for the applicable database type:
  • DataDirect JDBC driver class name for Oracle: 
    com.informatica.jdbc.oracle.OracleDriver
  • DataDirect JDBC driver class name for IBM DB2: 
    com.informatica.jdbc.db2.DB2Driver
  • DataDirect JDBC driver class name for Microsoft SQL Server: 
    com.informatica.jdbc.sqlserver.SQLServerDriver
  • DataDirect JDBC driver class name for Sybase ASE: 
    com.informatica.jdbc.sybase.SybaseDriver
  • DataDirect JDBC driver class name for Informix: 
    com.informatica.jdbc.informix.InformixDriver
  • DataDirect JDBC driver class name for MySQL: 
    com.informatica.jdbc.mysql.MySQLDriver
For more information about which driver class to use with specific databases, see the vendor documentation.
Connection String
Connection string to connect to the database. Use the following connection string: 
jdbc:<subprotocol>:<subname>
The following list provides sample connection strings that you can enter for the applicable database type:
  • Connection string for DataDirect Oracle JDBC driver: 
    jdbc:informatica:oracle://<host>:<port>;SID=<value>
  • Connection string for Oracle JDBC driver: 
    jdbc:oracle:thin:@//<host>:<port>:<SID>
  • Connection string for DataDirect IBM DB2 JDBC driver: 
    jdbc:informatica:db2://<host>:<port>;DatabaseName=<value>
  • Connection string for IBM DB2 JDBC driver: 
    jdbc:db2://<host>:<port>/<database_name>
  • Connection string for DataDirect Microsoft SQL Server JDBC driver: 
    jdbc:informatica:sqlserver://<host>;DatabaseName=<value>
  • Connection string for Microsoft SQL Server JDBC driver: 
    jdbc:sqlserver://<host>;DatabaseName=<value>
  • Connection string for Netezza JDBC driver: 
    jdbc:netezza://<host>:<port>/<database_name>
  • Connection string for Pivotal Greenplum driver: 
    jdbc:pivotal:greenplum://<host>:<port>;/database_name=<value>
  • Connection string for Postgres Greenplum driver: 
    jdbc:postgressql://<host>:<port>/<database_name>
  • Connection string for Teradata JDBC driver: 
    jdbc:teradata://<host>/database_name=<value>,tmode=<value>,charset=<value>
For more information about the connection string to use with specific drivers, see the vendor documentation.
Environment SQL
Optional. Enter SQL commands to set the database environment when you connect to the database. The Data Integration Service executes the connection environment SQL each time it connects to the database.
If you enable Sqoop, Sqoop ignores this property.
Transaction SQL
Optional. Enter SQL commands to set the database environment when you connect to the database. The Data Integration Service executes the transaction environment SQL at the beginning of each transaction.
If you enable Sqoop, Sqoop ignores this property.
SQL Identifier Character
Type of character that the database uses to enclose delimited identifiers in SQL queries. The available characters depend on the database type.
Select (None) if the database uses regular identifiers. When the Data Integration Service generates SQL queries, the service does not place delimited characters around any identifiers.
Select a character if the database uses delimited identifiers. When the Data Integration Service generates SQL queries, the service encloses delimited identifiers within this character.
If you enable Sqoop, Sqoop ignores this property.
Support Mixed-case Identifiers
Enable if the database uses case-sensitive identifiers. When enabled, the Data Integration Service encloses all identifiers within the character selected for the
SQL Identifier Character
 property.
When the
SQL Identifier Character
 property is set to none, the
Support Mixed-case Identifiers
 property is disabled.
If you enable Sqoop, Sqoop honors this property when you generate and execute a DDL script to create or replace a target at run time. In all other scenarios, Sqoop ignores this property.
0 COMMENTS
We’d like to hear from you!