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.

An optional global parameter. Specifies the number of threads that you want to set to process the IDT updates.

An optional global parameter. Specifies the number of threads that you want to set to process the persistent ID updates.

An optional global parameter. Specifies the size of the IDT or IDX transaction reader input queue. The default size is 5000.

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.

Optional parameter. Controls the amount of audit information to return. Specify this parameter at the global level or at the rule level. If specified at the rule level, the settings apply to the IDT to which the rule applies. For more information about auditing, see

Informatica MDM Registry Edition Design Guide

.

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.

A required rule-level parameter. Specifies the name of the IDT to be processed. This IDT must be present in the specified MDM Registry Edition system.

This is a Forced link and unlink rule parameter and is optional. By default, the

local_flul_cache

value is set to true and the Real-Time Synchronization server uses the local Forced Link/Unlink cache. If it needs to use the common Forced Link/Unlink cache in search server then the

local_flul_cache

flag should be set to false.

An optional rule-level parameter. The default value is false. If you set the value to true, the Notification Service is notified whenever the IDT is updated. The users who subscribed to the Notification Service for the rule receive notification messages about the updates.

Changes the behaviour to return only a warning when the IDT record cannot be found for a delete transaction.