Retry Options For Outbound Database Activities

This section contains the procedure for configuring the retry options for the following outbound database activities: Execute Query activity, Insert Rows activity, Update Rows activity, Delete Rows activity, and Call Procedure activity

Specify the retry options for outbound database activities

  1. Select the Retry task from the Checklist. The Retry pane is displayed.
  2. Configure the retry options for connecting to a database. The following table describes the retry options for connecting to a database:
    Table 1.
    Field Description
    Retry  
    1) Wait ___ second(s) between each retry. Specifies the amount of time (in seconds) that the Integration Appliance waits before trying to establish a connection to the database.
    2) Try to connect ___ times before failing. Specifies the retry count - the maximum number of times the Integration Appliance attempts to establish a connection to the database before issuing an error and stopping the processing of the current orchestration job.

    If you deploy an orchestration that contains the outbound database activity and the Integration Appliance cannot connect to the specified database, the Integration Appliance logs the connections errors as Warnings in the system and orchestration logs until the retry count value is reached. When the retry count is reached, the Integration Appliance logs an Error in the system and orchestration logs and the stops processing the current orchestration job.

    For example, the retry count is set to 3. The first, second, and third connection errors are shown in the system log as Warnings. The Integration Appliance logs the fourth connection error as an Error and stops processing the current orchestration job.
    Note: For the Database Execute Query activity, if you set this parameter to zero, the Integration Appliance retries the connection indefinitely.
    Activity Timeout    
    3) Time out after ___ seconds when the Endpoint does not respond to a request. Specifies the amount of time in seconds before a timeout occurs between the activity making a request on an Endpoint and the time it takes the Endpoint to respond. For example, the amount of time that the Integration Appliance waits for a response from the database after requesting an Insert, before the Integration Appliance issues a timeout error. An activity timeout is different from a connection timeout because an activity timeout occurs after the connection to the Endpoint has been established. A connection timeout specifies the amount of time in seconds before a timeout occurs between the Integration Appliance attempting to establish a connection to the Endpoint and the time it takes for the Endpoint to respond to the connection request. Set the connection timeout in the Database Endpoint tab. For more information about connection timeouts, see Creating or Editing a Database Activity Endpoint.