Specifying Retry and Delivery Options for Siebel Activities

Specifying the Retry and Delivery parameters is one of the tasks to configure a Siebel activity configuration.

About this task

This section contains the procedure for configuring the retry options for Siebel outbound and inbound activities.

Procedure

  1. Select the Retry task from the Checklist. The retry pane is displayed.
  2. Configure the retry options for connecting to a Siebel server as described in the following table.
    Table 1. Retry options
    Retry Fields Description
    Wait __ seconds between each retry. Specifies the number of seconds that the Integration Appliance waits before trying to establish a connection to the Siebel server.
    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 Siebel server before issuing an error and stopping the processing of the current orchestration job.
    Note: If you deploy an orchestration that contains the inbound or outbound Siebel activity and the Integration Appliance cannot connect to the specified Siebel server, 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.

Specifying the delivery rules options for Siebel inbound activities

About this task

This section contains the procedure for configuring the delivery rule options for Siebel inbound activities.

Procedure

  1. Select the Delivery Rules task from the Checklist. The delivery rules pane is displayed.
  2. Configure the delivery rules options to select the activity's behavior as described in the following table.
    Table 2. Delivery rules
    Delivery Rules Fields Description
    Poll for changes every ______ days/hours/minutes/seconds Specifies the time interval to poll for objects in the Siebel server. (For example, the Get created object activity polls for create objects at the specified time internal.) Time can be selected in the format days, hours, minutes, or seconds.
    Fetch ______ rows per poll Specifies how many objects or components the activity should retrieve from the Siebel server in each poll cycle.
    Delivery Messages
    ATMOST_ONCE A non-persistent mode in which a Siebel business object or business component is either delivered once or not delivered at all.
    ATLEAST_ONCE A persistent mode, in which the Siebel business objects or business components are not lost. As a result, there are chances that the orchestration can receive events once or more than once.



Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Siebel_Specifying_Retry_Parameters_for_Siebel_Activities.html