Optional. Enables pass-through security for the connection. When you enable pass-through security for a connection, the domain uses the client user name and password to log into the corresponding database, instead of the credentials defined in the connection object.

JDBC connection URL used to access metadata from the database.

jdbc:informatica:oracle://<host_name>:<port>;SID=<database name>

To connect to a secure database, include the following parameters:

EncryptionMethod. Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to SSL.
ValidateServerCertificate. Optional. Indicates whether Informatica validates the certificate that is sent by the database server.
If this parameter is set to true, Informatica validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
If this parameter is set to false, Informatica does not validate the certificate that is sent by the database server. Informatica ignores any truststore information that you specify.
HostNameInCertificate. Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
TrustStore. Required. Path and file name of the truststore file that contains the SSL certificate for the database.
TrustStorePassword. Required. Password for the truststore file for the secure database.
KeyStore. Required. Path and file name of the keystore file.
KeyStorePassword. Password for the keystore file for the secure database.

Informatica appends the secure JDBC parameters to the connection string. If you include the secure JDBC parameters directly to the connection string, do not enter any parameters in the AdvancedJDBCSecurityOptions field.

Connection string used to access data from the database.

Enter the connection string in the following format from the TNSNAMES entry:

Required. Code page used to read from a source database or write to a target database or file.

Optional. 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.

For example,

ALTER SESSION SET CURRENT_SCHEMA=INFA_USR;

Optional. SQL commands to execute before each transaction. The Data Integration Service executes the transaction SQL at the beginning of each transaction.

For example,

SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;

Optional. Enables parallel processing when loading data into a table in bulk mode. Used for Oracle. True or false. Default is false.

Optional. The character that you will use for quotes in this connection.

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 QuoteChar property. Default is 0.

Optional. Choose to enable quotes or not for this connection.

When enabled, the Data Integration Service places identifier characters around table, view, schema, synonym, and column names when generating and executing SQL against these objects in the connection. Use if the objects have mixed-case or lowercase names. Valid values are True or False. Default is True.

Optional. Enables connection pooling. When you enable connection pooling, the connection pool retains idle connection instances in memory. When you disable connection pooling, the Data Integration Service stops all pooling activity. Valid values are True or False. Default is True.

Optional. Maximum number of idle connections instances that the Data Integration Service maintains for a database connection. Set this value to be more than the minimum number of idle connection instances. Default is 15.

Optional. Number of seconds that a connection exceeding the minimum number of connection instances can remain idle before the connection pool drops it. The connection pool ignores the idletime when it does not exceed the minimum number of idle connection instances. Default is 120.

Optional. Minimum number of idle connection instances that the pool maintains for a database connection. Set this value to be equal to or less than the idle connection pool size. Default is 0.