Failover mechanism for Active Directory connector

Question

It would be usefully if there is a failover mechanism for active directory connector. 
 Currently you can configure in Active Directory Synchronization project only one DC where the synchronizator conencts, but it can be that there is a connection failure for that specific DC and whole synchronization process fails. 
 It would be usefully if one could configure a pool of DCs for failover cases. 
 
 Is there plan for this kind behavior?

Markus Weiss-Ehlers · Accepted Answer

You could convert the CP_ADServer variable into a scripted variable in the sync project (for a FullSync my comments from above apply. No synchronization optimization allowed then). 
 In the script, you could determine a DC of your domain and do some other checks as well (ping, login, whatsoever). 
 The sample script is just taking the first domain controller it gets from the collection: Further enhancements would be to check the DC classes, ping time, etc. 
 References System.DirectoryServices.dll
Imports System.DirectoryServices.ActiveDirectory


 Dim RootDN as String = VariableSet.Item("CP_ADRootdn")

 Dim DomainName As String = RootDN.Replace(",dc=",".").Replace("dc=","")
 Dim DomainCon As New DirectoryContext(DirectoryContextType.Domain, DomainName)
 
 Dim DCs As DomainControllerCollection = Domain.GetDomain(DomainCon).DomainControllers
 
 Return DCs.Item(0).Name
 
 'For Each DC As DirectoryServices.ActiveDirectory.DomainController In DCs
 ' Return DC.Name
 'Next

Markus Weiss-Ehlers · Answer

I assume this script is the code inside of a scripted variable. Inside this script, you do not have a normal Object Layer connection (or session). A rough idea (haven't thought about all details yet) would be: 
 
 For a full-sync, you could add a custom process to start the synchronization for your AD sync. In that process, you execute (after some rewrite) your detection script as normal DialogScript in an additional process step before the synchronization process step. That script needs to return a string in the OutParameter then that can be used in the OverrideVariables parameter of the synchronization process step. Or - assuming that the script running in the process step and the variable set would identify the same DC as a new PRIMARY, you could just run the scripted variable without the RevisionStore part, and the script in the process step is mainly for the deletion of the revision store entries in case of a change of PRIMARY happened. 
 For ad-hoc projections (where close timing might be important) you do not need to remove the revision store entries. But as you should work with a scripted variable here, to avoid too many process changes, you need to figure out a way to make this script work together with the solution from 1.

Failover mechanism for Active Directory connector

Top Replies