LiveCycle’s User Manager component introduced the concept of delta directory synchronization in ES2. This means that instead of re-synchronizing the entire configured LDAP structure every day, only changes (delta) are downloaded. For this to work, support for this has to be configured on the corporate LDAP directory as well as in LiveCycle Admin UI (see below).
Here in our eTech Lab, we have a few servers configured for daily delta synching against Adobe’s Active Directory LDAP. It usually takes about 5-7 minutes for the domain synchronization. Since Content Services ES2 is deployed, it takes an additional 3-4 minutes for the additional synchronization that it requires. This example is for an Oracle WebLogic 10.3 appserver instance on an Oracle Enterprise M-series M3000 Solaris/SPARC server with a single (quad-core) 2.75 GHz SPARC64 VII CPU. The DB is an Oracle 11g instance.
The start log entry for domain synchronization will look something like this:
[com.adobe.idp.um.businesslogic.synch.SynchronizationManager] Directory synchronization started.
The end log entry for domain synchronization will look something like this:
[com.adobe.idp.um.businesslogic.synch.SynchronizationManager] Synch was completed successfully for the following domains...
[com.adobe.idp.um.businesslogic.synch.SynchronizationManager] Directory synchronization completed in ......
The start log entry for Content Services synchronization will look something like this:
[com.adobe.livecycle.contentservices.dsc.impl.DocumentManagementServiceImpl] ALC-CSV-001-000-Number of users updated:50
The end log entry for Content Services synchronization will look something like this:
[com.adobe.livecycle.contentservices.dsc.impl.DocumentManagementServiceImpl] ALC-CSV-001-000-Content Services User/Group Synchronization Finished