Download and install Alfresco in Linux
From AlfrescoWiki
Note: This is from the README_war.txt included in the alfresco-war download
Contents |
[edit] Install Alfresco WAR Bundle
- Browse to http://www.alfresco.com/downloads
- Download the "Alfresco WAR Bundle" option
- Unzip alfresco-war-xxxxx.zip to a new directory or folder
- Copy the alfresco.war file to the appropriate location for your application server
If you have deployed previous versions of Alfresco, you may wish to remove any temporary files your application server has created.
NOTE: Alfresco 1.4 requires Tomcat 5 (and 5.5?) to be run with the -server option. For Fedora core 6, /etc/tomcat5/tomcat5.conf: CATALINA_OPTS="-server"
[edit] Add MySQL Database Connector
- Download the MySQL Java Database Connector http://dev.mysql.com/downloads/connector/j/
- Copy the JAR file into <container>/common/lib or <container>/server/default/lib
[edit] Create Database
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
- execute the db_setup.sql file
# 'mysql -u root -p mysql> source db_setup.sql Query OK, 1 row affected (0.00 sec) Query OK, 0 rows affected (0.00 sec) Query OK, 0 rows affected (0.00 sec)
- db_setup.sql can be found in the unpacked directory where you found the alfresco.war file.
<unpacked_directoy>/extras/databases/mysql/
You have now installed all the components needed to run the Alfresco server.
[edit] Optional Install of OpenOffice
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
- Browse to http://download.openoffice.org
- Download the appropriate version
- OpenOffice needs to be started in a specific way to work with Alfresco:
soffice "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" \ -nologo -headless
[edit] 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.
Details can be found here.
[edit] Running the Alfresco Server
Start your application server - you can now try Alfresco by visiting:
http://localhost:8080/alfresco
The first time you access the URL it will take some time as Alfresco is performing the database and filesystem initialization.
[edit] Logging In
The server is configured with a single administrative login with user name and password both set to 'admin'.
username: admin password: admin
[edit] Testing
To test the installation, you may wish to follow the tutorial, available from: http://dev.alfresco.com/tutorial_download.php or from the company space from within the Web Client.
[edit] Closing the Alfresco Server
Shut down your application server. You may also wish to stop the OpenOffice process, but the command for this depends on your platform.
[edit] Trouble-Shooting
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.
The JAVA_HOME variable must be set correctly to your Java5 installation.
[edit] Console Errors
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 ...
[edit] Startup Errors
If you see this error 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.
ERROR [protocol] FTP Socket error
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
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_Configuration.

