This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Priority Synchronization
Priority Synchronization

Version management

Difference between version and

At line 1 added 35 lines
!!! Overview
[{$pagename}] was introduced in eDirectory 8.8 introduces a new synchronization method in addition to the method.
[{$pagename}] is used when you need to sync your critical data immediately and does wait for normal [EDirectory Synchronization].
Priority sync does not use, but is complimentary to the normal [EDirectory Synchronization] process in eDirectory.
Unlike [EDirectory Synchronization], in [{$pagename}], the changes are __NOT__ put in the [Change Cache] before synchronizing them across the [replicas]. This makes [{$pagename}] faster than normal [EDirectory Synchronization].
[{$pagename}] is enabled by default.
!! [{$pagename}] Configuration
To sync modifications to critical data through priority sync, the following steps are used:
* Specify the number of [NDS Threads] for [{$pagename}].
* Specify the [{$pagename}] queue size.
* Create and define a [{$pagename}] policy by identifying the critical [attributes] that you want to be in [{$pagename}].
* Apply the [{$pagename}] policy to one or more [partitions].
The [{$pagename}] process is designed to sync only the modifications to [attributes] that you designate as critical.
If you create a new object that has the critical attributes, the created object is not synchronized with other servers.
[{$pagename}] maintains the object transaction model. So, if noncritical data is modified and is not yet synchronized, and if the critical data is changed for the same entry, the noncritical data along with critical data is synchronized.
!! An Example
For example, a user has the following attributes: Income, Employee No, Address, and Cube No. You identify Income and Address as critical attributes. Employee No and Cube No are modified but these modifications are not yet synchronized.
When the modifications to Income and Address are synchronized through priority sync, Employee No and Cube No also get synchronized, as they are not identified as critical data.
!! Category
%%category [eDirectory]%%
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop