cancel
Showing results for 
Search instead for 
Did you mean: 

Sync Configuration problem

g_rathod
Star Contributor
Star Contributor
Hi Friends,

I am using alfresco Enterprise 4.0
I have used alfresco chaining with openLdap and its running fine. The only issue is related to configuration.

#1) Regarding synchronization my file located at [ extension environment ] :

<alfresco4.0>\tomcat\shared\classes\alfresco\extension\subsystems\Synchronization\default\default-synchronization-context.xml

#2) And original location is :

<alfresco4.0>\tomcat\webapps\alfresco\WEB-INF\classes\alfresco\subsystems\Synchronization\default\default-synchronization-context.xml

Every other files works well on extension environment and my file deployed to shared extension perfectly. Since it will only consider to original path only instead path #1.

I have my custom class and bean entry in this file(default-synchronization-context.xml) everytime it calls path #2.
Any idea why extension file is not overridden ???

Thanks in advance.
3 REPLIES 3

mrogers
Star Contributor
Star Contributor
The extension path is wrong.   (there is a missing directory after default)  

I'm guessing (havn't looked it up) it should be the name of the authenticator you want to sync so you could do something like sync two different authenticators.

Its also unlikely that you need to faff with subsystem over-rides,  most stuff should be configured through alfresco-global.properties.

g_rathod
Star Contributor
Star Contributor
Thanks a lot  mrogers,

Actually I am not overridden any sync property from default-synchronization.properties but inside default-synchronization.xml I have changed one bean class that is my custom class.
And still I do not understand, generally we keep same folder structure as of WEB-INF/classes  but here why we need extra (default) ??
After adding it works, but could not understand structure.

mrogers
Star Contributor
Star Contributor
The subsystems have a folder pattern      subsystemName/type/name.

Its so that for example you could connect to two ldap servers with different properties.         Most subsystems don't need that so just have default/default.