Operations Guide

10.5
- 10.5 HotFix 1
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

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.
retry_conn_delay: An optional global parameter. Specifies the time in seconds that the Synchronization Server waits to retry a connection to the database after the connection fails.
queue_poll_rate: Optional. Specifies the number of times the synchronization server should check the input queue in the txn worker thread before turning idle. Default is 10. CPU usage might be high even when no records are in the queue for the synchronization server to process. To optimize CPU usage in such scenarios, use the
queue_poll_rate
and
queue_poll_wait
parameters.
queue_poll_wait: Specifies the time in microseconds during which the synchronization server is idle before checking the input queue in the txn worker thread. Default is 20. CPU usage might be high even when no records are in the queue for the synchronization server to process. To optimize CPU usage in such scenarios, use the
queue_poll_rate
and
queue_poll_wait
parameters.

If the default values for the

queue_poll_rate

and

queue_poll_wait

parameters result in high CPU usage, then set

queue_poll_rate

and

queue_poll_wait

. You can also reduce the number of worker threads to reduce CPU usage. If the

queue_poll_wait

time is significantly high, the response to updates from web services or NSA is affected.

Rename Saved Search

Table of Contents

Operations Guide

Operations Guide

Configuration Settings

Configuration Settings