Table of Contents

Search

  1. Preface
  2. Introduction to TDM Administration
  3. User and Role Administration
  4. Security Administration
  5. System Preferences
  6. TDM Server Administration
  7. Connections
  8. Pass Phrases
  9. Global Parameters
  10. Dictionaries
  11. User-Defined Datatypes

JDBC Connections in a Hadoop Plan

JDBC Connections in a Hadoop Plan

You can create a JDBC connection to use as a source, target ,or dictionary in a Hadoop plan to perform data masking operations.
The following table describes the JDBC connection properties that you can configure:
Property
Description
Name
Required. Name of the connection. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters, start with a number, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
Connection Type
Required. The connection type. Select JDBC.
Description
The description of the connection. The description cannot exceed 255 characters.
User Name
Required. The database user name.
Password
Required. The password for the database user name.
Owner
The owner of the connection. Default is the user who creates the connection. You can change the owner of the connection.
Used for Hadoop
Configures the connection properties based on how you want to use the connection. To use the connection in a Hadoop plan, choose
Yes
.
Driver Name
Indicates the JDBC driver name to interact with the database.
Enter the appropriate driver name for the database:
  • DB2 for Linux, UNIX, and Windows:
    com.informatica.jdbc.db2.DB2Driver
  • MySQL:
    com.informatica.jdbc.sqlserver.SQLServerDriver
  • Oracle:
    com.informatica.jdbc.oracle.OracleDriver
  • Sybase:
    com.informatica.jdbc.sybase.SybaseDriver
JDBC String
Required. The JDBC connection URL used to access metadata from the database. Enter the appropriate connection string for the database:
  • DB2 for Linux, UNIX, and Windows:
    jdbc:informatica:db2://<hostname>:<port number>/<dbname>
  • MySQL:
    jdbc:informatic​a:sqlserver://<hostname>:<port number>;SelectMeth​od=cursor;<dbname>
  • Oracle:
    jdbc:informatica:oracle://<hostname>:<port number>/<dbname>
  • Sybase:
    jdbc:informatica:sybase://<hostname>:<port number>/<dbname>
Use Sqoop Connector
Select the version of Sqoop Connector that you want to use to connect to the database.
Sqoop Arguments
Enabled when you choose to use Sqoop Connector. Enter the appropriate Sqoop arguments that you want to use to connect to the database and process data:
  • DB2 for Linux, UNIX, and Windows:
    --connect jdbc:db2://<hostname>:<port number>/<dbname> --verbose
  • MySQL:
    --connect jdbc:sqlserver://<hostname>:<port number>/<dbname> --verbose
  • Oracle:
    --connect jdbc:oracle:thin:@<hostname>:<port number>/<dbname> --verbose
  • Sybase:
    --connect jdbc:sybase:Tds:<hostname>:<port number>/<dbname> --verbose
Environment SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the connection environment SQL each time it connects to the database.
Used for all operations.
Transaction SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the transaction environment SQL at the beginning of each transaction.
Used for all operations.
SQL Identifier Character To Use
Required. The type of character used to identify special characters and reserved SQL keywords, such as WHERE.
The Data Integration Service places the selected character around special characters and reserved SQL keywords. The Data Integration Service also uses this character for the Support Mixed-case Identifiers property.
Select one of the following characters based on the database in the connection:
  • Double quotes " "
  • Single quotes ' '
  • Back quotes ` `
  • Brackets [ ]
Used for data discovery operations.
Support Mixed Case Identifiers
When enabled, the Data Integration Service places identifier characters around table, view, schema, synonym, and column names when generating and executing an SQL against these objects in the connection.
Use if the objects have mixed-case or lowercase names. By default, this option is not selected.
Used for data discovery operations.