Alfresco Community 3.2 Ubuntu Package Explained
**NOTE: **This instructions apply to Jaunty Jackalope (9.04). The package is currently being updated for Karmic Koala (9.10).
UPDATED: Added link to CIFS/iptables configuration
UPDATED: *Added note about applying amp files.
A couple weeks back we released the Alfresco Community V3.2 for Ubuntu package. The package was developed in conjunction with Canonical. We’ve been working on this for a while, but now have in place a general structure that will enable us to deliver updates to the package in a timely fashion.
Which version of Ubuntu? What is installed?
This initial release is packaged for Ubuntu 9.04 (Jaunty Jackalope). There maybe some back ports coming for older Ubuntu releases but nothing definite at this time. The idea is to make Alfresco Community easy to install, with most functionality available right out of the box. We’ve made a concerted effort to use base packages from the Jaunty distro, only adding ours when needed. The major packages that are installed when Alfresco is installed are: Tomcat 6, Sun Java 6, Mysql 5.1, OpenOffice.org 3 (Headless), ImageMagick, pdf2swf (from swftools — this is our own packaged version of the devel branch. It will be replaced with the next release of swftools when it is updated in the base of the distro).
How Do I Install It?
The alfresco-community package is located in the Ubuntu partner repository. These instructions assume that you are using the command line. You can also use an X-Windows desktop to install alfresco. If you do, some of the steps are a bit different, but the general outline can be grasped from these instructions. So let’s start…
You can add the partner repository by editing
/etc/apt/sources.list. You need to uncomment the partner repo:
deb http://archive.canonical.com/ubuntu jaunty partner
deb-src http://archive.canonical.com/ubuntu jaunty partner
Next, you need to add the signed repository key:
sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys E048451D9EE6D873
Refresh the apt cache for the newly added repository:
sudo apt-get update
You can now install Alfresco:
apt-get install alfresco-community
You will be prompted to enter the mysql admin password, to accept the Sun Java license, configure the alfresco database username and password (the default is to choose alfresco/alfresco), allow for the automatic configuration of tomcat.
Where does everything get put?
Using one of the default linux installs from www.alfresco.com, you will typically find alfresco installed under
/opt/alfresco. By using the default tomcat, shipped with ubuntu, we followed its directory/configuration structure.
- Alfresco indexes and contentstore: The Alfresco indexes and contentstore can be found under
- Alfresco war files: The alfresco and share war files can be found under
- Alfresco extension directories: The extension directory, where you should make configuration changes to alfresco and share, can be found under
- Alfresco log files: The alfresco log files can be found under
/var/log/tomcat6Many of these directories are symbolic links to directories under
/usr/share/tomcat6. However, the default tomcat configuration points to the
By using the default tomcat we gain the advantage of an out of the box init script to control start and stop of Alfresco. You can now use
/etc/init.d/tomcat start|stop|restart|try-restart|force-reload|status to control or check the status of the tomcat server.
To change the startup parameters of tomcat or those of Alfresco, (ie. memory settings, configuring JMX, etc.) modify the JAVA_OPTS variable in
Tomcat is run using a non-root user. This means that Alfresco cannot open the ports needed for CIFS, FTP, or NFS. Follow the instructions to configure alfresco and iptables to listen on non-standard ports and perform port forwarding. (Look at David Baker’s blog for step by step instructions on how to configure Alfresco CIFs with port forwarding using iptables.) The same use of non standard ports and iptables configurations should be applied to inbound SMTP and IMAP configurations.
Here are a few other important things to note
AMP Files – One noticeable difference is that there is no apply_amps script. This is an oversight on my part and will be corrected in the next release. Meantime, if you want to apply an AMP, you can download the MMT tool and follow the instructions to install AMPs with MMT. Note: After applying an amp you will need to stop the alfresco server, remove the existing alfresco directory (
rm -rf /var/lib/tomcat6/webapps/alfresco) and start alfresco. The new war file which contains the amps will then be deploy
What does the future hold?
The plan we are discussing would be to provide the core repository and Alfresco Explorer as the central package, with separate packages for share, mobile, web studio, WCM and the filesystem receiver.
We are also open for suggestions. Let us know what you think.