Specifying the Retry options for Force.com Bulk API activities

Specifying the Retry parameters is one of the tasks to configure an Force.com Bulk API activity.

About this task

Use this task to configure the retry options for configuring Force.com Bulk API activities. The Force.com Bulk API connector uses a single login session for all connections to a Force.com Bulk API endpoint. If a session expires, the connector automatically establishes a new session. The connector does not count the initial attempt to reacquiring the session as a retry attempt. The connector assumes the typical connector retry behavior after the initial attempt to reacquire a session fails.

Procedure

  1. Select the Retry task from the Checklist. The retry pane is displayed.
  2. Configure the retry and timeout options for connecting to an Force.com Bulk API instance, as described in the following table:
    Table 1. Retry options
    Retry Fields Description
    Wait __ second(s) between each retry. Specifies the number of seconds that the Integration Appliance waits before trying to establish a connection to the Force.com Bulk API instance.
    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 Force.com Bulk API instance before issuing an error and stopping the processing of the current orchestration job.
    Note: If you deploy an orchestration that contains the Force.com Bulk API activity and the Integration Appliance cannot connect to the specified Force.com Bulk API instance, 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 stops processing the current orchestration job. For example, you set the retry count to 3, the first, second, and third connection errors appear in the system log as warnings. The Integration Appliance logs the fourth connection error as an error and stops processing the current orchestration job.
    Activity Timeout
    Timeout after ____ second(s) when the endpoint does not respond to a request. Specifies the number of seconds the Integration Appliance waits before timing out, when the endpoint does not respond to a request. The default is 300 seconds.



Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


https://www.ibm.com/support/knowledgecenter/en/SS3LC4_7.5.3/com.ibm.wci.doc/BulkAPI_Specifying_Retry_Parameters_for_BulkAPI_Activities.html