Data Ingestion and Replication
- Data Ingestion and Replication
- All Products
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.
|
Description | Description of the connection. Maximum length is 4000 characters.
|
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not
supported by Data Ingestion and Replication and the Data Access Management services. When you enable the secret vault in the connection, you can select
which credentials that the Secure Agent retrieves from the secrets manager. If you
don't enable this option, the credentials are stored in the repository or on a local
Secure Agent, depending on how your organization is configured. If you’re using this connection
to apply data access policies through pushdown or proxy services, you cannot use
the Secret Vault configuration option. For information about how to configure and use a secrets manager, see
"Secrets manager configuration" in the Administrator help .
|
Runtime Environment | The name of the runtime environment where you want to run tasks. In Data Ingestion and Replication , you cannot run a streaming ingestion and replication task on a Hosted Agent,
serverless runtime environment, or elastic runtime
environment. |
JDBC Driver Class Name | Name of the JDBC driver class. For example, to connect to Aurora PostgreSQL, specify the
following driver class name: org.postgresql.Driver 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 example, the connection string for the Aurora PostgreSQL
database type is
jdbc:postgresql://<host>:<port>[/dbname] .For more information about the connection string to use with
specific drivers, see the corresponding third-party vendor
documentation. |
User Name | The user name to connect to the database. |
Password | The password to connect to the database. |
Property | Description |
|---|---|
Database Type | The database type to which you want to connect. Select one of
the following database types:
Default is Others. |
Schema Name | The schema name used for the JDBC object. 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. |
Connection Environment SQL | The SQL statement to set up the database environment when you
connect to a PostgreSQL database. The database environment applies
for the entire session that uses this connection. For example, you
can enter this statement to set the time zone: SET
timezone to 'America/New_York'; |
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. |
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 from the list based on
what delimiter the database uses for identifiers. When the
Secure Agent generates SQL queries, it encloses delimited
identifiers within this character. |