Result of the basic configuration will be an Alfresco system with following features:

This basic configuration starts with a fresh system installed like in 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 ¹⁾.
This folder is called <extension> 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 <config> tag.

1. Copy <default>/repository.properties to
   <extension>/custom-repository.properties
2. Copy custom-repository-context.xml.sample from the extensions folders inide the
   alfresco-community-war-2.9.0B to <extension>/custom-repository-context.xml.
3. Comment the Hibernate part inside the <extension>/custom-repository-context.xml. Otherwise the Spring Framework will not start.
4. Set root.dir to /usr/share/alfresco/.alf_data. ²⁾
5. 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.

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.

1. Copy <default>web-client-config.xml to <extension>web-client-config-custom.xml
   
2. Set in the <extension>web-client-config-custom.xml the edit-link-type setting to CIFS.
   

One of Alfrescos greatest benefits is the built-in CIFS server. So you can interact with the Alfresco repository with standard filesystem methods.

• CIFS Server Authentication
• File Server Configuration

1. Copy <default>file-servers.xml to <extension>file-servers-custom.xml
   
2. In <extension>file-servers-custom.xml remove all config blocks exept
   • CIFS Server
   • Filesystems
   • Filesystem Security
3. Set the replace=“true” attribut in these config tags
4. Set hostname, filesystem name, webpath and authenticator type=Alfresco
5. Activate the desktopActions