InstallationLinux This page contains instructions on installing Alfresco within an existing Tomcat installation on your system. It assumes that you have a working Java installation and Tomcat instance installed.
If you do not have an existing application server installed then you may want to consider using the Alfresco installers for Linux or the Alfresco Tomcat Bundle for Linux instead. For more information please see the information on Linux download and installation.
Note: This is from the README_war.txt included in the alfresco-war download
Copy the JAR file into <container>/common/lib or <container>/server/default/lib
Alfresco requires a MySQL database named 'alfresco' with a user account and password of 'alfresco'. This can be set up automatically by logging into Mysql and executing the db_setup.sql that comes with the distribution.
Log into Mysql using an account with sufficient privileges to create a database
db_setup.sql can be found in the unpacked directory where you found the alfresco.war file.
Alternatively, you may enter in the commands manually:
mysql> CREATE DATABASE alfresco; mysql> CREATE USER 'alfresco'@'localhost' IDENTIFIED BY '<password>'; mysql> GRANT ALL PRIVILEGES ON alfresco.* TO 'alfresco'@'localhost';
You have now installed all the components needed to run the Alfresco server.
Optional Install of OpenOffice
Due to a bug in Alfresco 3.2r2, if you don't have OpenOffice installed and running, Alfresco will fail to start and throw an OpenOfficeExcpetion.
If you would like to have a range of document transformations available from within Alfresco, you need to install OpenOffice. This is entirely optional and can be done at any point after Alfresco has been installed.
There are known issues with OpenOffice 2.0.1 and 2.0.2
Configure the Database Connection and Data Locations
Before running the server for the first time, it is highly recommended that the database connection details and alfresco data folder locations get checked and set according to the environment in which the server is running. By default, the server will create a data folder for storing content binaries and indexes at a location relative to the caller's location when the server is started. This is appropriate for quick previews and tests, but should be changed when running a server that will be storing long-lived data.
Shut down your application server. You may also wish to stop the OpenOffice process, but the command for this depends on your platform.
If you have problems with your installation, please look for help on the Installation forum at http://forums.alfresco.com and ask for any additional help you may need.
If your application server fails to start then check that you have a working JDK installed and that the JAVA_HOME environment variable is set to the correct location of the JDK installation.
If you see errors of the type java.net.BindException: Address already in use: JVM_Bind on server startup, check to see if you have any services running against port 8080 for the Alfresco server and port 21 for the Alfresco FTP integration.
If you are running Alfresco as a normal (i.e. non superuser) account - as you should do - then you may also see JVM_Bind errors relating to the CIFS/SMB service or the FTP integration on the console indicating that Alfresco could not bind to the privileged ports required. To get around this problem you can configure Alfresco to use higher-numbered ports for FTP and SMB/CIFS using iptables to map back to the privileged ports as described in File Server Subsystem.
If the following errors are reported on the console, they are not issues which will cause the server to fail. Alfresco is merely reporting that various external document transformation engines are not available for use by the server.
ERROR [AbstractImageMagickContentTransformer] JMagickContentTransformer not available: ERROR [AbstractImageMagickContentTransformer] ImageMagickContentTransformer not available: Failed to execute command: imconvert ...