Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. System Backup and Restore
  13. Batch Utilities

Configuration Settings

Configuration Settings

You can specify the following settings in the
xrserv.xml
file.
mode
A required global parameter. Possible values are generic or custom. Generic indicates that all the synchronized IDTs in the specified rulebase must be made available to Real Time clients. Custom indicates that only the specified IDTs must be made available to Real Time clients.
txn_thread_num
An optional global parameter. Specifies the number of threads that you want to set to process the IDT updates.
work_queue_size
An optional global parameter. Specifies the size of the IDT or IDX transaction reader input queue. The default size is 5000.
txn_commit_rate
An optional global parameter. Select an appropriate commit rate by tuning. In general, a high commit rate provides better transaction throughput. However, too high a rate might cause the database to run out of rollback space in a multi-user update environment, and updated records might not be visible to searches for long periods. The default value is 1.
rulebase
Required. Specifies the rulebase to use for Real Time operations. Specify at the global level for the generic mode or at the rule level for the custom mode.
system
A required rule-level parameter. Specifies the Identity Resolution system containing the IDT to be processed.
idt
A required rule-level parameter. Specifies the name of the IDT to be processed. This IDT must be present in the specified Identity Resolution system.
disable_idt_mutex_locking
An optional rule-level parameter. Disables the IDT mutex lock and improves synchronization performance. The default value is false.
If you are using a persistent identifier (PID), do not change the default value of the
disable_idt_mutex_locking
parameter.
del_not_found_warn_only
Changes the behaviour to return only a warning when the IDT record cannot be found for a delete transaction.
soft_skip_delete_fail
Skips restarting the Synchronization Server when a record that you try to delete does not exist.
skip_error_and_continue
Skips any errors and continues to process other records.

0 COMMENTS

We’d like to hear from you!