1. Remote and Replication Manager Administration Guide
  2. Setting Preferences for Update Notifications, Visibility Rules, and Routing Rules

Setting Preferences for Update Notifications, Visibility Rules, and Routing Rules

This task is a step in Process of Completing the Remote System Preferences Form.

To set preferences for update notifications, visibility rules, and routing rules

  1. Navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences view.

  2. In the Merger Friendly Notification field of the Remote System Preferences form, specify how Siebel Remote writes information about database updates to the Siebel Remote Status view on the remote client. Use a value from the following table.

    Value Description

    Conflicts

    Siebel Remote writes information about database updates that caused conflicts.

    FALSE

    Siebel Remote does not write information about database updates.

    TRUE

    Siebel Remote writes information about database updates.

  3. In the Merger Transactions per Commit field, specify how many database transactions the Transaction Merger server component processes before it sends a database commit:

    • You can set a low value, such as 1, to reduce how often the user encounters a locked database row, and to reduce the risk of deadlock.

    • You can set a high value, such as 10, to minimize processing overhead.

    For default values and recommended settings for various databases, see Values for System Preferences.

  4. Specify how to handle visibility and routing rules:

    1. In the Visibility Rules per Statement field, specify the number of visibility or routing rules that the Transaction Router server component for each SQL statement examines.

    2. In the Visibility Rules per Statement 1 field, specify the number of visibility or routing rules according to the following items:

      • Examine each SQL statement that the Database Extract server component processes.

      • Examine only the first SQL statement that includes header information.

      • In the Visibility Rules per Statement N field, specify the number of visibility or routing rules that Siebel Remote examines for each SQL statement that the Database Extract server component processes for other SQL statements.

    Do not modify these values without assistance. For help with visibility and routing rules, see Getting Help from Oracle.

    For more information, see Controlling the Data That Siebel Remote Routes to Clients and Values for System Preferences.