Specifying Delivery Rules for Database Activities

Specify how messages will be delivered at the Delivery Rules pane.

The delivery rules for inbound and outbound activities differ, as described in the following sections.

Specify the delivery rules for inbound database activities

  1. Select the Delivery Rules task from the Checklist.
  2. Configure the Delivery rules as described in the following table which describes the delivery rules for the inbound database activities (Get Inserted Rows, Get Updated Rows, Get Deleted Rows, and Poll Table):
    Table 1.
    Name Description
    Polling Interval   Specifies the time interval to poll for changes in database. For example, the Get Inserted Rows activity polls for INSERT trigger events at the specified time internal. For more information, see Polling interval behavior.
    Fetch size Specifies how many rows the activity should retrieve from the buffer table at one time. The default is 500 rows per poll. The range is 1 - 10,000.
    Note: To improve performance, set the Fetch Size to the maximum number of rows you expect to retrieve from the buffer table.
    Batch Specifies the number of rows to batch into a single message. By default, batching is turned off (the Batch check box is not selected). To turn on batching, select the Batch check box then specify the number of rows to batch. The range is 1 - 10,000. If the Batch check box is selected in Delivery Rules, then the multiple occurrences symbol displays next to the row element in the From Activity pane of the Map Outputs task of the inbound activity.
    Deliver Messages Select from one of the following options in the Deliver messages pull-down menu:
    • At least once - Specifies the message will be delivered at least once, but can be delivered more than once. This delivery option is typically used when the receiving system can detect or tolerate duplicate messages.
    • Exactly once - Specifies the message will be delivered once and only once.  If the Exactly once option is selected and the database is Sybase, the OverwriteCharLimits parameter must be set in the endpoint. For more information, see Oracle, Sybase, DB2, and Informix Parameters.
      Note: If you select the Exactly once option, you must create some control tables that are used by the Integration Appliance during run time. You create the control tables after publishing the orchestration from Studio to the Integration Appliance. You create the control tables using the Web Management Console (WMC) before you deploy the project.
      Note: If you select the Exactly Once option, you must enable persistence. For more information, see Enabling persistence.
    Delete rows after they have been processed This check box is displayed only for the Custom Poll activity. The Delete rows after they have been processed check box is used by the Integration Appliance to determine the action for a delete request while running a Poll Table activity:
    • If the check box is enabled, during run time the Integration Appliance sets the flag column to M and then deletes the row.
    • If the check box is cleared, during run time the Integration Appliance sets the flag column to M and then P but the row is not deleted.

Specify the delivery rules for outbound database activities

  1. Select the Delivery Rules task from the Checklist.
  2. Configure the Delivery rules as described in the following table, which describes the deliver rules for the outbound database activities (Insert Rows, Update Rows, Delete Rows, Call Procedure):
    Table 2.
    Name Description
    Deliver Messages Select from one of the following options in the Deliver messages menu:
    • At least once - Specifies the message will be delivered at least once, but can be delivered more than once. This delivery option is typically used when the receiving system can detect or tolerate duplicate messages.
    • Exactly once - Specifies the message will be delivered only once.
    Note: If you select the Exactly once option, you must create some control tables that are used by the Integration Appliance during run time. You create the control tables after publishing the orchestration from Studio to the Integration Appliance. You create the control tables using the Web Management Console (WMC) before you deploy the project.
    Batch __ rows at a time Specifies if the database operations on rows should be batched and how many rows to process by the database operation at one time. For example, if the size of the batch is set to 20 but 100 rows are processed by a database insert, 5 messages of size 20 are sent from the Integration Appliance to the database and then the final database commit message is sent.

    If the Batch __ rows at a time check box is selected in Delivery Rules, the multiple occurrences symbol displays next to the row element in the To Activity pane of the Map Inputs task of the outbound activity.

    Get Row Counts Not available for the Call Procedure activity - This check box specifies that during run time the activity returns how many rows were processed per transaction. If the Get Rows Counts check box is selected, the rowCount is available in the From Activity pane of the Map Outputs pane of the outbound activity.



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/db_specifying_delivery_rules_for_database_activities.html