<- [[:forum:alfresco]] ====== Basic Configuration ====== Result of the basic configuration will be an Alfresco system with following features: * User management injected from an Active Directory * Single sign on with InternetExplorer * Direct edit of of documents by clicking the ''Edit'' button. ===== Prelaminaries ===== This basic configuration starts with a fresh system installed like in [[forum:alfresco:installation]]. Most settings and configurations can be managed outside of the ''alfresco.war'' deployment. Others must be done within that folder. This of course results in a complex update procedure because instead of simply replace the ''alfresco.war'' by a new version you have to redo all these steps inside the ''alfresco.war'' folder to continue with the same environment as prior the update. So all changings done inside the deployment folder are maked with :!: The extension folder for custom extension files is\\ ''JBOSS_HOME/server/default/conf/alfresco/extension'' ((refer [[forum:alfresco:installation]])).\\ This folder is called '''' in our Wiki. Default configuration files are located in\\ ''JBOSS_HOME/server/default/deploy/alfresco.war/WEB-INF'' and\\ ''JBOSS_HOME/server/default/deploy/alfresco.war/WEB-INF/classes/alfresco''\\ The last one is called ''default'' in our Wiki. If you want to overwrite existing settings in your custom configuration you have to add the ''replace="true"'' attribute in the '''' tag. ===== Repository Properties ===== - Copy ''/repository.properties'' to\\ ''/custom-repository.properties'' - Copy ''custom-repository-context.xml.sample'' from the ''extensions'' folder inide the\\ ''alfresco-community-war-2.9.0B'' to ''/custom-repository-context.xml''. - Comment the Hibernate part inside the ''/custom-repository-context.xml''. Otherwise the Spring Framework will not start. - Set ''root.dir'' to /usr/share/alfresco/.alf_data. ((Of course another folder in the filesystem is possible...)) - :!: In ''JBOSS_HOME/server/default/deploy/alfresco.war/WEB-INF/classes/''\\ ''log4j.properties'' edit the ''File appender'' definition for ''alfresco.log'' and ''hibernate.log'' to ''/var/log''. ===== Edit Link Type ===== Per default editing of a document is a complex procedure. First you have to checkout the document inside the database. Then you can download the working copy to your local machine. Finally you open the local copy in the relevant application. To update the original you have to upload and thereafter checkin the document. Each of these steps is implemented with a couple of JSF pages. That means you need a lot of clicks and steps just to open and edit a document. Alfresco offers three options to handle an edit command. * the default way is HTTP download to local machine (as described above) * WebDAV - a browser with WebDAV functionality can serve the files like a local file system. * CIFS - the edit button links to a CIFS URL. This option enables direct editing of documents without pull/push. This is the preferred way here. - Copy ''web-client-config.xml'' to ''web-client-config-custom.xml''\\ - Set in the ''web-client-config-custom.xml'' the ''edit-link-type'' setting to ''CIFS''.\\ ===== Setup CIFS Server ===== One of Alfrescos greatest benefits is the built-in CIFS server. So you can interact with the Alfresco repository with standard filesystem methods. ==== References ==== * [[http://wiki.alfresco.com/wiki/CIFS_Server_Authentication|CIFS Server Authentication]] * [[http://wiki.alfresco.com/wiki/File_Server_Configuration|File Server Configuration]] ==== Setup ==== - Copy ''file-servers.xml'' to ''file-servers-custom.xml''\\ - In ''file-servers-custom.xml'' remove all config blocks exept * CIFS Server * Filesystems * Filesystem Security - Set the ''replace="true"'' attribut in these config tags - Set hostname, filesystem name, webpath and authenticator type=Alfresco - Activate the desktopActions ===== Automatic OOo service start ===== In the default configuration the OOo service for document transformation is started separately in a shell script. The idea is of course to handle this service by Alfresco itself during the bootstrap routine. ==== References ==== ==== Setup ==== DOESN'T WORK!!! FIXME - Copy ''openoffice-startup-context.xml'' from the\\ ''/usr/share/alfresco/install-extensions'' folder to ''/bootstrap'' - Correct paths, remove quotings in ''openoffice-startup-context.xml'' ===== Email Sending ===== - If neccessary for authentication create a account on the SMTP server. - Setup email properties in ''/custom-repository.properties'' - Setup ''from-email-address'' in ''/web-client-config-custom.xml'' - If you encounter problems when connecting to the smtp server check this bug [[https://issues.alfresco.com/jira/browse/ETHREEOH-559|ETHREEOH-559]] ===== Email Receiving ===== ==== References ==== * [[http://wiki.alfresco.com/wiki/Email_Server_Configuration]] ==== Setup ==== - Copy ''/emailserver/email-server.properties'' to\\ ''/custom-email-server.properties'' - Copy ''/emailserver/email-server-context.xml'' to\\ ''custom-email-server-context.xml'' - Add custom properties file in the location setting of ''custom-email-server-context.xml'' - Edit domain, port, allowed senders and enable in the properties file - Set aliases and aspects on some spaces ==== TODO ==== FIXME * Receive mails with all metadata fields (From, To, CC, Subject, etc.) * Enable Assoziations between Emails and their attachments. * Enable ''Answer'', ''Anser all'', ''Forward'' actions on Email documents ===== Setup Authentication ===== ==== References ==== * [[http://217.174.252.22/viewtopic.php?f=9&t=7750&st=0&sk=t&sd=a&start=15]] * [[http://wiki.alfresco.com/wiki/Configuring_the_CIFS_and_web_servers_for_Kerberos/AD_integration]] ==== Setup ==== - Copy ''/ntlm-authentication-context.xml'' to\\ ''/ntlm-authentication-context.xml'' - Add server property to that file - :!: Backup ''JBOSS_HOME/server/default/deploy/alfresco.war/WEB-INF/web.xml'' to\\ ''web.xml.original'' - :!: In ''web.xml'' uncomment NTLM filter and comment standard filters ===== LDAP User and Group sync ===== ==== References ==== * [[http://wiki.alfresco.com/wiki/Enterprise_Security_and_Authentication_Configuration]] * [[http://wiki.alfresco.com/wiki/Security_and_Authentication]] ==== Setup ==== - Copy from extension pack ''ldap-synchronisation-context.xml'' and\\ ''ldap-synchronisation.properties'' to '''' - Add in the xml a bean ''ldapInitialDirContextFactory'' and relating settings for this bean (get it from ''ldap-authentication-context.xml'' and ''ldap-authentication.properties'') instead of the existing alias. - Rename this bean to ''ldapSyncInitialDirContextFactory''\\ - Set the default properties relating to AD and add properties like in Table 1 - In ''/custom-authority-service-context.xml'' add and check admin user names. They HAVE TO BE case sensitiv even if the Alfresco setting for user names is "not case sensitiv". ^ Alfresco user property ^ AD property name ^ | company | organizationalId | | department | organization | | description | jobtitle | _{Table 1 - property relation Alfresco AD:} ===== Corrected and customized home folder creation ===== Alfresco creates the homefolder for users imported via LDAP automatically. Unfortunately these homefolders are located in the ''Company Home''. This task address that problem and place the homefolders into ''User Homes''. Additionally the inner structure of such a homefolder will be taken out of a template. - In ''/ldap-synchronisation.properties'' set\\ ''ldap.synchronisation.defaultHomeFolderProvider=userHomesHomeFolderProvider'' - Copy ''authentication-services-context.xml'' to\\ ''/custom-authentication-services-context.xml'' - In this file in the bean description for ''userHomesHomeFolderProvider'' add\\ property ''templatePath''. Point it to a folder which contains the user home template for example: /${spaces.company_home.childname}/${spaces.dictionary.childname}/${spaces.templates.childname}/cm:Homefolder - Take care! In ''ldap-synchronisation-context.xml'' the property\\ ''clearAllChildren'' of ''ldapPeopleImport'' MUST NOT set to true. ((I had activated this setting during the testphase to get new homefolders automatically during each LDAP lookup. But login and work inside the homefolder as a LDAP sync'd user results in tons of error messages.)) ~~DISCUSSION~~