Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Secure Agent services
  3. API Microgateway Service
  4. CMI Streaming Agent
  5. Common Integration Components
  6. Connector Service
  7. Data Access Management Agent service
  8. Data Access Management Proxy service
  9. Database Ingestion service
  10. Data Integration Server
  11. Elastic Server
  12. File Integration Service
  13. GitRepoConnectApp
  14. IDMC Data Gateway Service
  15. Mass Ingestion (Files)
  16. Metadata Foundation Application
  17. Metadata Platform Service
  18. Process Server
  19. SecretManagerApp
  20. Configuring Secure Agent service properties

Secure Agent Services

Secure Agent Services

Database Ingestion service properties

Database Ingestion service properties

To change or optimize the behavior of the Database Ingestion service that your Secure Agent group uses, you can configure Database Ingestion agent configuration properties for your runtime environment.
To configure the properties, open a Secure Agent in your runtime environment and click
Edit
. Under
System Configuration Details
, select
Database Ingestion
as the service and
DBMI_AGENT_CONFIG
or
LOCAL_TASK_CONFIG
as the type.
The following table describes the Database Ingestion agent service properties for the
DBMI_AGENT_CONFIG
type:
Property
Description
maxTaskUnits
The maximum number of
application ingestion and replication
task units and
database ingestion and replication
task units that can run concurrently on an on-premises machine where the Secure Agent is running.
Task units are not related to the capacity and availability of your hardware or software. You can configure maxTaskUnits to precisely control CPU usage. Valid values are 1 to 2000000000 (2 billion).
To calculate a reasonable number of task units for your Secure Agent machine, Informatica recommends that you divide the number of cores by 3 or 4. For example, if you have an 8-core machine, you could set this property to 2. Then monitor CPU usage and adjust the property value as needed to tune performance.
During initial load processing, this property determines the number of tables that can be unloaded simultaneously. Remaining tables are queued and start unload processing when resources become available.
A single job can process many tables. The total number of tables that can be processed is limited only by available memory. On the average, 25 MB of RAM is required per table for an initial load task based on a 1 KB row size.
During incremental load processing, this property determines the number of
application ingestion and replication
and
database ingestion and replication
jobs that can run simultaneously.
Setting this property to a value greater than the number of cores on the Secure Agent machine can increase parallelism for task execution but also cause performance bottlenecks at task execution time.
serviceLogRetentionPeriod
The number of days to retain each internal Database Ingestion service log file after the last update is written to the file. When this retention period elapses, the log file is deleted. The default value is 7 days.
Service logs are retained on the Secure Agent host where they are created:
<infaagent>/apps/Database_Ingestion/logs
.
This property is applicable to both
Application Ingestion and Replication
and
Database Ingestion and Replication
.
taskLogRetentionPeriod
The number of days to retain each job log file after the last update is written to the file. When this retention period elapses, the log file is deleted. The default value is 7 days.
ociPath
For Oracle sources and targets, the path to the Oracle Call Interface (OCI) directory that contains the oci.dll or libcIntsh.so file. By default, Oracle uses $ORACLE_HOME/lib on Linux or %ORACLE_HOME%\bin on Windows. The OCI library is used by database ingestion CDC tasks to connect to Oracle.
For a DBMI agent that is running, this value is appended to the PATH environment variable value on Windows or to the LD_LIBRARY_PATH environment variable value on Linux. This property is not required if you already included the OCI path in the PATH or LD_LIBRARY_PATH environment variable.
This property is applicable only to
Database Ingestion and Replication
.
serviceUrl
The URL that the Database Ingestion service uses to connect to the
Informatica Intelligent Cloud Services
cloud.
This property is applicable to both
Application Ingestion and Replication
and
Database Ingestion and Replication
.
logLevel
The level of detail to include in the logs that the Database Ingestion service produces. Options are:
  • TRACE
  • DEBUG
  • INFO
  • WARN
  • ERROR
The default value is TRACE.
This property is applicable to both
Application Ingestion and Replication
and
Database Ingestion and Replication
.
taskExecutionHeapSize
The maximum heap size, in gigabytes, for the Task Execution service. This heap size is used for the single Java process that hosts all
application ingestion and replication
tasks and
database ingestion and replication
tasks that run in the common Container service. You might need to increase this value if you run a large number of tasks or process a large volume of data. Enter the property value followed by "g" for gigabytes. The default value is '8g'.
This property is applicable to both
Application Ingestion and Replication
and
Database Ingestion and Replication
.
useProxy
Set this property to true to enable the DBMI Agent to go through a proxy when connecting to or writing data to targets. The DBMI Agent then uses the proxy settings from the Secure Agent proxy configuration. By default, proxy settings are not used.
This property is applicable to both
Application Ingestion and Replication
and
Database Ingestion and Replication
.
intermediateStorageDirectory
For incremental load and combined initial and incremental load jobs, the local root directory under which intermediate files that contain data are stored when the
Enable Persistent Storage
option is selected in the associated task definitions.
This property is applicable only to
Database Ingestion and Replication
.
storageBackupDirectory
For incremental load and combined initial and incremental load jobs, the path to the directory that stores backup files when the
Enable Persistent Storage
option is selected in the associated task definitions.
This property is applicable only to
Database Ingestion and Replication
.
storageProperties
For incremental load and combined initial and incremental load jobs, a comma-separated list of key=value pairs that is used when the
Enable Persistent Storage
option is selected in the associated task definitions. Specify this property only at the direction of Informatica Global Customer Support.
This property is applicable only to
Database Ingestion and Replication
.
supportedLoadTypes
For
application ingestion and replication
jobs and
database ingestion and replication
jobs, the load types that the Database Ingestion agent service can process. You can enter one or more of the following values, separated by a comma (,):
  • INITIAL. Initial load jobs or the initial load phase of combined initial and incremental load jobs.
  • INCREMENTAL. Incremental load jobs or the incremental phase of combined initial and incremental load jobs, which write to your target.
  • INCREMENTAL_STAGING. CDC staging tasks of incremental load or combined load jobs.
Default is INITIAL,INCREMENTAL,INCREMENTAL_STAGING, which indicates all load types.
Notes:
  • If multiple Database Ingestion agent services are configured to support the same load types, the jobs use the agent with the most available task units.
  • If the Database Ingestion agent service where a combined load job is running does not support the initial load type, the initial load phase of the combined load job is directed to another agent in the Secure Agent group where the initial load type enabled.
The following table describes the Database Ingestion agent service properties for the
LOCAL_TASK_CONFIG
type:
Property
Description
taskExecutionHeapSize
The maximum heap size, in gigabytes, available for running a single task, such as the CDC Staging Task, in its own Java Virtual Memory (JVM). You might need to increase this size if the task processes a large volume of data. Enter the property value followed by "g" for gigabytes. The default value is '2g'.
taskStartTimeoutSeconds
The number of seconds that must elapse before an attempt to start a task in its own JVM times out. The default value is 120.

0 COMMENTS

We’d like to hear from you!