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.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Data Engineering 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. Appendix A: Connections Reference
  10. Appendix B: Monitoring REST API

Data Engineering Administrator Guide

Data Engineering Administrator Guide

Back Next

JDBC V2 Connection Properties

JDBC V2 Connection Properties

When you set up a JDBC V2 connection, you must configure the connection properties.
The order of the connection properties might vary depending on the tool where you view them.
The following table describes the JDBC V2 connection properties:
Property
Description
Name
The name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. 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 4,000 characters.
Location
The domain where you want to create the connection.
Type
The connection type. Select JDBC V2.
The
Details
 tab contains the connection attributes of the JDBC V2 connection. The following table describes the connection attributes:
Property
Description
Username
The database user name.
User name with permissions to access the database that supports the Type 4 JDBC driver.
Password
The password for the database user name.
Schema Name
Optional. The schema name to connect in the database.
If you do not specify the schema name, all the schemas available in the database are listed.
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:
  • JDBC driver class name for Azure SQL Database: 
    com.microsoft.sqlserver.jdbc.SQLServerDriver
  • JDBC driver class name for Aurora PostgreSQL: 
    org.postgresql.Driver
  • JDBC driver class name for SAP HANA Database: 
    com.sap.db.jdbc.Driver
For more information about which driver class to use with specific databases, see the third-party 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 Azure SQL Database JDBC driver: 
    jdbc:sqlserver://<host>:<port>;database=<database_name>
  • Connection string for Aurora PostgreSQL JDBC driver: 
    jdbc:postgresql://<host>:<port>[/<database_name>]
  • Connection string for SAP HANA Database driver: 
    jdbc:sap://<host>:<port>/?databaseName=<Database_Name>
For more information about the connection string to use with specific drivers, see the third-party vendor documentation.
Sub Type
The database type to which you want to connect.
You can select from the following database types to connect:
  • Azure SQL Database
    . Connects to Azure SQL database.
  • PostgreSQL
    . Connects to Aurora PostgreSQL database.
  • SAP HANA Database
    . Connects to SAP HANA database.
  • Others
    . Connects to any database that supports the Type 4 JDBC driver.
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.
For example, Aurora PostgreSQL database supports mixed-cased characters. You must enable this property to connect to the Aurora PostgreSQL database.
When the
SQL Identifier Character
 property is set to none, the
Support Mixed-case Identifiers
 property is disabled.
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.
Select
SQL Identifier Character
 as
None
 when you specify the SAP HANA Database subtype.
0 COMMENTS
We’d like to hear from you!