Connection resilience is the ability of the Integration Service to tolerate temporary network failures when connecting to a relational database, an application, or the PowerExchange Listener. The Integration Service can also tolerate the temporary unavailability of the relational database, application, or PowerExchange Listener. The Integration Services is resilient to failures when it initializes the connection to the source or target and when it reads data from a source or writes data to a target.
You configure the resilience retry period in the connection object. You can configure the retry period for source, target, SQL transformation, and Lookup transformation connections. When a network failure occurs or the source or target becomes unavailable, the Integration Service attempts to reconnect for the amount of time configured for the
Connection Retry Period
property. If the Integration Service cannot reconnect to the source or target within the retry period, the session fails.
PowerExchange does not support runtime connection resilience for database connections other than those used for PowerExchange Express CDC for Oracle. Configure the workflow for automatic recovery of terminated tasks if recovery from a dropped PowerExchange connection is required. PowerExchange also does not support runtime resilience of connections between the Integration Service and PowerExchange Listener after the initial connection attempt. However, you can configure resilience for the initial connection attempt by setting the
Connection Retry Period
property to a value greater than 0 when you define PowerExchange Client for PowerCenter (PWXPC) relational and application connections. The Integration Service then retries the connection to the PowerExchange Listener after the initial connection attempt fails. If the Integration Service cannot connect to the PowerExchange Listener within the retry period, the session fails.
The Integration Service will
not
attempt to reconnect to a source or target in the following situations:
The database connection object is for an Informix connection.
The transformation associated with the connection object is not configured for deterministic and repeatable output.
The value for the DTM buffer size is less than what the session requires.
The truncate the target table option is enabled for a target and the connection fails during execution of the truncate query.
The database connection fails during a commit or rollback.
Use the retry period with the following connection types:
Relational database connections
FTP connections
JMS connections
WebSphere MQ queue connections
HTTP application connections
Web Services Consumer application connections
For a database connection to be resilient, the source or target must be a highly available database and you must have the high availability option or the real-time option.