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
  • INFACore
  • All Products

Table of Contents

Search

  1. Preface
  2. Connections to source and target endpoints

Connections for INFACore

Connections for INFACore

Back Next

JDBC

JDBC

Create a JDBC connection to connect to databases that support the JDBC Type 4 driver.

Feature snapshot

Operation
Support
Read
Yes
Write
Yes

Connection properties

Configure the connection properties to connect to databases compliant with the JDBC Type 4 driver.
Before you configure the connection properties, you'll need to get information from the database that you want to connect to.
The following table describes the JDBC connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
User Name
The user name to connect to the database.
Password
The password for the database user name.
Schema Name
Optional. The schema name.
If you don't specify the schema name, all the schemas available in the database are listed.
To read from
or write to
 Oracle public synonyms, enter PUBLIC.
JDBC Driver Class Name
Name of the JDBC driver class.
For more information about which driver class to use with specific databases, see the corresponding third-party vendor documentation.
Connection String
Connection string to connect to the database.
Use the following format to specify the connection string:
jdbc:<subprotocol>:<subname>
For more information about the connection string to use with specific drivers, see the corresponding third-party vendor documentation.
Additional Security Properties
Masks sensitive and confidential data of the connection string that you don't want to display in the session log.
Specify the part of the connection string that you want to mask.
When you create a connection, the string you enter in this field appends to the string that you specified in the
Connection String
 field.
Database Type
The database type to which you want to connect to that supports the Type 4 JDBC driver
Select the
Others
 option to connect to an Oracle database.
PostgreSQL and Azure SQL Database options are not applicable.
Enable Auto Commit
Specifies whether the driver supports connections to automatically commit data to the database when you run an SQL statement.
When disabled, the driver does not support connections to automatically commit data even if the auto-commit mode is enabled in the JDBC driver.
Default is disabled.
Support Mixed-Case Identifiers
Indicates whether the database supports case-sensitive identifiers.
When enabled, the Secure Agent encloses all identifiers within the character selected for the SQL Identifier Character property.
Default 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 Secure Agent generates SQL queries, it does not place delimited characters around any identifiers.
Select a character if the database uses delimited identifiers. When the Secure Agent generates SQL queries, it encloses delimited identifiers within this character.

Read properties

The following table describes the advanced source properties that you can configure in the Python code for the read operation:
Advanced Source Property
Description
Pre SQL
The SQL query that the Secure Agent runs before reading data from the source.
Post SQL
The SQL query that the Secure Agent runs after reading data from the source.
Fetch Size
The number of rows that the Secure Agent fetches from the database in a single call.
Table Name
Overrides the table name used in the metadata import with the table name that you specify.
Schema Name
Overrides the schema name of the source object.
If you specify the schema name both in the connection and the source properties, the Secure Agent uses the schema name specified in the source properties.
SQL Override
The SQL statement to override the default query and the object name that is used to read data from the JDBC V2 source.

Write properties

The following table describes the advanced target properties that you can configure in the Python code for the write operation:
Advanced Target Property
Description
Pre SQL
The SQL statement to run before writing data to the target.
Post SQL
The SQL statement to run after writing data to the target.
Truncate Target
Truncates the target table before inserting records to the target.
Reject Truncated/Overflow Rows
Writes truncated and overflow data to the reject file. If you select Reject Truncated/Overflow Rows, the Data Integration Service sends all truncated rows and any overflow rows to the reject file.
Table Name
Overrides the table name used in the metadata import with the table name that you specify.
Schema Name
Overrides the schema name of the target object.
If you specify the schema name both in the connection and the target properties, the Secure Agent considers the schema name specified in the target properties.
Update Mode
Determines the mode how the Secure Agent writes data to the target.
Select one of the following modes:
  • Update As Update. Updates all rows flagged for update if the entries exist.
  • Update Else Insert. Updates all rows flagged for update if the entries exist in the target. If the entries do not exist, the agent then inserts the entries.
0 COMMENTS
We’d like to hear from you!