Performance Tuning Guide

10.4.0
- 10.5.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Informatica Managed FIle Transfer Configuration Tuning

To improve performance, the following table describes the B2B Data Exchange property settings to be tuned:

Properties	Settings
dx.infamft.httpclient.maxConnPerRoute	Define the maximum number of HTTP requests to Informatica Managed File Transfer for the same project. For example, if Informatica Managed File Transfer is concurrently running five jobs from B2B Data Exchange for the same project, then the setting should be greater than five.
dx.infamft.httpclient.maxconnectionTotal	Define the maximum number of total HTTP requests to Informatica Managed File Transfer. The value should equal or exceed the total number of concurrent jobs launched from B2B Data Exchange that will run in Informatica Managed File Transfer.
dx.queue.pool.outbound.threads.max	The setting should have a higher value than the value for the property dx.infamft.httpclient.maxConnTotal .
dx.queue.pool.inbound.threads.max	Maximum number of Receive Jobs to trigger at a time.

The following connection and project timeout tuning is suggested:

Increase project timeout in B2B Data Exchange system properties.

Increase number of retry attempts for Informatica Managed File Transfer resource.

Zlib compression is preferred for the SFTP resource, if the remote server supports this compression option.

Increase the number of retry attempts for Informatica Managed File Transfer resources.

Increase the client timeouts for remote servers and server timeouts for Informatica Managed File Transfer resources.

The Admin Server configuration in Tomcat for Informatica Managed File Transfer should be tuned to increase the maximum number of threads and the connection timeout for Informatica Managed File Transfer.

For Informatica Managed File Transfer, the following database tuning is suggested:

Increase the maximum database connection to at least 200.

Increase the maximum idle connection to the maximum to at least 30 seconds.

Increase the maximum wait time to at least 10,000 msec.

Software Configuration

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal