Maximum amount of memory, in bytes, that the Data Integration Service can allocate for each mapping run for a single profile request.

Default is 536,870,912.

Determines whether to enable and start each application after you deploy it to a Data Integration Service.

Enter one of the following options:

For example, logical data object LDO3 joins data from logical data objects LDO1 and LDO2. A developer creates a mapping that uses LDO3 as the input and includes the mapping in an application. You enable caching for LDO1, LDO2, and LDO3. If you enable nested logical data object caching, the Data Integration Service uses cache data for LDO1 and LDO2 when it refreshes the cache table for LDO3. If you do not enable nested logical data object caching, the Data Integration Service accesses the source resources for LDO1 and LDO2 when it refreshes the cache table for LDO3.

Default is false.

By default, if the parser encounters a data field that it cannot parse, the data is ignored. But the source string complex data schema can change. For example, a software update on the server might change the JSON or XML. This option allows you to capture the data for analysis.

Default is false.

Default is false.

Directory for index and data cache files for transformations. Default is

<home directory>/cache

.

Enter a list of directories separated by semicolons to increase performance during cache partitioning for Aggregator, Joiner, or Rank transformations.

You cannot use the following characters in the directory path:

* ? < > " | ,

Root directory accessible by the node. This is the root directory for other service directories. Default is

<Informatica installation directory>/tomcat/bin

. If you change the default value, verify that the directory exists.

You cannot use the following characters in the directory path:

* ? < > " | ,

Default is false.

The directory containing a collection of Hadoop JARS on the cluster from the RPM Install locations. The directory contains the minimum set of JARS required to process Informatica mappings in a Hadoop environment. Type

/<PowerCenterBigDataEditionInstallationDirectory>/Informatica/services/shared/hadoop/[Hadoop_distribution_name]

.

The PowerCenter Big Data Edition home directory on every data node created by the Hadoop RPM install. Type

/<PowerCenterBigDataEditionInstallationDirectory>/Informatica

.

Maximum number of deployed jobs that can run concurrently in the Hadoop environment. The Data Integration Service moves Hadoop jobs from the queue to the Hadoop job pool when enough resources are available. Default is 100.

Maximum number of parallel threads that process a single mapping pipeline stage.

When you set the value greater than one, the Data Integration Service enables partitioning for mappings and for mappings converted from profiles. The service dynamically scales the number of partitions for a mapping pipeline at run time. Increase the value based on the number of CPUs available on the nodes where mappings run.

In the Developer tool, developers can change the maximum parallelism value for each mapping. When maximum parallelism is set for both the Data Integration Service and the mapping, the Data Integration Service uses the minimum value when it runs the mapping.

Default is 1. Maximum is 64.

Maximum amount of memory, in bytes, that the Data Integration Service can allocate for running all requests concurrently when the service runs jobs in the Data Integration Service process. When the Data Integration Service runs jobs in separate local or remote processes, the service ignores this value. If you do not want to limit the amount of memory the Data Integration Service can allocate, set this property to 0.

If the value is greater than 0, the Data Integration Service uses the property to calculate the maximum total memory allowed for running all requests concurrently. The Data Integration Service calculates the maximum total memory as follows:

Maximum Memory Size + Maximum Heap Size + memory required for loading program components

Default is 0.

Maximum number of deployed jobs that can run concurrently in the native environment. The Data Integration Service moves native mapping jobs from the queue to the native job pool when enough resources are available. Default is 10.

Maximum number of on-demand jobs that can run concurrently. Jobs include data previews, profiling jobs, REST and SQL queries, web service requests, and mappings run from the Developer tool. All jobs that the Data Integration Service receives contribute to the on-demand pool size. The Data Integration Service immediately runs on-demand jobs if enough resources are available. Otherwise, the Data Integration Service rejects the job. Default is 10.

Runs jobs in the Data Integration Service process, in separate DTM processes on the local node, or in separate DTM processes on remote nodes. Configure the property based on whether the Data Integration Service runs on a single node or a grid and based on the types of jobs that the service runs.

Enter one of the following options:

Default is OUT_OF_PROCESS.

Directory for reject files. Reject files contain rows that were rejected when running a mapping. Default is

<home directory>/reject

.

You cannot use the following characters in the directory path:

* ? < > " | ,

Directory for source flat files used in a mapping. Default is

<home directory>/source

.

If the Data Integration Service runs on a grid, you can use a shared directory to create one directory for source files. If you configure a different directory for each node with the compute role, ensure that the source files are consistent among all source directories.

You cannot use the following characters in the directory path:

* ? < > " | ,

Default directory for target flat files used in a mapping. Default is

<home directory>/target

.

Enter a list of directories separated by semicolons to increase performance when multiple partitions write to the flat file target.

If the Data Integration Service runs on a grid, you can use a shared directory to create one directory for target files. If you configure a different directory for each node with the compute role, ensure that the target files are consistent among all target directories.

You cannot use the following characters in the directory path:

* ? < > " | ,

Directory for temporary files created when jobs are run. Default is

<home directory>/disTemp

.

Enter a list of directories separated by semicolons to optimize performance during profile operations and during cache partitioning for Sorter transformations.

You cannot use the following characters in the directory path:

* ? < > " | , [ ]

If you configure this property, the Data Integration Service accepts requests from host names that match the allowed host name pattern. If you do not configure this property, the Data Integration Service uses the Denied Host Names property to determine which clients can send requests.

If you configure this property, the Data Integration Service accepts requests from IP addresses that match the allowed address pattern. If you do not configure this property, the Data Integration Service uses the Denied IP Addresses property to determine which clients can send requests.

If you configure this property, the Data Integration Service accepts requests from host names that do not match the denied host name pattern. If you do not configure this property, the Data Integration Service uses the Allowed Host Names property to determine which clients can send requests.

If you configure this property, the Data Integration Service accepts requests from IP addresses that do not match the denied IP address pattern. If you do not configure this property, the Data Integration Service uses the Allowed IP Addresses property to determine which clients can send requests.

When you set the HTTP protocol type to HTTPS or Both, you enable Transport Layer Security (TLS) for the service.

You can also enable TLS for each web service deployed to an application. When you enable HTTPS for the Data Integration Service and enable TLS for the web service, the web service uses an HTTPS URL. When you enable HTTPS for the Data Integration Service and do not enable TLS for the web service, the web service can use an HTTP URL or an HTTPS URL. If you enable TLS for a web service and do not enable HTTPS for the Data Integration Service, the web service does not start.

Default is HTTP.

Default is 8080.

The behavior of Maximum Memory Per Request depends on the following Data Integration Service configurations:

The service runs jobs in separate local or remote processes, or the service property Maximum Memory Size is 0 (default).
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to all transformations that use auto cache mode in a single request. The service allocates memory separately to transformations that have a specific cache size. The total memory used by the request can exceed the value of Maximum Memory Per Request.
The service runs jobs in the Data Integration Service process, and the service property Maximum Memory Size is greater than 0.
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to a single request. The total memory used by the request cannot exceed the value of Maximum Memory Per Request.

Default is 536,870,912.

Number of milliseconds that the DTM process stays open after it completes the last request. Identical SQL queries can reuse the open process.

Use the keepalive time to increase performance when the time required to process the SQL query is small compared to the initialization time for the DTM process. If the query fails, the DTM process terminates. Must be greater than or equal to 0. 0 means that the Data Integration Service does not keep the DTM process in memory. Default is 0.

You can also set this property for each SQL data service that is deployed to the Data Integration Service. If you set this property for a deployed SQL data service, the value for the deployed SQL data service overrides the value you set for the Data Integration Service.

The behavior of Maximum Memory Per Request depends on the following Data Integration Service configurations:

The service runs jobs in separate local or remote processes, or the service property Maximum Memory Size is 0 (default).
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to all transformations that use auto cache mode in a single request. The service allocates memory separately to transformations that have a specific cache size. The total memory used by the request can exceed the value of Maximum Memory Per Request.
The service runs jobs in the Data Integration Service process, and the service property Maximum Memory Size is greater than 0.
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to a single request. The total memory used by the request cannot exceed the value of Maximum Memory Per Request.

Default is 50,000,000.

The maximum number of threads that the Data Integration Service can use to run parallel tasks between a pair of inclusive gateways in a workflow. The default value is 10.

If the number of tasks between the inclusive gateways is greater than the maximum value, the Data Integration Service runs the tasks in batches that the value specifies. For example, if the Maximum Worker Threads value is 10, the Data Integration Service runs the tasks in batches of ten.

Number of milliseconds that the DTM process stays open after it completes the last request. Web service requests that are issued against the same operation can reuse the open process.

Use the keepalive time to increase performance when the time required to process the request is small compared to the initialization time for the DTM process. If the request fails, the DTM process terminates. Must be greater than or equal to 0. 0 means that the Data Integration Service does not keep the DTM process in memory. Default is 5000.

You can also set this property for each web service that is deployed to the Data Integration Service. If you set this property for a deployed web service, the value for the deployed web service overrides the value you set for the Data Integration Service.

The behavior of Maximum Memory Per Request depends on the following Data Integration Service configurations:

The service runs jobs in separate local or remote processes, or the service property Maximum Memory Size is 0 (default).
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to all transformations that use auto cache mode in a single request. The service allocates memory separately to transformations that have a specific cache size. The total memory used by the request can exceed the value of Maximum Memory Per Request.
The service runs jobs in the Data Integration Service process, and the service property Maximum Memory Size is greater than 0.
In this case, Maximum Memory Per Request is the maximum amount of memory, in bytes, that the Data Integration Service can allocate to a single request. The total memory used by the request cannot exceed the value of Maximum Memory Per Request.

Default is 50,000,000.

Prefix for the WSDL URL if you use an external HTTP load balancer. For example,

http://loadbalancer:8080

The Data Integration Service requires an external HTTP load balancer to run a web service on a grid. If you run the Data Integration Service on a single node, you do not need to specify the logical URL.